Table Of Contents
show sbc sbe policy-failure-stats
show sbc sbe policy-failure-stats dst-account
show sbc sbe policy-failure-stats dst-adjacency
show sbc sbe policy-failure-stats src-account
show sbc sbe policy-failure-stats src-adjacency
show sbc sbe qos-profiles
show sbc sbe radius-client-accounting accounting
show sbc sbe radius-client-accounting authentication
show sbc sbe radius-client-stats
show sbc sbe radius-server-stats
show sbc sbe redirect-limit
show sbc sbe resource-priority-sets
show sbc sbe sdp-h245-mapping
show sbc sbe sdp-match-table
show sbc sbe sdp-policy-table
show sbc sbe sip delegate-profiles
show sbc sbe sip essential-headers
show sbc sbe sip essential-methods
show sbc sbe sip essential-options
show sbc sbe sip fast-register-stats
show sbc sbe sip header-profile
show sbc sbe sip header-profiles
show sbc sbe sip ip-fqdn-mapping
show sbc sbe sip method-profile
show sbc sbe sip method-profiles
show sbc sbe sip method-stats
show sbc sbe sip option-profile
show sbc sbe sip option-profiles
show sbc sbe sip sdp-match-table
show sbc sbe sip sdp-media-profile
show sbc sbe sip sdp-policy-table
show sbc sbe sip statistics
show sbc sbe sip subscribers
show sbc sbe sip timers
show sbc services
signaling-address ipv4
signaling-peer
signaling-peer-port
signaling-port
sip dns
sip adjacency
sip-contact
sip encryption key
sip header-profile
sip home network identifier
sip hunting-trigger
sip ip-fqdn-mapping
sip inherit profile
sip max-connections
sip method-profile
sip option-profile
sip parameter-profile
sip sdp-match-table
sip sdp-media-profile
sip sdp origin-user-name
sip sdp-policy-table
sip timer
sip visited network identifier
sipi
snmp-server enable traps sbc
start
statistics-setting
subscriber
table-type
tcp (blacklist)
tcp-connect-timeout
tcp-idle-timeout
tcp timer giveup
tech-prefix
tgid-context
tgid-routing
time-offset
timeout
timezone-offset
transcode-deny
transcoder
translate
transport (SBE H.248)
transport (session border controller)
trigger-period
trigger-size
udp (blacklist)
udp-first-retransmit-interval
udp-max-retransmit-interval
udp-response-linger-period
unexpected-source-alerting
use-any-local-port
use-time-offset
vdbe
vpn
vrf
weight
show sbc sbe policy-failure-stats
To list the statistics for all of the policy failures on a specific SBE, use the show sbc sbe policy-failure-stats command in Privileged EXEC mode.
show sbc sbc-name sbe policy-failure-stats period
Syntax Description
sbc-name
|
Specifies the SBC service.
|
period
|
Specifies the time period for the statistics that you want to display. The time period can be one of the following:
• current15mins—Displays statistics in 15 minute intervals starting from the current minute.
• current5mins—Displays statistics in 5 minute intervals starting from the current minute.
• currentday—Displays statistics for the current day starting midnight of the same day.
• currenthour—Displays statistics for the current hour.
• previous15mins—Displays statistics from previous 15 minute intervals.
• previous5mins—Displays statistics from previous 5 minute intervals.
• previousday—Displays statistics from the previous day.
• previoushour—Displays statistics from the previous hour.
|
Command Default
No default behavior or values
Command Modes
Privileged EXEC (#)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.4
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Usage Guidelines
The statistics are collected at 5 minute intervals past the hour (that is, at 0, 5, 10, 15 minutes, and so on past the hour). For example, the periods covered by the various buckets at 12:43 would be as follows:
•
current five minutes: 12:40-12:43
•
previous five minutes: 12:35-12:40
•
current 15 minutes: 12:30-12:43
•
previous 15 minutes: 12:15-12:30
•
current hour: 12:00-12:43
•
last hour: 11:00-12:00
•
current day: 00:00-12:43
•
last day: 00:00-24h - 00:00.
Examples
The following example shows the complete policy failure statistics for source adjacency glophone and source account 200 for the current day:
Router# show sbc global sbe policy-failure-stats currentday
Policy failure statistics for the current day for source adjacency glophone:
Total call setup failures: 8
Call setups failed due to NA: 0
Call setups failed due to rtg: 8
Call setups failed due to CAC: 0
CAC fails due to num call lim: 0
CAC fails due to rate call lim: 0
CAC fails due to num channels lim: 0
CAC fails due to bandwidth lim: 0
Policy failure statistics for the current day for source account 200
Total call setup failures: 8
Call setups failed due to NA: 0
Call setups failed due to rtg: 8
Call setups failed due to CAC: 0
CAC fails due to num call lim: 0
CAC fails due to rate call lim: 0
CAC fails due to num channels lim: 0
CAC fails due to bandwidth lim: 0
Table 9 show sbc sbe policy-failure-stats Field Descriptions
Field
|
Description
|
Total call setup failures
|
Total number of call setup failures due to Number Analysis, Routing, and CAC Policies.
|
Call setups failed due to NA
|
Total number of call setup failures due to Number Analysis policies.
|
Call setups failed due to rtg
|
Total number of call setup failures due to routing policies.
|
Call setups failed due to CAC
|
Total number of call setup failures due to CAC policies.
|
CAC fails due to num call lim
|
Total number of call setup failures due to CAC call limits.
|
CAC fails due to call rate lim
|
Total number of call setup failures due to CAC call rate limits.
|
CAC fails due to num media channels lim
|
Total number of call setup failures due to CAC number of media channels limits.
|
CAC fails due to num media updates lim
|
Total number of call setup failures due to CAC number of media updates limits.
|
CAC fails due to bandwidth lim
|
Total number of call setup failures due to CAC Bandwidth Limits.
|
Related Commands
Command
|
Description
|
clear sbc sbe policy-rejection-stats
|
Clears all the policy rejection statistics by the SBE.
|
show sbc sbe policy-failure-stats src-adjacency
|
Lists the statistics for all the policy failures on the specified SBE.
|
show sbc sbe policy-failure-stats dst-adjacency
|
Lists the statistics for the policy failures for calls with the adjacency.
|
show sbc sbe policy-failure-stats src-account
|
Lists the statistics for the policy failures for calls with the account.
|
show sbc sbe policy-failure-stats dst-account
|
Lists the statistics for the policy failures for calls with the account.
|
show sbc sbe policy-failure-stats dst-account
To list policy failure statistics for a specified target account for a specified time period, use the show sbc sbe policy-failure-stats dst-account command in Privileged EXEC mode.
show sbc sbc-name sbe policy-failure-stats dst-account name period time-period
Syntax Description
sbc-name
|
Specifies the name of the SBC service.
|
name
|
Specifies the name of the account for which you would like to display statistics. The maximum length of this value is 30 characters.
|
period time-period
|
Specifies the time period to which the statistics apply. Choose one of the following time intervals:
• current15mins—Displays statistics in 15 minute intervals starting from the current minute.
• current5mins—Displays statistics in 5 minute intervals starting from the current minute.
• currentday—Displays statistics for the current day starting midnight of the same day.
• currenthour—Displays statistics for the current hour.
• previous15mins—Displays statistics from previous 15 minute intervals.
• previous5mins—Displays statistics from previous 5 minute intervals.
• previousday—Displays statistics from the previous day.
• previoushour—Displays statistics from the previous hour.
|
Command Default
No default behavior or values
Command Modes
Privileged EXEC (#)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.4
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Usage Guidelines
The statistics are collected at 5 minute intervals past the hour (that is, at 0, 5, 10, 15 minutes, and so on past the hour). For example, the periods covered by the various buckets at 12:43 would be as follows:
•
current five minutes: 12:40-12:43
•
previous five minutes: 12:35-12:40
•
current 15 minutes: 12:30-12:43
•
previous 15 minutes: 12:15-12:30
•
current hour: 12:00-12:43
•
last hour: 11:00-12:00
•
current day: 00:00-12:43
•
last day: 00:00-24h - 00:00.
Examples
The following example lists the policy failure statistics for an adjacent account named AA for the current hour:
Router# show sbc mysbc sbe policy-failure-stats dst-account AA period currenthour
Policy failure statistics for the current hour for source adjacency AA
Total call setup failures: 10
Call setups failed due to NA: 5
Call setups failed due to rtg: 3
Call setups failed due to CAC: 2
CAC fails due to num call lim: 1
CAC fails due to rate call lim: 0
CAC fails due to num channels lim: 0
CAC fails due to bandwidth lim: 1
Table 10 show sbc sbe policy-failure-stats dst-account Field Descriptions
Field
|
Description
|
Total call setup failures
|
Total number of call setup failures due to Number Analysis, Routing, and CAC Policies.
|
Call setups failed due to NA
|
Total number of call setup failures due to Number Analysis policies.
|
Call setups failed due to rtg
|
Total number of call setup failures due to routing policies.
|
Call setups failed due to CAC
|
Total number of call setup failures due to CAC policies.
|
CAC fails due to num call lim
|
Total number of call setup failures due to CAC call limits.
|
CAC fails due to call rate lim
|
Total number of call setup failures due to CAC call rate limits.
|
CAC fails due to num media channels lim
|
Total number of call setup failures due to CAC number of media channels limits.
|
CAC fails due to num media updates lim
|
Total number of call setup failures due to CAC number of media updates limits.
|
CAC fails due to bandwidth lim
|
Total number of call setup failures due to CAC Bandwidth Limits.
|
Related Commands
Command
|
Description
|
show sbc sbe policy-failure-stats dst-adjacency
|
Lists policy failure statistics for calls within the specified target adjacency for the specified time period.
|
show sbc sbe policy-failure-stats src-account
|
Lists policy failure statistics for calls within the specified source account for the specified time period.
|
show sbc sbe policy-failure-stats src-adjacency
|
Lists policy failure statistics for calls within the specified source adjacency for the specified time period.
|
show sbc sbe policy-failure-stats dst-adjacency
To list policy failure statistics for a specified target adjacency for a specified time period use the show sbc sbe policy-failure-stats dst-adjacency command in Privileged EXEC mode.
show sbc sbc-name sbe policy-failure-stats dst-adjacency name period time-period
Syntax Description
sbc-name
|
Specifies the name of the SBC service.
|
name
|
Specifies the name of the adjacency for which you would like to display statistics. The maximum length of this value is 30 characters.
|
period time-period
|
Specifies the time period to which the statistics apply. Choose one of the following time intervals:
• current15mins—Displays statistics in 15 minute intervals starting from the current minute.
• current5mins—Displays statistics in 5 minute intervals starting from the current minute.
• currentday—Displays statistics for the current day starting midnight of the same day.
• currenthour—Displays statistics for the current hour.
• previous15mins—Displays statistics from previous 15 minute intervals.
• previous5mins—Displays statistics from previous 5 minute intervals.
• previousday—Displays statistics from the previous day.
• previoushour—Displays statistics from the previous hour.
|
Command Default
No default behavior or values
Command Modes
Privileged EXEC (#)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.4
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Usage Guidelines
The statistics are collected at 5 minute intervals past the hour (that is, at 0, 5, 10, 15 minutes, and so on past the hour). For example, the periods covered by the various buckets at 12:43 would be as follows:
•
current five minutes: 12:40-12:43
•
previous five minutes: 12:35-12:40
•
current 15 minutes: 12:30-12:43
•
previous 15 minutes: 12:15-12:30
•
current hour: 12:00-12:43
•
last hour: 11:00-12:00
•
current day: 00:00-12:43
•
last day: 00:00-24h - 00:00.
Examples
The following example shows the policy failure statistics for an adjacency named ZZ for the current hour:
Router# show sbc mysbc sbe policy-failure-stats dst-adjacency ZZ period currenthour
Policy failure statistics for the current hour for source adjacency ZZ
Total call setup failures: 10
Call setups failed due to NA: 5
Call setups failed due to rtg: 3
Call setups failed due to CAC: 2
CAC fails due to num call lim: 1
CAC fails due to rate call lim: 0
CAC fails due to num channels lim: 0
CAC fails due to bandwidth lim: 1
Table 11 show sbc sbe policy-failure-stats dst-adjacency Field Descriptions
Field
|
Description
|
Total call setup failures
|
Total number of call setup failures due to Number Analysis, Routing, and CAC Policies.
|
Call setups failed due to NA
|
Total number of call setup failures due to Number Analysis policies.
|
Call setups failed due to rtg
|
Total number of call setup failures due to routing policies.
|
Call setups failed due to CAC
|
Total number of call setup failures due to CAC policies.
|
CAC fails due to num call lim
|
Total number of call setup failures due to CAC call limits.
|
CAC fails due to call rate lim
|
Total number of call setup failures due to CAC call rate limits.
|
CAC fails due to num media channels lim
|
Total number of call setup failures due to CAC number of media channels limits.
|
CAC fails due to num media updates lim
|
Total number of call setup failures due to CAC number of media updates limits.
|
CAC fails due to bandwidth lim
|
Total number of call setup failures due to CAC Bandwidth Limits.
|
Related Commands
Command
|
Description
|
show sbc sbe policy-failure-stats dst-account
|
Lists policy failure statistics for calls within the specified target account for the specified time period.
|
show sbc sbe policy-failure-stats src-account
|
Lists policy failure statistics for calls within the specified source account for the specified time period.
|
show sbc sbe policy-failure-stats src-adjacency
|
Lists policy failure statistics for calls within the specified source adjacency for the specified time period.
|
show sbc sbe policy-failure-stats src-account
To list policy failure statistics for a specified source account for a specified time period use the show sbc sbe policy-failure-stats src-account command in Privileged EXEC mode.
show sbc sbc-name sbe policy-failure-stats src-account name period time-period
Syntax Description
sbc-name
|
Specifies the name of the SBC service.
|
name
|
Specifies the name of the account for which you would like to display statistics. The maximum length of this value is 30 characters.
|
period time-period
|
Specifies the time period to which the statistics apply. Choose one of the following time intervals:
• current15mins—Displays statistics in 15 minute intervals starting from the current minute.
• current5mins—Displays statistics in 5 minute intervals starting from the current minute.
• currentday—Displays statistics for the current day starting midnight of the same day.
• currenthour—Displays statistics for the current hour.
• previous15mins—Displays statistics from previous 15 minute intervals.
• previous5mins—Displays statistics from previous 5 minute intervals.
• previousday—Displays statistics from the previous day.
• previoushour—Displays statistics from the previous hour.
|
Command Default
No default behavior or values
Command Modes
Privileged EXEC (#)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.4
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Usage Guidelines
The statistics are collected at 5 minute intervals past the hour (that is, at 0, 5, 10, 15 minutes, and so on past the hour). For example, the periods covered by the various buckets at 12:43 would be as follows:
•
current five minutes: 12:40-12:43
•
previous five minutes: 12:35-12:40
•
current 15 minutes: 12:30-12:43
•
previous 15 minutes: 12:15-12:30
•
current hour: 12:00-12:43
•
last hour: 11:00-12:00
•
current day: 00:00-12:43
•
last day: 00:00-24h - 00:00.
Examples
The following example shows the policy failure statistics for a source account named BB for the current hour:
Router# show sbc mysbc sbe policy-failure-stats src-account BB period currenthour
Policy failure statistics for the current hour for source adjacency BB
Total call setup failures: 10
Call setups failed due to NA: 5
Call setups failed due to rtg: 3
Call setups failed due to CAC: 2
CAC fails due to num call lim: 1
CAC fails due to rate call lim: 0
CAC fails due to num channels lim: 0
CAC fails due to bandwidth lim: 1
Table 12 show sbc sbe policy-failure-stats src-account Field Descriptions
Field
|
Description
|
Total call setup failures
|
Total number of call setup failures due to Number Analysis, Routing, and CAC Policies.
|
Call setups failed due to NA
|
Total number of call setup failures due to Number Analysis policies.
|
Call setups failed due to rtg
|
Total number of call setup failures due to routing policies.
|
Call setups failed due to CAC
|
Total number of call setup failures due to CAC policies.
|
CAC fails due to num call lim
|
Total number of call setup failures due to CAC call limits.
|
CAC fails due to call rate lim
|
Total number of call setup failures due to CAC call rate limits.
|
CAC fails due to num media channels lim
|
Total number of call setup failures due to CAC number of media channels limits.
|
CAC fails due to num media updates lim
|
Total number of call setup failures due to CAC number of media updates limits.
|
CAC fails due to bandwidth lim
|
Total number of call setup failures due to CAC Bandwidth Limits.
|
Related Commands
Command
|
Description
|
show sbc sbe policy-failure-stats dst-adjacency
|
Lists policy failure statistics for calls within the specified target adjacency for the specified time period.
|
show sbc sbe policy-failure-stats dst-account
|
Lists policy failure statistics for calls within the specified target account for the specified time period.
|
show sbc sbe policy-failure-stats src-adjacency
|
Lists policy failure statistics for calls within the specified source adjacency for the specified time period.
|
show sbc sbe policy-failure-stats src-adjacency
To list policy failure statistics for a specified source adjacency for a specified time period use the show sbc sbe policy-failure-stats src-adjacency command in Privileged EXEC mode.
show sbc sbc-name sbe policy-failure-stats src-adjacency name period time-period
Syntax Description
sbc-name
|
Specifies the name of the SBC service.
|
name
|
Specifies the name of the adjacency for which you would like to display statistics. The maximum name length is 30 characters.
|
period time-period
|
Specifies the time period to which the statistics apply. Choose one of the following time intervals:
• current15mins—Displays statistics in 15 minute intervals starting from the current minute.
• current5mins—Displays statistics in 5 minute intervals starting from the current minute.
• currentday—Displays statistics for the current day starting midnight of the same day.
• currenthour—Displays statistics for the current hour.
• previous15mins—Displays statistics from previous 15 minute intervals.
• previous5mins—Displays statistics from previous 5 minute intervals.
• previousday—Displays statistics from the previous day.
• previoushour—Displays statistics from the previous hour.
|
Command Default
No default behavior or values
Command Modes
Privileged EXEC (#)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.4
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Usage Guidelines
The statistics are collected at 5 minute intervals past the hour (that is, at 0, 5, 10, 15 minutes, and so on past the hour). For example, the periods covered by the various buckets at 12:43 would be as follows:
•
current five minutes: 12:40-12:43
•
previous five minutes: 12:35-12:40
•
current 15 minutes: 12:30-12:43
•
previous 15 minutes: 12:15-12:30
•
current hour: 12:00-12:43
•
last hour: 11:00-12:00
•
current day: 00:00-12:43
•
last day: 00:00-24h - 00:00.
Examples
The following example displays policy failure statistics for a source adjacency named YY for the current hour:
Router# show sbc test sbe policy-failure-stats src-adjacency Acct1
Policy failure statistics for the current 15 mins for source adjacency Acct1
Total call setup failures: 0
Call setups failed due to NA: 0
Call setups failed due to rtg: 0
Call setups failed due to CAC: 0
CAC fails due to num call lim: 0
CAC fails due to rate call lim: 0
CAC fails due to num channels lim: 0
CAC fails due to bandwidth lim: 0
Table 13 show sbc sbe policy-failure-stats src-adjacency Field Descriptions
Field
|
Description
|
Total call setup failures
|
Total number of call setup failures due to Number Analysis, Routing, and CAC Policies.
|
Call setups failed due to NA
|
Total number of call setup failures due to Number Analysis policies.
|
Call setups failed due to rtg
|
Total number of call setup failures due to routing policies.
|
Call setups failed due to CAC
|
Total number of call setup failures due to CAC policies.
|
CAC fails due to num call lim
|
Total number of call setup failures due to CAC call limits.
|
CAC fails due to call rate lim
|
Total number of call setup failures due to CAC call rate limits.
|
CAC fails due to num media channels lim
|
Total number of call setup failures due to CAC number of media channels limits.
|
CAC fails due to num media updates lim
|
Total number of call setup failures due to CAC number of media updates limits.
|
CAC fails due to bandwidth lim
|
Total number of call setup failures due to CAC Bandwidth Limits.
|
Related Commands
Command
|
Description
|
show sbc sbe policy-failure-stats dst-adjacency
|
Lists policy failure statistics for calls within the specified target adjacency for the specified time period.
|
show sbc sbe policy-failure-stats src-account
|
Lists policy failure statistics for calls within the specified source account for the specified time period.
|
show sbc sbe policy-failure-stats dst-account
|
Lists policy failure statistics for calls within the specified target account for the specified time period.
|
show sbc sbe qos-profiles
To list all QoS profiles, use the show sbc sbe qos-profiles command in Privileged EXEC mode.
show sbc sbc-name sbe qos-profiles [profile-name]
Syntax Description
sbc-name
|
Specifies the name of the SBC service.
|
profile-name
|
(Optional) Specifies the profile name.
If you specify a QoS profile, the details of that profile are shown.
|
Defaults
No default behavior or values
Command Modes
Privileged EXEC (#)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.4
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Examples
The following example shows how to list all of the QoS profiles on the SBE:
Router# show sbc test sbe qos-profiles
---------------------------------------------------------
The show sbc test sbe qos-profiles command is invalid when displaying one profile. Correct usage is singular as shown below.
Router# show sbc test sbe qos-profiles profile6
% long command detected at '^' marker.
Router# show sbc test sbe qos-profile profile6
show sbc sbe radius-client-accounting accounting
To list the parameters configured for the account, use the show sbc sbe radius-client-accounting accounting command in Privileged EXEC mode.
show sbc sbc-name sbe radius-client-accounting accounting client-name
Syntax Description
sbc name
|
This is the name of the SBC service.
|
client-name
|
Clears all statistics for the specified local RADIUS client.
|
Defaults
No default behavior or values
Command Modes
Privileged EXEC (#)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.4
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Examples
The following example lists the parameters configured for accounting:
Router# show sbc uut105-1 sbe radius-client-accounting accounting SBC1-account-1
radius client address = 88.105.2.100
radius client retry interval = 1200
radius client retry limit = 5
radius client concurrent requests limit = 250
show sbc sbe radius-client-accounting authentication
To list the parameters configured for the authentication, use the show sbc sbe radius-client-accounting authentication command in Privileged EXEC mode.
show sbc sbc-name sbe radius-client-accounting authentication
Syntax Description
sbc name
|
This is the name of the SBC service.
|
Defaults
No default behavior or values
Command Modes
Privileged EXEC (#)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.4
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Examples
The following example lists the parameters configured for the authentication:
Router# show sbc mysbc sbe radius-client-accounting authentication
radius client address = 88.105.128.100
radius client retry interval = 1800
radius client retry limit = 5
radius client concurrent requests limit = 250
show sbc sbe radius-client-stats
To list the RADIUS accounting client statistics for all accounting clients configured on an SBE, use the show sbc sbe radius-client-stats command in Privileged EXEC mode.
show sbc sbc-name sbe radius-client-stats radius-client [accounting client-name |
authentication]
Syntax Description
sbc name
|
This is the name of the SBC service.
|
radius-client
|
Specifies the RADIUS client to show.
|
accounting client-name
|
Specifies the name to assign to the accounting RADIUS client.
|
authentication
|
Enables client authentication.
|
Defaults
No default behavior or values
Command Modes
Privileged EXEC (#)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.4
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Examples
The following example shows how to list the RADIUS accounting server statistics for all accounting servers configured on an SBE:
Router# show sbc j sbe radius-client-stats accounting CISCO_UM
The following example shows how to list the RADIUS accounting server statistics for all authentication servers configured on an SBE:
Router# show sbc j sbe radius-client-stats authentication
show sbc sbe radius-server-stats
To list the RADIUS server statistics for all accounting servers configured on a RADIUS client on an SBE, use the show sbc sbe radius-server-stats command in Privileged EXEC mode.
show sbc sbc-name sbe radius-server-stats radius-client [accounting client-name |
authentication]
Syntax Description
sbc name
|
This is the name of the SBC service.
|
radius-client
|
Specifies the RADIUS client to show.
|
accounting client-name
|
Specifies the name to assign to the accounting RADIUS client.
|
authentication
|
Enables client authentication.
|
Defaults
No default behavior or values
Command Modes
Privileged EXEC (#)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.4
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Examples
The following example shows how to list the RADIUS server statistics for all accounting servers configured on a radius client on an SBE:
Router# show sbc sanity sbe radius-server-stats accounting SBC1-account-1
Access-request retransmitted: 0
Access-accepts received: 0
Access-reject received: 0
Access-challenge received: 0
Accounting-requests sent: 0
Accounting-requests retransmitted: 0
Accounting-responses received: 0
Malformed packets received: 0
Invalid authenticators received: 0
Outstanding respsonses: 0
The following example shows how to list the RADIUS server statistics for all authentication servers configured on a radius client on an SBE:
Router# show sbc sanity sbe radius-server-stats authentication
Access-request retransmitted: 0
Access-accepts received: 0
Access-reject received: 0
Access-challenge received: 0
Accounting-requests sent: 0
Accounting-requests retransmitted: 0
Accounting-responses received: 0
Malformed packets received: 0
Invalid authenticators received: 0
Outstanding respsonses: 0
show sbc sbe redirect-limit
To display the current limit on the maximum number of redirections that a call can undergo, use the show sbc sbe redirect-limit command in Privileged EXEC mode.
show sbc sbc-name sbe redirect-limit
Syntax Description
sbc-name
|
Specifies the name of the SBC service.
|
Defaults
No default behavior or values
Command Modes
Privileged EXEC (#)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.4
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Examples
The following example displays the limit on the maximum number of redirections that a call can undergo:
Router# show service sbc mysbc sbe redirect-limit
show sbc sbe resource-priority-sets
To display the resource priority sets, use the show sbc sbe resource-priority-sets command in Privileged EXEC mode.
show sbc sbc-name sbe resource-priority-sets
Syntax Description
sbc-name
|
Specifies the name of the SBC service.
|
Command Default
No default behavior or values
Command Modes
Privileged EXEC (#)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.4
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Usage Guidelines
Lists the high-level status and capabilities of each instantiated SBE or DBE.
Examples
The following example shows how the show sbc sbe resource-priority-sets command is used to display the resource priority sets:
Router# show sbc mysbc sbe resource-priority-sets
---------------------------------------------------------
Router# show sbc test sbe resource-priority-set dsn
Resource priority set: dsn
---------------------------------------------------------------------
show sbc sbe sdp-h245-mapping
To display the mapping for codec strings between SDP (SIP) and H245 (H323), use the show sbc sbe sdp-h245-mapping command in Privileged EXEC mode.
show sbc sbc-name sbe sdp-h245-mapping
Syntax Description
sbc-name
|
Specifies the name of the SBC service.
|
Command Default
No default behavior or values
Command Modes
Privileged EXEC (#)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.4
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Usage Guidelines
Lists the high-level status and capabilities of each instantiated SBE or DBE.
Examples
The following example shows how the show sbc sbe sdp-h245-mapping command is used.
Router# show sbc mysbc sbe sdp-h245-mappings
- T.38 fax is the only non-audio codec supported.
- Audio codecs not in the list above are reported as ''PCMU''.
In SIP/H.323 interworking calls, only audio codecs using static
RTP payload types are supported.
show sbc sbe sdp-match-table
This command was deprecated in Cisco IOS XE Release 2.5.
To show the SDP match table configured on the SBC, use the show sbc sbe sdp-match-table command in Privileged EXEC mode.
show sbc sbc-name sbe sdp-match-table [detail]
Syntax Description
sbc-name
|
Specifies the name of the SBC service.
|
detail
|
Shows the SDP attribute configured on a given SDP match table.
|
Command Default
No default behavior or values
Command Modes
Privileged EXEC (#)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.4
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Cisco IOS XE Release 2.5
|
This command was deprecated. It was replaced by the new command show sbc sbe sip sdp-match-table.
|
Examples
The following example shows how the show sbc sbe sdp-match-table command is used to display SDP match table:
Router# show sbc pgw sbe sdp-match-table detail
Action : blacklist <--- action: blacklist or whitelist
Match String : ddd <--- several match string
-------------------------------------------------
Related Commands
Command
|
Description
|
show sbc sbe sdp-h245-mapping
|
Displays the mapping for codec strings between SDP (SIP) and H245 (H323).
|
show sbc sbe sdp-policy-table
This command was deprecated in Cisco IOS XE Release 2.5.
To show the SDP policy table configured on the SBC, use the show sbc sbe sdp-policy-table command in Privileged EXEC mode.
show sbc sbc-name sbe sdp-policy-table
Syntax Description
sbc-name
|
Specifies the name of the SBC service.
|
Command Default
No default behavior or values
Command Modes
Privileged EXEC (#)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.4
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Cisco IOS XE Release 2.5
|
This command was deprecated. It was replaced by the new command show sbc sbe sip sdp-policy-table.
|
Examples
The following example shows how the show sbc sbe sdp-policy-table command is used to display the SDP policy table:
Router# show sbc pgw sbe sdp-policy-table
--------------------------------------------------
p m <--- "m" is sdp match table name
Related Commands
Command
|
Description
|
show sbc sbe sdp-match-table
|
Shows the SDP match table configured on the SBC.
|
show sbc sbe sip delegate-profiles
To display delegate profiles for subscribers for whom Provisioned Delegate Registration has been configured, use the show sbc sbe sip delegate-profiles command in Privileged EXEC mode.
show sbc sbc-name sbe sip delegate-profiles
Syntax Description
sbc-name
|
Specifies the name of the SBC service.
|
Command Default
No default behavior or values
Command Modes
Privileged EXEC (#)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.4
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Examples
The following example displays delegate profiles for subscribers for whom delegate registration has been configured:
Router# show sbc mySBC sbe sip delegate-profiles
012345789012345789012345789012345789012345789012345789012345789012345789
--------------------------------------------------
Retry Interval (secs) = 30
Refresh Buffer (secs) = 30
--------------------------------------------------
show sbc sbe sip essential-headers
To display a list of the essential SIP headers, use the show sbc sbe sip essential-headers command in Privileged EXEC mode.
show sbc sbc-name sbe sip essential-headers
Syntax Description
sbc-name
|
Specifies the name of the SBC service.
|
Command Default
No default behavior or values
Command Modes
Privileged EXEC (#)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.4
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Examples
The following example shows how the show sbc sbe sip essential-headers command is used to display a list of all essential headers:
Router# show sbc mySbc sbe sip essential-headers
AUTHORIZATION CALL-ID CONTACT CONTENT-LENGTH
CONTENT-TYPE CSEQ EVENT EXPIRES FROM MAX-FORWARDS
MIN-EXPIRES PROXY-AUTHORIZATION
PROXY-AUTHENTICATE PROXY-REQUIRE RACK
RECORD-ROUTE REFERRED-BY REFER-TO REPLACES
REQUIRE ROUTE RSEQ SUBSCRIPTION-STATE SUPPORTED
Related Commands
Command
|
Description
|
show sbc sbe sip header-profile
|
Displays a list of all configured SIP header profiles.
|
show sbc sbe sip essential-methods
To display a list of the essential SIP methods, use the show sbc sbe sip essential-methods command in Privileged EXEC mode.
show sbc sbc-name sbe sip essential-methods
Syntax Description
sbc-name
|
Specifies the name of the SBC service.
|
.
Command Default
No default behavior or values
Command Modes
Privileged EXEC (#)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.4
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Examples
The following example shows how the show sbc sbe sip essential-methods command is used to display a list of all essential methods:
Router# show sbc mySbc sbe sip essential-methods
ACK BYE CANCEL INVITE NOTIFY PRACK REFER REGISTER
Related Commands
Command
|
Description
|
show sbc sbe sip method-profiles
|
Displays a list of all configured SIP method profiles.
|
show sbc sbe sip essential-options
To show the options that are vital for base SBC operation, use the show sbc sbe sip essential-options command in Privileged EXEC mode.
show sbc sbc-name sbe sip essential-options
Syntax Description
sbc-name
|
Specifies the name of the SBC service.
|
Command Default
No default behavior or values
Command Modes
Privileged EXEC (#)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.4
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Usage Guidelines
These options can not be configured on an option profile.
Examples
The following example shows how the show sbc sbe sip essential-options command is used to display a list of all essential methods:
Router# show sbc test sbe sip essential-options
show sbc sbe sip fast-register-stats
To show how many subscribers have been afforded fast register status by the application, use the show sbc sbe sip fast-register-stats command in Privileged EXEC mode.
show sbc sbc-name sbe sip fast-register-stats
Syntax Description
sbc-name
|
Specifies the name of the SBC service.
|
Command Default
No default behavior or values
Command Modes
Privileged EXEC (#)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.4
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Usage Guidelines
A register message in the context of this command is counted as a unique combination of the pair of address-of-record (AOR) and Contact-URI (CURI). Thus, a single REGISTER message from the subscriber, identified by an AOR with two contact URI will translate to a count of 2.
Examples
The following example shows how the show sbc sbe sip essential-options command is used to display a list of all essential methods:
Router# show sbc mysbc sbe sip fast-register-stats
SIP fast register statistics:
show sbc sbe sip header-profile
To display all SIP header profiles or to show details for a specified header profile, use the show sbc sbe sip header-profile command in Privileged EXEC mode.
show sbc sbc-name sbe sip header-profile [profile-name]
Syntax Description
sbc-name
|
Specifies the name of the SBC service.
|
profile-name
|
Optional. Specifies the name of the profile and displays details about the specified profile.
If omitted, the command shows information about all SIP header profiles.
|
Command Default
No default behavior or values
Command Modes
Privileged EXEC (#)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.4
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Cisco IOS XE Release 2.5
|
The profile-name argument was changed from required to optional. The ability to list all SIP header profiles was added.
|
Examples
The following example shows how the show sbc sbe sip header-profile command is used to display details of the specified header profile:
Router# show sbc test sbe sip header-profile default
Header profile ''default''
The following example shows how the show sbc sbe sip header-profile command is used to display a list of all configured header profiles:
Router# show sbc mySbc sbe sip header-profile
Header profile for SBC service "mysbc"
====================================
show sbc sbe sip header-profiles
To display a list of all configured SIP header profiles, use the show sbc sbe sip header-profiles command in Privileged EXEC mode.
show sbc sbc-name sbe sip header-profiles
Syntax Description
sbc-name
|
Specifies the name of the SBC service.
|
Command Default
No default behavior or values
Command Modes
Privileged EXEC (#)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.4
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Cisco IOS XE Release 2.5
|
This command was deprecated. Its functionality was added to the show sbc sbe sip header-profile command.
|
Examples
The following example shows how the show sbc sbe sip header-profiles command is used to display a list of all configured header profiles:
Router# show sbc mySbc sbe sip header-profiles
Header profile for SBC service "mysbc"
====================================
Related Commands
Command
|
Description
|
show sbc sbe sip header-profile
|
Displays details of the specified SIP header profile.
|
show sbc sbe sip ip-fqdn-mapping
To display the IP-FQDN mapping table, use the show sbc sbe sip ip-fqdn-mapping command in the privileged EXEC mode.
show sbc sbc-name sbe sip ip-fqdn-mapping
Syntax Description
sbc-name
|
Specifies the name of the SBC service.
|
Command Default
No default behavior or values
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.5
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Examples
The following example shows the IP-FQDN mappings that are configured on SBEs:
Router# show sbc test sbe sip ip-fqdn-mapping
IP FQDN mappings for SBC service "test"
1 Yes 11.22.33.41 <-> example.sbc1.com
* -> = one-way, <-> = both-ways
The "Up?" column in the output shows whether an entry is active or inactive. Inactive entries are often caused by mappings that clash with each other.
show sbc sbe sip method-profile
To display all SIP method profiles or to show details for a specified method profile, use the show sbc sbe sip method-profile command in Privileged EXEC mode.
show sbc sbc-name sbe sip method-profile [prof-name]
Syntax Description
sbc-name
|
Specifies the name of the SBC service.
|
prof-name
|
Optional. Name of profile. If omitted, the command shows information about all profiles.
|
Defaults
No default behavior or values
Command Modes
Privileged EXEC (#)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.4
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Cisco IOS XE Release 2.5
|
The prof-name argument was changed from required to optional. The ability to list all SIP method profiles was added.
|
Examples
The following example shows how the show sbc sbe sip method-profile command is used to display a specific method profile:
Router# show sbc test sbe sip method-profile method2
Method profile ''method2''
The following example shows how the show sbc sbe sip method-profile command is used to display a list of all configured method profiles:
Router# show sbc mySbc sbe sip method-profile
Method profile for SBC service "mysbc"
====================================
show sbc sbe sip method-profiles
This command was deprecated in Cisco IOS XE Release 2.5.
To display a list of all SIP method profiles, use the show sbc sbe sip method-profiles command in Privileged EXEC mode.
show sbc sbc-name sbe sip method-profiles
Syntax Description
sbc-name
|
Specifies the name of the SBC service.
|
Defaults
No default behavior or values
Command Modes
Privileged EXEC (#)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.4
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Cisco IOS XE Release 2.5
|
This command was deprecated. Its functionality was added to the show sbc sbe sip method-profile command.
|
Examples
The following example shows how the show sbc sbe sip method-profiles command is used to display a list of all configured method profiles:
Router# show sbc mySbc sbe sip method-profiles
Method profile for SBC service "mysbc"
====================================
Related Commands
Command
|
Description
|
show sbc sbe sip method-profile
|
Displays details of the specified SIP method profile.
|
show sbc sbe sip method-stats
To show the summary or detailed statistics for a SIP method, use the show sbc sbe sip method-stats command in Privileged EXEC mode.
Note
This command name was changed slightly in Cisco IOS XE Release 2.5.
show sbc sbc-name sbe sip method-stats adj-name sip-req-name sip-response-code
summery-period
Syntax Description
sbc-name
|
Specifies the name of the SBC service.
|
adj-name
|
Specifies the name of the adjacency.
|
sip-req-name
|
Specifies the request name: ACK BYE CANCEL INFO INVITE MESSAGE NOTIFY OPTIONS PRACK REFER REGISTER SUBSCRIBE UNKNOWN UPDATE
|
sip-response-code
|
100-999
|
summery-period
|
Values you can enter are current5mins, current15mins, currenthour, currentday, previous5mins, previous15mins, previoushour, or previousday.
|
Command Default
No default behavior or values
Command Modes
Privileged EXEC (#)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.4.1
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Cisco IOS XE Release 2.5
|
This command name was changed from show sbc sbe sip-method-stats to show sbc sbe sip method-stats (the hyphen between sip and method was removed).
|
Usage Guidelines
The statistics-setting command must be configured before using the show sbc sbe sip method-stats command to display SIP method statistics.
•
Use the statistics-setting summary command to allow the show sbc sbe sip method-stats command to display statistics about SIP request names only.
•
Use the statistics-setting detail command to allow the show sbc sbe sip method-stats command to display statistics about SIP response codes and SIP request names.
Summary statistics display all the response codes sent and received for a specific SIP method.
Detailed statistics display the statistics for specific SIP method and response code. You must use the sip-response-code string to view detailed statistics.
Examples
The following example shows how the show sbc sbe sip method-stats command is used to display summary statistics for a specific SIP method. The statistics-setting summary command was configured on the adjacency before executing the show sbc sbe sip method-stats command.
Router# show sbc sbc sbe sip method-stats sip-41 invite currenthour
Statistics for SIP method INVITE
Total request recieved :3
Total 1xx response received :0
Total 1xx response sent :3
Total 2xx response received :0
Total 2xx response sent :0
Total 3xx response received :0
Total 3xx response sent :0
Total 4xx response received :0
Total 4xx response sent :0
Total 5xx response received :0
Total 5xx response sent :0
Total 6xx response received :0
Total 6xx response sent :3
Other response received :0
The following example shows how the show sbc sbe sip method-stats command is used to display detailed statistics for a specific SIP method. The statistics-setting detail command was configured on the adjacency before executing the show sbc sbe sip method-stats command.
Router# show sbc sbc sbe sip method-stats sip-41 invite 604 currenthour
Statistics for SIP method INVITE ,response 604
The following example shows that the statistics-setting detail command was not configured on the adjacency before executing the show sbc sbe sip method-stats command:
Router# show sbc sbc sbe sip method-stats sip-41 invite 604 currenthour
Statistics not available.
Set adjacency statistics-setting to detail to enable detailed statistics
Related Commands
Command
|
Description
|
clear sbc sbe adjacency statistics
|
Clears the SIP method statistics counters and resets them to zero.
|
show sbc sbe adjacencies
|
Lists the adjacencies configured on signaling border elements (SBEs).
|
show sbc sbe sip option-profiles
|
Displays a list of all configured SIP option profiles.
|
statistics-setting
|
Configures an adjacency to support SIP method statistics.
|
show sbc sbe sip option-profile
To display all SIP option profiles or to show details for a specified option profile, use the show sbc sbe sip option-profile command in Privileged EXEC mode.
show sbc sbc-name sbe sip option-profile [profile-name]
Syntax Description
sbc-name
|
Specifies the name of the SBC service.
|
profile-name
|
Optional. Specifies the name of the profile. If omitted, the command shows information about all SIP option profiles.
|
Command Default
No default behavior or values
Command Modes
Privileged EXEC (#)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.4
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Cisco IOS XE Release 2.5
|
The profile-name argument was changed from required to optional. The ability to list all SIP option profiles was added.
|
Examples
The following example shows how the show sbc sbe sip option-profile command is used to display details of the specified option profile:
Router# show sbc test sbe sip option-profile profile1
Option profile ''profile1''
Adjacency: sip-60 (in-px)
Router# show sbc test sbe sip option-profile profile2
Option profile ''profile2''
Not in use with any adjacencies
The following example shows how the show sbc sbe sip option-profile command is used to display details of the specified header profile:
Router# show sbc test sbe sip option-profile
Option profiles for SBC service "test":
===================================================
default Default profile Yes
show sbc sbe sip option-profiles
This command was deprecated in Cisco IOS XE Release 2.5.
To display a summary of the configured option profiles, use the show sbc sbe sip option-profiles command in Privileged EXEC mode.
show sbc sbc-name sbe sip option-profiles
Syntax Description
sbc-name
|
Specifies the name of the SBC service.
|
profile-name
|
Specifies the name of the profile.
|
Command Default
No default behavior or values
Command Modes
Privileged EXEC (#)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.4
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Cisco IOS XE Release 2.5
|
This command was deprecated. Its functionality was added to the show sbc sbe sip option-profile command.
|
Examples
The following example shows how the show sbc sbe sip option-profiles command is used to display details of the specified header profile:
Router# show sbc test sbe sip option-profiles
Option profiles for SBC service "test":
===================================================
default Default profile Yes
Related Commands
Command
|
Description
|
show sbc sbe sip option-profile
|
Displays a specified option profile.
|
show sbc sbe sip sdp-match-table
To show the SDP match table configured on the SBC, use the show sbc sbe sip sdp-match-table command in Privileged EXEC mode.
show sbc sbc-name sbe sip sdp-match-table [detail]
Syntax Description
sbc-name
|
Specifies the name of the SBC service.
|
detail
|
Shows the SDP attribute configured on a given SDP match table.
|
Command Default
No default behavior or values
Command Modes
Privileged EXEC (#)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.5
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Examples
The following example shows how the show sbc sbe sip sdp-match-table command is used to display SDP match table:
Router# show sbc pgw sbe sip sdp-match-table detail
Action : blacklist <--- action: blacklist or whitelist
Match String : ddd <--- several match string
-------------------------------------------------
Related Commands
Command
|
Description
|
show sbc sbe sdp-h245-mapping
|
Displays the mapping for codec strings between SDP (SIP) and H245 (H323).
|
show sbc sbe sip sdp-media-profile
To show all SDP media profiles in an SBC service or details for a specified profile, use the show sbc sbe sip sdp-media-profile command in Privileged EXEC mode.
show sbc sbc-name sbe sip sdp-media-profile [profile-name]
Syntax Description
sbc-name
|
Specifies the name of the SBC service.
|
profile-name
|
Specifies the name of the profile. If omitted, the command lists all profiles in the SBC service.
|
Command Default
No default behavior or values
Command Modes
Privileged EXEC (#)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.5
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Examples
The following example shows a list of SDP media profiles configured under an SBC:
Router#show sbc test sbe sip sdp-media-profile
SDP Media profiles for SBC service "test"
====================================
The following example shows the contents of a named SDP media profile:
Router#show sbc test sbe sip sdp-media-profile MediaProfile
SDP media profile "MediaProfile"
Line 1 : m=audio 0 RTP/AVP 31
Not in use by any CAC table entries
Related Commands
Command
|
Description
|
sdp-media-profile
|
Creates or modifies a customized SDP media profile.
|
show sbc sbe sip sdp-policy-table
To show the SDP policy table configured on the SBC, use the show sbc sbe sip sdp-policy-table command in Privileged EXEC mode.
show sbc sbc-name sbe sip sdp-policy-table
Syntax Description
sbc-name
|
Specifies the name of the SBC service.
|
Command Default
No default behavior or values
Command Modes
Privileged EXEC (#)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.5
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Examples
The following example shows how the show sbc sbe sip sdp-policy-table command is used to display the SDP policy table:
Router# show sbc pgw sbe sip sdp-policy-table
--------------------------------------------------
p m <--- "m" is sdp match table name
Related Commands
Command
|
Description
|
show sbc sbe sip sdp-match-table
|
Shows the SDP match table configured on the SBC.
|
show sbc sbe sip statistics
To display the aggregated SIP statistics handled by the Cisco Unified Border Element (SP Edition) process on the Cisco ASR 1000 Series Routers, use the show sbc sbe sip statistics command in Privileged EXEC mode.
show sbc {service name} sbe sip statistics
Syntax Description
service name
|
Specifies the name of the Session Border Controller (SBC) service.
|
Defaults
No default behavior or values
Command Modes
Privileged EXEC (#)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.4.1
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Usage Guidelines
Examples
The following example shows the aggregated SIP statistics handled by the Cisco Unified Border Element (SP Edition) process on the Cisco ASR 1000 Series Routers:
Router# show sbc global sbe sip statistics
Total SIP Transactions: 6
SIP Client Errors (4xx) 0 0
SIP Server Errors (5xx) 0 0
SIP Global Errors (6xx) 0 0
Internally Generated SIP Response Classes:
SIP Client Errors (4xx) 0
SIP Server Errors (5xx) 0
SIP Global Errors (6xx) 0
Transaction Manager (TM) Internal Statistics:
Request/Response Congestion Failures = 0
Current Transactions awaiting response = 0
Free Buffers in TM inbound pool = 1200
Free Buffers in TM outbound pool = 20000
TM Congestion Level (uncongested = 0) = 0
Congestion Queue - Packets Accepted = 0
Congestion Queue - Packets Rejected = 0
Congestion Queue - Length = 0
Congestion Queue - Time Since Reset(ms)= 904270
Congestion Queue - Oldest Pkt Age (ms) = 0
Congestion Queue - Max Pkt Delay (ms) = 0
Control Block (CB) utilization:
Server Location NAPTR CBs = 0
Server Location SRV CBs = 0
Server Location address CBs = 2
Server Location Cache CBs = 0
Server Location Alias CBs = 0
Proxy Proto Dialog CBs = 0
Proxy Server Transaction CBs = 0
Proxy Client Transaction CBs = 0
Table 14 show sbc sbe sip statistics Field Descriptions
Field
|
Description
|
In
|
Counts of messages that have been received by the endpoints. These are messages received in the SBC by the Cisco IOS task running on the route processor.
|
Out
|
Counts of messages sent out of the SBC. The message count is an aggregation of the messages internally generated and generated in response to an external event.
|
SIP Request Messages
|
In and Out message counts of the Request classes for the SIP messages. Request classes are: SIP INVITES, SIP ACKs, SIP BYEs, SIP CANCELs, SIP OPTIONS, SIP REGISTERs, SIP SUBSCRIBEs, SIP REFERs, and SIP NOTIFY.
|
SIP Response Classes
|
In and Out message counts of the Response classes for the SIP messages. Response classes are: SIP Info, SIP Success, SIP Redirects, SIP Client Errors, SIP Server Errors, and SIP Global Errors.
|
Internally Generated SIP Response Classes
|
In and Out message counts generated by the SBC due to a decision that is outside the normal call flow.
|
Transaction Manager (TM) Internal Statistics
|
Describes statistics of the state of the dynamic message handling.
|
Control Block (CB) utilization
|
Count of the memory usage of the control blocks.
|
Related Commands
Command
|
Description
|
clear sbc sbe sip statistics
|
Clears aggregated SIP statistics handled by the Cisco Unified Border Element (SP Edition).
|
show sbc sbe sip subscribers
To display details of all SIP endpoints that have registered with the SBC, use the show sbc sbe sip subscribers command in Privileged EXEC mode.
show sbc sbc-name sbe sip subscribers [filter prefix] [adjacency adj-name] [delegate]
Syntax Description
sbc-name
|
Specifies the name of the SBC service.
|
filter prefix
|
Match only subscribers whose address-of-record starts with the specified prefix.
|
adjacency adj-name
|
Match only subscribers registered on this adjacency.
|
delegate
|
Display subscribers that have provisioned delegate registration configured, and the associated Uniform Resource Identifier (URI) contact information for the subscribers.
|
Command Default
No default behavior or values
Command Modes
Privileged EXEC (#)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.4
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Examples
The following example shows how the show sbc sbe sip subscribers command is used to display details of the SIP endpoints that have registered with the SBC:
Router# show sbc node2 sbe sip subscribers
AOR: sip:4082230000@amd-ua3.amd.com
Subscriber location: sip:4082230000@103.2.192.1:5060;transport=UDP
SIP URI : sip:4082230000@102.102.102.45:5060
AOR: sip:4082220000@amd-ua2.amd.com
Subscriber location: sip:4082220000@103.2.128.1:5060;transport=UDP
SIP URI : sip:4082220000@102.102.102.45:5060
The following show example displays subscribers for which delegate registration have been configured. The delegate keyword displays the associated URI contact information for subscribers.
Router# show sbc mySBC sbe sip subscribers delegate
012345789012345789012345789012345789012345789012345789012345789012345789
AOR: sip:steve1.cisco.com
Subscriber Location[s]: sip:contact@cisco.com -> CallMgrC
sip:contact2@cisco.com -> CallMgrD
Registrar: sip:myreg@172.18.52.148
show sbc sbe sip timers
To show the current configuration of SIP-related timers, use the show sbc sbe sip timers command in Privileged EXEC mode.
show sbc service-name sbe sip timers
Syntax Description
service-name
|
Specifies the name of the SBC.
|
Command Default
No default behavior or values
Command Modes
Privileged EXEC (#)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.4
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Examples
The following example shows how to list the configurations of SIP-related timers:
Router# show sbc test sbe sip timers
TCP connect timeout: 0 ms
TCP idle timeout: 120000 ms
TLS idle timeout: 3600000 ms
UDP first retransmit interval: 500 ms
UDP max retransmit interval: 4000 ms
UDP response linger period: 5000 ms
show sbc services
To display lists all of the SBC services on the chassis, use the show sbc services command in Privileged EXEC mode.
show sbc services
Syntax Description
This command has no arguments or keywords.
Command Default
No default behavior or values
Command Modes
Privileged EXEC (#)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.4
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Usage Guidelines
Lists the high-level status and capabilities of each instantiated SBE or DBE.
Examples
The following example shows how the show sbc services command is used to display lists of all the SBC services on the chassis.
Router# show sbc mysbc services
H.248 media gateway control (MGC)
signaling-address ipv4
To define the local IPv4 signaling address of an H.323 or SIP adjacency, use the signaling-address ipv4 command in the appropriate configuration mode. To return to the default behavior, use the no form of this command.
signaling-address ipv4 ipv4_IP_address
no signaling-address
Syntax Description
ipv4_IP_address
|
Specifies the IPv4 address for the signaling address of the SIP or H.323 adjacency.
|
Defaults
No default behavior or values
Command Modes
Adjacency H.323 configuration (config-sbc-sbe-adj-h323)
Adjacency SIP configuration (config-sbc-sbe-adj-sip)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.4
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Usage Guidelines
To use this command, you must be in the correct configuration mode and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
When defined, the SBE listens on this address for inbound call signaling from the adjacency. If two adjacencies share the same signaling address, a different remote domain name must be specified for each one.
Examples
The following example shows how to configure the H.323 adjacency h323ToIsp42 to listen on signaling address 10.1.0.2:
Router# configure terminal
Router(config)# sbc mySbc
Router(config-sbc-sbe)# adjacency h323 h323ToIsp42
Router(config-sbc-sbe-adj-h323)# signaling-address ipv4 10.1.0.2
The following example shows how to configure the SIP adjacency adjSip1 to listen on signaling address 10.10.10.10:
Router# configure terminal
Router(config)# sbc mySbc
Router(config-sbc-sbe)# adjacency sip adjSip1
Router(config-sbc-sbe-adj-sip)# signaling-address ipv4 10.10.10.10
signaling-peer
To configure an H.323 or SIP adjacency to use the given remote signaling-peer, use the signaling-peer command in the appropriate configuration mode. To remove this configuration, use the no form of this command.
signaling-peer gk peer-name
no signaling-peer
Syntax Description
peer-name
|
Specifies the IPv4 address in dotted decimal format.
|
gk
|
Specifies the H.323 gatekeeper.
|
Defaults
No default behavior or values
Command Modes
Adjacency H.323 configuration (config-sbc-sbe-adj-h323)
Adjacency SIP configuration (config-sbc-sbe-adj-sip)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.4
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Usage Guidelines
To use this command, you must be in the correct configuration mode and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
Examples
The following example shows how to configure the H.323 adjacency h323ToIsp42 to use gatekeeper andrew:
Router# configure terminal
Router(config)# sbc mySbc
Router(config-sbc-sbe)# adjacency h323 h323ToIsp42
Router(config-sbc-sbe-adj-h323)# signaling-peer gk andrew
Note
You can use the signaling-peer command to configure the SIP adjacency using the IP address or the host name of the given remote signaling-peer.
The following example shows how to configure SIP adjacency using the IP address of the given remote signaling-peer:
Router# configure terminal
Router(config)# sbc mySbc
Router(config-sbc-sbe)# adjacency sip adjSip1
Router(config-sbc-sbe-adj-sip)# signaling-peer 10.1.2.3
The following example shows how to configure SIP adjacency using the hostname of the given remote signaling-peer:
Router# configure terminal
Router(config)# sbc mySbc
Router(config-sbc-sbe)# adjacency sip SipToIsp42
Router(config-sbc-sbe-adj-sip)# signaling-peer athene
Related Commands
Command
|
Description
|
signaling-peer-port
|
Configures an H.323 or SIP adjacency to use the given remote signaling-peer's port.
|
signaling-peer-port
To configure an H.323 or SIP adjacency to use the given remote signaling-peer's port, use the signaling-peer-port command in the appropriate configuration mode. To remove this configuration, use the no form of this command.
signaling-peer-port port-num
no signaling-peer-port
Syntax Description
port-num
|
Specifies the number of the signaling port. Range is 1 to 65535.
|
Defaults
By default, this command assumes that port-num is 5060.
Command Modes
Adjacency H.323 configuration (config-sbc-sbe-adj-h323)
Adjacency SIP configuration (config-sbc-sbe-adj-sip)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.4
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Usage Guidelines
To use this command, you must be in the correct configuration mode and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
Examples
The following example shows how to configure the H.323 adjacency h323ToIsp42 to use port 123 on the signaling peer:
Router# configure terminal
Router(config)# sbc mySbc
Router(config-sbc-sbe)# adjacency h323 h323ToIsp42
Router(config-sbc-sbe-adj-h323)# signaling-peer-port 123
The following example shows how to configure the SIP adjacency SipToIsp42 to port 123 as the signaling peer's port:
Router# configure terminal
Router(config)# sbc mySbc
Router(config-sbc-sbe)# adjacency sip SipToIsp42
Router(config-sbc-sbe-adj-sip)# signaling-peer-port 123
signaling-port
To define the local port of signaling address of an H.323 or SIP adjacency, use the signaling-port command in the appropriate configuration mode. To return to the default value, use the no form of this command.
signaling-port port-num [max-port-num]
no signaling-port
Syntax Description
port-num
|
Required for both H.323 and SIP adjacencies. Specifies the number of the signaling peer. Range is 1 to 65535.
|
max-port-num
|
Optional for SIP adjacencies. Specifies the maximum port number of the range (the upper boundary of the range) of local listen ports for the adjacency. Range is from 1 through 65535.
Configure both port-num and max-port-num if you want a range of local listen ports for a SIP adjacency.
max-port-num should not be specified if this is an IPsec-enabled adjacency.
|
Defaults
port-num is 5060.
Command Modes
Adjacency H.323 configuration (config-sbc-sbe-adj-h323)
Adjacency SIP configuration (config-sbc-sbe-adj-sip)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.4
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Cisco IOS XE Release 2.5
|
The max-port-num argument was added for SIP adjacencies.
|
Usage Guidelines
The SBE will listen on this port for inbound call signaling from the adjacency. The port will also be appended to the SBE's contact header on outbound SIP requests and responses.
If both port-num and max-port-num are specified, then the port-num indicates the lower boundary of the range and max-port-num indicates the upper boundary of the range. If no max-port-num is specified, then the adjacency listens only on the single port-num. Max-port-num only needs to be set if a range of local listen ports is required for this adjacency.
For the Contact Username Passthrough feature for non-IMS networks—the signaling-port command configures a range of valid signaling ports (on the same registrar-facing SIP adjacency where the registration contact username passthrough command was configured) to allow the SBC to disambiguate subscribers that register from different devices with the same username.
The port-num and max-port-num cannot be changed while the adjacency is active.
The number of ports in the range (max-port-num - port-num + 1) must be less than or equal to 10. Also max-num-port should not be specified if this is an IPsec-enabled adjacency.
Examples
The following example shows how to configure the SIP adjacency SipToIsp42 to listen on signaling port 5000:
Router# configure terminal
Router(config)# sbc mySbc
Router(config-sbc-sbe)# adjacency sip SipToIsp42
Router(config-sbc-sbe-adj-sip)# signaling-port 5000
The following is an example showing that a signaling port range of 5060 to 5062 (3 local ports) is configured for a SIP adjacency where registration contact username passthrough is configured:
inherit profile preset-core
signaling-address ipv4 192.168.101.1
statistics-setting summary
remote-address ipv4 192.168.101.12 255.255.255.255
signaling-peer 192.168.101.12
registration target address 192.168.101.12
registration target port 7069
registration contact username passthrough
Related Commands
Command
|
Description
|
signaling-address ipv4
|
Configures a SIP adjacency to use the given remote signaling-peer.
|
registration contact username
|
Specifies if the contact username in a SIP REGISTER request is passed through unchanged
|
sip dns
To enter the SIP DNS configuration mode, use the sip dns command in the SBE configuration mode. To exit this mode, use the exit command.
sip dns
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
SBE configuration (config-sbc-sbe)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.4
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Usage Guidelines
To use this command, you must be in the correct configuration mode and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
Examples
The following example shows how to configure limits on DNS entries:
Router# configure terminal
Router(config)# sbc mySbc
Router(config-sbc-sbe)# sip dns
Related Commands
Command
|
Description
|
cache-lifetime
|
Configures the lifetime of any DNS entry.
|
cache-limit
|
Configures the maximum number of entries that are permitted in the DNS cache.
|
sip adjacency
To configure a SIP adjacency for a Session Border Controller (SBC) service, use the sip adjacency command in the SBE configuration mode. To deconfigure the SIP adjacency, use the no form of this command.
sip adjacency adjacency-name
no sip adjacency adjacency-name
Syntax Description
adjacency-name
|
Specifies the name of the SIP adjacency.
|
Defaults
No default behavior or values.
Command Modes
SBE configuration (config-sbc-sbe)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.4
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Usage Guidelines
Examples
The following example shows how to configure a SIP adjacency named sipGW:
Router# configure terminal
Router(config)# sbc mySbc
Router(config-sbc-sbe)# sip adjacency sipGW
Related Commands
Command
|
Description
|
adjacency
|
Configures a H.323 adjacency.
|
sip-contact
To configure the SIP contact information for a specified Uniform Resource Identifier (URI) for a delegate subscriber, use the sip-contact command in subscriber-entry configuration mode. To remove the SIP contact information for an URI for a delegate subscriber, use the no sip-contact command.
sip-contact {uri}
no sip-contact {uri}
Syntax Description
uri
|
This is the Uniform Resource Identifier (URI) of the delegate subscriber for whom you want to configure Provisioned Delegate Registration.
It is an IP address. It is a string field of 62 characters maximum length.
|
Command Default
No default behavior or values
Command Modes
subscriber-entry configuration (config-sbc-sbe-subscriber-entry)#
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.4
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Usage Guidelines
This command configures the SIP contact information for a specified URI IP address location or address of record. The contact information is used to provision the SBC with client device information, so the SBC can register the device.
A delegate subscriber must have one or more SIP contacts or Uniform Resource Identifiers (URIs) associated with it. For every delegate registration configured with the delegate-registration hostname command, one or more SIP contacts/URIs must be configured in the SIP Contacts table (amb_mw_sudb_local_id). After a SIP contact is configured, the client adjacency is also defined in a subsequent step.
The following rules apply to configuring SIP contact information:
•
The subscriber detail table must exist before contacts can be created.
•
Contacts in a currently active subscriber cannot be created, modified, or deleted.
•
A contact cannot be deactivated while the parent subscriber is active.
Examples
The following example configures a SIP contact information for a subscriber, for whom a subscriber detail table exists, and for whom, after the SIP contact is configured, delegate registration can be configured:
subscriber sip:bob@isp.example
sip-contact sip:steve@10.1.1.2
The following example configures a SIP contact information for a delegate subscriber at the address of record, where aor= sip:bob@isp.example, and configures delegate registration for the subscriber:
(config-sbc-sbe)# subscriber sip:bob@isp.example
(config-sbc-sbe-subscriber-entry)# sip-contact sip:steve@10.1.1.2
(config-sbc-sbe-subscriber-contact)# adjacency CallMgrB
(config-sbc-sbe-subscriber-contact)# exit
(config-sbc-sbe-subscriber-entry)# delegate-registration sip:registrar@1.1.1.1
(config-sbc-sbe-subscriber-delegate)# adjacency CallMgrA
(config-sbc-sbe-subscriber-delegate)# profile my-profile
(config-sbc-sbe-subscriber-delegate)# activate
Related Commands
Command
|
Description
|
subscriber
|
Defines a unique subscriber for whom you want to configure Provisioned Delegate Registration.
|
delegate-profile
|
Configures a delegate registration profile that is applied to a delegate registration subscriber.
|
delegate-registration
|
Configures a delegate registration for a delegate client.
|
adjacency
|
Configures the adjacency facing the registrar.
|
profile
|
Applies a delegate registration profile to a delegate registration subscriber.
|
show sbc sbe sip delegate-profile
|
Displays subscriber profiles for whom Provisioned Delegate Registration has been configured.
|
show sbc sbe sip subscribers
|
Displays subscribers for whom Provisioned Delegate Registration has been provisioned.
|
sip encryption key
To configure a global encryption key on a SIP Interconnection Border Control Function (IBCF) adjacency, use the sip encryption key command in the SIP adjacency mode. To deconfigure the global encryption key, use the no form of this command.
sip encryption key key
no sip encryption key key
Syntax Description
key
|
Specifies the encryption key.
|
Defaults
No default behavior or values.
Command Modes
Adjacency SIP configuration (config-sbc-sbe-adj-sip)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.4
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Usage Guidelines
To use this command, you must be in the correct configuration mode and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
Examples
The following example shows how the sip encryption key command is used to configure a global encryption key on a SIP IBCF adjacency:
Router# configure terminal
Router(config)# sbc mySbc
Router(config-sbc-sbe)# adjacency sip SipToIsp42
Router(config-sbe-adj-sip)# encryption key mykey
Related Commands
Command
|
Description
|
sip inherit profile
|
Configures a global inherit profile in the SIP adjacency mode.
|
sip header-profile
To configure a header profile in the mode of an SBE entity, use the sip header-profile command in SBE configuration mode. To remove the method profile, use the no form of this command.
sip header-profile profile-name
no sip method-profile
Syntax Description
profile-name
|
Specifies the name of the method profile. If you enter the name default, the default profile is configured.
|
Command Default
No default behavior or values
Command Modes
SBE configuration (config-sbc-sbe)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.4
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Usage Guidelines
To use this command, you must be in the correct configuration mode and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
Examples
The following example shows how the sip header-profile command configures a method profile with the name of test1:
Router# configure terminal
Router(config)# sbc mysbc
Router(config-sbc-sbe)# sip header-profile test1
sip home network identifier
To configure a home network identifier on all IBCF adjacencies, use the sip home network identifier command in the SBE configuration mode. To deconfigure the home network identifier, use the no form of this command.
sip home network identifier network-name
no sip home network identifier
Syntax Description
network-name
|
Specifies the name of the home network identifier.
|
Defaults
No default behavior or values
Command Modes
SBE configuration (config-sbc-sbe)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.4
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Usage Guidelines
To use this command, you must be in the correct configuration mode and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
Examples
The following example shows how the home network identifier command is used to configure a home network identifier on all IBCF adjacencies:
Router# configure terminal
Router(config)# sbc mySbc
Router(config-sbc-sbe)# sip home network identifier myhome.com
Related Commands
Command
|
Description
|
sip visited network identifier
|
Configures a visited network identifier on a SIP Proxy-Call Session Control Function (P-CSCF) adjacency.
|
sip hunting-trigger
To configure failure return codes to trigger hunting in SBE configuration mode, use the sip hunting-trigger command in SBE configuration mode.
The no form of the command clears all error codes.
If you specify no sip hunting-trigger x y, then just codes x and y are removed from the configured list.
sip hunting-trigger {error-codes | disable} error-codes
no sip hunting-trigger {error-codes | disable} error-codes
Syntax Description
error-codes
|
Signifies a space-separated list of SIP numeric error codes.
|
Defaults
No default behavior or values
Command Modes
SBE configuration (config-sbc-sbe)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.4
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Usage Guidelines
If you enter sip hunting-trigger x followed by sip hunting-trigger y, the value of x is replaced with y.
To set both x and y to be hunting triggers, you must enter sip hunting-trigger x y.
The related command hunting-trigger is used to configure failure return codes to trigger hunting in H.323 (global H.323 scope), adjacency SIP (destination SIP adjacency), and adjacency h323 (destination H.323 adjacency) modes. The hunting-trigger command does not apply in global SIP mode; instead the sip hunting-trigger command is used in global SIP mode.
Examples
The following example shows how to configure SIP to retry routing if it receives a 415 (media unsupported) or 480 (temporarily unavailable) error:
Router# configure terminal
Router(config)# sbc mySbc
Router (config-sbc-sbe)# sip hunting-trigger 416 480
Related Commands
Command
|
Description
|
show sbc sbe hunting-trigger
|
Shows the H.323 or SIP hunting triggers at the global level.
|
sip ip-fqdn-mapping
To configure SIP IP-to-FQDN mapping on signaling border elements (SBEs), use the sip ip-fqdn-mapping command in the SBE configuration submode.
sip ip-fqdn-mapping index ipv4 ip-address fqdn {both-ways | ip-to-fqdn}
Syntax Description
index
|
Index number that uniquely identifies this mapping
|
ip-address
|
Specifies the IPv4 address for the signaling address of the SIP
|
fqdn
|
Fully qualified domain name
|
both-ways
|
Both ways mapping between IP address and FQDN
|
ip-to-fqdn
|
Only maps IP address to FQDN
|
Defaults
No default behavior or values
Command Modes
SBE configuration (config-sbc-sbe)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.5
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Usage Guidelines
To use this command, you must be in the correct configuration mode and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
Examples
The following example shows how to configure the both ways mapping between IP and FQDN:
Enter configuration commands, one per line. End with CNTL/Z.
Router(config-sbc-sbe)# sip ip-fqdn-mapping 1 ipv4 11.22.33.41 example.sbc1.com both-ways
The following example shows how to configure the one way IP-to-FQDN mapping:
Enter configuration commands, one per line. End with CNTL/Z.
Router(config-sbc-sbe)# sip ip-fqdn-mapping 2 ipv4 11.22.33.44 example2.sbc1.com
ip-to-fqdn
sip inherit profile
To configure a global inherit profile, use the sip inherit profile command in adjacency SIP configuration mode. To deconfigure the global inherit profile, use the no form of this command.
sip inherit profile {preset-access | preset-core | preset-ibcf-ext-untrusted | preset-ibcf-external
| preset-ibcf-internal | preset-p-cscf-access | preset-p-cscf-core | preset-peering |
preset-standard-non-ims}
no sip inherit profile
Syntax Description
preset-access
|
Specifies a preset access profile.
|
preset-core
|
Specifies a preset core profile.
|
preset-ibcf-ext-untrusted
|
Specifies a preset IBCF external untrusted profile.
|
preset-ibcf-external
|
Specifies a preset IBCF external profile.
|
preset-ibcf-internal
|
Specifies a preset IBCF internal profile.
|
preset-p-cscf-access
|
Specifies a preset P-CSCF-access profile.
|
preset-p-cscf-core
|
Specifies a preset P-CSCF-core profile.
|
preset-peering
|
Specifies a preset peering profile.
|
preset-standard-non-ims
|
Specified a preset standard-non-IMS profile.
|
Defaults
No default behavior or values
Command Modes
Adjacency SIP configuration (config-sbc-sbe-adj-sip)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.4
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Usage Guidelines
To use this command, you must be in the correct configuration mode and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
Examples
The following example shows how the sip inherit profile command is used to configure a P-CSCF-access inherit profile on a SIP adjacency:
Router# configure terminal
Router(config)# sbc mySbc
Router(config-sbc-sbe)# adjacency sip SipToIsp42
Router(config-sbe-adj-sip)# sip inherit profile preset-p-cscf-access
Related Commands
Command
|
Description
|
sip timer
|
Enters the mode of a SIP timer function.
|
sip max-connections
To configure the maximum number of SIP connections that will be made to each remote address, use the sip max-channels command in SBE configuration mode. To set this to an unlimited number of connections, use the no form of this command.
sip max-connections number-of-connections
no sip max-connections number-of-connections
Syntax Description
number-of-connections
|
The maximum number of connections.
|
Defaults
No default behavior or values
Command Modes
SBE configuration (config-sbc-sbe)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.4
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Usage Guidelines
To use this command, you must be in the correct configuration mode and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
Examples
The following command configures the maximum number of connections to each remote address to 1:
Router(config)# sbc mySbc
Router(config-sbc-sbe)# sip max-connections 1
Related Commands
Command
|
Description
|
max-bandwidth
|
Configures the maximum bandwidth for an entry in an admission control table.
|
max-regs-rate
|
Configures the maximum call number of subscriber registrations for an entry in an admission control table.
|
max-updates
|
Configures the maximum call updates for an entry in an admission control table.
|
sip method-profile
To configure a method profile in the mode of an SBE entity, use the sip method-profile command in SBE configuration mode. To remove the method profile, use the no form of this command.
sip method-profile profile-name
no sip method-profile
Syntax Description
profile-name
|
Specifies the name of the method profile. If you enter the name default, the default profile is configured. This profile is used for all adjacencies that do not have a specific profile configured.
|
Command Default
No default behavior or values
Command Modes
SBE configuration (config-sbc-sbe)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.4
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Usage Guidelines
To use this command, you must be in the correct configuration mode and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
Examples
The following example shows how the sip method-profile command configures a method profile with the name of test1:
Router# configure terminal
Router(config)# sbc mysbc
Router(config-sbc-sbe)# sip method-profile test1
sip option-profile
To configure a option profile in the mode of an SBE entity for a SIP option whitelist or blacklist profile, use the sip option-profile command in SBE configuration mode. To remove the option profile, use the no form of this command.
sip option-profile {profile-name | default}
no sip option-profile {profile-name | default}
Syntax Description
profile name
|
Name of the method profile.
|
default
|
Configures the default option profile.
|
Defaults
No default behavior or values
Command Modes
SBE configuration (config-sbc-sbe)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.4
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Usage Guidelines
To use this command, you must be in the correct configuration mode and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
If a configuration is loaded on top of an active configuration, warnings are generated to notify that the configuration cannot be modified. If you must modify the entire configuration by loading a new one, please remove the existing configuration first.
Use the sip option-profile command to enter SBE SIP option configuration mode.
If you use the default keyword, the default profile is configured. This profile is used for all adjacencies which do not have a specific profile configured.
Examples
The following example shows how to configure a option profile with the name of test1.
Router# configure terminal
Router(config)# sbc mySbc
Router(config-sbc-sbe)# sip method-profile test1
Router(config-sbc-sbe-sip-opt)#
Related Commands
Command
|
Description
|
blacklist
|
Configures SIP header or method blacklist profiles on a Session Initiation Protocol (SIP) message.
|
description
|
Configures the description for the SIP header-profile or SIP method-profile.
|
method
|
Adds a method with a specified name to a SIP message profile.
|
pass-body
|
Permits 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.
|
sip parameter-profile
To configure a parameter profile for a method profile in the mode of an SBE entity, use the sip parameter-profile command in SBE configuration mode. To remove the parameter profile, use the no form of this command.
sip parameter-profile profile-name
no sip parameter-profile profile-name
Syntax Description
profile name
|
Name of the parameter profile.
|
Defaults
No default behavior or values
Command Modes
SBE configuration
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.4
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Usage Guidelines
To use this command, you must be in the correct configuration mode and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
The following example shows how to configure a parameter profile with the name of paramprof1:
Router# configure terminal
Router(config)# sbc mySbc
Router(config-sbc-sbe)# sip parameter-profile paramprof1
Router(config-sbc-sbe-sip-prm)# parameter user
Router(config-sbc-sbe-sip-prm-ele)# action add-not-present value phone
Related Commands
Command
|
Description
|
sip-method profile
|
Configures a method-profile.
|
sip sdp-match-table
To create an SDP match table, use the sip sdp-match-table command in SBE configuration mode. To remove an SDP match table, use the no form of this command.
sip sdp-match-table table_name
no sip sdp-match-table table_name
Syntax Description
table_name
|
The user name to fill in on generated SDPs.
|
Defaults
No default behavior or values
Command Modes
SBE configuration (config-sbc-sbe)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.4
|
The sdp-match-table command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Cisco IOS XE Release 2.5
|
This command was modified to be sip sdp-match-table.
|
Usage Guidelines
One policy can only hold one sdp-match-table.
To use this command, you must be in the correct configuration mode and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
Examples
The following command configures the SDP match table foo:
Router(config)# sbc mySbc
Router(config-sbc-sbe)# sip sdp-match-table foo
Router(config-sbc-sbe-sip)#
Related Commands
Command
|
Description
|
action (sdp)
|
Configures an SDP policy table action.
|
match-string
|
Configure an SDP attribute matching string.
|
sip sdp-policy-table
|
Configure an SDP policy table.
|
sip sdp-media-profile
To create or modify an SDP media profile, or to associate an SDP media profile to a CAC policy, use the sip sdp-media-profile command in SBE configuration mode or in SBE CAC policy CAC table entry mode. Use the no form of the command to remove an SDP media profile.
sip sdp-media-profile profile-name
no sip sdp-media-profile profile-name
Syntax Description
profile-name
|
Name of profile to create or modify.
|
Defaults
The global default is used.
Command Modes
SBE configuration (config-sbc-sbe)
SBE CAC policy CAC table entry (sbc-sbe-cacpolicy-cactable-entry)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.5
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Usage Guidelines
Use the sip sdp-media-profile command to configure media descriptions for customized offers for late-to-early media interworking. After creating an SDP media profile, associate the profile to a signal by adding the profile name to a CAC policy. You can add a maximum of ten entries for each sdp-media-profile.
To use this command, you must be in the correct configuration mode and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
Examples
The following example shows how to create a new SDP profile for customizing media descriptions in late-to-early interworking offers:
Router# configure terminal
Router(config-sbc-sbe)# sip sdp-media-profile MediaProfile
Router(config-sbc-sbe-sip-sdp-media)# entry 1
Router(config-sbc-sbe-sip-sdp-media-ele)# line 1 "m=audio 0 RTP/AVP 31"
Router(config-sbc-sbe-sip-sdp-media-ele)# line 2 "a=aaa:testing"
Router(config-sbc-sbe-sip-sdp-media-ele)# Ctrl Z
The following example associates the profile to an existing CAC policy:
Router# configure terminal
Router(config-sbc-sbe)# cac-policy-set 1
Router(config-sbc-sbe-cacpolicy)# cac-table testpolicytable
Router(config-sbc-sbe-cacpolicy-cactable)# entry 1
Router(config-sbc-sbe-cacpolicy-cactable-entry)# sip sdp-media-profile MediaProfile
Router(config-sbc-sbe-cacpolicy-cactable-entry)
Related Commands
Command
|
Description
|
entry
|
Creates or modifies an entry in a table or an SDP media profile.
|
media-line
|
Adds a media description line to an entry in an SDP media profile.
|
show sbc sbe sip sdp-media-profile
|
Shows all SDP media profiles in an SBC service or details for a specified profile.
|
sip sdp origin-user-name
To configure the originating user name that is filled in generated SDPs, use the sdp origin-user-name command in the SBE configuration mode. To reset this user name such that received user name from an SDP is the user name used on the generated SDP, use the no form of this command.
sip sdp origin-user-name user-name
no sip sdp origin-user-name user-name
Syntax Description
user-name
|
The user name to fill in on generated SDPs.
|
Defaults
No default behavior or values
Command Modes
SBE configuration (config-sbc-sbe)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.4
|
The sdp origin-user-name command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Cisco IOS XE Release 2.5
|
This command was modified to be sip sdp origin-user-name.
|
Usage Guidelines
To use this command, you must be in the correct configuration mode and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
Examples
The following command configures the SDP username to use on generated SDPs to foo:
Router(config)# sbc mySbc
Router(config-sbc-sbe)# sip sdp origin-user-name foo
Router(config-sbc-sbe-sip)#
sip sdp-policy-table
To configure an SDP policy table, use the sip sdp-policy-table command in the SBE configuration mode. To deconfigure an SDP policy table, use the no form of this command.
sip sdp-policy-table table_name
no sip sdp-policy-table table_name
Syntax Description
table_name
|
The name of the SDP policy. The maximum number of characters is 30.
|
Defaults
No default behavior or values
Command Modes
SBE configuration (config-sbc-sbe)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.4
|
The sdp-policy-table command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Cisco IOS XE Release 2.5
|
This command modified to be sip sdp-policy-table.
|
Usage Guidelines
To use this command, you must be in the correct configuration mode and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
Examples
The following command configures the SDP policy table foo:
Router# configure terminal
Router(config)# sbc mySbc
Router(config-sbc-sbe)# sip sdp-policy-table foo
Router(config-sbc-sbe-sip)#
Related Commands
Command
|
Description
|
sip sdp-match-table
|
Creates an SDP match table.
|
action (sdp)
|
Configures an SDP policy table action.
|
match-string
|
Configure an SDP attribute matching string.
|
sip timer
To enter the mode of the SIP timer function, use the sip timer command in SBE configuration mode. To return to the default value, use the no form of this command.
sip timer
no sip timer
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
SBE configuration (config-sbc-sbe)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.4
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Usage Guidelines
To use this command, you must be in the correct configuration mode and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
Examples
The following example shows how to enter the SIP timer submode:
Router(config)# sbc mySbc
Router(config-sbc-sbe)# sip timer
Router(config-sbc-sbe-sip-tmr)
sip visited network identifier
To configure a visited network identifier on a SIP P-CSCF adjacency, use the sip visited network identifier command in SBE configuration mode. To deconfigure the visited network identifier, use the no form of this command.
sip visited network identifier network-name
no sip visited network identifier
Syntax Description
network-name
|
Specifies the name of the visited network identifier.
|
Defaults
No default behavior or values
Command Modes
Adjacency SIP configuration (config-sbc-sbe-adj-sip)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.4
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Usage Guidelines
To use this command, you must be in the correct configuration mode and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
Examples
The following example shows how to use the sip visited network identifier command to configure a visited network identifier on a P-CSCF-access adjacency:
Router# configure terminal
Router(config)# sbc mySbc
Router(config-sbc-sbe)# adjacency sip SipToIsp42
Router(config-sbe-adj-sip)# sip visited network identifier cisco.com2
Related Commands
Command
|
Description
|
sip home network identifier
|
Configures a home network identifier on all IBCF adjacencies.
|
sipi
To configure the SIP-I commands on a SIP adjacency, use the sipi command in adjacency SIP configuration mode. To deconfigure the SIP-I commands, use the no form of this command.
sipi passthrough
no sipi passthrough
Syntax Description
passthrough
|
Configures a SIP adjacency for SIP-I passthrough.
|
Defaults
No default behavior or values
Command Modes
Adjacency SIP configuration (config-sbc-sbe-adj-sip)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.4
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Usage Guidelines
To use this command, you must be in the correct configuration mode and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
Examples
The following example shows how the sipi command is used to configure a SIP adjacency for SIP-I passthrough:
Router# configure terminal
Router(config)# sbc mySbc
Router(config-sbc-sbe)# adjacency sip SipToIsp42
Router(config-sbe-adj-sip)# sipi passthrough
Related Commands
Command
|
Description
|
show sbcs sbe adjacencies
|
Lists the adjacencies configured on the SBE.
|
snmp-server enable traps sbc
To enable all SBC notification types, use the snmp-server enable traps sbc command in global configuration mode without keywords. To disable all SBC notification types, use the no form of this command without keywords.
snmp-server enable traps sbc [adj-status | blacklist | congestion-alarm | h248-ctrlr-status |
media-source | radius-conn-status | sla-violation | svc-state ]
no snmp-server enable traps sbc [adj-status | blacklist | congestion-alarm | h248-ctrlr-status |
media-source | radius-conn-status | sla-violation | svc-state ]
Syntax Description
adj-status
|
Enable SNMP SBC Adjacency Status traps.
|
blacklist
|
Enable SNMP SBC Blacklist traps.
|
congestion-alarm
|
Enable SNMP SBC Congestion Alarm traps.
|
h248-ctrlr-status
|
Enable SNMP SBC H.248 Controller Status traps.
|
media-source
|
Enable SNMP SBC Media Source Alert traps.
|
radius-conn-status
|
Enable SNMP SBC Radius Connect Status traps.
|
sla-violation
|
Enable SNMP SBC Sla Violation traps.
|
svc-state
|
Enable SNMP SBC Service state traps.
|
Defaults
Disable all SBC related traps.
Command Modes
Global configuration
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.4
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Usage Guidelines
To use this command, you must be in the correct configuration mode and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
Use the snmp-server enable traps sbc command by itself to enable or disable all of the SNMP traps. Use specific keywords to enable or disable specific SNMP traps.
After you enable the trap, you will need to specify the recipient of a SNMP notification operation with the snmp-server host command. For information about that command, see the Cisco IOS Release 12.2 SR Command References at http://www.cisco.com/univercd/cc/td/doc/product/software/ios122sr/cr/index.htm.
Examples
The following example shows how to enable only the SNMP blacklist notification:
Router# configure terminal
Router(config)# snmp-server enable traps sbc blacklist
start
To configure either the H.323 slow start or H.323 fast start mode of operation for an adjacency, use the start command in adjacency h323 configuration mode. The no form of the command resets to the default of outgoing call start mode is the same as the incoming call start mode.
start [ fast | slow ]
no start
Syntax Description
fast
|
Specifies H.323 fast start mode of operation where the SBC only uses the fast start mode for outgoing calls on the adjacency. However, incoming slow start calls are converted to fast start mode as they cross the SBC.
|
slow
|
Specifies H.323 slow start mode of operation where the SBC only uses the slow start mode for outgoing calls on the adjacency. However, incoming fast start calls are converted to slow start as they cross the SBC.
|
Defaults
Default is outgoing call start mode is the same as the incoming call start mode
Command Modes
Adjacency H.323 configuration (config-sbc-sbe-adj-h323)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.5
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Usage Guidelines
When the fast start mode is configured, the SBC only uses the fast start mode for outgoing calls. However, incoming slow start calls are converted to fast start mode as they cross the SBC.
When the slow start mode is configured, the SBC only uses the slow start mode for outgoing calls. However, incoming fast start calls are converted to slow start as they cross the SBC.
If neither fast start nor slow start mode is configured on the adjacency, the default is that the outgoing call start is the same as the incoming call start. The mode of operation can be modified while the adjacency is active but the change will only affect new calls.
See the H.323 Support chapter for more information on the H.323 Slow Start to H.323 Fast Start Interop feature.
Examples
The following example shows how to configure slow start mode of operation on the adjacency h323:
Router# configure terminal
Router(config)# sbc mySbc
Router (config-sbc-sbe)# adjacency h323
Router (config-sbc-sbe-adj-h323)# start slow
Related Commands
Command
|
Description
|
adjacency
|
Configures an adjacency on the SBC.
|
statistics-setting
To configure an adjacency to support SIP method statistics, use the statistics-setting command in adjacency SIP configuration mode. To return to the default behavior, use the no form of this command.
statistics-setting {detail | summary}
no statistics-setting {detail | summary}
Syntax Description
detail
|
Allows the show sbc sbe sip-method-stats command to display statistics about SIP response codes and SIP request names, such as INVITE.
|
summary
|
Allows the show sbc sbe sip-method-stats command to display statistics about SIP request names only, such as INVITE.
|
Command Default
Adjacencies are not configured to support SIP method statistics.
Command Modes
Adjacency SIP configuration (config-sbc-sbe-adj-sip)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.4.1
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Usage Guidelines
The statistics-setting command must be configured on an adjacency before using the show sbc sbe sip-method-stats command to display SIP method statistics.
Examples
The following example configures the sipGW adjacency to support detailed SIP method statistics:
Router# configure terminal
Router(config)# sbc mySbc
Router(config-sbc-sbe)# adjacency sip sipGW
Router(config-sbc-sbe-adj-sip)# statistics-setting detail
Related Commands
Command
|
Description
|
clear sbc sbe adjacency statistics
|
Clears the SIP method statistics counters and resets them to zero.
|
show sbc sbe sip-method-stats
|
Displays summary or detailed statistics for a SIP method.
|
subscriber
To define a unique subscriber for whom you want to configure Provisioned Delegate Registration, use the subscriber command in SBE configuration mode. To remove a subscriber for whom you have configured Provisioned Delegate Registration, use the no subscriber command.
subscriber {aor}
no subscriber {aor}
Syntax Description
aor
|
This is the address of record of the delegate client and defines the unique subscriber for whom you want to configure Provisioned Delegate Registration.
It is a string field with a 62 characters maximum length.
|
Command Default
No default behavior or values
Command Modes
SBE configuration (config-sbc-sbe)#
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.4
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Usage Guidelines
Delegate registration is done underneath the SBE configuration for globally unique subscribers. The subscriber must have one or more SIP contacts or Uniform Resource Identifiers (URIs) associated with it.
Examples
The following example configures a delegate registration profile that can be applied to a delegate registration subscriber:
delegate-profile my-profile
The following example configures a SIP contact for a subscriber, for whom a subscriber detail table exists, and for whom, after the SIP contact is configured, Provisioned Delegate Registration can be configured:
subscriber sip:bob@isp.example
sip-contact sip:steve@10.1.1.2
The following example configures a delegate registration aor= sip:bob@isp.example
(config-sbc-sbe)# subscriber sip:bob@isp.example
(config-sbc-sbe-subscriber-entry)# sip-contact sip:steve@10.1.1.2
(config-sbc-sbe-subscriber-contact)# adjacency CallMgrB
(config-sbc-sbe-subscriber-contact)# exit
(config-sbc-sbe-subscriber-entry)# delegate-registration sip:registrar@1.1.1.1
(config-sbc-sbe-subscriber-delegate)# adjacency CallMgrA
(config-sbc-sbe-subscriber-delegate)# profile my-profile
(config-sbc-sbe-subscriber-delegate)# activate
Related Commands
Command
|
Description
|
delegate-profile
|
Configures a delegate registration profile that is applied to a delegate registration subscriber.
|
sip-contact
|
Configures the SIP contact information for a specified Uniform Resource Identifier (URI) for a delegate subscriber
|
delegate-registration
|
Configures a delegate registration for a delegate client.
|
adjacency
|
Configures the adjacency facing the registrar.
|
profile
|
Applies a delegate registration profile to a delegate registration subscriber.
|
show sbc sbe sip delegate-profile
|
Displays subscriber profiles for whom Provisioned Delegate Registration has been configured.
|
show sbc sbe sip subscribers
|
Displays subscribers for whom Provisioned Delegate Registration has been provisioned.
|
table-type
To configure a Call Admission Control (CAC) table type that enables the priority of the call to be used as a criterion in CAC policy, use the table-type command in CAC table configuration mode. To delete the CAC Policy Set or Limit table, use the no form of this command.
table-type {policy-set | limit {list of limit tables}}
no table-type {policy-set | limit {list of limit tables}}
Syntax Description
policy-set
|
Specifies a Policy Set table type.
For a Policy Set table type, the event is applied to all entries in the CAC table. You can define the scope at which CAC policy limits are applied using the cac-scope command in each entry.
|
limit
|
Specifies a Limit table type.
For a Limit table type, the event matches a single, most specific entry. Only one entry is matched in a limit table type. You can define the match-value within the entry in the Limit table using the match-value command. A limit table type inherits its scope from its parent table.
|
list of limit tables
|
Specifies the type of Limit table. This parameter governs the syntax of the match-value fields of the entries in the table.
The Limit table types are:
• account—Compare the name of the account.
• adj-group—Compare the name of the adjacency group.
• adjacency—Compare the name of the adjacency.
• all—No comparison type. All events match this type.
• call-priority—Compare with call priority.
• category—Compare the number analysis assigned category.
• dst-account—Compare the name of the destination account.
• dst-adj-group—Compare the name of the destination adjacency group.
• dst-adjacency—Compare the name of the destination adjacency.
• dst-prefix—Compare the beginning of the dialed digit string.
• event-type—Compare with CAC policy event types.
• src-account—Compare the name of the source account.
• src-adj-group—Compare the name of the source adjacency group.
• src-adjacency—Compare the name of the source adjacency.
• src-prefix—Compare the beginning of the calling number string.
• sub-category—Compare events sent to or received from members of the same subscriber category.
• sub-category-pfx—Compare events sent to or received from members of the same subscriber category prefix.
|
Defaults
No default behavior or values
Command Modes
CAC table configuration (config-sbc-sbe-cacpolicy-cactable)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.4
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Cisco IOS XE Release 2.5
|
The sub-category and sub-category-pfx Limit table types were added.
|
Usage Guidelines
When creating a CAC table, you must configure the table type parameter as a Policy Set table type or Limit table type.
You cannot modify the table type if entries are currently configured for a different table type. You will receive the error message "Cannot modify table-type with entries currently configured for previous type."
For Policy Set tables, the event is applied to all entries in the Policy Set table. You can define the scope at which CAC limits are applied within each entry with the cac-scope command. The cac-scope command is only available to entries defined within a Policy Set table type.
For Limit tables, the event matches only a single entry. With Limit tables, you can define the match-value within the entry with the match-value command. A Limit table inherits its scope from its parent table.
To define a CAC policy, you must define the limit and the scope at which the policy is applied. For example, you can define a policy such that not more than 10 concurrent calls (limit) could ever be made from a single account (scope).
For more information on Policy Set and Limit table types, see Chapter 12, "Implementing Cisco Unified Border Element (SP Edition) Policies."
Examples
The following example shows how to configure the CAC policy-set table TAB1:
Router# configure terminal
Router(config)# sbc mySbc
Router(config-sbc-sbe)# cac-policy-set 1
Router(config-sbc-sbe-cacpolicy)# first-cac-table TAB1
Router(config-sbc-sbe-cacpolicy)# cac-table TAB1
Router(config-sbc-sbe-cacpolicy-cactable)# table-type policy-set
Router(config-sbc-sbe-cacpolicy-cactable)# entry 1
Router(config-sbc-sbe-cacpolicy-cactable-entry)# cac-scope call
Router(config-sbc-sbe-cacpolicy-cactable-entry)# max-num-calls 20
Router(config-sbc-sbe-cacpolicy-cactable-entry)# action cac-complete
Router(config-sbc-sbe-cacpolicy-cactable-entry)# exit
Router(config-sbc-sbe-cacpolicy-cactable)# exit
Router(config-sbc-sbe-cacpolicy)# complete
Related Commands
Command
|
Description
|
cac-table
|
Configures CAC tables.
|
match-value
|
Configures the match-value of an entry in a Limit table.
|
cac-scope
|
Allows you to choose a scope at which CAC limits are applied within each entry in a Policy Set table.
|
tcp (blacklist)
To enter the mode for configuring blacklisting for TCP protocol only, use the tcp command in the SBE blacklist IPv4 configuration mode.
tcp port number
Syntax Description
port number
|
Port number to blacklist. Range is 0-65535.
|
Defaults
No default behavior or values
Command Modes
SBE blacklist IPv4 configuration (config-sbc-sbe-blacklist-ipv4)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.4
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Usage Guidelines
To use this command, you must be in the correct configuration mode and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
Examples
The following example shows how to enter the mode for configuring blacklisting for TCP protocol only:
Router(config)# sbc mySbc
Router(config-sbc-sbe)# blacklist
Router(config-sbc-sbe-blacklist)# ipv4 1.1.1.1
Router(config-sbc-sbe-blacklist-ipv4)# tcp 1
Router(config-sbc-sbe-blacklist-ipv4-tcp)#
Related Commands
blacklist
|
Enters the mode for configuring the default event limits for the source addresses in a given VPN.
|
address-default
|
Enters the mode for configuring the default event limits for the source addresses in a given VPN.
|
clear sbc sbe blacklist
|
Clears the blacklist for the specified SBC service.
|
reason
|
Enters a submode for configuring a limit to a specific event type on the source.
|
tcp-connect-timeout
To configure the time that SBC waits for a SIP TCP connection to a remote peer to complete before failing that connection, use the tcp-connect-timeout command in SIP timer mode. To return to the default value, use the no form of this command.
tcp-connect-timeout interval
no tcp-connect-timeout
Syntax Description
interval
|
Specifies the time, in milliseconds, that the SIP TCP connection to a remote peer stays alive before timing out.
|
Defaults
Default interval is 30000 milliseconds
Command Modes
SIP timer (config-sbc-sbe-sip-tmr)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.4
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Usage Guidelines
To use this command, you must be in the correct configuration mode and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
Examples
The following example shows how to set the TCP connection timeout to 30 seconds:
Router# configure terminal
Router(config)# sbc mysbc
Router(config-sbc-sbe)# sip timer
Router(config-sbc-sbe-sip-tmr)# tcp-connect-timeout 30000
tcp-idle-timeout
To configure the length of time that the TCP connection should stay active when in the idle state, use the tcp-idle-timeout command in SIP timer mode. To return to the default value, use the no form of this command.
tcp-idle-timeout interval
no tcp-idle-timeout
Syntax Description
interval
|
Specifies the minimum time, in milliseconds, that the TCP connection stays active when it is not processing any traffic. After this time, the TCP connection closes. Range is 1 to 4294967295 ms.
Note The value for this command might not be precise since the idle timers are checked every 12 seconds.
|
Command Default
Default value is 120000 ms (2 minutes).
Command Modes
SIP timer (config-sbc-sbe-sip-tmr)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.4
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Usage Guidelines
To use this command, you must be in the correct configuration mode and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
Examples
The following example shows how to configure the minimum TCP idle timeout value to 10000 ms:
Router# configure terminal
Router(config)# sbc mysbc
Router(config-sbc-sbe)# sip timer
Router(config-sbc-sbe-sip-tmr)# tcp-idle-timeout 10000
tcp timer giveup
To configure a giveup time period that controls how long a TCP connection retries active connections, use the tcp timer giveup command in SBE configuration mode. To disable the giveup timer, use the no form of this command.
tcp timer giveup {1-2400}
no tcp timer giveup
Syntax Description
1-2400
|
Specifies number of seconds that a TCP connection continues to retry on active connections. The TCP connection is dropped when the giveup time period is reached.
|
Defaults
By default, the giveup timer is disabled.
Command Modes
SBE configuration (config-sbc-sbe)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.4
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Usage Guidelines
You use the tcp timer giveup command to specify a time period in seconds that controls how long a TCP connection continues to retry on active connections before giving up. On the Cisco ASR 1000 Series Routers, TCP connections will retry for a few minutes due to excessive default retry counts and retry intervals. If the giveup time period is reached without a reply from the peer, the TCP connection is dropped. By default, the giveup timer is disabled which means TCP retries based on the platform default.
Because the TCP connection timeout may vary depending on the network, a recommended timeout value must be based on how the endpoints are configured. It is recommended that the timeout value is chosen, such that it is not less than the timer B value that is used by the endpoints and defined in section 17.1.1.2 of RFC3261.
Examples
The following example shows that a giveup timer has been configured for 40 seconds:
Router# configure terminal
Router(config)# sbc mySbc
Router(config-sbc-sbe)# tcp timer giveup 40
Related Commands
Command
|
Description
|
tcp-connect-timeout
|
Configures the time that SBC waits for a SIP TCP connection to a remote peer to complete before failing that connection.
|
tcp-idle-timeout
|
Configures the length of time that the TCP connection should stay active when in the idle state.
|
tech-prefix
To configure the RAS tech prefix on an H.323 adjacency, use the tech-prefix command in adjacency H.323 configuration mode. To deconfigure RAS Tech Prefix, use the no form of this command.
tech-prefix tech-prefix name
no tech-prefix tech-prefix name
Syntax Description
tech-prefix name
|
Specifies the name of the tech prefix. Use a combination of the numbers from 0-9 and the special characters star (*), hash (#), and comma (,).
|
Defaults
No default behavior or values
Command Modes
Adjacency H.323 configuration (config-sbc-sbe-adj-h323)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.4
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Usage Guidelines
To use this command, you must be in the correct configuration mode and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
Examples
The following example shows how the tech-prefix command is used to configure RAS tech prefix on an H.323 adjacency named H323ToIsp42:
Router# configure terminal
Router(config)# sbc mySbc
Router(config-sbc-sbe)# adjacency h323 H323ToIsp42
Router(config-sbc-sbe-adj-h323)# tech-prefix 2334
tgid-context
To define trunk-group ID context and trunk-group ID values to match the entries of the routing table, use the tgid-context command in RTG routing table configuration mode. To delete the TGID values of the given entry in the routing table, use the no form of this command.
tgid-context tgid-context-name {tgid tgid-name}
no tgid-context tgid-context-name {tgid tgid-name}
Syntax Description
tgid-context-name
|
Specifies trunk-group ID context to match on.
|
tgid-name
|
Specifies trunk-group ID to match on complete.
|
Command Default
No default behavior or values
Command Modes
RTG routing table configuration (config-sbc-sbe-rtgpolicy-rtgtable-entry)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.5
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Usage Guidelines
To use this command, you must be in the correct configuration mode and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
Examples
The following example configures the trunk-group ID context and trunk-group ID to match in the new routing table MyRtgTable:
Router# configure terminal
Router(config)# sbc mysbc
Router(config-sbc-sbe)# adjacency sip adj1
Router(config-sbc-sbe-adj-sip)# tgid-routing
Router(config-sbc-sbe-adj-sip)# exit
Router(config-sbc-sbe)# call-policy-set 1
Router(config-sbc-sbe-rtgpolicy)# rtg-dst-trunk-group-id-table MyRtgTable
Router(config-sbc-sbe-rtgpolicy-rtgtable)# entry 1
Router(config-sbc-sbe-rtgpolicy-rtgtable-entry)# action complete
Router(config-sbc-sbe-rtgpolicy-rtgtable-entry)# dst-adjacency SIP-AS540-PSTN-GW2
Router(config-sbc-sbe-rtgpolicy-rtgtable-entry)# match-type tgid
Router(config-sbc-sbe-rtgpolicy-rtgtable-entry)# tgid-context example-domain tgid
trunkgroup1
Router(config-sbc-sbe-rtgpolicy-rtgtable-entry)#
Related Commands
Command
|
Description
|
call-policy-set
|
Enters the mode of a routing policy configuration within an SBE entity.
|
sbc
|
Creates a new SBC service and enters a new SBC configuration mode. Alternatively, enters the configuration mode of an existing service.
|
sbe
|
Enters the mode of an SBE entity within an SBC service.
|
rtg-src-trunk-group- id-table
|
Enters the configuration mode of an existing routing table or creates a new table whose entries match the source TGID or TGID context parameters of an SBE policy set.
|
rtg-dst-trunk-group- id-table
|
Enters the configuration mode of an existing routing table or creates a new table whose entries match the destination TGID or TGID context parameters of an SBE policy set.
|
tgid-routing
|
Enables parsing the trunk-group identifier for call routing.
|
tgid-routing
To enable parsing the trunk-group identifier for call routing, use the tgid-routing command in adjacency SIP configuration mode. Use the no form of this command to disable the parsing.
tgid-routing
no tgid-routing
Command Default
No default behavior or values
Command Modes
Adjacency SIP configuration (config-sbc-sbe-adj-sip)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.5
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Usage Guidelines
To use this command, you must be in the correct configuration mode and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
Examples
The following command enables parsing the trunk-group identifier for call routing.
Router# configure terminal
Router(config)# sbc mysbc
Router(config-sbc-sbe)# adjacency sip adj1
Router(config-sbc-sbe-adj-sip)# tgid-routing
Router(config-sbc-sbe-adj-sip)# exit
Related Commands
Command
|
Description
|
sbc
|
Creates a new SBC service and enters a new SBC configuration mode. Alternatively, enters the configuration mode of an existing service.
|
sbe
|
Enters the mode of an SBE entity within an SBC service.
|
rtg-src-trunk-group- id-table
|
Enters the configuration mode of an existing routing table or creates a new table whose entries match the source TGID or TGID context parameters of an SBE policy set.
|
rtg-dst-trunk-group- id-table
|
Enters the configuration mode of an existing routing table or creates a new table whose entries match the destination TGID or TGID context parameters of an SBE policy set.
|
time-offset
Use the time-offset specified by the timezone-offset command. To disable using the time-offset specified by the timezone-offset command, use the no form of this command.
time-offset hour hr min min [negative]
no time-offset
Syntax Description
hr:hour_offset
|
Range: h: -23 to +23
|
min: minute_offset
|
Range: m:-59 to +59
|
negative
|
Specifies behind the local time.
|
Defaults
No default behavior or values
Command Modes
RTG routing table entry configuration (config-sbc-sbe-rtgpolicy-rtgtable-entry)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.4
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Usage Guidelines
To use this command, you must be in the correct configuration mode and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
Without this command the time-offset specified by the timezone-offset command under the SBE configuration submode is unused.
Examples
The following example shows how to configure the destination adjacency of an entry in the new routing table MyRtgTable to softswitch1:
Router# configure terminal
Router(config)# sbc mySbc
Router(config-sbc-sbe)# call-policy-set 1
Router(config-sbc-sbe-rtgpolicy)# rtg-dst-address-table MyRtgTable
Router(config-sbc-sbe-rtgpolicy-rtgtable)# entry 1
Router(config-sbc-sbe-rtgpolicy-rtgtable-entry)# use-time-offset
Related Commands
Command
|
Description
|
timezone-offset
|
Configures the number of hours and minutes that the desired time zone is ahead of or behind the local time.
|
timeout
To define the length of time that packets from the source are blocked if the number of authentication requests exceed the set limit, use the timeout command in blacklist reason mode. The no form of this command releases the limit duration for blacklisting the source.
timeout time-period
no timeout
Syntax Description
time-period
|
Duration for which the source is blacklisted after activation of blacklisting.
• 0 = source not blacklisted
• never = blacklisting is permanent
• number {milliseconds | seconds | minutes | hours | days}
Note Period must be less than 23 days.
|
Command Default
•
The address-default value defaults to its initial settings. The port-default values default to zero.
•
If this field is omitted on explicit ports, it defaults to the value given in the port-default for this address.
•
If this field is omitted on explicit addresses, this field defaults to the value in the address-default for this address.
•
If this field is omitted for VPN, it defaults to the value for global addresses.
•
If this field is omitted for the global address space, it defaults to the initial settings.
Command Modes
Blacklist address-default submode (config-sbc-sbe-blacklist-addr-default-reason)
Blacklist global submode (config-sbc-sbe-blacklist-global-reason)
Blacklist ipv4 submode (config-sbc-sbe-blacklist-ipv4-reason)
Blacklist vpn submode (config-sbc-sbe-blacklist-vpn-reason)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.4
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Usage Guidelines
To use this command, you must be in the correct configuration mode and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
Examples
The following command configures a new blacklist on the SBE to affect all packets arriving from address 125.12.12.15 for three minutes:
Router# configure terminal
Router(config)# sbc mysbc
Router(config-sbc-sbe)# blacklist
Router(config-sbc-sbe-blacklist)# ipv4 125.12.12.15
Router(config-sbc-sbe-blacklist-ipv4)# reason authentication-failure
Router(config-sbc-sbe-blacklist-ipv4-reason)# timeout 180 seconds
Router(config-sbc-sbe-blacklist-ipv4-reason)# exit
Related Commands
Command
|
Description
|
reason
|
Enters a submode for configuring a limit to a specific event type on the source (in other words, a port, IP address, VPN, global address space).
|
trigger-size
|
Defines the number of the specified events from the specified source that are allowed before the blacklisting is triggered, and blocks all packets from the source.
|
trigger-period
|
Defines the period over which events are considered. For details, see the description of the trigger-size command.
|
show sbc sbe blacklist configured-limits
|
Lists the explicitly configured limits, showing only the sources configured. Any values not explicitly defined for each source are in brackets.
|
show sbc sbe blacklist
|
Lists the limits in force for a particular source (whether they are from defaults or explicitly configured) in a form in which they can be entered into the CLI. Also listed are any defaults for a smaller scope configured at this address.
|
show sbc sbe blacklist current-blacklisting
|
Lists the limits causing sources to be blacklisted.
|
timezone-offset
To configure the number of hours and minutes that the desired time zone is ahead of or behind the local time, use the timezone-offset command in SBE configuration mode. To remove the time-zone offset, use the no form of this command.
timezone-offset h:hour_offset m: minute_offset {positive | negative}
no timezone-offset h:hour_offset m: minute_offset
Syntax Description
h:hour_offset
|
Range: h: -23 to +23
|
m: minute_offset
|
Range: m:-59 to +59
|
positive
|
Specifies ahead of the local time.
|
negative
|
Specifies behind the local time.
|
Defaults
Zero is the default.
Command Modes
SBE configuration (config-sbc-sbe)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.4
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Usage Guidelines
To use this command, you must be in the correct configuration mode and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
Examples
The following example shows how to configure the offset timezone to 11 hours and 45 minutes behind the local time:
Router# configure terminal
Router(config)# sbc mySbc
Router(config-sbc-sbe)# call-policy-set 1
Router(config-sbc-sbe-rtgpolicy)# rtg-dst-domain-table MyRtgTable
Routerconfig-sbc-sbe-rtgpolicy-rtgtable# timezone-offset 11 45 negative
Related Commands
Command
|
Description
|
use-time-offset
|
Uses the time-offset specifiedby the timezone-offset comand.
|
transcode-deny
To forbid transcoding for an entry in the admission control table, use the transcode-deny command in CAC table entry configuration mode. To allow transcoding for this entry in the admission control table, use the no form of this command.
transcode-deny
no transcode-deny
Syntax Description
This command has no arguments or keywords.
Defaults
By default, transcoding for this entry in the admission control table is allowed.
Command Modes
CAC table entry configuration (config-sbc-sbe-cacpolicy-cactable-entry)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.4
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Usage Guidelines
To use this command, you must be in the correct configuration mode and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
Examples
The following example shows how to configure the entry to forbid transcoding in the new admission control table MyCacTable:
Router(config)# sbc mySbc
Router(config-sbc-sbe)# cac-policy-set 1
Router(config-sbc-sbe-cacpolicy)# cac-table MyCacTable
Router(config-sbc-sbe-cacpolicy)# table-type limit dst-prefix
Router(config-sbc-sbe-cacpolicy-cactable)# entry 1
Router(config-sbc-sbe-cacpolicy-cactable-entry)# transcode-deny
transcoder
To configure that the media gateway is a transcoder, use the transcoder command in media gateway codecs configuration mode. To return to the default behavior, use the no form of this command.
transcoder
no transcoder
Syntax Description
This command has no arguments or keywords.
Defaults
By default, this command assumes the media gateway has no transcoding features.
Command Modes
Media gateway codecs configuration (config-sbc-sbe-mg-codecs)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.4
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
|
Usage Guidelines
To use this command, you must be in the correct configuration mode and submode. The Examples section shows the hierarchy of modes and submodes required to run the command.
Examples
The following example shows how to set media gateway 10.0.0.1 to be a transcoder:
Router# configure terminal
Router(config)# sbc mySbc
Router(config-sbc-sbe)# media-gateway ipv4 10.0.0.1
Router(config-sbc-sbe-mg)# codecs m=audio 1234 RTP/AVP 0 2 8 18,a=rtpmap:0
PCMU/8000,a=rtpmap:a=rtpmap:8 PCMA/8000,a=rtpmap:18 G729/80002 G72 6-32/8000,a=rtpmap:8
PCMA/8000,a=rtpmap:18 G729/8000
Router(config-sbc-sbe-mg-codecs)# transcoder
translate
To configure IP-to-FQDN or FQDN-to-IP translation on signaling border elements (SBEs), use the translate command in the adjacency SIP configuration submode.
trans