- 100rel inbound through critical-alert-size
- deact-mode (billing) through group
- h225 address through overload-time-threshold
- packetcable-em transport radius through show monitor event-trace sbc ha
- show platform hardware qfp active feature sbc sfx through show sbc sbe media-gateways
- show sbc sbe policy-failure-stats through xml (billing)
- deact-mode (billing)
- deact-mode (XML Billing)
- deactivation-mode (session border controller)
- debug condition vrf
- debug ip bgp igp-metric ignore
- debug ip bgp route-server
- debug ip multicast topology
- de bug ip wccp
- debug platform hardware qfp active feature wccp
- debug platform hardware qfp feature sbc
- debug platform software wccp
- debug sbc alarm-filter
- debug sbc alarm-log-level
- debug sbc asr log-level filter
- debug sbc correlation-logs filter
- debug sbc errors
- debug sbc events
- debug sbc filter
- debug sbc filter billing_id
- debug sbc filter bm
- debug sbc filter cac
- debug sbc filter call
- debug sbc filter (session border controller)
- debug sbc ha
- debug sbc info
- debug sbc ips (session border controller)
- debug sbc log-level console
- debug sbc log-level file
- debug sbc logging
- debug sbc mem-trace dump
- debug sbc nbase
- debug sbc off
- debug sbc pd filter component
- debug sbc pd filter context
- debug sbc pd filter product
- debug sbc pd log-level
- debug vrf
- default-port-limit
- delegate-profile
- delegate-registration
- description (route server context)
- description (session border controller)
- description (sip-opt)
- dial-plan-suffix
- diameter
- div-address
- div-address (header)
- domain-name
- dscp
- dst-address
- dst-address (editor)
- dst-adjacency
- dtmf-duration (session border controller)
- dtmf disable sip
- dtmf sip
- duration
- early-media-deny
- early-media-timeout
- early-media-type
- edit-cic
- edit-src
- edit
- editor-list
- editor-type
- editor
- entry
- entry (enum)
- enum
- error-profile
- exit-if-vnet
- exit-route-server-context
- exit-vrf-list
- expires-header
- fast-register-interval
- fast-register disable
- filename (session border controller)
- first-cac-scope
- first-cac-table
- first-call-routing-table
- first-inbound-na-table
- first-outbound-na-table
- first-reg-routing-table
- flipped-interval (XML Billing)
- flipped-size (XML Billing)
- fmtp (codec variant)
- fmtp (session border controller)
- force-signaling-peer
- g107a-factor
- g107 bpl
- g107 ie
- generic-stream callee
- generic-stream caller
- generic-stream media-type
- generic-stream branch
- global
- group (session border controller)
deact-mode (billing)
To configure the deactivate mode for the billing method, use the deact-mode command in the packetcable-em configuration mode. To disable the deactivate mode, use the no form of this command.
Syntax Description
Command Default
Command Modes
Packet-cable em configuration (config-sbc-sbe-billing-packetcable-em)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to delay the deactivation of the billing method:
Related Commands
deact-mode (XML Billing)
To configure the deactivate mode for the XML billing method, use the deact-mode command in the SBE billing XML configuration mode. The deact-mode command defines the state after which the billing method will be deactivated. To disable the deactivate mode, use the no form of this command.
deact-mode {normal | quiesce | abort}
Syntax Description
Command Default
Command Modes
SBE billing XML configuration (config-sbc-sbe-billing-xml)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Routers. |
Usage Guidelines
The XML billing method can be deactivated forcefully using the deact-mode command from SBE billing XML configuration mode.
Since the calls are still in progress, it is important to bill the calls that are completed before the XML billing method is deactivated. To bill the CDRs for the existing calls before deactivating the XMl billing method, use the deact-mode normal command.
As an option to wait for the calls that have still not ended, and to build the CDRs for the existing calls as well as the calls that are still in progress, use the deact-mode quiesce command.
To immediately abort the XML billing method without billing the CDRs, use the deact-mode abort command.
Examples
The following example shows how to set the deactivation mode to normal. This will process the CDRs for the existing calls:
The following example shows how to bill CDRs for the existing calls and will continue to build the CDRs for the calls that are still in progress:
The following example shows how to deactivate the XML billing method without building the CDRs:
Related Commands
|
|
|
|---|---|
Configures the billing method as XML for the Billing Manager. |
|
Configures the time at which long duration records are checked. |
deactivation-mode (session border controller)
To specify the action to take upon DBE or SBE deactivation, use the deactivation-mode command in the appropriate configuration mode. To revert to the default value, use the no form of this command.
Syntax Description
Command Default
Command Modes
SBC-DBE configuration (config-sbc-dbe)
SBE configuration (config-sbc-sbe)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
|
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to set the DBE to deactivate in quiesce mode to prepare the device for hardware maintenance:
Related Commands
|
|
|
|---|---|
Creates the DBE service on a SBC and enters into the DBE-SBE configuration mode. |
|
Initiates the DBE service of the Session Border Controller (SBC). |
debug condition vrf
To limit debug output to a specific Virtual Routing and Forwarding (VRF) instance, use the debug condition vrf command in privileged EXEC mode. To remove the debug condition, use the undebug version of the command.
undebug condition vrf vrf-name
Syntax Description
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Use this command to limit debug output to a single VRF.
Note
EIGRP does not support the EIGRP does not support the debug condition vrf command.
Examples
The following example shows how to limit debugging output to VRF red:
Related Commands
|
|
|
|---|---|
debug ip bgp igp-metric ignore
To display information related to the system ignoring the Interior Gateway Protocol (IGP) metric during best path selection, use the debug ip bgp igp-metric ignore command in privileged EXEC mode. To disable such debugging output, use the no form of the command.
debug ip bgp igp-metric ignore
no debug ip bgp igp-metric ignore
Syntax Description
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
You might use this command if the path you expected to be chosen as the best path at the shadow RR was not chosen as such. That could be because the bgp bestpath igp-metric ignore command makes the best path algorithm choose the same best path as the primary RR if they are not co-located.
Examples
The following example turns on debugging of events related to the system ignoring the IGP metric during bestpath selection:
Related Commands
|
|
|
|---|---|
Specifies that the system ignore the Interior Gateway Protocol (IGP) metric during best path selection. |
debug ip bgp route-server
To turn on debugging for a BGP route server, use the debug ip bgp route-server command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ip bgp route-server { client | context | event | import | policy } [ detail ]
no debug ip bgp route-server { client | context | event | import | policy } [ detail ]
Syntax Description
Displays information about route server events, such as importing into the virtual RS table. |
|
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Use this command to turn on debugging of a BGP router server.
Examples
In the following example, BGP route server client debugging is turned on:
Related Commands
|
|
|
|---|---|
Specifies on a BGP route server that a neighbor is a route server client. |
|
Creates a route-server context in order to provide flexible policy handling for a BGP route server. |
debug ip multicast topology
To enable debugging output for IP multicast stream topology creation events, deletion events, and IP multicast stream access control list (ACL) matching events, use the debug ip multicast topology command in privileged EXEC mode. To disable debugging output, use the no form of this command.
no debug ip multicast topology
Syntax Description
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Use this command when IP multicast stream topology creation, IP multicast stream topology deletion, or IP multicast stream ACL matching appears not to be functioning.
Examples
The following example shows how to enable debugging output for IP multicast stream topology creation events, IP multicast stream topology deletion events, and IP multicast stream ACL matching events:
Related Commands
|
|
|
|---|---|
Associates a multicast topology with a multicast group with a specific mroute entry. |
|
debug ip wccp
To display information about Web Cache Control Protocol (WCCP) services, use the debug ip wccp command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ip wccp { default | vrf vrf-name { events | packets [ control ]} | events | packets [ bypass | control | redirect ] | platform | subblocks }
no debug ip wccp { default | vrf vrf-name { events | packets [ control ]} | events | packets [ bypass | control | redirect ] | platform | subblocks }
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
This command was introduced. This command replaces the debug ip wccp packets and debug ip wccp events commands. |
|
This command was integrated into Cisco IOS Release 12.2(33)SRE. |
|
Usage Guidelines
When the vrf keyword is not used, the command displays debug information about all WCCP services on the router. The default keyword is used to specify default WCCP services.
Examples
The following is sample output from the debug ip wccp events command when a Cisco Cache Engine is added to the list of available Web caches:
The following is sample output from the debug ip wccp packets command. The router is sending keepalive packets to the Cisco Cache Engines at 192.168.25.4 and 192.168.25.3. Each keepalive packet has an identification number associated with it. When the Cisco Cache Engine receives a keepalive packet from the router, it sends a reply with the identification number back to the router.
Related Commands
debug platform hardware qfp active feature wccp
To enable debug logging for the Web Cache Communication Protocol (WCCP) client in the Cisco Quantum Flow Processor (QFP), use the debug platform hardware qfp active feature wccp command in privileged EXEC mode. To disable WCCP QFP debug logging, use the no form of this command.
debug platform hardware qfp active feature wccp {{ client | lib-client { all | error | info | trace | warning }} | datapath all }
no debug platform hardware qfp active feature wccp {{ client | lib-client { all | error | info | trace | warning }} | datapath all }
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
When the debug platform hardware qfp active feature wccp command is configured, QFP client debugs are enabled and can be collected from the forwarding processor (FP) from the file cpp_cp_F0-0.log.
When the debug platform hardware qfp active feature wccp lib-client all command is configured, QFP lib-client debugs are enabled and can be collected from the FP from the file fman-fp_F0-0.log.
When the debug platform hardware qfp active feature wccp datapath all command is configured, QFP datapath debugs are enabled and can be collected from the FP from the file cpp_cp-F0-0.log.
Examples
The following is sample output from the debug platform hardware qfp active feature wccp command:
The sequence of messages repeats for each access control entry (ACE) of a merged access control list (ACL):
WCCP redirection is configured on an interface:
Debug messages appear for each ACE of the merged ACL for a service group:
Redirection is removed from an interface:
A service group is unconfigured:
The following is sample output from the debug platform hardware qfp active feature wccp lib-client all command:
A WCCP service group is configured:
The set of debug messages repeats for each ACE of the merged ACL of the WCCP service group:
WCCP redirection is configured on an interface:
WCCP is unconfigured on an interface:
A WCCP service group is unconfigured:
The debug messages repeat for each ACE of the merged ACL for the WCCP service group:
The following is sample output from the debug platform hardware qfp active feature wccp datapath all command:
A packet is successfully redirected:
Related Commands
debug platform hardware qfp feature sbc
To enable debug logging for signaling border element (SBE) or the data border element (DBE) logs in the Cisco QuantumFlow Processor (QFP), use the debug platform hardware qfp feature sbc command in Privileged EXEC mode. To disable this form of debugging, use the no form of this command.
debug platform hardware qfp {active | standby} feature sbc {sbe {pfilter | sfx {datapath}} | dbe {client {all | clear | error | informational | trace | warning} | datapath {all | drop | dtmf | error | events | find | latch | proxy | rtcp}}
no debug platform hardware qfp {active | standby} feature sbc {sbe {pfilter | sfx {datapath}} | dbe {client {all | clear | error | informational | trace | warning} | datapath {all | drop | dtmf | error | events | find | latch | proxy | rtcp}}
Syntax Description
Command Default
Command Modes
Command History
|
|
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
The output of the debugs is stored in the harddisk:tracelog/ directory.
Examples
The following example turns on debugging of SBE logs for SIP fast-register (SFX) datapath messages residing on the active processor in the Cisco QuantumFlow Processor (QFP):
The following example turns on debugging of DBE logs for datapath DTMF debugs residing on the active processor in the Cisco QuantumFlow Processor (QFP):
Related Commands
debug platform software wccp
To enable Web Cache Control Protocol (WCCP) platform debug messages, use the debug platform software wccp command in privileged EXEC mode. To disable WCCP platform debug messages, use the no form of this command.
debug platform software wccp { configuration | counters | detail | messages }
no debug platform software wccp { configuration | counters | detail | messages }
Syntax Description
Enables detailed debugs for all WCCP related configurations. |
|
Enables debugs related to type definition language (TDL) messages being exchanged. |
Command Default
Command Modes
Command History
|
|
|
|---|---|
Examples
The following is sample output from the debug platform software wccp configuration command:
A WCCP service is configured on an interface:
A WCCP service is removed from an interface:
A WCCP service group is unconfigured:
The following is sample output from debug platform software wccp messages command:
A WCCP service is removed from an interface:
A WCCP service is removed from an interface:
A WCCP service group is unconfigured:
The following is sample output from the debug platform software wccp detail command:
The debug messages appear for each access control entry (ACE) of the merged access control list (ACL) for the service group:
A WCCP service group is unconfigured:
The following is sample output from the debug platform software wccp counters command.
Statistics are collected for the first time on a WCCP-enabled interface:
The following debug messages are displayed every 10 seconds:
Related Commands
debug sbc alarm-filter
To configure the alarm types for which alarm logs must be generated, use the debug sbc alarm-filter command in the privileged EXEC mode. To unconfigure generation of alarm logs for a specified alarm type, use the no form of this command.
debug sbc sbc-name alarm-filter alarm-type
no debug sbc sbc-name alarm-filter alarm-type
Syntax Description
Command Default
The default is that alarm logs are generated for all alarm types.
Command Modes
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
Run this command for each alarm type for which you want logs to be generated. You can use the show debugging command to display the debugging settings created by running the debug sbc alarm-log-level command.
Examples
The following example shows how the debug sbc alarm-filter command is used to configure the generation of alarm logs for call audit congestion alarms:
The following example shows how the show debugging command displays the configuration settings created by running the debug sbc alarm-filter command. For example:
Related Commands
debug sbc alarm-log-level
To configure the output mode and the alarm severity level at which alarms must be logged, use the debug sbc alarm-log-level command in the privileged EXEC mode. To unconfigure the display and storage of alarm logs, use the no form of this command.
debug sbc sbc-name alarm-log-level [ buffer | console] severity-level
no debug sbc sbc-name alarm-log-level [ buffer | console]
Syntax Description
Command Default
This command applies to all the alarms for which you configure logging by running the debug sbc alarm-filter command.
Command Modes
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
If you specify buffer as the output mode for the alarm logs, note that the logs are moved to a file in the specified file system when the capacity of the buffer is exceeded. The size of a single log file created on the file system cannot exceed 2 MB. When the size of a particular log file reaches 2 MB, a new file is created and logging output is stored in the new file. Use the show debugging command to display the debug settings created by running the debug sbc alarm-log-level command.
Examples
In the following example, the debug sbc alarm-log-level command is run twice. The first run of this command is used to specify that logs must be generated for alarms that are of severity 20 or higher and that these logs must be stored in the buffer. The second run of the command is used to specify that logs must be generated for alarms that are of severity 40 or higher and that these logs must be displayed on the console.
Router# debug sbc MySbc alarm-log-level console 40
The show debugging command shows the configuration settings created by running the debug sbc alarm-log-level command. For example:
Related Commands
debug sbc asr log-level filter
To set the problem determination (PD) log level at which filtering occurs, use the debug sbc asr log-level filter command in the Exec mode. To disable this form of debugging, use the no form of this command.
debug sbc asr log-level filter level
no debug sbc asr log-level filter level
Syntax Description
Command Default
Command Modes
Command History
|
|
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
Logs with severity greater than the specified threshold, matching the include/exclude filter set, or the log group filter are output regardless of the configured unconditional log levels for the buffer, file and console output streams. They are output to all three of those streams.
Examples
The following examples show various output for this command:
Related Commands
|
|
|
|---|---|
Turns on different logs from the problem determination (PD) filters. |
|
Turns on problem determination (PD) filter product group logs. |
|
debug sbc correlation-logs filter
To enable the correlation-logs filter, use the debug sbc correlation-logs filter command in the privileged EXEC mode. To disable the correlation-logs filter, use the no form of this command.
debug sbc sbc-name correlation-logs filter filter-name [ pdtrc-log-level value ]
no debug sbc sbc-name correlation-logs filter filter-name
Syntax Description
(Optional) Specifies the value of the pdtrc log level. The range is from 0 to 100. The default is 60. |
Command Default
Command Modes
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
Use the show debugging command to display the debug logs, filters, and log levels.
Examples
The following example shows the various filters available for filtering the correlation logs:
The following example shows the filtering of correlation logs based on the adjacency parameter:
The following example shows the filtering of correlation logs based on the remote signalling address parameter:
Related Commands
|
|
|
|---|---|
debug sbc errors
To debug sbc service errors, use the debug sbc errors command in the Exec mode. To disable this form of debugging, use the no form of this command.
Syntax Description
Command Default
Command Modes
Command History
|
|
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
Examples
The following command turns on sbc error debugging:
Related Commands
|
|
|
|---|---|
debug sbc events
To debug sbc service events, use the debug sbc events command in privileged EXEC mode. To disable this form of debugging, use the no form of this command.
Syntax Description
Command Default
Command Modes
Command History
|
|
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
Examples
The following command turns on debugging for sbc events:
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
Logs showing the flow of control through the session border controller (SBC) components. |
|
Command Default
Command Modes
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
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.
NoteThe debug logs are only output if the appropriate filter keywords have been specified. 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:
- 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 include the following keywords:
billing, call, media, overview, protocol
Examples
The following example shows all debug logs for the H.248 control channel to the SBE on an SBC called “mySbc”:
The following example shows all debug logs relating to media flows on an SBC called “mySbc”:
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:
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:
Related Commands
debug sbc filter billing_id
To print log entries to the console and file based on a billing_id context, use the debug sbc filter billing_id command in privileged EXEC mode. To disable this form of debugging, use the no form of this command.
debug sbc sbc-name filter billing_id billing_id
no debug sbc sbc-name filter billing_id billing_id
Syntax Description
Command Default
Command Modes
Command History
|
|
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
Examples
The following command prints log entries to the console and file based on a billing_id context:
Related Commands
debug sbc filter bm
To print log entries to the console and file from the bandwidth manager component group, use the debug sbc filter bm command in privileged EXEC mode. To disable this form of debugging, use the no form of this command.
no debug sbc sbc-name filter bm
Syntax Description
Command Default
Command Modes
Command History
|
|
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
Examples
The following command prints log entries to the console and file from the bandwidth manager component group:
Related Commands
debug sbc filter cac
To print log entries to the console and file from the call admission control (CAC) component group, use the debug sbc filter cac command in privileged EXEC mode. To disable this form of debugging, use the no form of this command.
no debug sbc sbc-name filter cac
Syntax Description
Command Default
Command Modes
Command History
|
|
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
Examples
The following command prints log entries to the console and file from the CAC component group:
Related Commands
debug sbc filter call
To print log entries to the console and file from the call product group, use the debug sbc filter call command in privileged EXEC mode. To disable this form of debugging, use the no form of this command.
debug sbc sbc-name filter call
no debug sbc sbc-name filter call
Syntax Description
Command Default
Command Modes
Command History
|
|
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
Examples
The following command prints log entries to the console and file from the call product group:
Related Commands
debug sbc filter (session border controller)
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
Logs showing the flow of control through the Session Border Controller (SBC) components. |
|
Command Default
Command Modes
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
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.
NoteThe debug logs are only output if the appropriate filter keywords have been specified. 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:
- 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 include the following keywords:
billing, call, media, overview, protocol
Examples
The following example shows all debug logs for the H.248 control channel to the SBE on an SBC called “mySbc”:
The following example shows all debug logs relating to media flows on an SBC called “mySbc”:
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:
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:
The following command prints log entries to the console and file based on an adjacency context:
The following command prints log entries to the console and file from the billing product group:
The following command prints log entries to the console and file from the bandwidth manager component group:
The following command prints log entries to the console and file from the ICC component group:
The following command prints log entries to the console and file from the h323 component group:
The following command prints log entries to the console and file from the ICC component group:
The following command prints log entries to the console and file based on an ipv4 address context:
The following command prints log entries to the console and file from the media product group:
The following command prints log entries to the console and file from the media product group:
The following command prints log entries to the console and file from the media product group:
The following command prints log entries to the console and file from the media product group:
The following command prints log entries to the console and file from the MGM component group:
The following command prints log entries to the console and file based on a number context:
The following command prints log entries to the console and file based on a number context:
The following command prints log entries to the console and file from the overview product group:
The following command prints log entries to the console and file from the overview product group:
The following command prints log entries to the console and file from the protocol product group:
The following command prints log entries to the console and file from the RADIUS component group:
The following command prints log entries to the console and file from the routing component group:
The following command prints log entries to the console and file from the SIP component group:
Related Commands
debug sbc ha
To turn on debugging for Session Border Controller high availability, use the debug sbc ha command in privileged EXEC mode. To disable this form of debugging, use the no form of this command.
Syntax Description
Command Default
Command Modes
Command History
|
|
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
Examples
The following command turns on debugging for sbc high availability:
Related Commands
|
|
|
|---|---|
debug sbc info
To debug sbc services information, use the debug sbc info command in the Exec mode. To disable this form of debugging, use the no form of this command.
Syntax Description
Command Default
Command Modes
Command History
|
|
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
Examples
The following command turns on debugging for sbc information:
Related Commands
|
|
|
|---|---|
debug sbc ips (session border controller)
To turn on IPS tracing (giving details of inter-component signals flowing between the internal components of the Session Border Controller (SBC) process), use the debug sbc ips command in the Exec mode. To disable this form of debugging, use the no form of this command.
debug sbc sbc-name ips {file | in-memory}
no debug sbc sbc-name ips {file | in-memory}
Syntax Description
Command Default
Command Modes
Command History
|
|
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
This command provides details of inter-component signals flowing between the internal components of the SBC process. Events should be logged on IPS trace file for further debugging.
Examples
The following command turns on IPS tracing:
Related Commands
|
|
|
|---|---|
Turns on different logs from the problem determination (PD) filters. |
|
Turns on problem determination (PD) filter product group logs. |
|
debug sbc log-level console
To set the console logging level, use the debug sbc log-level console command in Exec mode. To disable this form of debugging, use the no form of this command.
debug sbc name log-level console level
no debug sbc name log-level console level
Syntax Description
This is the name of the Session Border Controller (SBC) service. |
|
The level to set. 0 gives all pd logging and 100 gives none. The log levels are defined as follows: 30+ Verbose operational events |
Command Default
Command Modes
Command History
|
|
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
This command configures the display of the most serious logs directly to the console. Note that when you run the debug sbc name log-level console 0 command, a large number of log messages are generated. This could cause an increase in the response time of the system. To limit the rate of messages logged per second, use the logging rate-limit console command in global configuration mode.
Examples
The following command sets the log level for fatal errors to the console at 90:
Related Commands
|
|
|
|---|---|
debug sbc log-level file
To set the file logging level, use the debug sbc log-level file command in the Exec mode. To disable this form of debugging, use the no form of this command.
debug sbc name log-level file level
no debug sbc name log-level file level
Syntax Description
This is the name of the Session Border Controller (SBC) service. |
|
The level to set. 0 gives all pd logging and 100 gives none. The log levels are defined as follows: 30+ Verbose operational events |
Command Default
Command Modes
Command History
|
|
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
Examples
The following command sets the log level to send to file to 60:
Related Commands
|
|
|
|---|---|
debug sbc logging
To debug SBC logging information, use the debug sbc logging command in the Exec mode. To disable this form of debugging, use the no form of this command.
Syntax Description
Command Default
Command Modes
Command History
|
|
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
Examples
The following command turns on debugging for sbc information:
Related Commands
|
|
|
|---|---|
Turns on different logs from the problem determination (PD) filters. |
|
Turns on problem determination (PD) filter product group logs. |
|
debug sbc mem-trace dump
To dump current memory usage statistics to file, use the debug sbc mem-trace dump command in the Exec mode. To disable printing to the terminal, use the no form of this command.
debug sbc sbc-name mem-trace dump
no debug sbc sbc-name mem-trace dump
Syntax Description
Command Default
Command Modes
Command History
|
|
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
Examples
The following example dumps current memory usage statistics to file:
Related Commands
|
|
|
|---|---|
Turns on different logs from the problem determination (PD) filters. |
|
Turns on problem determination (PD) filter product group logs. |
|
debug sbc nbase
To enable printing to the terminal for the debug sbc log-level console command, use the debug sbc nbase command in the Exec mode. To disable printing to the terminal, use the no form of this command.
Syntax Description
Command Default
Command Modes
Command History
|
|
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
Examples
The following command enables printing to the terminal for the debug sbc log-level console command:
Related Commands
|
|
|
|---|---|
Turns on different logs from the problem determination (PD) filters. |
|
Turns on problem determination (PD) filter product group logs. |
|
debug sbc off
To turn off all sbc filters and set the log-level back to default (63), use the debug sbc off command in the Exec mode. To disable this form of debugging, use the no form of this command.
Syntax Description
Command Default
Command Modes
Command History
|
|
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
Examples
The following command turns on debugging for sbc information:
Related Commands
|
|
|
|---|---|
Turns on problem determination (PD) filter product group logs. |
|
debug sbc pd filter component
To turn on problem determination (PD) filter components, use the debug sbc pd command in the Exec mode. To disable this form of debugging, use the no form of this command.
debug sbc sbc-name pd filter component [bm | cac | control | h323 | hm | icc | mgm | radius | routing | sip]
no debug sbc sbc-namee pd filter component [bm | cac | control | h323 | hm | icc | mgm | radius | routing | sip]
Syntax Description
Command Default
Command Modes
Command History
|
|
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
This command provides details of inter-component signals flowing between the internal components of the SBC process. Events should be logged on IPS trace file for further debugging.
Examples
The following command turns on IPS tracing:
Related Commands
|
|
|
|---|---|
Turns on different logs from the problem determination (PD) filters. |
|
Turns on problem determination (PD) filter product group logs. |
|
debug sbc pd filter context
To turn on different logs from the problem determination (PD) filters, use the debug sbc pd filter context command in the Exec mode. To disable this form of debugging, use the no form of this command.
debug sbc sbc-name pd filter context [adjacency name name| billing_id name | ipv4 name | number name]
no debug sbc sbc-name pd filter context [adjacency name name| billing_id name | ipv4 name | number name]
Syntax Description
Command Default
Command Modes
Command History
|
|
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
This command provides details of inter-component signals flowing between the internal components of the SBC process. Events should be logged on IPS trace file for further debugging.
Examples
The following command turns on the adjacency log filter:
Related Commands
|
|
|
|---|---|
Turns on different logs from the problem determination (PD) filters. |
|
Turns on problem determination (PD) filter product group logs. |
|
debug sbc pd filter product
To turn on problem determination (PD) filter product group logs, use the debug sbc pd filter product command in the Exec mode. To disable this form of debugging, use the no form of this command.
debug sbc sbc-name pd filter context [billing | call | media | overview | protocol]
no debug sbc sbc-name pd filter context [adjacency | billing_id | ipv4 | number]
Syntax Description
Command Default
Command Modes
Command History
|
|
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
This command provides details of inter-component signals flowing between the internal components of the SBC process. Events should be logged on IPS trace file for further debugging.
Examples
The following command turns on the logs from the protocol product group:
Related Commands
|
|
|
|---|---|
Turns on different logs from the problem determination (PD) filters. |
|
Turns on problem determination (PD) filter product group logs. |
|
debug sbc pd log-level
To set the file logging level, use the debug sbc pd log-level command in the Exec mode. To disable this form of debugging, use the no form of this command.
debug sbc sbc-name pd log-level {console level | file level | filter level}
no debug sbc sbc-name pd log-level {console level | file level | filter level}
Syntax Description
Command Default
Command Modes
Command History
|
|
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
Examples
The following command sets the log level to send to file to 60:
Related Commands
|
|
|
|---|---|
Turns on different logs from the problem determination (PD) filters. |
|
Turns on problem determination (PD) filter product group logs. |
|
debug vrf
To get debugging information on virtual routing and forwarding (VRF) instances, use the debug vrf command in privileged EXEC mode. To turn off the debug output, use the undebug version of the command.
debug vrf { create | delete | error | ha | initialization | interface | ipv4 | ipv6 | issu | lock | lookup | mpls | selection }
undebug vrf { create | delete | error | ha | initialization | interface | ipv4 | ipv6 | issu | lock | lookup | mpls | selection }
Syntax Description
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Examples
The following example shows how to turn on debugging of VRF interface assignment:
Related Commands
|
|
|
|---|---|
default-port-limit
To enter the mode for configuring the default event limits for the ports of a given address, use the default-port-limit command in the SBE blacklist IPv4 configuration mode. To remove the event limits set, use the no form of this command.
Syntax Description
Command Default
Command Modes
SBE blacklist IPv4 configuration (config-sbc-sbe-blacklist-ipv4)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how the blacklist default-port-limit command is used to enter the mode for configuring the default event limits for the ports of the source address 123.123.2.2:
Related Commands
delegate-profile
To configure a delegate client registration profile that can be applied to a delegate subscriber, use the delegate-profile command in SBE configuration mode. To remove a delegate client registration profile, use the no delegate-profile command.
delegate-profile {profile name}
no delegate-profile {profile name}
Syntax Description
This is the name of the delegate client registration profile that can be applied to a delegate subscriber. The profile name is a string field of 24 characters maximum length. |
Command Default
Command Modes
SBE configuration (config-sbc-sbe)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
After a delegate profile is configured, the following profile parameters may optionally be configured:
Before configuring provisioned delegate registration, you need to configure a delegate registration profile and a SIP contact for a subscriber for whom a subscriber detail table exists, and then you can configure delegate registration for the subscriber. See the Examples section.
Delegate registration is done underneath the SBE configuration for globally unique subscribers.
Examples
The following example configures a delegate registration profile that can be applied to a delegate registration subscriber:
The following example configures a SIP contact for a subscriber, for whom a subscriber detail table exists, and for whom, after the SIP contact is configured, Provisioned Delegate Registration can be configured:
The following example configures a delegate registration aor= sip:bob@isp.example
Related Commands
delegate-registration
To configure provisioned delegate registration for a specific delegate client, use the delegate-registration command in subscriber-entry configuration mode. To remove provisioned delegate registration for a specific delegate client, use the no delegate-registration command.
delegate-registration {hostname}
no delegate-registration {hostname}
Syntax Description
Command Default
Command Modes
subscriber-entry configuration mode (config-sbc-sbe-subscriber-entry)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
This command allows you to configure a provisioned delegate registration for a specific delegate client. While in the subscriber-delegate configuration mode, you typically configure adjacency and profile, as shown in the examples section.
Before configuring provisioned delegate registration, you need to configure a delegate registration profile, a SIP contact for a subscriber for whom a subscriber detail table exists, and then you can configure delegate registration for the subscriber. See the Examples section.
Examples
The following example configures a delegate registration aor= sip:bob@isp.example:
The following example configures a delegate registration profile that can be applied to a delegate registration subscriber.
The following example configures a SIP contact for a subscriber, for whom a subscriber detail table exists, and for whom, after the SIP contact is configured, delegate registration can be configured:
The following example configures a delegate registration for a specified client device address location, after the SIP contact information has been configured:
Related Commands
description (route server context)
To specify a description for a BGP route server context, use the description command in route server context configuration mode. To remove the description, use the no form of this command.
Syntax Description
Description of the route server context. The string can be up to 80 characters long. |
Command Default
Command Modes
Route server context configuration (config-router-rsctx)
Command History
|
|
|
|---|---|
Usage Guidelines
Create a route server context if you want your BGP route server to support customized, flexible policies. The routes needing flexible policy handling are selected for import into a route server context by an import map that you configure. The import map references a route map, where the actual policy is defined.
The description command allows an optional description of a route server context to remind you of the purpose of the context or policy, for example. This is more user-friendly and scannable than trying to interpret the route map commands when looking at a configuration file or show output.
Examples
In the following example, the description is a user-friendly way to see the purpose of the context, without having to interpret the import map and route map:
Related Commands
|
|
|
|---|---|
Creates a route-server context in order to provide flexible policy handling for a BGP route server. |
description (session border controller)
To configure descriptive text for a policy set, an adjacency, a source and its event limits, a number analysis table, a stream list, or an administrative domain, use the description command in the appropriate configuration mode. To remove this configuration, use the no form of this command.
Syntax Description
Command Default
Command Modes
Adjacency H.323 configuration (config-sbc-sbe-adj-h323)
Adjacency SIP configuration (config-sbc-sbe-adj-sip)
Routing policy table (config-sbc-sbe-rtgpolicy)
CAC policy-set configuration (config-sbc-sbe-cacpolicy)
CAC table configuration (config-sbc-sbe-cacpolicy-cactable)
NA routing table configuration (config-sbc-sbe-rtgpolicy-natable)
RTG routing table configuration (config-sbc-sbe-rtgpolicy-rtgtable)
SBE blacklist configuration (config-sbc-sbe-blacklist)
SIP header configuration (config-sbc-sbe-sip-hdr)
SIP method profile configuration (config-sbc-sbe-sip-mth)
Administrative domain configuration (config-sbc-sbe-ad)
Stream list configuration (config-sbc-sbe-stream-list)
SIP Body Editor configuration (config-sbc-sbe-mep-bdy)
SIP Method Editor configuration (config-sbc-sbe-mep-mth)
SIP Option Editor configuration (config-sbc-sbe-mep-opt)
SIP Header Editor configuration (config-sbc-sbe-mep-hdr)
SIP Parameter Editor configuration (config-sbc-sbe-mep-prm)
Command History
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of the modes required to run the command.
The use of special characters, such as backslash (\), and a three or larger digit for character settings such as description , results in incorrect translation.
Examples
The following example shows how to configure the h323ToIsp42 H.323 adjacency to use the description test adjacency:
The following example shows how to set the SipToIsp42 SIP adjacency to use the description test adjacency:
Router(config-sbc-sbe-adj-sip)# description test adjacency
The following example shows how to create a description for the MyNaTable number analysis table with entries that match the entire dialed number:
The following example shows how to create an empty policy set, identified by the number 1, on mySbc:
The following example shows how to set the description of the MyCacTable admission control table:
The following example shows how to create a description for the MyNaTable number analysis table with entries that match the start of the dialed number:
The following example shows how to add a description for a specific source IP address:
The following example shows how to create an empty policy set, identified by the number 1, on mySbc:
The following example shows how to add a description for an administrative domain:
The following example shows how to add a description for a stream list:
The following examples shows how to add a description to the header, body, option, parameter, and method editors.
Router(config-sbc-sbe-mep-prm)# description “The Parameter Editor”
Router(config-sbc-sbe-mep-hdr)# description “The Header Editor”
Router(config-sbc-sbe-mep-opt)# description “The Option Editor”
Router(config-sbc-sbe-mep-bdy)# description “The Body Editor”
Router(config-sbc-sbe-mep-mth)# description “The Method Editor”
description (sip-opt)
To set the description for the profile, use the description command in SIP option mode. Use the no form of this command to remove description from this profile.
Syntax Description
The description of the profile. The maximum number of characters is 80. |
Command Default
Command Modes
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command:
Examples
The following example shows how to set the description for the profile.
dial-plan-suffix
To configure the dial plan suffix used for the ENUM query, use the dial-plan-suffix command in ENUM entry configuration mode. To return the dial plan suffix to the default value, use the no form of this command.
Syntax Description
Command Default
Command Modes
ENUM entry configuration (config-sbc-sbe-enum-entry)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to configure the dial plan suffix used for the ENUM query:
Related Commands
diameter
To enable the Diameter protocol on a node and enter the Diameter configuration mode, use the diameter command in SBE configuration mode. To disable the Diameter protocol on a node, use the no form of this command.
Syntax Description
Command Default
Command Modes
SBE configuration (config-sbc-sbe)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Diameter is an Authentication Authorization Accounting (AAA) protocol and is an enhanced version of the RADIUS (Remote Authentication Dial-In User Service) protocol. Diameter is the protocol of choice for the next generation network IP Multimedia Subsystem (IMS) developed by 3rd Generation Partnership Project (3GPP).
Examples
The following example shows how to enable the Diameter protocol on a node and enter the diameter configuration mode:
Related Commands
div-address
To enter the diverted-by address mode to set the priority of the header or headers from which to derive a diverted-by address (inbound only), use the div-address command in SIP header configuration mode. To exit the diverted-by address mode, use the no form of this command or the exit command.
Syntax Description
Command Default
Command Modes
SIP header configuration (config-sbc-sbe-sip-hdr)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section that follows shows the hierarchy of modes required to run the command.
This command puts you in the diverted-by address mode where you use the header-prio header-name command to set the priority of the header or headers from which a diverted-by address is derived.
NoteThe header list is for inbound calls only. The header list is for inbound calls only.
Examples
The following example shows how to enter the diverted-by address mode:
Related Commands
div-address (header)
To enter the Diverted-by address mode and set the priority of the header or headers from which to derive a diverted-by address (inbound only), use the div-address command in the Session Initiation Protocol (SIP) Header Editor configuration mode. To remove the priority list of headers, use the no form of this command.
Syntax Description
Command Default
Command Modes
SIP Header Editor configuration (config-sbc-sbe-mep-hdr)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
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.
This command puts you in the Diverted-by address mode from where you can use the header-prio header-name command to set the priority of the header or headers from which a diverted-by address is derived.
Examples
The following example shows how to enter the Diverted-by address mode:
Related Commands
|
|
|
|---|---|
domain-name
To specify the domain name of a Border Access Controller (BAC) adjacency that replaces the domain name of the Access Gateway Control Function (AGCF) and the Media Gateway Control Function (MGCF), use the domain-name command in the H248 BAC adjacency configuration mode. To remove the specification of the domain name for a BAC adjacency, use the no form of this command.
Syntax Description
Command Default
Command Modes
H248 BAC adjacency configuration (config-h248-bac-adj)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
This command can be configured only in the access adjacency submode and not in the core adjacency submode.
Examples
The following example shows how the domain-name command is used to specify the domain name of a BAC adjacency:
Related Commands
|
|
|
|---|---|
dscp
To configure a DSCP with which to mark IP packets belonging to a given QoS profile, use the dscp command in the appropriate configuration mode. To return to the default, use the no form of this command.
Syntax Description
Specifies the DSCP value with which to mark packets. Range is 0 to 63. |
Command Default
Command Modes
QoS sig configuration (config-sbc-sbe-qos-sig)
QoS video configuration (config-sbc-sbe-qos-video)
QoS voice configuration (config-sbc-sbe-qos-voice)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to configure the QoS profile for sig to mark IP packets with a DSCP of 10:
The following example shows how to configure the QoS profile for video to mark IP packets with a DSCP of 10:
The following example shows how to configure the QoS profile for voice to mark IP packets with a DSCP of 10:
dst-address
To enter the destination address mode to set the priority of the header or headers from which to derive a called party address (inbound only), use the dst-address command in SIP header configuration mode. To exit the destination address mode, use the no form of this command or the exit command.
Syntax Description
Command Default
Command Modes
SIP header configuration (config-sbc-sbe-sip-hdr)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section that follows shows the hierarchy of modes required to run the command.
This command puts you in the destination address mode where you use the header-prio header-name command to set the priority of the header or headers from which a called party address is derived.
NoteThe header list is for inbound calls only. The header list is for inbound calls only.
Examples
The following example shows how to enter the destination address mode:
Related Commands
dst-address (editor)
To enter the Destination address mode to set the priority of the header or headers from which to derive a called party address (inbound only), use the dst-address command in the Session Initiation Protocol (SIP) Header Editor configuration mode. To exit the Destination address mode, use the no form of this command or the exit command.
Syntax Description
Command Default
Command Modes
SIP Header Editor configuration (config-sbc-sbe-mep-hdr)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
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.
This command enables you to enter the Destination address mode from where you can use the header-prio header-name command to set the priority of the header or headers from which a called party address is derived.
NoteThe header list is for inbound calls only. The header list is for inbound calls only.
Examples
The following example shows how to enter the Destination address mode:
Related Commands
dst-adjacency
To configure the destination adjacency of an entry in a routing table, use the dst-adjacency command in RTG routing table configuration mode. To delete the destination adjacency, use the no form of this command.
dst-adjacency target-adjacency
no dst-adjacency target-adjacency
Syntax Description
Specifies the string that identifies the destination adjacency to use. |
Command Default
Command Modes
RTG routing table configuration (config-sbc-sbe-rtgpolicy-rtgtable)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
The target-adjacency argument is mandatory for routing tables entries with table-type round-robin .
Examples
The following example shows how to configure the destination adjacency of an entry in the new routing table MyRtgTable to softswitch1:
The following example shows how to configure the destination adjacency of an entry in the new routing table MyRtgTable to softswitch1:
The following example shows how to configure the destination adjacency of an entry in the new routing table MyRtgTable to softswitch1:
The following example shows how to configure the destination adjacency of an entry in the new routing table MyRtgTable to softswitch1:
The following example shows how to configure the destination adjacency of an entry in the new routing table MyRtgTable to softswitch1:
dtmf-duration (session border controller)
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.
Syntax Description
This is the default duration of a DTMF event in milliseconds. The range is 0-1000. The default is 200. |
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) for distributed SBC
VDBE configuration (config-sbc-vdbe) for unified SBC
Command History
|
|
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
|
Usage Guidelines
This command can be used on both unified and distributed SBC, but in slightly different configuration modes. Note the correct mode to use for either unified or distributed SBC.
Examples
The following example configures the duration of a DTMF event to be 250 milliseconds for a unified SBC:
The following example configures the duration of a DTMF event to be 250 milliseconds for a distributed SBC:
Related Commands
|
|
|
|---|---|
dtmf disable sip
To turn off automatic detection of dual tone multifrequency-specific options, use the dtmf disable sip command in adjacency SIP configuration mode. To turn on the automatic detection of dual tone multifrequency (DTMF) relay, use the no form of this command.
dtmf disable sip { info | notify }
no dtmf disable sip { info | notify }
Syntax Description
Command Default
Command Modes
Adjacency SIP configuration (config-sbc-sbe-adj-sip)
Command History
|
|
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section that follows shows the hierarchy of the modes and modes required to run the command.
Examples
The following example shows how to turn off automatic detection of DTMF relay using the INFO method as the preferred DTMF transport method for the endpoints on an adjacency:
dtmf sip
To configure DTMF SIP, use the dtmf sip command in adjacency SIP configuration mode. To unconfigure DTMF SIP, use the no form of this command.
dtmf sip { default duration millisec | info always-supported | notify interval millisec }
no dtmf sip { default duration millisec | info always-supported | notify interval millisec }
Syntax Description
Command Default
Command Modes
Adjacency SIP configuration (config-sbc-sbe-adj-sip)
Command History
|
|
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section that follows shows the hierarchy of the modes and modes required to run the command.
Examples
The following example shows how to configure DTMF SIP:
duration
To configure the expiration time during which the Cisco Unified Border Element (SP Edition) tries to perform provisioned delegate registration before stopping, use the duration command in subscriber delegate profile configuration mode. To reset the expiration time to the default duration time, use the no duration command.
no duration {dur time in secs}
Syntax Description
This is the duration time in seconds. The range is 1 to 2,147,483 seconds. The default duration time is 1800 seconds. |
Command Default
Command Modes
Subscriber delegate profile configuration mode (config-sbc-sbe-subscriber-delegate-prof)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
This command configures the expiration time when the delegate client is due to expire, that is, the length of time in seconds during which the SBC tries to perform delegate registration before stopping. This is one of the delegate profile parameters you can configure.
After a delegate profile is configured, the following profile parameters may optionally be configured:
Examples
The following example configures a provisioned delegate registration profile that can be applied to a delegate registration subscriber and configures a delegate registration for delegate client (aor= sip:bob@isp.example). The delegate registration profile is configured with a duration expiration time of 1000 seconds, a retry count of 5 times, a retry interval of 60 seconds, and a refresh timeout time of 200 seconds:
Related Commands
early-media-deny
To configure whether to disallow early-media for an entry in an admission control table, use the early-media-deny command in CAC table configuration mode. To return to the default value, use the no form of this command.
Syntax Description
Command Default
Command Modes
CAC table configuration (config-sbc-sbe-cacpolicy-cactable)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to disallow early-media for an existing entry in the admission control table MyCacTable:
Related Commands
|
|
|
|---|---|
Configures the time to allow early-media before a call is established. |
early-media-timeout
To configure the amount of time for which to allow early-media before a call is established, use the early-media-timeout command in CAC table configuration mode. To return to the default value, use the no form of this command.
Syntax Description
Specifies the timeout period (in seconds). A value of 0 means that calls are not timed out. |
Command Default
Command Modes
CAC table configuration (config-sbc-sbe-cacpolicy-cactable)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to configure the early-media-timeout for an existing entry in the admission control table MyCacTable:
early-media-type
To configure the direction of early media to allow for an entry in a call admission control table, use the early-media-type command in CAC table configuration mode. To return to the default value, use the no form of this command.
early-media-type {backward-half-duplex | forward-half-duplex | full-duplex}
Syntax Description
Command Default
Command Modes
CAC table configuration (config-sbc-sbe-cacpolicy-cactable)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to disallow early-media for an existing entry in the admission control table MyCacTable:
|
|
|
|---|---|
Configures the time to allow early-media before a call is established. |
edit-cic
To manipulate a carrier identification code in number analysis and routing tables, use the edit-cic command call policy set table mode. The no form of the command removes the configured string.
edit-cic [ del-prefix pd ] | [ del-suffix sd ] | [ add-prefix pa ] | [ replace ds ]
Syntax Description
Command Default
Command Modes
NA-DST-address-table configuration (config-sbc-sbe-rtgpolicy-natable-entry)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
This command is used to manipulate the carrier identification code (cic) address in number analysis and routing tables. You can configure more than one edit action (del-prefix, del-suffix, and add-prefix) and configure combinations of edit actions, as long as you follow the rules. The rules are as follows:
- The edit-cic action keywords del-prefix, del-suffix, and add-prefix can be combined in any order, with at least one keyword required.
- Combinations of edit-cic actions are implemented from left to right. For example, the combination edit-cic del-prefix 3 add-prefix 919 del-suffix 4 command changes the dialed digit string, 2025551212, into 919555.
- The edit-cic replace action cannot be combined with other edit actions.
If you want to remove the carrier ID entirely from outgoing messages, specify a replacement string of 0000 or a prefix deletion length of 4. For example:
Re-entering the edit-cic command with a new combination of edit actions replaces the existing combination.
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to configure entry 1 to delete four digits from the end of the dialed string, delete three digits from the beginning of the dialed string, and then add 202 to the beginning of the dialed string in the new number analysis table MyNaTable:
The following example replaces the entire carrier code identification address of dialed digits with the digits 2025551212:
The following command sets entry 1 to delete the first digit of the carrier ID in NA table MyNaTable :
Related Commands
edit-src
To configure a source address manipulation action in the number analysis table and the routing table, use the edit-src command in the appropriate configuration mode. To remove a configured string, use the no form of this command.
edit-src [ del-prefix pd ] | [ del-suffix sd ] | [ add-prefix pa ] | [ replace ds ]
Syntax Description
Command Default
Command Modes
Number Analysis table entry (config-sbc-sbe-rtgpolicy-natable-entry)
Command History
Usage Guidelines
You cannot use this command if the table is a part of the active policy set.
This command is used to manipulate the source address in the number analysis table and the routing table. You can configure more than one edit action ( del-prefix , del-suffix , and add-prefix ) or combinations of edit actions, as long as you follow these rules:
- The del-prefix, del-suffix, and add-prefix edit-src action keywords can be combined in any order, with at least one keyword being mandatory.
- Combinations of edit-src actions are implemented from left to right. For example, the edit-src del-prefix 3 add-prefix 919 del-suffix 4 combination command changes the dialed digit string 2025551212 into 919555.
- The edit-src replace action command cannot be combined with other edit actions.
Re-entering the edit-src command with a new combination of edit actions replaces the existing combination.
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of the modes required to run the command.
Examples
The following example shows how to configure entry 1 to delete four digits from the end of the dialed string, delete three digits from the beginning of the dialed string, and then add 202 to the beginning of the dialed string in the new number analysis table, MyNaTable:
The following example shows how to replace the entire source address of the dialed digits with the digit 2025551212:
The following command shows how to set entry 1 to delete the first digit of the source address in the MyTable routing table:
Related Commands
edit
To configure a string manipulation action in number analysis and routing tables with entries of the table matching the whole dialed number or the source number, use the edit command in NA routing table entry configuration mode. To return to the default value, use the no form of this command.
edit [ del-prefix pd ] | [ del-suffix sd ] | [ add-prefix pa ] | [ replace ds ]
Syntax Description
Command Default
Command Modes
NA routing table entry configuration (config-sbc-sbe-rtgpolicy-natable-ent)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
This command is used to manipulate the source address or a destination address in number analysis and routing tables. You can configure more than one edit action (del-prefix, del-suffix, and add-prefix) and configure combinations of edit actions, as long as you follow the rules. The rules are as follows:
- The edit action keywords del-prefix, del-suffix, and add-prefix can be combined in any order, with at least one keyword required.
- Combinations of edit actions are implemented from left to right. For example, the combination edit del-prefix 3 add-prefix 919 del-suffix 4 command changes the dialed digit string, 2025551212, into 919555.
- The edit replace action cannot be combined with other edit actions.
Re-entering the edit command with a new combination of edit actions replaces the existing combination.
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to configure entry 1 to delete four digits from the end of the dialed string, delete three digits from the beginning of the dialed string, and then add 202 to the beginning of the dialed string in the new number analysis table MyNaTable:
The following example replaces the entire address of dialed digits with the digits 2025551212:
Related Commands
|
|
|
|---|---|
Manipulates a carrier identification code in number analysis and routing tables. |
|
Configures a source number manipulation action in number analysis and routing tables. |
editor-list
To specify the stage at which you want the editors to be applied, use the editor-list command in the adjacency SIP editor configuration mode. To remove the configuration of the editor list, use the no form of this command.
editor-list {after-send | before-receive}
no editor-list {after-send | before-receive}
Syntax Description
Command Default
Command Modes
Adjacency SIP editor configuration (config-sbc-sbe-adj-sip-ed)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of the modes required to run this command.
Note that the editors must be configured before you run this command.
Examples
In the following example, the editor-list command is used to specify that the editors must be applied to the messages after the messages are received:
Related Commands
editor-type
To configure an editor type for a SIP adjacency to apply, use the editor-type command in the SIP adjacency configuration mode. To unconfigure an editor type, use the no form of this command.
editor-type { editor | profile }
Syntax Description
Uses the method, header, option, parameter, or body profile. |
Command Default
Command Modes
SIP adjacency configuration (config-sbc-sbe-sip)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of the modes required to run the command.
Examples
The following example shows how to configure an editor type for a SIP adjacency to apply:
Related Commands
|
|
|
|---|---|
editor
If multiple editors have been configured in an editor list, to specify the order in which a particular editor must be applied in the sequence defined by the list, use the editor command in the adjacency SIP editor configuration mode. To remove the configuration of the editor, use the no form of this command.
editor order-number editor-name [condition [body contains sdp]]
no editor order-number editor-name [condition [body contains sdp]]
Syntax Description
Command Default
Command Modes
Adjacency SIP editor configuration (config-sbc-sbe-adj-sip-ed)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of the modes required to run this command.
Examples
In the following example, the editor command is used to set the load order for the my_editor editor to 4. A header editor is configured in this example.
Related Commands
entry
To create or modify an entry in a table or an SDP media profile, use the entry command in the appropriate configuration mode. To destroy the given entry, use the no form of this command.
Syntax Description
Command Default
Command Modes
CAC table configuration (config-sbc-sbe-cacpolicy-cactable)
NA routing table configuration (config-sbc-sbe-rtgpolicy-natable)
RTG routing table configuration (config-sbc-sbe-rtgpolicy-rtgtable)
SIP SDP media profile configuration (config-sbc-sbe-sip-sdp-media)
Command History
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
NoteYou cannot change the configuration of tables in the context of the active policy set. An entry may not be destroyed if the table is a part of the active policy set. You cannot change the configuration of tables in the context of the active policy set. An entry may not be destroyed if the table is a part of the active policy set.
Examples
The following example shows how to create an entry in the new admission control table, MyCacTable:
entry (enum)
To configure the ENUM client entry name and enter the ENUM entry configuration mode, use the entry (enum) command in SBE configuration mode. To remove the ENUM client entry name, use the no form of this command.
Syntax Description
Command Default
Command Modes
ENUM configuration (config-sbc-sbe-enum)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to configure the ENUM client entry name:
Related Commands
enum
To configure the ENUM client ID number and enter the ENUM configuration mode, use the enum command in SBE configuration mode. To remove the ENUM client ID number, use the no form of this command.
Syntax Description
ENUM client ID number. Currently, only the number 1 is allowed. |
Command Default
Command Modes
SBE configuration (config-sbc-sbe)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
The ENUM ID number is used by the Routing Policy Service (RPS) to initiate service requests.
At the SBE level, multiple ENUM client entries can be provisioned.
Examples
The following example shows how to configure the ENUM client ID number and enter the ENUM configuration mode:
Related Commands
error-profile
To configure an existing error profile as the outbound SIP error profile, use the error-profile outbound command in adjacency SIP configuration mode. To remove an error profile as the SIP error profile, use the no form of this command.
error-profile outbound profile-name
no error-profile outbound profile-name
Syntax Description
Name of the existing error profile to be used as the inbound or outbound SIP error profile. |
Command Default
Command Modes
Adjacency SIP configuration (config-sbc-sbe-adj-sip)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to configure an existing error profile as the outbound SIP error profile:
Related Commands
exit-if-vnet
To exit virtual network interface mode, use the exit-if-vnet command in virtual network interface mode.
Syntax Description
Command Modes
Virtual network interface mode (config-if-vnet)
Command History
|
|
|
|---|---|
Usage Guidelines
This command is not saved in a configuration and therefore does not appear in show running-config output.
The exit-if-vnet command is one of the commands that will be displayed in system help if you enter a ? at the Router(config-if-vnet)# prompt. However, the exit command performs the same function as the exit-if-vnet command and is a shorter command to enter.
Examples
The following example shows how to exit virtual network interface mode:
Related Commands
exit-route-server-context
To exit a route server context and return to router configuration mode, use the exit-route-server-context command in route server context configuration mode.
Syntax Description
Command Modes
Route server context configuration (config-router-rsctx)
Command History
|
|
|
|---|---|
Usage Guidelines
When you configure a BGP route server with a flexible policy, you create a route server context with an import map, which is when you might use the exit-route-server-context command. The exit-route-server-context command is one of the commands that will be displayed in system help if you enter a ? at the Router(config-router-rsctx)# prompt. However, the exit command performs the same function as the exit-route-server-context command.
Examples
In the following example, a route server context is created and the exit-route-server-context command is used to exit route server context configuration mode:
Related Commands
|
|
|
|---|---|
Creates a route-server context in order to provide flexible policy handling for a BGP route server. |
exit-vrf-list
To exit VRF list submode, use the exit-vrf-list command in VRF list submode.
Syntax Description
Command Modes
VRF list submode (config-vrf-list)
Command History
|
|
|
|---|---|
Usage Guidelines
This command is not saved in a configuration and therefore does not appear in show running-config output.
The exit-vrf-list command is one of the commands that will be displayed in system help if you enter a ? at the Router(config-vrf-list)# prompt. However, the exit command performs the same function as the exit-vrf-list command and is a shorter command to enter.
Examples
The following example shows how to exit VRF list submode:
Related Commands
|
|
|
|---|---|
Exits any configuration mode to the next highest mode in the CLI mode hierarchy. |
|
expires-header
To configure expires parameter in the SIP contact header, use the expires-header command in adjacency SIP configuration mode. To remove an expires parameter from the header, use the no form of this command.
Syntax Description
Command Default
Command Modes
Adjacency SIP configuration (config-sbc-sbe-adj-sip)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to configure an expires header parameter on the SIP contact header:
Related Commands
|
|
|
|---|---|
Displays all the detailed field output pertaining to a specified Session Initiation Protocol (SIP) adjacency. |
fast-register-interval
To configure the fast-path register interval (in seconds), use the fast-register-interval command in adjacency SIP configuration mode. To unconfigure the fast-path register interval, use the no form of this command.
fast-register-interval interval
Syntax Description
Specifies the interval value in seconds. Range is 1 to 2000000. |
Command Default
Command Modes
Adjacency SIP configuration (config-sbc-sbe-adj-sip)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
If fast-path register support is enabled on this adjacency, this is the minimum expiry period accepted on a subscriber registration. The interval at which registrations are forwarded on to the softswitch is governed by the registration minimum expiry value.
NoteThe The interval must be less than the minimum expiry value.
Examples
The following example shows how to enable the fast-register interval on the SIP adjacency SipToIsp42 to 10 seconds:
Related Commands
|
|
|
|---|---|
fast-register disable
To disable fast-path register support on the SIP adjacency, use the fast-register disable command in adjacency SIP configuration mode. To enable fast-path register support, use the no form of this command.
Syntax Description
Command Default
Command Modes
Adjacency SIP configuration (config-sbc-sbe-adj-sip)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Fast-path register is used to prevent the SBC from forwarding all SIP register messages to the softswitch, thus reducing the load on the softswitch. This is enabled by default and can be disabled using this command. When active, a SIP register message received from the same host and port as an existing registration, and with a nonzero expires interval, is immediately responded to without further parsing or other processing performed.
Examples
The following example shows how to disable fast-path register support on the SIP adjacency SipToIsp42:
Related Commands
|
|
|
|---|---|
filename (session border controller)
To specify the path and name of the script file written using the Lua programming language, use the filename command in the SBE script-set script configuration mode.
filename { device-type:file-path-and-name }
Syntax Description
Command Default
Command Modes
SBE script-set script configuration (config-sbc-sbe-scrpset-script)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of the modes required to run this command.
Examples
In the following example, the filename command specifies that the script file is mySBCScript.lua and is located on the bootflash device:
Related Commands
first-cac-scope
To configure the scope at which to begin defining limits when performing the admission control stage of policy, use the first-cac-scope command in CAC-policy-set configuration mode. Use the no form of this command to delete the routing table.
Syntax Description
Command Default
Command Modes
CAC-policy-set configuration (config-sbc-sbe-cacpolicy)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
|
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to set the scope category as the first scope at which to define an admission control policy in configuration set 1 on mySbc:
first-cac-table
To configure the name of the first policy table to process when performing the admission control stage of policy, use the first-cac-table command in CAC-policy-set configuration mode. To remove this configuration, use the no form of this command.
Syntax Description
Specifies the admission control table that should be processed first. |
Command Default
Command Modes
CAC-policy-set configuration (config-sbc-sbe-cacpolicy)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to set the table RootCacTable as the first admission control table in configuration set 1 on mySbc:
first-call-routing-table
To configure the name of the first policy table to process when performing the routing stage of policy for new-call events, use the first-call-routing-table command in routing policy table mode. To unconfigure the name of the first policy table, use the no form of this command.
first-call-routing-table table-name
Syntax Description
Command Default
Command Modes
Routing policy table (config-sbc-sbe-rtgpolicy)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to configure the table RootCallRtgTable as the first routing table for new-call events in configuration set 1 on mySbc:
first-inbound-na-table
To configure the name of the first inbound policy table to be processed when performing the number analysis stage of a policy, use the first-inbound-na-table command in the Routing policy table configuration mode. To unconfigure the name of the first inbound policy table, use the no form of this command.
first-inbound-na-table table-name
Syntax Description
Command Default
Command Modes
Routing policy table (config-sbc-sbe-rtgpolicy)
Command History
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of the modes required to run the command.
Examples
The following example shows how to configure the table RootNaTable as the first inbound number analysis table in configuration set 1 on mySbc:
Related Commands
first-outbound-na-table
To configure the name of the first outbound policy table to be processed when performing the number analysis stage of a policy, use the first-outbound-na-table command in the Routing policy table configuration mode. To deconfigure the name of the first outbound policy table, use the no form of this command.
first-outbound-na-table table-name
Syntax Description
Command Default
Command Modes
Routing policy table (config-sbc-sbe-rtgpolicy)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of the modes required to run the command.
Examples
The following example shows how to configure the table RootOutTable as the first outbound number analysis table in configuration set 1 on mySbc:
Related Commands
first-reg-routing-table
To configure the name of the first policy table to process when performing the routing stage of policy for subscriber-registration events, use the first-reg-routing-table command in routing policy table configuration mode. To deconfigure the name of the first policy table, use the no form of this command.
first-reg-routing-table table-name
Syntax Description
Command Default
Command Modes
Routing policy table (config-sbc-sbe-rtgpolicy)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to configure the table RootRegRtgTable as the first routing table for subscriber-registration events in configuration set 1 on mySbc:
flipped-interval (XML Billing)
To configure the maximum interval at which to flip a billing XML file, use the flipped-interval command in the SBE billing XML configuration mode. To reset the flip interval to its default value of 3 minutes, use the no form of this command.
Syntax Description
Command Default
Command Modes
SBE billing XML configuration (config-sbc-sbe-billing-xml)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Routers. |
Usage Guidelines
The XML billing files are stored under the CDR path configured by the administrator. An XML billing file is generated for CDRs at regular intervals and not exceeding the defined flip size. To switch the XML billing file from one XML file to another, use the flipped-interval seconds command from the SBE billing xml configuration mode. The default interval to flip an XML billing file is 3 minutes.
Examples
The following example shows how to set the flip interval to 5 minutes (300 seconds):
Related Commands
|
|
|
|---|---|
Configures the billing method as XML for the Billing Manager. |
|
Configures the time at which long duration records are checked. |
flipped-size (XML Billing)
To configure the maximum file-size, that if exceeds, leads to the flipping of the billing XML file, use the flipped-size command in the SBE billing XML configuration mode. To reset the flip-size to its default value of 10 MB, use the no form of this command.
Syntax Description
Command Default
By default, the maximum size of billing file after which the billing file is flipped to a new file, is 10 MB.
Command Modes
SBE billing XML configuration (config-sbc-sbe-billing-xml)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Routers. |
Usage Guidelines
The XML billing files are stored in the CDR path configured by the administrator. An XML billing file is generated for the CDR at regular intervals not exceeding the defined flip-size. To switch the XML billing file from one XML file to another after the flip size is exceeded, execute the flipped-size size command from the SBE billing XML configuration mode. The default file size to flip an XML billing file is 10 MB.
Examples
The following example shows how to set the flip size to 512000:
Related Commands
|
|
|
|---|---|
Configures the billing method as XML for the Billing Manager. |
|
Configures the time at which long duration records are checked. |
fmtp (codec variant)
To define the format-specific parameters for a variant, use the fmtp command in the Codec variant configuration mode. To remove the defined format-specific parameters, use the no form of this command.
Syntax Description
The format-specific parameter string in the name=value format. |
Command Default
Command Modes
Codec variant configuration (config-sbc-sbe-codec-var-codec)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
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.
To view the default format-specific parameters values associated with variants, use the show sbc sbe codecs variant command.
Examples
The following example shows how to define the format-specific parameters for a variant in the Codec variant configuration mode:
fmtp (session border controller)
To configure the default value of the format-specific parameters for Session Description Protocol (SDP), use the fmtp command in the Codec system configuration mode.To remove the default value of the format-specific parameters, use the no form of this command.
Syntax Description
The format-specific parameter string for SDP, in the name=value format. |
Command Default
Command Modes
Codec system configuration (config-sbc-sbe-codec-def)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
When a codec is converted from a standard to a variant representation, the default format-specific parameters, if any, are stripped out of the resulting SDP. However, when the format-specific parameters under codec variant in a codec variant contains parameters that match the default format-specific parameters for the variant's standard codec, those parameters are deemed matched in SDP if either one of the following is true:
- The exact '< name >=< value >' parameter has been received.
- No parameters that start with '< name >=' have been received.
To view the default format-specific parameters values associated with standard codecs, use the show sbc sbe codecs command.
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 configure the default value of the format-specific parameters for SDP using the fmtp command in the Codec system configuration mode:
force-signaling-peer
To force the Session Initiation Protocol (SIP) messages for either only out-of-dialog requests (that is, dialog-creating requests) or both in-dialog and out-of-dialog requests to go to a configured signaling peer, use the force-signaling-peer command in adjacency SIP configuration mode. To disable this feature, use the no form of this command.
no force-signaling-peer [ all ]
Syntax Description
Forces the hop to a configured signaling peer for both in-dialog requests and out-of-dialog requests. |
Command Default
Command Modes
Adjacency SIP configuration (config-sbc-sbe-adj-sip)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
|
Usage Guidelines
While configuring redundant peer addresses, you must include the all keyword in the command. This is to force SIP messages for both in-call requests and out-of-call requests to go to the configured signaling peer.
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to force SIP messages to go to a configured signaling peer in the context of both in-dialog and out-of-dialog requests:
Related Commands
Configures the priority of a signaling peer on a SIP adjacency. |
|
Configures a SIP adjacency to switch the signaling peer to an available destination. |
g107a-factor
To set the Advantage (A) factor, use the g107a-factor command in the adjacency H.323 configuration mode or adjacency SIP configuration mode. The Advantage factor is one of the parameters used in the calculation of the MOS-CQE score. To remove the Advantage factor setting, use the no form of this command.
Syntax Description
Command Default
Command Modes
Adjacency H.323 configuration (config-sbc-sbe-adj-h323)
Adjacency SIP configuration (config-sbc-sbe-adj-sip)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of the modes required to run this command.
Examples
The following example shows how to configure the Advantage factor by using the g107a-factor command in the adjacency H.323 configuration mode:
Related Commands
g107 bpl
To set the Packet-Loss Robustness (Bpl) factor, use the g107 bpl command in the codec definition mode. The Packet-Loss Robustness factor is one of the parameters used in the calculation of the MOS-CQE score. To remove the Packet-Loss Robustness factor setting, use the no form of this command.
Syntax Description
Value of the Packet-Loss Robustness factor. The range is from 1 to 40. |
Command Default
Command Modes
Codec definition mode (config-sbc-sbe-codec-def)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of the modes required to run this command.
Examples
The following example shows how to configure the Packet-Loss Robustness factor by using the g107 bpl command in the adjacency H.323 configuration mode:
Related Commands
g107 ie
To set the Equipment Impairment (Ie) factor, use the g107 ie command in the codec definition mode. The Equipment Impairment factor is one of the parameters used in the calculation of the MOS-CQE score. To remove the Equipment Impairment factor setting, use the no form of this command.
Syntax Description
Value of the Equipment Impairment factor. The range is from 0 to 50. |
Command Default
Command Modes
Codec definition mode (config-sbc-sbe-codec-def)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of the modes required to run this command.
Examples
The following example shows how to configure the Equipment Impairment factor by using the g107 ie command in the adjacency H.323 configuration mode:
Related Commands
generic-stream callee
To configure the generic media stream list settings for a callee, use the generic-stream callee command in the CAC table entry configuration mode. To deconfigure the generic media stream list settings, use the no form of this command.
generic-stream callee generic-stream-list
Syntax Description
The name of the generic stream list. This generic stream list should be defined during the configuration of the stream list. |
Command Default
Command Modes
CAC table entry configuration (config-sbc-sbe-cacpolicy-cactable-entry)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
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 configure the generic media stream list settings for a callee using the generic-stream callee command in the CAC table entry mode:
generic-stream caller
To configure the generic media stream list settings for a caller, use the generic-stream caller command in the CAC table entry configuration mode. To deconfigure the generic media stream list settings, use the no form of this command.
generic-stream caller generic-stream-list
Syntax Description
The name of the generic stream list. This generic stream list should be defined during the configuration of the stream list. |
Command Default
Command Modes
CAC table entry configuration (config-sbc-sbe-cacpolicy-cactable-entry)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
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 configure the generic media stream list settings for a caller using the generic-stream caller command in the CAC table entry mode:
generic-stream media-type
To configure the media type for a generic stream, use the generic-stream media-type command in the Stream list configuration mode. To deconfigure the media type for a generic stream, use the no form of this command.
generic-stream media-type { application | message } transport udp protocol protocol-name
no generic-stream media-type { application | message } transport udp protocol protocol-name
Syntax Description
The protocol name for the generic stream. The protocol name is case sensitive. |
Command Default
Command Modes
Stream list configuration (config-sbc-sbe-stream-list)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of the modes required to run the command.
Examples
The following example shows how to configure application as the media type for the generic stream using the generic-stream media-type command in the Stream list configuration mode:
Related Commands
|
|
|
|---|---|
generic-stream branch
To configure the generic media stream list settings for a caller or a callee, use the generic-stream branch command in the CAC table entry configuration mode. To unconfigure the generic media stream list settings, use the no form of this command.
generic-stream branch generic-stream-list
Syntax Description
Command Default
Command Modes
CAC table entry configuration (config-sbc-sbe-cacpolicy-cactable-entry)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of the modes required to run the command.
Examples
The following example shows how to configure the generic media stream list settings by using the generic-stream branch command:
Related Commands
|
|
|
|---|---|
Configures the generic media stream list settings for a callee. |
|
Configures the generic media stream list settings for a caller. |
global
To enter the mode for configuring blacklisting to apply to all addresses, use the global command in the SBE blacklist configuration mode.
Syntax Description
Command Default
Command Modes
SBE blacklist configuration (config-sbc-sbe-blacklist)
Command History
|
|
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to enter the mode for configuring blacklisting to apply to all addresses:
Related Commands
group (session border controller)
To configure an adjacency to an adjacency group, use the group command in the appropriate adjacency mode. To remove the adjacency from the specified group, use the no form of this command.
Syntax Description
Indicates the group name for the adjacency. The maximum size is 32 characters. |
Command Default
Command Modes
Adjacency H.323 configuration (config-sbc-sbe-adj-h323)
Adjacency SIP configuration (config-sbc-sbe-adj-sip)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how the group command assigns a SIP adjacency named sipGW to adjacency group named InternetEth0:
The following example shows how the group command assigns an H.323 adjacency named H323ToIsp42 to an adjacency group named Isp42.
Feedback