COMMAND DESCRIPTION     27/190 82-CRA 119 1170/1 Uen C    

BGF Command Reference

© Ericsson AB 2009–2010. All rights reserved. No part of this document may be reproduced in any form without the written permission of the copyright owner.

Disclaimer

The contents of this document are subject to revision without notice due to continued progress in methodology, design and manufacturing. Ericsson shall have no liability for any error or damage of any kind resulting from the use of this document.

Trademark List

SmartEdge is a registered trademark of Telefonaktiebolaget LM Ericsson.

Contents

1Command Descriptions
1.1clear media-gateway [instance] mgc-group
1.2clear media-gateway [instance] statistics
1.3debug sctp
1.4debug [standby] media-gateway [instance]
1.5debug media-gateway manager
1.6default-realm
1.7extended-port-range
1.8maximum
1.9maximum (realm)
1.10media-gateway
1.11media-gateway-controller
1.12media-local-address
1.13mgc-group
1.14process mgd
1.15process mgmd
1.16profile
1.17qos mark out dcsp
1.18realm
1.19reserve calls
1.20segmentation
1.21show media-gateway [instance]
1.22show media-gateway [instance] circuit
1.23show media-gateway instance media-flow
1.24show media-gateway [instance] mgc-group
1.25show media-gateway [instance] statistics
1.26show process mgd
1.27show process mgmd
1.28show process sctp
1.29show sctp
1.30shutdown
1.31signaling-endpoint
1.32timers
1.33transaction-response-ack
1.34transport


1   Command Descriptions

All commands for border gateway function features are included.

1.1   clear media-gateway [instance] mgc-group

clear media-gateway [instanceinstance-id] mgc-group name

1.1.1   Purpose

Clears information about the MGC group for all media gateway (MG) instances or a specified MG instance in the specified MGC group.

1.1.2   Command Mode

exec mode (10)

1.1.3   Syntax Description

instance instance-id

Optional. Instance ID. Specify the instance ID of the border gateway function (BGF) for which to clear information. The range of values is 1 to 3.

mgc-group-name

Media gateway controller (MGC) group name. Specify the MGC group name for which to clear information. The valid value is an alphanumeric string of up to 30 characters.

1.1.4   Default

None

1.1.5   Usage Guidelines

Use the clear media-gateway mgc-grp command to clear information for all virtual media gateways (VMGs) or a specified VMG instance in the specified MGC group. To clear the information, this command shuts down and then brings up the affected VMGs at the MG group level.

1.1.6   Examples

The following example shows how to clear information for VMG instance 3 in MGC group group2.

[local]Redback#clear media-gateway instance 3 mgc-group group2

The following example shows how to clear information for all VMG instances in the MGC group group2.

[local]Redback#clear media-gateway mgc-group group2

1.2   clear media-gateway [instance] statistics

clear media-gateway [instance instance-id] statistics { call rate | mgc-group name}

1.2.1   Purpose

Clears statistical information about all of the virtual media gateways (VMGs) or a specified VMG instance.

1.2.2   Command Mode

exec mode (10)

1.2.3   Syntax Description

mgc-grp mgc-group-name

Media gateway controller (MGC) group name. Specify the MGC group name for which to clear statistical information. The valid value is an alphanumeric string of up to 30 characters.

statistics call rate

Clear VMG call rate statistics.

1.2.4   Default

None

1.2.5   Usage Guidelines

Use the clear statistics media-gateway command to clear statistical information about all of the VMGs or a specified VMG instance.

This command clears all signalling and media statistics.

1.2.6   Examples

The following example shows how to clear VMG statistics within the MGC group group7 of the MG instance 3

[local]Redback#clear media-gateway instance 3 mgc-group group7

1.3   debug sctp

debug sctp

no debug sctp

1.3.1   Purpose

Enables generation of debug messages for events related to the Stream Control Transmission Protocol (SCTP).

1.3.2   Command Mode

exec

1.3.3   Syntax Description

This command has no keywords or arguments.

1.3.4   Default

Generation of debug messages is disabled.

1.3.5   Usage Guidelines

Use the debug sctp command to enable generation of debug messages for SCTP events. SCTP is used on the media gateway (MG) to transport H.248 control messages between the MG and the controlling device.


 Caution! 
Risk of performance loss. Enabling generation of debug messages can severely affect system performance. To reduce the risk, exercise caution when enabling generation of debug messages on a production system.

To store debug messages in the system log buffer, use the logging debug command (in global configuration mode). Use the show log command (in exec mode) to display these stored debug messages.

To display messages in real time, use the logging console command (in context configuration mode) if you are connected to the system through the console port. Use the terminal monitor command (in exec mode) if you are connected to the system through a Telnet or Secure Shell (SSH) session.

Note:  
For more information about logging commands, see the Logging document.

Use the no form of this command to disable generation of debug messages.

1.3.6   Examples

The following example shows how to enable generation of debug messages for SCTP:

[local]Redback#debug sctp

1.4   debug [standby] media-gateway [instance]

debug [standby] media-gateway [instance instance-id] {all | call | caudit | config | general | ips | manager | media | pkg | port-table | protocol | rcm | resource | shm}

1.4.1   Purpose

Enables generation of debug messages for media gateway (MG) daemons.

1.4.2   Command Mode

exec (10)

1.4.3   Syntax Description

Enables generation of debug messages for:

all

All MG daemon functions available in this mode.

caudit

All MG daemon configuration audits.

call

MG calls.

config

Back-end configuration handling.

general

General operation.

ips

Enables buffer tracing for IPS.

media

Media traffic.

pkg

Package operations.

port-table

Port table.

protocol

H.248 protocol processing. Optional.

rcm

Router Configuration Manager (RCM).

resource

Resource processing. Optional.

shm

Shared memory.

1.4.4   Default

Generation of debug messages for the MG daemons is disabled.

1.4.5   Usage Guidelines

Use the debug media-gateway command to enable generation of debug messages for MG daemons. Use the debug standby media-gateway command to enable generation of debug messages for MG daemons on the standby controller card in a SmartEdge® router. Specify the instance keyword to enable debug messages for the daemons of a specified MG instance.

Use the no form of this command to disable generation of debug messages for the specified type of MG daemon.

1.4.6   Example

The following example enables generation of debug messages for all media gateway daemons:

[local]Redback#debug media-gateway all
[local]Redback#

1.5   debug media-gateway manager

debug media-gateway manager {all | call | caudit | config | general | ppa | rcm | resource | shm}

1.5.1   Purpose

Enables generation of debug messages for media gateway manager (MGM) daemons.

1.5.2   Command Mode

exec (10)

1.5.3   Syntax Description

Enables generation of debug messages for:

all

All MGM functions available in this mode.

caudit

All MGM daemon configuration audits.

config

Back-end configuration handling.

general

General operation.

ppa

PPA interactions.

rcm

Router Configuration Manager (RCM).

resource

Resource processing. Optional.

shm

Shared memory.

1.5.4   Default

Generation of debug messages for the MGM events is disabled.

1.5.5   Usage Guidelines

Use the debug media-gateway command to enable generation of debug messages for MGM daemons. Use the debug standby media-gateway command to enable generation of debug messages for MGM daemons on the standby controller card in a SmartEdge router.

Use the no form of this command to disable generation of debug messages for the specified type of MGM daemons.

1.5.6   Example

The following example enables generation of debug messages for MGM general operations:

[local]Redback#debug media-gateway manager general
[local]Redback#

1.6   default-realm

default-realm realm-name

1.6.1   Purpose

Configures the default realm for the media gateway controller (MGC) group.

1.6.2   Command Mode

MGC group configuration

1.6.3   Syntax Description

realm-name

Default realm name. The valid value is an alphanumeric string of up to 63 characters.

1.6.4   Default

The default realm is local.

1.6.5   Usage Guidelines

Use the default-realm command to configure the default realm to use for the MG. If no realm is specified by the Session Gateway Controller (SGC) for a call, the configured default realm is used.

Use the no form of this command to return to the default setting of local.

1.6.6   Example

The following example shows how to configure the default realm named defaultaccess1 for the MG:

[local]Redback(config-grp)#default-realm defaultaccess1
[local]Redback(config-grp)#

1.7   extended-port-range

extended-port-range

1.7.1   Purpose

Specifies to use ports in the range of 32K to 48K for the configured loopback IP address.

1.7.2   Command Mode

realm MG configuration

1.7.3   Syntax Description

This command has no keywords or arguments.

1.7.4   Default

The port range of 16K to 32K is used for an IP address.

1.7.5   Usage Guidelines

Use the extended-port-range command to specify to use ports in the range 32K to 48K for the configured loopback IP address. This command allows you to maximize the port usage per configured loopback IP address. Use the no form of this command to return to the default behavior. Removing the extended port range deletes calls gracefully.

Note:  
This command is supported only for configurations where the SmartEdge OS is used only as a border gateway function (BGF).

Note:  
Before using extended-port-range command, ensure that there are no port conflicts for the configured loopback IP address. Do not use this command if the same loopback IP address is also used as the H.248 local signalling IP address.

1.7.6   Example

The following example shows how to specify the extended port range for interface media20, which has a loopback address used for media traffic within the realm. This interface is configured in interface configuration mode, in the same context in which the realm is configured.

[local]Redback(config-realm)#media-local-address interface media20
[local]Redback(config-realm-media)#extended-port-range

1.8   maximum

maximum {calls | signaling-rtt | pending-responses} value

no maximum {calls | signaling-rtt | pending-responses}

1.8.1   Purpose

Sets system maximum values related to the media gateway controller (MGC) group function.

1.8.2   Command Mode

MGC configuration (global)

1.8.3   Syntax Description

calls

Sets the maximum number of media calls (that is, H.248 contexts) allowed on the MGC group at any given time. This value corresponds to the H.248 BaseRoot package property maxNumberOfContexts. The default value is 76,500.

signalling-rtt

Sets the maximum acceptable round-trip propagation delay, in seconds, in the network. This delay is added to the interval configured for the timers request option to construct the H.248 “long timer,” which determines how long transaction responses are cached for retransmission. The retransmission timer is dynamically adjusted based on the measured round-trip time (RTT). The configured maximum signalling RTT value limits the value used in the retransmission timer computation. The range of values is 1 to 1,073,741,823. The default value is 4.

pending-responses

Sets the maximum number of pending responses generated before a request is considered timed out. This value corresponds to the H.248 BaseRoot package property MGOriginatedPendingLimit. The range of values is 1 to 100. The default value is 6.

value

Value to be used for the specified maximum.

1.8.4   Default

All maximum values are set to their default values.

1.8.5   Usage Guidelines

Use the maximum command to set maximum values related to the MGC group function.

Use the no form of this command to restore the default values for MGC group maximums.

1.8.6   Examples

The following example shows how to set the maximum number of calls on the MG to 2000:

[local]Redback(config-grp)#maximum calls 2000

The following example shows how to set the maximum number of calls to the default value:

[local]Redback(config-mg)#no maximum calls

The following example shows how to set the maximum number of pending responses on the MG to 6:

[local]Redback(config-mg)#maximum pending-responses 6

The following example shows how to disable the sending of pending responses:

[local]Redback(config-mg)#no maximum pending-responses

1.9   maximum (realm)

maximum {l4-payload-size bytes | rate {inkbps | outkbps}

no maximum {l4-payload-size bytes | rate {inkbps | outkbps}

1.9.1   Purpose

For the specified realm, configures the maximum values for media packet size and rate attributes.

1.9.2   Command Mode

realm configuration (context specific)

1.9.3   Syntax Description

l4-payload-size bytes

Optional. Specifies the maximum media packet size in bytes for this realm. The range of values is 0 to 65535; the default value is 65,535. Any media packets exceeding the configured size are dropped and included in dropped-packet statistics.

rate

Specifies the maximum rate value for this realm.

in kbps

Specifies the maximum egress rate, in kbps, for this realm. The range of values is 1 to 4,294,967,295; the default value is 4,294,967,295.

out kbps

Specifies the maximum ingress rate, in kbps, for this realm. The range of values is 1 to 4,294,967,295; the default value is 4,294,967,295.

1.9.4   Default

The default values for media packet size and rate attributes are specified in the Syntax Description section.

1.9.5   Usage Guidelines

Use the maximum command to configure the maximum values for media packet size and rate attributes.

Use the maximum command with the l4-payload-size keyword to configure the maximum value for media packets. If the l4-payload-size keyword is not configured, the MG forwards legitimate media packets of any size by default.

Use the maximum rate in command to configure the maximum ingress rate for this realm. The default is 232 kbps.

Use the maximum rate out command to configure the maximum egress rate for this realm. The default is 232 kbps.

Note:  
Specifying a low maximum egress or ingress rate value may result in a failure of calls.

1.9.6   Examples

The following example shows how to configure a maximum value of 65535 bytes for media packets for the realm:

[local]Redback(config-realm)#maximum l4-payload-size 65535

The following example shows how to configure a maximum traffic rate of 100000 kbps for the realm:

[local]Redback(config-realm)#maximum rate in 100000

1.10   media-gateway

media-gateway

no media-gateway

1.10.1   Purpose

In global configuration mode, enters the media gateway (MG) configuration mode for the configuration of border gateway function (BGF) services on the router.

In context configuration mode, enters the MG configuration mode for the configuration of BGF services available in the context.

1.10.2   Command Mode

1.10.3   Syntax Description

This command has no keywords or arguments.

1.10.4   Default

None.

1.10.5   Usage Guidelines

Use the media-gateway command (in global configuration mode) to enter the MG configuration mode to configure BGF services on the router. The SmartEdge OS currently supports only one configured BGF. When a BGF is configured, three MG instances are created along with a MG manager.

Use the no form of this command to remove the BGF from the router. When the BGF is removed by using the no form of the configuration command, the MG level is forcibly shut down and the BGF configuration is deleted.

Use the media-gateway command (in context configuration mode) to enter the MG configuration mode to configure BGF services in the context.

Use the no form of this command to remove the BGF from the context.

1.10.6   Examples

The following example shows how to enter the MG configuration mode to configure MG services on the router:

[local]Redback(config)#media-gateway
[local]Redback(config-mg)#

The following example shows how to remove the MG from the router:

[local]Redback(config)#no media-gateway
[local]Redback(config)#

The following example shows how to enter MG context configuration mode to configure MG services for the context:

[local]Redback(config-ctx)#media-gateway
[local]Redback(config-ctx-mg)#

The following example shows how to remove the MG from the context you are in:

[local]Redback(config-ctx)#no media-gateway
[local]Redback(config-ctx)#

1.11   media-gateway-controller

media-gateway-controller index

no media-gateway-controller index

1.11.1   Purpose

Adds a media gateway controller (MGC) to the numbered list of MGCs that can control the virtual media gateway (VMG) on the router, or enters configuration mode for the specified MGC.

1.11.2   Command Mode

MGC group configuration

1.11.3   Syntax Description

index

Position of this MGC in the list of MGCs that can control the VMG. The range of values is from 1 to 4,294,967,295.

1.11.4   Default

None

1.11.5   Usage Guidelines

Use the media-gateway-controller command to add an entry to the list of external MGCs able to control the VMG on the router, or to enter configuration mode for an MGC to define its characteristics. This command allows you to define the association between the VMG corresponding to the MGC group and the MGC.

MGCs are referenced by number. The index value is used to position each MGC within the list. When the VMG starts up, it attempts to establish an association with each MGC in the list one by one, in the order specified by the index values. If it fails to establish an association with all listed MGCs, it begins again at the start of the list, continuing this process indefinitely.

Use the no form of this command to remove the specified MGC from the list.

1.11.6   Examples

The following example shows how to configure an MGC as the fourth MGC in the MGC list and enter configuration mode for the MGC:

[local]Redback(config-grp)#media-gateway-controller 4

[local]Redback(config-mgc)#

The following example shows how to remove the MGC in position 4 from the list:

[local]Redback(config-grp)#no media-gateway-controller 4
[local]Redback(config-grp)#

1.12   media-local-address

media-local-address interface if-name

no media-local-address interface if-name

1.12.1   Purpose

Specifies the interface to use for media traffic in the realm you are configuring.

1.12.2   Command Mode

realm configuration mode (context-specific)

1.12.3   Syntax Description

interface if-name

Specifies the interface to use for media traffic. This must be a loopback interface that has already been defined within the context.

1.12.4   Default

None

1.12.5   Usage Guidelines

Use the media-local-address command to specify the interface to use for media traffic in the realm you are configuring. The interface must be a media loopback interface already defined for this context. You can specify one or more media loopback interfaces for a realm.

Use the no form of this command to remove the specified interface configuration for media traffic.

1.12.6   Examples

The following example shows how to configure the media local address using the address of a loopback interface named loopback-mg:

[local]Redback(config-realm)#media-local-address interface loopback-mg

[local]Redback(config-realm-media)#

1.13   mgc-group

mgc-group mgc-group-name

no mgc-group mgc-group-name

1.13.1   Purpose

In global media gateway (MG) configuration mode, specifies a media gateway controller (MGC) group name to configure and enters MGC group configuration mode.

In realm configuration mode, specifies an MGC group that can use this realm for calls.

1.13.2   Command Mode

1.13.3   Syntax Description

mgc-group-name

MGC group name. Specify the MGC group name to configure. The valid value is an alphanumeric string of up to 30 characters.

1.13.4   Default

In MG (global) configuration mode, there is no default behavior.

In realm configuration mode, calls from all MGC groups are allowed by default. If an MGC group is specified in a realm configuration, only that MGC group can use that realm.

1.13.5   Usage Guidelines

Use the mgc-group command (in global MG configuration mode) to specify an MGC group name to configure and enter MGC group configuration mode. The maximum number of MGC groups you can configure is 64. Use the no form of this command to remove a specified MGC group from the MG.

When a MGC group is configured, three virtual media gateways (VMGs) are created. The parameters applied to the MGC group are also applied to each VMG, with the exception of the local port on which the VMG opens the link; the local port for the VMG or MGC is not defined. Any change applied to the MGC group parameters are also applied to each of the VMGs.

Use the mgc-group command (in realm configuration mode) to specify an MGC group that can use this realm for calls. This MGC group advertises to the MGC, indicating that it can use this realm. This group must already be defined in global MG configuration mode. If no MGC group is specified, this realm is used by all MGC groups. Use the no form of this command to remove a specified MGC group from using a realm for its calls.

1.13.6   Examples

The following example shows how to specify the MGC group named group1 to configure and enter MGC group configuration mode:

[local]Redback(config-mg)#mgc-group group1 
[local]Redback(config-grp)#

The following example shows how to specify the MGC group named group1 that can use realm realm1.

[local]Redback(config-ctx-mg)#realm realm1
[local]Redback(config-realm)#mgc-group group1

1.14   process mgd

process {restart | stop | start} mgd [instance instance-id]

1.14.1   Purpose

Starts, stops, or restarts the media gateway (MG) daemon process.

1.14.2   Command Mode

all modes

1.14.3   Syntax Description

restart

Restart the process.

stop

Stop the process.

start

Start the process.

1.14.4   Default

None

1.14.5   Usage Guidelines

Use the process mgd command to restart, stop, or start the MG daemon process.

1.14.6   Examples

The following example shows how to restart the MG daemon process using the process command:

[local]Redback#process restart mgd

1.15   process mgmd

process {restart | stop | start} mgmd

1.15.1   Purpose

Starts, stops, or restarts the media gateway manager (MGM) daemon process.

1.15.2   Command Mode

all modes

1.15.3   Syntax Description

restart

Restart the process.

stop

Stop the process.

start

Start the process.

1.15.4   Default

None

1.15.5   Usage Guidelines

Use the process mgmd command to restart, stop, or start the MGM daemon process.

1.15.6   Examples

The following example shows how to restart the MGM daemon process using the process command:

[local]Redback#process restart mgmd

1.16   profile

profile {etsi-bgf | ericsson-bgf} [version version-num]

no profile [etsi-bgf | ericsson-bgf] [version]

1.16.1   Purpose

Specifies the H.248 protocol profile to use for the association between the virtual media gateway (VMG) and the media gateway controller (MGC).

1.16.2   Command Mode

MGC group configuration (global)

1.16.3   Syntax Description

etsi-bgf

Uses the European Telecommunications Standards Institute (ETSI) H.248 protocol profile for the border gateway function (BGF).

ericsson-bgf

Sets the Ericsson H.248 protocol profile for the BGF.

version version-num

Optional. Sets the version number of the protocol profile. The only supported value for the ETSI profile is version 1, the default value. The only supported value for the Ericsson profile is version 2, the default value.

1.16.4   Default

The default profile is Ericsson version 2.

1.16.5   Usage Guidelines

Use the profile command to specify the H.248 protocol profile to use in the association between the VMG and MGC.

Specifying the ETSI profile causes the BGF to send the string ETSI_BGFin service change messages on the ROOT termination. Specifying the Ericsson profile causes the BGF to send the string ETSI_BGFin service change messages on the ROOT termination. The profile version number is concatenated to the profile string with a slash (“/”) as the separator character.

Use the no form of this command to restore the default protocol profile and version.

1.16.6   Examples

The following example shows how to change the protocol profile in the MGC group groupt3 from the default profile to ETSI version 1, which is the default version for the ETSI profile:

[local]Redback(config-mg)#mgc-group groupt3
[local]Redback(config-grp)#profile etsi_bgf
[local]Redback(config-grp)#

1.17   qos mark out dcsp

qos mark out dcsp {dscp-class [override]|ignore}

no qos mark out dcsp {dscp-class [override]|ignore}

1.17.1   Purpose

Assigns a quality of service (QoS) Differentiated Services Code Point (DSCP) priority value to all outgoing media packets that a virtual media gateway (VMG) can use for the realm.

1.17.2   Command Mode

realm configuration

1.17.3   Syntax Description

dscp-class

Optional. DSCP priority value with which packets are marked. Values can be:


  • Integer from 0 to 63.

  • One of the keywords in Table 1.


Only one marking instruction can be in effect at any time.

override

Optional. Overrides any DSCP value the media gateway controller (MGC) specifies for all outgoing traffic for a realm and instead uses the specified DSCP value.

ignore

Optional. Ignores any DSCP value the MGC specifies for all outgoing traffic for a realm so that the DSCP value is not changed.

1.17.4   Default

Packets are assigned a DSCP priority value for a realm, based on the command that the MGC sends to the VMG.

1.17.5   Usage Guidelines

Use the qos mark out dcsp command to assign a QoS DSCP priority value to all outgoing media packets that a VMG can use for the realm.

Use the no form of this command to return to the default behavior.

Table 1 lists the keywords for the dscp-class argument.

Table 1    DSCP Class Keywords

DSCP Class

Keyword

DSCP Class

Keyword

Assured Forwarding (AF) Class 1/ Drop precedence 1

af11

Class Selector 0 (same as default forwarding)

cs0 (same as df)

AF Class 1/Drop precedence 2

af12

Class Selector 1

cs1

AF Class 1/Drop precedence 3

af13

Class Selector 2

cs2

AF Class 2/Drop precedence 1

af21

Class Selector 3

cs3

AF Class 2/Drop precedence 2

af22

Class Selector 4

cs4

AF Class 3/Drop precedence 3

af23

Class Selector 5

cs5

AF Class 3/Drop precedence 1

af31

Class Selector 6

cs6

AF Class 3/Drop precedence 2

af32

Class Selector 7

cs7

AF Class 3/Drop precedence 3

af33

Default Forwarding (same as Class Selector 0)

df (same as cs0)

AF Class 4/Drop precedence 1

af41

Expedited Forwarding

ef

AF Class 4/Drop precedence 2

af42

 

 

AF Class 4/Drop precedence 3

af43

 

 

1.17.6   Example

The following example shows how to assign the QoS DSCP priority value of ef for expedited forwarding of all outgoing media packets for the realm.

[local]Redback(config-mg)#qos mark out dcsp ef

1.18   realm

realm realm-name

no realm realm-name

1.18.1   Purpose

Specifies the name of a realm to configure for the border gateway function (BGF) and enters realm configuration mode.

1.18.2   Command Mode

MG context

1.18.3   Syntax Description

realm-name

Name of realm. The valid value is an alphanumeric string of up to 63 characters.

1.18.4   Default

None.

1.18.5   Usage Guidelines

Use the realm command to specify the name of a realm to configure for the BGF and enter realm configuration mode. This realm is added in the context you are configuring.

Realms map to either an access network or a core network. The realm name must be unique across all contexts.

Use the no form of this command to remove the specified realm from the BGF, resulting in the deletion of all configured IP addresses.

Note:  
Using the no form of the realm command deletes all H.248 contexts in the specified realm.

1.18.6   Examples

The following example shows how to enter the context sanjosenorth and MG configuration mode to configure a realm named access1:

[local]Redback(config)#context sanjosenorth
[local]Redback(config-ctx)#media gateway
[local]Redback(config-ctx-mg)#realm access1
[local]Redback(config-realm)#

1.19   reserve calls

reserve calls emergency percentage-value

no reserve calls emergency percentage-value

1.19.1   Purpose

Configure reserved call values for the border gateway function (BGF).

1.19.2   Command Mode

MG group configuration (global)

1.19.3   Syntax Description

emergency percentage-value

Specify the percentage of total calls reserved for emergency. The range of values is 0 to 100. The default value is 20.

1.19.4   Default

None.

1.19.5   Usage Guidelines

Use the reserve calls command to configure reserved call values for the BGF. Use the no form of this command to remove the specified reserved call values.

1.19.6   Examples

The following example shows how to reserve 5% of the total calls BGF handles for emergency calls:

[local]Redback(config-mg)#reserved calls emergency 5

1.20   segmentation

segmentation {size size |hold-time hold-time}

no segmentation [size | hold-time]

1.20.1   Purpose

Sets the properties for segmentation when the H.248 segmentation package is used.

1.20.2   Command Mode

MGC group configuration (global)

1.20.3   Syntax Description

size size

Sets the maximum size, in bytes, of the protocol data unit (PDU) that can be sent to the media gateway controller (MGC) from the media gateway (MG) when the segmentation package is used. The range of values is from 1 to 65,535.

hold-time hold-time

Sets the time, in milliseconds, within which the MGC can receive any outstanding message segments from the MG when the segmentation package is used. The range of values is from 1 to 30,000.

1.20.4   Default

By default, use of the segmentation package is disabled.

1.20.5   Usage Guidelines

Use the segmentation command to set the properties for segmentation when the H.248 Segmentation Package (defined in the ITU-T H.248.1 specification, Gateway Control Protocol, version 3, Annex E) is used.

Use the no form of this command to disable use of the segmentation package. When use of the segmentation package is disabled, any MGC request that includes segmentation package properties is rejected.

1.20.6   Examples

The following example shows how to set the maximum PDU size to 2500:

[local]Redback(config-group)#segmentation size 2500

The following example shows how to set the MGC hold time to 360:

[local]Redback(config-group)#segmentation hold-time 360

1.21   show media-gateway [instance]

show media-gateway [instance instance-id] [circuit | mgc-group | statistics]

1.21.1   Purpose

Displays high-level information for one or all media gateway (MG) instances, depending on configuration.

1.21.2   Command Mode

all modes

1.21.3   Syntax Description

instance

Displays MG instance information. Specify the instance ID of the MG to display. The range of values is 1 to 3. If an MG instance is not specified, information for all instances is displayed.

circuit

Displays MG information on circuits. For more information, see show media-gateway [instance] circuit.

mgc-group

Displays media gateway controller (MGC) group information. For more information, see show media-gateway [instance] mgc-group.

statistics

Displays MG statistics. For more information, see show media-gateway [instance] statistics.

1.21.4   Default

None

1.21.5   Usage Guidelines

Use the show media-gateway command to display high-level information for one or all three media gateway (MG) instances, depending on configuration. Without the circuit, mgc-group, or statistics keywords specified, the output of the show media-gateway command displays the operation state of all MG instances or a specified instance.

1.21.6   Examples

The following example shows how to display output from the show media-gateway command for all MG instances:

[local]Redback#show media-gateway
Instance ID                     Oper State
------------------------------------------
1                               Up

Instance ID                     Oper State
------------------------------------------
2                               Up

Instance ID                     Oper State
------------------------------------------
3                               Up

The following example shows how to display output from the show media-gateway instance 2 command for MG instance 2:

[local]Redback#show media-gateway instance 2
Instance ID                     Oper State
------------------------------------------
2                               Up

1.22   show media-gateway [instance] circuit

show media-gateway [instance instance-id ] circuit {user-name user-name | agent-circuit-id agent-circuit-id | agent-remote-id agent-remote-id | slot/port:chan-num:sub-chan-num | all}

1.22.1   Purpose

Displays summary information for circuits enabled with media gateway (MG) functionality for all MG instances or a specified MG instance.

1.22.2   Command Mode

all modes

1.22.3   Syntax Description

instance instance-id

Instance ID. Specify the instance ID of the border gateway function (BGF) to display. The range of values is 1 to 3.

agent-circuit-id agent-circuit-id

Optional. Displays information for the specified agent circuit ID.

agent-remote-id agent-remote-id

Optional. Displays information for circuits associated with the specified remote agent.

all

Displays information for all VoIP-enabled circuits on the system.

slot/port:chan-num: sub-chan-num

Optional. Displays circuit information for a specific slot on the chassis:


slot is the slot number of a traffic card.


port is the port number of the slot.


chan-num is the channel number. The range of values depends on the type of port.


sub-chan-num is the subchannel number. If a subchannel is not specified, circuit information for all subchannels is displayed for the specified channel. The range depends on the type of port.

user-name user-name

Optional. Displays information for circuits associated with the specified subscriber.

1.22.4   Default

None

1.22.5   Usage Guidelines

Use the show media-gateway instance circuit command to display information for circuits enabled with media gateway (MG) functionality for all MG instances or a specified MG instance.

For subscriber circuits, the show media-gateway circuit command displays a summary of the voice over IP (VoIP) information for the subscriber, including the Address of Record (AOR) that is active on the circuit, and whether the AOR is registered. If the AOR is registered, the registrar’s adjacency and registered contacts are displayed. For nonsubscriber circuits, the command displays the number of media flows active on the circuit. For each media flow, the context ID, local IP address, and port associated with the flows are listed, and the media flow type—Real-Time Transfer Protocol (RTP) flow or a Real-Time Transfer Control Protocol (RTCP)—is displayed. For trunk circuits, the number of media flows can be very large.

1.22.6   Examples

The following example shows how to display summary information for a specified slot, port, channel, and subchannel of a circuit enabled with media gateway (MG) functionality in the MG instance 2

[local]Redback#show media-gateway instance 2 circuit 4/2:1023:63

--------------------------------------------
Instance Id : 2
--------------------------------------------
Circuit:           4/2 pppoe 69
Internal Circuit:  4/2:1023:63/6/2/69
Context Id:        0
Port Table Entries:4

1.23   show media-gateway instance media-flow

show media-gateway instance instance-id media-flows [context ctx-name [ip-address ip-addr [port port]]] [detail]

1.23.1   Purpose

Displays summary information for all media flows associated with the specified media gateway (MG) instance.

1.23.2   Command Mode

all modes

1.23.3   Syntax Description

instance-id

Instance ID. Specify the instance ID of the border gateway function (BGF) to display. The range of values is 1 to 3.

context ctx-name

Optional. Displays information for media flows in the specified context.

ip-address ip-addr

Optional. Displays information for media flows for the specified IP address.

port port

Optional. Displays information for media flows on the specified port. The range is 16K to 48K.

detail

Optional. Displays detailed information for media flows for the specified BGF instance, context or IP address, depending on which keyword you enter.

1.23.4   Default

Displays summary information for all media flows associated with the instance ID.

1.23.5   Usage Guidelines

Use the show media-gateway instance media-flows command to display media flow information for a specified MG instance.

1.23.6   Examples

The following example shows how to display all media flows on the MG instance 1 at a detailed level:

[local]Redback(config-group)#show media-gateway instance 1 media-flows detail
Context Id:         0x40080003
IpAddress:          12.0.0.2        Port:           17284
State:              Unbound         Type:           RTP
Circuit:            Unknown circuit
Remote User IP:     12.0.0.2        Port:           17292
Active PPA Slots:   None
Configured Services:
        Send-Recv
        DSCP Remarking      : 0xe
Inactivity Duration: 0              Direction:      None
Slot:               06              Status:         Active
BW params
Realm Index:   0    IN:       128  OUT:      128
Policing:      Disabled  SDR:      0    MBS:      0
----------------------------------------------------------------
Context Id:         0x40080003
IpAddress:          12.0.0.2        Port:           17292
State:              Unbound         Type:           RTP
Circuit:            Unknown circuit
Remote User IP:     12.0.0.2        Port:           17284
Active PPA Slots:   None
Configured Services:
        Send-Recv
        DSCP Remarking      : 0xe
Inactivity Duration: 10000          Direction:      Both
Slot:               05              Status:         Active
BW params
Realm Index:   0    IN:       128  OUT:      128
Policing:      Disabled  SDR:      0    MBS:      0
----------------------------------------------------------------

1.24   show media-gateway [instance] mgc-group

show media-gateway [instance instance-id] mgc-group mgc-group-name [{context context-number | termination name}] [detail]

1.24.1   Purpose

Displays information for the virtual media gateway (VMG) corresponding to the media gateway controller (MGC) group for all media gateway (MG) instances or a specified MG instance.

1.24.2   Command Mode

all modes

1.24.3   Syntax Description

instance-id

Optional. Instance ID. Specify the instance ID of the border gateway function (BGF) to display. The range of values is 1 to 3.

mgc-group-name

MGC group name. Specify the MGC group name for which to display information. The valid value is an alphanumeric string of up to 30 characters.

context context-number

Optional. Displays information for all active H.248 contexts or for a specified active H.248 context. To display information for a specific context, enter the H.248 context ID. The valid values are from 1 to 4,294,967,295.

termination name

Optional. Displays information for all active H.248 terminations or for a specified active H.248 termination. To display information for a specific H.248 termination, enter the H.248 termination ID. The valid value is an alphanumeric string of up to 30 characters.

detail

Displays detailed MGC group statistics.

1.24.4   Default

None

1.24.5   Usage Guidelines

Use the show media-gateway instance mgc-group command to display information for the VMG corresponding to the MGC group for all MG instances or a specified MG instance.

1.24.6   Examples

The following example shows how to display the MGC group information for the MGC group named mg1:

[local]Redback#show media-gateway mgc-group mg1
--------------------------------------------
Instance Id : 1
--------------------------------------------
Media gateway                           : mg1/1
==============================================================
Admin state                             : Up
Operational state                       : Up
Maximum number of calls                 : 445
Maximum round trip propagation delay    : 1000
Maximum number of pending response      : 20
Initial association wait time           : 5000 ms
Maximum association wait time           : 60000 ms
Normal execution time                   : 900 ms
Pending response time                   : 1000 ms
Request timeout                         : 15000 ms
Signaling inactivity time               : 0 ms
Overload threshold time                 : 0 ms
Default media idle time                 : 10000 sec
Segmentation size                       : 0
Segmentation hold time                  : 0
Profile name                            : ETSI_BGF
Profile Version                         : 2

MGC Index  Local IP:Port         Remote IP:Port        Transport  Active
------------------------------------------------------------------------
1          10.110.110.1:64079    10.0.6.3:2944         SCTP       Yes



--------------------------------------------
Instance Id : 2
--------------------------------------------
Media gateway                           : mg1/2
==============================================================
Admin state                             : Up
Operational state                       : Up
Maximum number of calls                 : 441
Maximum round trip propagation delay    : 1000
Maximum number of pending response      : 20
Initial association wait time           : 5000 ms
Maximum association wait time           : 60000 ms
Normal execution time                   : 900 ms
Pending response time                   : 1000 ms
Request timeout                         : 15000 ms
Signaling inactivity time               : 0 ms
Overload threshold time                 : 0 ms
Default media idle time                 : 10000 sec
Segmentation size                       : 0
Segmentation hold time                  : 0
Profile name                            : ETSI_BGF
Profile Version                         : 2

MGC Index  Local IP:Port         Remote IP:Port        Transport  Active
------------------------------------------------------------------------
1          10.110.110.1:59396    10.0.6.3:2944         SCTP       Yes



--------------------------------------------
Instance Id : 3
--------------------------------------------
Media gateway                           : mg1/3
==============================================================
Admin state                             : Up
Operational state                       : Up
Maximum number of calls                 : 432
Maximum round trip propagation delay    : 1000
Maximum number of pending response      : 20
Initial association wait time           : 5000 ms
Maximum association wait time           : 60000 ms
Normal execution time                   : 900 ms
Pending response time                   : 1000 ms
Request timeout                         : 15000 ms
Signaling inactivity time               : 0 ms
Overload threshold time                 : 0 ms
Default media idle time                 : 10000 sec
Segmentation size                       : 0
Segmentation hold time                  : 0
Profile name                            : ETSI_BGF
Profile Version                         : 2

MGC Index  Local IP:Port         Remote IP:Port        Transport  Active
------------------------------------------------------------------------
1          10.110.110.1:65519    10.0.6.3:2944         SCTP       Yes

The following example shows how to display the MGC group information for the MGC group named mg1 in MG instance 1:

[local]Redback#show media-gateway instance 1 mgc-group mg1

Instance Id : 1
--------------------------------------------
Media gateway                           : mg1/1
==============================================================
Admin state                             : Up
Operational state                       : Up
Maximum number of calls                 : 445
Maximum round trip propagation delay    : 1000
Maximum number of pending response      : 20
Initial association wait time           : 5000 ms
Maximum association wait time           : 60000 ms
Normal execution time                   : 900 ms
Pending response time                   : 1000 ms
Request timeout                         : 15000 ms
Signaling inactivity time               : 0 ms
Overload threshold time                 : 0 ms
Default media idle time                 : 10000 sec
Segmentation size                       : 0
Segmentation hold time                  : 0
Profile name                            : ETSI_BGF
Profile Version                         : 2

MGC Index  Local IP:Port         Remote IP:Port        Transport  Active
------------------------------------------------------------------------
1          10.110.110.1:64079    10.0.6.3:2944         SCTP       Yes

1.25   show media-gateway [instance] statistics

show media-gateway [instance instance-id] statistics [{call [rate] | mgc-group mgc-group-name [call]}]

1.25.1   Purpose

Displays media gateway (MG) statistics for all MG instances or a specified MG instance.

1.25.2   Command Mode

all modes

1.25.3   Syntax Description

instance-id

Optional. Instance ID. Specify the instance ID of the border gateway function (BGF) to display. The range of values is 1 to 3.

call

Optional. Displays MG call statistics.


When used with the mgc-groupkeyword, displays call statistics for the specified MGC group.

rate

Optional. Displays MG call rate statistics.

mgc-group mgc-group-name

Optional. MGC group name. Specify the MGC group name for which to display statistics. The valid value is an alphanumeric string of up to 30 characters.

1.25.4   Default

None

1.25.5   Usage Guidelines

Use the show media-gateway instance statistics command to display MG statistics for a specified MG instance.

1.25.6   Examples

The following example shows how to display MGC group call statistics for the MGC group mg1 in MG instance 1.

[local]Redback#show media-gateway instance 1 statistics mgc-group mg1 call
--------------------------------------------
Instance Id : 1
--------------------------------------------
Current Calls:        69
Peak Calls:           5794

Call Type             Current     Peak
==============================================
Normal Calls:         69          5794
Emergency Calls:      0           0


Rejections Due To
====================
Emergency Threshold:  0
Licensing Limit:      0
Stream Limit:         0
Bandwidth Limit:      0

1.26   show process mgd

show process mgd [instance instance-id] [crash-info | detail]

1.26.1   Purpose

Displays the process status for the media gateway (MG) daemon for all MG instances or a specified MG instance.

1.26.2   Command Mode

all modes

1.26.3   Syntax Description

instance instance-id

Optional. Instance ID. Specify the instance ID of the border gateway function (BGF) for which to display information. The range of values is 1 to 3.

crash-info

Optional. Displays information about a process crash.

detail

Optional. Displays detailed information about the process.

1.26.4   Default

None

1.26.5   Usage Guidelines

Use the show process mgd command to display the process status for the media gateway (MG) daemon for all MG instances or a specified MG instance. Use this command to determine if the MG process is running or stopped.

1.26.6   Examples

The following example shows how to display the status of the MG daemon process for all MG instances:

[local]Redback#show process mgd
NAME           PID    SPAWN    MEMORY  TIME            %CPU  STATE     UP/DOWN
mgd-1          952        1   116228K  00:17:48.43    0.00%  run          5d01h
mgd-2          890        1   113720K  00:17:54.57    0.05%  run          5d01h
mgd-3          953        1   116080K  00:17:50.66    0.00%  run          5d01h

1.27   show process mgmd

show process mgmd [crash-info | detail]

1.27.1   Purpose

Displays the process status for the media gateway manager (MGM) daemon for the border gateway function (BGF).

1.27.2   Command Mode

all modes

1.27.3   Syntax Description

crash-info

Optional. Displays information about a process crash.

detail

Optional. Displays detailed information about the process.

1.27.4   Default

None

1.27.5   Usage Guidelines

Use the show process mgmd command to display the process status for the MGM daemon for the BGF. Use this command to determine if the MGM process is running or stopped.

1.27.6   Examples

The following example shows how to display the status of the MGM daemon process:

[local]Redback#show process mgmd
NAME           PID    SPAWN    MEMORY  TIME            %CPU  STATE     UP/DOWN
mgmd           913        1     4772K  00:01:50.74    0.00%  run          5d01h

1.28   show process sctp

show process sctp [crash-info | detail]

1.28.1   Purpose

Displays the process status for the Stream Control Transmission Protocol (SCTP).

1.28.2   Command Mode

all modes

1.28.3   Syntax Description

crash-info

Optional. Displays information about a process crash.

detail

Optional. Displays detailed information about the process.

1.28.4   Default

None

1.28.5   Usage Guidelines

Use the show process sctp command to display the SCTP process status. Use this command to determine if the SCTP process is running or stopped.

1.28.6   Examples

The following example shows how to display the status of the SCTP process:

[local]Redback#show process sctp
NAME           PID    SPAWN    MEMORY  TIME            %CPU  STATE     UP/DOWN 
sctp         1237   5        18468K  00:00:13.22     1.32% run      00:17:56

1.29   show sctp

show sctp [brief [all] | statistics]

1.29.1   Purpose

Displays information and statistics about the Stream Control Transmission Protocol (SCTP) and SCTP associations.

1.29.2   Command Mode

all modes

1.29.3   Syntax Description

brief

Optional. Displays active Internet connections.

all

Optional. Displays active Internet connections, including servers. Used with the brief keyword.

statistics

Optional. Displays SCTP statistics.

1.29.4   Default

None

1.29.5   Usage Guidelines

Use the show sctp command to display SCTP information and statistics.

1.29.6   Examples

The following example displays output when the statistics keyword is specified:

[local]Redback#show sctp statistics
sctp:
        5144073 input packets
                5144068 datagrams
                2138719 packets that had data
                837066 input SACK chunks
                2138719 input DATA chunks
                36 duplicate DATA chunks
                2090216 input HB chunks
                77971 HB-ACK chunks
                0 input ECNE chunks
                0 input AUTH chunks
                0 chunks missing AUTH
                0 invalid HMAC ids received
                0 invalid secret ids received
                0 auth failed
                2138665 fast path receives all one chunk
                0 fast path multi-part data
        3868728 output packets
                1309870 output SACKs
                2136422 output DATA chunks
                106 retransmitted DATA chunks
                3 fast retransmitted DATA chunks
                0 FR's that happened more than once to same chunk.
                78030 intput HB chunks
                0 output ECNE chunks
                0 output AUTH chunks
                6 ip_output error counter
        Packet drop statistics:
                0 from middle box
                0 from end host
                0 with data
                0 non-data, non-endhost
                0 non-endhost, bandwidth rep only
                0 not enough for chunk header
                0 not enough data to confirm
                0 where process_chunk_drop said break
                0 failed to find TSN
                0 attempt reverse TSN lookup
                0 e-host confirms zero-rwnd
                0 midbox confirms no space
                0 data did not match TSN
                0 TSN's marked for Fast Retran
        Timeouts:
                3 iterator timers fired
                23 T3 data time outs
                0 window probe (T3) timers fired
                418 INIT timers fired
                2718 sack timers fired
                0 shutdown timers fired
                78696 heartbeat timers fired
                0 a cookie timeout fired
                711 an endpoint changed its cookiesecret
                4337 PMTU timers fired
                0 shutdown ack timers fired
                0 shutdown guard timers fired
                0 stream reset timers fired
                0 early FR timers fired
                0 an asconf timer fired
                0 auto close timer fired
                0 asoc free timers expired
                0 inp free timers expired
        0 packet shorter than header
        0 checksum error
        5 no endpoint for port
        0 bad v-tag
        0 bad SID
        0 no memory
        0 number of multiple FR in a RTT window
        483254 RFC813 allowed sending
        1653168 RFC813 does not allow sending
        45 max burst dosn't allow sending
        0 look ahead tells us no memory in interface
        0 numbers of window probes sent
        0 times an output error to clamp down on next user send.
        0 times sctp_senderrors were caused from a user
        0 number of in data drops due to chunk limit reached
        0 number of in data drops due to rwnd limit reached
        0 times a ECN reduced the cwnd
        5144065 used express lookup via vtag
        0 collision in express lookup.
        0 times the sender ran dry of user data on primary
        0 same for above
        12 sacks the slow way
        0 window update only sacks sent
        0 sends with sinfo_flags !=0
        0 unordered sends
        0 sends with EOF flag set
        0 sends with ABORT flag set
        0 times protocol drain called
        0 times we did a protocol drain
        0 times recv was called with peek
        5392405 cached chunks used
        0 cached stream oq's used
        51 unread messages abandonded by close
        3 send burst avoidance, already max burst inflight to net
        0 send cwnd full avoidance, already max burst inflight to net
        0 number of map array over-runs via fwd-tsn's

The following example displays general information about SCTP and SCTP associations:

[local]Redback#show sctp
Active SCTP associations
Socket    Proto Type  Local Address          Foreign Address        (state)
1008cd000 sctp  1to1   10.110.110.1.65519     10.0.6.3.2944         ESTABLISHED

1008cd274 sctp  1to1   10.110.110.1.64079     10.0.6.3.2944         ESTABLISHED

1008cd4e8 sctp  1to1   10.110.110.1.59396     10.0.6.3.2944         ESTABLISHED

1008cd75c sctp  1to1   10.110.110.2.58234     10.0.6.5.2944         ESTABLISHED

1008cd9d0 sctp  1to1   10.110.110.2.56890     10.0.6.5.2944         ESTABLISHED

1008cdc44 sctp  1to1   10.110.110.2.59679     10.0.6.5.2944         ESTABLISHED

1.30   shutdown

The syntax in media gateway (MG) and media gateway controller (MGC) configuration modes is:

shutdown

no shutdown

The syntax in media gateway controller (MGC) group configuration mode is:

shutdown [graceful | force]

no shutdown

1.30.1   Purpose

Administratively shuts down or brings up the border gateway function (BGF), the specified media gateway controller (MGC) group, or the specified MGC.

1.30.2   Command Mode

1.30.3   Syntax Description

graceful

In MGC group configuration mode, brings down the corresponding virtual media gateways (VMGs) gracefully. A service change request with graceful method is sent out to the MGC. Calls are not deleted and remain until a subtract message is received from MGC.

force

In MGC group configuration mode, specifies to bring down the corresponding VMGs forcefully. A service change request with forced method is sent to the MGC. All calls are deleted immediately.

1.30.4   Default

The default is to shut down forcefully.

1.30.5   Usage Guidelines

Use the shutdown command to administratively take the BGF, an MGC group, or an MGC out of service. The behavior on shutdown depends on where the command is issued:

Note:  
A forced shutdown can follow a graceful shutdown.

Use the no form of this command to administratively enable a BGF, an MGC group, or an MGC.

1.30.6   Examples

The following example shows how to create a BGF 1 and then bring it into service:


[local]Redback(config)#media-gateway
[local]Redback(config-mg)#no shutdown

The following example shows how to disable the MGC with index 57:

[local]Redback(config-group)#media-gateway-controller 57

[local]Redback(config-mgc)#shutdown

1.31   signaling-endpoint

signaling-endpoint {local ip-address [context context-name] | remote ip-address [port} ]

no signaling-endpoint {local | remote}

1.31.1   Purpose

Specifies the IP addresses for the signalling endpoints.

1.31.2   Command Mode

Media gateway controller (MGC) configuration (global)

1.31.3   Syntax Description

local ip-address

Specifies the IP address for the local signalling endpoint—that is, the endpoint on the virtual media gateway (VMG). This is the local IP address that the VMG uses to establish connection with the MGC. This must be the IP address of a loopback address in the local context unless otherwise specified with the context keyword.

context context-name

Specifies the global context in which the local IP address resides. The default is the local context.

remote ip-address

Specifies the IP address for the remote signalling endpoint—the endpoint on the external media gateway controller (MGC).

port

Specifies the port on the remote signalling endpoint to use for H.248 signalling traffic. The range is 0 to 65,535.

1.31.4   Default

There is no default IP address.

1.31.5   Usage Guidelines

Use the signaling-endpoint command to specify the IP addresses and ports for the local signalling endpoint (that is, the border gateway function (BGF)) and the remote signalling endpoint (that is, the MGC). VMGs choose a local port from the port range. The local port may change when the association breaks and is retried.

Use the no form of this command to remove configuration for the specified endpoint.

1.31.6   Examples

The following example sets 40.1.1.1 as the IP address to be used by MGC 5 for sending signals to the local BGF endpoint:

[local]Redback(config-grp)#media-gateway-controller 5

[local]Redback(config-mgc)#signaling-endpoint local 40.1.1.1

The following example sets 53.2.2.2 as the IP address used by the border gateway function (BGF) for sending signals to the remote endpoint on MGC 5. Because the port is not specified, the default port 2944 is assumed:

[local]Redback(config-grp)#media-gateway-controller 5

[local]Redback(config-mgc)#signaling-endpoint remote 53.2.2.2

The following example removes configuration for the remote signalling endpoint IP address for MGC 1:

[local]Redback(config-grp)#media-gateway-controller 1

[local]Redback(config-mgc)#no signaling-endpoint remote

1.32   timers

timers {association-init | association-maximum | media-idle | normal-execution | overload-threshold | pending-response | request | signaling-inactivity} value

no timers {association-init | association-maximum | media-idle | normal-execution | overload-threshold | pending-response | request | signaling-inactivity} }

1.32.1   Purpose

Sets the virtual media gateway (VMG) timers for H.248 signalling activity.

1.32.2   Command Mode

MGC group configuration (global)

1.32.3   Syntax Description

association-init

Specifies the amount of time, in milliseconds, the MG waits for an association to initialize. If this timer is exceeded, the MG times out and generates an error message. The range of values is 1 to 300,000. The default value is 5000.

association-maximum

Specifies the amount of time, in milliseconds, the MG waits for a maximum association. If this timer is exceeded, the MG times out and generates an error message. The range of values is 1 to 300,000. The default value is 60,000.

media-idle

Specifies the amount of time, in milliseconds, the MG waits for media inactivity. If this timer is exceeded, the MG times out and generates an error message. The range of values is 10 to 86,400. The default value is 10.


The media idle timer value is used if the MGC does not specify a value while enabling an ipstop event.

normal-execution

Specifies the amount of time, in milliseconds, the MG waits for normal execution activity. If this timer is exceeded, the MG times out and generates an error message. This timer corresponds to the H.248.1 BaseRoot package property normalMGExecutionTime. The range of values is 1 to 10,000. The default value is 2000.

overload-threshold

Specifies the processing time threshold for MG overload protection. If the H.248 request includes an ADD action, and the time between receiving the request and sending this response exceeds the overload threshold, a notification of an H.248 overload control event is sent for each Add command in the original request, if the media gateway controller (MGC) has subscribed to the overload control event. The range of values is 1 to 300,000. By default, MG overload protection is disabled, and an MGC request for subscription to overload control events is rejected.

pending-response

Specifies the amount of time, in milliseconds, the MG waits for pending responses. If this timer is exceeded, the MG times out and generates an error message. This timer corresponds to the H.248.1 BaseRoot package property MGProvisionalResponseTimerValue. The range of values is 1 to 110000. The default value is 3000.

request

Specifies the amount of time, in milliseconds, the MG waits for requests. If this timer is exceeded, the MG times out and generates an error message. This timer corresponds to the H.248.1 T-MAX timer. It is added to the interval configured for the maximum signaling-rtt option to construct the H.248 “long timer,” which is used to determine how long transaction responses are cached for retransmission. The range of values is 1 to 300,000. The default value is 15,000.

signaling-inactivity

Specifies the amount of time, in milliseconds, the MG waits before timing out due to signalling inactivity. The range of values is 10 to 655,350. By default, signalling inactivity is disabled.

value

Value to use for the specified timer.

1.32.4   Default

All timers are set to their default values.

1.32.5   Usage Guidelines

Use the timers command to set the VMG timers for H.248 signalling activity. No error message is generated when these timers expire.

Note:  
The MG can be configured only when it has been administratively shut down.

Use the no form of this command to restore any MG timer to its default value.

1.32.6   Examples

The following example sets the value for the normal execution timer:

[local]Redback(config-mg)#timers normal-execution 2100

The following example sets the value for the pending response timer:

[local]Redback(config-mg)#timers pending-response 2200

The following example sets the value for the request timer:

[local]Redback(config-mg)#timers request 10000

The following example sets the value for the association initialization timer:

[local]Redback(config-mg)#timers association-init 1100

The following example sets the value for the association maximum timer:

[local]Redback(config-mg)#timers association-maximum 11000

The following example sets the value for the signalling inactivity timer:

[local]Redback(config-mg)#timers signaling-inactivity 10000

1.33   transaction-response-ack

transaction-response-ack {count count | delay delay}

no transaction-response-ack [count | delay]

1.33.1   Purpose

Specifies the behavior of the virtual media gateway (VMG) for sending transaction response acknowledgements to the media gateway controller (MGC).

1.33.2   Command Mode

MGC configuration (global)

1.33.3   Syntax Description

count count

Sets the number of transaction responses the MG should receive before sending a transaction acknowledgement to the MGC. The range of values is 1 to 300.

delay delay

Sets the time, in seconds, that the MG should wait before sending a transaction acknowledgement response to the MGC. The range of values is 1 to 30,000.

1.33.4   Default

The sending of transaction response acknowledgements is disabled.

1.33.5   Usage Guidelines

Use the transaction-response-ack command to specify the behavior of the MG for sending transaction response acknowledgements to the MGC. When transaction response acknowledgements are enabled, the acknowledgements are sent when either the count or the delay is reached.

Use the no form of this command to disable transaction response acknowledgements.

1.33.6   Examples

The following example shows how to configure MGC mg2 so that it waits to receive 5 transaction responses or waits for 45 seconds before sending a transaction response acknowledgement:

[local]Redback(config-mg)#media-gateway-controller mg2

[local]Redback(config-mgc)#transaction-response-ack count 5

[local]Redback(config-mgc)#transaction-response-ack delay 45

1.34   transport

transport {udp | tcp | sctp}

transport

1.34.1   Purpose

Sets the transport protocol used to carry H.248 signalling messages between the virtual media gateway (VMG) and the media gateway controller (MGC).

1.34.2   Command Mode

MGC configuration (global)

1.34.3   Syntax Description

udp

Sets User Datagram Protocol (UDP) as the transport protocol.

tcp

Sets Transmission Control Protocol (TCP) as the transport protocol.

sctp

Sets Stream Control Transmission Protocol (SCTP) as the transport protocol.

1.34.4   Default

The transport protocol is SCTP.

1.34.5   Usage Guidelines

Use the transport command to set the transport protocol used to carry H.248 signalling messages between the VMG and the MGC.

Note:  
SCTP protocol is supported only on XCRP4 Controller cards.

Use the no form of this command to restore the default transport protocol.

1.34.6   Examples

The following example shows how to set TCP as the transport protocol for messages between the MG and MGC 2:

[local]Redback(config-mg)#media-gateway-controller 2

[local]Redback(config-mgc)#transport tcp