[an error occurred while processing this directive][an error occurred while processing this directive]

Configuring Latch Deadlock and Media Inactivity Detection

The gateway can request to be notified by the virtual BGF when a latching deadlock or media inactivity exists on a gate. You can configure latching deadlock and media inactivity detection parameters for use by the virtual BGF when it monitors media traffic that is flowing through the gate.

Latch deadlock detection is defined in Gateway Control Protocol: Application Data Inactivity Package, ITU-T Recommendation H.248.40, January, 2007.

To configure parameters for latching deadlock and media inactivity detection:

  1. Access the configuration of your virtual BGF and specify data inactivity detection.
    [edit services pgcp]user@host# edit gateway bgf-1 data-inactivity-detection
  2. Configure the number of seconds before the virtual BGF begins checking for media inactivity on new gates for which there is a latching signal.
    [edit services pgcp gateway bgf-1 data-inactivity-detection]user@host# set latch-deadlock-delay 10
  3. Configure the number of seconds before the virtual BGF begins checking for media inactivity on new gates that do not have a latching signal.
    [edit services pgcp gateway bgf-1 data-inactivity-detection]user@host# set inactivity-delay 10
  4. Configure the duration of inactivity detection checks that the virtual BGF performs on a gate. If no media packets are received during a check, the virtual BGF sends the gateway controller a quality (QUA) alert, ADID alert, or service change notification. If media packets are received, the timer is reset and checking continues. This parameter applies to all gates, regardless of whether there is a latching signal for the gate.
    [edit services pgcp gateway bgf-1 data-inactivity-detection]user@host# set inactivity-duration 60
  5. Configure the virtual BGF to stop inactivity detection when a gate action is set to drop. Use this option to handle calls that are placed on hold. When calls are resumed, the BGF starts the delay timer and resumes data inactivity detection. By default, inactivity detection continues when a gate is ready to drop
    [edit services pgcp gateway bgf-1 data-inactivity-detection]user@host# set inactivity-duration
  6. Specify that a notification (or service change) occur immediately when no media packets are detected during the initial checking delay period (latch-deadlock-delay or inactivity-delay). By default, inactivity is not reported until the delay period and an inactivity duration period have elapsed.
    [edit services pgcp gateway bgf-1 data-inactivity-detection]user@host# set send-notification-on-delay
  7. Request a service change to take gates with latch deadlocks or media inactivity out of service, dropping all packets for the gates. Specify whether to notify the gateway controller with error code 906 (loss of lower layer connectivity) or 910 (media capability failure).
    [edit services pgcp gateway bgf-1 data-inactivity-detection]user@host# edit report-service-change[edit services pgcp gateway bgf-1 data-inactivity-detection report-service-change]user@host# set service-change-type forced-910

Published: 2010-04-13

[an error occurred while processing this directive]