Cisco Unified Border Element (SP Edition) Command Reference: Distributed Model

Cisco Unified Border Element (SP Edition) Command Reference: Distributed Model

The commands listed in this command reference are Cisco Unified Border Element (SP Edition) distributed model commands.

Cisco Unified Border Element (SP Edition) was formerly known as Cisco Integrated Session Border Controller and may be commonly referred to in this document as the session border controller (SBC). The name of this command reference was changed in August, 2009.

activate

To initiate the data border element (DBE) service of the session border controller (SBC), use the activate command in SBC-DBE configuration mode. To deactivate the DBE service, use the no form of this command.

activate

no activate

Syntax Description

This command has no arguments or keywords.

Command Default

The default state is that the DBE is not activated.

Command Modes

SBC-DBE configuration (config-sbc-dbe)

Command History

Usage Guidelines

After all DBE address configuration is completed, the activate command initiates the DBE service of the SBC. The command ensures that the DBE is not started in an inconsistent state.

Use the sbc dbe command to enter into SBC-DBE configuration mode first.

Examples

The following example creates a DBE service on an SBC called "mySbc," enters into SBC-DBE configuration mode, and activates the DBE service with the activate command:

Router(config)# sbc mySbc dbe 

Router(config-sbc-dbe)# activate

Related Commands

attach-controllers

To configure a data border element (DBE) to attach to an H.248 controller, use the attach-controllers command in VDBE configuration mode. To detach the DBE from its controller, use the no form of this command.

attach-controllers

no attach-controllers

Syntax Description

This command has no arguments or keywords.

Command Default

The default is that no controllers are attached.

Command Modes

VDBE configuration (config-sbc-dbe-vdbe)

Command History

Usage Guidelines

The attachment and detachment of the DBE from its controller does not always complete immediately. To view the current attachment status, use the show sbc dbe controllers command.

Examples

In a configuration where the DBE has been created and controllers have been configured, the following example shows how to attach the DBE to a controller in VDBE configuration mode:

Router(config)# sbc mySbc dbe 

Router(config-sbc-dbe)# vdbe 

Router(config-sbc-dbe-vdbe)# attach-controllers

Router(config-sbc-dbe-vdbe)# end

Related Commands

bandwidth-fields mandatory

To set the bandwidth description of Session Description Protocol (SDP) as mandatory, use the bandwidth-fields mandatory command in Virtual Data Border Element (VDBE) configuration mode. To set the bandwidth description as optional, use the no form of this command.

bandwidth-fields mandatory

no bandwidth-fields

Syntax Description

This command has no arguments or keywords.

Command Default

The default behaviour is that the bandwidth description of SDP is optional.

Command Modes

VDBE configuration (config-sbc-dbe-vdbe)

Command History

Usage Guidelines

To use this command, you must be in a user group that is associated with a task group that includes the proper task IDs. To use this command, you must be in the correct configuration mode. The Examples section that follows shows the hierarchy of the modes required to run the command.

Examples

The following example shows how to set the bandwidth description of the SDP as mandatory in the VDBE configuration mode:

Router# configure terminal 

Router# sbc sbc dbe

Router(config-sbc-dbe)# vdbe global

Router(config-sbc-dbe-vdbe)# bandwidth-fields mandatory

Related Commands

bandwidth-police tman

To configure the data border element (DBE) to perform no bandwidth policing unless either Traffic Management (Tman) properties, tman/pdr and tman/sdr, or all, are specified in the media and signaling flows, use the bandwidth-police tman command in Virtual Data Border Element (VDBE) configuration mode. To reset to the default behavior, use the no form of this command.

bandwidth-police tman

no bandwidth-police tman

Syntax Description

This command has no arguments or keywords.

Command Default

The default behavior is to perform bandwidth policing based on information from the b-line of the session description protocol (SDP).

Command Modes

VDBE configuration (config-sbc-dbe-vdbe)

Command History

Usage Guidelines

In Cisco IOS XE Release 2.6, this command implements the Optional Tman Bandwidth Parameter Policing feature. The command configures the DBE to perform no traffic policing unless either Traffic Management (Tman) properties, tman/pdr and tman/sdr, or all, are specified in the media and signaling flows. In effect, this command disables bandwidth traffic policing if either tman/pdr or tman/sdr is missing, and disregards the b-line information. When the DBE performs no traffic policing, it means the DBE does not drop packets if bandwidth is exceeded.

The Optional Tman Bandwidth Parameter Policing feature improves H.248 interworking capability with the Traffic Management (Tman) package. This feature is used to disable bandwidth policing from using b-line information when Tman parameters are missing. This complies with the Tman package definition of the ETSI Ia profile (ETSI ES 283 018 V2.4.1 (2008-09), 5.17.1.5.5), which states that traffic policing shall not be done based on the b-line.

If the bandwidth-police tman command is configured and tman/pdr or tman/sdr is received from the media gateway controller (MGC), the DBE performs bandwidth policing using tman/pdr or tman/sdr.

The no bandwidth-police tman form of the command sets the default behavior, which is to perform bandwidth policing based on information from the bandwidth, b- line, of the SDP when Tman parameters are missing. This default behavior was the behavior prior to Cisco IOS XE Release 2.6 where, if both tman/pdr and tman/sdr are missing, the DBE would do bandwidth policing based on information from the b-line.

The command is implemented in the following manner:

When the feature is turned on with the bandwidth-police tman command configured on the DBE:

•If the DBE receives no Tman parameters, the DBE does not perform traffic policing.

•If tman/pol=ON and the DBE receives tman/pdr or tman/sdr parameters, the DBE performs bandwidth traffic policing based on Tman parameters.

•If tman/pol=ON and the DBE receives no tman/pdr or tman/sdr parameters, the DBE does not perform traffic policing.

•If tman/pol=OFF and the DBE receives no tman/pdr or tman/sdr parameters, the DBE does not perform traffic policing.

When the feature is turned off with the no bandwidth-police tman command configured on the DBE:

•If the DBE receives no Tman parameters, the DBE performs traffic policing based on the b-line information in the SDP.

•If the DBE receives Tman parameters, the DBE performs traffic policing based on Tman parameters.

•If tman/pol=OFF and the DBE receives no tman/pdr or tman/sdr parameters, the DBE does not perform traffic policing.

•If tman/pol=OFF and the DBE receives tman/pdr or tman/sdr parameters, the DBE does not perform traffic policing.

Note When the feature is turned off with the no bandwidth-police tman command, the DBE behavior is generally the same behavior as prior to Cisco IOS XE Release 2.6.

Examples

In the following example, the DBE is configured to perform no traffic policing unless tman/pdr and/or tman/sdr properties in the Traffic Management (Tman) package are specified; if tman/pdr and tman/sdr are in the flow, policing is performed using tman/pdr or tman/sdr.

Router# configure terminal 

Router(config)# sbc global dbe 

Router(config-sbc-dbe)# vdbe global 

Router(config-sbc-dbe-vdbe)# bandwidth-police tman

The following example sets the default behavior to configure the DBE to perform bandwidth policing based on information from the b-line of the SDP; this assumes the DBE received no Tman parameters:

Router# configure terminal 

Router(config)# sbc global dbe 

Router(config-sbc-dbe)# vdbe global 

(config-sbc-dbe-vdbe)# no bandwidth-police tman

Related Commands

clear sbc dbe media-stats

To clear all the statistics collected by the media gateway manager of the data border element (DBE), use the clear sbc dbe media-stats command in privileged EXEC mode.

clear sbc {sbc-name} dbe media-stats

Syntax Description

Command Default

No default behavior or values are available.

Command Modes

Privileged EXEC (#)

Command History

Usage Guidelines

This command clears the statistics displayed by the show sbc dbe media-stats command and the show sbc dbe forwarder-stats command. It does not clear the statistics displayed by the show sbc dbe media-flow-stats command.

Examples

The following example clears all the statistics collected by the media gateway manager of a DBE on an SBC called "mySbc":

Router# clear sbc mySbc dbe media-stats

Related Commands

congestion-cleared

To configure that the congestion has cleared when the level of system resources reaches the congestion cleared threshold, use the congestion-cleared command in VDBE configuration mode. To disable this configuration, use the no form of this command.

congestion-cleared {percentage}

no congestion-cleared {percentage}

Syntax Description

Command Default

The system default percentage is 60% if you do not configure the congestion-cleared command or if you configure no congestion-cleared.

Command Modes

VDBE configuration (config-sbc-dbe-vdbe)

Command History

Usage Guidelines

When the DBE has previously signaled a congestion event to the SBE, the DBE will signal that the congestion has cleared when the level of system resources used reaches the congestion cleared threshold. This threshold is configured using the congestion-cleared command.

Examples

The following example creates a DBE service on an SBC called "mySbc," enters into SBC-DBE configuration and VDBE configuration modes, and configures the DBE to signal to the SBE that congestion has cleared at 90% percent of system resources consumed:

Router(config)# sbc mySbc dbe 

Router(config-sbc-dbe)# vdbe 

Router(config-sbc-dbe-vdbe)# congestion-cleared 90

Router(config-sbc-dbe-vdbe)# end

Related Commands

congestion-threshold

To configure the data border element (DBE) to signal a congestion event to the signaling border element (SBE) when a maximum percentage has been reached, use the congestion-threshold command in VDBE configuration mode. To disable this configuration, use the no form of this command.

congestion-threshold [percentage]

no congestion-threshold [percentage]

Syntax Description

Command Default

The system default percentage is 80% if you do not configure the congestion-threshold command, or if you issue the default congestion-threshold command, or if you configure no congestion-threshold.

Command Modes

VDBE configuration (config-sbc-dbe-vdbe)

Command History

Usage Guidelines

When the DBE reaches the maximum configured congestion-threshold percentage for either number of calls or media bandwidth, it sends a congestion message to the SBE.

Examples

The following example creates a DBE service on an SBC called "mySbc," enters into SBC-DBE configuration and VDBE configuration modes, and shows how to configure the DBE to signal a congestion event to the SBE when 95% percent of capacity is reached.

Router(config)# sbc mySbc dbe 

Router(config-sbc-dbe)# vdbe 

Router(config-sbc-dbe-vdbe)# congestion-threshold 95

Router(config-sbc-dbe-vdbe)# end

Related Commands

control-address h248 ipv4

To configure a data border element (DBE) to use a specific IPv4 H.248 control address, use the control-address h248 ipv4 command in VDBE configuration mode. To deconfigure a DBE from using an IPv4 H.248 control address, use the no form of this command.

control-address h248 ipv4 {A.B.C.D}

no control-address h248 ipv4

Syntax Description

Command Default

No default behavior or values are available.

Command Modes

VDBE configuration (config-sbc-dbe-vdbe)

Command History

Usage Guidelines

If the remote address on any controller is configured, the H.248 control address cannot be changed or deleted, unless you first remove the remote address. To remove the remote address, use the no remote-address ipv4 command.

Examples

The following example tries to change the control address to IP address 210.229.108.253, while H.248 controllers are configured, and receives the message that the control address cannot be changed while the controllers are configured:

Router(config-sbc-dbe-vdbe)# control-address h248 ipv4 210.229.108.253

SBC: control-address cannot be changed while controllers are configured.

The following example creates a DBE service on an SBC called "mySbc," enters into SBC-DBE configuration and VDBE configuration modes, and configures the DBE to use 10.0.0.1 as its H.248 control address:

Router(config)# sbc mySbc dbe 

Router(config-sbc-dbe)# vdbe

Router(config-sbc-dbe-vdbe)# control-address h248 ipv4 10.0.0.1

Router(config-sbc-dbe-vdbe)# end

Related Commands

control-dscp marker-dscp pdr-coefficient

To enable the Two-Rate Three-Color Policing and Marking feature on the data border element (DBE) for each affected traffic flow and to color traffic with a configured differentiated services code point (DSCP) value and configured peak data rate (pdr) coefficient, use the control-dscp marker-dscp pdr-coefficient command in VDBE configuration mode. To disable the feature for all traffic flows, use the no form of this command.

control-dscp value1 marker-dscp value2 pdr-coefficient value3

no control-dscp value1 marker-dscp value2 pdr-coefficient value3

Syntax Description

Command Default

None

Command Modes

VDBE configuration mode (config-sbc-dbe-vdbe)

Command History

Usage Guidelines

The control-dscp command is used to enable the Two-Rate Three-Color Policing and Marking feature on the DBE. The marker-dscp pdr-coefficient command is used to color traffic that does not conform to the lower sustainable data rate (sdr), but conforms to the higher peak data rate (pdr). This refinement of traffic is done with a DSCP marker (value2) and pdr value configured by the CLI (not transmitted from the H.248 diffserv package).

The pdr coefficient value is calculated by the CLI (it is not passed from the H.248 diffserv package) and is used for coloring traffic that conforms to this calculated pdr. The calculated pdr uses the formula:
pdr = sdr * value3 /100. value3 has a range of values (101 to 65535) and is not a DSCP value. The pdr value must be greater than the sdr value.

Examples

The following example enables the Two-Rate Three-Color Policing and Marking feature for flows with a diffserv DSCP value matching the configured control-dscp value of af31. If the feature is enabled on a flow, the marker-dscp af11 keyword is used to color af11 class of packets that conform to pdr, but do not conform to sdr. In the example, a value3 of 150 is entered to calculate the pdr coefficient (where pdr is calculated as pdr = sdr * 150/100).

Router(config)# sbc mySbc dbe 

Router(config-sbc-dbe)# vdbe 

Router(config-sbc-dbe-vdbe)# control-dscp af31 marker-dscp af11 pdr-coefficient 150

Router(config-sbc-dbe-vdbe)# exit

Related Commands

controller h248

To configure the H.248 controller for a data border element (DBE) or enter into Controller H.248 configuration mode, use the controller h248 command in VDBE configuration mode. To delete the H.248 controller, use the no form of this command.

controller h248 {controller-index}

no controller h248 {controller-index}

Syntax Description

Command Default

No default behavior or values are available.

Command Modes

VDBE configuration (config-sbc-dbe-vdbe)

Command History

Usage Guidelines

Once a controller is configured and attached, it must be detached with the no attach-controllers command before you can modify any controller information.

Note This command is invalid for the unified model, where both the SBE and DBE logical entities co-exist on the same network element.

Examples

The following example creates a DBE service on an SBC called "mySbc," enters into SBC-DBE configuration and VDBE configuration modes, and configures an H.248 controller with index 1.

Router(config)# sbc mySbc dbe 

Router(config-sbc-dbe)# vdbe 

Router(config-sbc-dbe-vdbe)# controller h248 1

The following example configures an H.248 controller with index 1 and tries to configure an IPv4 remote address on the controller. The message indicates that the controller must be detached first before the remote address can be modified.

Router(config-sbc-dbe-vdbe)# controller h248 1

Router(config-sbc-dbe-vdbe-h248)# remote-address ipv4 210.229.108.253

SBC: remote-address cannot be changed while controllers are attached.

Related Commands

deactivation-mode

To specify the action the data border element (DBE) of a session border controller (SBC) takes upon deactivation of the DBE service, use the deactivation-mode command in SBC-DBE configuration mode. To revert deactivation behavior to the default of normal behavior, use the no form of this command.

deactivation-mode {deact-type}

no deactivation-mode

Syntax Description

Command Default

If the deactivation mode is not configured, or the default deactivation-mode command or no deactivation-mode commands are used, the state of the DBE service becomes normal.

Command Modes

SBC-DBE configuration (config-sbc-dbe)

Command History

Usage Guidelines

Use the no activate command to deactivate the DBE service. The deactivation-mode command tells the DBE how to behave or what action to take after the DBE is deactivated.

Use the sbc dbe command to enter into SBC-DBE configuration mode first.

Examples

The following example creates a DBE service on an SBC called "mySbc," enters into SBC-DBE configuration mode, and sets the DBE to deactivate in quiesce mode to prepare the device for hardware maintenance.

Router(config)# sbc mySbc dbe 

Router(config-sbc-dbe)# deactivation-mode quiesce

Router(config-sbc-dbe)# end

Related Commands

debug sbc filter

To enable logging based on a number of filters, use the debug sbc filter command in privileged EXEC mode. To disable logging based on these filters, use the no form of this command.

debug sbc {sbc-name} filter [adjacency {adj-name}] [bill {billing-id}] [ipv4 {ipv4-address}] [ipv6 {ipv6-address}] [number {number}] [billing] [call] [media] [overview] [protocol] [bm | cac | control | h323 | icc | radius | routing | sip | mgm]

no debug sbc {sbc-name} filter [adjacency {adj-name}] [bill {billing-id}] [ipv4 {ipv4-address}] [ipv6 {ipv6-address}] [number {number}] [billing] [call] [media] [overview] [protocol] [bm | cac | control | h323 | icc | radius | routing | sip | mgm]

Syntax Description

Command Default

Debugging is off.

Command Modes

Privileged EXEC (#)

Command History

Usage Guidelines

You can specify any number of optional keywords, but each keyword can only be specified once. At least one keyword must be specified for the debug sbc filter command. You can issue multiple debug sbc filter commands.

Note The debug logs are only output if the appropriate filter keywords have been specified.

The keywords are composed of the following types of filters:

•String filters—Allow the user to turn on logs about common SBC objects such as adjacencies. An object matches the string filter if the object exactly matches the string or the prefix matches the string.

String filters include the following keywords:

–adjacency {adj-name}

–bill {billing-id}

–ipv4 {ipv4-address}

–ipv6 {ipv6-address}

–number {number}

•Component filters—Turn on logs from individual components (or groups of components) within the SBC service. Only one component filter may be specified per debug sbc filter command.

Component filters include the following keywords:

bm, cac, control, h323, icc, radius, routing, sip, mgm

•Cross-SBC filters—Turn on logs across all components of the SBC service.

Cross-SBC filters include the following keywords:

billing, call, media, overview, protocol

Caution Because debugging output is assigned high priority in the CPU process, it can render the system unusable. For this reason, use debug commands only to troubleshoot specific problems or during troubleshooting sessions with Cisco technical support personnel. Moreover, it is best to use debug commands during periods of lower network traffic and fewer users. Debugging during these periods decreases the likelihood that increased debug command processing overhead will affect system use.

Examples

The following example shows all debug logs for the H.248 control channel to the SBE on an SBC called "mySbc":

Router# debug sbc mySbc filter control

The following example shows all debug logs relating to media flows on an SBC called "mySbc":

Router# debug sbc mySbc filter media

The following example shows all debug logs relating to media flows with a source or destination address of 10.0.1.1 on an SBC called "mySbc" including output logs for the specified IPv4 IP address:

Router# debug sbc mySbc filter media ipv4 10.0.1.1

The following example shows that if you want to show all debug logs that relate to media flowing to and from 10.0.1.1 or 10.0.1.2, you must issue the following two commands:

Router# debug sbc mySbc filter media ipv4 10.0.1.1

Router# debug sbc mySbc filter media ipv4 10.0.1.2

Related Commands

debug sbc ips

To turn on inter-process signal (IPS) tracing, use the debug sbc ips command in privileged EXEC mode. To turn off IPS tracing, use the no form of this command.

debug sbc {sbc-name} ips

no debug sbc {sbc-name} ips

Syntax Description

Command Default

Debugging is off.

Command Modes

Privileged EXEC (#)

Command History

Usage Guidelines

Inter-process signal (IPS) tracing provides details of inter-component signals flowing between the internal components of the session border controller (SBC) process. IPS traces are stored internally in an in-memory buffer and can be dumped to the file system using the sbc dump-diagnostics command. IPS traces are in a binary format and are intended to be used by Cisco customer support engineers to diagnose problems.

Caution Because debugging output is assigned high priority in the CPU process, it can render the system unusable. For this reason, use debug commands only to troubleshoot specific problems or during troubleshooting sessions with Cisco technical support personnel. Moreover, it is best to use debug commands during periods of lower network traffic and fewer users. Debugging during these periods decreases the likelihood that increased debug command processing overhead will affect system use.

Examples

The following example turns on IPS tracing on the SBC service called "mySbc":

Router# debug sbc mySbc ips

Related Commands

debug sbc log-level

To set the debug logging level for logging to the cyclic buffer or to the system logger, use the debug sbc log-level command in privileged EXEC mode. To disable the debug logging level, use the no form of this command.

debug sbc {sbc-name} log-level {buffer | console} {level}

no debug sbc {sbc-name} log-level {buffer | console}

Syntax Description

Command Default

Debugging is off.

Command Modes

Privileged EXEC (#)

Command History

Usage Guidelines

In the no form of this command, you do not need to specify the logging level because the command sets the logging level to the default.

Caution Because debugging output is assigned high priority in the CPU process, it can render the system unusable. For this reason, use debug commands only to troubleshoot specific problems or during troubleshooting sessions with Cisco technical support personnel. Moreover, it is best to use debug commands during periods of lower network traffic and fewer users. Debugging during these periods decreases the likelihood that increased debug command processing overhead will affect system use.

Examples

In the following example, setting the debug logging level to 90 logs fatal errors directly to the console:

Router# debug sbc mySbc log-level console 90

In the following example, setting the debug logging level to 0 writes all logs to the cyclic buffer:

Router# debug sbc mySbc log-level buffer 0

Related Commands

debug sbc mpf

To turn on debugging messages in the DBE forwarding processor for both session border controller (SBC) services and low-level drivers, use the debug sbc mpf command in privileged EXEC mode. To disable debugging, use the no form of this command.

debug sbc {sbc-name} mpf {all | error | info | flow}

no debug sbc {sbc-name} mpf {all | error | info | flow}

Syntax Description

Command Default

Debugging is off.

Command Modes

Privileged EXEC (#)

Command History

Usage Guidelines

Caution Because debugging output is assigned high priority in the CPU process, it can render the system unusable. For this reason, use debug commands only to troubleshoot specific problems or during troubleshooting sessions with Cisco technical support personnel. Moreover, it is best to use debug commands during periods of lower network traffic and fewer users. Debugging during these periods decreases the likelihood that increased debug command processing overhead will affect system use.

Examples

The following example shows the debug output from the debug sbc mpf all command and the SBC service called "global." The type of debugging message is indicated in bold and is not part of the debug output.

Router# debug sbe global mpf all

Flow Debugging Messages

(Func: zismps_rcv_pmi_flowp_alloc) Flow pair allocated (flow_pair_index = 20).

(Func: zismps_send_pmi_flowp_events_ind) Flow pair events (flow_pair_index = 20)

Side A: 1 ( media_up)

Side B: 0 ().

(Func: zismps_send_pmi_flowp_events_ind) Flow pair events (flow_pair_index = 20)

Side A: 0 ()

Side B: 1 ( media_up).

(Func: zismps_rcv_pmi_flowp_delete) Flow pair deleted (flow_pair_index = 20).

(Func: zismps_free_flow_pair) Flow pair freed (flow_pair_index = 20).

Informational Debugging Messages

Func: zismpf_reset) Resetting media packet forwarder

(Func: zismps_rcv_pmi_deactivate) MPF stub deactivated.

(Func: zismps_rcv_pmi_init) MPF stub initialized.

Error Debugging Message

(Func: zismpp_divert_packet) Incoming DTMF queue full - packet dropped

Related Commands

dtmf-duration

To configure the default duration of a dual-tone multifrequency (DTMF) event in milliseconds, use the dtmf-duration command in VDBE configuration mode. To reconfigure the default duration of a DTMF event in milliseconds, use the no form of this command.

dtmf-duration {duration}

no dtmf-duration

Syntax Description

Command Default

The default is 200 ms if this command is not configured, or the no dtmf-duration command is issued.

Command Modes

VDBE configuration (config-sbc-dbe-vdbe)

Command History

Examples

The following example creates a DBE service on an SBC called "mySbc," enters into SBC-DBE configuration and VDBE configuration modes, and configures the default duration of a DTMF event to be 250 milliseconds.

Router(config)# sbc mySbc dbe 

Router(config-sbc-dbe)# vdbe 

Router(config-sbc-dbe-vdbe)# dtmf-duration 250

Router(config-sbc-dbe-vdbe)# end

h248-association-timeout

To configure the data border element (DBE) to reset the H.248 association with the Media Gateway Controller (MGC) when the controller does not respond to any event notification, use the h248-association-timeout command in VDBE configuration mode. To configure the DBE to reset the H.248 association only when the controller fails to respond to the inactivity timer (it/ito) event, use the no form of this command. (This behavior is the default and standard H.248 protocol behavior.)

h248-association-timeout

no h248-association-timeout

Syntax Description

This command has no arguments or keywords.

Command Default

The default is no h248-association-timeout; only failure to notify the MGC of the it/ito event causes the H.248 association with the MGC to be reset. (This behavior is the standard H.248 protocol behavior.)

Command Modes

VDBE configuration (config-sbc-dbe-vdbe)

Command History

Examples

The following example configures the DBE to reset the H.248 association with the MGC controller when the controller does not respond to any event notification:

Router (config)# sbc mySbc dbe 

Router (config-sbc-dbe)# vdbe

Router (config-sbc-dbe-vdbe)# h248-association-timeout

Router (config-sbc-dbe-vdbe)# end

The following example configures the DBE to reset the H.248 association only when the controller fails to respond to the inactivity timer (it/ito) event:

Router (config)# sbc mySbc dbe 

Router (config-sbc-dbe)# vdbe

Router (config-sbc-dbe-vdbe)# no h248-association-timeout

Router (config-sbc-dbe-vdbe)# end

Related Commands

h248-event-storage

To enable permanent storage of all H.248 events, use the h248-event-storage command in VDBE configuration mode. To disable permanent storage of H.248 events, where H.248 events are only retained until they are acknowledged by the media gateway controller (MGC), use the no form of the command.

h248-event-storage

no h248-event-storage

Syntax Description

This command has no arguments or keywords.

Command Default

The default is that H.248 events are only stored until they are acknowledged by the MGC. The default is no h248-event-storage.

Command Modes

VDBE configuration (config-sbc-dbe-vdbe)

Command History

Usage Guidelines

It is important to understand that H.248 event storage is always turned on. There are two modes of H.248 storage:

•Permanent storage of H.248 events, enabled by the h248-event-storage command.

In this mode, H.248 events are stored permanently. To reduce the memory required to store event information, the DBE only stores the most recent H.248 event of each type for each stream, except for dual-tone multifrequency (DTMF) events, which are always stored.

•Storage of H.248 events only until the events are acknowledged by the media gateway controller (MGC). This is enabled by the no h248-event-storage command and is the system default.

H.248 events other than those relating to a media timeout are deleted by the MGC after the MGC has acknowledged them. In this mode, the H.248 events relating to a media timeout are retained if the H.248 association fails.

Examples

The following example configures the data border element (DBE) to enable permanent H.248 event storage:

Router (config)# sbc mySbc dbe

Router (config-sbc-dbe)# vdbe

Router (config-sbc-dbe-vdbe)# h248-event-storage

Router (config-sbc-dbe-vdbe)# end

Related Commands

h248-inactivity-duration

To define the duration of the provisioned inactivity timer, use the h248-inactivity-duration command in VDBE configuration mode. To reconfigure the duration of the provisioned inactivity timer to the default value (0 milliseconds), use the no form of this command.

h248-inactivity-duration duration

no h248-inactivity-duration

Syntax Description

Command Default

If the h248-inactivity-duration command is not specified, the default is 0 milliseconds, which indicates the timer is not in effect.

Command Modes

VDBE configuration (config-sbc-dbe-vdbe)

Command History

Usage Guidelines

The advantage of a provisioned inactivity timer is that the DBE can detect MGC failure whether or not the MGC has subscribed to the inactivity timer event.

The MGC can still subscribe to the inactivity timer event, and situations can occur when a different duration interval is specified for the MGC than that specified for the DBE in the provisioned inactivity timer. When two conflicting values are specified, the MGC subscription duration value overrides the provisioned duration value. However, if the MGC cancels its subscription, or the association fails, the provisioned duration value goes back into effect. The provisioned inactivity timer is started when a successful response is received to the initial ServiceChange request to the MGC.

Examples

The following example creates a DBE service on an SBC called "mySbc," enters into SBC-DBE configuration and VDBE configuration modes, and configures the DBE to use a duration of 100 milliseconds for the provisioned inactivity timer:

Router(config)# sbc mySbc dbe

Router(config-sbc-dbe)# vdbe

Router(config-sbc-dbe-vdbe)# h248-inactivity-duration 10

Router(config-sbc-dbe-vdbe)# end

h248-media-alert-event

To enable the Middlebox Pinhole Timer Expired event when the DBE detects media loss, use the h248-media-alert-event command in VDBE configuration mode. To disable the Middlebox Pinhole Timer Expired event, use the no form of this command.

h248-media-alert-event

no h248-media-alert-event

Syntax Description

This command has no arguments or keywords.

Command Default

The default behavior is that this event is generated.

Command Modes

VDBE configuration mode (config-sbc-dbe-vdbe)

Command History

Usage Guidelines

The media gateway controller (MGC) may additionally request a Network Package Quality Alert event be generated, independent of the setting of this feature.

Examples

The following example enables generation of the Middlebox Pinhole Timer Expired event on detection of lost media:

(config)# sbc mySbc dbe

(config-sbc-dbe)# vdbe

(config-sbc-dbe-vdbe)# h248-media-alert-event

(config-sbc-dbe-vdbe)# end

The following example disables generation of the Middlebox Pinhole Timer Expired event on detection of lost media:

(config)# sbc mySbc dbe

(config-sbc-dbe)# vdbe

(config-sbc-dbe-vdbe)# no h248-media-alert-event

(config-sbc-dbe-vdbe)# end

h248-napt-package

To define which H.248 package, either the IP NAPT Traversal (ipnapt) package or the NAT Traversal (ntr) package, the DBE uses for signaling Network Address Translation (NAT) features, use the h248-napt-package command in VDBE configuration mode. To reconfigure the DBE to use the default NTR package, use the no form of this command.

h248-napt-package [napt | ntr]

no h248-napt-package

Syntax Description

Command Default

If the h248-napt-package command is not specified, the ntr value is used.

Command Modes

VDBE configuration mode (config-sbc-dbe-vdbe)

Command History

Usage Guidelines

Terminations may not be programmed using both the ntr and ipnapt packages.

The IP NAPT Traversal (ipnapt) package, defined in H.248.37. IP NAPT is an alternative method to the existing support of the NAT Traversal (ntr) package defined in ETSI TS 102 333. IP NAPT defines two signals, latch and relatch, to control how the DBE learns remote addresses for endpoints behind a NAT.

Examples

The following example creates a data border element (DBE) service on an SBC called "mySbc," enters into SBC-DBE configuration and VDBE configuration modes, and configures the DBE to use the IP NAPT Traversal package:

Router(config)# sbc mySbc dbe 

Router(config-sbc-dbe)# vdbe

Router(config-sbc-dbe-vdbe)# h248-napt-package napt

Router(config-sbc-dbe-vdbe)# end

Related Commands

h248-preserve-gates

To configure the data border element (DBE) to preserve media terminations or contexts when all streams within the context are in media-down state while the H.248 association with the controller is down, use the h248-preserve-gates command in VDBE configuration mode. To allow the DBE to delete contexts when all streams within the context are in media-down state and there is no current H.248 association with a media gateway controller (MGC), use the no form of this command.

h248-preserve-gates

no h248-preserve-gates

Syntax Description

This command has no arguments or keywords.

Command Default

The default is no h248-preserve-gates; the DBE can delete contexts when all streams within the context are in media-down state and there is no current H.248 association with the MGC. (This behavior is the standard H.248 protocol behavior.)

Command Modes

VDBE configuration (config-sbc-dbe-vdbe)

Command History

Usage Guidelines

If this command is not enabled, silent gate deletion can occur. The DBE can delete contexts when all streams within the context are in media-down state, that is, when streams have no media flowing for the media-timeout duration, and there is no current H.248 association with the MGC.

Examples

The following example configures the DBE to preserve media terminations or contexts when all streams within the context are in media-down state while the H.248 association with the controller is down:

Router (config)# sbc mySbc dbe 

Router (config-sbc-dbe)# vdbe

Router (config-sbc-dbe-vdbe)# h248-preserve-gates

Router (config-sbc-dbe-vdbe)# end

The following example configures the DBE to allow the DBE to delete contexts when all streams within the context are in media-down state and there is no current H.248 association with an MGC:

Router (config)# sbc mySbc dbe 

Router (config-sbc-dbe)# vdbe

Router (config-sbc-dbe-vdbe)# no h248-preserve-gates

Router (config-sbc-dbe-vdbe)# end

Related Commands

h248-profile

To configure a Virtual Data Border Element (VDBE) H.248 profile name to interoperate with the data border element (DBE), use the h248-profile command in the vDBE configuration mode. To return to the default value, use the no form of this command.

h248-profile {etsi-bgf | gate-ctrl} version version-number

no h248-profile

Syntax Description

Command Default

Default value is gatecontrol.

Command Modes

VDBE configuration (config-sbc-dbe-vdbe)

Command History

Usage Guidelines

To use this command, you must be in a user group that is associated with a task group that includes the proper task IDs. To use this command, you must also be in the correct configuration mode. The Examples section that follows shows the hierarchy of the modes required to run the command.

After the DBE is configured to use the H.248 profile name, the applicable profile name is advertised with the Service Change messages.

Examples

The following example shows how to configure the vDBE H.248 Ia profile to interoperate with the DBE:

Router# configure terminal

Router(config-sbc)# sbc mysbc dbe

Router(config-sbc-dbe)# vdbe

Router(config-sbc-dbe-vdbe)# h248-profile etsi-bgf version 2

Related Commands

h248-version

To define the version of the H.248 protocol that the DBE uses when it forms associations with an H.248 controller, use the h248-version command in VDBE configuration mode. To reconfigure to the default version, use the no form of this command.

h248-version version

no h248-version

Syntax Description

Command Default

If the h248-version command is not specified, the default is H.248.1 version 2.

Command Modes

VDBE configuration mode (config-sbc-dbe-vdbe)

Command History

Usage Guidelines

This command configures the DBE to support H.248.1v3, thus allowing the DBE to interoperate with an SBE or media gateway controller (MGC) which requires H.248.1 version 3. The DBE can accept H.248.1 version 2 or version 3.

The DBE rejects attempts to negotiate with the MGC to a lower version once the DBE is configured to support version 3.

Examples

The following example creates a data border element (DBE) service on an SBC called "mySbc," enters into SBC-DBE configuration and VDBE configuration modes, and configures the virtual data border element (vDBE) to use H.248.1 version 3:

Router(config)# sbc mySbc dbe 

Router(config-sbc-dbe)# vdbe

Router(config-sbc-dbe-vdbe)# h248-version 3

Router(config-sbc-dbe-vdbe)# end

Related Commands

inbound

To configure inbound call packets to use a specific Security Parameters Index (SPI) to identify the security association to which an incoming packet is bound when the Interim Authentication Header (IAH) is enabled, use the inbound command in IAH Key configuration mode. To remove the configuration, use the no form of this command.

inbound spi hex-key

no inbound spi hex-key

Syntax Description

Command Default

None

Command Modes

IAH Key configuration mode (config-sbc-dbe-vdbe-h248-iah)

Command History

Usage Guidelines

The inbound command is used in conjunction with the outbound and transport (session border controller) commands. The three commands are used together to enable Interim Authentication Header (IAH) authentication of inbound and outbound call packets. If you specify a hashing scheme (ah-md5-hmac or ah-sha-hmac type of authentication), using the transport (session border controller) command, you need to configure incoming and outgoing call packets using both inbound and outbound commands. The inbound and outbound commands are used to specify the Security Parameters Index (SPI) and hex-key.

Both inbound and outbound SPI need to be configured. If authentication is set to MD5 or SHA hashing scheme and only the inbound or outbound SPI key or neither inbound or outbound SPI key is configured, the authentication reverts back to zero authentication and the DBE issues a warning message "Both inbound and outbound keys must be configured to enable authentication." In this event, the DBE sets all fields in the IAH header to zeroes and accepts any IAH without authentication.

Examples

The following example shows you how to configure the IAH to use the HMAC-SHA hashing scheme, set the inbound Security Parameters Index (SPI) to 300 and the outbound SPI to 400, and hash key to "myInboundKey45" and "myOutboundKey89" respectively:

Router(config)# sbc global dbe

Router(config-sbc-dbe)# vdbe global

Router(config-sbc-dbe-vdbe)# h248-version 3

Router(config-sbc-dbe-vdbe)# h248-napt-package napt

Router(config-sbc-dbe-vdbe)# local-port 2970

Router(config-sbc-dbe-vdbe)# control-address h248 ipv4 200.50.1.40

Router(config-sbc-dbe-vdbe)# controller h248 2

Router(config-sbc-dbe-vdbe-h248)# remote-address ipv4 200.50.1.254

Router(config-sbc-dbe-vdbe-h248)# remote-port 2970

Router(config-sbc-dbe-vdbe-h248)# transport tcp interim-auth-header ah-sha-hmac 

Router(config-sbc-dbe-vdbe-h248-iah)# inbound 300 myInboundKey45

Router(config-sbc-dbe-vdbe-h248-iah)# outbound 400 myOutboundKey89

Router(config-sbc-dbe-vdbe-h248)# exit

Router(config-sbc-dbe-vdbe)# attach-controllers

Related Commands

interface sbc

To create a session border controller (SBC) interface and enter interface configuration mode, use the interface sbc command in global configuration mode. To delete the SBC interface, use the no form of this command.

interface sbc {interface-number}

no interface sbc {interface-number}

Syntax Description

Command Default

No default behavior or values are available.

Command Modes

Global configuration (config)

Command History

Usage Guidelines

This command creates an SBC logical interface and enters into interface configuration mode, the submode of the SBC interface, where you can perform configuration on the SBC interface, such as configuring IP addresses.

Examples

The following example creates SBC interface 10 and enters into interface configuration mode:

Router(config)# interface sbc 10

Router(config-if)# 

Related Commands

ip address (session border controller)

To configure the IPv4 address and the subnet mask on a session border controller (SBC) interface, use the ip address command in interface configuration mode. To delete the IPv4 address on the SBC interface, use the no form of this command.

ip address {IPv4 address} {IPv4 subnet mask}

no ip address {IPv4 address} {IPv4 subnet mask}

Syntax Description

Command Default

No IPv4 addresses are defined for any SBC interface.

Command Modes

Interface configuration (config-if)

Command History

Usage Guidelines

Use the ip address command to configure the IPv4 address and the subnet mask on an SBC interface first before using the media-address ipv4 command or the media-address pool ipv4 command.

The subnet mask on the SBC interface is used by SBC configuration in the media-address ipv4 command or the media-address pool ipv4 command.

To avoid SBC configuration errors, all corresponding DBE IPv4 media addresses set by the media-address ipv4 command and IPv4 media address pools set by the media-address pool ipv4 command must be removed from the SBC configuration before removing the IPv4 address from the SBC interface.

Note Configure the IPv4 addresses first, then configure the media addresses with the media-address ipv4 command. When the media addresses have been configured, the media addresses will be automatically generated on an SBC interface. It is highly recommended that you do not change or remove the automatically configured media addresses.

Examples

The following example creates an IPv4 address 1.1.1.1 with subnet mask 255.255.0.0 on interface SBC "3":

Router(config)# interface sbc 3

Router(config-if)# ip address 1.1.1.1 255.255.0.0

Router(config-if)# end

Related Commands

ipv6 address (session border controller)

To configure an IPv6 address based on an IPv6 general prefix and enable IPv6 processing on an SBC interface, use the ipv6 address (session border controller) command in interface configuration mode. To remove the address and prefix from the SBC interface, use the no form of this command.

ipv6 address {IPv6 address/prefix-length}

no ipv6 address {IPv6 address/prefix-length}

Syntax Description

Command Default

No IPv6 addresses are defined for any SBC interface.

Command Modes

Interface configuration (config-if)

Command History

Usage Guidelines

Configure the IPv6 prefix first before you use the media-address ipv6 or media-address pool ipv6 commands.

To avoid SBC configuration errors, all corresponding DBE IPv6 media addresses set by the media-address ipv6 command and IPv6 media address pools set by the media-address pool ipv6 command must be removed from the SBC configuration before removing the IPv6 address from the SBC interface.

Note Configure the IPv6 addresses first, then configure the media addresses with the media-address ipv6 command. When the media addresses have been configured, the media addresses will be automatically generated on an SBC interface. It is highly recommended that you do not change or remove the automatically configured media addresses.

Examples

The following example creates an SBC interface called "3," enters into interface configuration mode, and creates an IPv6 prefix 1::1/64 on SBC interface "3":

Router(config)# interface sbc 3

Router(config-if)# ipv6 address 1::1/64

Router(config-if)# end

Related Commands

local-port

To configure a data border element (DBE) to use a specific local port when connecting to the default media gateway controller (MGC), use the local-port command in VDBE configuration mode. To disable this configuration, use the no form of this command.

local-port {port-num}

no local-port

Syntax Description

Command Default

The default is to use any available local port.

Command Modes

VDBE configuration (config-sbc-dbe-vdbe)

Command History

Usage Guidelines

The local port cannot be modified once any controller has been configured on the virtual data border element (vDBE). You must delete the controller before you can modify or configure the local port.

Examples

The following example creates a DBE service on an SBC called "mySbc," enters into SBC-DBE configuration and VDBE configuration modes, and configures the DBE to use the local port number 5090:

Router(config)# sbc mySbc dbe

Router(config-sbc-dbe)# vdbe

Router(config-sbc-dbe-vdbe)# local-port 5090

Router(config-sbc-dbe-vdbe)# end

Related Commands

local-remote-desc always

To configure the data border element (DBE) so that it always returns the local and remote descriptors in an H.248 Reply to the signaling border element (SBE ), use the local-remote-desc always command in VDBE configuration mode. To reset to the default behavior, use the no form of this command.

local-remote-desc always

no local-remote-desc always

Syntax Description

This command has no arguments or keywords.

Command Default

The default behavior is that the DBE only returns a local or remote descriptor in an H.248 Reply when the descriptor is either under-specified or over-specified in the associated request.

Command Modes

VDBE configuration (config-sbc-dbe-vdbe)

Command History

Usage Guidelines

This command configures the DBE to always return the local and remote descriptors in an H.248 Reply if the descriptors are present in the H.248 request. This command enhances H.248 interoperability with the SBE.

The default behavior is that the DBE only returns a local or remote descriptor in an H.248 Reply when the descriptor is either under-specified or over-specified in the associated request. Under-specified means the SBE includes a CHOOSE ($) wildcard in the Request. Over-specified means the SBE includes multiple codecs in the Request and allows the DBE to choose one codec from the list.

Examples

The following example configures the DBE to always include the local and remote descriptor in an H.248 Reply if those descriptors are present in the H.248 request:

Router# configure terminal 

Router(config)# sbc global dbe 

Router(config-sbc-dbe)# vdbe global 

Router(config-sbc-dbe-vdbe)# local-remote-desc always

The following example uses the no form of the command to configure the DBE to not include local and remote descriptor in an H.248 Reply except under the condition that the descriptors are returned only if they were under-specified or over-specified on the H.248 request:

Router# configure terminal 

Router(config)# sbc global dbe 

Router(config-sbc-dbe)# vdbe global

Router(config-sbc-dbe-vdbe)# no local-remote-desc always

Related Commands

location-id

To configure the location ID for a data border element (DBE) service of the session border controller (SBC), use the location-id command in SBC-DBE configuration mode. To set the location ID to the default, use the no form of this command.

location-id {location-id}

no location-id

Syntax Description

Command Default

The default is 0xFFFFFFFF (-1) if the command is not configured, or the no location-id command is issued.

Command Modes

SBC-DBE configuration (config-sbc-dbe)

Command History

Usage Guidelines

The no form of the command does not take an argument and sets the location ID to the default, which is 0xFFFFFFFF (-1).

A location ID is configured on each DBE. The SBE may associate endpoints with a particular location ID and then use the location IDs to route calls between different DBEs.

Use the sbc dbe command to enter into SBC-DBE configuration mode prior to entering the location-id command.

Examples

The following example creates a DBE service on an SBC called "mySbc," enters into SBC-DBE configuration mode, and sets the location ID for a DBE to be 1:

Router(config)# sbc mySbc dbe 

Router(config-sbc-dbe)# location-id 1

Router(config-sbc-dbe)# end

Related Commands

logging filter control protocol

To set the H.248 protocol message filter to display only the H.248 text from the console logs on the Data Border Element (DBE), use the logging filter control protocol command in VDBE configuration mode. To disable the H.248 protocol message filter, use the no form of this command.

logging filter control protocol

no logging filter control protocol

Syntax Description

This command has no arguments or keywords.

Command Default

No default behavior or values are available..

Command Modes

VDBE configuration mode (config-sbc-dbe-vdbe)

Command History

Usage Guidelines

Use this command to set the H.248 protocol message filter for console logging to display only the H.248 text without any internal message logs.

Note If you enable the logging filter control protocol using both a debug command and the logging filter control protocol command, the logging filter control protocol must be disabled by both commands before the filter is disabled.

Examples

The following example shows sample DBE configuration steps where the H.248 protocol message filter is enabled:

Router(config)# sbc global dbe

Router(config-sbc-dbe)# vdbe global

Router(config-sbc-dbe-vdbe)# h248-version 3

Router(config-sbc-dbe-vdbe)# h248-napt-package napt

Router(config-sbc-dbe-vdbe)# local-port 2971

Router(config-sbc-dbe-vdbe)# control-address h248 ipv4 200.50.1.41

Router(config-sbc-dbe-vdbe)# logging filter control protocol

Router(config-sbc-dbe-vdbe)# controller h248 2

Router(config-sbc-dbe-vdbe-h248)# remote-address ipv4 200.50.1.254

Router(config-sbc-dbe-vdbe-h248)# remote-port 2971

Router(config-sbc-dbe-vdbe-h248)# exit

Router(config-sbc-dbe-vdbe)# attach-controllers

Router(config-sbc-dbe-vdbe)# end

With the H.248 protocol message filter enabled, the following is an example log output for a single H.248 ADD message and the Reply:

*Dec 20 00:19:33.090: %SYS-5-CONFIG_I: Configured from console by console

*Dec 20 00:19:36.951: %SBC-7-MSG-2E01-0074-67C592-0537: SBC/MG-CTRL: 

Megaco message received.

Remote address = 200.50.1.254

Message text   = 

AU=0x12345678:0x90ABCDEF:0x000000000000000000000000123456

!/3 [200.50.1.40]:2971 T=6 {

C = $ {

A = abc/sip4/gn/0/1/0/1/ac/$ {

M {

TS { SI = IV },

ST = 1 {

O { MO = SR

},

R {

v=0

c=IN IP4 3.0.0.3

m=application 5000 udp 0

},

L {

v=0

c=IN IP4 $

m=application $ udp 0

}

}

}

},

A = abc/sip4/gn/0/1/0/1/bb/$ {

M { 

TS { SI = IV },

ST = 1 {

O { MO = SR,

ds/dscp = 1D},

R {

v=0

c=IN IP4 3.0.0.3

m=application 5000 udp 0

}

*Dec 20 00:19:36.986: %SBC-7-MSG-2E01-0073-1C5642-0992: SBC/MG-CTRL: 

Megaco message sent.

Remote address = 200.50.1.254

Message text   = 

!/3 [200.50.1.40]:2971

P=6{

C=1{

A=abc/sip4/gn/0/1/0/1/ac/1{

M{

ST=1{

L{

v=0

c=IN IP4 202.50.2.1

m=application 10000 udp 0

}}}},

A=abc/sip4/gn/0/1/0/1/bb/2{

M{

ST=1{

L{

v=0

c=IN IP4 202.50.2.1

m=application 10001 udp 0

}}}}}}

Related Commands

logging level

To enable console logging for non-default logging and set the logging level used for logging H.248 and other messages to the Data Border Element (DBE), use the logging level command in VDBE configuration mode. To disable the console logging, use the no form of this command.

logging level [value]

no logging level [value]

Syntax Description

Command Default

Logging level 63 is on by default if you do not specify a logging level.

Command Modes

VDBE configuration mode (config-sbc-dbe-vdbe)

Command History

Usage Guidelines

This command sends messages to a logging process, which controls the distribution of logging messages to the syslog server and the console. This command sets the severity logging level on the DBE and limits logging messages displayed on the console to messages for that specified level and above. For example a specified logging level of 30 would display log messages from logging levels 30, 40, 50, 60, 70, 80, and 90.

A logging level of 30 generates logs showing H.248 requests and responses. The lower the log level, the more syslog bandwidth is taken up.

Note that some messages may be displayed on the standby Route Processor (RP) because some of the components remain in the active stage on the standby RP and may produce those messages.

Session Border Controller (SBC) debug commands that set the logging level and the H.248 protocol message filter, such as debug sbc log-level and debug sbc filter, can be enabled at the same time.

The logging level command works with SBC and Cisco IOS debug commands as follows:

•If logging and logging level are enabled by the logging level command, it can only be disabled by the logging level command. The undebug all and no debug sbc log-level commands have no effect.

•If logging and logging level are enabled by a debug command, it can be disabled by the undebug all and no debug sbc log-level command.

•If two different logging levels are set by both a debug command and the logging level command, the lower logging level is applied.

•If the same level is set using both the logging level command and a debug command—to turn off logging for that level, you must disable logging using both the logging level command and the debug command.

Examples

The following example shows sample DBE configuration steps where logging level 30 is set:

Router(config)# sbc global dbe

Router(config-sbc-dbe)# vdbe global

Router(config-sbc-dbe-vdbe)# h248-version 3

Router(config-sbc-dbe-vdbe)# h248-napt-package napt

Router(config-sbc-dbe-vdbe)# local-port 2971

Router(config-sbc-dbe-vdbe)# control-address h248 ipv4 200.50.1.41

Router(config-sbc-dbe-vdbe)# logging level 30

Router(config-sbc-dbe-vdbe)# controller h248 2

Router(config-sbc-dbe-vdbe-h248)# remote-address ipv4 200.50.1.254

Router(config-sbc-dbe-vdbe-h248)# remote-port 2971

Router(config-sbc-dbe-vdbe-h248)# exit

Router(config-sbc-dbe-vdbe)# attach-controllers

Router(config-sbc-dbe-vdbe)# end

The following shows sample log output produced on an ADD request with logging level 30 set:

*Sep 10 06:38:39.039: %SBC-7-MSG-2E01-0092: SBC/MG-CTRL: (gctarecv.c

1397) Application has completed processing a transaction asynchronously

Transaction ID          = 3

Transaction type        = 0X01

*Sep 10 06:38:49.539: %SBC-7-MSG-2E01-0050: SBC/MG-CTRL: (gctphash.c

701) A hash table has been resized.

The previous size of the hash table was 1024 entries.

The new size of the hash table is 512 entries.

The following example shows log output for a single H.248 ADD request to the DBE from the MGC, with the logging filter control protocol enabled:

*Aug 13 06:20:02.519: %SBC-7-MSG-2E01-0074: SBC/MG-CTRL: 

Megaco message received.

Remote address = 200.50.1.254

Message text   =

AU=0x12345678:0x90ABCDEF:0x000000000000000000000000123456

!/3 [200.50.1.40]:2970 T=3 {

C = $ {

A = abc/sip4/gn/0/1/0/1/ac/$ {

M {

TS { SI = IV },

ST = 1 {

O { MO = SR

},

R {

v=0

c=IN IP4 3.0.0.3

m=application 5000 udp 0

},

L {

v=0

c=IN IP4 $

m=application $ udp 0

}

}

}

},

A = abc/sip4/gn/0/1/0/1/bb/$ {

M { TS { SI = IV },

ST = 1 {

O { MO = SR,

ds/dscp = 1D},

R {

v=0

c=IN IP4 3.0.0.3

Related Commands

media-address ipv4

To add an IPv4 address to the set of addresses that can be used by the data border element (DBE) as a local media address, use the media-address ipv4 command in SBC-DBE configuration mode. To remove an IPv4 address from the set of local media addresses, use the no form of this command.

media-address ipv4 {A.B.C.D} [nat-mode twice-nat | vrf vrf-name | managed-by {dbe | mgc}]

no media-address ipv4 {A.B.C.D} [nat-mode twice-nat | vrf vrf-name | managed-by {dbe | mgc}]

Syntax Description

Command Default

No default behavior or values are available.

Command Modes

SBC-DBE configuration (config-sbc-dbe)

Command History

Usage Guidelines

Use the media-address ipv4 command to configure a local media address for traffic arriving on the DBE for each IP address that you specified under the SBC virtual interface with the ip address command.

Once you have configured a local media address, the media address cannot be modified while the DBE service is active. Deactivate the DBE with the no activate command first.

The media address is a pool of IP addresses on the DBE for media relay functionality. A pool of addresses is defined for the global VPN to which the DBE is attached. All vDBEs within the DBE draw media addresses from this pool.

Examples

The following example shows that IPv4 address 10.0.1.1, configured on an SBC interface, is the local address used for media traffic arriving on the DBE and it is reserved for Twice-NAT pinholes:

Router(config)# sbc mySbc dbe 

Router(config-sbc-dbe)# media-address ipv4 10.0.1.1 managed-by mgc nat-mode twice-nat

Router(config-sbc-dbe-media-address)# end

The following example shows that IP address 10.0.1.1 (which is an address configured on an SBC interface) is used for media traffic arriving on the DBE from the global VPN:

Router(config)# sbc mySbc dbe 

Router(config-sbc-dbe)# media-address ipv4 10.0.1.1

Router(config-sbc-dbe-media-address)# end

The following example tries to delete the media address 1.1.1.1 before first deactivating the DBE, and receives an error message:

Router(config-sbc-dbe)# no media-address ipv4 1.1.1.1

SBC: Unable to delete a media address whilst the DBE is active.

SBC: Please deactivate the DBE and try again.

Related Commands

media-address ipv6

To add an IPv6 address to the set of addresses that can be used by the data border element (DBE) as a local media address, use the media-address ipv6 command in SBC-DBE configuration mode. To remove an IPv6 address from the set of local media addresses, use the no form of this command.

media-address ipv6 {ipv6-address} [nat-mode twice-nat | vrf vrf-name | managed-by {dbe | mgc}]

no media-address ipv6 {ipv6-address} [nat-mode twice-nat | vrf vrf-name | managed-by {dbe | mgc}]

Syntax Description

Command Default

The default is that the IPv6 address is a member of the global VRF, and only the DBE may select the IPv6 address as the local address for flows.

Command Modes

SBC-DBE configuration (config-sbc-dbe)

Command History

Usage Guidelines

Use the media-address ipv6 command to configure a local media address for traffic arriving on the DBE for each IP address that you specified under the SBC virtual interface with the ipv6 address command.

Use the media-address ipv6 command to enter into SBC-DBE media address IPv6 configuration mode before using the port-range (ipv6) command.

After you have configured a local media address, the media address cannot be modified while the DBE service is active. Deactivate the DBE with the no activate command before modifying the media-address ipv6 specification.

The media address is a pool of IP addresses on the DBE for media relay functionality. A pool of addresses is defined for the global VPN to which the DBE is attached. All virtual data border elements (vDBEs) within the DBE draw media addresses from this pool.

Examples

The following example configures IPv6 address 5::1:1as the local address, reserved for Twice-NAT pinholes:

Router(config)# sbc mySbc dbe

Router(config-sbc-dbe)# media-address ipv6 5::1:1 managed-by mgc nat-mode twice-nat

Router(cfg-sbc-dbe-media-addr-ipv6)# exit

The following example configures IPv6 address 5::1:1:

Router(config)# sbc mySbc dbe

Router(config-sbc-dbe)# media-address ipv6 5::1:1

Router(cfg-sbc-dbe-media-addr-ipv6)# exit

The following example tries to delete the IPv6 media address 5::1:1 before first deactivating the DBE, and receives an error message:

Router(config-sbc-dbe)# no media-address ipv6 5::1:1

SBC: Unable to delete a media address whilst the DBE is active.

SBC: Please deactivate the DBE and try again.

Related Commands

media-address pool ipv4

To create a pool of sequential IPv4 media addresses that can be used by the data border element (DBE) as local media addresses, use the media-address pool ipv4 command in SBC-DBE configuration mode. This pool of addresses is added to the set of local media addresses that can be used by DBE. To remove this pool of IPv4 addresses from the set of local media addresses, use the no form of this command.

media-address pool ipv4 {A.B.C.D} {E.F.G.H} [nat-mode twice-nat | vrf vrf-name | managed-by {dbe | mgc}]

no media-address pool ipv4 {A.B.C.D} {E.F.G.H} [nat-mode twice-nat | vrf vrf-name | managed-by {dbe | mgc}]

Syntax Description

Command Default

If a pool of IPv4 media addresses is specified, but the optional parameters are not specified, the following default values are used:

•Addresses in the pool are members of the global VRF.

•Only the DBE is allowed to select these addresses as local addresses for flows.

Command Modes

SBC-DBE configuration (config-sbc-dbe)

Command History

Usage Guidelines

The media address pool size is limited to 1024 IPv4 addresses. If more IPv4 addresses are required, we recommend you create multiple SBC interfaces and then configure the address pools from the subnets on those interfaces.

After you have configured a local media address, the media address cannot be modified while the DBE service is active. Deactivate the DBE with the no activate command before modifying the media-address pool ipv4 specification.

A media address is one of a pool of IP addresses on the DBE that are used for media relay functionality. A pool of addresses is defined for the global VPN to which the DBE is attached. All virtual data border elements (vDBEs) within the DBE draw media addresses from this pool.

Examples

The following example adds IPv4 addresses from 10.0.2.1 to 10.0.2.10 to the media address pool as local addresses, reserved for Twice-NAT pinholes:

Router(config)# sbc mySbc dbe 
Router(config-sbc-dbe)# media-address pool ipv4 10.0.2.1 10.0.2.10 nat-mode twice-nat 
Router(config-sbc-dbe-media-address-pool)# exit

The following example creates a DBE service on an SBC called "mySbc," enters into SBC-DBE configuration mode, and configures addresses from 10.0.2.1 to 10.0.2.10 in the global VRF:

Router(config)# sbc mySbc dbe 
Router(config-sbc-dbe)# media-address pool ipv4 10.0.2.1 10.0.2.10 
Router(config-sbc-dbe-media-address-pool)# exit

The following example creates a DBE service on an SBC called "mySbc," enters into SBC-DBE configuration mode, and configures addresses from 10.0.2.20 to 10.0.2.25 in vpn3:

Router(config)# sbc mySbc dbe 
Router(config-sbc-dbe)# media-address pool ipv4 10.0.2.20 10.0.2.25 vrf vpn3 
Router(config-sbc-dbe-media-address-pool)# exit

The following example tries to delete the media address 10.0.2.1 before first deactivating the DBE and receives an error message:

Router(config-sbc-dbe)# no media-address ipv4 10.0.2.1

SBC: Unable to delete a media address whilst the DBE is active.

SBC: Please deactivate the DBE and try again.

Related Commands

media-address pool ipv6

To create a pool of sequential IPv6 media addresses that can be used by the data border element (DBE) as local media addresses, use the media-address pool ipv6 command in SBC-DBE configuration mode. This pool of addresses is added to the set of local media addresses that can be used by the DBE. To remove this pool of IPv6 addresses from the set of local media addresses, use the no form of this command.

media-address pool ipv6 {start-ipv6-address} {end-ipv6-address} [nat-mode twice-nat | vrf vrf-name | managed-by {dbe | mgc}]

no media-address pool ipv6 {start-ipv6-address} {end-ipv6-address} [nat-mode twice-nat | vrf vrf-name | managed-by {dbe | mgc}]

Syntax Description

Command Default

If a pool or range of IPv6 media addresses is specified, but the optional parameters are not specified, the following default values are used:

•Addresses in the pool are members of the global VRF.

•Only the DBE is allowed to select these addresses as local addresses for flows.

Command Modes

SBC-DBE configuration (config-sbc-dbe)

Command History

Usage Guidelines

Use the media-address pool ipv6 command to enter into SBC-DBE media address pool IPv6 configuration mode before using the port-range (ipv6) command.

After you have configured a local media address, the media address cannot be modified while the DBE service is active. Deactivate the DBE with the no activate command before modifying the media-address pool ipv6 specification.

A media address is one of a pool of IP addresses on the DBE that are used for media relay functionality. A pool of addresses is defined for the global VPN to which the DBE is attached. All virtual data border elements (vDBEs) within the DBE draw media addresses from this pool.

Examples

The following example adds IPv6 addresses from 5::1:1 to 5::1:10 to the media address pool as local addresses, reserved for Twice-NAT pinholes:

Router(config)# sbc mySbc dbe 

Router(config-sbc-dbe)# media-address pool ipv6 5::1:1 5::1:10 nat-mode twice-nat

Router(cfg-sbc-dbe-media-addr-pl-ipv6)# exit

The following example creates a DBE service on an SBC called "mySbc," enters into SBC-DBE configuration mode, and adds IPv6 addresses from 5::1:1 to 5::1:10 to the media address pool:

Router(config)# sbc mySbc dbe 

Router(config-sbc-dbe)# media-address pool ipv6 5::1:1 5::1:10

Router(cfg-sbc-dbe-media-addr-pl-ipv6)# exit

The following example tries to delete IPv6 addresses from 5::1:1 to 5::1:10 in the media address pool before first deactivating the DBE, and receives an error message:

Router(config-sbc-dbe)# no media-address pool ipv6 5::1:1 5::1:10

SBC: Unable to delete a media address whilst the DBE is active.

SBC: Please deactivate the DBE and try again.

Related Commands

media-timeout

To set the maximum time a data border element (DBE) waits after receiving the last media packet on a call and before cleaning up the call resources, use the media-timeout command in SBC-DBE configuration mode. To reset the media-timeout value to the default value of 30 seconds, use the no form of this command.

media-timeout {timeout} first-packet

no media-timeout

Syntax Description

Command Default

The default is 30 seconds if media timeout is not configured.

Command Modes

SBC-DBE configuration (config-sbc-dbe)

Command History

Usage Guidelines

This command sets the maximum time the DBE waits after receiving the last media packet on a call before the DBE determines that the call has ceased and begins to clear up the call resources and to signal the signaling border element (SBE) to do the same. This command is used when the SBE is not able to clear up the calls itself. The normal method for clearing a call is for the SBE to explicitly signal the DBE.

You can halt detection of the media timeout event with the first-packet keyword of the media-timeout command. The first-packet keyword instructs the DBE to wait until it has received the first packet since the call has been established before starting the media timeout timer to start counting the number of seconds for which it has not seen an SBC packet. By the DBE waiting, SBC packets can continue to be forwarded because there is no media timeout yet. After waiting for the first packet and counting the configured number of seconds, then the DBE generates an alert to the SBE.

Use the sbc dbe command to enter into SBC-DBE configuration mode before using the media-timeout command.

Examples

The following example creates a DBE service on an SBC called "mySbc," enters into SBC-DBE configuration mode, and configures the DBE to wait 10 seconds after receiving the last media packet and before cleaning up the call resources:

Router(config)# sbc mySbc dbe

Router(config-sbc-dbe)# media-timeout 10

Router(config-sbc-dbe)# end

The following example shows that the media-timeout command is configured to instruct the DBE to wait until it receives the first SBC packet on the call before it starts to count 1000 seconds, after which the DBE generates a media timeout alert to the SBE.

Router(config)# sbc global dbe

Router(config-sbc-dbe)# media-timeout 1000 first-packet

Router(config-sbc-dbe)# end

Related Commands

outbound

To configure outbound call packets to use a specific Security Parameters Index (SPI) to identify the security association to which an outgoing packet is bound when the Interim Authentication Header (IAH) is enabled, use the outbound command in IAH Key configuration mode. To remove the configuration, use the no form of this command.

outbound spi hex-key

no outbound spi hex-key

Syntax Description

Command Default

None

Command Modes

IAH Key configuration mode (config-sbc-dbe-vdbe-h248-iah)

Command History

Usage Guidelines

The outbound command is used in conjunction with the inbound and transport (session border controller) commands. The three commands are used together to enable Interim Authentication Header (IAH) authentication of inbound and outbound call packets. If you specify a hashing scheme (ah-md5-hmac or ah-sha-hmac authentication) using the transport (session border controller) command, you need to configure incoming and outgoing call packets using both inbound and outbound commands. The inbound and outbound commands are used to specify the Security Parameters Index (SPI) and hex-key.

Both inbound and outbound SPI need to be configured. If authentication is set to MD5 or SHA hashing scheme and only the inbound or outbound SPI key or neither inbound or outbound SPI key is configured, the authentication reverts back to zero authentication and the DBE issues a warning message "Both inbound and outbound keys must be configured to enable authentication." In this event, the DBE sets all fields in the IAH header to zeroes and accepts any IAH without authentication.

Examples

The following example shows you how to configure the IAH to use the HMAC-SHA hashing scheme, set the inbound Security Parameters Index (SPI) to 300 and the outbound SPI to 400, and hash key to "myInboundKey45" and "myOutboundKey89" respectively:

Router(config)# sbc global dbe

Router(config-sbc-dbe)# vdbe global

Router(config-sbc-dbe-vdbe)# h248-version 3

Router(config-sbc-dbe-vdbe)# h248-napt-package napt

Router(config-sbc-dbe-vdbe)# local-port 2970

Router(config-sbc-dbe-vdbe)# control-address h248 ipv4 200.50.1.40

Router(config-sbc-dbe-vdbe)# controller h248 2

Router(config-sbc-dbe-vdbe-h248)# remote-address ipv4 200.50.1.254

Router(config-sbc-dbe-vdbe-h248)# remote-port 2970

Router(config-sbc-dbe-vdbe-h248)# transport tcp interim-auth-header ah-sha-hmac 

Router(config-sbc-dbe-vdbe-h248-iah)# inbound 300 myInboundKey45

Router(config-sbc-dbe-vdbe-h248-iah)# outbound 400 myOutboundKey89

Router(config-sbc-dbe-vdbe-h248)# exit

Router(config-sbc-dbe-vdbe)# attach-controllers

Related Commands

overload-time-threshold

To configure the threshold for media gateway (MG) overload control detection, use the overload-time-threshold command in SBC-DBE configuration mode. To reset the threshold value to its default value of 100 milliseconds, use the no form of this command.

overload-time-threshold {time}

no overload-time-threshold

Syntax Description

Command Default

If a time threshold value is not configured, the default value is 100 milliseconds.

Command Modes

SBC-DBE configuration (config-sbc-dbe)

Command History

Usage Guidelines

The overload-time threshold defines the maximum delay allowed by a session border controller (SBC) that has subscribed to overload control events for the data border element (DBE) to add a new flow.

If the threshold is exceeded, the DBE generates an overload event notification.

If an SBC has subscribed for overload control events, the data border element (DBE) sends an overload event notification to the signaling border element (SBE) for every request to add a new flow whose execution takes longer than this threshold.

Examples

The following example creates a DBE service on an SBC called "mySbc," and configures the overload control detection threshold to be 400 milliseconds. If an SBC has subscribed for overload control events, then the DBE will send an event notification every time a request to add a new flow takes longer than 400 milliseconds to process:

Router(config)# sbc mySbc dbe 
Router(config-sbc-dbe)# overload-time-threshold 400

Router(config-sbc-dbe)# end

package

To configure the data border element (DBE) to interoperate with the media gateway controller (MGC) using the Enhanced Root (eroot) package, use the package command in VDBE configuration mode. The eroot package is a proprietary package for the transport of the location ID and Media Gateway (MG) ID from the SBE. To disable use of the eroot package, use the no form of this command.

package {package-name}

no package {package-name}

Syntax Description

Command Default

If this command is not configured, the eroot package is enabled.

Command Modes

VDBE configuration (config-sbc-dbe-vdbe)

Command History

Examples

The following example enables the eroot package:

Router (config)# sbc mySbc dbe 

Router (config-sbc-dbe)# vdbe

Router (config-sbc-dbe-vdbe)# package eroot

Router (config-sbc-dbe-vdbe)# end

The following example disables the eroot package:

Router (config)# sbc mySbc dbe 

Router (config-sbc-dbe)# vdbe

Router (config-sbc-dbe-vdbe)# no package eroot

Router (config-sbc-dbe-vdbe)# end

package segment max-pdu-size

To configure a data border element (DBE) to use the H.248 Segmentation package and to specify the maximum protocol data unit (PDU) size that the User Datagram Protocol (UDP) should use for H.248 control signaling, use the package segment max-pdu-size command in VDBE configuration mode. To reconfigure the default maximum PDU size of 0 and disable the package, use the no form of the command.

package segment max-pdu-size {size}

no package segment max-pdu-size

Syntax Description

Command Default

The default is 0 if the command is not configured, or the no package segment max-pdu-size command is issued.

Command Modes

VDBE configuration (config-sbc-dbe-vdbe)

Command History

Examples

The following example enables the H.248 Segmentation package and configures the DBE to use 64000 bytes as the maximum PDU size during segmentation:

Router (config)# sbc mySbc dbe 

Router (config-sbc-dbe)# vdbe

Router (config-sbc-dbe-vdbe)# package segment max-pdu-size 64000

Router (config-sbc-dbe-vdbe)# end

Related Commands

port-range (ipv4)

To create a port range associated with an IPv4 media address or a pool of IPv4 media addresses, use the port-range command in the corresponding SBC-DBE media address configuration mode or the SBC-DBE media address pool configuration mode. To delete a port range, use the no form of this command.

port-range {min-port} {max-port} [any | voice | video | signaling | fax]

no port-range {min-port} {max-port}

Syntax Description

Command Default

If the port-range command is not configured, the default min-port value is 16384, the default max-port value is 32767, and the default class of service affinity is any.

Command Modes

SBC-DBE media address configuration (config-sbc-dbe-media-address) or SBC-DBE media address pool configuration (config-sbc-dbe-media-address pool)

Command History

Usage Guidelines

Use the port-range command in SBC-DBE media address configuration mode to specify a port range for a single media address.

Use the media-address ipv4 command to enter SBC-DBE media address configuration mode before entering the port-range command for a single media address.

Use the port-range command in SBC-DBE media address pool configuration mode to specific a port range for a pool of media addresses.

Use the media-address pool ipv4 command to enter SBC-DBE media address pool configuration mode before entering the port-range command for a pool of media addresses.

Examples

The following example creates a new port range between 10000 to 20000 with a service class affinity of voice for a single media address:

Router(config-sbc-dbe-media-address)# port-range 10000 20000 voice

The following example modifies the service class affinity set for the media address by the previous example to any class of service:

Router(config-sbc-dbe-media-address)# port-range 10000 20000 any

The following example deletes the port range set for the media address by the previous example:

Router(config-sbc-dbe-media-address)# no port-range 10000 20000

The following example creates a new port range between 10000 to 20000 with a service class affinity of voice for a pool of media addresses:

Router(config-sbc-dbe-media-address pool)# port-range 10000 20000 voice

The following example modifies the service class affinity set for the pool of media addresses by the previous example to any class of service:

Router(config-sbc-dbe-media-address pool)# port-range 10000 20000 any

The following example deletes the port range set for the pool of media addresses by the previous example:

Router(config-sbc-dbe-media-address pool)# no port-range 10000 20000

Related Commands

port-range (ipv6)

To create a port range associated with a single IPv6 media address or a pool of IPv6 media addresses, use the port-range command in the corresponding SBC-DBE media address IPv6 configuration mode or the SBC-DBE media address pool IPv6 configuration mode. To delete a port range, use the no form of this command.

port-range {min-port} {max-port} signaling

no port-range {min-port} {max-port}

Syntax Description

Command Default

If the port-range command is not configured, the default min-port value is 16384 and the default max-port value is 32767, and the default class of service affinity is signaling.

Command Modes

SBC-DBE media address IPv6 configuration (cfg-sbc-dbe-media-addr-ipv6)

SBC-DBE media address pool IPv6 configuration (cfg-sbc-dbe-media-addr-pl-ipv6)

Command History

Usage Guidelines

This command is used to specify only the signaling class of service for the port range for a single IPv6 media address or for a range or pool of IPv6 media addresses. "Range" means the same as "pool."

The related port-range command is used for a single IPv4 media address or a range or pool of IPv4 media addresses, and can specify voice, video, signaling, fax, and any class of service affinity for the port range.

Use the media-address ipv6 command to enter into SBC-DBE media address IPv6 configuration mode before entering the port-range command for a single IPv6 media address.

Use the media-address pool ipv6 command to enter into SBC-DBE media address pool IPv6 configuration mode before entering the port-range command for a pool of IPv6 media addresses.

Examples

The following example creates a new port range for a single IPv6 media address where the port range values are specified between 10000 and 20000. Use the media-address ipv6 command first to enter into the submode for the specified single IPv6 media address.

Router(config)# sbc mySbc dbe 

Router(config-sbc-dbe)# media-address ipv6 5::1:1

Router(cfg-sbc-dbe-media-addr-ipv6)# port-range 10000 20000 signaling

The following example deletes the port range between 10000 and 20000 for a single IPv6 media address:

Router(config)# sbc mySbc dbe 

Router(config-sbc-dbe)# media-address ipv6 5::1:1

Router(cfg-sbc-dbe-media-addr-ipv6)# no port-range 10000 20000

The following example creates a new port range for an IPv6 media address range or pool. The port range values are between 10000 and 20000. Use the media-address pool ipv6 command first to enter into the submode for a range of IPv6 media addresses.

Router(config)# sbc mySbc dbe 

Router(config-sbc-dbe)# media-address pool ipv6 5::1:1 5::1:10

Router(cfg-sbc-dbe-media-addr-pl-ipv6)# port-range 10000 20000 signaling

The following example deletes the port range between 10000 and 20000 for a range or pool of IPv6 media addresses:

Router(config)# sbc mySbc dbe 

Router(config-sbc-dbe)# media-address pool ipv6 5::1:1 5::1:10

Router(cfg-sbc-dbe-media-addr-pl-ipv6)# no port-range 10000 20000

Related Commands

remote-address ipv4

To configure the IPv4 remote address of the H.248 controller for the signaling border element (SBE), use the remote-address ipv4 command in Controller H.248 configuration mode. To remove the IPv4 remote address, use the no form of this command.

remote-address ipv4 {remote-address}

no remote-address ipv4 {remote-address}

Syntax Description

Command Default

No default behavior or values are available.

Command Modes

Controller H.248 configuration (config-sbc-dbe-vdbe-h248)

Command History

Usage Guidelines

After the remote address is configured, you cannot modify or delete it unless you detach the H.248 controller first by using the no attach-controllers command.

Note This command is invalid for the unified model, where both the SBE and DBE logical entities co-exist on the same network element.

Examples

The following example creates a DBE service on an SBC called "mySbc," enters into SBC-DBE configuration and VDBE configuration modes, creates an H.248 controller with index 1, enters into Controller H.248 configuration mode, and configures the remote address as 1.1.1.1 on the H.248 controller:

Router(config)# sbc mySbc dbe 

Router(config-sbc-dbe)# vdbe 

Router(config-sbc-dbe-vdbe)# controller h248 1

Router(config-sbc-dbe-vdbe-h248)# remote-address ipv4 1.1.1.1

Router(config-sbc-dbe-vdbe-h248)# end

Related Commands

remote-port

To define the port to connect to the signaling border element (SBE) for an H.248 controller, use the remote-port command in Controller H.248 configuration mode. To unconfigure the port to connect to the SBE for an H.248 controller, use the no form of this command.

remote-port {port-num}

no remote-port

Syntax Description

Command Default

If the port is not configured or is configured with the value 0, then the H.248 default port number is 2944.

Command Modes

Controller H.248 configuration (config-sbc-dbe-vdbe-h248)

Command History

Usage Guidelines

This command is invalid for the unified model, where both the SBE and DBE logical entities co-exist on the same network element.

Examples

The following example creates a DBE service on an SBC called "mySbc," enters into SBC-DBE configuration and VDBE configuration modes, enters into Controller H.248 configuration mode, creates an H.248 controller with index 1, and configures the port to 2944 on the H.248 controller with index 1.

Router(config)# sbc mySbc dbe 

Router(config-sbc-dbe)# vdbe 

Router(config-sbc-dbe-vdbe)# controller h248 1

Router(config-sbc-dbe-vdbe-h248)# remote-port 2944

Router(config-sbc-dbe-vdbe-h248)# end

Related Commands

sbc dbe

To create the data border element (DBE) service on a session border controller (SBC) and enter into the SBC-DBE configuration mode, use the sbc dbe command in global configuration mode. To remove the DBE entity, use the no form of this command.

sbc {sbc-name} dbe

no sbc {sbc-name} dbe

Syntax Description

Command Default

No default behavior or values are available.

Command Modes

Global configuration (config)

Command History

Examples

The following example creates a DBE service on an SBC called "mySbc," and enters into SBC-DBE configuration mode:

Router(config)# sbc mySbc dbe

Router(config-sbc-dbe)# end

Related Commands

sbc dump-diagnostics

To dump any in-memory diagnostics currently gathered by the SBC service to either the current default, or the specified file system, use the sbc dump-diagnostics command in privileged EXEC mode. To disable the dump, use the no form of this command.

sbc dump-diagnostics [file-system]

no sbc dump-diagnostics [file-system]

Syntax Description

Command Default

If no file system is specified, the command dumps SBC diagnostics to a default location.

Command Modes

Privileged EXEC (#)

Command History

Usage Guidelines

This command generates the following files:

•ipstrc_buf*.* —Contains binary IPS trace files used by Cisco customer support engineers

•pdtrc_buf*.* — Contains log messages that are stored in the logging buffer (as specified by the debug sbc log-level buffer command)

Examples

The following example dumps in-memory diagnostics to a specified file system called "disk2":

Router# sbc dump-diagnostics disk2:

Related Commands