Table Of Contents
packetcable-em transport radius
request-line request-uri rewrite
service sbc sbe radius accounting
packetcable-em transport radius
To configure a packet-cable billing instance, use the packetcable-em transport radius command in the SBE billing configuration mode. To disable the packet-cable billing instance, use the no form of this command.
packetcable-em method-index transport radius RADIUS-client-name
no packetcable-em method-index transport radius RADIUS-client-name
Syntax Description
method-index
Specifies the packetcable billing instance. The range is 0 to 7.
RADIUS-client-name
The RADIUS client name. The maximum size is 80 characters.
Command Default
No default behavior or values.
Command Modes
SBE billing configuration (config-sbc-sbe-billing)
Command History
Cisco IOS XE Release 2.4
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 and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
Examples
The following example configures packet-cable billing instances of four with a RADIUS client name of `test':
Router# configureRouter# sbc mySbcRouter(config-sbc)# sbe(config-sbc-sbe)# billing(config-sbc-sbe-billing)# packetcable-em 4 transport radius test(config-sbc-sbe-billing-packetcable-em)#Related Commands
parameter
To add a parameter with a specified name to a SIP message profile, use the parameter command in SBE SIP parameter-profile configuration mode. To remove the method from the profile, use the no form of this command.
parameter {parameter name}
no parameter {parameter name}
Syntax Description
parameter name
Name of the parameter added to the parameter profile. Valid names are 1 to 32 characters in length (inclusive) and are case-sensitive.
Defaults
No default behavior or values
Command Modes
SIP parameter-profile configuration
Command History
Cisco IOS XE Release 2.4
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 and submode. The Examples section shows the hierarchy of modes and submodes 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 the parameter command adds a parameter named user to the parameter profile MyProfile:
Router# configureRouter(config)# sbc mySbcRouter(config-sbc)# sbeRouter(config-sbc-sbe)# sip parameter-profile MyProfileRouter(config-sbc-sbe-sip-prm)# parameter userRouter(config-sbc-sbe-sip-prm-ele)# action add-not-present value phoneRelated Commands
action
Configures the action to take in a profile.
parameter-profile
Configures a parameter profile.
parameter-profile
To add a parameter profile associated with a header, use the parameter-profile command in SBE configuration mode. To remove the parameter profile, use the no form of this command.
parameter-profile profile-name
no parameter-profile profile-name
Syntax Description
Defaults
No default behavior or values
Command Modes
SIP header configuration element (config-sbc-sbe-sip-hdr-ele)
Command History
Cisco IOS XE Release 2.4
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 and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
Examples
The following example shows how to add a parameter profile to the header element for a header profile:
Router# configRouter(config)# sbc mySbcRouter(config-sbc)# sbeRouter(config-sbc-sbe)# sip header-profile headerprof1Router(config-sbc-sbe-sip-hdr)# header ToRouter(config-sbc-sbe-sip-hdr-ele)# parameter-profile parmprof1Related Commands
sip method-profile
Configures a method-profile.
sip header-profile
Configures a header profile.
pass-body
To permit SIP message bodies to pass through [for non-vital SIP methods accepted by a method profile] in the SIP method profile mode of an SBE entity, use the pass-body command in SIP method configuration mode. To remove the message bodies out of non-vital SIP messages accepted by the method profile, use the no form of this command.
pass-body
no pass-body
Syntax Description
This command has no arguments or keywords.
Defaults
By default, the message bodies are removed out of non-vital SIP messages.
Command Modes
SIP method (config-sbc-sbe-sip-mth)
Command History
Cisco IOS XE Release 2.4
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 and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
Examples
The following example shows how the pass-body command permits SIP message bodies to pass through for non-vital SIP methods accepted by method profile test1:
Router# configureRouter(config)# sbc mySbcRouter(config-sbc)# sbeRouter(config-sbc-sbe)# sip method-profile test1Router(config-sbc-sbe-sip-mth)# pass-body
ping-enable
To configure the adjacency to poll its remote peer by sending SIP OPTIONS pings to it and to enter the ping option submode, use the ping-enable command in adjacency SIP configuration mode. Use the no form of this command to disable polling the remote peer for the adjacency.
ping-enable
no ping-enable
Syntax Description
Defaults
Options pings are disabled by default.
Command Modes
Adjacency SIP configuration (config-sbc-sbe-adj-sip)
Command History
Cisco IOS XE Release 2.4
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 and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
Examples
The following example shows how to configure the adjacency to poll its remote peer by sending SIP OPTIONS pings:
Router# configureRouter(config)# sbc mySbcRouter(config-sbc)# sbeRouter(config-sbc-sbe)# adjacency sip SipAdj1Router(config-sbc-sbe-adj-sip)# ping-enableRouter(config-sbc-sbe-adj-sip-ping)# exitRouter(config-sbc-sbe-adj-sip)#ping-fail-count
To configure the number of consecutive pings that must fail before the adjacencies peer is deemed to be unavailable, use the ping-fail-count command in ping option mode. Use the no form of this command to set the fail count to default.
ping-fail-count fail-count
no ping-fail-count
Syntax Description
Defaults
fail-count = 3
Command Modes
Ping option (config-sbc-sbe-adj-sip-ping)
Command History
Cisco IOS XE Release 2.4
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 and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
Examples
The following example shows how to configure the number of consecutive pings that must fail before the adjacencies peer is deemed to be unavailable:
Router# configureRouter(config)# sbc mySbcRouter(config-sbc)# sbeRouter(config-sbc-sbe)# adjacency sip SipAdj1Router(config-sbc-sbe-adj-sip)# ping-enableRouter(config-sbc-sbe-adj-sip-ping)# ping-fail-count 10Router(config-sbc-sbe-adj-sip-ping)#ping-interval
To configure the interval between SIP OPTIONS pings which are sent to the remote peer, use the ping-interval command in ping option mode. Use the no form of this command to set the interval to default.
ping-interval interval
no ping-interval
Syntax Description
Defaults
32 seconds
Command Modes
Ping option (config-sbc-sbe-adj-sip-ping)
Command History
Cisco IOS XE Release 2.4
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 and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
Examples
The following example shows how to configure the interval between SIP OPTIONS pings that are sent to the remote peer to 100 seconds:
Router# configureRouter(config)# sbc mySbcRouter(config-sbc)# sbeRouter(config-sbc-sbe)# adjacency sip SipAdj1Router(config-sbc-sbe-adj-sip)# ping-enableRouter(config-sbc-sbe-adj-sip-ping)# ping-interval 100Router(config-sbc-sbe-adj-sip-ping)#ping-lifetime
To configure the duration for which SBC waits for a response to an options ping for the adjacency, use the ping-lifetime command in ping option mode. Use the no form of this command to set the duration to default.
ping-lifetime duration
no ping-lifetime
Syntax Description
Defaults
32 seconds
Command Modes
Ping option (config-sbc-sbe-adj-sip-ping)
Command History
Cisco IOS XE Release 2.4
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
Usage Guidelines
If no response is received in the duration time, then the ping is deemed to have failed.
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.
Examples
The following example shows how to configure the duration for which SBC waits for a response to an options ping for the adjacency to 100 seconds:
Router# configureRouter(config)# sbc mySbcRouter(config-sbc)# sbeRouter(config-sbc-sbe)# adjacency sip SipAdj1Router(config-sbc-sbe-adj-sip)# ping-enableRouter(config-sbc-sbe-adj-sip-ping)# ping-lifetime 100Router(config-sbc-sbe-adj-sip-ping)#port
To configure the port that the RADIUS server will use to receive Access-Request or Accounting-Request packets, use the port command in the appropriate configuration mode. Use the no form of the command to disregard the configuration.
port port-num
no port
Syntax Description
port-num
Specifies the port where the RADIUS server receives access-request packets. Range is 1 to 65535.
Defaults
Access-Request packets use default port 1812.
Accounting-Request packets use default port 1813.
Command Modes
RADIUS accounting configuration (config-sbc-sbe-acc-ser)
RADIUS authentication configuration (config-sbc-sbe-auth-ser)
Command History
Cisco IOS XE Release 2.4
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 and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
Examples
The following example shows how to configure authentication server acctsvr to use port 1009 on mySbc for the authentication RADIUS client instance:
Router# configureRouter(config)# sbc mySbcRouter(config-sbc)# sbeRouter(config-sbc-sbe)# radius authenticationRouter(config-sbc-sbe-auth)# server acctsvrRouter(config-sbc-sbe-auth-ser)# port 1009port (SBE H.248)
To configure an SBE to use a given IPv4 H.248 port for H.248 communications when acting as a media gateway controller, use the port command in H.248 control address mode. To delete a given IPv4 H.248 port, use the no form of this command.
port port-number
no port port-number
Syntax Description
Defaults
No default behavior or values
Command Modes
H.248 control address (config-sbc-sbe-ctrl-h248)
Command History
Cisco IOS XE Release 2.4
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 and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
Examples
The following example shows how to configure an SBE to use port 2000:
Router# configureRouter(config)# sbc mySbcRouter(config-sbc)# sbeRouter(config-sbc-sbe)# control address h248 index 0Router(config-sbc-sbe-ctrl-h248)# ipv4 1.1.1.1Router(config-sbc-sbe-ctrl-h248)# port 2000Related Commands
port-range (ipv4)
To create a port range associated with an IPv4 media address or a pool of IPv4 media addresses, use the port-range command in the corresponding SBC media address configuration or SBC media address pool configuration mode; or SBC-DBE media address configuration mode or the SBC-DBE media address pool configuration mode. To delete a port range, use the no form of this command.
port-range {min-port} {max-port} [any | voice | video | signaling | fax]
no port-range {min-port} {max-port}
Syntax Description
Command Default
If the port-range command is not configured, the default min-port value is 16384, the default max-port value is 32767, and the default class of service affinity is any.
Command Modes
SBC media address configuration (cfg-sbc-media-address) or SBC media address pool configuration (cfg-sbc-media-address pool) for unified Session Border Controller (SBC)
SBC-DBE media address configuration (config-sbc-dbe-media-address) or SBC-DBE media address pool configuration (config-sbc-dbe-media-address pool) for distributed SBC
Command History
Usage Guidelines
Use the port-range command in media address configuration mode to specify a port range for a single media address.
Use the media-address ipv4 command to enter media address configuration mode before entering the port-range command for a single media address.
Use the port-range command in media address pool configuration mode to specific a port range for a pool of media addresses.
Use the media-address pool ipv4 command to enter media address pool configuration mode before entering the port-range command for a pool of media addresses.
Examples
The following example for a unified SBC creates a port range of 10000 to 20000 associated with IPv4 address 10.10.10.1 within a media address or a pool of media addresses for the port range for any class of service:
Router# configure terminalRouter(config)# sbc globalRouter(config-sbc)# media-address ipv4 10.10.10.1Router(cfg-sbc-media-address)# port-range 10000 20000 anyThe following example for a distributed SBC creates a port range of 10000 to 20000 associated with IPv4 address 10.10.10.1 within a media address or a pool of media addresses for the port range for any class of service:
Router# configure terminalRouter(config)# sbc mySbc dbeRouter(config-sbc-dbe)# media-address ipv4 10.10.10.1Router(config-sbc-dbe-media-address pool)# port-range 10000 20000 anyThe following example for a distributed SBC creates a port range of 10000 to 20000 associated with a pool of sequential IPv4 media addresses from 10.10.10.1 through 10.10.10.20 for any class of service:
Router# configureRouter(config)# sbc mySbc dbeRouter(config-sbc-dbe)# media-address pool ipv4 10.10.10.1 10.10.10.20Router(config-sbc-dbe-media-address pool)# port-range 10000 20000 anyThe following example for a distributed SBC creates a new port range between 10000 to 20000 with a service class affinity of voice for a single media address:
Router(config-sbc-dbe-media-address)# port-range 10000 20000 voiceThe following example for a distributed SBC modifies the service class affinity set for the media address by the previous example to any class of service:
Router(config-sbc-dbe-media-address)# port-range 10000 20000 anyThe following example for a distributed SBC deletes the port range set for the media address by the previous example:
Router(config-sbc-dbe-media-address)# no port-range 10000 20000The following example for a distributed SBC creates a new port range between 10000 to 20000 with a service class affinity of voice for a pool of media addresses:
Router(config-sbc-dbe-media-address pool)# port-range 10000 20000 voiceThe following example for a distributed SBC modifies the service class affinity set for the pool of media addresses by the previous example to any class of service:
Router(config-sbc-dbe-media-address pool)# port-range 10000 20000 anyThe following example for a distributed SBC deletes the port range set for the pool of media addresses by the previous example:
Router(config-sbc-dbe-media-address pool)# no port-range 10000 20000Related Commands
preferred-transport
To set the preferred transport protocol for SIP signaling on an adjacency, use the preferred-transport command in adjacency SIP configuration mode.
preferred-transport {tcp | udp}
no preferred-transport
Syntax Description
Defaults
Adjacencies use UDP by default.
Command Modes
Adjacency SIP configuration (config-sbc-sbe-adj-sip)
Command History
Cisco IOS XE Release 2.4
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 and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
Examples
The following command sets the preferred transport of the SipAdj1 adjacency to TCP:
Router# configureRouter(config)# sbc mySbcRouter(config-sbc)# sbeRouter(config-sbc-sbe)# adjacency sip SipAdj1Router(config-sbc-sbe-adj-sip)# preferred-transport tcpRouter(config-sbc-sbe-adj-sip)# exitprecedence
To configure the precedence of the routing entry, use the precedence command in RTG routing table entry configuration mode. Todeconfigure the precedence of the routing entry, use the no form of this command.
precedence precedence
no precedence precedence
Syntax Description
precedence
Range: [0-0xFFFFFFFF]. A value of 0 means the entry will never be matched.
Zero is the default.
Defaults
Zero is the default.
Command Modes
RTG routing table entry configuration (config-sbc-sbe-rtgpolicy-rtgtable-entry)
Command History
Cisco IOS XE Release 2.4
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
Usage Guidelines
If more than one entry matches the current time, selection is based on precedence.
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.
Examples
The following example shows how to configure an SBE to use port 2000:
Router# configureRouter(config)# sbc mySbcRouter(config-sbc)# sbeRouter(config-sbc-sbe)# call-policy-set 1Router(config-sbc-sbe-rtgpolicy)# rtg-category-table MyRtgTableRouter(config-sbc-sbe-rtgpolicy-rtgtable)# entry 1Router(config-sbc-sbe-rtgpolicy-rtgtable-entry)# precedence 0Router(config-sbc-sbe-rtgpolicy-rtgtable)# endRelated Commands
prefix
To configure whether the match-address of this entry matches the start of the source or destination address, use the prefix command in the routing table configuration mode. To delete the table-type in the routing table, use the no form of this command.
prefix
no prefix
Syntax Description
This command has no arguments or keywords.
Defaults
By default, the match-address is not be denoted as a prefix.
Command Modes
Routing table entry (config-sbc-sbe-rtgpolicy-rtgtable-entry
Command History
Cisco IOS XE Release 2.4
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 and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
Examples
The following example shows how to configure an entry to match dialed numbers starting with 9:
Router# configureRouter(config)# sbc mySbcRouter(config-sbc)# sbeRouter(config-sbc-sbe)# call-policy-set 1Router(config-sbc-sbe-rtgpolicy)# rtg-dst-address-table MyRtgTableRouter(config-sbc-sbe-rtgpolicy-rtgtable)# entry 1Router(config-sbc-sbe-rtgpolicy-rtgtable-entry)# match-address 9Router(config-sbc-sbe-rtgpolicy-rtgtable-entry)# prefixpriority
To configure the priority of the accounting or authentication server, use the priority command in the appropriate configuration mode. To disable any previously set priority, use the no form of this command.
priority pri
no priority
Syntax Description
Defaults
By default, this command assumes that pri is 1.
Command Modes
Server accounting (config-sbc-sbe-acc-ser)
Server authentication (config-sbc-sbe-auth)
Command History
Cisco IOS XE Release 2.4
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 and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
The priority determines which of the configured servers is selected as the default server and where all requests are sent. A RADIUS client contacts the RADIUS servers sequentially, in order of priority, to establish an active RADIUS session. Each RADIUS client sends call detail records to the currently active RADIUS server.
Examples
The following example shows how to configure accounting servers acctsvr as priority 1 and acctsvr2 as priority 2 on mySbc for RADIUS client instance radius1:
Router# configureRouter(config)# sbc mySbcRouter(config-sbc)# sbeRouter(config-sbc-sbe)# radius accounting radius1Router(config-sbc-sbe-acc)# server acctsvrRouter(config-sbc-sbe-acc-ser)# priority 1Router(config-sbc-sbe-acc-ser)# exitRouter(config-sbc-sbe-acc)# server acctsvr2Router(config-sbc-sbe-acc-ser)# priority 2priority (rsrc-pri)
To configure the priority to associate with the Resource-Priority SIP header, use the priority command in the Resource-Priority SIP header configuration mode. To disable any previously set priority, use the no form of this command.
priority {critical | flash | flash-override | immediate | priority | routine}
no priority {critical | flash | flash-override | immediate | priority | routine}
Syntax Description
Defaults
By default, this command assumes that the priority is routine.
Command Modes
Resource-Priority SIP header (config-sbc-sbe-rsrc-pri-set-rsrc-pri)
Command History
Cisco IOS XE Release 2.4
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 and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
Examples
The following example shows how to configure a critical priority to associate with the Resource-Priority SIP header:
Router# configureRouter(config)# sbc mysbcRouter(config-sbc)# sbeRouter(config-sbc-sbe)# resource-priority-set dsnRouter(config-sbc-sbe-rsrc-pri-set)# resource-priority dsn.flashRouter(config-sbc-sbe-rsrc-pri-set-rsrc-pri)# priority criticalRouter(config-sbc-sbe-rsrc-pri-set-rsrc-pri)#privacy restrict outbound
To configure an H.323 adjacency to apply privacy restriction on outbound messages if the user requests it, use the privacy restrict outbound command in the adjacency H.323 configuration mode. To disallow privacy restriction on outbound messages sent out by the adjacency, use the no form of this command.
privacy restrict outbound
no privacy restrict outbound
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Adjacency H.323 configuration (config-sbc-sbe-adj-h323)
Command History
Cisco IOS XE Release 2.4
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 and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
Examples
The following example shows how the privacy restrict outbound command is used to configure an H.323 adjacency to apply privacy restriction on outbound messages if a user requests it:
Router# configureRouter(config)# sbc mySbcRouter(config-sbc)# sbeRouter(config-sbc-sbe)# adjacency h323 h323ToIsp422Router(config-sbe-adj-h323)# privacy restrict outboundRelated Commands
allow private info
Configures an H.323 adjacency to allow private information on messages sent out by the H.323 adjacency.
profile
To apply a delegate registration profile to a delegate registration subscriber, use the profile command in subscriber-delegate configuration mode. To remove the delegate registration profile, use the no profile command.
profile {profile name}
no profile {profile name}
Syntax Description
profile name
This is the name of the delegate client registration profile that can be applied to a delegate subscriber.
The profile name is a string field of 24 characters maximum length.
Command Default
No default behavior or values
Command Modes
subscriber-delegate configuration mode (config-sbc-sbe-subscriber-delegate)#
Command History
Cisco IOS XE Release 2.4
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
Usage Guidelines
apply the delegate registration profile, created previously with the delegate-profile command, to a delegate registration subscriber
After a delegate profile is configured, the following profile parameters may optionally be configured:
•
duration
•
•
•
Delegate registration is done underneath the SBE configuration for globally unique subscribers.
Examples
The following example configures a provisioned delegate registration profile that can be applied to a delegate registration subscriber and configures a delegate registration for delegate client (aor= sip:bob@isp.example). The delegate registration profile is configured with a duration expiration time of 1000 seconds, a retry count of 5 times, a retry interval of 60 seconds, and a refresh timeout time of 200 seconds:
Router# configure terminalRouter(config)# sbc mySbcRouter(config-sbc)# sbeRouter(config-sbc-sbe)# delegate-profile my-profileRouter(config-sbc-sbe-subscriber-delegate-prof)# duration 1000Router(config-sbc-sbe-subscriber-delegate-prof)# retry-count 5Router(config-sbc-sbe-subscriber-delegate-prof)# retry-interval 60Router(config-sbc-sbe-subscriber-delegate-prof)# refresh-buffer 200Router(config-sbc-sbe-subscriber-delegate-prof)# exitRouter(config-sbc-sbe)# subscriber sip:bob@isp.exampleRouter(config-sbc-sbe-subscriber-entry)# sip-contact sip:steve@10.1.1.2Router(config-sbc-sbe-subscriber-contact)# adjacency CallMgrBRouter(config-sbc-sbe-subscriber-contact)# exitRouter(config-sbc-sbe-subscriber-entry)# delegate-registration sip:registrar@1.1.1.1Router(config-sbc-sbe-subscriber-delegate)# adjacency CallMgrARouter(config-sbc-sbe-subscriber-delegate)# profile my-profileRouter(config-sbc-sbe-subscriber-delegate)# activateRouter(config-sbc-sbe-subscriber-delegate)# endRelated Commands
qos fax
To configure a fax QoS profile, use the qos fax command in SBE configuration mode. To destroy the given profile, use the no form of this command.
qos fax qos-name
no qos fax qos-name
Syntax Description
Defaults
No default behavior or values
Command Modes
SBE configuration (config-sbc-sbe)
Command History
Cisco IOS XE Release 2.4
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 and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
Examples
The following example shows how to enter the submode for configuring a fax QoS profile named residential:
Router# configure terminalRouter(config)# sbc mySbcRouter(config-sbc)# sbeRouter(config-sbc-sbe)# qos fax residentialRouter(config-sbc-sbe-fax)# exitqos sig
To configure a signaling QoS profile, use the qos sig command in SBE configuration mode. To destroy the given profile, use the no form of this command.
qos sig qos-name
no qos sig qos-name
Syntax Description
Defaults
No default behavior or values
Command Modes
SBE configuration (config-sbc-sbe)
Command History
Cisco IOS XE Release 2.4
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 and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
Examples
The following example shows how qos sig command enters the submode for configuring a signaling QoS profile residential:
Router# configureRouter(config)# sbc mySbcRouter(config-sbc)# sbeRouter(config-sbc-sbe)# qos sig residentialRouter(config-sbc-sbe-sig)# exitqos video
To configure a video QoS profile, use the qos video command in the SBE configuration mode. To destroy the given profile, use the no form of this command
qos video qos-name
no qos video qos-name
Syntax Description
Defaults
No default behavior or values
Command Modes
SBE configuration (config-sbc-sbe)
Command History
Cisco IOS XE Release 2.4
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 and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
Examples
The following example shows how to enter the submode for configuring a video QoS profile named residential:
Router# configureRouter(config)# sbc mySbcRouter(config-sbc)# sbeRouter(config-sbc-sbe)# qos video residentialRouter(config-sbc-sbe-video)# exitqos voice
To configure a voice QoS profile, use the qos voice command in SBE configuration mode. To destroy the given profile, use the no form of this command.
qos voice qos-name
no qos voice qos-name
Syntax Description
Defaults
No default behavior or values
Command Modes
SBE configuration (config-sbc-sbe)
Command History
Cisco IOS XE Release 2.4
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 and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
Examples
The following example shows how to enter the submode for configuring a voice QoS profile named residential:
Router# configureRouter(config)# sbc mySbcRouter(config-sbc)# sbeRouter(config-sbc-sbe)# qos voice residentialRouter(config-sbc-sbe-voice)# exitradius
To create and configuring a RADIUS client for accounting or authentication purposes, use the radius command in SBE configuration mode. To delete the RADIUS client, use the no form of this command.
radius [accounting client-name | authentication]
no radius [accounting client-name | authentication]
Syntax Description
accounting client-name
Specifies the name to assign to the accounting RADIUS client.
authentication
Enables client authentication.
Defaults
No default behavior or values
Command Modes
SBE configuration (config-sbc-sbe)
Command History
Cisco IOS XE Release 2.4
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 and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
Each named client maintains a list of servers consisting of one active server and a set of standby servers. The list is traversed by the client in order of configured priority. An SBC instance can be configured with multiple clients (each with its own ordered set of servers) if call detail reports (CDRs) must be sent to multiple RADIUS servers simultaneously. CDRs are sent by the client to the currently active server. If the active server cannot be contacted, a standby server is used.
Examples
The following example shows how to create a RADIUS client instance called radius1 and enables client authentication:
Router# configureRouter(config)# sbc mySbcRouter(config-sbc)# sbeRouter(config-sbc-sbe)# radius accounting radius1Router(config-sbc-sbe-acc)# exitRouter(config-sbc-sbe)# radius authenticationRouter(config-sbc-sbe-auth)# exitRelated Commands
range
To map a range of response codes to a response code, use the range command in the SIP method-profile map-status-coding configuration mode. To destroy the mapping, use the no form of this command.
range statuscoderange value statuscodevalue
no range statuscoderange value statuscodevalue
Syntax Description
Defaults
No default behavior or values
Command Modes
SIP method-profile map-status-coding configuration (config-sbc-sbe-sip-mth-ele-map)
Command History
Cisco IOS XE Release 2.4
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 and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
Examples
The following example shows how the method command adds a method test to the method profile MyProfile:
Router/Admi# configureRouter/Admi(config)# sbc testRouter/Admi(config-sbc)# sbeRouter/Admi(config-sbc-sbe)# sip method-profile mthdprof1Router/Admi(config-sbc-sbe-sip-mth)# method INVITERouter/Admi(config-sbc-sbe-sip-mth-ele)# map-status-codeRouter/Admi(config-sbc-sbe-sip-mth-ele)# map-status-codeRouter/Admi(config-sbc-sbe-sip-mth-ele-map)# range 5XX value 500
ras retry
To configure an H.323 Registration, Admission, and Status (RAS) retry count for an RAS transaction type, use the ras retry command in the appropriate configuration mode. To return to the default value for the specified RAS transaction type, use the no form of this command.
ras retry {arq | brq | drq | grq | rrq | urq} value
no ras retry {arq | brq | drq | grq | rrq | urq} value
Syntax Description
Command Default
The default values are 2 for all except URQ which is 1.
Command Modes
Adjacency H.323 configuration (config-sbc-sbe-adj-h323)
H.323 configuration (config-sbc-sbe-h323)
Command History
Cisco IOS XE Release 2.4
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 and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
Examples
The following example shows how the ras retry command configures an H.323 RAS retry count in Adjacency H.323 configuration mode:
Router# configureRouter(config)# sbc mySbcRouter(config-sbc)# sbeRouter(config-sbc-sbe)# adjacency h323 h323ToIsp42Router(config-sbc-sbe-adj-h323)# ras retry arq 5The following example shows how the ras retry command configures an H.323 RAS retry count in H.323 configuration mode:
Router# configureRouter(config)# sbc mySbcRouter(config-sbc)# sbeRouter(config-sbc-sbe)# h323Router(config-sbc-sbe-h323)# ras retry arq 5ras rrq
To configure the registration request (RRQ), use the ras rrq command in the appropriate configuration mode. To return to the default value, use the no form of this command.
ras rrq {keepalive | ttl} value
no ras rrq {keepalive | ttl} value
Syntax Description
Command Default
The default keepalive value is 45000 milliseconds.
The default ttl value is 2 seconds.
Command Modes
Adjacency H.323 configuration (config-sbc-sbe-adj-h323)
H.323 configuration (config-sbc-sbe-h323)
Command History
Cisco IOS XE Release 2.4
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 and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
Examples
The following example shows how the ras rrq command configures H.323 RAS RRQ in adjacency H.323 configuration mode:
Router# configureRouter(config)# sbc mySbcRouter(config-sbc)# sbeRouter(config-sbc-sbe)# adjacency h323 h323ToIsp42Router(config-sbc-sbe-adj-h323)# ras rrq ttl 100Router(config-sbc-sbe-adj-h323)# ras rrq keepalive 60The following example shows how the ras rrq command configures RAS RRQ in H.323 configuration mode:
Router# configureRouter(config)# sbc mySbcRouter(config-sbc)# sbeRouter(config-sbc-sbe)# h323Router(config-sbc-sbe-h323)# ras rrq ttl 100Router(config-sbc-sbe-h323)# ras rrq keepalive 60ras timeout
To configure an H.323 RAS timeout interval, use the ras timeout command in the appropriate configuration mode. To return to the default value, use the no form of this command.
ras timeout {arq | brq | drq | grq | rrq | urq} value
no ras timeout {arq | brq | drq | grq | rrq | urq} value
Syntax Description
Command Default
The default values vary depending on the transaction type.
Command Modes
Adjacency H.323 configuration (config-sbc-sbe-adj-h323)
H.323 configuration (config-sbc-sbe-h323)
Command History
Cisco IOS XE Release 2.4
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 and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
Examples
The following example shows how the ras timeout command configures an H.323 RAS timeout interval in adjacency H.323 configuration mode.
Router# configureRouter(config)# sbc mySbcRouter(config-sbc)# sbeRouter(config-sbc-sbe)# adjacency h323 h323ToIsp42Router(config-sbc-sbe-adj-h323)# ras timeout arq 1The following example shows how the ras timeout command configures an H.323 RAS timeout interval in H.323 configuration mode.
Router# configureRouter(config)# sbc mySbcRouter(config-sbc)# sbeRouter(config-sbc-sbe)# h323Router(config-sbc-sbe-h323)# ras timeout arq 1reason
To enter a submode for configuring a limit to a specific event type on the source (a port, IP address, VPN, global address space), use the reason command in SBE blacklist mode. The no form of this command, returns the event to its previous values.
reason {event | description}
no reason
Syntax Description
Command Default
No default behavior or values
Command Modes
SBE blacklist (config-sbc-sbe-blacklist)
Command History
Cisco IOS XE Release 2.4
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
Usage Guidelines
This field can only take the explicit strings described in the Syntax Description.
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.
Examples
The following example shows the use of the reason command in context:
Router# configureRouter(config)# sbc mysbcRouter(config-sbc)# sbeRouter(config-sbc-sbe)# blacklistRouter(config-sbc-sbe-blacklist)# ipv4 125.12.12.15Router(config-sbc-sbe-blacklist-ipv4)# reason authentication-failureRelated Commands
record-media-create-info
To activate support for media information support in billing, use the record-media-create-info command in SBE billing configuration mode. To disable support, use the no form of this command.
record-media-create-info
no record-media-create-info
Syntax Description
This command has no arguments or keywords.
Defaults
By default, this is disabled.
Command Modes
SBE billing configuration (config-sbc-sbe-billing)
Command History
Cisco IOS XE Release 2.4
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 and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
Examples
The following example shows how to activate the billing functionality after configuration is committed:
Router/Admin# configureRouter/Admin(config)# sbc mySbcRouter/Admin(config-sbc)# sbeRouter/Admin(config-sbc-sbe)# billingRouter/Admin(config-sbc-sbe-billing)# record-media-create-info
Related Commands
redirect-limit
To configure the maximum number of redirections that SBC performs on a call, use the redirect-limit command in SBE configuration mode. The no form of this command returns the adjacency to the default behavior.
redirect-limit limit
no redirect-limit limit
Syntax Description
Command Default
The default number of redirections is 2.
Command Modes
SBE configuration (config-sbc-sbe)
Command History
Cisco IOS XE Release 2.4
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 and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
Examples
The following example shows how to configure the maximum number of SIP 3xx retries as 4:
Router# configureRouter(config)# sbc mysbcRouter(config-sbc)# sbeRouter(config-sbc-sbe)# redirect-limit 4redirect-mode
To configure the behavior of SBC on receipt of a 3xx response to an invite from the SIP adjacency, use the redirect-mode command in adjacency SIP configuration mode. The no form of this command returns the adjacency to the default behavior.
redirect-mode {pass-through | recurse}
no redirect-mode{pass-through | recurse}
Syntax Description
Command Default
pass-through
Command Modes
Adjacency SIP configuration (config-sbc-sbe-adj-sip)
Command History
Cisco IOS XE Release 2.4
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 and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
Examples
The following example shows how to resend an invite to the first listed contact address or else pass the 3xx responses back to the sender:
Router# configureRouter(config)# sbc mysbcRouter(config-sbc)# sbeRouter(config-sbc-sbe)# adjacency sip test1Router(config-sbc-sbe-adj-sip)# redirect-mode recurseRouter(config-sbc-sbe-adj-sip)#Related Commands
redirect-limit
Configures the maximum number of redirections SBC performs on a call.
refresh-buffer
To configure the length of time by which the Cisco Unified Border Element (SP Edition) attempts to renew or refresh the address location with a delegate registration before the specified expiration time, use the refresh-buffer command in subscriber delegate profile configuration mode. To reset the refresh time to the default refresh time, use the no refresh-buffer command.
refresh-buffer{timeout in secs}
no refresh-buffer{timeout in secs}
Syntax Description
timeout in secs
This is the refresh expiration time in seconds. The range is 1 to 2,147,483 seconds. The default is 30 seconds.
Command Default
The default refresh expiration time is 30 seconds.
Command Modes
Subscriber delegate profile configuration mode (config-sbc-sbe-subscriber-delegate-prof)#
Command History
Cisco IOS XE Release 2.4
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
Usage Guidelines
This is the length of time by which the SBC attempts to renew or refresh the address location with a delegate registration before the specified expiration time (configured with the duration command). This is one of the delegate profile parameters you can configure.
After a delegate profile is configured, the following profile parameters may optionally be configured:
•
•
•
•
Examples
The following example configures a provisioned delegate registration profile that can be applied to a delegate registration subscriber and configures a delegate registration for delegate client (aor= sip:bob@isp.example). The delegate registration profile is configured with a duration expiration time of 1000 seconds, a retry count of 5 times, a retry interval of 60 seconds, and a refresh timeout time of 200 seconds:
Router# configure terminalRouter(config)# sbc mySbcRouter(config-sbc)# sbeRouter(config-sbc-sbe)# delegate-profile my-profileRouter(config-sbc-sbe-subscriber-delegate-prof)# duration 1000Router(config-sbc-sbe-subscriber-delegate-prof)# retry-count 5Router(config-sbc-sbe-subscriber-delegate-prof)# retry-interval 60Router(config-sbc-sbe-subscriber-delegate-prof)# refresh-buffer 200Router(config-sbc-sbe-subscriber-delegate-prof)# exitRouter(config-sbc-sbe)# subscriber sip:bob@isp.exampleRouter(config-sbc-sbe-subscriber-entry)# sip-contact sip:steve@10.1.1.2Router(config-sbc-sbe-subscriber-contact)# adjacency CallMgrBRouter(config-sbc-sbe-subscriber-contact)# exitRouter(config-sbc-sbe-subscriber-entry)# delegate-registration sip:registrar@1.1.1.1Router(config-sbc-sbe-subscriber-delegate)# adjacency CallMgrARouter(config-sbc-sbe-subscriber-delegate)# profile my-profileRouter(config-sbc-sbe-subscriber-delegate)# activateRouter(config-sbc-sbe-subscriber-delegate)# endRelated Commands
registration aggregate
To enable Aggregate Registration, use the registration aggregate command in adjacency sip configuration mode. To disable Aggregate Registration, use the no registration aggregate command.
registration aggregate
no registration aggregate
Syntax Description
This command has no arguments or keywords.
Command Default
No default behavior or values
Command Modes
adjacency sip configuration (config-sbc-sbe-adj-sip)#
Command History
Cisco IOS XE Release 2.4
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
Usage Guidelines
This command enables Aggregate Registration support from the specified SIP adjacency facing the Registrar server.
Examples
The following example enables Aggregate Registration on adjacency Cary-IP-PBX, which has a preset access profile specified because it faces an access device on a UNI network. The last three commands in the configuration, entered in the correct order, enable the aggregate registration call routing to work.
sbc mySbcsbeadjacancy sip Cary-IP-PBXregistration rewrite-registerinherit profile preset-accessregistration aggregateheader-name to passthroughrequest-line request-uri rewriteThe following example displays detailed output for adjacency Cary-IP-PBX, including the "Register Aggregate:" field that shows Aggregate Registration is "Enabled."
Router# show sbc mySbc sbe adjacencies Cary-IP-PBX detailSBC Service "mySBC"Adjacency Cary-IP-PBX (SIP)Status: AttachedSignaling address: 100.100.100.100:5060, VRF AdminSignaling-peer: 10.10.51.10:5060Force next hop: NoAccount:Group: NoneIn header profile: DefaultOut header profile: DefaultIn method profile: DefaultOut method profile: DefaultIn UA option prof: DefaultOut UA option prof: DefaultIn proxy opt prof: DefaultOut proxy opt prof: DefaultPriority set name: NoneLocal-id: NoneRewrite REGISTER: OffTarget address: NoneRegister Out Timer: 1800 secondsRegister Aggregate: EnabledNAT Status: Auto DetectReg-min-expiry: 30 secondsFast-register: EnabledFast-register-int: 30 secondsAuthenticated mode: NoneAuthenticated realm: NoneAuth. nonce life time: 300 secondsIMS visited NetID: NoneInherit profile: DefaultForce next hop: NoHome network Id: NoneUnEncrypt key data: NoneSIPI passthrough: NoRewrite from domain: YesRewrite to header: YesMedia passthrough: NoPreferred transport: UDPHunting Triggers: Global TriggersRedirect mode: Pass-throughSecurity: UntrustedOutbound-flood-rate: NonePing-enabled: NoSignaling Peer Status: Not TestedRewrite Request-uri: EnabledRegistration Monitor: DisabledThe following is a configuration example showing that Aggregate Registration and SoftSwitch Shielding are configured:
sbc testsbesip header-profile myheaderheader P-Called-Party-ID entry 1action passadjacency sip sippa ==============================> Adjacency facing IP-PBXheader-profile inbound myheaderheader-profile outbound myheaderinherit profile preset-accesspreferred-transport udpsignaling-address ipv4 99.99.103.150signaling-port 5080remote-address ipv4 100.100.1.64 255.255.255.255signaling-peer 100.100.1.64signaling-peer-port 5080registration rewrite-registeraccount sipp-aregistration aggregatefast-register disableheader-name to passthroughrequest-line request-uri rewriteattachadjacency sip sippb ==================================> Adjacency facing REGISTRARnat force-offheader-profile inbound myheaderheader-profile outbound myheaderinherit profile preset-corepreferred-transport udpsignaling-address ipv4 99.99.103.150signaling-port 5082remote-address ipv4 100.100.1.64 255.255.255.255signaling-peer 100.100.1.64signaling-peer-port 5082account sipp-bregistration target address 100.100.1.64registration target port 5084fast-register disableattachcac-policy-set 1first-cac-table mytablefirst-cac-scope src-adjacencycac-table mytabletable-type limit adjacencyentry 1match-value sippamax-num-calls 10action cac-completecompleteactive-cac-policy-set 1call-policy-set 1first-call-routing-table src-acc-tablefirst-reg-routing-table src-acc-tablertg-src-adjacency-table src-acc-tableentry 1action completedst-adjacency sippbmatch-adjacency sippaentry 2action completedst-adjacency sippamatch-adjacency sippbcompletecall-policy-set 2active-call-policy-set 1!vdbe globalunexpected-source-alertingmedia-address ipv4 99.99.103.156media-timeout 9999activate!Softswitch shielding config===================sbc testsbeadjacency sip sippasignaling-address ipv4 99.99.103.150signaling-port 5080remote-address ipv4 100.100.1.64 255.255.255.255signaling-peer 100.100.1.64signaling-peer-port 5080registration rewrite-registeraccount sipp-aattachadjacency sip sippbsignaling-address ipv4 99.99.103.150signaling-port 5082remote-address ipv4 100.100.1.64 255.255.255.255signaling-peer 100.100.1.64signaling-peer-port 5082account sipp-bregistration outgoing timer 86400registration target address 100.100.1.64registration target port 5084attachcall-policy-set 1first-call-routing-table src-acc-tablefirst-reg-routing-table src-acc-tablertg-src-adjacency-table src-acc-tableentry 1action completedst-adjacency sippbmatch-adjacency sippaentry 2action completedst-adjacency sippamatch-adjacency sippbcompleteactive-call-policy-set 1!media-address ipv4 99.99.103.156media-timeout 9999activate!Related Commands
registration monitor
To enable the Registrar server to monitor subscriber event changes due to registration changes, use the registration monitor command in adjacency sip configuration mode. To disable registration monitoring, use the no registration monitor command.
registration monitor
no registration monitor
Syntax Description
This command has no arguments or keywords.
Command Default
No default behavior or values
Command Modes
adjacency sip configuration (config-sbc-sbe-adj-sip)#
Command History
Cisco IOS XE Release 2.4
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
Usage Guidelines
This command enables the Registrar server to monitor event subscriptions due to changes to the state of the registration. Subscription changes for each subscriber that re-registers with the Registrar server situation on the specified adjacency may cause Cisco Unified Border Element (SP Edition) to add, remove, or update the subscriber state.
Examples
The following example shows how registration monitoring is enabled:
sbc Raleigh-SBCsbeadjacancy sip Cary-IP-PBXregistration monitorThe following example displays detailed output for adjacency Cary-IP-PBX, including the "Registration Monitor:" field that shows Registration Monitoring is "Enabled:"
Router# show sbc mySBC sbe adjacencies Cary-IP-PBX detailSBC Service "mySbc"Adjacency Cary-IP-PBX (SIP)Status: AttachedSignaling address: 100.100.100.100:5060, VRF AdminSignaling-peer: 10.10.51.10:5060Force next hop: NoAccount:Group: NoneIn header profile: DefaultOut header profile: DefaultIn method profile: DefaultOut method profile: DefaultIn UA option prof: DefaultOut UA option prof: DefaultIn proxy opt prof: DefaultOut proxy opt prof: DefaultPriority set name: NoneLocal-id: NoneRewrite REGISTER: OffTarget address: NoneRegister Out Timer: 1800 secondsRegister Aggregate: EnabledNAT Status: Auto DetectReg-min-expiry: 30 secondsFast-register: EnabledFast-register-int: 30 secondsAuthenticated mode: NoneAuthenticated realm: NoneAuth. nonce life time: 300 secondsIMS visited NetID: NoneInherit profile: DefaultForce next hop: NoHome network Id: NoneUnEncrypt key data: NoneSIPI passthrough: NoRewrite from domain: YesRewrite to header: YesMedia passthrough: NoPreferred transport: UDPHunting Triggers: Global TriggersRedirect mode: Pass-throughSecurity: UntrustedOutbound-flood-rate: NonePing-enabled: NoSignaling Peer Status: Not TestedRewrite Request-uri: DisabledRegistration Monitor: EnabledRelated Commands
registration outgoing timer
To enable SoftSwitch Shielding by setting the registration outgoing timer for the time interval when Cisco Unified Border Element (SP Edition) forwards outgoing registration messages, use the registration outgoing timer command in adjacency sip configuration mode. To set the outgoing time interval to zero and disable SoftSwitch Shielding, use the no registration outgoing timer command.
registration outgoing timer {sec}
no registration outgoing timer {sec}
Syntax Description
Command Default
The default value of zero disables SoftSwitch Shielding.
Command Modes
adjacency sip configuration (config-sbc-sbe-adj-sip)#
Command History
Cisco IOS XE Release 2.4
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
Usage Guidelines
This command enables SoftSwitch Shielding. It sets the registration timeout timer for the time interval in seconds when Cisco Unified Border Element (SP Edition) keeps forwarding outgoing REGISTER messages to the softswitch before timing out.
Examples
The following example configures SoftSwitch Shielding on adjacency "SoftSwitch:"
sbc mySbcsbeadjacancy sip SoftSwitchregistration outgoing timer <sec>registration rewrite-registerinherit profile preset-coreThe following is a configuration example showing that SoftSwitch Shielding is configured for adjacency sippb:
SoftSwitch Shielding Configuration===================================sbc testsbeadjacency sip sippasignaling-address ipv4 99.99.103.150signaling-port 5080remote-address ipv4 100.100.1.64 255.255.255.255signaling-peer 100.100.1.64signaling-peer-port 5080registration rewrite-registeraccount sipp-aattachadjacency sip sippbsignaling-address ipv4 99.99.103.150signaling-port 5082remote-address ipv4 100.100.1.64 255.255.255.255signaling-peer 100.100.1.64signaling-peer-port 5082account sipp-bregistration outgoing timer 86400registration target address 100.100.1.64registration target port 5084attachcall-policy-set 1first-call-routing-table src-acc-tablefirst-reg-routing-table src-acc-tablertg-src-adjacency-table src-acc-tableentry 1action completedst-adjacency sippbmatch-adjacency sippaentry 2action completedst-adjacency sippamatch-adjacency sippbcompleteactive-call-policy-set 1!media-address ipv4 99.99.103.156media-timeout 9999activate!The following example shows detailed information for sippb adjacency, including the "Register Out Interval" field that indicates SoftSwitch Shielding is enabled with a timeout interval of 86400 seconds or 24 hours:
show sbc test sbe adjacencies sippb detailSBC Service "test"Adjacency sippb (SIP)Status: AttachedSignaling address: 99.99.103.150:5082Signaling-peer: 100.100.1.64:5082Force next hop: NoAccount: sipp-bGroup: NoneIn header profile: DefaultOut header profile: DefaultIn method profile: DefaultOut method profile: DefaultIn UA option prof: DefaultOut UA option prof: DefaultIn proxy opt prof: DefaultOut proxy opt prof: DefaultPriority set name: NoneLocal-id: NoneRewrite REGISTER: OffTarget address: 100.100.1.64:5084NAT Status: Auto DetectReg-min-expiry: 3000 secondsFast-register: EnabledFast-register-int: 30 secondsRegister aggregate: DisabledRegister Out Interval: 86400 secondsAuthenticated mode: NoneAuthenticated realm: NoneAuth. nonce life time: 300 secondsIMS visited NetID: NoneInherit profile: DefaultForce next hop: NoHome network Id: NoneUnEncrypt key data: NoneSIPI passthrough: NoRewrite from domain: YesRewrite to header: YesMedia passthrough: NoClient authentication: NoHunting Triggers: Global TriggersRedirect mode: Pass-throughSecurity: Untrusted-UnencryptedSignaling Peer Status: Not TestedRewrite Request-uri: DisabledRegistration Monitor: DisabledDTMF SIP NOTIFY Relay: EnabledDTMF SIP NOTIFY Interval: 2000DTMF SIP default duration: 200DTMF Preferred Method: SIP NOTIFYRelated Commands
registration rewrite-register
To configure the SIP register request rewriting, use the registration rewrite-register command in Adjacency SIP configuration mode. To deconfigure the register request rewriting, use the no form of this command.
registration rewrite-register
no registration rewrite-register
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Adjacency SIP configuration (config-sbc-sbe-adj-sip)
Command History
Cisco IOS XE Release 2.4
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 and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
Examples
The following example shows how the registration rewrite-register command configures the SIP register request rewriting on SIP adjacency SipToIsp42.
Router# configureRouter(config)# sbc mySbcRouter(config-sbc)# sbeRouter(config-sbc-sbe)# adjacency sip SipToIsp42Router(config-sbc-sbe-adj-sip)# registration rewrite-registerregistration target address
To set the address to be used when an outbound SIP register request rewriting occurs, use the registration target address command in Adjacency SIP configuration mode. To remove the address, use the no form of this command.
registration target address host address
no registration target address host address
Syntax Description
Defaults
No default behavior or values
Command Modes
Adjacency SIP configuration (config-sbc-sbe-adj-sip)
Command History
Cisco IOS XE Release 2.4
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 and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
Examples
The following example shows how the registration target address command sets the target address for SIP adjacency SipToIsp42 as example.com:
Router# configureRouter(config)# sbc mySbcRouter(config-sbc)# sbeRouter(config-sbc-sbe)# adjacency sip SipToIsp42Router(config-sbc-sbe-adj-sip)# registration target address example.comregistration target port
To set the port to be used when an outbound SIP REGISTER request rewriting occurs, use the registration target port command in Adjacency SIP configuration mode. To enter the default value, use the no form of this command.
registration target port port-number
no registration target port port-number
Syntax Description
port-number
Specifies the port number to use when an outbound SIP REGISTER request rewriting occurs. Valid values can be from 1 to 65535. If you enter the default value of 0, no port address is set.
Defaults
Default value is 0. This cannot be directly entered.
Command Modes
Adjacency SIP configuration (config-sbc-sbe-adj-sip)
Command History
Cisco IOS XE Release 2.4
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 and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
Examples
The following example shows how the registration target port command sets the port number for SIP adjacency SipToIsp42 as 5070:
Router# configureRouter(config)# sbc mySbcRouter(config-sbc)# sbeRouter(config-sbc-sbe)# adjacency sip SipToIsp42Router(config-sbc-sbe-adj-sip)# registration target port 5070reg-min-expiry
To configure the minimum registration period in seconds on the SIP adjacency, use the reg-min-expiry command in the adjacency SIP configuration mode. To enter the default value, use the no form of this command.
reg-min-expiry period
no reg-min-expiry period
Syntax Description
Defaults
3000 seconds
Command Modes
Adjacency SIP configuration (config-sbc-sbe-adj-sip)
Command History
Cisco IOS XE Release 2.4
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
Usage Guidelines
This is the minimum expiry period accepted on a subscriber registration if not fast-pathing, or the minimum-expiry period passed onward if fast-pathing is in use.
The minimum registration period cannot be changed after an adjacency has been configured. To change the minimum registration period, remove the adjacency by running no sbc sbc-name sbe adjacency sip adjacency-name command and then reconfigure the adjacency.
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.
Examples
The following example shows how to enable the register minimum expiry on the SIP adjacency SipToIsp42 to 300 seconds:
Router# configureRouter(config)# sbc mySbcRouter(config-sbc)# sbeRouter(config-sbc-sbe)# adjacency sip SipToIsp42Router(config-sbc-sbe-adj-sip)# reg-min-expiry 300Router(config-sbc-sbe-adj-sip)# exitremote-address ipv4
To configure an H.323 or SIP adjacency to restrict the set of remote signaling peers that can be contacted over the adjacency to those with the given IP address prefix, use the remote-address ipv4 command in the appropriate configuration mode. To remove this configuration, use the no form of this command.
To configure the remote address for vDBE H.248 controller, use the remote-address ipv4 command in the vDBE h248 mode. To return to the default value, use the no form of this command.
remote-address ipv4 ip-address ip-mask
no remote-address ipv4 ip-address ip-mask
Syntax Description
Defaults
No default behavior or values
Command Modes
Adjacency SIP configuration (config-sbc-sbe-adj-sip)
Adjacency H323 configuration (config-sbc-sbe-adj-h323)
VDBE H248(config-sbc-dbe-vdbe-h248)
Command History
Cisco IOS XE Release 2.1
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
Usage Guidelines
The remote-address cannot be deleted by itself; the entire controller must be removed using the no controller h248 command.
Examples
The following example creates a DBE service on an SBC called mySbc, enters into SBC-DBE configuration and VDBE configuration modes, creates an H.248 controller with index 1, enters into H248 configuration mode, and configures the remote address as 1.1.1.1 on the H.248 controller:
Router# configure terminalRouter(config)# sbc mySbc dbeRouter(config-sbc-dbe)# vdbeRouter(config-sbc-dbe-vdbe)# controller h248 1Router(config-sbc-dbe-vdbe-h248)# remote-address ipv4 1.1.1.1Router(config-sbc-dbe-vdbe-h248)# exitThe following example shows how to configure the SIP adjacency SipToIsp42 to match calls from 36.36.36.20 to this adjacency:
Router(config)# sbc mySbcRouter(config-sbc)# sbeRouter(config-sbc-sbe)# adjacency sip SipToIsp42Router(config-sbc-sbe-adj-sip)# remote-address ipv4 36.36.36.20 255.255.255.0
Related Commands
remote-port
To define the port to connect to on the SBE for an H.248 controller, use the remote-port command in VDBE h248 mode.
remote-port port-num
Syntax Description
port-num
This is the port number to be configured.
If the port is not configured or is configured with the value zero, then the H.248 default port number, 2944, is used.
Defaults
Port number 2944
Command Modes
VDBE h248 (config-sbc-dbe-h248)
Command History
Cisco IOS XE Release 2.1
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
Usage Guidelines
The local-port and control-address are not applied until the controller is added and the remote address is configured. Also, the controller should be deleted to delete the remote address.
If the port is not configured, or is configured with the value zero, then the H.248 default port number, 2944, is used.
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.
Examples
The following example configures the port to 2944 on the H.248 controller with index 1:
Router# configure terminalRouter(config)# sbc mySbc dbeRouter(config-sbc-dbe)# vdbeRouter(config-sbc-dbe-vdbe)# controller h248 1Router(config-sbc-dbe-vdbe-h248)# remote-port 2944Router(config-sbc-dbe-vdbe-h248)# exitRelated Commands
request-line request-uri rewrite
To request the SBC to rewrite the Request-URI to a different user and hostname before sending a request to a registered subscriber, use the request-line request-uri rewrite command in Adjacency SIP configuration mode.
request-line request-uri rewrite
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Adjacency SIP configuration (config-sbc-sbe-adj-sip)
Command History
Cisco IOS XE Release 2.4
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
Usage Guidelines
This command is used in Aggregate Registration only and is configured on the adjacency facing the IP-PBX which requires Aggregate Registration. This command allows outgoing calls to the endpoint registered with Aggregate Registration. The SBC rewrites the Request-URI as <user>@<hostname>, before sending a request to the registered subscriber (IP-PBX) on an adjacency.
The "request-uri" field indicates whether this adjacency faces an aggregation device, such as an IP-PBX, which cannot route incoming messages based on the P-Called-Party-ID or To header, but only on the Request-URI.
The Request-URI would normally be set to the Contact address registered by the IP-PBX rather than an endpoint address.
Before sending a request to a registered subscriber, for example IP-PBX, on this adjacency, the SBC will rewrite the Request-URI as <user>@<hostname> where:
•
•
Uniform Resource Identifier (URI) is an IP address of the subscriber. It is a string field of 62 characters maximum length.
Examples
The following example shows the rewrite of the Request-URI to sip:bill@1.1.1.1 in an Aggregate Registration configuration:
Router(config-sbc-sbe-adj-sip)# request-line request-uri rewrite sip:bill@1.1.1.1
The following example enables Aggregate Registration on adjacency Cary-IP-PBX, which has a preset access profile specified because it faces an access device on a UNI network. The last three commands in the configuration, entered in the correct order, enable the aggregate registration call routing to work.
sbc mySbcsbeadjacancy sip Cary-IP-PBXregistration rewrite-registerinherit profile preset-accessregistration aggregateheader-name to passthroughrequest-line request-uri rewriteRelated Commands
header-name
Configures the contact header and passthrough header in non-REGISTER requests.
registration aggregate
Enables Aggregate Registration.
resource-priority
To configure the priority of a resource-priority header string, use the resource-priority command in resource priority mode. To deconfigure the priority, use the no form of this command.
resource-priority value
no resource-priority value
Syntax Description
value
Specifies the string value to be assigned the priority. The value must be followed by the priority as shown: value.priority.
Defaults
No default behavior or values
Command Modes
Resource priority (config-sbc-sbe-rsrc-pri-set)
Command History
Cisco IOS XE Release 2.4
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 and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
Examples
The following example shows how the resource-priority command configures the priority for resource-priority header string dsn.
Router# configureRouter(config)# sbc mysbcRouter(config-sbc)# sbeRouter(config-sbc-sbe)# resource-priority-set dsnRouter(config-sbc-sbe-rsrc-pri-set)# resource-priority dsn.flashresource-priority-set
To establish the resource priority set to be used with the specified SIP adjacency in the mode of an SBE entity, use the resource-priority-set command in adjacency SIP configuration mode. To remove the priority set, use the no form of this command.
resource-priority-set resource-priority-set-name
no resource-priority-set resource-priority-set-name
Syntax Description
Command Default
No default behavior or values
Command Modes
Adjacency SIP configuration (config-sbc-sbe-adj-sip)
Command History
Cisco IOS XE Release 2.4
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 and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
Examples
The following example shows how the resource-priority-set command sets the SIP adjacency SipToIsp42 with the resource-priority-set named dsn:
Router# configureRouter(config)# sbc mysbcRouter(config-sbc)# sbeRouter(config-sbc-sbe)# adjacency sip SipToIsp42Router(config-sbc-sbe-adj-sip)# resource-priority-set dsnresponse-code-mapping
To define a response code map, use the response-code-mapping command in SIP method-profile configuration mode. The no form of this command removes all mappings.
response-code-mapping map
no response-code-mapping map
Syntax Description
Command Default
No response code mapping.
Command Modes
SIP method-profile configuration (config-sbc-sbe-sip-mth)
Command History
Cisco IOS XE Release 2.4
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 and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
Examples
The following example defines a response code map:
Router# configureRouter(config)# sbc mySbcRouter(config-sbc)# sbeRouter(config-sbc-sbe)# sip method-profile MyProfileRouter(config-sbc-sbe-sip-mth)# response-code-mapping maptestRelated Commands
retry-count
To configure the number of times the Cisco Unified Border Element (SP Edition) repeats the provisioned delegate registration processing after the retry interval ends, use the retry-count command in subscriber delegate profile configuration mode. To reset the retry count time to the default retry count time, use the no retry-count command.
retry-count {#times to retry}
no retry-count {#times to retry}
Syntax Description
#times to retry
the number of times the SBC repeats the delegate registration processing after the retry interval ends. The default is 3 times. The range is 0 to 255 times.
Command Default
The default number of retries is 3 times.
Command Modes
Subscriber delegate profile configuration mode (config-sbc-sbe-subscriber-delegate-prof)#
Command History
Cisco IOS XE Release 2.4
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
Usage Guidelines
Configures the number of times the Cisco Unified Border Element (SP Edition) repeats the delegate registration processing after the retry interval ends. The default is 3 times. This is one of the delegate profile parameters you can configure.
After a delegate profile is configured, the following profile parameters may optionally be configured:
•
•
•
•
Examples
The following example configures a provisioned delegate registration profile that can be applied to a delegate registration subscriber and configures a delegate registration for delegate client (aor= sip:bob@isp.example). The delegate registration profile is configured with a duration expiration time of 1000 seconds, a retry count of 5 times, a retry interval of 60 seconds, and a refresh timeout time of 200 seconds:
Router# configure terminalRouter(config)# sbc mySbcRouter(config-sbc)# sbeRouter(config-sbc-sbe)# delegate-profile my-profileRouter(config-sbc-sbe-subscriber-delegate-prof)# duration 1000Router(config-sbc-sbe-subscriber-delegate-prof)# retry-count 5Router(config-sbc-sbe-subscriber-delegate-prof)# retry-interval 60Router(config-sbc-sbe-subscriber-delegate-prof)# refresh-buffer 200Router(config-sbc-sbe-subscriber-delegate-prof)# exitRouter(config-sbc-sbe)# subscriber sip:bob@isp.exampleRouter(config-sbc-sbe-subscriber-entry)# sip-contact sip:steve@10.1.1.2Router(config-sbc-sbe-subscriber-contact)# adjacency CallMgrBRouter(config-sbc-sbe-subscriber-contact)# exitRouter(config-sbc-sbe-subscriber-entry)# delegate-registration sip:registrar@1.1.1.1Router(config-sbc-sbe-subscriber-delegate)# adjacency CallMgrARouter(config-sbc-sbe-subscriber-delegate)# profile my-profileRouter(config-sbc-sbe-subscriber-delegate)# activateRouter(config-sbc-sbe-subscriber-delegate)# endRelated Commands
retry-interval
To set the interval for resending an accounting request to the Radius server, use the retry-interval command in SBE accounting mode. To set the interval to its default, use the no form of this command.
retry-interval range
no retry-interval range
Syntax Description
Command Default
1200 ms
Command Modes
Server accounting (config-sbc-sbe-acc-ser)
Server authentication (config-sbc-sbe-auth)
Command History
Cisco IOS XE Release 2.4
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 and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
Examples
The following example shows how to set the retry-interval to 1000 ms.
Router# configureRouter(config)# sbc uut105-1Router(config-sbc)# sbeRouter(config-sbc-sbe)# radius accounting SBC1-account-1Router(config-sbc-sbe-acc)# retry-interval 1000Related Commands
retry-limit
Sets the retry interval to the RADIUS server.
concurrent-requests
Sets the maximum number of concurrent requests to the RADIUS server.
activate
Activates the RADIUS client.
retry-interval (registration)
To configure the length of time the Cisco Unified Border Element (SP Edition) waits before it retries provisioned delegate registration, use the retry-interval command in subscriber delegate profile configuration mode. To reset the retry interval to the default retry interval, use the no retry-interval command.
retry-interval {retry time in secs}
no retry-interval {retry time in secs}
Syntax Description
retry time in secs
This is the length of time before the delegate registration processing is retried after the retry interval ends. The range is 1 to 2,147,483 seconds. The default is 30 seconds.
Command Default
The default retry time is 30 seconds.
Command Modes
Subscriber delegate profile configuration mode (config-sbc-sbe-subscriber-delegate-prof)#
Command History
Cisco IOS XE Release 2.4
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
Usage Guidelines
Configures the length of time the SBC waits before it retries delegate registration after the retry interval ends. The default is 30 seconds. This is one of the delegate profile parameters you can configure.
After a delegate profile is configured, the following profile parameters may optionally be configured:
•
•
•
•
Examples
The following example configures a provisioned delegate registration profile that can be applied to a delegate registration subscriber and configures a delegate registration for delegate client (aor= sip:bob@isp.example). The delegate registration profile is configured with a duration expiration time of 1000 seconds, a retry count of 5 times, a retry interval of 60 seconds, and a refresh timeout time of 200 seconds:
Router# configure terminalRouter(config)# sbc mySbcRouter(config-sbc)# sbeRouter(config-sbc-sbe)# delegate-profile my-profileRouter(config-sbc-sbe-subscriber-delegate-prof)# duration 1000Router(config-sbc-sbe-subscriber-delegate-prof)# retry-count 5Router(config-sbc-sbe-subscriber-delegate-prof)# retry-interval 60Router(config-sbc-sbe-subscriber-delegate-prof)# refresh-buffer 200Router(config-sbc-sbe-subscriber-delegate-prof)# exitRouter(config-sbc-sbe)# subscriber sip:bob@isp.exampleRouter(config-sbc-sbe-subscriber-entry)# sip-contact sip:steve@10.1.1.2Router(config-sbc-sbe-subscriber-contact)# adjacency CallMgrBRouter(config-sbc-sbe-subscriber-contact)# exitRouter(config-sbc-sbe-subscriber-entry)# delegate-registration sip:registrar@1.1.1.1Router(config-sbc-sbe-subscriber-delegate)# adjacency CallMgrARouter(config-sbc-sbe-subscriber-delegate)# profile my-profileRouter(config-sbc-sbe-subscriber-delegate)# activateRouter(config-sbc-sbe-subscriber-delegate)# endRelated Commands
retry-limit (radius)
To set the number of times for resending an accounting request to the Radius server, use the retry-limit command in SBE accounting mode. To set the number to its default, use the no form of this command.
retry-limit range
no retry-limit range
Syntax Description
Command Default
5 retries.
Command Modes
Server accounting (config-sbc-sbe-acc)
Server authentication (config-sbc-sbe-auth)
Command History
Cisco IOS XE Release 2.4
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 and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
Examples
The following example shows how to set the retry-limit to 4 attempts.
Router# configureRouter(config)# sbc uut105-1Router/Admin(config-sbc)# sbeRouter/Admin(config-sbc-sbe)# radius accounting SBC1-account-1Router/Admin(config-sbc-sbe-acc)# retry-limit 4Related Commands
retry-interval
Sets the retry interval to connect to the RADIUS server.
concurrent-requests
Sets the maximum number of concurrent requests to the RADIUS server.
activate
Activates the RADIUS client.
retry-limit (routing table)
To set the maximum number of routing table lookup retry attempts, use the retry-limit command in SBE configuration mode. To set the number to its default, use the no form of this command.
retry-limit 0-200
Syntax Description
Command Default
3 retries.
Command Modes
SBE configuration (config-sbc-sbe)
Command History
Cisco IOS XE Release 2.4
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 and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
Examples
The following example shows how to set the retry-limit to 4 attempts.
Router# configureRouter(config)# sbc uut105-1Router/Admin(config-sbc)# sbeRouter/Admin(config-sbc-sbe)# retry-limit 4rtg-carrier-id-table
To enter the configuration mode of a routing table or to create a new routing table, whose events match the carrier ID of an SBE policy set, use the rtg-carrier-id-table command in SBE callpolicy mode.
The no form of the command destroys the routing table. However, a routing table may not be destroyed if it is in the context of the active policy set.
rtg-carrier-id-table table-name
no rtg-carrier-id-table table-name
Syntax Description
Command Default
No default behavior or values
Command Modes
SBE routing policy (config-sbc-sbe-rtgpolicy)
Command History
Cisco IOS XE Release 2.4
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 and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
Examples
The following example shows how to add the carrier ID table MyCarrierIDTable:
Router# configureRouter(config)# sbc mySbcRouter(config-sbc)# sbeRouter(config-sbc-sbe)# call-policy-set 1Router(config-sbc-sbe-rtgpolicy)# rtg-carrier-id-table MyCarrierIDTableRouter(config-sbc-sbe-rtgpolicy-rtgtable)#Related Commands
rtg-category-table
To enter the submode of configuration of a routing table whose entries match on the category within the context of an SBE policy set, use the rtg-category-table command in SBE routing call policy mode.
The no form of the command destroys the routing table. However, a routing table may not be destroyed if it is in the context of the active policy set.
rtg-category-table WORD
no rtg-category-table WORD
Syntax Description
Command Default
No default behavior or values
Command Modes
SBE routing policy (config-sbc-sbe-rtgpolicy)
Command History
Cisco IOS XE Release 2.4
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
Usage Guidelines
If necessary, a new routing table is created. The user is not allowed to enter the submode of routing table configuration in the context of the active policy set.
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.
Examples
The following example creates the routing policy table MyRtgTable:
Router# configureRouter(config)# sbc mySbcRouter(config-sbc)# sbeRouter(config-sbc-sbe)# call-policy-set 1Router(config-sbc-sbe-rtgpolicy)# rtg-category-table MyRtgTableRouter(config-sbc-sbe-rtgpolicy-rtgtable)# endRelated Commands
rtg-dst-address-table
To enters the configuration mode of a routing table whose entries match on the dialed number (after number analysis) within the context of an SBE policy set, use the rtg-dst-address-table command in the SBE routing policy mode. To remove the routing table, use the no form of this command.
rtg-dst-address-table table-id
no rtg-dst-adress-table table-id
Syntax Description
Command Default
No default behavior or values
Command Modes
SBE routing policy (config-sbc-sbe-rtgpolicy)
Command History
Cisco IOS XE Release 2.4
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
Usage Guidelines
If necessary, a new routing table is created. The user is not allowed to enter the submode of routing table configuration in the context of the active policy set.
A routing 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 and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
Examples
The following command creates the routing policy table MyRtgTable:
Router# configureRouter(config)# sbc mySbc sbeRouter(config-sbc-sbe)# call-policy-set 1Router(config-sbc-sbe-rtgpolicy)# rtg-dst-address-table MyRtgTableRouter(config-sbc-sbe-rtgpolicy-rtgtable)# exitRouter(config-sbc-sbe-rtgpolicy)# exitRelated Commands
rtg-dst-domain-table
To enter the configuration submode of a routing table with entries that match the destination domain name of an SBE policy set, use the rtg-dst-domain-table command in SBE callpolicy mode. If no table exists, the command creates a new routing table.
The no form of the command deletes the routing table.
rtg-dst-domain-table table-name
no rtg-dst-domain-table table-name
Syntax Description
Command Default
No default behavior or values
Command Modes
SBE routing policy (config-sbc-sbe-rtgpolicy)
Command History
Cisco IOS XE Release 2.4
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 and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
You cannot delete a routing table if it is in the active policy set. You cannot enter the submode of a routing table configuration in the active policy set.
Examples
The following command creates the routing policy table MyRtgTable.
Router# configureRouter(config)# sbc mySbcRouter(config-sbc)# sbeRouter(config-sbc-sbe)# call-policy-set 1Router(config-sbc-sbe-rtgpolicy)# rtg-dst-domain-table MyRtgTableRouter(config-sbc-sbe-rtgpolicy-rtgtable)#Related Commands
rtg-least-cost-table
To configure the least-cost routing table and enter the submode of configuration of a routing table, use the rtg-least-cost-table command in SBE routing policy mode.
The no form of the command destroys the routing table. However, a routing table may not be destroyed if it is in the context of the active policy set.
rtg-least-cost-table table_name
no rtg-least-cost-table table_name
Syntax Description
Command Default
No default behavior or values
Command Modes
SBE routing policy (config-sbc-sbe-rtgpolicy)
Command History
Cisco IOS XE Release 2.4
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
Usage Guidelines
If necessary, a new routing table is created. The user is not allowed to enter the submode of routing table configuration in the context of the active policy set.
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.
Examples
The following command creates the routing policy table MyRtgTable:
Router# configureRouter(config)# sbc mySbcRouter(config-sbc)# sbeRouter(config-sbc-sbe)# call-policy-set 1Router(config-sbc-sbe-rtgpolicy)# rtg-least-cost-table MyRtgTableRouter(config-sbc-sbe-rtgpolicy-rtgtable)# endRelated Commands
rtg-round-robin-table
To enter the configuration mode of a policy table, whose events have no match-value parameters or next-table actions, use the rtg-round-robin-table command SBE callpolicy mode. Use the no form of this command to delete the table.
rtg-round-robin-table table-name
no rtg-round-robin-table-name
Syntax Description
Command Default
No default behavior or values
Command Modes
SBE routing policy (config-sbc-sbe-rtgpolicy)
Command History
Cisco IOS XE Release 2.4
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
Usage Guidelines
The actions of this command are restricted to setting destination adjacency. A group of adjacencies is chosen for an event if an entry in a routing table matches that event and points to a round-robin adjacency table in the next table action.
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.
Examples
The following example show how to add the round robin routing table MyRoundRobinTable:
Router# configureRouter(config)# sbc mySbcRouter(config-sbc)# sbeRouter(config-sbc-sbe)# call-policy-set 1Router(config-sbc-sbe-rtgpolicy)# rtg-round-robin-table MyRoundRobinTableRouter(config-sbc-sbe-rtgpolicy-rtgtable)#Related Commands
rtg-src-account-table
To enter the configuration mode of an existing routing table or to create a new one, with entries that match the source account, use the rtg-src-account-table command SBE callpolicy mode.
Note
The no form of the command deletes the match value of the given entry in the routing table.
rtg-src-account-table table-id
no rtg-src-account-table table-id
Syntax Description
Command Default
No default behavior or values
Command Modes
SBE routing policy (config-sbc-sbe-rtgpolicy)
Command History
Cisco IOS XE Release 2.4
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 and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
Examples
The following command enters the configuration mode of an existing routing table MyRtgTable:
Router# configureRouter(config)# sbc mySbcRouter(config-sbc)# sbeRouter(config-sbc-sbe)# call-policy-set 1Router(config-sbc-sbe-rtgpolicy)# rtg-src-account-table MyRtgTableRouter(config-sbc-sbe-rtgpolicy-rtgtable)#Related Commands
rtg-src-address-table
To enter the configuration mode of a routing table whose entries match on the dialer's number within the context of an SBE policy set, use the rtg-src-address-table command in SBE routing policy mode. To remove the table entry, use the no form of this command.
rtg-src-address-table table-id
no rtg-src-address-table table-id
Syntax Description
Command Default
No default behavior or values
Command Modes
SBE routing policy (config-sbc-sbe-rtgpolicy)
Command History
Cisco IOS XE Release 2.4
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 and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
Examples
The following command creates the routing policy table MyRtgTable:
Router# configureRouter# sbc mySbcRouter(config-sbc)# sbeRouter(config-sbc-sbe)# call-policy-set 1Router(config-sbc-sbe-rtgpolicy)# rtg-src-address-table MyRtgTableRouter(config-sbc-sbe-rtgpolicy-rtgtable)# exitRouter(config-sbc-sbe-rtgpolicy)# exitRelated Commands
rtg-src-adjacency-table
To enter the configuration mode of an existing routing table or to create a new table whose entries match the source adjacency, use the rtg-src-adjacency-table command in SBE callpolicy mode. Use the no form of this command to delete the routing table.
rtg-src-adjacency-table table-id
no rtg-src-adjacency-table table-id
Syntax Description
Command Default
No default behavior or values
Command Modes
SBE routing policy (config-sbc-sbe-rtgpolicy)
Command History
Cisco IOS XE Release 2.4
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 and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
Examples
The following command creates a new table, MyRtgTable, whose entries match the source adjacency.
Router# configureRouter(config)# sbc mySbcRouter(config-sbc)# sbeRouter(config-sbc-sbe)# call-policy-set 1Router(config-sbc-sbe-rtgpolicy)# rtg-src-adjacency-table MyRtgTableRelated Commands
rtg-src-domain-table
To enter the submode of a routing table configuration, with entries that match the source domain name, use the rtg-src-domain table command in SBE callpolicy mode. If no table exists, the command creates a new routing table.
Note
The no form of the command destroys the routing table.
Note
rtg-src-domain-table table-name
no rtg-src-domain-table table-name
Syntax Description
table-name
Name of the number analysis table within an SBE policy set, with entries matching the source account.
Command Default
No default behavior or values
Command Modes
SBE routing policy (config-sbc-sbe-rtgpolicy)
Command History
Cisco IOS XE Release 2.4
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 and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
Examples
The following command creates the routing policy table MyRtgTable.
Router# configureRouter(config)# sbc mySbcRouter(config-sbc)# sbeRouter(config-sbc-sbe)# call-policy-set 1Router(config-sbc-sbe-rtgpolicy)# rtg-src-domain-table MyRtgTableRouter(config-sbc-sbe-rtgpolicy-rtgtable)#Related Commands
rtg-time-table
To configure time-based routing and enter the routing table submode, use the rtg-time-table command in SBE routing call policy mode.
The no form of the command destroys the routing table. However, a routing table may not be destroyed if it is in the context of the active policy set.
rtg-time-table table_name
no rtg-time-table table_name
Syntax Description
Command Default
No default behavior or values
Command Modes
SBE routing policy (config-sbc-sbe-rtgpolicy)
Command History
Cisco IOS XE Release 2.4
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
Usage Guidelines
If necessary, a new routing table is created. The user is not allowed to enter the submode of routing table configuration in the context of the active policy set.
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.
Examples
The following command creates the routing policy table MyRtgTable:
Router# configureRouter(config)# sbc mySbcRouter(config-sbc)# sbeRouter(config-sbc-sbe)# call-policy-set 1Router(config-sbc-sbe-rtgpolicy)# rtg-time-table MyRtgTableRouter(config-sbc-sbe-rtgpolicy-rtgtable)# endRelated Commands
sbc
To enter the submode of an SBC service (creating it if necessary), use the sbc command in the SBC configuration mode. To delete the service, use the no form of this command.
sbc sbc-name
no sbc sbc-name
Syntax Description
Defaults
No default behvior or values
Command Modes
SBC configuation mode (config-sbc)
Command History
Cisco IOS XE Release 2.4
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers for the unified model.
Examples
The following command creates SBC service mySbc.
Router# configureRouter(config)# sbc mySbcRouter(config-sbc)# sbeRouter(config-sbc)# exitRelated Commands
sbe
To configure the submode of the SBE entity within a SBC service, creating it if necessary, use the sbe command in Exec mode. To destroy the SBE entity, use the no form of this command.
sbe
no sbe
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Exec (#)
Command History
Cisco IOS XE Release 2.4
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
Examples
The following example shows how the sbe command is used to enter the submode of the SBE entity within a SBC service:
Router# configureRouter(config)# sbc mySbcRouter(config-sbc)# sbe(config-sbc-sbe)# exitsc-cold-boot-delay
To configure a delay timer that delays generation of a ServiceChange coldBoot request, use the sc-cold-boot-delay command in VDBE configuration mode.
The no form of the command turns off the cold boot delay timer on the next reboot.
sc-cold-boot-delay delay
no sc-cold-boot-delay delay
Syntax Description
Command Default
No default behavior or values
Command Modes
VDBE configuration mode (config-sbc-dbe-vdbe)
Command History
Cisco IOS XE Release 2.4
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers for distributed Session Border Controller (SBC).
Usage Guidelines
This command is supported in distributed SBC. This command configures a delay timer that delays generation of the Service Change Cold Boot after SBC has started with the activate command. The delay of the Service Change Cold Boot can only occur while the system is booting. This delay allows SBC to start up and be ready to respond to a large number of SIP pinhole requests that will be initiated by the ServiceChange ColdBoot.
To disable the delay Service Change Cold Boot timer, you must issue the no activate command followed by an activate command to attach to the MGC immediately. The no sc-cold-boot-delay command is used to make sure that the delayed SC mode doesn't occur on the next reboot.
Use the show sbc dbe controllers command to display the configured delay and the time remaining before the Service Change will be issued.
Examples
The following command describes a DBE configuration where a delay timer is configured to 120 seconds to delay generation of a ServiceChange coldBoot request:
Router# configure terminalRouter(config)# sbc global dbeRouter(config-sbc-dbe)# vdbe globalRouter(config-sbc-dbe-vdbe)# h248-version 3Router(config-sbc-dbe-vdbe)# h248-napt-package naptRouter(config-sbc-dbe-vdbe)# local-port 2970Router(config-sbc-dbe-vdbe)# control-address h248 ipv4 200.50.1.40Router(config-sbc-dbe-vdbe)# controller h248 2Router(config-sbc-dbe-vdbe-h248)# remote-address ipv4 200.50.1.254Router(config-sbc-dbe-vdbe-h248)# remote-port 2970Router(config-sbc-dbe-vdbe-h248)# exitRouter(config-sbc-dbe-vdbe)# attach-controllersRouter(config-sbc-dbe-vdbe)# sc-cold-boot-delay 120Router(config-sbc-dbe-vdbe)# exitRouter(config-sbc-dbe)# activateThe following example shows that the configured activation delay is 112 seconds, which is the time remaining before the Service Change is issued, and the controller status is detached.
Router# show sbc global dbe controllersSBC Service "global"vDBE in DBE location 1DBE Admin Status: Activation Delayed 112 secondsMedia gateway controller in use:H.248 controller address200.50.1.254:2970Status: DetachedSent Received FailedRetriedRequests 1 0 0 1Replies 0 0 0Segmentation:MGC PDU Size: N/AMG PDU Size: N/AMGC Seg timer: N/AMG Seg timer: N/ASegments Sent: N/ASegments Rcvd: N/AConfigured controllers:H.248 controller 2:Related Commands
activate
To initiate the DBE service of the SBC.
show sbc dbe controllers
Lists the MGCs and controller address configured on each DBE.
sdp-attribute-table
To configure an SDP attribute table that lists the attributes to add or remove, use the sdp-attribute-table command in SDP match table configuration mode. To deconfigure an SDP attribute table, use the no form of this command.
sdp-attribute-table table_name
no sdp-attribute-table table_name
Syntax Description
Defaults
No default behavior or values
Command Modes
SDP match table (config-sbc-sbe- sdpmatchtable) configuration mode
Command History
Cisco IOS XE Release 2.4
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 and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
Examples
The following command configures the SDP username to use on generated SDPs to "foo:"
Router# configureRouter(config)# sbc mySbcRouter(config-sbc)# sbeRouter(config-sbc-sbe)# sdp attribute-table fooRelated Commands
sdp-match-table
To create an SDP match table, use the sdp-match-table command in mode. To remove an SDP match table, use the no form of this command.
sdp-match-table table_name
no sdp-policy-table table_name
Syntax Description
Defaults
No default behavior or values
Command Modes
SBE configuration (config-sbc-sbe)
Command History
Cisco IOS XE Release 2.4
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
Usage Guidelines
One policy can only hold one sdp-match-table.
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.
Examples
The following command configures the SDP match table foo:
Router# configureRouter(config)# sbc mySbcRouter(config-sbc)# sbeRouter(config-sbc-sbe)# sdp-match-table fooRelated Commands
action (sdp)
Configures an SDP policy table action.
match-string
Configure an SDP attribute matching string.
sdp-policy-table
Configure an SDP policy table.
sdp origin-user-name
To configure the originating user name that is filled in generated SDPs, use the sdp origin-user-name command in the SBE configuration mode. To reset this user name such that received user name from an SDP is the user name used on the generated SDP, use the no form of this command.
sdp origin-user-name user-name
no sdp origin-user-name user-name
Syntax Description
Defaults
No default behavior or values
Command Modes
SBE configuration (config-sbc-sbe)
Command History
Cisco IOS XE Release 2.4
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 and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
Examples
The following command configures the SDP username to use on generated SDPs to foo:
Router# configureRouter(config)# sbc mySbcRouter(config-sbc)# sbeRouter(config-sbc-sbe)# sdp origin-user-name foosdp-policy-table
To configure an SDP policy table, use the sdp-policy-table command in the SBE configuration mode. To deconfigure an SDP policy table, use the no form of this command.
sdp-policy-table table_name
no sdp-policy-table table_name
Syntax Description
Defaults
No default behavior or values
Command Modes
SBE configuration (config-sbc-sbe)
Command History
Cisco IOS XE Release 2.4
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 and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
Examples
The following command configures the SDP policy table foo:
Router# configureRouter(config)# sbc mySbcRouter(config-sbc)# sbeRouter(config-sbc-sbe)# sdp-policy-table fooRelated Commands
sdp-match-table
Creates an SDP match table.
action (sdp)
Configures an SDP policy table action.
match-string
Configure an SDP attribute matching string.
secure-media
To configure the Session Border Controller (SBC) to enable a DTLS or SRTP media passthrough, use the secure-media command in the SBE configuration mode. To disable the media passthrough, use the no form of this command.
secure-media
no secure-media
Syntax Description
This command has no arguments or keywords.
Defaults
The media passthrough is disabled.
Command Modes
SBE configuration (config-sbc-sbe)
Command History
Cisco IOS XE Release 2.4
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
Examples
The following example configures the SBC to treat every media flow as an encrypted media flow. This allows media packets, such as DTLS and SRTP packets, to pass through the SBC.
Router# configure terminalRouter(config)# sbc globalRouter(config-sbc)# sbeRouter(config-sbc-sbe)# secure-mediaRelated Commands
sbc
Creates the SBC service on Cisco Unified Border Element (SP Edition).
sbe
Enters the mode of the signaling border element (SBE) function of the SBC.
security
To implement transport-level security on a Session Initiation Protocol (SIP) adjacency, use the security command in SBE adjacency SIP configuration mode. To indicate that the adjacency cannot be secured, use the no form of this command.
security [untrusted | trusted-encrypted | untrusted-encrypted | trusted-unencrypted]
no security [untrusted | trusted-encrypted | untrusted-encrypted | trusted-unencrypted]
Syntax Description
Defaults
untrusted is the default.
Command Modes
Adjacency SIP configuration (config-sbc-sbe-adj-sip)
Command History
Cisco IOS XE Release 2.4
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
Usage Guidelines
Any number of accounting servers can be specified. Call Detail Reports are sent to the accounting server with the highest priority upon call termination.
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.
Examples
The following command configures accounting servers castor and pollux on mySbc for RADIUS client instance radius1:
Router# configureRouter(config)# sbc mySbcRouter(config)# sbc mySbcRouter(config-sbc)# sbeRouter(config-sbc-sbe)# sip adjacency testRouter(config-sbc-sbe-adj-sip)# security trusted-encryptedRelated Commands
server
To enter a submode for configuring ordered lists of RADIUS accounting and RADIUS authentication servers, use the server command in server accounting and server authentication configuration modes. Use the no form of the command to leave the submode.
server server-name
no server server-name
Syntax Description
Defaults
No default behavior or values
Command Modes
Server accounting (config-sbc-sbe-acc)
Server authentication (config-sbc-sbe-auth)
Command History
Cisco IOS XE Release 2.4
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
Usage Guidelines
Any number of accounting servers and authentication servers can be specified. Call Detail Reports are sent to the accounting server or authentication server with the highest priority upon call termination.
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.
Examples
The following command configures accounting servers castor and pollux on mySbc for RADIUS client instance radius1:
Router# configureRouter(config)# sbc mySbcRouter(config)# sbc mySbcRouter(config-sbc)# sbeRouter(config-sbc-sbe)# radius accounting radius1Router(config-sbc-sbe-acc)# server castorRouter(config-sbc-sbe-acc-ser)# address ipv4 200.200.200.12Router(config-sbc-sbe-acc-ser)# exitRouter(config-sbc-sbe-acc)# server polluxRouter(config-sbc-sbe-acc-ser)# address ipv4 200.200.200.15Router(config-sbc-sbe-acc-ser)# exitserver-retry disable
To disable the SBC from automatically retrying a failed RADIUS server, use the server-retry disable command in the server authentication mode or the server accounting mode. Use the no form of this command to enable the SBC to automatically retry a failed RADIUS server.
server-retry disable
Syntax Description
This command has no arguments or keywords.
Command Default
No default behavior or values
Command Modes
Server accounting (config-sbc-sbe-acc)
Server authentication (config-sbc-sbe-auth)
Command History
Cisco IOS XE Release 2.4
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 and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
If you have disabled the SBC from automatically retrying a failed RADIUS server with the server-retry disable command, you must use the service sbc sbe radius accounting command to reactivate the connection between the SBC and a RADIUS server after connectivity is lost or to restart billing after connectivity is restored.
Examples
The following example shows how to stop the SBC from automatically retrying a failed RADIUS server:
Router# configureRouter(configure)# sbc mysbcRouter(config-sbc)# sbeRouter(config-sbc-sbe)# radius authenticationRouter(config-sbc-sbe-auth)# server-retry disableRelated Commands
service sbc sbe radius accounting
Reactivates connection between the SBC and a RADIUS server after connectivity is lost or to restart billing after connectivity is restored.
service sbc sbe radius accounting
To reactivate connection between the SBC and a RADIUS server after connectivity is lost or to restart remote billing after connectivity is restored, use the service sbc sbe radius accounting command in the Privileged EXEC mode.
service sbc name sbe radius accounting radius client name {resend | server word reactivate}
Syntax Description
Command Default
No default behavior or values
Command Modes
Privileged EXEC (#)
Command History
Cisco IOS XE Release 2.4
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
Examples
The following example shows how to resend cached messages:
Router# service sbc test sbe radius accounting acc resend
The following example shows how to reactivate connection to a RADIUS server:
Router# service sbc test sbe radius accounting acc server svr reactivate
