Reports the maximum total length, in seconds, a session on this service is allowed to run before SSG ends it regardless of activity; 0 means no such cap. Unlike the idle timeout, this fires even on a session that's actively passing traffic the whole time, so it's the control that enforces a hard session-length policy, common on time-boxed trial or hourly-billed access, rather than reclaiming genuinely-idle sessions. A '1-hour free trial' service would show cssgServiceSessionTimeout as 3600, ending the session at the one-hour mark even if the subscriber is actively streaming right up to the cutoff.