- 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)
Cisco Unified Border Element (SP Edition) Command Reference: Unified Model
Bias-Free Language
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
- Updated:
- September 30, 2010
Chapter: h225 address through overload-time-threshold
- h225 address
- h225 address (session border controller)
- h225 timeout
- h245-address-pass
- h245-tunnel disable
- h248-profile-version
- h248-profile
- h248-version (session border controller)
- h248 allow-all-mg
- h323 (session border controller)
- header-editor
- header-editor (method)
- header-name
- header-name p-asserted-id
- header-name supported header-value timer insert
- header-name via passthrough
- header-prio header-name
- header-prio header-name (editor)
- header-profile
- header (editor)
- header (session border controller)
- heart-beat terminate
- hold-media-timeout
- hunt-on-reject
- hunting-mode
- hunting-trigger
- import-map
- ims media-service
- ims pani
- ims realm
- ims rf
- ims rx
- ims rx preliminary-aar-forbid
- inbound secure
- inherit profile
- interwork cost
- interwork maximum
- invite-timeout
- ipsec maximum
- ipv4
- ipv4 (blacklist)
- ipv4 (SBE H.248)
- ip access-list
- ip host
- ip multicast-routing
- ip multicast rpf mofrr
- ip multicast rpf select topology
- ip multicast topology
- ip precedence
- ip servic e reflect
- ip TOS (session border controller)
- ip wccp outbound-acl-check
- ip wccp redirect
- ip wccp source-interface
- ip wccp version
- key (session border controller)
- ldr-check
- ldr-check (XML billing)
- load-order
- local-address ipv4
- local-address ipv4 (packet-cable)
- local-id host
- local-jitter-ratio
- local-port (session border controller)
- location-id (session border controller)
- max-call-rate-per-scope
- max-connections
- max-in-call-msg-rate
- max-num-calls
- max-out-call-msg-rate
- max-recursive-depth
- max-regs-rate-per-scope
- max-regs
- max-responses
- max-updates
- media
- media-address
- media-address ipv4
- media-address pool
- media-gateway
- media-gateway policy type
- media-late-to-early-iw
- media-line
- media-policy
- media-timeout (session border controller)
- media address preserve
- media bandwidth-fields ignore
- media bypass
- media bypass type
- media limits
- media police
- method-editor
- method-profile
- method 3GPP-RF
- method (editor)
- method packetcable-em
- method (session border controller)
- method xml
- minor-alert-size
- mode (session border controller)
- mon itor ev ent-trace sbc ha (EXEC)
- mon itor ev ent-trace sbc ha (global)
- na-carrier-id-table
- na-dst-address-table
- na-dst-prefix-table
- na-src-account-table
- na-src-address-table
- na-src-adjacency-table
- na-src-name-anonymous-table
- na-src-prefix-table
- nat (session border controller)
- nat force-on
- network-id (session border controller)
- network
- option-editor
- option-profile
- options
- option (editor)
- option (session border controller)
- origin-host
- origin-host (Rf interface)
- origin-realm
- origin-realm (Rf interface)
- outbound-flood-rate
- overload-time-threshold (session border controller)
h225 address
To configure the sourceAddress and destinationAddress fields of an H.225 message in the H.323 adjacency, use the h225 address command in the H.323 adjacency configuration mode. To return to the default value, use the no form of this command.
h225 address { block | usage { e164 | h323id }}
no h225 address { block | usage }
Syntax Description
Command Default
By default, the sourceAddress and destinationAddress in a H.225 message are not blocked.
The H.225 sourceAddress and destinationAddress fields are interpreted in the H.323-ID format.
Command Modes
Adjacency H.323 configuration (config-sbc-sbe-adj-h323)
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 SBC to block the sourceAddress and destinationAddress fields in H.225 messages received on the adjacency by using the h225 address block command in the H.323 adjacency configuration mode:
The following example shows how to configure the H.225 sourceAddress and destinationAddress fields so that they are interpreted in the e164 format:
Related Commands
|
|
|
|---|---|
h225 address (session border controller)
To configure the sourceAddress and destinationAddress of H.225 message in the H.323 adjacency, use the h225 address command in the H.323 adjacency configuration mode. To return to the default value, use the no form of this command.
h225 address { block | usage { e164 | h323id }}
no h225 address { block | usage }
Syntax Description
Command Default
By default, the sourceAddress and destinationAddress in a H.225 message are not blocked.
The H.225 sourceAddress and destinationAddress fields are interpreted in the H.323-ID format.
Command Modes
Adjacency H.323 configuration (config-sbc-sbe-adj-h323)
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 SBC to block the sourceAddress and destinationAddress fields in H.225 messages received on the adjacency by using the h225 address block command in the H.323 adjacency configuration mode:
The following example shows how to configure the H.225 sourceAddress and destinationAddress fields so that they are interpreted in the e164 format:
Related Commands
|
|
|
|---|---|
h225 timeout
To configure the H.225 timeout interval, use the h225 timeout command in the appropriate configuration mode. To return to the default value, use the no form of this command.
h225 timeout { setup | proceeding | establishment } value
no h225 timeout { setup | proceeding | establishment } value
Syntax Description
Command Default
Command Modes
Adjacency H.323 configuration (config-sbc-sbe-adj-h323)
H.323 configuration (config-sbc-sbe-h323)
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 h225 timeout command configures an H.225 timeout interval in adjacency H.323 configuration mode:
The following example shows how the h225 timeout command configures an H.225 timeout interval in H.323 configuration mode:
h245-address-pass
To specify when an H.245 address is passed to the caller when the caller does not support tunneling, use the h245-address-pass command in the adjacency H.323 configuration mode. The no form of this command shows default behavior, where H.323 supplies the H.245 address on a Q.931 call proceeding, and all subsequent messages to the caller until the H.245 connection is opened.
h245-address-pass wait-connect
no h245-address-pass wait-connect
Syntax Description
Pass H.245 address to caller until call is connected. H.323 supplies only the H.245 address on the Q.931 connect |
Command Default
Command Modes
Adjacency H.323 configuration (config-sbc-sbe-adj-h323)
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 H.323 adjacency to allow delay passing the H.245 address to caller:
Router(config-sbc-sbe-adj-h323)# h245-address-pass wait-connect
Related Commands
|
|
|
|---|---|
h245-tunnel disable
To disable H.245 tunneling on a per-adjacency basis, use the h245-tunnel disable command in adjacency H.323 configuration mode. To enable tunneling, use the no form of this command.
Syntax Description
Command Default
Command Modes
Adjacency H.323 configuration (config-sbc-sbe-adj-h323)
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 h245-tunnel disable command disables H.245 tunneling on an H.323 adjacency named H323ToIsp42:
h248-profile-version
To configure the vDBE H.248 profile version to interoperate with media gateway controller (SBE), use the h248-profile-version command in the vDBE H.248 profile configuration mode.To return to the default value, use the no form of this command.
h248-profile-version { profile-version }
Syntax Description
Version number of the H.248 profile. The values are from 1 to 3. The value of 3 stands for gate control. The value of 1 stands for etsi-bgf. |
Command Default
Command Modes
vDBE H.248 profile configuration (config-sbc-dbe-vdbe-h248-profile)
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 a user group associated with a task group that includes the proper task IDs. To use this command, you must be in the correct configuration mode and submode. The “Examples” section shows the hierarchy of modes and submodes required to run the command.
Use the h248-profile-version command after you have defined the name of the profile using the h248-profile command.
Examples
The following example shows how to configure the vDBE H.248 profile version to interoperate with the media gateway controller (SBE):
Related Commands
h248-profile
To configure a Virtual Data Border Element (VDBE) H.248 profile name to interoperate with the data border element (DBE), use the h248-profile command in the vDBE configuration mode. To return to the default value, use the no form of this command.
h248-profile { etsi-bgf | gate-ctrl } version version-number
Syntax Description
The profile’s version number. The default version number for etsi-bgf is 2 and gate-ctrl is 3. |
Command Default
Command Modes
VDBE configuration (config-sbc-dbe-vdbe)
Command History
Usage Guidelines
To use this command, you must be in a user group that is associated with a task group that includes the proper task IDs. To use this command, you must also be in the correct configuration mode and submode. The Examples section that follows shows the hierarchy of the modes and submodes required to run the command.
After the DBE is configured to use the H.248 profile name, the applicable profile name is advertised with the Service Change messages.
Examples
The following example shows how to configure the vDBE H.248 Ia profile to interoperate with the DBE:
Router(config-sbc-dbe-vdbe)# h248-profile etsi-bgf version 2
Related Commands
|
|
|
|---|---|
Defines the version of an H.248 protocol that the DBE uses when it forms associations with an H.248 controller. |
|
h248-version (session border controller)
To define the version of an H.248 protocol that the data border element (DBE) uses when it forms associations with an H.248 controller, use the h248-version command in VDBE configuration mode. To leave the default as version 2 of the H.248 protocol, use the no form of this command.
no h248-version version-number
Syntax Description
Specifies the version number. The DBE can accept H.248.1 version 2 or version 3. The default is H.248.1 version 2. |
Command Default
Command Modes
VDBE configuration mode (config-sbc-dbe-vdbe)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers for distributed SBC. |
Usage Guidelines
This command configures the DBE to support H.248.1v3, thus allowing the DBE to interoperate with an SBE or media gateway controller (MGC) which requires H.248.1 version 3. The DBE can accept H.248.1 version 2 or version 3.
The DBE rejects attempts to negotiate with the MGC to a lower version once the DBE is configured to support version 3.
Examples
The following example creates a DBE service on an SBC called “mySbc” and configures the DBE to use version 3 of the H.248.1 protocol, for a distributed SBC:
Related Commands
|
|
|
|---|---|
Defines which H.248 package, either IP NAT Traversal package (ipnapt) or NAT Traversal package (ntr), the DBE uses for signaling Network Address Translation (NAT) features. |
h248 allow-all-mg
To configure the H.248 signaling stack to allow connections from all Media Gateways, use the h248 allow-all-mg command in the SBE configuration mode. Use the no form of this command to deconfigure the H.248 signaling stack from allowing connections from all media gateways.
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.
Examples
The following command configures the H.248 signaling stack to allow any Media Gateway to connect to the SBE:
h323 (session border controller)
To enter the H.323 configuration mode, use the h323 command in SBE configuration mode.
Syntax Description
Command Default
Command Modes
SBE configuration (config-sbc-sbe)
Command History
|
|
|
|---|---|
This command was not supported in Cisco IOS XE Release 2.4 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 H.323 configuration mode:
Related Commands
|
|
|
|---|---|
Configures an H.323 Registration, Admission, and Status (RAS) retry count for an RAS transaction type. |
|
header-editor
To set a specified header editor for inbound and outbound signaling on the signaling border element (SBE) session initiation protocol (SIP) adjacency, use the header-editor command in the Adjacency SIP configuration mode. To remove a header editor, use the no form of this command.
header-editor { inbound | outbound} { editor-name | default }
no header-editor { inbound | outbound} { editor-name | default }
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 the modes required to run the command.
Examples
The following example shows how the header-editor command sets header editors for inbound and outbound signaling on the SIPP SBE SIP adjacency:
Related Commands
|
|
|
|---|---|
header-editor (method)
To add a header editor to act on a method, use the header-editor command in the signaling border element (SBE) SIP method element configuration mode. To remove a header editor, use the no form of this command.
Syntax Description
Command Default
Command Modes
SBE SIP Method Element configuration (config-sbc-sbe-mep-mth-ele)
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 the header-editor command adds a header editor to act on a method:
|
|
|
|---|---|
header-name
To configure various headers, use the header-name command in the adjacency SIP configuration mode. To deconfigure the headers, use the no form of this command.
header-name {contact {add [tls-param] | contact-param {passthrough | strip}} | expires suppress | from {passthrough} | p-asserted-id {assert | header-value {word}} | record-route {passthrough} | route {destination-address {word} | port port number } | supported {header-value {timer {insert}}} | to {passthrough} |
via {passthrough {inbound | outbound}}}
no header-name {contact {add [tls-param] | contact-param {passthrough | strip}} | expires suppress | from {passthrough} | p-asserted-id {assert | header-value {word} } | record-route {passthrough} | route {destination-address {word} | port port number } | supported {header-value {timer {insert}}} | to {passthrough} |
via {passthrough {inbound | outbound}}}
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. |
|
This command was modified. The contact -param keyword was added. |
|
Usage Guidelines
This command is used in configuring Aggregate Registration.
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 header-name command is used to configure the passthrough header for non-REGISTER requests:
Related Commands
|
|
|
|---|---|
Requests the SBC to rewrite the Request-URI to a different user and hostname before sending a request to a registered subscriber. |
header-name p-asserted-id
To specify the value for the P-Asserted-Identity on the outgoing SIP message, use the header-name p-asserted-id command in SBC SBE Adjacency SIP mode. Use the no form of this command to remove the P-Asserted-Identity.
header-name p-asserted-id [header-value [ header-value ] | assert]
no header-name p-asserted-id [header-value [ header-value ] | assert]
Syntax Description
A value for the P-Asserted-Identity header as defined by RFC 3325. |
|
Enable the P-Asserted-Identity on the outgoing SIP messages. |
Command Default
Command Modes
SBC SBE Adjacency SIP (config-sbc-sbe-adj-sip)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
The header is added to all requests and responses except ACK, CANCEL, INFO, PRACK, REGISTER and UPDATE.
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 specify the header value for the P-Asserted-Identity for adjacency CORE. In the following example, sip:1234@cisco.com is specified as the header-value:
header-name supported header-value timer insert
To insert a “Supported:timer” header, use the header-name supported header-value timer insert command in SBC SBE Adjacency SIP mode. Use the no form of this command to disable inserting the header.
header-name supported header-value timer insert
no header-name supported header-value timer insert
Syntax Description
Command Default
Command Modes
SBC SBE Adjacency SIP (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 the SIP adjacency CORE to insert a supported timer header:
The following show command output provides details on the above configuration. Note the value of the supported timer insert field:
header-name via passthrough
To configure the session border controller (SBC) to allow the Via headers on inbound requests or outbound requests for a specified adjacency to pass through, use the header-name via passthrough command in the adjacency SIP configuration mode. To disable passthrough of Via headers on inbound requests or outbound requests, use the no form of this command.
header-name via passthrough {inbound | outbound}
no header-name via passthrough {inbound | outbound}
Syntax Description
Command Default
The SBC removes the existing Via headers and adds its own Via header.
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 use the header-name via passthrough command to allow the Via headers on inbound requests and outbound requests for a specified adjacency to pass through:
Related Commands
|
|
|
|---|---|
Configures the contact header and passthrough header in non-REGISTER requests. |
|
Specifies the value for the P-Asserted-Identity header on outgoing SIP messages. |
|
header-prio header-name
To configure the priority of a header that is used to derive a source, destination, or diverted-by address, use the header-prio header-name command in the appropriate SIP header address configuration mode. To remove the priority from a header, use the no form of this command.
header-prio priority-level header-name header-name [ request-uri ]
no header-prio priority-level header-name header-name [ request-uri ]
Syntax Description
Command Default
Command Modes
SIP header destination address configuration (config-sbc-sbe-sip-hdr-dst)
SIP header source address configuration (config-sbc-sbe-sip-hdr-src)
SIP header diverted-by address configuration (config-sbc-sbe-sip-hdr-div)
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 can be used multiple times to set the priorities of multiple headers.
Examples
The following example shows how to configure the priority of a header that uses the Request URI to derive a destination address:
The following example shows how to configure a list of headers to derive a destination address:
ASR-1002(config-sbc-sbe-sip-hdr-dst)# end
The following example shows how to configure a list of headers to derive a source address:
The following example shows how to configure a list of headers to derive a source address of a diverted call:
The following is an example of the show command output after the header list for destination address, source address, and diversion address is configured on an SBC:
Related Commands
header-prio header-name (editor)
To configure the priority of a header that is used to derive a source, destination, or diverted-by address, use the header-prio header-name command in the appropriate session initiation protocol (SIP) Header Address configuration mode. To remove the priority from a header, use the no form of this command.
header-prio priority-level header-name header-name [ request-uri ]
Syntax Description
Command Default
Command Modes
SIP header destination address configuration (config-sbc-sbe-sip-hdr-dst)
SIP header source address configuration (config-sbc-sbe-sip-hdr-src)
SIP header diverted-by address configuration (config-sbc-sbe-sip-hdr-div)
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 can be used multiple times to set the priorities of multiple headers.
Examples
The following example shows how to configure the priority of a header that uses the Request URI to derive a destination address:
The following example shows how to configure a list of headers to derive a destination address:
Router(config-sbc-sbe-mep-hdr-dst)# end
The following example shows how to configure a list of headers to derive a source address:
The following example shows how to configure a list of headers to derive the source address of a diverted call:
Related Commands
header-profile
To set a specified header profile for inbound and outbound signaling on a specified SBE SIP adjacency, use the header-profile command in adjacency sip configuration mode.
header-profile { inbound | outbound} profile-name
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 the header-profile command sets header profiles for inbound and outbound signaling on an SBE SIP adjacency test:
header (editor)
To add a header to a SIP message editor, use the header command in the SIP Header Editor configuration mode. To remove a header, use the no form of this command.
header header-name [ entry entry-number ]
no header header-name [ entry entry-number ]
Syntax Description
Name of the header to be added to the header editor. Valid names are 1 to 32 characters in length (inclusive) and case-sensitive. |
|
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 shows the hierarchy of the modes required to run the command.
Examples
The following example shows how the header command adds a header, test, to the Myeditor header editor:
Related Commands
|
|
|
|---|---|
Configures a SIP header or method blacklist editor on a SIP message. |
|
header (session border controller)
To add a header with a specified name to a SIP message profile, use the header command in SIP header-profile configuration mode. To remove the method from the profile, use the no form of this command.
Syntax Description
Specifies the name of the header added to the header profile. Valid names are 1 to 32 characters in length (inclusive) and are case-sensitive. |
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 shows the hierarchy of modes required to run the command.
Examples
The following example shows how the header command adds the header “test” to the header profile Myprofile:
Related Commands
|
|
|
|---|---|
Configures SIP header or method blacklist profiles on a SIP message. |
|
heart-beat terminate
To configure the interval during which only one heartbeat request from an H.248 terminal device can pass through the Border Access Controller (BAC), and terminate the other heartbeat requests sent during this interval, use the heart-beat terminate command in the H248 BAC adjacency configuration mode. To return to the default value, use the no form of this command.
heart-beat terminate terminate-interval
no heart-beat terminate terminate-interval
Syntax Description
Interval during which heartbeat requests are terminated, in seconds. The range is from 0 to 3600. The default value is 60. |
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
To disable the heartbeat termination function, set the terminate-interval to 0 seconds. If the terminate-interval is 0 seconds, then all the heartbeat requests are passed through the BAC and none are terminated.
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 heart-beat terminate command is used to configure the terminate interval :
hold-media-timeout
To configure the time an SBE will wait after receiving a media timeout notification from the DBE for an on-hold call before tearing that call down, use the hold-media-timeout command in SBE configuration mode. To set the number to its default, use the no form of this command.
Syntax Description
Specifies the time in milliseconds an SBE will wait after receiving a media timeout notification from the DBE for an on-hold call before tearing that call down. |
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.
Examples
The following command configures the SBE to wait two hours after receiving the last media packet on an on-hold call before cleaning up the call resources:
hunt-on-reject
To set the trigger on hunting, use the hunt-on-reject command in the signaling border element (SBE) SIP body element configuration mode. To stop the trigger, use the no form of this command.
Syntax Description
Command Default
Command Modes
SBE SIP body element configuration (config-sbc-sbe-mep-bdy-ele)
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 create a body editor named bodyeditor1, describe the body type that is to act on the messages with the application/ISUP Content Type header , and set the trigger on hunting:
Related Commands
hunting-mode
To configure the form of H.323 hunting to perform if hunting is triggered, use the hunting-mode command in one of its supported modes: H.323 (global H.323 scope) and adjacency h323 (destination H.323 adjacency). The no form of the command resets to the default of alternate end points.
hunting-mode {altEndps | multiARQ}
Syntax Description
Command Default
Default is alternate end points (altEndps) if user does not configure a hunting-mode or configures no hunting-mode. It does not disable hunting completely.
Command Modes
H.323 configuration (config-sbc-sbe-h323)
Adjacency H.323 configuration (config-sbc-sbe-adj-h323)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
The SBC hunts for other routes or destination adjacencies in the event of a failure. Hunting re-routes the call in response to a specific user-configured event or error code. The hunting mode is typically set after the hunting-trigger is configured.
The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to configure H.323 to perform multiARQ hunting and to retry routing if it receives a noBandwidth or securityDenied error:
Related Commands
|
|
|
|---|---|
hunting-trigger
To configure failure return codes to trigger hunting, use the hunting-trigger command in one of its supported modes: SIP (global SIP scope), H.323 (global H.323 scope), adjacency SIP (destination SIP adjacency), and adjacency h323 (destination H.323 adjacency). The no form of the command clears all error codes.
If you enter no hunting-trigger x y, then just codes x and y are removed from the configured list.
hunting-trigger {error-codes | disable} error-codes
no hunting-trigger {error-codes | disable} error-codes
Syntax Description
Command Default
Command Modes
SBE SIP configuration (config-sbc-sbe)
H.323 configuration (config-sbc-sbe-h323)
Adjacency SIP configuration (config-sbc-sbe-adj-sip)
Adjacency H.323 configuration (config-sbc-sbe-adj-h323)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
If both adjacency level and SBE level hunting triggers are configured, the adjacency level takes priority.
If you enter hunting-trigger x followed by hunting-trigger y, the value of x is replaced with y.
To set both x and y to be hunting triggers, you must enter hunting-trigger x y.
The Examples section shows the hierarchy of modes required to run the command.
In the adjacency SIP or H.323 adjacency modes, if you specify the special hunting-trigger value of disable, routes are never retried to this adjacency, even if the error code is on the global retry list.
To configure more than one H.323 hunting trigger, you must enter the commands as separate lines, such as in the following example:
Examples
The following example shows how to configure SIP to retry routing if it receives a 415 (media unsupported) or 480 (temporarily unavailable) error:
The following example shows how to configure H.323 to retry routing if it receives a noBandwidth or securityDenied error. Note that for multiple error codes, each hunting trigger must be configured on a separate line:
The following example shows how to configure SIP to retry routing to the SIP adjacency SipAdj1 if it receives a 415 (media unsupported) or 480 (temporarily unavailable) error:
The following example shows how to configure H.323 to retry routing to the H.323 adjacency h323Adj1 if it receives a noBandwidth or securityDenied error. Note that for multiple error codes, each hunting trigger must be configured on a separate line:
import-map
To configure flexible policy handling by a BGP route server, use the import-map command in route server context address family configuration mode. To remove the route server’s flexible policy handling, use the no form of this command.
Syntax Description
Name of the route map that controls which routes will be added to the route server client virtual table. |
Command Default
No import map exists and no flexible policy handling by a route server exists.
Command Modes
Route server context address family configuration (config-router-rsctx-af)
Command History
|
|
|
|---|---|
Usage Guidelines
Use this command if your BGP route server needs to support flexible policies.
In order to configure flexible policy handling, you must create a route server context, which includes an import map. The import map references a standard route map. You may match on nexthop, AS path, communities, and extended communities.
Note
Do not confuse the Do not confuse the import-map command with the import map command in VRF configuration submode, which configures an import route map for a VPN routing and forwarding (VRF) instance.
Examples
In the following example, the local router is a BGP route server. Its neighbors at 10.10.10.12 and 10.10.10.13 are its route server clients. A route server context named ONLY_AS27_CONTEXT is created and applied to the neighbor at 10.10.10.13. The context uses an import map that references a route map named only_AS27_routemap. The route map matches routes permitted by access list 27. Access list 27 permits routes that have 27 in the autonomous system path.
Related Commands
ims media-service
To configure a CAC table to allow the use of media resources and 3rd party transcoding resources as well as Rx resources, use the ims media-service command in CAC table entry configuration mode. To return to the default condition where only Rx is used, use the no form of this command.
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 modes required to run the command.
By default, only Rx is in use, and media and 3rd-party transcoding resources cannot be used. When IMS media service is configured, Rx is used as well as media resources and 3rd party transcoding resources.
NoteMedia bypass takes precedence over IMS media service configuration. Media bypass takes precedence over IMS media service configuration.
Examples
The following example shows how to configure a CAC table to allow the use of media resources and 3rd party transcoding resources as well as Rx resources.
Related Commands
ims pani
To configure the P-Access-Network-Info (PANI) header process preference for an adjacency, use the ims pani command in adjacency SIP configuration mode. To remove a PANI header process preference from an adjacency, use the no form of this command.
ims pani [ received | rx | received rx | rx received ]
no ims pani [ received | rx | received rx | rx received ]
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.
NoteThis command may be used when the adjacency is active, but it will only apply to new calls. It will not effect existing calls. This command may be used when the adjacency is active, but it will only apply to new calls. It will not effect existing calls.
Examples
The following example shows how to configure the PANI header process preference for an adjacency:
Related Commands
ims realm
To configure an IMS realm for use by either an IMS Rx interface or an IMS Rf interface, use the ims realm command in adjacency SIP configuration mode. To remove an IMS realm, use the no form of this command.
Syntax Description
Specifies a case sensitive, unique name for the realm. The maximum length is 63 characters. |
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 IMS realm for use by an IMS Rx interface:
Related Commands
ims rf
To enable the IP Multimedia Subsystem (IMS) Rf interface for an access adjacency on the Cisco Session Border Controller (SBC), use the ims rf command in the SBC SBE adjacency SIP configuration mode. To disable the IMS Rf interface for an access adjacency, use the no form of this command.
Syntax Description
Command Default
Command Modes
SBC SBE 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
This command cannot be modified unless the operational state of the access adjacency is down.
Examples
The following example shows how to disable the IMS Rf interface for an access adjacency on the SBC:
ims rx
To configure an IMS Rx interface for access adjacency, use the ims rx command in adjacency SIP configuration mode. To remove an IMS Rx interface, use the no form of this command.
Syntax Description
Command Default
When PCRF is not specified, Rx messages are routed by realm.
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.
NoteThis command can only be used when the operational state of the adjacency is down. This command can only be used when the operational state of the adjacency is down.
Examples
The following example shows how to configure an IMS Rx interface for access adjacency:
Related Commands
ims rx preliminary-aar-forbid
To prevent preliminary AAR messages from being sent in an IMS Rx session, use the ims rx preliminary-aar-forbid command in CAC table entry configuration mode. To return to the default condition where preliminary AAR messages are sent, use the no form of this command.
no ims rx preliminary-aar-forbid
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 modes required to run the command.
Examples
The following example shows how to prevent preliminary AAR messages from being sent in an IMS Rx session:
Related Commands
inbound secure
To configure the incoming calls from an H.323 adjacency as secure calls, use the inbound secure command in the H.323 Adjacency configuration mode. To restore the insecure status to the incoming calls, use the no form of this command.
Syntax Description
Command Default
Command Modes
H.323 Adjacency configuration mode (config-sbc-sbe-adj-h323)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Routers. |
Usage Guidelines
To ensure that the calls coming from an H323 adjacency are treated as secure calls, define the incoming calls from an H.323 adjacency as secure calls using the inbound secure command in the H.323 Adjacency configuration mode. By default, all incoming calls are insecure calls.
To configure the incoming secure calls as not secured, use the no inbound secure command from H.323 adjacency configuration mode.
NoteIf an H.323 adjacency is configured as untrusted, you cannot configure an incoming calls as secure calls. If an H.323 adjacency is configured as untrusted, you cannot configure an incoming calls as secure calls.
Examples
The following example shows how to configure incoming calls from an H.323 adjacency as secure calls:
Related Commands
|
|
|
|---|---|
inherit profile
To configure a global inherit profile for the SIP adjacency, use the inherit profile command in adjacency SIP configuration mode. To deconfigure the global inherit profile, use the no form of this command.
inherit profile { preset-access | preset-core | preset-ibcf-ext-untrusted | preset-ibcf-external | preset-ibcf-internal | preset-p-cscf-access | preset-p-cscf-core | preset-peering | preset-standard-non-ims}
Syntax Description
Command Default
Command Modes
Adjacency SIP configuration (config-sbc-sbe-adj-sip)
Command History
|
|
|
|---|---|
The 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.
This adjacency-specific configuration overrides any global configuration of the adjacency that was configured using the sip inherit profile command.
Examples
The following example shows how the inherit profile command is used to configure a P-CSCF-access inherit profile on a SIP adjacency:
Related Commands
|
|
|
|---|---|
interwork cost
To specify the resource cost for an audio stream using inband DTMF interworking or to specify the resource cost for an audio or video stream using SRTP encryption and decryption, use the transcode cost command in the SBE media policy configuration mode. To remove this configuration, use the no form of this command.
interwork {inband-dtmf | srtp} cost number
no interwork {inband-dtmf | srtp} cost
Syntax Description
Command Default
The default resource cost for an audio stream using inband DTMF interworking is 4. Similarly, the default resource cost for an audio or video stream using SRTP encryption and decryption is 15. When you use the no form of this command, the resource cost is changed to the default value.
Command Modes
SBE media policy configuration (config-sbc-sbe-media-pol)
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 interwork cost command is used to set the resource cost for an audio stream using inband DTMF interworking to 8. This command is also used to set the resource cost for an audio or video stream using SRTP encryption and decryption to 20.
Related Commands
interwork maximum
To specify the maximum number of media streams that can use the inband DTMF interworking resource or the SRTP interworking resource at any point of time, use the interwork maximum command in the SBE media policy configuration mode. To remove the maximum limit, use the no form of this command.
interwork {inband-dtmf | srtp} maximum number
no interwork {inband-dtmf | srtp} maximum
Syntax Description
Maximum number of media streams that can use the interworking service specified in the command. |
Command Default
The default maximum number of media streams that can use the inband DTMF interworking resource or the SRTP interworking resource at any point of time is 4294967295. When you use the no form of this command, any maximum limit set earlier is changed to this default value.
Command Modes
SBE media policy configuration (config-sbc-sbe-media-pol)
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
In the following example, the interwork maximum command is used to set the maximum number of calls that use the SRTP interworking service at any point of time to 500:
Related Commands
invite-timeout
To configure the time that SBC waits for a final response to an outbound SIP invite request, use the invite-timeout command in IP timer configuration mode. To return to the default value, use the no form of this command.
invite-timeout {interval-value}
Syntax Description
Time, in seconds, SBC waits before timing out an outbound invite request. |
Command Default
The default wait interval is 180 seconds. If no response is received during that time, an internal 408 request timeout response is generated and is sent to the caller.
Command Modes
SIP timer (config-sbc-sbe-sip-tmr)
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 a configuration is loaded on top of an active configuration, warnings are generated to notify that the configuration cannot be modified. If you must modify the entire configuration by loading a new one, please remove the existing configuration first.
Examples
The following example shows how to configure the SBC to time out invite transactions after 60 seconds:
Related Commands
|
|
|
|---|---|
Configures the time period that SBC retains negative UDP responses to invite requests. |
ipsec maximum
To specify the maximum number of endpoint registrations that can use IPsec encryption and decryption on their signaling link to the SBC or the maximum number of calls that can use IPsec-protected signaling, use the ipsec maximum command in the SBE CAC table CAC policy configuration mode. To remove this configuration, use the no form of this command.
ipsec maximum {registers | calls} number
no ipsec maximum {registers | calls}
Syntax Description
Command Default
The default maximum number of media streams that can use IPsec encryption and decryption on their signaling link or that can use IPsec-protected signaling, at any point of time, is 4294967295. When you use the no form of this command, any maximum limit set earlier is changed to this default value.
Command Modes
SBE CAC table CAC policy 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
In the following example, the ipsec maximum command is used to set the maximum number of media streams that can use IPsec encryption and decryption on their signaling link to 200. In addition, the command is used to set the maximum number of media streams that can use IPsec-protected signaling to 80.
Related Commands
ipv4
To create an IPv4 address within a DBE media address pool, use the ipv4 command in media address configuration mode. To delete an IPv4 address within a DBE media address pool, use the no form of this command.
ipv4 ipv4_address [vrf vrf-name ]
no ipv4 ipv4_address [vrf vrf-name ]
Syntax Description
Command Default
Command Modes
Media address (config-sbc-dbe-media-address)
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 address 10.0.1.1 for use both for non-VPN media and for media to or from vpn3:
ipv4 (blacklist)
To enter the mode for applying blacklisting options to a single IP address or for configuring the default event limits for the source addresses in a given VPN (where the IP address is under the VPN), use the ipv4 command in the SBE blacklist configuration mode. Use the no form of the command to remove the blacklist entry for an address.
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 applying blacklisting options to a single IP address:
Related Commands
ipv4 (SBE H.248)
To configure an SBE to use a given IPv4 H.248 control address, use the ipv4 command in H.248 control address configuration mode. To delete a given IPv4 H.248 control address, use the no form of this command.
Syntax Description
Command Default
Command Modes
H.248 control address (config-sbc-sbe-ctrl-h248)
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 SBE to use a given IPv4 H.248 control address:
Related Commands
|
|
|
|---|---|
Configures an SBE to use a certain transport for H.248 communications. |
ip access-list
To define an IP access list or object-group access control list (ACL) by name or number or to enable filtering for packets with IP helper-address destinations, use the ip access-list command in global configuration mode. To remove the IP access list or object-group ACL or to disable filtering for packets with IP helper-address destinations, use the no form of this command.
ip access-list { { standard | extended } { access-list-name | access-list-number } |
helper egress check }
no ip access-list { { standard | extended } { access-list-name | access-list-number } |
helper egress check }
Syntax Description
Command Default
No IP access list or object-group ACL is defined, and outbound ACLs do not match and filter IP helper relayed traffic.
Command Modes
Command History
Usage Guidelines
Use this command to configure a named or numbered IP access list or an object-group ACL. This command places the router in access-list configuration mode, where you must define the denied or permitted access conditions by using the deny and permit commands.
Specifying the standard or extended keyword with the ip access-list command determines the prompt that appears when you enter access-list configuration mode. You must use the extended keyword when defining object-group ACLs.
You can create object groups and IP access lists or object-group ACLs independently, which means that you can use object-group names that do not yet exist.
Named access lists are not compatible with Cisco IOS software releases prior to Release 11.2.
Use the ip access-group command to apply the access list to an interface.
The ip access-list helper egress check command enables outbound ACL matching for permit or deny capability on packets with IP helper-address destinations. When you use an outbound extended ACL with this command, you can permit or deny IP helper relayed traffic based on source or destination User Datagram Protocol (UDP) ports. The ip access-list helper egress check command is disabled by default; outbound ACLs will not match and filter IP helper relayed traffic.
Examples
The following example defines a standard access list named Internetfilter:
The following example shows how to create an object-group ACL that permits packets from the users in my_network_object_group if the protocol ports match the ports specified in my_service_object_group:
The following example shows how to enable outbound ACL filtering on packets with helper-address destinations:
Related Commands
ip host
To resolve host names to IP addresses in evaluation cases where a DNS server is not available, use the ip host command in Global configuration mode. To return to the default value, use the no form of this command.
no ip host hostname ip_address
Syntax Description
Command Default
The default wait interval is 180 seconds. If no response is received during that time, an internal 408 request timeout response is generated and is sent to the caller.
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.
If a configuration is loaded on top of an active configuration, warnings are generated to notify that the configuration cannot be modified. If you must modify the entire configuration by loading a new one, please remove the existing configuration first.
Examples
The following example shows how to configure the SBC to time out invite transactions after 60 seconds:
ip multicast-routing
To enable IP multicast routing, use the ip multicast-routing command in global configuration mode. To disable IP multicast routing, use the no form of this command.
ip multicast-routing [ vrf vrf-name ] [ distributed ]
no ip multicast-routing [ vrf vrf-name ]
ip multicast-routing {[ vrf vrf-name ] distributed }
no ip multicast-routing {[ vrf vrf-name ] distributed }
Syntax Description
(Optional) Enables IP multicast routing for the Multicast VPN routing and forwarding (MVRF) instance specified for the vrf-name argument. |
|
Command Default
Command Modes
Command History
Usage Guidelines
When IP multicast routing is disabled, the Cisco IOS software does not forward any multicast packets.
The optional distributed keyword for this command is not supported in Cisco IOS XE Release 3.2S.
Either the distributed keyword or the vrf vrf-name distributed keyword and argument combination for this command is required in Cisco IOS XE Release 3.3S and later releases.
NoteFor IP multicast, after enabling IP multicast routing, PIM must be configured on all interfaces. Disabling IP multicast routing does not remove PIM; PIM still must be explicitly removed from the interface configurations. For IP multicast, after enabling IP multicast routing, PIM must be configured on all interfaces. Disabling IP multicast routing does not remove PIM; PIM still must be explicitly removed from the interface configurations.
Examples
The following example shows how to enable IP multicast routing:
The following example shows how to enable IP multicast routing on a specific VRF:
Router(config)# ip multicast-routing vrf vrf1
The following example shows how to disable IP multicast routing:
Router(config)# no ip multicast-routing
The following example shows how to enable MDS in Cisco IOS XE Release 3.3S a specific VRF:
Router(config)# ip multicast-routing vrf vrf1 distributed
Related Commands
|
|
|
|---|---|
ip multicast rpf mofrr
To enable a Provider Edge (PE) router to perform Reverse Path Forwarding (RPF) lookups using multicast only fast re-route (MoFRR) on an IP address of the exit router in the global table or a specific VPN, use the ip multicast rpf mofrr command in global configuration mode. To disable this functionality, use the no form of this command.
ip multicast [vrf vrf-name ] rpf mofrr {access-list-number | access-list-name} [sticky]
no ip multicast [vrf vrf-name ] rpf mofrr {access-list-number | access-list-name} [sticky]
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Use the ip multicast rpf mofrr command to enable a PE router to perform RPF lookups using MoFRR on an IP address of the exit router in the global table or a specific VPN. MoFRR uses standard Protocol Independent Multicast (PIM) join messages to set up a primary and a secondary multicast forwarding path by establishing a primary and a secondary RPF interface on each router that receives a PIM join message. Data is received from both the primary and backup paths. If the router detects a forwarding error in the primary path, it switches RPF to the secondary path and immediately has packets available to forward out to each outgoing interface.
MoFRR accepts extended ACLs only. It does not accept standard ACLs.
Examples
The following example shows how to enable a PE router to perform RPF lookups using MoFRR for the mroute matching the ACL numbered 150:
Related Commands
|
|
|
|---|---|
Displays information about the multicast routing (mroute) table. |
|
Displays the information that IP multicast routing uses to perform the RPF check for a multicast source. |
ip multicast rpf select topology
To associate a multicast topology with a multicast group with a specific mroute entry, use the ip multicast rpf select topology command in global configuration mode. To disable the functionality, use the no form of this command.
ip multicast rpf select topology { multicast | unicast } topology-name access-list-number
no ip multicast rpf select topology { multicast | unicast } topology-name access-list-number
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The ip multicast rpf select topology command associates a multicast topology with an (S,G) mroute entry. One (S,G) mroute entry can be associated with multiple topologies. During RPF lookup, PIM MT-ID will be used (smaller ID has higher priority) to select a topology.
One access list could be associated with multiple (S,G) mroute entries. The sequence number in the access list is used to determine the order of (S,G) mroute entry lookup within the access list.
Examples
The following example shows how to associate a multicast topology with an (S,G) mroute entry:
Related Commands
|
|
|
|---|---|
Enables debugging output for IP multicast stream topology creation events, deletion events, and IP multicast stream ACL matching events. |
|
ip multicast topology
To configure topology selection for multicast streams, use the ip multicast topology command in global configuration mode. To disable the functionality, use the no form of this command.
ip multicast topology { multicast | unicast } topology-name tid topology-number
no ip multicast topology { multicast | unicast } topology-name tid topology-number
Syntax Description
Command Default
All multicast streams are associated with the multicast base topology.
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The ip multicast topology command configures topology selection for multicast streams, which is usually only required for first hop and last hop routers (and may not be required for transit routers in between). The stream, specified by an extended IP access list, can be source based, group based, or a combination of both. The sequence number in the access list will decide the order of the (S,G) mroute entries.
Examples
The following example shows how to configure topology selection for multicast streams:
Related Commands
ip precedence
To configure an IP precedence with which to mark IP packets belonging to the given QoS profile, use the ip precedence command in the appropriate configuration mode. To return to the default behavior, use the no form of this command.
Syntax Description
Specifies the IP precedence with which to mark packets. Range is 0 to 7. |
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 to mark IP packets with a precedence of 1:
ip service reflect
To match and rewrite multicast packets routed onto a Vif1 interface, use the ip service reflect command in interface configuration mode. To disable this feature, use the no form of this command.
ip service reflect input-interface destination destination-address to new-destination-address mask-len number source new-source-address
no ip service reflect input-interface destination destination-address to new-destination-address mask-len number source new-source-address
Syntax Description
Command Default
Command Modes
Interface configuration (config-if)
Command History
|
|
|
|---|---|
This command was integrated into Cisco IOS Release 12.2(33)SXI4. |
|
Usage Guidelines
Use the ip service reflect command to match and rewrite multicast packets routed onto a Vif1 interface.
The matched and rewritten packet is sent back into Cisco multicast packet routing, where it is handled like any other packet arriving from an interface.
More than one multicast service reflection operation can be configured to match the same packet, allowing you to replicate the same received traffic to multiple destination addresses.
Examples
The following example shows how to translate any multicast packet with a destination address of 239.1.1.0/24 to a destination of 239.2.2.0/24 with a new source address of 10.1.1.2. For example, a packet with a source and destination of (10.10.10.10, 239.1.1.15) would be translated to (10.1.1.2, 239.2.2.15).
ip TOS (session border controller)
To configure an IP ToS (type of service) with which to mark IP packets belonging to the QoS profile, use the ip TOS command in the appropriate configuration mode. To return the QoS profile to setting the default IP ToS, use the no form of this command.
Syntax Description
Specifies the IP ToS with which to mark packets. This may be a value of 0 (normal service) or a bit field consisting of one or more of the following bits: |
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 an IP TOS:
ip wccp outbound-acl-check
To check the outbound access control list (ACL) for Web Cache Communication Protocol (WCCP), use the ip wccp outbound-acl-check command in global configuration mode. To disable the outbound check, use the no form of this command.
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
This command performs the same function as the ip wccp check acl outbound command.
Examples
The following example shows how to configure a router to check the outbound ACL for WCCP:
Related Commands
|
|
|
|---|---|
Enables support of the WCCP service for participation in a service group. |
|
ip wccp redirect
To enable packet redirection on an outbound or inbound interface using Web Cache Communication Protocol (WCCP), use the ip wccp redirect command in interface configuration mode. To disable WCCP redirection, use the no form of this command.
ip wccp [ vrf vrf-name ] { web-cache | service-number } redirect { in | out }
no ip wccp [ vrf vrf-name ] { web-cache | service-number } redirect { in | out }
Syntax Description
Command Default
Command Modes
Interface configuration (config-if)
Command History
Usage Guidelines
WCCP transparent caching bypasses Network Address Translation (NAT) when fast (Cisco Express Forwarding [CEF]) switching is enabled. To work around this situation, WCCP transparent caching should be configured in the outgoing direction, fast/CEF switching enabled on the Content Engine interface, and the ip wccp web-cache redirect out command specified. Configure WCCP in the incoming direction on the inside interface by specifying the ip wccp redirect exclude in command on the router interface facing the cache. This prevents the redirection of any packets arriving on that interface.
You can also include a redirect list when configuring a service group and the specified redirect list will deny packets with a NAT (source) IP address and prevent redirection. Refer to the ip wccp command for configuration of the redirect list and service group.
The ip wccp redirect in command allows you to configure WCCP redirection on an interface receiving inbound network traffic. When the command is applied to an interface, all packets arriving at that interface will be compared against the criteria defined by the specified WCCP service. If the packets match the criteria, they will be redirected.
Likewise, the ip wccp redirect out command allows you to configure the WCCP redirection check at an outbound interface.
Tips Be careful not to confuse the ip wccp redirect {out | in} interface configuration command with the ip wccp redirect exclude in interface configuration command.
NoteThis command has the potential to affect the This command has the potential to affect the ip wccp redirect exclude in command. (These commands have opposite functions.) If you have ip wccp redirect exclude in set on an interface and you subsequently configure the ip wccp redirect in command, the “exclude in” command will be overridden. The opposite is also true: configuring the “exclude in” command will override the “redirect in” command.
Examples
In the following configuration, the multilink interface is configured to prevent the bypassing of NAT when fast/CEF switching is enabled:
The following example shows how to configure a session in which reverse proxy packets on Ethernet interface 0 are being checked for redirection and redirected to a Cisco Cache Engine:
The following example shows how to configure a session in which HTTP traffic arriving on Ethernet interface 0/1 is redirected to a Cisco Cache Engine:
Related Commands
|
|
|
|---|---|
Displays the usability status of interfaces that are configured for IP. |
|
ip wccp source-interface
To specify the interface that Web Cache Communication Protocol (WCCP) uses as the preferred router ID and generic routing encapsulation (GRE) source address, use the ip wccp source-interface command in global configuration mode. To enable the WCCP default behavior for router ID selection, use the no form of this command.
ip wccp [ vrf vrf-name ] source-interface source-interface
no ip wccp [ vrf vrf-name ] source-interface
Syntax Description
(Optional) Specifies a virtual routing and forwarding instance (VRF) to associate with a service group. |
|
Command Default
If this command is not configured, WCCP selects a loopback interface with the highest IP address as the router ID.
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Use this command to set the interface from which WCCP may derive the router ID and GRE source address. The router ID must be a reachable IPv4 address.
The interface identified by the source-interface argument must be assigned an IPv4 address and be operational before WCCP uses the address as the router ID. If the configured source interface cannot be used to derive the WCCP router ID, a Cisco IOS error message similar to the following is displayed:
The reason field in the error output indicates why the interface has been ignored and can include the following:
- VRF mismatch —The VRF domain associated with the interface does not match the VRF domain associated with the WCCP command.
- interface does not exist —The interface has been deleted.
- no address —The interface does not have a valid IPv4 address.
- line protocol down —The interface is not fully operational.
This command provides control only of the router ID and GRE source address. This command does not influence the source address used by WCCP control protocol (“Here I Am” and Removal Query messages). The WCCP control protocol is not bound to a specific interface and the source address is always selected based on the destination address of an individual packet.
Examples
The following example shows how to select Gigabit Ethernet interface 0/0/0 as the WCCP source interface:
Related Commands
ip wccp version
To specify the version of Web Cache Communication Protocol (WCCP), use the ip wccp version command in global configuration mode.
Syntax Description
Specifies Web Cache Communication Protocol Version 1 (WCCPv1). |
|
Specifies Web Cache Communication Protocol Version 2 (WCCPv2). |
Command Default
Command Modes
Command History
Usage Guidelines
Configuring this command does not have any impact on Cisco ASR 1000 Series Routers because these routers support only WCCPv2. WCCPv2 is enabled by default on Cisco ASR 1000 series routers when a service group is configured or a service group is attached to an interface.
Examples
In the following example, the user changes the WCCP version from the default of WCCPv2 to WCCPv1, starting in privileged EXEC mode:
Related Commands
|
|
|
|---|---|
Enables support of the WCCP service for participation in a service group. |
|
key (session border controller)
To configure the authentication key of the accounting and authentication servers, use the key command in the appropriate server configuration mode. To disable any previously set authentication key, use the no form of this command.
Syntax Description
Specifies the authentication key. This is only valid if authentication is turned on. |
Command Default
Command Modes
Server accounting (config-sbc-sbe-acc-ser)
Server authentication (config-sbc-sbe-auth)
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 acctsvr accounting server with the HJ5689 authentication key and acctsvr2 accounting server with the cisco authentication key on mySbc for RADIUS client instance radius1:
ldr-check
To configure the time of day (local time) to run the Long Duration Check (LDR), use the ldr-check command in SBE billing configuration mode. To return to 00:00, use the no form of this command.
Syntax Description
Time in hours and minutes using a 24-hour clock. The range of the HH argument is 0 to 23. The range of the MM argument is 0 to 59. |
Command Default
Command Modes
SBE billing configuration (config-sbc-sbe-billing)
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 a configuration is loaded on top of an active configuration, warnings are generated to notify that the configuration cannot be modified. If you must modify the entire configuration by loading a new one, please remove the existing configuration first.
Examples
The following example shows how to configure the remote long-duration-call check to occur at 10.30 p.m., to specify the time each day when SBC should check for any call whose duration is over 24 hours:
Related Commands
|
|
|
|---|---|
Activates the billing functionality after configuration is committed. |
|
ldr-check (XML billing)
To configure the time at which to check all calls over 24-hour-long, use the ldr-check hour min command in the SBE billing XML configuration mode. To disable the configuration, 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
It is important to take a note of calls that are more than 24-hours-long. To report long duration calls that are more than 24 hours, use the ldr-check hour min command from SBE billing XML configuration mode. The initial value is inherited from the value in the Billing-MGR table. The hour and minute values must be set using the 24-hour clock. The no form of the command does not require any parameter. The default duration at which LDR checks are performed is 00 hour and 00 minutes.
Examples
The following example shows how to configure the time 23 hour and 30 minutes to check long duration calls:
Related Commands
|
|
|
|---|---|
Configures the time at which long duration records are checked. |
load-order
To specify the load order of a script in a script set, use the load-order command in the SBE script-set script configuration mode.
Syntax Description
Order in which the script must be loaded. The range is from 1 to 4294967295. |
Command Default
The default load order number of the first script set that you configure without using the load-order command, is 100. For scripts that are subsequently added without using the load-order command, the default order index number is set in multiples of 100, that is, 200, 300, 400, and so on.
Command Modes
SBE script-set script configuration (config-sbc-sbe-scrpset-script)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 100 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 scripts are loaded in ascending order of the order index number. For example, a script with the order index number 4 is loaded before a script with the order index number 6.
Examples
In the following example, the load-order command is used to specify 2 as the load order:
Related Commands
local-address ipv4
To configure the local IPv4 address that appears in the CDR, use the local-address ipv4 command in SBE billing configuration mode. To deconfigure the local IPV4 address, use the no form of this command.
local-address ipv4 { A.B.C.D. }
Syntax Description
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.
If a configuration is loaded on top of an active configuration, warnings are generated to notify that the configuration cannot be modified. If you must modify the entire configuration by loading a new one, please remove the existing configuration first.
NoteThis field cannot be reconfigured when billing is active. This field cannot be reconfigured when billing is active.
Examples
The following example shows how to configure the local-address to 10.20.1.1 for the billing:
Related Commands
|
|
|
|---|---|
Configures the time of day (local time) to run the Long Duration Check (LDR). |
|
local-address ipv4 (packet-cable)
To configure the local address of the packet-cable billing instance, use the local-address ipv4 command in the packetcable-em configuration mode. To disable the local address, 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.
If no address is configured, the SBC uses any local address.
Examples
The following example shows how to enter the billing mode for mySbc:
Related Commands
local-id host
To configure the local identify name on a SIP adjacency, use the local-id command in adjacency SIP configuration mode. To remove this configuration, use the no form of this command.
Syntax Description
Specifies the local identity name to present on outbound SIP messages. |
Command Default
When the name field is not set, the local signaling address is used in SIP messages.
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 set the SIP local identity of SIP adjacency SipToIsp42 to mcarthur:
local-jitter-ratio
To specify the percentage of calls that must be used to calculate the local jitter ratio, use the local-jitter-ratio command in the adjacency H.323 configuration mode or adjacency SIP configuration mode. To remove this configuration, use the no form of this command.
local-jitter-ratio call-percentage
Syntax Description
Percentage of calls. The range is from 0 to 1000. For example, if you enter 305 as the value of call-percentage , the SBC uses 30.5 percent of the calls for measuring local jitter. |
Command Default
By default, the value of call-percentage is 0 because jitter determination is a performance drain on the MPF. When the value is 0, measurements of the jitter ratio and the MOS-CQE are not available for the adjacency.
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
In the following example, the local-jitter-ratio command is used to specify that 20.5 percent of the calls must be used to calculate the local jitter ratio:
Related Commands
local-port (session border controller)
To configure a data border element (DBE) to use a specific local port when connecting to the default media gateway controller (MGC), use the local-port command in either SBC configuration mode or VDBE configuration mode. To disable this configuration, use the no form of this command.
Syntax Description
Command Default
Default is to use local port 2944. Note that use-any-local-port should not be used when there is a redundant Session Border Controller (SBC). If it is, the connection to the MGC may be lost with an SBC switch over.
Command Modes
VDBE configuration (config-sbc-dbe-vdbe) for distributed SBC
Command History
|
|
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers for distributed SBC. |
Usage Guidelines
The Examples section shows the hierarchy of modes required to run the command.
The local port cannot be modified after any controller has been configured on the DBE. You must delete the controller before you can modify or configure the local port.
Examples
The following example creates a DBE service on a distributed SBC called mySbc and configures the DBE to use the local port number 5090:
The following example creates a DBE service on a unified SBC called mySbc and configures the DBE to use the local port number 5090:
Related Commands
|
|
|
|---|---|
Configures a DBE to use any available local port when connecting to the default MGC. |
location-id (session border controller)
To configure the location ID for a DBE service of the Session Border Controller (SBC), use the location-id command in SBC-DBE configuration mode. To set the location ID to the default, use the no form of this command.
Syntax Description
The location ID of the DBE. The location ID range is from -1 to 65535. |
Command Default
Command Modes
SBC-DBE configuration (config-sbc-dbe)
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 no form of the command does not take an argument and sets the location-id to the default, which is 0xFFFFFFFF (-1).
A location ID is configured on each DBE. The SBE may associate endpoints with a particular location ID and then use the location IDs to route calls between different DBEs.
Use the dbe command to enter into SBC-DBE configuration mode prior to entering the location-id command.
Examples
The following example creates a DBE service on an SBC called mySbc, enters into SBC-DBE configuration mode, and sets the location ID for a DBE to be 1:
Related Commands
|
|
|
|---|---|
Creates the DBE service on a SBC and enters into DBE-SBE configuration mode. |
max-call-rate-per-scope
To configure the maximum call rate for an entry in an admission control table and specify the averaging period to be used in rate calculation, use the max-call-rate-per-scope command in the CAC table configuration mode. To unconfigure the maximum call rate for an entry in an admission control table and to remove the averaging period, use the no form of this command.
max-call-rate-per-scope limit [ averaging-period period-num ]
no max-call-rate-per-scope limit [ averaging-period period-num ]
Syntax Description
Command Default
Command Modes
CAC table configuration (config-sbc-sbe-cacpolicy-cactable)
Command History
Usage Guidelines
Only one parameter should be supplied for each command.
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 maximum call rate for an entry CAC table 1:
Related Commands
max-connections
To configure the maximum number of SIP connections that will be made to each remote address, use the max-channels command in SBE configuration mode. To set this to an unlimited number of connections, use the no form of this command.
max- connections number-of-connections
no max- connections number-of-connections
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.
Examples
The following command configures the maximum number of connections to each remote address to 1:
Related Commands
max-in-call-msg-rate
To configure the maximum in-call rate and specify the averaging period to be used in rate calculation, use the max-in-call-msg-rate command in the CAC table entry configuration mode. To deconfigure the maximum in-call rate and remove the specified averaging period, use the no form of this command.
max-in-call-msg-rate limit [ averaging-period period-num ]
no max-in-call-msg-rate limit [ averaging-period period-num ]
Syntax Description
Command Default
Command Modes
CAC table entry configuration (config-sbc-sbe-cacpolicy-cactable-entry)
Command History
Usage Guidelines
In-call messages include all the messages within the context of a call, including provisional responses during call setup and call renegotiation messages, but not including call setup or tear-down messages.
When configuring the maximum rate of in-call messages in Call Admission Control (CAC), note that the following messages are not rate-limited:
- SIP INVITE requests: 200 responses and ACK messages
- SIP PRACK messages and response
- SIP BYE messages and responses
- Any SIP message with nonduplicate SDP on
- For H.323 calls: Q.931 SETUP, Q.931 CONNECT, and Q.931 RELEASE messages
The Cisco Unified Border Element (SP Edition) will reject the in-call messages when the rate exceeds the rate that is specified in the CAC.
The averaging period must be configured using the cac-policy-set command before the averaging period is specified in this command.
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 command shows how to configure the maximum number of connections to each remote address to 1:
Related Commands
max-num-calls
To configure the maximum number of calls of an entry in an admission control table, use the max-num-calls command in CAC table configuration mode. To delete the maximum number of calls in the given entry in the admission control table, use the no form of this command.
Syntax Description
Positive integer specifying the maximum number of calls to permit at the relevant scope. |
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 maximum number of calls for an entry in the new admission control table MyCacTable:
Related Commands
max-out-call-msg-rate
To configure the maximum out-call rate and specify the averaging period to be used in rate calculation, use the max-out-call-msg-rate command in the CAC table entry configuration mode. To disable the maximum out-call rate and remove the specified averaging period, use the no form of this command.
max-out-call-msg-rate limit [ averaging-period period-num ]
no max-out-call-msg-rate limit [ averaging-period period-num ]
Syntax Description
Command Default
Command Modes
CAC table entry configuration (config-sbc-sbe-cacpolicy-cactable-entry)
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 averaging period must be configured using the cac-policy-set command before the averaging period is specified in this command.
Examples
The following command shows how to configure the maximum number of connections to each remote address to 1:
Related Commands
max-recursive-depth
To configure the maximum number of recursive ENUM look-ups for non-terminal Resource Records (RR), use the max-recursive-depth command in ENUM configuration mode. To return the maximum number of recursive ENUM look-ups to the default value, 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 maximum number of recursive ENUM look-ups for non-terminal Resource Records (RR).
Related Commands
max-regs-rate-per-scope
To configure the maximum call number of subscriber registrations for an entry in an admission control table and specify the averaging period to be used in rate calculation, use the max-regs-rate-per-scope command in the CAC table configuration mode. To delete the maximum number of subscriber registrations in a given entry in the admission control table and to remove the averaging period, use the no form of this command.
max-regs-rate-per-scope limit [ averaging-period period-num ]
no max-regs-rate-per-scope limit [ averaging-period period-num ]
Syntax Description
Command Default
Command Modes
CAC table configuration (config-sbc-sbe-cacpolicy-cactable)
Command History
Usage Guidelines
Only one parameter should be supplied for each command.
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 averaging period must be configured using the cac-policy-set command before the averaging period is specified in this command.
Examples
The following example shows how to configure the maximum registration rate for an entry in the new admission control table MyCacTable:
Related Commands
max-regs
To configure the maximum number of subscriber registrations of an entry in an admission control table, use the max-regs command in CAC table configuration mode. To delete the maximum number of subscriber registrations in the given entry in the admission control table, use the no form of this command.
Syntax Description
Positive integer specifying the maximum number of subscriber registrations to permit at the relevant scope. |
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 maximum number of subscriber registrations for an entry in the new admission control table MyCacTable:
Related Commands
max-responses
To configure the maximum number of ENUM records returned to the routing module, use the max-response command in ENUM configuration mode. To return the number of records returned to the default value, use the no form of this command.
Syntax Description
Maximum number of ENUM records. The range is 0 to 2147483647. |
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 maximum number of ENUM records returned to the routing module:
Related Commands
max-updates
To configure the maximum call updates for an entry in an admission control table, use the max-updates command in CAC table configuration mode. To delete the maximum call updates in the given entry in the admission control table, use the no form of this command.
Syntax Description
Positive integer specifying the maximum number of updates to call media to permit at the relevant scope. |
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 maximum number of call updates for an entry in the new admission control table MyCacTable:
Related Commands
media
To enable the media bypass feature or the media down detect feature on a Border Access Controller (BAC) adjacency, use the media command in the H248 BAC adjacency configuration mode. To disable the media bypass feature or the media down detect feature on 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. |
Examples
The following example shows how to enable the media bypass feature on a BAC adjacency:
media-address
To add an IPv4 or IPv6 address to the set of addresses that can be used by the data border element (DBE) as a local media address, use the media-address command in either the SBC configuration mode or the SBC-DBE configuration mode. To remove an IPv4 or IPv6 address from the set of local media addresses, use the no form of this command.
media-address { ipv4 | ipv6 } { addr} [nat-mode twice-nat | vrf vrf-name | managed-by { dbe | mgc } ]
no media-address { ipv4 | ipv6 } { addr} [nat-mode twice-nat | vrf vrf-name | managed-by { dbe | mgc } ]
Syntax Description
Command Default
Command Modes
SBC configuration (config-sbc) for unified SBC
SBC-DBE configuration (config-sbc-dbe) for distributed SBC
Voice service VoIP for TDM gateways and CUBE(config-voi-serv)
Command History
Usage Guidelines
Use the media-address command to configure a local media address for the traffic arriving on the DBE for each IP address that you specified under the SBC virtual interface with the ip address command.
After you have configured a local media address, it cannot be modified while the DBE service is active. You must first deactivate the DBE with the no activate command.
Media address is a pool of IP addresses on the DBE for the media relay functionality. A pool of addresses is defined for the global VPN to which the DBE is attached. All the vDBEs within the DBE draw media addresses from this pool.
Examples
The following example for a unified SBC shows how the IP address 10.0.1.1, which is configured on an SBC interface, is used when media traffic arrives on the DBE from the global VPN:
The following example for a distributed SBC shows that the IPv4 address 10.0.1.1, which is configured on an SBC interface, is the local address used when media traffic arrives on the DBE, and is reserved for Twice-NAT pinholes:
The following example for a distributed SBC shows that the IP address 10.0.1.1, which is an address configured on an SBC interface, is used when media traffic arrives on the DBE from the global VPN:
The following example for a distributed SBC tries to delete the media address 1.1.1.1 before deactivating the DBE, and receives an error message:
Router (conf-voi-serv)# media-address range 1.3.6.3 1.3.6.4
Related Commands
media-address ipv4
To add an IPv4 H.248 Border Access Controller (BAC) address to the set of addresses that the BAC can use as local media address, use the media-address ipv4 command in the H248 BAC configuration mode. To remove an IPv4 address from the set of local media addresses, use the no form of this command.
media-address ipv4 ipv4-address realm realm-number vrf vrf-name
no media-address ipv4 ipv4-address realm realm-number vrf vrf-name
Syntax Description
Command Default
Command Modes
H248 BAC configuration (config-h248-bac)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
A realm group can contain multiple media addresses. When you configure a realm group under an adjacency, the IP address and port for the media stream of this adjacency is allocated from the media addresses in this realm group.
The media-address ipv4 command includes the port-range port-range subcommand that configures the port range of the media address.
Examples
The following example shows how the media-address ipv4 command is used to configure an H.248 media address instance:
Related Commands
|
|
|
|---|---|
media-address pool
To create a pool of sequential IPv4 or Ipv6 media addresses that can be used by the data border element (DBE) as local media addresses, use the media-address pool command in the appropriate configuration mode. This pool of addresses is added to the set of local media addresses that can be used by the DBE. To remove this pool of IPv4 addresses from the set of local media addresses, use the no form of this command.
media-address pool { ipv4 | ipv6 } { start-addr } { end-addr } [ nat-mode twice-nat | vrf vrf-name | managed-by { dbe | mgc }]
no media-address pool { ipv4 | ipv6 } { start-addr } { end-addr } [ nat-mode twice-nat | vrf vrf-name | managed-by { dbe | mgc }]
Syntax Description
Command Default
If a pool of IPv4 or IPv6 media addresses is specified, but the optional parameters are not specified, the following default values are used:
Command Modes
SBC configuration (config-sbc): for unified SBC
SBC-DBE configuration (config-sbc-dbe): for distributed SBC
Voice service VoIP(config-voi-serv): for TDM gateways and CUBE
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
This command was modified. The nat-mode twice-nat keyword was introduced. |
|
This command was modified to be supported under the voice service VoIP configuration. |
Usage Guidelines
Depending on whether you are running an unified SBC or a distributed SBC, use this command in the appropriate configuration mode.
The media address pool size is limited to 1024 IPv4 addresses. If more IPv4 addresses are required, we recommend that you create multiple SBC interfaces, and then configure the address pools from the subnets on those interfaces.
After you configure a local media address, it cannot be modified while the DBE service is active. Deactivate the DBE with the no activate command before modifying the media-address pool ipv4 specification.
A media address is a part of a pool of IP addresses on the DBE that are used for the media relay functionality. A pool of addresses is defined for the global VPN to which the DBE is attached. All the virtual data border elements (vDBEs) within the DBE draw media addresses from this pool.
Examples
The following example for a unified SBC shows how to create a DBE service on an SBC called “global” and how to configure addresses from 10.0.2.1 to 10.0.2.10 in the global VRF:
Router(cfg-sbc-media-address-pool)# end
The following example for a distributed SBC shows how to add IPv4 addresses from 10.0.2.1 to 10.0.2.10 to the media address pool as local addresses reserved for the Twice-NAT pinholes:
Router(config-sbc-dbe)# media-address pool ipv4 10.0.2.1 10.0.2.10 nat-mode twice-nat
Router(config-sbc-dbe-media-address-pool)# end
The following example for a distributed SBC shows how to create a DBE service on an SBC called “mySbc,” and enters into the SBC-DBE configuration mode, and how to configure addresses from 10.0.2.1 to 10.0.2.10 in the global VRF:
Router(config-sbc-dbe)# media-address pool ipv4 10.0.2.1 10.0.2.10
Router(config-sbc-dbe-media-address-pool)# end
The following example for a distributed SBC shows how to create a DBE service on an SBC called “mySbc,” and enters into the SBC-DBE configuration mode, and how to configure addresses from 10.0.2.20 to 10.0.2.25 in vpn3:
Router(config-sbc-dbe)# media-address pool ipv4 10.0.2.20 10.0.2.25 vrf vpn3
Router(config-sbc-dbe-media-address-pool)# exit
The following example for a distributed SBC tries to delete the media address 10.0.2.1 before deactivating the DBE, and receives an error message:
Related Commands
|
|
|
|---|---|
Adds an IPv4 address to the set of addresses that can be used by the DBE as a local media address. |
media-gateway
To configure a media gateway, use the media-gateway command in SBE configuration mode. To remove a media gateway configuration, 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.
Examples
The following example shows how to access media gateway mode from where you configure a media gateway.
Related Commands
|
|
|
|---|---|
Displays a list of known media gateways with an active association. |
|
media-gateway policy type
To configure a media gateway policy, use the media-gateway policy type command in the SBE configuration mode. To remove the policy, use the no form of this command.
media-gateway policy type {default | local | {remote {ipv4 | ipv6} ip-address [port port-number ]}}
no media-gateway policy type {default | local | {remote {ipv4 | ipv6} ip-address [port port-number ]}}
Syntax Description
Command Default
Command Modes
SBE configuration (config-sbc-sbe)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series 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
In the following example, the media-gateway policy type command is used to configure a remote-type media gateway policy on the media gateway at 192.0.2.26:
Related Commands
media-late-to-early-iw
To configure late-to-early media interworking (iw), use the media-late-to-early-iw command in Adjacency SIP configuration mode. To deconfigure late-to-early media interworking (iw), use the no form of this command.
media-late-to-early-iw {incoming | outgoing}
no media-late-to-early-iw {incoming | outgoing}
Syntax Description
Enable late-to-early media iw for calls from caller on this adjacency. |
|
Enable late-to-early media iw for calls to callee on this adjacency. |
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 late-to-early media iw for calls from caller on this adjacency.
Related Commands
|
|
|
|---|---|
media-line
To add a media description line to an entry in an SDP media profile, use the media-line command in SBC SBE SIP SDP media profile entry configuration mode. To delete a line, use the no form of this command.
media-line index '' media-description ''
Syntax Description
Command Default
Command Modes
SBC SBE SIP SDP media profile entry configuration (config-sbc-sbe-sip-sdp-media-ele)
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.
Use the media- line command to add media description lines into an entry of an SDP media profile.
Examples
The following example shows how to create lines in an SDP media profile entry :
Related Commands
|
|
|
|---|---|
Shows all SDP media profiles in an SBC service or details for a specified profile. |
media-policy
To configure a media policy, use the media-policy command in the SBE configuration mode. To remove the media policy configuration, 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 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
In the following example, the media-policy command is used to create the my_media_policy media policy:
Related Commands
media-timeout (session border controller)
To set the maximum time a DBE waits after receiving the last media packet on a call and before cleaning up the call resources, use the media-timeout command in SBC-DBE configuration mode. To reset the timeout value to the default value of 30 seconds, use the no form of this command.
media-timeout { timeout} first-packet
Syntax Description
Command Default
The default is 30 seconds if media-timeout is not configured.
Command Modes
SBC-DBE configuration (config-sbc-dbe)
Command History
|
|
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
|
Usage Guidelines
This command sets the maximum time the DBE waits after receiving the last media packet on a call before the DBE determines that the call has ceased and begins to clear up the call resources and to signal the signaling border element (SBE) to do the same. This command is used when the SBE is not able to clear up the calls itself. The normal method for clearing a call is for the SBE to explicitly signal the DBE.
You can halt detection of the media timeout event with the first-packet keyword of the media-timeout command. The first-packet keyword instructs the DBE to wait until it has received the first packet since the call has been established before starting the media timeout timer to start counting the number of seconds for which it has not seen an SBC packet. By the DBE waiting, SBC packets can continue to be forwarded because there is no media timeout yet. After waiting for the first packet and counting the configured number of seconds, then the DBE generates an alert to the SBE.
Use the sbc dbe command to enter into SBC-DBE configuration mode before using the media-timeout command.
Examples
The following example configures the DBE to wait 10 seconds after receiving the last media packet and before cleaning up the call resources:
Related Commands
|
|
|
|---|---|
media address preserve
To ensure that media pinholes are preserved for deleted streams so that if a stream is re-enabled, the Cisco Unified Border Element (SP Edition) will re-use the same pinhole, use the media address preserve command in CAC table entry configuration mode. To preserve media addresses allocated during the initial call negotiation process, use the init-negotiation keyword. To allow a media pinhole for a deleted stream to be deleted, use the no form of this command.
media address preserve init-negotiation
Syntax Description
Enable or disable Media Address Preservation during initial call negotiaiton. |
Command Default
If the media address preserve command is not configured or the no media address preserve command is used, the media pinhole for a deleted stream will be deleted.
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. |
|
Enhancement for Media Address Preservation during initial negotitation introduced. |
Usage Guidelines
The media address preserve command configures the Support Renegotiated Call Over NAT feature. This feature is used to avoid de-allocation of a video pinhole in a Network Address Translation (NAT) scenario where Delta Renegotiation mode is in effect and a video transmission is paused. Although the standard Secure Device Provisioning (SDP) protocol when a video transmission is paused is to set the video stream to “a=inactive” (which indicates that SBC should keep the stream allocated), there are known devices that do not set the video stream to “a=inactive” to pause it. Instead, these devices delete the video stream by setting its port to 0. To ensure that the stream remains allocated and the pinhole is preserved even when the SBC receives a port value of 0 during a media stream renegotiation, you can enable the media address preserve command on a per-call basis. When the media address preserve command is enabled, stream statistics and SDP billing information will be output at call termination, not at Delta Renegotiation.
The init-negotiation keyword enables you to preserve media addresses allocated during the initial call negotiation process. This means that a media address/port allocated due to SDP in an initial offer remains allocated for the lifetime of the call.
Examples
The following example ensures that media pinholes are preserved for deleted streams so that if a stream is re-enabled, the Cisco Unified Border Element (SP Edition) will re-use the same pinhole. Note that the media address preserve command is applied on a per-call basis.
Router(config-sbc-sbe-cacpolicy-cactable)# entry 1
Related Commands
media bandwidth-fields ignore
To set the media flag to ignore the b-line and use CODEC to calculate the baseline bandwidth required for the media stream, use the media bandwidth-fields ignore command in the CAC table entry configuration mode. To return to the default state, use the no form of this command.
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 modes required to run the command.
Examples
The following example shows how to set the AMB_CAC_MEDIA_FLAG_IGN_EXPL_BW media flag to ignore the b-line and use CODEC to calculate the baseline bandwidth required for the media stream:
Related Commands
|
|
|
|---|---|
Displays detailed information for a given entry in a CAC policy table. |
media bypass
To configure the Multiple SBC Media Bypass feature on a Session Initiation Protocol (SIP) adjacency, use the media bypass command in the adjacency SIP configuration mode. To disable the Multiple SBC Media Bypass feature, use the no form of this command.
media bypass { max-data-len data-length | tag sequence-number tag-name | auto-nat-tag-gen }
no media bypass { max-data-len | tag sequence-number | auto-nat-tag-gen }
Syntax Description
Command Default
The SBC relays media for all the endpoints associated with the adjacency.
Command Modes
Adjacency SIP configuration mode (config-sbc-sbe-adj-sip)
Command History
Usage Guidelines
On any particular adjacency, you can configure both the media bypass tag sequence-number tag-name command and the media bypass auto-nat-tag-gen command.
To use the media bypass command, you must be in the correct configuration mode. The Examples section shows the hierarchy of the modes required to run the command.
NoteMedia bypass is not supported for H.323 calls. Media bypass is not supported for H.323 calls.
Examples
The following example shows how to use the media bypass command to configure the Multiple SBC Media Bypass feature and to set the maximum length of the multiple SBC media bypass data that can be transmitted on the outbound signaling messages on the adjacency to 150 bytes. The second media bypass command in this example is used to set TAG1 as the name of the tag that is used to control the groups that belong to the endpoints on the adjacency.
The following example shows how to use the media bypass command to configure the Multiple SBC Media Bypass feature and to specify that a media bypass tag must be automatically generated for each endpoint that is behind a NAT device on the adjacency.
Related Commands
|
|
|
|---|---|
media bypass type
To configure the Multiple SBC Media Bypass feature for a Call Admission Control (CAC) policy set, use the media bypass type command in the CAC table entry configuration mode. To deconfigure the Multiple SBC Media Bypass feature, use the no form of this command.
media bypass type [ all | none | full [ hairpin partial ] | hairpin [ full partial ] | partial [ full hairpin ]
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 Multiple SBC Media Bypass feature to enable all types of media bypass:
Related Commands
|
|
|
|---|---|
Configures a CAC table type to enable the priority of the call to be used as a criterion in the CAC policy. |
media limits
To specify the media policy to be associated with the CAC policy table entry or applied on the media gateway, use the media limits command in the SBE CAC table CAC policy configuration mode or the SBE media gateway configuration mode. To remove this configuration, use the no form of this command.
Syntax Description
Command Default
Command Modes
The configuration mode can be one of the following:
- SBE CAC table CAC policy configuration (config-sbc-sbe-cacpolicy-cactable-entry)
- SBE media gateway configuration (config-sbc-sbe-mg-pol)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series 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
In the following example, the media limits command is used to specify that the mp1 policy must be applied as entry 1 in the t1 CAC table.
In the following example, the media limits command is used to specify that the audio_limit1 media policy must be applied on the remote media gateway at 192.0.2.82:
Related Commands
media police
To configure how SBC handles media streams that exceed bandwidth limits for media calls, use the media police command in CAC table entry configuration mode. To return the policing conditions to the default value, use the no form of this command.
media police strip | reject | degrade
no media police strip | reject | degrade
Syntax Description
Command Default
When media police is not configured, the default is to inherit the conditions from the interface, which in most cases is equivalent to the conditions for strip.
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 modes required to run the command.
The degrade option is not supported on H.323 calls.
Using the degrade option may cause a 2 to 5 percent performance degradation.
Examples
The following example shows how to configure SBC to degrade media streams to lower bandwidths when requests exceed bandwidth limits.
Related Commands
method-editor
To configure a method editor, use the method-editor command in the Adjacency SIP configuration mode. To remove a method editor, use the no form of this command.
method-editor { inbound | outbound} { editor-name | default }
no method-editor { inbound | outbound} { editor-name | default }
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 the modes required to run the command.
Examples
The following example shows how the method-editor command configures an inbound method editor named test1:
Related Commands
|
|
|
|---|---|
method-profile
To configure a method profile in the mode of an SBE entity, use the method-profile command in Adjacency SIP configuration mode. To remove the method profile, use the no form of this command.
method-profile { inbound | outbound} profile-name
no method-profile { inbound | outbound}
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 the method-profile command configures a method profile with the name of test1:
method 3GPP-RF
To enable the 3GPP-RF billing method on the Cisco Session Border Controller (SBC), use the method 3GPP-RF command in the SBC SBE billing configuration mode. To disable the 3GPP-RF billing method, use the no form of this command.
Syntax Description
Command Default
Command Modes
SBC SBE billing configuration (config-sbc-sbe-billing)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Examples
The following example shows how to enable the 3GPP-RF billing method on the SBC:
method (editor)
To add a method to an method editor, use the method command in the session initiation protocol (SIP) Method Editor configuration mode. To remove a method from an editor, use the no form of this command.
Syntax Description
Name of the method to be added to the method editor. Valid names are 1 to 32 characters in length (inclusive) and are case-sensitive. |
Command Default
Command Modes
SIP Method Editor configuration (config-sbc-sbe-mep-mth)
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 the method command adds a method, test, to the Myeditor method editor:
Related Commands
|
|
|
|---|---|
method packetcable-em
To enable the packet-cable billing method, use the method packetcable-em in the SBE billing configuration mode. To disable the packet-cable billing method, use the no form of this command.
Syntax Description
Command Default
Command Modes
SBE billing configuration (config-sbc-sbe-billing)
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 enable the packet-cable billing method :
Related Commands
|
|
|
|---|---|
Activates the billing functionality after configuration is committed. |
|
Configures the time of day (local time) to run the Long Duration Check (LDR). |
|
method (session border controller)
To add a method with a specified name to a SIP message profile, use the method command in the SIP method-profile mode. To remove the method from the profile, use the no form of this command.
Syntax Description
Specifies the name of the method added to the method profile. Valid names are 1 to 32 characters in length (inclusive) and are case-sensitive. |
Command Default
Command Modes
SIP method-profile configuration (config-sbc-sbe-sip-mth)
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 method command adds a method test to the method profile Myprofile:
method xml
To configure the Billing Manager such that it enables enabling the XML billing method, use the method xml command in the SBE billing configuration mode. To disable the XML billing method, use the no form of this command.
Syntax Description
Command Default
Command Modes
SBE billing configuration (config-sbc-sbe-billing)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Routers. |
Usage Guidelines
The XML method has been introduced to provision IP-centric logging information. Because the PacketCable billing method was too telephonic-specific, and uses the BAF format, the XML method has been introduced.
To enable the XML billing method on Billing Manager, you need to execute the method xml command from SBE billing configuration mode. To disable, the XML billing method, execute the no method xml command.
NoteIf XML billing instances are configured, the If XML billing instances are configured, the no method xml command cannot be successfully executed.
Examples
The following example shows how to enable the XML billing method on the Billing Manager:
Related Commands
|
|
|
|---|---|
Indicates the path in which to store CDR billing records on the local machine. |
|
Configures the time at which long duration records are checked. |
minor-alert-size
To configure the number of specified events before a minor alert is triggered, use the minor-alert-size command in the blacklist reason mode. To disable the number of specified events, use the no form of this command.
minor-alert-size number-of-events
Syntax Description
The number of events for alert to be triggered. This can be of any value ranging from 1 to 65535. |
Command Default
Command Modes
Blacklist reason mode (config-sbc-sbe-blacklist-reason)
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 number of specified events for a minor alert to be triggered using the minor-alert-size command in the blacklist reason mode:
Related Commands
mode (session border controller)
To enter a mode for configuring the mode of a RADIUS Authentication server or RADIUS accounting server, use the server mode command in the server authentication mode. To exit the mode for configuring of RADIUS Authentication server mode, use the no form of this command.
Syntax Description
Command Default
Command Modes
Server authentication (config-sbc-sbe-auth-ser)
Server accounting (config-sbc-sbe-acc-ser)
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 server mode:
monitor event-trace sbc ha (EXEC)
To monitor and control the event trace function of the Session Border Controller (SBC), use the monitor event-trace sbc ha command in privileged EXEC mode.
monitor event-trace sbc ha { clear | continuous [ cancel ] | disable | dump [ pretty ] | enable | one-shot }
Syntax Description
Command Default
Command Modes
Command History
Usage Guidelines
Use the monitor event-trace sbc ha command to control when and how and what kind of event trace data pertaining to the SBC on the Cisco ASR 1000 Series Aggregation Services Routers is collected.
Use this command after you have configured the event trace functionality on the Cisco ASR 1000 Series Routers using the monitor event-trace sbc ha command in global configuration mode.
Note The amount of data collected from the trace depends on the trace message size that has been configured using the monitor event-trace sbc ha command in global configuration mode for each instance of a trace.
You can enable or disable SBC event tracing either by using the monitor event-trace sbc ha command in privileged EXEC mode or by using the monitor event-trace sbc command in global configuration mode. To disable event tracing, you should enter either of these commands with the disable keyword. To enable event tracing again, you should enter either of these commands with the enable keyword.
Use the show monitor event-trace sbc ha command to display trace messages. Use the monitor event-trace sbc ha dump command to save the trace message information for a single event. By default, trace information is saved in binary format. If you want to save trace messages in ASCII format, possibly for additional application processing, use the monitor event-trace sbc ha dump pretty command.
To configure the file in which you want to save trace information, use the monitor event-trace sbc ha dump-file dump-file-name command in global configuration mode. The trace messages are saved in binary format.
Examples
The following example shows the privileged EXEC commands that stop event tracing, clear the current contents of memory, and re-enable the trace function for the SBC high availability events. This example assumes that the tracing function is configured and enabled on the networking device.
The following example shows how to configure the continuous display of the latest SBC high availability trace entries:
The following example shows how to stop the continuous display of the latest trace entries:
Related Commands
monitor event-trace sbc ha (global)
To configure event tracing for the Session Border Controller (SBC), use the monitor event-trace sbc ha command in the global configuration mode. To remove event tracing configuration from the SBC, use the no form of this command.
monitor event-trace sbc ha { disable | dump-file dump - file-name | enable | size number | stacktrace [ depth ]}
no monitor event-trace sbc ha { dump-file dump - file-name | size number | stacktrace [ depth ]}
Syntax Description
Command Default
Command Modes
Command History
Usage Guidelines
Use the monitor event-trace sbc ha command to enable or disable event tracing and to configure event trace parameters for the SBC.
The Cisco IOS XE software allows the SBC to define whether support for event tracing is enabled or disabled by default. The command interface for event tracing allows you to change the default value either by using the monitor event-trace sbc ha command in the privileged EXEC mode or by using the monitor event-trace sbc ha command in the global configuration mode.
Additionally, default settings do not appear in the configuration file. If the SBC enables event tracing by default, the monitor event-trace sbc ha enable command does not appear in the configuration file of the networking device. However, disabling event tracing that has been enabled by default by the subsystem creates a command entry in the configuration file.
NoteThe amount of data collected from the trace depends on the trace message size that has been configured using the The amount of data collected from the trace depends on the trace message size that has been configured using the monitor event-trace sbc ha size command for each instance of a trace. Some Cisco IOS software subsystem components set the size by default. To display the size parameters, use the show monitor event-trace sbc ha parameters command.
To determine whether event tracing is enabled by default for the SBC, use the show monitor event-trace sbc ha command to display the trace messages.
To specify the trace call stack at tracepoints, you must first clear the trace buffer with the monitor event-trace sbc ha clear privileged EXEC command.
Examples
The following example shows how to enable event tracing for the SBC subsystem component in the Cisco IOS XE software, and to configure the size to 10,000 messages. The trace messages file is set to sbc-ha-dump in flash memory.
Related Commands
|
|
|
|---|---|
Configures event tracing for a specified Cisco IOS software subsystem component. |
|
Monitors and controls the event trace function pertaining to the SBC. |
|
na-carrier-id-table
To enter the configuration mode of a number analysis table within the context of an SBE policy set, use the na-carrier-id-table command in the SBE call policy set mode. To remove the number analysis table, use the no form of this command.
na-carrier-id-table table-name
no na-carrier-id-table table-name
Syntax Description
Command Default
Command Modes
SBE routing policy (config-sbc-sbe-rtgpolicy)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
|
This command was modified. The na-dst-number-attr-table was renamed as na-carrier-id-table. |
Usage Guidelines
The entries in this table are matched with the carrier ID. If necessary, a new number analysis table is created. Do not change the configuration of the tables in the context of the active policy set.
A number analysis table should not be removed if it is in the context of the active policy set.
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 command shows how to enter the configuration mode of the na-table number analysis table within the context of an SBE policy set:
Related Commands
na-dst-address-table
To enter the configuration mode of a number analysis table within the context of an SBE policy set, use the na-dst-address-table command in the SBE call policy set mode. To remove the number analysis table, use the no form of this command.
na-dst-address-table table-name
no na-dst-address-table table-name
Syntax Description
Command Default
Command Modes
SBE call policy set (config-sbc-sbe-rtgpolicy)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
|
This command was modified. The na-dst-number-table was renamed as na-dst-address-table. |
Usage Guidelines
The entries in this table are matched with the complete dialed number. If necessary, a new number analysis table is created. Do not change the configuration of the tables in the context of the active policy set.
A number analysis table should not be removed if it is in the context of the active policy set.
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 command shows how to create the MyNaTable number analysis table with the table entries matching the complete dialed number:
Related Commands
na-dst-prefix-table
To enter the mode in which to configure a number analysis table, with numbers that match the prefix of the dialed number within an SBE policy set, use the na-dst-prefix-table command in SBE call policy set mode. Use the no form of this command to destroy the number analysis table.
na-dst-prefix-table table-name
no na-dst-prefix-table table-name
Syntax Description
Command Default
Command Modes
SBE routing policy (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 illustrates the use of the na-dst-prefix-table command to create a number analysis table called MyNaTable.
Related Commands
na-src-account-table
To enter the mode for configuring a number analysis table within an SBE policy set, with entries that match the source account, use the na-src-account-table command in the SBE call policy set mode. Use the no form of this command to destroy the table.
na-src-account-table table-name
no na-src-account-table table-name
Syntax Description
Command Default
Command Modes
SBE routing policy (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 commands enter the mode for the NA table MyNaTable, or if it does not already exist, it creates it.
Related Commands
na-src-address-table
To enter the configuration mode of a source number analysis table within the context of an SBE policy set, use the na-src-address-table command in the SBE call policy set mode. To remove the number analysis table, use the no form of this command.
na-src-address-table table-name
no na-src-address-table table-name
Syntax Description
Command Default
Command Modes
SBE call policy set (config-sbc-sbe-rtgpolicy)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
|
This command was modified. The na-src-number-table was renamed as na-src-address-table. |
Usage Guidelines
The entries in this table are matched with the complete number from which the call originated. If necessary, a new number analysis table is created. Do not change the configuration of the tables in the context of the active policy set.
A number analysis table should not be removed if it is in the context of the active policy set.
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 command shows how to enter the configuration mode of the na-table number analysis table within the context of an SBE policy set:
Related Commands
na-src-adjacency-table
To enter the mode of configuration of a number analysis table within the context of an SBE policy set, use the na-src-adjacency-table command in SBE routing policy mode. The no form of this command destroys the number analysis table.
na-src-adjacency-table table-name
no na-src-adjacency-table table-name
Syntax Description
Command Default
Command Modes
SBE routing policy (config-sbc-sbe-rtgpolicy)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
The entries of this table match against the source adjacency. If necessary, a new number analysis table is created. You may not change the configuration of tables in the context of the active policy set. A number analysis table may not be destroyed if it is in the context of the active policy set.
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 commands enter the mode for the NA table MyNaTable with entries matching against the whole dialed number:
Related Commands
na-src-name-anonymous-table
To enter the configuration mode of a number analysis table, to determine whether the display name or presentation number is anonymous, use the na-src-name-anonymous-table command in the SBE routing policy configuration mode. Use the no form of this command to remove the number analysis table.
na-src-name-anonymous-table table-name
no na-src-name-anonymous-table table-name
Syntax Description
Command Default
Command Modes
SBE routing policy (config-sbc-sbe-rtgpolicy)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers |
Usage Guidelines
The entries of this table match against the carrier ID. If necessary, a new number analysis table is created. You may not change the configuration of tables in the context of the active policy set.
A number analysis table may not be destroyed if it is in the context of the active policy set.
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 command enters the mode of configuration of a number analysis table na-table within the context of an SBE policy set.
Related Commands
na-src-prefix-table
To enter the mode in which to configure a number analysis table, with numbers that match the prefix of the source number within an SBE policy set, use the na-src-prefix-table command in SBE call policy set mode. Use the no form of this command to destroy the number analysis table.
na-src-prefix-table table-name
no na-src-prefix-table table-name
Syntax Description
Command Default
Command Modes
SBE routing policy (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 illustrates the use of the na-src-prefix-table command to create a number analysis table called MySrcPrefixNaTable.
Related Commands
nat (session border controller)
To configure a SIP adjacency to assume that all endpoints are behind a NAT device, use the nat command in the SIP adjacency mode. To deconfigure this feature on the SIP adjacency, use the no form of this command.
no nat { force-on | force-off }
Syntax Description
Sets the SIP adjacency to assume that all endpoints are behind a NAT device. |
|
Sets the SIP adjacency to assume that the endpoints are not behind a NAT device. |
Command Default
The SBC autodetects whether all the endpoints are behind a NAT device.
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 the nat force-on command is used to configure the SIP adjacency to assumes that all endpoints are behind a NAT device:
nat force-on
To configure all the endpoints of an access adjacency for the H.248 Border Access Controller (BAC) to be behind a NAT device, use the nat force-on command in the H248 BAC access adjacency configuration mode. To configure all the endpoints of an access adjacency for the H.248 BAC not to be behind a NAT device, use the no form of this command.
Syntax Description
Command Default
All the endpoints of an H.248 BAC access adjacency are not behind a NAT device.
Command Modes
H248 BAC access adjacency. (config-h248-bac-adj)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Examples
The following example shows how the nat force-on command is used to configure all the endpoints of an access adjacency for the H.248 BAC to be behind a NAT device:
network-id (session border controller)
To configure the network ID, use the network-id command in SBE configuration mode. To deconfigure the network ID, 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.
Examples
The following example shows how to set the network ID to 88888:
network
To configure either an IPv4 or IPv6 network on a redundant peer, use the network command in adjacency Session Initiation Protocol (SIP) peer configuration mode. To deconfigure a network, use the no form of this command.
network { IPv4 address netmask | IPv6 address netmask }
no network { IPv4 address netmask | IPv6 address netmask }
Syntax Description
Command Default
Command Modes
Adjacency SIP peer configuration (config-sbc-sbe-adj-sip-peer)
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 the network command is used to configure an IPv4 network on a redundant peer on a SIP adjacency:
Related Commands
|
|
|
|---|---|
Configures either an IP address or a host name to act as a redundant peer. |
|
option-editor
To set an adjacency to use a specified editor for the whitelisting or blacklisting options, use the option-editor command. To remove the option editor, use the no form of this command.
option-editor [ua | proxy] [inbound | outbound] [editor-name | default]
no option-editor [ua | proxy] [inbound | outbound] [editor-name | default]
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
UA editors are applied to the Supported and Require headers. Proxy editors are applied to the Proxy-Require headers.
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 set the adjacency to use the specified editor for the whitelisting or blacklisting options:
Related Commands
|
|
|
|---|---|
option-profile
To set the adjacency to use the specified profile for white/blacklisting options, use the option-profile command. Use the no form of the command to select the default global configuration.
option-profile [ua | proxy] [inbound | outbound] [ prof-name | default]
no option-profile [ua | proxy] [inbound | outbound] [ prof-name | default]
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
User agent (UA) profiles are applied to Supported and Require headers. Proxy profiles are applied to Proxy-Require headers.
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 adjacency to use the specified profile for white/blacklisting options:
options
To configure the codec that will support voice inband DTMF, use the options command in codec definition mode. Use the no form of this command to remove an existing option from this codec.
options {none | transrate | transcode | inband-dtmf}
no options {none | transrate | transcode | inband-dtmf}
Syntax Description
Command Default
Command Modes
Codec definition (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 modes required to run the command:
Examples
The following example shows how to add an option to the codec.
option (editor)
To add an option to an editor, use the option command in the Session Initiation Protocol (SIP) Option Editor configuration mode. To remove an option, use the no form of this command.
Syntax Description
Command Default
Command Modes
SIP Option Editor configuration (config-sbc-sbe-mep-opt)
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 add an option to an editor:
Related Commands
|
|
|
|---|---|
option (session border controller)
To add an option to a profile, use the option command in SIP option mode. Use the no form of this command to remove an existing option from this profile.
Syntax Description
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 add an option to the profile.
origin-host
To configure the domain name of an IMS local host, use the origin-host command in Diameter configuration mode. To remove the origin host, use the no form of this command.
Syntax Description
Specifies the name of the local host. The maximum length is 255 characters. |
Command Default
Command Modes
Diameter configuration (config-sbc-sbe-diameter)
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 domain name of the local host (origin-host) is reported in the Diameter Origin-host AVP.
Examples
The following example shows how to configure the domain name of an IMS local host.
Related Commands
origin-host (Rf interface)
To specify the domain name of an origin host for Rf support on the Session Border Element (SBE) of the Session Border Controller (SBC), use the origin-host command in the SBC SBE billing Rf configuration mode. To unconfigure the domain name of an origin host for Rf support on the SBE of the SBC, use the no form of this command.
Syntax Description
Unique name (case sensitive) for an origin host. String length range: 1 to 30. |
Command Default
Command Modes
SBC SBE billing Rf configuration (config-sbc-sbe-billing-rf)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Examples
The following example shows how to specify the domain name of an origin host for Rf support on the SBE of the SBC:
Related Commands
|
|
|
|---|---|
Specifies the domain name of an origin realm for Rf support on the SBE of the SBC. |
|
origin-realm
To configure the domain name of an IMS local realm, use the origin-realm command in Diameter configuration mode. To remove the origin realm, use the no form of this command.
Syntax Description
Specifies the domain name of the local realm. The maximum length is 63 characters. |
Command Default
Command Modes
Diameter configuration (config-sbc-sbe-diameter)
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 a realm-based routing protocol, where multiple IMS peers can be configured. The domain name of the local realm (origin-realm) is reported in the Diameter Origin-Realm AVP.
Examples
The following example shows how to configure the domain local name of an IMS realm.