- 100rel inbound through critical-alert-size
- deact-mode (billing) through group
- h225 address through overload-time-threshold
- packetcable-em transport radius through show monitor event-trace sbc ha
- show platform hardware qfp active feature sbc sfx through show sbc sbe media-gateways
- show sbc sbe policy-failure-stats through xml (billing)
- packetcable-em transport radius
- parameter-editor
- parameter-profile
- parameter (editor)
- parameter (session border controller)
- pass-body
- payload-type asymmetric
- peer (session border controller)
- ping-bad-rsp-codes
- ping-enable
- ping-fail-count
- ping-interval
- ping-lifetime
- ping-suppression
- policy (session border controller)
- port (session border controller)
- port (SBE H.248)
- port-rang e
- precedence (session border controller)
- preferred-transport
- prefix (session border controller)
- priority (session border controller)
- privacy restrict outbound
- privacy (session border controller)
- profile (session border controller)
- qos fax
- qos sig
- qos video
- qos voice
- range (session border controller)
- ras retry (session border controller)
- ras rrq
- ras timeout (session border controller)
- realm
- realm (diameter)
- realm (H.248 BAC)
- realm (Rf billing)
- reason
- redirect-limit
- redirect-mode
- redundant peer
- refresh-buffer
- reg-min-expiry
- register-rate
- registration aggregate
- registration contact username
- registration monitor
- registration outgoing timer
- registration required
- registration rewrite-register
- registration target address
- registration target port
- registration unencrypted-convert
- reject-threshold
- remote-address ipv4
- remote-port (session border controller)
- req-timeout
- request-line
- request-line request-uri rewrite
- resource-priority-set
- resource-priority
- response-code-mapping
- retry-count
- retry-interval
- retry-interval (registration)
- retry-limit (radius)
- retry-limit (routing table)
- rf
- rtcp-mux
- rt cp-regenerate
- rtg-carrier-id-table
- rtg-category-table
- rtg-dst-address-table
- rtg-dst-domain-table
- rtg-dst-trunk-group-id-table
- rtg-least-cost-table
- rtg-round-robin-table
- rtg-src-account-table
- rtg-src-address-table
- rtg-src-adjacency-table
- rtg-src-domain-table
- rtg-src-trunk-group-id-table
- rtg-time-table
- sbc
- sbc dbe
- sbc dump-alarms
- sbc periodic-dump-alarms
- sbc redundancy-group tcp (session border controller)
- sc-cold-boot-delay
- sck-pool-size
- script-set lua
- script
- sdp repeat answer
- secure-media
- security (session border controller)
- server-retry disable
- server ipv4
- server (session border controller)
- service sbc sbe radius accounting
- session-refresh renegotiation
- sh ow debu ggi ng
- show mo ni tor event-trace sbc ha
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
Specifies the packetcable billing instance. The range is 0 to 7. |
|
Command Default
Command Modes
SBE billing configuration (config-sbc-sbe-billing)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example configures packet-cable billing instances of four with a RADIUS client name of ‘test’:
Related Commands
|
|
|
|---|---|
Activates the billing functionality after configuration is committed. |
|
Configures the time of day (local time) to run the Long Duration Check (LDR). |
|
parameter-editor
To add a parameter editor associated with a header, use the parameter-editor command in the SIP Header Editor element configuration mode. To remove a parameter editor, use the no form of this command.
Syntax Description
Command Default
Command Modes
SIP Header Editor element configuration (config-sbc-sbe-sip-hdr-ele)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of the modes required to run the command.
The parameter editor should be initially configured using the sip parameter-editor command in the SBE configuration mode.
Examples
The following example shows how to add a parameter editor to the header element of a header editor:
Related Commands
|
|
|
|---|---|
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
Command Default
Command Modes
SIP header configuration element (config-sbc-sbe-sip-hdr-ele)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to add a parameter profile to the header element for a header profile:
Related Commands
|
|
|
|---|---|
parameter (editor)
To add a parameter to an editor, use the parameter command in the SIP Parameter Editor configuration mode. To remove a parameter from an editor, use the no form of this command.
Syntax Description
Name of the parameter to be added to the parameter editor. Valid names are 1 to 32 characters in length (inclusive) and are case-sensitive. |
Command Default
Command Modes
SIP Parameter Editor configuration (config-sbc-sbe-mep-prm)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of the modes required to run the command.
Use the parameter command to enter the SIP Parameter Editor Element configuration mode.
Examples
The following example shows how the parameter command adds a parameter named user to the parameter editor:
Related Commands
|
|
|
|---|---|
parameter (session border controller)
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.
no parameter { parameter name }
Syntax Description
Name of the parameter added to the parameter profile. Valid names are 1 to 32 characters in length (inclusive) and are case-sensitive. |
Command Default
Command Modes
SIP parameter-profile configuration
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
If a configuration is loaded on top of an active configuration, warnings are generated to notify that the configuration cannot be modified. If you must modify the entire configuration by loading a new one, please remove the existing configuration first.
Examples
The following example shows how the parameter command adds a parameter named user to the parameter profile Myprofile:
Related Commands
|
|
|
|---|---|
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.
Syntax Description
Command Default
By default, the message bodies are removed out of non-vital SIP messages.
Command Modes
SIP method (config-sbc-sbe-sip-mth)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how the pass-body command permits SIP message bodies to pass through for non-vital SIP methods accepted by method profile test1:
payload-type asymmetric
To configure an SBC to support Asymmetric payload types, use the payload-type asymmetric command. Use the no form of this command to disallow an SBC from supporting Asymmetric payload types.
payload-type asymmetric {allowed | disallowed}
no payload-type asymmetric {allowed | disallowed}
Syntax Description
Command Default
Command Modes
Configure CAC Policy CAC Table (config-sbc-sbe-cacpolicy-cactable-entry)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section that follows shows the hierarchy of modes required to run the command.
Examples
The following example shows how to configure the SBC to specify support for asymmetric payload types on the mySBC SBC:
Following is a command output for the command show sbc sbe cac-policy-set command:
(config)#show sbc RAND sbe cac-policy-set 1 TAB1
peer (session border controller)
To create an IMS peer and configure the name and IPv4 address of the peer, use the peer command in diameter configuration mode. To remove the peer, use the no form of this command.
peer peer-name [ vpn vpn-name ] { ipv4 ipv4-address | dns-name } [ port port-number ]
no peer peer-name [ vpn vpn-name ] { ipv4 ipv4-address | dns-name } [ port port-number ]
Syntax Description
Command Default
If port is not specified, the default port number of the peer is 3868.
Command Modes
Diameter configuration (config-sbc-sbe-diameter)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Note
When you configure the peer with a VPN, only the IPv4 address can be configured with it. You cannot use the DNS name. When you configure the peer with a VPN, only the IPv4 address can be configured with it. You cannot use the DNS name.
Examples
The following example shows how to create an IMS peer:
Related Commands
ping-bad-rsp-codes
To configure the congestion response codes on SIP Adjacency by sending SIP OPTIONS pings to it , use the ping-bad-rsp-codes command in adjacency ping option mode. Use the no form of this command to disable congestion response codes on SIP Adjacency.
Syntax Description
The response code range that SBC considers as ping failure indication. |
Command Default
Command Modes
Ping option (config-sbc-sbe-adj-sip-ping)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to configure the congestion response codes on SIP adjacency by sending SIP OPTIONS pings:
ping-enable
To configure the adjacency to poll its remote peer by sending SIP OPTIONS pings to it and to enter the ping option mode, 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.
Syntax Description
Command Default
Command Modes
Adjacency SIP configuration (config-sbc-sbe-adj-sip)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to configure the adjacency to poll its remote peer by sending SIP OPTIONS pings:
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.
Syntax Description
Command Default
Command Modes
Ping option (config-sbc-sbe-adj-sip-ping)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to configure the number of consecutive pings that must fail before the adjacencies peer is deemed to be unavailable:
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.
Syntax Description
The number of seconds. The possible values are 1 to 2147483. |
Command Default
Command Modes
Ping option (config-sbc-sbe-adj-sip-ping)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to configure the interval between SIP OPTIONS pings that are sent to the remote peer to 100 seconds:
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.
Syntax Description
Command Default
Command Modes
Ping option (config-sbc-sbe-adj-sip-ping)
Command History
|
|
|
|---|---|
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. The Examples section shows the hierarchy of modes 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:
ping-suppression
To configure SBC to send ping when required on sip Adjacency, use the ping-suppression command in ping option mode. Use the no form of this command to disable sending pings on SIP adjacency.
Syntax Description
Command Default
Command Modes
Ping option (config-sbc-sbe-adj-sip-ping)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to configure SBC to send ping when required on sip Adjacency by sending SIP OPTIONS pings:
policy (session border controller)
To configure the packetization period policy, use the policy command in the codec list configuration mode. To deconfigure the packetization period policy, use the no form of this command.
policy {minimum | transrating}
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to configure a minimum packetization period policy using the policy command in the codec list configuration mode:
Related Commands
|
|
|
|---|---|
port (session border controller)
To configure a port for a redundant peer, use the port command in adjacency Session Initiation Protocol (SIP) peer configuration mode. To deconfigure a port, use the no form of this command.
Syntax Description
The p ort of a redundant peer . The range is from 0 to 65535. |
Command Default
Command Modes
Adjacency SIP peer configuration (config-sbc-sbe-adj-sip-peer)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section that follows shows the hierarchy of the modes and modes required to run the command.
Examples
The following example shows how the port command is used to configure a port for a redundant peer on a SIP adjacency:
Related Commands
|
|
|
|---|---|
Configures either an IP address or a host name to act as the redundant peer. |
|
Configures either an IPv4 or IPv6 network in a redundant peer. |
|
port (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.
Syntax Description
Specifies the listening port number. The range is from 1 to 9999. |
Command Default
Command Modes
H.248 control address (config-sbc-sbe-ctrl-h248)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to configure an SBE to use port 2000:
Related Commands
|
|
|
|---|---|
Configures an SBE to use a given IPv4 H.248 control address. |
|
Configures an SBE to use a certain transport for H.248 communications. |
port-range
To create a port range associated with corresponding media address pool entries, use the port-range command in media address configuration mode. To delete a port range, use the no form of this command.
port-range start-rtp-port end-rtp-port
no port-range start-rtp-port end-rtp-port
Syntax Description
Command Default
Command Modes
Media address configuration (conf-media-addr-range)
Command History
|
|
|
|---|---|
Usage Guidelines
Use the port-range command in the media address configuration mode to specify up to 10 port ranges for a single media address.
Examples
The following example for a unified SBC shows how to create two port ranges for a media address:
Related Commands
precedence (session border controller)
To configure the precedence of the routing entry, use the precedence command in RTG routing table entry configuration mode. To deconfigure the precedence of the routing entry, use the no form of this command.
Syntax Description
Range: [0-0xFFFFFFFF]. A value of 0 means the entry will never be matched. |
Command Default
Command Modes
RTG routing table entry configuration (config-sbc-sbe-rtgpolicy-rtgtable-entry)
Command History
|
|
|
|---|---|
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. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to configure an SBE to use port 2000:
Related 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}
Syntax Description
Command Default
Command Modes
Adjacency SIP configuration (config-sbc-sbe-adj-sip)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following command sets the preferred transport of the SipAdj1 adjacency to TCP:
prefix (session border controller)
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.
Syntax Description
Command Default
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
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to configure an entry to match dialed numbers starting with 9:
priority (session border controller)
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.
Syntax Description
Command Default
Command Modes
Server accounting (config-sbc-sbe-acc-ser)
Server authentication (config-sbc-sbe-auth)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
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:
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.
Syntax Description
Command Default
Command Modes
Adjacency H.323 configuration (config-sbc-sbe-adj-h323)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how the privacy restrict outbound command is used to configure an H.323 adjacency to apply privacy restriction on outbound messages if a user requests it:
Related Commands
|
|
|
|---|---|
Configures an H.323 adjacency to allow private information on messages sent out by the H.323 adjacency. |
privacy (session border controller)
To configure the trust level for determining whether the privacy service should be applied, use the privacy command in adjacency SIP configuration mode. To disable the trust level, use the no form of this command.
privacy [ inherit-profile | trusted | untrusted ]
Syntax Description
Command Default
Command Modes
Adjacency SIP configuration (config-sbc-sbe-adj-sip)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to configure the trust level of the SIP adjacency to trusted:
Related Commands
|
|
|
|---|---|
profile (session border controller)
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.
Syntax Description
This is the name of the delegate client registration profile that can be applied to a delegate subscriber. The profile name is a string field of 24 characters maximum length. |
Command Default
Command Modes
subscriber-delegate configuration mode (config-sbc-sbe-subscriber-delegate)
Command History
|
|
|
|---|---|
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:
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:
Related 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.
Syntax Description
Command Default
Command Modes
SBE configuration (config-sbc-sbe)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to enter the mode for configuring a fax QoS profile named residential:
qos 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.
Syntax Description
Command Default
Command Modes
SBE configuration (config-sbc-sbe)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how qos sig command enters the mode for configuring a signaling QoS profile residential:
qos 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
Syntax Description
Command Default
Command Modes
SBE configuration (config-sbc-sbe)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to enter the mode for configuring a video QoS profile named residential:
qos 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.
Syntax Description
Command Default
Command Modes
SBE configuration (config-sbc-sbe)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to enter the mode for configuring a voice QoS profile named residential:
range (session border controller)
To map a range of response codes to a response code, use the range command in the session initiation protocol (SIP) method profile map configuration mode or the SIP method editor map configuration mode. To remove the mapping , use the no form of this command.
range statuscoderange value statuscodevalue
Syntax Description
Command Default
Command Modes
SIP method profile map configuration (config-sbc-sbe-sip-mth-ele-map)
SIP method editor map configuration (config-sbc-sbe-mep-mth-ele-map)
Command History
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of the modes required to run the command.
Examples
The following example shows how the method command adds a method, test, to the Myprofile method profile:
Related Commands
|
|
|
|---|---|
Configures SIP header or method blacklist profiles on a SIP message. |
|
Permits SIP message bodies to pass through for nonvital SIP methods accepted by a method profile. |
The following example shows how to specify the range for mapping the response codes received for a method:
ras retry (session border controller)
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
Command Modes
Adjacency H.323 configuration (config-sbc-sbe-adj-h323)
H.323 configuration (config-sbc-sbe-h323)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how the ras retry command configures an H.323 RAS retry count in Adjacency H.323 configuration mode:
The following example shows how the ras retry command configures an H.323 RAS retry count in H.323 configuration mode:
Related Commands
|
|
|
|---|---|
ras 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
Command Modes
Adjacency H.323 configuration (config-sbc-sbe-adj-h323)
H.323 configuration (config-sbc-sbe-h323)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how the ras rrq command configures H.323 RAS RRQ in adjacency H.323 configuration mode:
The following example shows how the ras rrq command configures RAS RRQ in H.323 configuration mode:
Related Commands
|
|
|
|---|---|
Configures an H.323 RAS retry count for an RAS transaction type. |
|
ras timeout (session border controller)
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
Specifies timeout value (seconds). Valid values are from 1000 to 45000 milliseconds. |
Command Default
Command Modes
Adjacency H.323 configuration (config-sbc-sbe-adj-h323)
H.323 configuration (config-sbc-sbe-h323)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how the ras timeout command configures an H.323 RAS timeout interval in adjacency H.323 configuration mode.
The following example shows how the ras timeout command configures an H.323 RAS timeout interval in H.323 configuration mode.
Related Commands
|
|
|
|---|---|
realm
To configure an adjacency with the realm that it belongs to as part of configuring an IP Realm under an adjacency, use the realm command in adjacency SIP configuration mode. To remove the IP realm from the adjacency, use the no realm command.
no realm {IP realm identifier}
Syntax Description
The IP Realm Identifier is used to indicate to which packet network the media addresses belong. The IP Realm identifier is a string, which may be in a domain name format, for example, “mynet.net” or any other string format. The format of the realm string is up to the user with certain restrictions. Realms strings are case insensitive and are made up of the characters described in the table in the “IP Realm Support” chapter of the Cisco Unified Border Element (SP Edition) Configuration Guide: Unified Model . |
Command Default
Command Modes
adjacency SIP configuration (config-sbc-sbe-adj-sip)
Command History
|
|
|
|---|---|
This command was introduced on the unified model on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
In the SBC unified model, use the realm command to tag the adjacencies with the realm that they belong to. This will enable subsequent calls to use media addresses from that realm.
Examples
The following example shows how to tag the SIP adjacency Cisco-gw with the realm cisco.com:
The following example shows the running configuration after the SIP adjacency Cisco-gw is tagged with the realm cisco.com:
Related Commands
realm (diameter)
To configure a peer and assign the peer to a realm, use the realm command in diameter configuration mode. To remove the peer from the realm, use the no form of this command.
realm realm-name [ app rx ] peer peer-name [ priority priority ]
no realm realm-name [ app rx ] peer peer-name [ priority priority ]
Syntax Description
Command Default
If priority is not specified, the default priority of the peer is 1.
Command Modes
Diameter configuration (config-sbc-sbe-diameter)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to configure a peer and assign the peer to a realm:
Related Commands
realm (H.248 BAC)
To configure an IP realm of the Border Access Controller (BAC) under an adjacency, use the realm command in the H248 BAC adjacency configuration mode. To unconfigure the IP realm from the adjacency, use the no form of this command.
Syntax Description
Number of the IP realm that belongs to the BAC. The range is from 1 to 100. |
Command Default
Command Modes
H248 BAC adjacency configuration (config-h248-bac-adj)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
A realm group can contain multiple media addresses. When you configure a realm group under an adjacency, the IP address and port for the media stream of this adjacency is allocated from the media addresses in this realm group.
Examples
The following example shows how the realm command is used to configure an adjacency:
Related Commands
|
|
|
|---|---|
Adds an IPv4 address to the set of addresses that the BAC can use as local media address. |
realm (Rf billing)
To configure the realm information for Rf billing support on the Session Border Element of the Session Border Controller (SBC), use the realm command in the SBC SBE billing Rf configuration mode. To unconfigure the realm information for Rf billing support on the SBE of the SBC, use the no form of this command.
realm realm-name [usePCFAHeader | cdf cdf-name {FQDN FQDN-name | ipv4 ipv4-addr | vpn vpn-name} [port port-num] [priority priority]]
no realm realm-name [usePCFAHeader | cdf cdf-name {FQDN FQDN-name | ipv4 ipv4-addr | vpn vpn-name} [port port-num] [priority priority]]
Syntax Description
Configures the Fully Qualified Domain Name (FQDN) of the CDF. |
|
Port number of the CDF socket. Range: 1 to 65535. Default: 3868. |
|
Command Default
Command Modes
SBC SBE billing Rf configuration (config-sbc-sbe-billing-rf)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Examples
The following example shows how to configure the usePCFAHeader for Rf billing support on the SBE of the SBC:
reason
To enable the entry of a user into a mode for configuring a limit to a specific event type on the source (a port, IP address, VPN, and global address space), use the reason command in SBE blacklist mode. The no form of this command returns the event to its previous values.
Syntax Description
Command Default
Command Modes
SBE blacklist (config-sbc-sbe-blacklist)
Command History
Usage Guidelines
The event field can only take the strings described in the Syntax Description.
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows the use of the reason command in context:
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. T he no form of this command returns the adjacency to the default behavior.
Syntax Description
Specifies the maximum number of SIP 3xx retry attempts. The range is 0 to 200. |
Command Default
Command Modes
SBE configuration (config-sbc-sbe)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to configure the maximum number of SIP 3xx retries as 4:
redirect-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
On 300, 301, 302, and 305 invite responses, the SBC resends the invite to the first listed contact address, or else passes the 3xx responses back. |
Command Default
Command Modes
Adjacency SIP configuration (config-sbc-sbe-adj-sip)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to resend an invite to the first listed contact address or else pass the 3xx responses back to the sender:
Related Commands
|
|
|
|---|---|
Configures the maximum number of redirections SBC performs on a call. |
redundant peer
To configure an alternative signaling peer for an adjacency, use the redundant peer command in the adjacency SIP configuration mode. To deconfigure an alternative signaling peer, use the no form of this command.
Syntax Description
Command Default
Command Modes
Adjacency SIP configuration (config-sbc-sbe-adj-sip)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section that follows shows the hierarchy of the modes and modes required to run the command.
Examples
The following example shows how the redundant peer command is used to configure an alternative signaling peer for an adjacency:
Related Commands
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
This is the refresh expiration time in seconds. The range is 1 to 2,147,483 seconds. The default is 30 seconds. |
Command Default
Command Modes
Subscriber delegate profile configuration mode (config-sbc-sbe-subscriber-delegate-prof)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
This 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:
Related Commands
reg-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.
Syntax Description
The minimum expiry period in seconds. The range is 1 to 2000000. |
Command Default
Command Modes
Adjacency SIP configuration (config-sbc-sbe-adj-sip)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
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. The Examples section shows the hierarchy of modes 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:
register-rate
To configure the register rate for a Session Border Controller (SBC) H.248 access adjacency, use the register-rate command in the H248 BAC adjacency configuration mode. To set the default value for the register rate, use the no form of this command.
Syntax Description
Register rate for an SBC H.248 access adjacency, in seconds. Range: 30 to 300. Default: 100. |
Command Default
Command Modes
H248 BAC adjacency configuration (config-h248-bac-adj)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Examples
The following example shows how to configure the register rate for an SBC H.248 access adjacency:
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.
Syntax Description
Command Default
Command Modes
adjacency sip configuration (config-sbc-sbe-adj-sip)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
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.
The following example displays detailed output for adjacency Cary-IP-PBX, including the “Register Aggregate:” field that shows Aggregate Registration is “Enabled.”
The following is a configuration example showing that Aggregate Registration and SoftSwitch Shielding are configured:
Related Commands
registration contact username
To configure a contact username in a SIP REGISTER request to either pass through unchanged or be allowed to be modified, use the registration contact username command in the Adjacency SIP configuration mode. To reset to the default, use the no form of this command.
registration contact username [ passthrough | rewrite [ numeric | userid-and-numeric ]]
no registration contact username [ passthrough | rewrite [ numeric | userid-and-numeric ]]
Syntax Description
Command Default
By default, the contact username in a SIP REGISTER request can be changed or rewritten.
Command Modes
Adjacency SIP configuration (config-sbc-sbe-adj-sip)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
|
This command was modified. The numeric and userid-and-numeric keywords were added. |
Usage Guidelines
The registration contact-username command must be configured on the adjacency facing the registrar.
The registration contact username command with the passthrough option allows you to specify that the contact username in the SIP REGISTER request should be passed through unchanged when rewriting contacts. The passthrough option disambiguates subscribers who register from different devices with the same private username by using a unique local port number when multiple contact URIs are registered for the same public ID.
The range of valid signaling ports are configured with the signaling-port command on a registrar-facing adjacency. If signaling-port is not configured on the adjacency, the SBC is not able to disambiguate subscribers who register from different devices with the same username.
NoteIf a contact username is longer than 32 characters, the username is not passed, and the contact username is rewritten as a hashed value. If a contact username is longer than 32 characters, the username is not passed, and the contact username is rewritten as a hashed value.
Examples
The following example shows how to pass a single contact username unchanged:
The following is an example flow of multiple registrations for the same subscriber. The example shows how a sequence of REGISTER requests registering multiple contacts behaves. This example assumes that all the headers, apart from the contact headers, are omitted from the requests, and that the registrar-facing adjacency has a signaling port range of 5060 to 5063 (this means that four local ports are available).
1.
A REGISTER is received registering two contact addresses for the number 5551234:
2. The SBC forwards this REGISTER to the registrar after rewritting the contact address and port:
3. Another REGISTER is received for the number 5551234, registering another endpoint with a duplicate username:
4. The SBC forwards this to the registrar, passing the username through unchanged:
5. A third endpoint is registered for the same number. This endpoint provides a very long contact name in the Contact field:
6. The SBC forwards this request to the registrar and rewrites the username because it is over the maximum passthrough length (32):
The following example shows how to rewrite a contact username in a SIP REGISTER request as an originating user ID and a hashed numeric value:
The following examples show the SIP headers when the userid-and-numeric keyword is used:
The following example shows how to rewrite a contact username in a SIP REGISTER request as an originating hashed numeric value:
Router(config-sbc-sbe-adj-sip)# registration contact username rewrite numeric
The following examples show the SIP headers when the numeric keyword is used:
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.
Syntax Description
Command Default
Command Modes
adjacency sip configuration (config-sbc-sbe-adj-sip)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
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:
The following example displays detailed output for adjacency Cary-IP-PBX, including the “Registration Monitor:” field that shows Registration Monitoring is “Enabled:”
Related 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
Command Modes
adjacency sip configuration (config-sbc-sbe-adj-sip)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
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:”
The following is a configuration example showing that SoftSwitch Shielding is configured for adjacency sippb:
Related Commands
|
|
|
|---|---|
Enables the Registrar server to monitor subscriber event changes due to registration changes. |
|
Configures Provisioned Delegate Registration for a specific delegate client. |
registration required
To specify that registration is required for a call to proceed, use registration required command in the SBC SBE Adjacency SIP mode. Use the no form of this command to specify that registration is not required for the call to proceed.
Syntax Description
Command Default
Command Modes
SBC SBE Adjacency SIP (config-sbc-sbe-adj-sip)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode.
Examples
The following example specifies that registration is required for a call to proceed on the SIP adjacency CORE:
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.
no registration rewrite-register
Syntax Description
Command Default
Command Modes
Adjacency SIP configuration (config-sbc-sbe-adj-sip)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how the registration rewrite-register command configures the SIP register request rewriting on SIP adjacency SipToIsp42.
registration 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
Command Default
Command Modes
Adjacency SIP configuration (config-sbc-sbe-adj-sip)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how the registration target address command sets the target address for SIP adjacency SipToIsp42 as example.com:
registration 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
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. |
Command Default
Command Modes
Adjacency SIP configuration (config-sbc-sbe-adj-sip)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how the registration target port command sets the port number for SIP adjacency SipToIsp42 as 5070:
registration unencrypted-convert
To enable the conversion of SIPS URIs to SIP URIs on a trusted-unencrypted adjacency, use the registration unencrypted-convert command in adjacency SIP configuration mode. To remove this configuration, use the no form of this command.
registration unencrypted-convert
no registration unencrypted-convert
Syntax Description
Command Default
Command Modes
Adjacency SIP configuration (config-sbc-sbe-adj-sip)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of the modes required to run the command.
Examples
The following example shows how the registration unencrypted-convert command is used to enable the conversion of SIPS URIs to SIP URIs on the my_adjacency adjacency:
Related Commands
reject-threshold
To configure the memory threshold and reject rate for new calls, use the reject-threshold command. Use the no form of this command to restore the default values.
reject-threshold [ level ] memory [ percentage ] [ reject rate ]
[no] reject-threshold [ level ] memory [ percentage ]
Syntax Description
Command Modes
Configure SBC SBE (config-sbc-sbe)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section that follows shows the hierarchy of the modes required to run the command.
Follow these rules when configuring the threshold using this command:
Examples
The following example shows how to configure the minor memory congestion level set when 30 percentage of total memory is available. The reject rate at this level is set to 0:
The following example shows how to restore the default major memory threshold and drop rate:
Following is an example of the show command output for reject threshold:
remote-address ipv4
To configure a remote IPv4 H.248 signaling address for the Media Gateway Control Function (MGCF) and the Access Gateway Control Function (AGCF), use the remote-address ipv4 command in the H248 BAC adjacency configuration mode. To unconfigure the MGC and the AGCF from using a remote IPv4 H.248 signaling address, use the no form of this command.
remote-address ipv4 ipv4-address port port-number
no remote-address ipv4 ipv4-address port port-number
Syntax Description
Configures an IPv4 H.248 signaling remote address for the MGCF and AGCF. |
|
Number for the adjacency address port. The range is from 1 to 65535. |
Command Default
Command Modes
H.248 BAC adjacency configuration (config-h248-bac-adj)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
This command can be configured only in the core adjacency submode and not in the access adjacency submode.
Examples
The following example shows how the remote-address ipv4 command is used to configure a remote IPv4 H.248 signaling address for the MGCF and AGCF:
Related Commands
|
|
|
|---|---|
Configures a local IPv4 H.248 signaling address for the BAC. |
remote-port (session border controller)
To define the port to connect to on the SBE for an H.248 controller, use the remote-port command in VDBE h248 mode.
Syntax Description
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. |
Command Default
Command Modes
VDBE h248 (config-sbc-dbe-h248)
Command History
|
|
|
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. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example configures the port to 2944 on the H.248 controller with index 1:
Related Commands
|
|
|
|---|---|
Configures a virtual data border element (VDBE) and enters the VDBE configuration mode. |
|
req-timeout
To configure the ENUM request timeout period, use the req-timeout command in ENUM configuration mode. To return the timeout period to the default value, use the no form of this command.
Syntax Description
ENUM request timeout period in milliseconds. The range is 0 to 2147483647. |
Command Default
Command Modes
ENUM configuration (config-sbc-sbe-enum)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to configure the ENUM request timeout period:
Related Commands
request-line
To configure the actions for modifying a request line, on the outbound side, use the request-line command in the SIP Header Editor configuration mode. To deconfigure the actions, use the no form of this command.
request-line [ entry entry-number ]
no request-line [ entry entry-number ]
Syntax Description
Command Default
Command Modes
SIP Header Editor configuration (config-sbc-sbe-mep-hdr)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of the modes required to run the command.
Examples
The following example shows how to configure the actions required to modify a request line:
Related Commands
|
|
|
|---|---|
Configures a SIP header or method blacklist editors on a SIP message. |
|
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.
Note Uniform Resource Identifier (URI) is an IP address of the subscriber. It is a string field of 62 characters maximum length.
Command Default
Command Modes
Adjacency SIP configuration (config-sbc-sbe-adj-sip)
Command History
|
|
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
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:
- <user> is taken from the P-Called-Party-ID header if present, or if not, the To header.
- <hostname> is taken from the Contact address that was registered for this subscriber.
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.
Related Commands
|
|
|
|---|---|
Configures the contact header and passthrough header in non-REGISTER requests. |
|
resource-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
Command Modes
Adjacency SIP configuration (config-sbc-sbe-adj-sip)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how the resource-priority-set command sets the SIP adjacency SipToIsp42 with the resource-priority-set named dsn:
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.
Syntax Description
Specifies the string value to be assigned the priority. The value must be followed by the priority as shown: value.priority. |
Command Default
Command Modes
Resource priority (config-sbc-sbe-rsrc-pri-set)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how the resource-priority command configures the priority for resource-priority header string dsn.
response-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.
Syntax Description
Command Default
Command Modes
SIP method-profile configuration (config-sbc-sbe-sip-mth)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example defines a response code map :
Related 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.
no retry-count {#times to retry}
Syntax Description
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
Command Modes
Subscriber delegate profile configuration mode (config-sbc-sbe-subscriber-delegate-prof)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
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:
Related 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.
Syntax Description
Command Default
Command Modes
Server accounting (config-sbc-sbe-acc-ser)
Server authentication (config-sbc-sbe-auth)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to set the retry-interval to 1000 ms.
Related Commands
|
|
|
Sets the maximum number of concurrent requests to the RADIUS server. |
|
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
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
Command Modes
Subscriber delegate profile configuration mode (config-sbc-sbe-subscriber-delegate-prof)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
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:
Related 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.
Syntax Description
Command Default
Command Modes
Server accounting (config-sbc-sbe-acc)
Server authentication (config-sbc-sbe-auth)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to set the retry-limit to 4 attempts.
Related Commands
|
|
|
Sets the maximum number of concurrent requests to the RADIUS server. |
|
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.
Syntax Description
Command Default
Command Modes
SBE configuration (config-sbc-sbe)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to set the retry-limit to 4 attempts.
rf
To create a new Rf billing instance on the Session Border Element (SBE), use the rf command in the SBC SBE billing configuration mode. To delete a new Rf billing instance on the SBE, use the no form of this command.
Syntax Description
Command Default
Command Modes
SBC SBE billing configuration (config-sbc-sbe-billing)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Examples
The following example shows how to enable Rf support for index 0 on the SBE of the Cisco Session Border Controller (SBC):
Related Commands
|
|
|
|---|---|
Specifies the domain name of an origin host for Rf support on the SBE of the SBC. |
|
Specifies the domain name of an origin realm for Rf support on the SBE of the SBC. |
rtcp-mux
To configure the detection of RTCP streams multiplexed with RTP streams (or SRTCP streams multiplexed with SRTP streams), use the rtcp-mux command in the SBE configuration mode. To disable this feature, use the no form of the command.
Syntax Description
Command Default
By default, the detection of RTCP streams multiplexed with RTP streams is disabled. The same applies to SRTCP streams multiplexed with SRTP streams.
Command Modes
SBE configuration (config-sbc-sbe)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of the modes required to run this command.
Examples
The following example shows how to configure the detection of RTCP streams multiplexed with RTP streams using the rtcp-mux command. The same applies to SRTCP streams multiplexed with SRTP streams.
Related Commands
|
|
|
|---|---|
rtcp-regenerate
To generate and terminate the RTCP packets on the SPA-DSP, use the rtcp-regenerate command in the SBC configuration mode for the Cisco Unified Border Element: Unified Model, and from the SBC DBE configuration mode for the Cisco Unified Border Element: Distributed Model.
Syntax Description
Command Default
Command Modes
SBC configuration (config-sbc) for the Unified Model
SBC DBE configuration (config-sbc-dbe) for the Distributed Model
Command History
|
|
|
|---|---|
Usage Guidelines
Use this command to generate and terminate the RTCP packets on the SPA-DSP on a Cisco ASR 1000 Series Router.
Examples
The following example shows how to generate and terminate the RTCP packets on the SPA-DSP on the Unified Model:
The following example shows how to generate and terminate the RTCP packets on the SPA-DSP on the Distributed Model:
rtg-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 call policy set 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
Command Modes
SBE routing policy (config-sbc-sbe-rtgpolicy)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to add the carrier ID table MyCarrierIDTable:
Related Commands
rtg-category-table
To enter the mode 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.
Syntax Description
Command Default
Command Modes
SBE routing policy (config-sbc-sbe-rtgpolicy)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
If necessary, a new routing table is created. The user is not allowed to enter the mode of routing table configuration in the context of the active policy set.
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example creates the routing policy table MyRtgTable:
Related 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-address-table table-id
Syntax Description
Command Default
Command Modes
SBE routing policy (config-sbc-sbe-rtgpolicy)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
If necessary, a new routing table is created. The user is not allowed to enter the mode 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. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following command creates the routing policy table MyRtgTable:
Related Commands
rtg-dst-domain-table
To enter the configuration mode 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 call policy set 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
Command Modes
SBE routing policy (config-sbc-sbe-rtgpolicy)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
You cannot delete a routing table if it is in the active policy set. You cannot enter the mode of a routing table configuration in the active policy set.
Examples
The following command creates the routing policy table MyRtgTable.
Related Commands
rtg-dst-trunk-group-id-table
To enter the configuration mode of an existing routing table or to create a new table whose entries match the destination TGID or TGID context parameters of an SBE policy set, use the rtg-dst-trunk-group-id-table command in SBE call policy set mode. Use the no form of this command to delete the routing table.
rtg-dst-trunk-group-id-table table-id
no rtg-dst-trunk-group-id-table table-id
Syntax Description
Command Default
Command Modes
SBE routing policy (config-sbc-sbe-rtgpolicy)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following command creates a new table, MyRtgTable, whose entries match the destination TGID or TGID context parameters.
Related Commands
rtg-least-cost-table
To configure the least-cost routing table and enter the mode 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
Command Modes
SBE routing policy (config-sbc-sbe-rtgpolicy)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
If necessary, a new routing table is created. The user is not allowed to enter the mode of routing table configuration in the context of the active policy set.
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following command creates the routing policy table MyRtgTable:
Related 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 call policy set 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
Command Modes
SBE routing policy (config-sbc-sbe-rtgpolicy)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
The 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. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example show how to add the round robin routing table MyRoundRobinTable:
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 call policy set mode.
NoteYou cannot issue this command if the table is part of the active policy set. You cannot issue this command if the table is part of the active policy set.
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
Command Modes
SBE routing policy (config-sbc-sbe-rtgpolicy)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following command enters the configuration mode of an existing routing table MyRtgTable:
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
Command Modes
SBE routing policy (config-sbc-sbe-rtgpolicy)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following command creates the routing policy table MyRtgTable:
Related 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 call policy set 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
Command Modes
SBE routing policy (config-sbc-sbe-rtgpolicy)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following command creates a new table, MyRtgTable, whose entries match the source adjacency.
Related Commands
rtg-src-domain-table
To enter the mode of a routing table configuration, with entries that match the source domain name, use the rtg-src-domain table command in SBE call policy set mode. If no table exists, the command creates a new routing table.
NoteYou cannot enter the mode of a routing table configuration in the active policy set. You cannot enter the mode of a routing table configuration in the active policy set.
The no form of the command destroys the routing table.
NoteYou cannot destroy a routing table if it is in the active policy set. You cannot destroy a routing table if it is in the active policy set.
rtg-src-domain-table table-name
no rtg-src-domain-table table-name
Syntax Description
Command Default
Command Modes
SBE routing policy (config-sbc-sbe-rtgpolicy)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following command creates the routing policy table MyRtgTable.
Related Commands
rtg-src-trunk-group-id-table
To enter the configuration mode of an existing routing table or to create a new table whose entries match the source TGID or TGID context parameters of an SBE policy set, use the rtg-src-trunk-group-id-table command in SBE call policy set mode. Use the no form of this command to delete the routing table.
rtg-src-trunk-group-id-table table-id
no rtg-src-trunk-group-id-table table-id
Syntax Description
Command Default
Command Modes
SBE routing policy (config-sbc-sbe-rtgpolicy)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following command creates a new table, MyRtgTable, whose entries match the source TGID or TGID context parameters.
Related Commands
rtg-time-table
To configure time-based routing and enter the routing table mode, 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.
Syntax Description
Command Default
Command Modes
SBE routing policy (config-sbc-sbe-rtgpolicy)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
If necessary, a new routing table is created. The user is not allowed to enter the mode of routing table configuration in the context of the active policy set.
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following command creates the routing policy table MyRtgTable:
Related Commands
sbc
To enter the mode 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.
Syntax Description
Command Default
Command Modes
SBC configuration mode (config-sbc)
Command History
|
|
|
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.
Related Commands
|
|
|
|---|---|
sbc dbe
To create the data border element (DBE) service on a session border controller (SBC) and enter into the SBC-DBE configuration mode, use the sbc dbe command in global configuration mode. To remove the DBE entity, use the no form of this command.
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Examples
The following example creates a DBE service on an SBC called “mySbc,” and enters into SBC-DBE configuration mode:
Related Commands
|
|
|
|---|---|
sbc dump-alarms
To move alarm logs from the buffer to a file system, use the sbc dump-alarms command in privileged EXEC mode.
sbc dump-alarms [ file-system ]
Syntax Description
Command Modes
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
The following is the naming convention for the log file that is generated when you run the sbc dump-alarms command:
Examples
The following example show how the sbc dump-alarms command is used to move alarm logs to the bootflash file system:
The following is the name of a sample log file that is generated when the sbc dump-alarms command is run on 12-May-2011 at 04:34:31:
Related Commands
sbc periodic-dump-alarms
To configure periodic movement of alarm logs from the buffer to a file system, use the sbc periodic-dump-alarms command in the privileged EXEC mode.
sbc periodic-dump-alarms {dump-location file-system [time-period time-period ] | time-period time-period }
Syntax Description
Command Default
The default is that alarm logs are moved to the default file system at 60-minute intervals.
Command Modes
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
The buffer that is used to store alarm logs may run out of free space when log files are stored in it. In addition, you may want to store alarm logs for future reference. Use the sbc periodic-dump-alarms command to meet the requirements created by this scenario. Use the sbc periodic-dump-alarms time-period 0 command if you want to disable the periodic movement of alarm logs from the buffer to a file system.
Examples
In the following example, the sbc periodic-dump-alarms command is used to specify that the logs must be moved to the bootflash file system at 120-minute intervals:
The following is the naming convention for the log file that is generated:
yyyymmdd_hhmmss _periodic_alarmtrc.log
The following is the name of a sample log file that is generated when the sbc periodic-dump-alarms command is used to configure periodic dumping of log files at 1-hour intervals:
Related Commands
sbc redundancy-group tcp (session border controller)
To assign a redundancy group for the Session Border Controller (SBC) to track, use the sbc redundancy-group tcp command in the global configuration mode. To unassign a redundancy group, use the no form of this command.
sbc redundancy-group group-number tcp
no sbc redundancy-group group-number tcp
Syntax Description
Specifies the Transmission Control Protocol (TCP), and the redundancy group protocol. |
Command Default
Command Modes
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Examples
The following example shows how to assign an redundancy group for the SBC to track:
sc-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.
Syntax Description
Command Default
Command Modes
VDBE configuration mode (config-sbc-dbe-vdbe)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers for distributed 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:
The 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.
Related Commands
|
|
|
|---|---|
Lists the MGCs and controller address configured on each DBE. |
sck-pool-size
To configure the buffer size of a Session Initiation Protocol (SIP) socket control, use the sck-pool-size command in the SBE configuration mode. To reconfigure the buffer size of the SIP socket control to the default value, use the no form of this command.
Syntax Description
Pool size number. The range is from 1 to 65535. The default is 400. |
Command Default
Command Modes
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Examples
The following example shows how to configure the buffer size of an SIP socket control:
script-set lua
To configure a script set composed of scripts written using the Lua programming language, use the script-set command in the SBE configuration mode. To remove the configuration of the script set, use the no form of this command.
script-set script-set-number lua
no script-set script-set-number
Syntax Description
Command Default
Command Modes
SBE configuration (config-sbc-sbe)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 100 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of the modes required to run this command.
Examples
In the following example, the script-set command is used to configure a script set with the script order number 10:
Related Commands
script
To configure a script written using the Lua programming language, use the script command in the SBE script-set configuration mode. To remove the configuration of the script, use the no form of this command.
Syntax Description
Command Default
Command Modes
SBE script-set configuration (config-sbc-sbe-script-set)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 100 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of the modes required to run this command.
Examples
In the following example, the script command is used to configure a script file with the name mySBCScript:
Related Commands
sdp repeat answer
To configure SBC to repeat an agreed Session Description Protocol (SDP), in a 200 INVITE response, after the successful provisioning of an offer-answer exchange when needed, use the sdp repeat answer command in CAC table entry configuration mode. To restore the default, where agreed SDPs are not repeated, use the no form of this command.
Syntax Description
Command Default
By default, an agreed SDP in a 200 INVITE response is not repeated.
Command Modes
CAC table entry configuration (config-sbc-sbe-cacpolicy-cactable-entry)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to configure the repeat of an Session Description Protocol (SDP), in a 200 INVITE response, after the successful provisioning of an offer-answer exchange:
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.
Syntax Description
Command Default
Command Modes
SBE configuration (config-sbc-sbe)
Command History
|
|
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
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.
Related Commands
|
|
|
|---|---|
Creates the SBC service on Cisco Unified Border Element (SP Edition). |
|
Enters the mode of the signaling border element (SBE) function of the SBC. |
security (session border controller)
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
Command Default
Command Modes
Adjacency SIP configuration (config-sbc-sbe-adj-sip)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
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. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following command configures accounting servers castor and pollux on mySbc for RADIUS client instance radius1:
server-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.
Syntax Description
Command Default
Command Modes
Server accounting (config-sbc-sbe-acc)
Server authentication (config-sbc-sbe-auth)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
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:
Related Commands
|
|
|
|---|---|
Reactivates connection between the SBC and a RADIUS server after connectivity is lost or to restart billing after connectivity is restored. |
server ipv4
To configure the IPv4 address of a DNS server for ENUM client and optionally associate the DNS server to a VRF, use the server ipv4 command in ENUM entry configuration mode. To remove IPv4 address of a DNS server for ENUM client, use the no form of this command.
server ipv4 ip_address [ vrf vrf_name ]
no server ipv4 ip_address [ vrf vrf_name ]
Syntax Description
Command Default
Command Modes
ENUM entry configuration (config-sbc-sbe-enum-entry)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to configure the IPv4 address of a DNS server for ENUM client and associate the DNS server to a VRF:
Related Commands
server (session border controller)
To enter a mode 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 mode.
Syntax Description
Command Default
Command Modes
Server accounting (config-sbc-sbe-acc)
Server authentication (config-sbc-sbe-auth)
Command History
|
|
|
|---|---|
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. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following command configures accounting servers castor and pollux on mySbc for RADIUS client instance radius1:
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
Command Modes
Command History
|
|
|
|---|---|
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
session-refresh renegotiation
To enable or disable renegotiation of media bypass after session refreshes, use the session-refresh renegotiation command in the CAC table entry configuration mode. To remove this configuration, use the no form of this command.
session-refresh renegotiation {allow | suppress}
no session-refresh renegotiation
Syntax Description
Command Default
The default is that the session refresh strategy for the call is not affected by this CAC policy entry.
Command Modes
CAC table entry configuration (config-sbc-sbe-cacpolicy-cactable-entry)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of the modes required to run the command.
Examples
The following example shows how to disable renegotiation of media bypass after the session refreshes:
Related Commands
show debugging
To display information about the types of debugging that are enabled for your router, use the show debugging command in the privileged EXEC mode.
Syntax Description
Command Modes
Command History
Examples
The following is sample output of the show debugging command. In this example, the remote host is neither configured nor connected.
The following is sample output of the show debugging command when user-group debugging is configured:
The following is sample output of the show debugging command when SNAP debugging is configured:
Persistent variable debugging is currently All
Table 1 describes the significant fields in the output.
show monitor event-trace sbc ha
To display the event trace messages for the Session Border Controller (SBC), use the show monitor event-trace sbc command in the privileged EXEC mode.
show monitor event-trace sbc ha { all [ detail ] | back { minutes | hours:minutes } [ detail ] | clock hours : minutes [ day month ] [ detail ] | from-boot [ seconds ] [ detail ] | latest [ detail ] | parameters }1
Syntax Description
Command Modes
Command History
|
|
|
|---|---|
The sbc_ha keyword was bifurcated into two keywords, sbc and ha . |
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
Use the show monitor event-trace sbc ha command to display trace message information pertaining to the SBC high availability.
The trace function is not locked when information is displayed on the console, which means that the new trace messages can be accumulated in memory. If entries are accumulated faster than they may be displayed, some messages can be lost. If this happens, the show monitor event-trace sbc ha command generates a message indicating that some messages may be lost. However, messages continue to be displayed on the console. If the number of lost messages is excessive, the show monitor event-trace sbc ha command stops displaying messages.
Examples
The following is a sample output of the show monitor event-trace sbc ha all command. In the following example, all the messages from the SBC high availability events are displayed:
Table 2 describes the significant fields shown in the display.
The following is a sample output of the show monitor event-trace sbc ha latest command. This command displays the messages from the SBC high availability events since the last show monitor event-trace sbc ha command was entered.
This command displays the messages since the last show monitor event-trace sbc ha command was entered.
Table 3 describes the significant fields shown in the display.
|
|
|
|---|---|
ILT events. ILT is the interface and mechanism for transporting SBC high availability data. |
|
The following is a sample output of the show monitor event-trace sbc ha parameters command. This command displays the number of event trace messages in the trace file, and whether stacktrace is disabled.
Related Commands
|
|
|
|---|---|
Feedback