Per-Realm Media Guard Timers

Oracle Communications Session Border Controller realm configurations support media guard timers whose settings take precedence over global media guard timers configured in the media manager. Both generic flow and TCP-specific flow timer settings are available. The user configures these timers in seconds in the realm-config.

Media guard timer parameters configured within a realm use the same syntax and define the same windows as the global timers. They differ in that they affect flows that traverse the realm only. Applicable timers include:

• flow-time-limit
• initial-guard-timer
• subsq-guard-timer
• tcp-flow-time-limit
• tcp-initial-guard-timer
• tcp-subsq-guard-timer

Per-realm media guard timer settings differ slightly from the global timers:

• The default value of -1 disables the realm setting, allowing the system to fall back to the global timer settings.
• A value of 0 disables the use of that type of timer for all flows traversing that realm, regardless of whether there are enabled ingress, egress or global settings.
• Timer ranges differ, as documented in the command reference.

Important operational considerations include:

• The system refers to both ingress and egress realm settings to time each flow, using the lower settings to resolve setting conflicts.
• Upon the expiry of the flow timer sequence, the Oracle Communications Session Border Controller sends a BYE that includes reason header indicating that the system has cleared the session due to media flow guard timer expiry.
• This feature interacts with guard-notify-gap in the media manager. When a flow guard timer expiry is received by MBCD, and if the required 'gap' since the last notification has not elapsed, the system queues the new notification to be sent when the required notify gap time has elapsed.

Note:

Media guard timers in static flow configurations are not impacted by per-realm (or global) media timers. Per-realm and global timers are for dynamic flows.