Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Configuring PGCP (NSM Procedure)

    You can use the Packet Gateway Control Protocol (PGCP) options to configure the Border Gateway Function. See the following topics:

    Configuring Gateway (NSM Procedure)

    You can configure a virtual Border gateway Function (BGF) on the router by configuring gateway. See the following topics:

    Configuring a Virtual Border Gateway Function on the Router (NSM Procedure)

    You can configure a virtual BGF on the router using the Gateway option.

    To configure a virtual BGF on the router in NSM:

    1. In the navigation tree select Device Manager > Devices.
    2. In the Devices list, double-click the device to select it.
    3. In the Configuration tab, expand Services > Pgcp.
    4. Select Gateway.
    5. Add or modify the settings as specified in Table 1.
    6. Click one:
      • OK—To save the changes.
      • Cancel—To cancel the modifications.

    Table 1: Virtual BGF Configuration Details

    TaskYour Action

    Configure a virtual BGF on the router

    1. In the Name box, enter the identifier of the virtual BGF.
    2. In the Comment box, enter the comment.
    3. In the Gateway Address box, enter the IP address of the virtual BGF that you are configuring on the router.
    4. From the Gateway Port list, select the port number of the virtual BGF that you are configuring on the router.

      Range: 0 through 65,535

    5. From the Cleanup Timeout list, select the interval before inactivity detection starts.

      Range: 0 through 65,535 seconds

    6. From the Service State list, select the service state of the virtual BGF.
    7. From the Max Concurrent Calls list, select the Maximum number of concurrent calls on the virtual BGF.

      Range: 0 through 10,000

    Configuring Data Inactivity Detection (NSM Procedure)

    You can configure data inactivity detection to detect latch deadlocks or other media inactivity on a gate.

    To configure data inactivity detection on the router in NSM:

    1. In the navigation tree select Device Manager > Devices.
    2. In the Devices list, double-click the device to select it.
    3. In the Configuration tab, expand Services > Pgcp.
    4. Select Gateway.
    5. Add or modify the settings as specified in Table 2.
    6. Click one:
      • OK—To save the changes.
      • Cancel—To cancel the modifications.

    Table 2: Data Inactivity Detection Configuration Details

    TaskYour Action

    Configure data inactivity detection.

    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.

    Change the service state of inactive terminations.

    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).

    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:

    1. In the navigation tree select Device Manager > Devices.
    2. In the Devices list, double-click the device to select it.
    3. In the Configuration tab, expand Services > Pgcp.
    4. Select Gateway.
    5. Add or modify the settings as specified in Table 3.
    6. Click one:
      • OK—To save the changes.
      • Cancel—To cancel the modifications.

    Table 3: Gateway Controller Configuration Details

    TaskYour Action

    Configure a gateway controller.

    1. Click Add new entry next to Gateway.
    2. Click Gateway Controller next to gateway.
    3. Click Add new entry next to Gateway Controller.
    4. In the Name box, enter the name of the gateway controller or BSG.
    5. In the Comment box, enter the comment.
    6. In the Controller Address box, enter the IP address of the gateway controller.
    7. From the Controller Port list, select the port number of the gateway controller.

      Range: 0 through 65535

    8. Expand gateway-controller.
    9. Click Interim Ah Scheme.
    10. In the Comment box, enter the comment.
    11. From the Algorithm list, select the algorithm used for the interim AH scheme.

      HMAC null is currently the only algorithm supported

    Configuring Graceful Restart (NSM Procedure)

    You can configure graceful restart properties that are used during synchronization between the pgcpd process and the Multiservices PIC or DPC.

    To configure graceful restart in NSM:

    1. In the navigation tree select Device Manager > Devices.
    2. In the Devices list, double-click the device to select it.
    3. In the Configuration tab, expand Services > Pgcp.
    4. Select Gateway.
    5. Add or modify the settings as specified in Table 4.
    6. Click one:
      • OK—To save the changes.
      • Cancel—To cancel the modifications.

    Table 4: Graceful Restart Configuration Details

    TaskYour Action

    Configure graceful restart properties.

    1. Click Add new entry next to Gateway.
    2. Click Graceful Restart next to gateway.
    3. In the Comment box, enter the comment.
    4. From the Maximum Synchronization Time list, select the maximum time allowed for the synchronization procedure with the PIC or DPC.

      Range: 0 through 300

    5. From the Maximum Synchronization Mismatches list, select the maximum number of mismatches allowed during the synchronization procedure with the PIC or DPC.

      Range: 0 through 20000

    6. Select the No Synchronization check box to disable the synchronization procedure with the PIC.

    Configuring H248 Options Properties (NSM Procedure)

    You can configure properties for the H.248 options. See the following topics:

    Configuring H248 Options (NSM Procedure)

    You can configure options that affect virtual BGF H.248 behavior.

    To configure H248 options in NSM:

    1. In the navigation tree select Device Manager > Devices.
    2. In the Devices list, double-click the device to select it.
    3. In the Configuration tab, expand Services > Pgcp.
    4. Select Gateway.
    5. Add or modify the settings as specified in Table 5.
    6. Click one:
      • OK—To save the changes.
      • Cancel—To cancel the modifications.

    Table 5: H248 Configuration Details

    TaskYour Action

    Configure options that affect virtual BGF H.248 behavior.

    1. Click Add new entry next to Gateway.
    2. Click H248 Options next to gateway.
    3. In the Comment box, enter the comment.
    4. Select the Audit Observed Events Returns option to enable a history of media inactivity events to be viewed by the gateway controller.

    Changing Encoding Defaults (NSM Procedure)

    You can change the encoding defaults using this option.

    To configure encoding defaults in NSM:

    1. In the navigation tree select Device Manager > Devices.
    2. In the Devices list, double-click the device to select it.
    3. In the Configuration tab, expand Services > Pgcp.
    4. Select Gateway.
    5. Add or modify the settings as specified in Table 6.
    6. Click one:
      • OK—To save the changes
      • Cancel—To cancel the modifications

    Table 6: Encoding Defaults Configuration Details

    TaskYour Action

    Change encoding defaults.

    1. Click Add new entry next to Gateway.
    2. Click H248 Options next to gateway.
    3. Expand H248 Options.
    4. Click Encoding next to H248 Options.
    5. In the Comment box, enter the comment.
    6. Select the No Dscp Bit Mirroring check box to disable mirroring of DSCP bits.
    7. Select the Use Lower Case check box to configure upper-case encoding for H.248 messages.

    Configuring Service Change (NSM Procedure)

    Service change specifies the method and reason that the virtual BGF includes in ServiceChange commands that it sends to the gateway controller when the state of a control association, virtual interface, or context changes. See the following topics:

    Configuring Context Indications (NSM Procedure)

    Context indications specify the method and reason that the virtual BGF includes in Service-Interruption ServiceChange commands that it sends to the gateway controller when the gates of a context no longer provide their configured services. When the virtual BGF sends a Service-Interruption message, both terminations in the context become Out-of-Service.

    To configure context indications in NSM:

    1. In the navigation tree select Device Manager > Devices.
    2. In the Devices list, double-click the device to select it.
    3. In the Configuration tab, expand Services > Pgcp.
    4. Select Gateway.
    5. Add or modify the settings as specified in Table 7.
    6. Click one:
      • OK—To save the changes.
      • Cancel—To cancel the modifications.

    Table 7: Context indication Configuration Details

    TaskYour Action

    Configure context indications.

    1. Click Add new entry next to Gateway.
    2. Click H248 Options next to gateway.
    3. Expand H248 Options.
    4. Click Service Change next to H248 Options.
    5. In the Comment box, enter the comment.
    6. Select the Use Wildcard Response check box to enable the virtual BGF to issue service change commands as wildcard-response commands, which trigger a short response from the gateway controller.
    7. Expand Service Change.
    8. Click Context Indications next to Service Change.
    9. In the Comment box, enter the comment.
    10. From the State Loss list, select the method and reason that the virtual BGF includes in Service-Interruption ServiceChange commands that it sends to the gateway controller after a state loss on a specific context.

    Configure Control Association Indications (NSM Procedure)

    Specify the method and reason that the virtual BGF includes in ServiceChange commands that it sends to the gateway controller when the state of the control association changes.

    To configure control associations indications in NSM:

    1. In the navigation tree select Device Manager > Devices.
    2. In the Devices list, double-click the device to select it.
    3. In the Configuration tab, expand Services.
    4. Select Pgcp.
    5. Add or modify the settings as specified in Table 8.
    6. Click one:
      • OK—To save the changes.
      • Cancel—To cancel the modifications.

    Table 8: Control Association Configuration Details

    TaskYour Action

    Specify the method and reason that the virtual BGF includes in Registration Request ServiceChange commands when it attempts to reregister with the gateway controller or register with a new gateway controller after the control association is disconnected.

    1. Click Add new entry next to Gateway.
    2. Click H248 Options next to gateway.
    3. Expand H248 Options.
    4. Click Service Change next to H248 Options.
    5. Expand Service Change.
    6. Click Control Association Indications next to Service Change.
    7. In the Comment box, enter the comment.
    8. Expand Control Association Indications.
    9. Click Disconnect next to Control Association Indications.
    10. In the Comment box, enter the comment.
    11. From the Reconnect list, select the method and reason that the virtual BGF includes in Registration Request ServiceChange commands when it attempts to reregister with the gateway controller or register with a new gateway controller after the control association is disconnected.
    12. From the Controller Failure list, select the method and reason that the virtual BGF includes in Registration Request ServiceChange commands when it attempts to reregister with the gateway controller or register with a new gateway controller after the control association is disconnected.

    Specify the method and reason that the virtual BGF includes in Unregistration Messages in ServiceChange commands that it sends to the gateway controller when a control association transitions to Out-of-Service because of a failure.

    1. Click Down next to Control Association.
    2. In the Comment box, enter the comment.
    3. From the Administrative list, select the method and reason that the virtual BGF includes in Unregistration Messages in ServiceChange commands that it sends to the gateway controller when a control association transitions to Out-of-Service because of an administrative operation.
    4. From the Failure list, select the method and reason that the virtual BGF includes in Unregistration or Notification Messages in ServiceChange commands when a control association transitions to Out-of-Service.
    5. From the Graceful list, select the method and reason that the virtual BGF includes in Notification ServiceChange commands that it sends to the gateway controller when the control association transitions from In-Service to Out-of-Service-Graceful.

    Specify the method and reason that the virtual BGF includes in Notification Messages or Registration commands in ServiceChange commands when a control association transitions to In-Service.

    1. Click Up next to Control Association.
    2. In the Comment box, enter the comment.
    3. From the Failover Cold list, select the method and reason that the virtual BGF includes in Registration ServiceChange commands when it attempts to register with a new gateway controller following a cold failover.
    4. From the Failover Warm list, select the method and reason that the virtual BGF includes in Registration ServiceChange commands when it attempts to register with a new gateway controller following a warm failover.
    5. From the Cancel Graceful list, select the method and reason that the virtual BGF includes in Notification ServiceChange commands that it sends to the gateway controller when the control association transitions from the Draining state to the Forwarding state.

    Configuring Virtual Interface Indications (NSM Procedure)

    Virtual interface indications specify the method and reason that the virtual BGF includes in ServiceChange commands that it sends to the gateway controller when the state of the virtual interface changes.

    To configure virtual interface indications in NSM:

    1. In the navigation tree select Device Manager > Devices.
    2. In the Devices list, double-click the device to select it.
    3. In the Configuration tab, expand Services > Pgcp .
    4. Select Gateway.
    5. Add or modify the settings as specified in Table 9.
    6. Click one:
      • OK—To save the changes.
      • Cancel—To cancel the modifications.

    Table 9: Virtual Interface Indications Configuration Details

    TaskYour Action

    Specify the method and reason that the virtual BGF includes in ServiceChange commands that it sends to the gateway controller when the state of the virtual interface changes to Out-of-Service.

    1. Click Add new entry next to Gateway.
    2. Click H248 Options next to gateway.
    3. Expand H248 Options.
    4. Click Service Change next to H248 Options.
    5. Expand Service Change.
    6. Click Virtual Interface Indications next to Service Change.
    7. In the Comment box, enter the comment.
    8. Expand Virtual Interface Indications.
    9. Click Virtual Interface Down next to Virtual Interface Indications.
    10. In the Comment box, enter the comment.
    11. From the Graceful list, select the method and reason that the virtual BGF includes in Notification ServiceChange commands that it sends to the gateway controller when the control association transitions from In-Service to Out-of-Service-Graceful.
    12. From the Administrative list, select the method and reason that the virtual BGF includes in Unregistration Messages in ServiceChange commands that it sends to the gateway controller when a control association transitions to Out-of-Service because of an administrative operation.
    13. From the Failure list, select the method and reason that the virtual BGF includes in Unregistration or Notification Messages in ServiceChange commands when a control association transitions to Out-of-Service.
    14. From the Link Loss list, select the method and reason that the virtual BGF includes in Service-Interruption ServiceChange commands that it sends to the gateway controller when the virtual interface transitions to Out-of-Service because of a link loss.

    Specifying the ServiceChange command that the virtual BGF sends to the gateway controller when the state of the virtual interface changes to In-Service.

    1. Click Virtual Interface Up next to Virtual Interface Indications.
    2. In the Comment box, enter the comment.
    3. From the Warm list, select the method and reason that the virtual BGF includes in Service-Restoration ServiceChange commands that it sends to the gateway controller when a virtual interface transitions to In-Service.
    4. From the Cancel Graceful list, select the method and reason that the virtual BGF includes in Notification ServiceChange commands that it sends to the gateway controller when the control association transitions from the Draining state to the Forwarding state.

    Configuring H248 Properties (NSM Procedure)

    You can configure default values for H248 properties using the following options. See the following topics:

    Configuring Application Data Inactivity Detection (NSM Procedure)

    You can activate or deactivate regulated notification of media inactivity events.

    To configure application data inactivity detection in NSM:

    1. In the navigation tree select Device Manager > Devices.
    2. In the Devices list, double-click the device to select it.
    3. In the Configuration tab, expand Services > Pgcp.
    4. Select Gateway .
    5. Add or modify the settings as specified in Table 10.
    6. Click one:
      • OK—To save the changes
      • Cancel—To cancel the modifications

    Table 10: Data Inactivity Detection Configuration Details

    TaskYour Action

    Activate or deactivate regulated notification of media inactivity events.

    1. Click Add new entry next to Gateway.
    2. Click H248 Properties next to gateway.
    3. In the Comment box, enter the comment.
    4. Expand H248 Properties.
    5. Click Application Data Inactivity Detection next to H248 Properties.
    6. In the Comment box, enter the comment.
    7. From the IP Flow Stop Detection list, select the regulated or non-regulated (immediate) notification of media inactivity events.

    Configuring Base Root (NSM Procedure)

    You can configure default values for properties in the base root package using the Base Root option:

    To configure base root package in NSM:

    1. In the navigation tree select Device Manager > Devices.
    2. In the Devices list, double-click the device to select it.
    3. In the Configuration tab, expand Services > Pgcp.
    4. Select Gateway.
    5. Add or modify the settings as specified in Table 11.
    6. Click one:
      • OK—To save the changes.
      • Cancel—To cancel the modifications.

    Table 11: Base Root Package Configuration Details

    TaskYour Action

    Set default, maximum, and minimum values for the MG originated pending limit property of the base root package.

    1. Click Add new entry next to Gateway.
    2. Click H248 Properties next to gateway.
    3. Expand H248 Properties.
    4. Click Base Root next to H248 Properties.
    5. In the Comment box, enter the comment.
    6. Expand Base Root.
    7. Click Mg Originated Pending limit next to Base Root.
    8. In the Comment box, enter the comment.
    9. From the Default list, select the default number of transaction pending messages that the gateway controller can receive from the virtual BGF.

      Range: 1 through 512

    Set default, maximum, and minimum values for the MG provisional response timer property of the base root package.

    1. Click Mg Provisional Response Value Timer next to Base Root.
    2. In the Comment box, enter the comment.
    3. From the Default list, select the default time within which the gateway controller waits for a pending response from the virtual BGF if a transaction cannot be completed.

      Range: 500 through 3000 milliseconds

    Set default, maximum, and minimum values for the MGC originated pending limit property of the base root package.

    1. Click Mgc Originated Pending Limit next to Base Root.
    2. In the Comment box, enter the comment.
    3. From the Default list, select the default number of transaction pending messages that the virtual BGF can receive from the gateway controller.

      Range: 1 through 512

    Set default, maximum, and minimum values for the MGC provisional response timer value property of the base root package.

    1. Click Mgc Provisional Response Timer Value next to Base Root.
    2. In the Comment box, enter the comment.
    3. From the Default list, select the default time within which the virtual BGF waits for a pending response from the gateway controller if a transaction cannot be completed.

      Range: 500 through 3000 milliseconds

    Set default, maximum, and minimum values for the normal MG execution time property of the base root package.

    1. Click Normal Mg Execution Time next to Base Root.
    2. In the Comment box, enter the comment.
    3. From the Default list, select the default interval within which the gateway controller waits for a response to transactions from the virtual BGF.

      Range: 500 through 29000 milliseconds

    Set default, maximum, and minimum values for the normal MGC execution time property of the base root package.

    1. Click Normal Mgc Execution Time next to Base Root.
    2. In the Comment box, enter the comment.
    3. From the Default list, select the default interval within which the virtual BGF waits for a response to transactions from the gateway controller.

      Range: 500 through 29,000 milliseconds.

    Configuring Differentiated Services (NSM Procedure)

    You can configure default values for properties in the Differentiated Services (DiffServ) package using the Diffserv option.

    To configure DiffServ in NSM:

    1. In the navigation tree select Device Manager > Devices.
    2. In the Devices list, double-click the device to select it.
    3. In the Configuration tab, expand Services > Pgcp.
    4. Select Gateway.
    5. Add or modify the settings as specified in Table 12.
    6. Click one:
      • OK—To save the changes.
      • Cancel—To cancel the modifications.

    Table 12: DiffServ Configuration Details

    TaskYour Action

    Configure default values for properties in the Differentiated Services (DiffServ) package.

    1. Click Add new entry next to Gateway.
    2. Click H248 Properties next to gateway.
    3. Expand H248 Properties.
    4. Click Diffserv next to H248 Properties.
    5. In the Comment box, enter the comment.
    6. Click Dscp next to Diffserv.
    7. In the Comment box, enter the comment.
    8. From the Default list, select the default values for Differentiated Services Code Point (DSCP) marking that the virtual BGF uses for outgoing traffic when the DSCP value is not already defined by the gateway controller.

    Configuring Event Timestamp Notification (NSM Procedure)

    You can enable or disable the gateway controller to access timestamp information for media inactivity event notifications.

    To configure event timestamp notification in NSM:

    1. In the navigation tree select Device Manager > Devices.
    2. In the Devices list, double-click the device to select it.
    3. In the Configuration tab, expand Services > Pgcp .
    4. Select Gateway.
    5. Add or modify the settings as specified in Table 13.
    6. Click one:
      • OK—To save the changes.
      • Cancel—To cancel the modifications.

    Table 13: Event Timestamp Notification Configuration Details

    TaskYour Action

    Configure event timestamp notification.

    1. Click Add new entry next to Gateway.
    2. Click H248 Properties next to gateway.
    3. Expand H248 Properties.
    4. Click Event Timestamp Notification next to H248 Properties.
    5. In the Comment box, enter the comment.
    6. From the Request Timestamp list, select whether time stamp information is made available to the gateway controller or is suppressed.
      • Select requested to enable gateway controller access to time stamp information for notifications.
      • Select suppressed to disable gateway controller access to time stamp information for notifications.
      • Select autonomous which is equivalent to suppressed.

    Hanging Termination Detection (NSM Procedure)

    You can enable and configure hanging termination detection using this option.

    To configure hanging termination detection in NSM:

    1. In the navigation tree select Device Manager > Devices.
    2. In the Devices list, double-click the device to select it.
    3. In the Configuration tab, expand Services > Pgcp.
    4. Select Gateway.
    5. Add or modify the settings as specified in Table 14.
    6. Click one:
      • OK—To save the changes.
      • Cancel—To cancel the modifications.

    Table 14: Hanging Termination Detection Configuration Details

    TaskYour Action

    Configure hanging termination detection

    1. Click Add new entry next to Gateway.
    2. Click H248 Properties next to gateway.
    3. Expand H248 Properties.
    4. Click Hanging Termination Detection next to H248 Properties.
    5. In the Comment box, enter the comment.
    6. From the Timerx list, select the number of seconds between the last message exchanged for this termination and when the BGF sends a notification to the gateway controller.

      Range: 0 through 2,147,480

    Configuring Inactivity Timer (NSM Procedure)

    You can configure the inactivity timer package, which allows the BGF to use message inactivity to detect that its active gateway controller has failed using this option.

    To configure Inactivity Timer in NSM:

    1. In the navigation tree select Device Manager > Devices.
    2. In the Devices list, double-click the device to select it.
    3. In the Configuration tab, expand Services > Pgcp.
    4. Select Gateway.
    5. Add or modify the settings as specified in Table 15.
    6. Click one:
      • OK—To save the changes.
      • Cancel—To cancel the modifications.

    Table 15: Inactivity Timer Configuration Details

    TaskYour Action

    Configure the inactivity timeout event.

    1. Click Add new entry next to Gateway.
    2. Click H248 Properties next to gateway.
    3. Expand H248 Properties.
    4. Click Inactivity Timer next to H248 Properties.
    5. In the Comment box, enter the comment.
    6. Expand Inactivity Timer.
    7. Click Inactivity Timeout next to Inactivity Timer.
    8. In the Comment box, enter the comment.
    9. Select the Detect check box to specify the BGF detects inactivity timeout events received from the BGF by default.
    10. Expand Inactivity Timeout.

    Configure maximum inactivity time.

    1. Click Maximum Inactivity Time next to Inactivity Timeout.
    2. In the Comment box, enter the comment.
    3. From the Defaultlist, select the default value for the maximum inactivity time.

      Range: 100 through 65,535 (10-millisecond units)

    Configuring Notification Behavior (NSM Procedure)

    You can configure the default frequency for regulated media inactivity notifications sent by the BGF using the Notification Behavior option.

    To configure notification behavior in NSM:

    1. In the navigation tree select Device Manager > Devices.
    2. In the Devices list, double-click the device to select it.
    3. In the Configuration tab, expand Services > Pgcp.
    4. Select Gateway.
    5. Add or modify the settings as specified in Table 16.
    6. Click one:
      • OK—To save the changes.
      • Cancel—To cancel the modifications.

    Table 16: Notification Behavior Configuration Details

    TaskYour Action

    Configure the default frequency for sending media inactivity notifications for regulated events.

    1. Click Add new entry next to Gateway.
    2. Click H248 Properties next to gateway.
    3. Expand H248 Properties.
    4. Click Notification Behavior next to H248 properties.
    5. In the Comment box, enter the comment.
    6. Expand Notification Behavior.
    7. Click Notification Regulation next to Notification Behavior.
    8. In the Comment box, enter the comment.
    9. In the Default box, enter the default frequency for sending media inactivity notifications for regulated events.

    Configuring Segmentation (NSM Procedure)

    You can configure default values for properties in the segmentation package using this option.

    To configure segmentation in NSM:

    1. In the navigation tree select Device Manager > Devices.
    2. In the Devices list, double-click the device to select it.
    3. In the Configuration tab, expand Services > Pgcp.
    4. Select Gateway.
    5. Add or modify the settings as specified in Table 17.
    6. Click one:
      • OK—To save the changes.
      • Cancel—To cancel the modifications.

    Table 17: Segmentation Package Configuration Details

    TaskYour Action

    Set default, maximum, and minimum values for the MG maximum PDU size property of the segmentation package.

    1. Click Add new entry next to Gateway.
    2. Click H248 Properties next to gateway.
    3. Expand H248 Properties.
    4. Click Segmentation next to H248 properties.
    5. In the Comment box, enter the comment.
    6. Expand Segmentation.
    7. Click Mg Maximum Pdu Size next to Segmentation.
    8. In the Comment box, enter the comment.
    9. From the Default list, select the default maximum size of messages that the gateway controller sends to the BGF.

      Range: 512 through 65,507 bytes

    Set default, maximum, and minimum values for the MG segmentation timer value property of the segmentation package.

    1. Click Mg Segmentation Timer next to Segmentation.
    2. In the Comment box, enter the comment.
    3. From the Default list, select the default time within which the gateway controller waits to receive outstanding message segments from the virtual BGF after it receives the SegmentationCompleteToken.

      Range: 500 through 30,000 milliseconds

    Set default, minimum, and maximum values for the MGC maximum Protocol Data Unit (PDU) size property of the segmentation package.

    1. Click Mgc Maximum Pdu Size next to Segmentation.
    2. In the Comment box, enter the comment.
    3. From the Default list, select the default maximum size of messages that the virtual BGF sends to the gateway controller.

      Range: 512 through 65,507 bytes

    Set default, maximum, and minimum values for the MGC segmentation timer value property of the segmentation package.

    1. Click Mgc Segmentation Timer next to Segmentation.
    2. In the Comment box, enter the comment.
    3. From the Default list, select the default time within which the virtual BGF waits to receive outstanding message segments from the gateway controller after it receives the SegmentationCompleteToken.

      Range: 500 through 30,000 milliseconds

    Configuring Traffic Management (NSM Procedure)

    You can configure traffic management of the gate stream and the RTP Control Protocol (RTCP) stream. The parameters for the RTCP stream take effect only when the gate is an Real-time Transport Protocol (RTP)/RTCP gate.

    To configure traffic management in NSM:

    1. In the navigation tree select Device Manager > Devices.
    2. In the Devices list, double-click the device to select it.
    3. In the Configuration tab, expand Services > Pgcp.
    4. Select Gateway.
    5. Add or modify the settings as specified in Table 18.
    6. Click one:
      • OK—To save the changes.
      • Cancel—To cancel the modifications.

    Table 18: Traffic Management Configuration Details

    TaskYour Action

    Configure the maximum burst size for RTP/RTCP gate streams.

    1. Click Add new entry next to Gateway.
    2. Click H248 Properties next to gateway.
    3. Expand H248 Properties.
    4. Click Traffic Management next to H248 properties.
    5. In the Comment box, enter the comment.
    6. Click Max Burst Size next to Traffic Management.
    7. In the Comment box, enter the comment.
    8. From the Default list, select the default maximum burst size.

      Range: 20 through 2147483647 bytes

    9. Expand Maximum Burst Size.
    10. Click Rtcp next to Maximum Burst Size.
    11. In the Comment box, enter the comment.
    12. Expand Rtcp.
    13. Click Percentage next to Rtcp.
    14. Select one of the following:
      • percentage—if the value entered is a percentage of the RTP gate’s rate.
      • fixed-value—if the value entered is a fixed number of bytes per second.

        Range: 20 through 2147483647 bytes-per-second

    Configure the peak data rate for RTP/RTCP gate streams.

    1. Click Peak Data Rate next to Traffic Management.
    2. In the Comment box, enter the comment.
    3. From the Default list, select the default peak data rate.

      Range: 125 through 2147483647 bytes per second

    4. Expand Peak Data Rate.
    5. Click Rtcp next to Peak Data Rate.
    6. In the Comment box, enter the comment.
    7. Expand Rtcp.
    8. Click Percentage next to Rtcp.
    9. Select one of the following:
      • percentage—if the value entered is a percentage of the RTP’s gate rate.
      • fixed-value—if the value entered is a fixed number of bits per second.

        Range: 0 through 2147483647

    Configure the sustained data rate for streams of any protocol, including RTP.

    1. Click Sustained Data Rate next to Traffic Management.
    2. In the Comment box, enter the comment.
    3. From the Default list, select the default value for sustained data rate.

      Range: 125 through 4,294,967,295 bytes per second

    4. Expand Sustained Data Rate.
    5. Click Rtcp next to Sustained Data Rate.
    6. In the Comment box, enter the comment.
    7. Expand Rtcp.
    8. Click Percentage next to Rtcp.
    9. Select one of the following:
      • percentage—if the value entered is a percentage of the RTP’s gate rate.
      • fixed-value—if the value entered is a fixed number of bits per second.

        Range: 0 through 2147483647

    Configuring H248 Timers (NSM Procedure)

    You can configure H.248 timers for the PGCP connection using the H248 Timers option.

    To configure H248 timers in NSM:

    1. In the navigation tree select Device Manager > Devices.
    2. In the Devices list, double-click the device to select it.
    3. In the Configuration tab, expand Services > Pgcp.
    4. Select Gateway.
    5. Add or modify the settings as specified in Table 19.
    6. Click one:
      • OK—To save the changes.
      • Cancel—To cancel the modifications.

    Table 19: H248 Timers Configuration Details

    TaskYour Action

    Configure H248 Timers.

    1. Click Add new entry next to Gateway.
    2. Click H248 Timers next to gateway.
    3. In the Comment box, enter the comment.
    4. From the Maximum Waiting Delay list, select the maximum time the virtual BGF waits before contacting a new gateway controller when the connection to the controlling gateway controller is lost.

      Range: 100 through 300000 milliseconds

      Default: 3000

    5. From the Tmax Retransmission Delay list, select the duration of the delay before the BGF considers the gateway controller to be down.

      Range: 1000 through 60000 milliseconds

      Default: 25000

    6. From the Initial Average Ack Delay list, select the assumed initial average delay.

      Range: 500 through 4000 milliseconds

      Default: 1000

    7. From the Maximum Net Propagation Delay list, select the duration of the maximum network propagation delay time.

      Range: 500 through 10000 milliseconds

      Default: 5000

    Configuring the Monitor (NSM Procedure)

    You can enable Real-Time Control Protocol (RTCP) and Real-Time Transport Protocol (RTP) application-level gateways (ALGs) for media flows and monitor packets using the Monitor option.

    To configure the monitor in NSM:

    1. In the navigation tree select Device Manager > Devices.
    2. In the Devices list, double-click the device to select it.
    3. In the Configuration tab, expand Services > Pgcp.
    4. Select Gateway.
    5. Add or modify the settings as specified in Table 20.
    6. Click one:
      • OK—To save the changes.
      • Cancel—To cancel the modifications.

    Table 20: Monitor Configuration Details

    TaskYour Action

    Configure the monitor.

    1. Click Add new entry next to Gateway.
    2. Click Monitor next to gateway.
    3. In the Comment box, enter the comment.
    4. Expand Monitor.
    5. Click Media next to Monitor.
    6. In the Comment box, enter the comment.
    7. Select the Rtp check box to enable Real-Time Transport Protocol (RTP) application-level gateway (ALG) on media flows created when the gateway controller installs media gates on the virtual BGF.
    8. Select the Rtcp check box to enable Real-Time Control Protocol (RTCP) application-level gateway (ALG) on media flows created when the gateway controller installs media gates on the virtual BGF.

    Configuring Overload Control (NSM Procedure)

    You can configure the BGF to send overload messages to the gateway controller based on the status of its work queue. The overload messages cause the gateway controller to lower the rate at which it admits packets for processing.

    To configure overload control in NSM:

    1. In the navigation tree select Device Manager > Devices.
    2. In the Devices list, double-click the device to select it.
    3. In the Configuration tab, expand Services > Pgcp.
    4. Select Gateway.
    5. Add or modify the settings as specified in Table 21.
    6. Click one:
      • OK—To save the changes.
      • Cancel—To cancel the modifications.

    Table 21: Overload Control Configuration Details

    TaskYour Action

    Configure the BGF to send overload messages.

    1. Click Add new entry next to Gateway.
    2. Click Overload Control next to gateway.
    3. In the Comment box, enter the comment.
    4. From the Queue Limit Percentage list, select the percentage of the overload control work queue in use that triggers creation of an overload notification.

      Range: 1 through 100

    Configuring Session Mirroring (NSM Procedure)

    You can configure the session mirroring feature using the Session Mirroring option.

    To configure session mirroring in NSM:

    1. In the navigation tree select Device Manager > Devices.
    2. In the Devices list, double-click the device to select it.
    3. In the Configuration tab, expand Services > Pgcp.
    4. Select Gateway.
    5. Add or modify the settings as specified in Table 22.
    6. Click one:
      • OK—To save the changes.
      • Cancel—To cancel the modifications.

    Table 22: Session Mirroring Configuring Details

    TaskYour Action

    Configure the delivery function that receives the session mirroring information.

    1. Click Add new entry next to Gateway.
    2. Click Session Mirroring next to gateway.
    3. In the Comment box, enter the comment.
    4. Select the Disable Session Mirroring check box to disable the session mirroring feature.
    5. Expand Session Mirroring.
    6. Click Delivery Function next to Session Mirroring.
    7. Click Add new entry next to Delivery Function.
    8. In the New delivery-function window, enter the name of the delivery function that receives the session mirroring information.

    Configuring Media Service (NSM Procedure)

    You can configure media services for the Border gateway Function (BGF) configuration. Media services are applied to Packet Gateway Control Protocol (PGCP) packets.

    To configure media service in NSM:

    1. In the navigation tree select Device Manager > Devices.
    2. In the Devices list, double-click the device to select it.
    3. In the Configuration tab, expand Services > Pgcp.
    4. Select Media Service.
    5. Add or modify the settings as specified in Table 23.
    6. Click one:
      • OK—To save the changes.
      • Cancel—To cancel the modifications.

    Table 23: Media Service Configuration Details

    TaskYour Action

    Configure media service.

    1. Click Add new entry next to Media Service.
    2. In the Name box, enter the identifier for the media service name.
    3. In the Comment box, enter the comment.
    4. In the Nat Pool box, enter the identifier for the NAT address pool.

    Configuring a Rule (NSM Procedure)

    You can specify the rule that the router uses when it applies the media service.

    To configure a rule in NSM:

    1. In the navigation tree select Device Manager > Devices.
    2. In the Devices list, double-click the device to select it.
    3. In the Configuration tab, expand Services > Pgcp.
    4. Select Rule.
    5. Add or modify the settings as specified in Table 24.
    6. Click one:
      • OK—To save the changes.
      • Cancel—To cancel the modifications.

    Table 24: Configuring Rule

    TaskYour Action

    Configure a rule.

    1. Click Add new entry next to Rule.
    2. In the Name box, enter the identifier for the rule.
    3. In the Comment box, enter the comment.
    4. From the Gateway list, select the identifier of the virtual BGF.
    5. Expand rule.
    6. Click Media Service next to rule.
    7. Click Add new entry next to Media Service.
    8. In the New media-service window, enter the identifier for the media service name.

    Configuring Rule Set (NSM Procedure)

    You can specify the rule set the router uses when applying this service.

    To configure Rule Set in NSM:

    1. In the navigation tree select Device Manager > Devices.
    2. In the Devices list, double-click the device to select it.
    3. In the Configuration tab, expand Services > Pgcp.
    4. Select Rule Set.
    5. Add or modify the settings as specified in Table 25.
    6. Click one:
      • OK—To save the changes.
      • Cancel—To cancel the modifications.

    Table 25: Configuring Rule Set

    TaskYour Action

    Configure a rule set.

    1. Click Add new entry next to Rule Set.
    2. In the Name box, enter the identifier for the collection of rules that make up this rule set.
    3. In the Comment box, enter the comment.
    4. Expand rule-set.
    5. Click Rule next to rule-set.
    6. Click Add new entry next to Rule.
    7. From the Name list, select the identifier for the rule.
    8. In the Comment box, enter the comment.

    Configuring Session Mirroring (NSM Procedure)

    You can configure the session mirroring feature using the session mirroring option.

    To configure session mirroring in NSM:

    1. In the navigation tree select Device Manager > Devices.
    2. In the Devices list, double-click the device to select it.
    3. In the Configuration tab, expand Services > Pgcp.
    4. Select Session Mirroring.
    5. Add or modify the settings as specified in Table 26.
    6. Click one:
      • OK—To save the changes.
      • Cancel—To cancel the modifications.

    Table 26: Session Mirroring Configuration Details

    TaskYour Action

    Configure session mirroring.

    1. In the Comment box, enter the comment.
    2. Select the Disable Session Mirroring check box to disable session mirroring on the BGF.
    3. Expand Session Mirroring.
    4. Click Delivery Function next to Session Mirroring.
    5. Click Add new entry next to Delivery Function.
    6. In the Name box, enter the name of the delivery function that receives the session mirroring information.
    7. In the Comment box, enter the comment.
    8. In the Destination Address box, enter the address of the server to which the BGF sends session-mirroring information.
    9. From the Destination Port list, select the port on the delivery function server that receives session-mirroring information.

      Range: 0 through 65535

    10. In the Network Operator Id box, enter the network operator ID. The ID can be up to five characters.
    11. In the Source Address box, enter the address of the interface on which the BGF sends session-mirroring data to the delivery function.
    12. From the Source Port list, select the port on which the BGF sends session-mirroring data to the delivery function.

      Range: 0 through 65,535

    13. Expand delivery-function.
    14. Click Memory Management next to delivery-function.
    15. In the Comment box, enter the comment.
    16. From the Operational Mode list, select the operational mode.

    Configuring Traceoptions (NSM Procedure)

    You can configure Packet Gateway Control Protocol (PGCP) trace options using the traceoptions option.

    To configure traceoptions in NSM:

    1. In the navigation tree select Device Manager > Devices.
    2. In the Devices list, double-click the device to select it.
    3. In the Configuration tab, expand Services > Pgcp.
    4. Select Traceoptions.
    5. Add or modify the settings as specified in Table 27.
    6. Click one:
      • OK—To save the changes.
      • Cancel—To cancel the modifications.

    Table 27: Traceoptions Configuration Details

    TaskYour Action

    Configure PGCP trace options.

    1. In the Comment box, enter the comment.
    2. Select the No Remote Trace check box to disable remote tracing.
    3. Expand Traceoptions.
    4. Click File next to Traceoptions.
    5. In the Comment box, enter the comment.
    6. In the Filename box, enter the name of the file to which the tracing messages are written.
    7. In the Size box, enter the size parameter (in bytes) to trigger rotation of files.
    8. From the Files list, select the number of trace files.
    9. Select one of the following:
      • world-readable—To allow all users to use the log file.
      • no-world-readable—To disallow all users from using the log file.
    10. In the Match box, enter the regular expression.
    11. Click Flag next to Traceoptions.
    12. Click Add new entry next to Flag.
    13. In the Comment box, enter the comment.

    Configuring Virtual Interface (NSM Procedure)

    You can configure a virtual interface for the BGF using the Virtual Interface option.

    To configure virtual interface in NSM:

    1. In the navigation tree select Device Manager > Devices.
    2. In the Devices list, double-click the device to select it.
    3. In the Configuration tab, expand Services > Pgcp.
    4. Select Virtual Interface.
    5. Add or modify the settings as specified in Table 28.
    6. Click one:
      • OK—To save the changes.
      • Cancel—To cancel the modifications.

    Table 28: Virtual Interface Configuration Details

    TaskYour Action

    Configure a virtual interface

    1. Click Add new entry next to Virtual Interface.
    2. In the Name box, enter the identifier number for the interface.

      Range: 0 through 1023

    3. In the Comment box, enter the comment.
    4. From the Service State list, select the service state of the virtual interface.
    5. In the Interface box, enter the interface name.
    6. Expand virtual-interface.
    7. Click Media Service next to virtual-interface.
    8. Click Add new entry next to Media Service.
    9. In the dialog box, enter the identifier for the media service name.
    10. Click Routing Instance next to virtual-interface.
    11. In the Comment box, enter the comment.
    12. From the Routing Instance Name list, select the name of a routing instance.
    13. In the Service Interface box, enter the name and logical interface number of the service Interface in interface-name.unit-number form.

    Published: 2013-01-02