Configuring Gateway Controller (Nsm Procedure); Table 275: Data Inactivity Detection Configuration Details - Juniper NETWORK AND SECURITY MANAGER 2010.4 - M-SERIES AND MX-SERIES DEVICES GUIDE REV 1 Manual

M-series and MX-series Devices
466

Table 275: Data Inactivity Detection Configuration Details

Task
Configure data inactivity
detection.
Change the service state of
inactive terminations.

Configuring Gateway Controller (NSM Procedure)

You can configure a gateway controller either as a remote controller or as a local
controller. Configure the gateway controller as a remote controller if you are using an
external gateway controller and configure the gateway controller as a local controller if
you are using a border signaling gateway (BSG).
To configure gateway controller in NSM:
In the navigation tree select Device Manager > Devices.
1.
In the Devices list, double-click the device to select it.
2.
In the Configuration tab, expand Services > Pgcp.
3.
Select Gateway.
4.
Your Action
1. Expand Gateway.
2. Click Data Inactivity Detection next to Gateway.
3. In the Comment box, enter the comment.
4. From the Inactivity Delay list, select the time interval before
checking for media inactivity.
Range: 0 through 3600 seconds
Default: 5
5. From the Latch Deadlock delay list, select the time interval
before checking for data packets.
Range: 0 through 3600 seconds
6. Select the Send Notification on Delay check box to send an
inactivity notification immediately when no media packets
are detected during a delay period that precedes checking for
media inactivity.
7. From the Inactivity Duration list, select the time during which
no packets are received.
Range: 5 through 86400 seconds
Default: 30
8. Select the Stop Detection On Drop check box to configure
the BGF to stop inactivity detection when a gate action is set
to drop.
1. Expand Data Inactivity Detection.
2. Click Report Service Change next to Data Inactivity Detection.
3. In the Comment box, enter the comment.
4. From the Service Change Type list, select the method and
reason used in changing the service state of the termination
to active in order to curtail sending of inactivity messages.
forced-906—if the service is to be terminated using a forced
termination method with reason code 906 (loss of lower
layer connectivity).
forced-910—if the service is to be terminated using a forced
termination with reason code 910 (media capability failure).
Copyright © 2010, Juniper Networks, Inc.