- 100rel inbound through critical-alert-size
- deact-mode (billing) through group
- h225 address through overload-time-threshold
- packetcable-em transport radius through show monitor event-trace sbc ha
- show platform hardware qfp active feature sbc sfx through show sbc sbe media-gateways
- show sbc sbe policy-failure-stats through xml (billing)
Cisco Unified Border Element (SP Edition) Command Reference: Unified Model
- Updated:
- July 16, 2014
Chapter: 100rel inbound through critical-alert-size
- 100rel inbound
- 100rel outbound
- account (session border controller)
- action (body)
- action (body editor)
- action (CAC)
- action drop-msg
- action (header-editor)
- ac tion (method-editor)
- action (method profile)
- action (NA-)
- ac tion (parameter)
- action (parameter editor)
- action (RTG-)
- action (SDP)
- action (SIP)
- activate (billing)
- activate (enum)
- activate (radius)
- activate (session border controller)
- cac-policy-set global
- call-policy-set default
- active-script-set
- address ipv4 (session border controller)
- address (session border controller)
- adjacency
- adjacency h248
- adjacency timeout
- admin-domain
- admin-domain (adjacency)
- alias (session border controller)
- allow diff-med-sig-vpn
- allow private info
- associate dspfarm profile
- attach-controllers (session border controller)
- attach (H.248 BAC)
- attach (Rf billing)
- attach (session border controller)
- audit (H.248 BAC)
- authentication mode (session border controller)
- authentication (session border controller)
- bandwidth-fields mandatory
- bandwidth (session border controller)
- batch-size
- batch-time
- bgp additional-paths select
- bgp bestpath igp-metric ignore
- bgp consistency-checker
- bgp refresh max-eor-time
- bgp refresh stalepath-time
- billing
- billing (CAC)
- blacklist
- blacklist (profile)
- blacklist (sip-opt)
- blended-codec-list
- blended-transcode
- body-editor
- body-editor (method)
- body-profile
- body-profile (sip adj)
- body
- body (editor)
- branch bandwidth-field
- branch codec
- branch codec-list
- branch hold-setting
- branch inband-dtmf-mode
- branch inbound-policy
- branch media bypass
- branch media-caps
- branch media-description disabled
- branch media-type
- branch outbound-policy
- branch port-range-tag
- branch privacy edit-privacy-request
- branch privacy privacy-service
- branch ptime
- branch secure-media
- branch sig-qos-profile
- branch tel-event payload type
- branch video-qos-profile
- branch voice-qos-profile
- cac-policy-set
- cac-policy-set (admin-domain)
- cac-policy-set global
- cac-table
- cache-lifetime
- cache-limit
- cache (session border controller)
- cac-policy-set global
- cac-scope
- calc-moscqe
- call-policy-set
- call-policy-set (admin-domain)
- call-policy-set default
- callee-bandwidth-field
- callee-codec-list
- callee-hold-setting
- callee-inbound-policy
- callee-media-caps
- callee-outbound-policy
- callee-privacy edit-privacy-request
- callee-privacy privacy-service
- callee-sig-qos-profile
- callee tel-event payload type
- callee-video-qos-profile
- callee-voice-qos-profile
- callee codec
- callee inband-dtmf-mode
- callee media-description disabled
- callee media-type
- callee media bypass
- callee port-range-tag
- callee ptime
- callee secure-media
- caller-bandwidth-field
- caller-codec-list
- caller-hold-setting
- caller-inbound-policy
- caller-media-caps
- caller-outbound-policy
- caller-privacy edit-privacy-request
- caller-privacy privacy-service
- caller-sig-qos-profile
- caller tel-event payload type
- caller-video-qos-profile
- caller-voice-qos-profile
- caller codec
- caller inband-dtmf-mode
- caller media-description disabled
- caller media-type
- caller media bypass
- caller port-range-tag
- caller ptime
- caller secure-media
- call-policy-set default
- category (NA-)
- cause
- cdr
- cdr alarm (XML Billing)
- cdr path
- clear platform hardware qfp active feature sbc sfx
- clear platform software wccp
- clear sbc
- clear sbc dbe media-stats (session border controller)
- clear sbc h248 bac
- clear sbc sbe adjacency statistics
- clear sbc sbe blacklist
- clear sbc sbe cac-policy-set-stats
- clear sbc sbe cac-rejection-stats
- clear sbc sbe call-policy-set-stats
- clear sbc sbe call-rate-stats
- clear sbc sbe call-rejection-stats
- clear sbc sbe call-stats
- clear sbc sbe call
- clear sbc sbe policy-failure-stats
- clear sbc sbe policy-rejection-stats
- clear sbc sbe radius-client-stats
- clear sbc sbe radius-client
- clear sbc sbe script-set-stats
- clear sbc sbe sip statistics
- clear sbc sbe sip subscriber aor
- clear sbc sbe statistics
- clear sbc sbe transcoding-stats
- codec-list description
- codec-preference-list
- codec-restrict-to-list
- codec
- codecs
- codec custom
- codec list
- codec packetization-period
- codec system
- codec variant
- concurrent-requests
- condition (editor)
- condition (session border controller)
- congestion-cleared
- congestion-threshold
- congestion sip reject-code
- control-address h248 ipv4
- control-address ipv4
- controller h248
- control address aaa
- control address h248 index
- control address h248 port
- control address h248 transport
- copy logs
- core-adj
- cost
- critical-alert-size
- current15minutes
- current5minutes
- currentday
- currenthour
- currentindefinite
100rel inbound
To configure the 100rel interworking parameters for inbound SIP adjacencies on signaling border elements (SBEs), use the 100rel inbound command in the adjacency SIP configuration mode.
100rel inbound {strip | support}
Syntax Description
Command Default
Command Modes
Adjacency SIP configuration (config-sbc-sbe-adj-sip)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to enable the 100rel strip option for the incoming INVITE request for inbound SIP adjacency:
The following example shows how to enable 100rel support option to send reliable provisional responses for all the incoming SIP INVITE requests that contains “Supported:100rel” header:
100rel outbound
To configure the 100rel interworking parameters for outbound SIP adjacencies on signaling border elements (SBEs), use the 100rel outbound command in the adjacency SIP configuration mode.
100rel outbound {require-add | support-add}
Syntax Description
Command Default
Command Modes
Adjacency SIP configuration (config-sbc-sbe-adj-sip)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to enable 100rel Require header option in the outgoing INVITE request:
The following example shows how to enable 100rel Support header option in the outgoing INVITE request:
account (session border controller)
To define a SIP or H.323 adjacency account on an SBE, use the account command in the appropriate configuration mode. To remove this definition, use the no form of this command.
Syntax Description
Command Default
Command Modes
Adjacency SIP configuration (config-sbc-sbe-adj-sip)
Adjacency H.323 configuration (config-sbc-sbe-adj-h323)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to configure the H.323 adjacency h323ToIsp42 to account isp42:
The following example shows how to configure the SIP adjacency SipToIsp42 to account isp42:
action (body)
To set the action to take on a body type in a SIP body profile for a non-SDP message body, use the action (body) command in SBE configuration mode. To restore the default behavior of action nopass, use the no action command.
action [ pass | nopass | strip | reject]
no action [ pass | nopass | strip | reject]
Syntax Description
Command Default
Command Modes
SBE SIP Body Element configuration (config-sbc-sbe-sip-body-ele)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
The action (body) command is used in conjunction with the sip body-profile {profle_name} and body {body_name} commands to complete the configuration.
After creating a body profile with the sip body-profile {profile_name} command, you can associate the body profile at the following levels and configuration modes:
- At the SIP signaling entity level (ingress or egress), under SBE mode, using the sip default body-profile [[inbound|outbound] {profle_name}] command. The body profile is associated for the entire signlaing instance (that is all messages, either ingress or egress, passing through the SBC).
- SIP adjacency level, under SIP adjacency mode, using the body-profile [[inbound|outbound] {profle_name}] command. The body profile is associated to an adjacency.
- At SIP method profile level, under method profile mode, using the body-profile {profle_name} command. The body profile is associated to a method profile.
SBC uses a body profile that you create and associate to filter non-SDP bodies from incoming and outgoing SIP messages, based on the Content-Type header field. A body profile allows a message containing a specific non-SDP body to be either passed (without altering the message), stripped of the body (and pass the rest of the message), or be rejected.
Examples
The following example creates a body profile named bodyprofile1, associates the body profile at the SIP signaling level for all inbound calls passing through the SBC, describes the body type that is to act on messages with the "application/ISUP" content-type header, and instructs SBC to strip that particular message body and pass the rest of the message.
Related Commands
action (body editor)
To set an action to be taken on a body type in a SIP body editor for a non-SDP message body, use the action command in the signaling border element (SBE) SIP body element configuration mode. To remove the action, use the no form of this command.
action [ pass | nopass | strip | reject]
Syntax Description
Command Default
Command Modes
SBE SIP body element configuration (config-sbc-sbe-mep-bdy-ele)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
The action (body) command is used in conjunction with the sip body-editor {editor-name} and body {word} commands to complete the configuration.
The SBC uses a body editor that you have created and associated, to filter the non-SDP bodies from the incoming and outgoing SIP messages, based on the Content Type header field. A body editor allows a message containing a specific non-SDP body to be passed (without altering the message), stripped off the body (and pass the rest of the message), or rejected.
Examples
The following example shows how to create a body editor named bodyeditor1, describe the body type, that is to act on the messages with the application/ISUP Content Type header , and instruct the SBC to strip that particular message body and pass the rest of the message:
Related Commands
action (CAC)
To configure the action to perform after this entry in an admission control table, use the action command in CAC table entry configuration mode.
action { cac-complete | next-table goto-table-name }
no action { cac-complete | next-table goto-table-name }
Syntax Description
Table name identifying the next CAC table to process (or cac-complete, if processing should stop). |
Command Default
Command Modes
CAC table entry configuration (config-sbc-sbe-cacpolicy-cactable-entry)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to configure the next table to process for the entry in the new admission control table MyCacTable:
Related Commands
|
|
|
|---|---|
Configures the action to perform after an entry in an admission control table. |
|
action drop-msg
To add an action of dropping the message to a SIP message profile, use the action drop-msg command in SIP header-profile configuration mode. To remove the method from the profile, use the no form of this command.
Syntax Description
Command Default
Command Modes
SIP header configuration (config-sbc-sbe-sip-hdr)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows action of dropping the message to a SIP message profile to the header profile Myprofile:
Related Commands
|
|
|
|---|---|
action (header-editor)
To configure an action that is to be taken on an element type in a header editor or parameter editor, use the action command in the appropriate configuration mode. To remove an action from the element type, use the no form of this command.
action {add-first-header| add-header | replace-name | replace-value} { value word }
action {as-editor | drop-msg | pass | strip}
action reject [ status-code code-number ]
Syntax Description
Command Default
Command Modes
SBE Header Editor Header configuration (config-sbc-sbe-mep-hdr-ele)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of the modes required to run the command.
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, you must remove the existing configuration first.
Examples
The following example shows how to set the as-editor action for the To header element type in the headerprof1 parameter editor:
Related Commands
|
|
|
|---|---|
action (method-editor)
To configure an action to be taken on a method editor, use the action command in the signaling border element (SBE) method editor element configuration mode. To deconfigure an action, use the no form of this command.
action {as-editor | pass | reject}
Syntax Description
Passes the method for the whitelist method editor, and rejects for the blacklist method editor. |
|
Command Default
Command Modes
SBE method editor element configuration (config-sbc-sbe-mep-mth-ele)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of the modes required to run the command.
Examples
The following example shows the reject action:
Related Commands
|
|
|
|---|---|
action (method profile)
To configure the action to take on a method profile, use the action command in the SBE method profile element configuration mode. To remove the action on a method profile, use the no form of this command.
action {as-profile | pass | reject}
Syntax Description
Command Default
Command Modes
SBE method profile element configuration (config-sbc-sbe-sip-mth-ele)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows the action to drop the method:
Related Commands
|
|
|
|---|---|
action (NA-)
To configure the action of an entry in the number analysis table with entries of the table matching a source number (prefix or whole number), a dialed number (prefix or whole number) or the source adjacency or account, use the action (NA-) command in the Number analysis table configuration mode. To deconfigure the action, use the no form of this command.
action { next-table goto-table-name | accept | reject }
Syntax Description
Command Default
Command Modes
Number analysis table configuration (config-sbc-sbe-rtgpolicy-natable-entry)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
|
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to configure the call to be accepted if it matches the entry in the new number analysis table MyNaTable:
The following example shows how to configure the call to be accepted if it matches the start of the entry in the new number analysis table MyNaTable:
The following example shows how to configure the call to be accepted if it matches the source adjacency entry in the new number analysis table MyNaTable:
The following example shows how to configure the call to be accepted if it matches the source account entry in the new number analysis table MyNaTable:
Related Commands
|
|
|
|---|---|
Configures the action to perform after an entry in an admission control table. |
|
action (parameter)
To configure the action to take on an element type in a parameter, use the action command in the appropriate configuration mode. To remove an action from the element type, use the no form of this command.
action {add-not-present | add-or-replace | strip}
no action {add-not-present | add-or-replace | strip}
Syntax Description
Adds the parameter if it is not present or replace the parameter if it is present. |
|
Command Default
Command Modes
SBE header profile header configuration (config-sbc-sbe-sip-hdr-ele)
SBE parameter profile parameter configuration (config-sbc-sbe-sip-prm-ele)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
If a configuration is loaded on top of an active configuration, warnings are generated to notify that the configuration cannot be modified. If you must modify the entire configuration by loading a new one, please remove the existing configuration first.
Examples
The following example shows how to set the action for parameter element type user in parameter profile paramprof1 to add-not-present:
Router(config-sbc-sbe-sip-prm-ele)# action add-not-present value phone
The following example shows how to set the action for header element type To in parameter profile headerprof1 to as-profile:
Related Commands
|
|
|
|---|---|
action (parameter editor)
To configure an action to be taken on an element type in a parameter editor, use the action command in the SIP Parameter Editor Element configuration mode. To remove an action from an element type, use the no form of this command.
action {add-not-present | add-or-replace} {value} { word | private-ip-address | public-ip-address}
Syntax Description
Command Default
Command Modes
SIP Parameter Editor Element configuration (config-sbc-sbe-mep-prm-ele)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of the modes required to run the command.
Examples
The following example shows how to set the add-not-present action for the parameter element type user in the paramedit1 parameter editor:
Related Commands
|
|
|
|---|---|
action (RTG-)
To configure the action to take if a routing entry is chosen, use the action command in the RTG routing table configuration mode. To delete the action, use the no form of this command.
action { next-table goto-table-name | complete | reject }
Syntax Description
Specifies the next routing table to process if the event matches the entry. |
|
Command Default
Command Modes
RTG routing table configuration (config-sbc-sbe-rtgpolicy-rtgtable-entry)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to configure the match-value of an entry in the new routing table MyRtgTable and if any calls match this criterion, they are rejected.
The following example shows how to configure the match-value of an entry in the new routing table MyRtgTable and if any calls match this criterion, they are rejected.
The following example shows how to configure the match-value of an entry in the new routing table MyRtgTable and if any calls match this criterion, they are rejected.
The following example shows how to configure the match-value of an entry in the new routing table MyRtgTable and if any calls match this criterion, they are rejected.
The following example configures the match-value of an entry in the new routing table MyRtgTable and if any calls match this criterion, they are rejected.
Related Commands
action (SDP)
To configure an SDP policy table action, use the action command in sdp match table configuration mode. To return to the default, use the no form of this command.
action {whitelist | blacklist}
Syntax Description
Block the defined set of attributes and allow the rest. This is the default. |
Command Default
Command Modes
SDP match table configuration (config-sbc-sbe-sdp-match-tbl)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows action of dropping the message to a SIP message profile to the header profile Myprofile:
Related Commands
|
|
|
|---|---|
action (SIP)
To configure the action to take on an element type in a header or parameter profile, use the action command in the appropriate configuration mode. To remove an action from the element type, use the no form of this command.
action {add-first-header| add-header | as-profile | drop-msg | pass | replace-name | replace-value | strip}
no action {add-first-header| add-header | as-profile | drop-msg | pass | replace-name | replace-value | strip}
Syntax Description
Adds the first occurrence of a header (no action if a header exists). |
|
Unconditionally strips the matched body, header, or parameter element. |
Command Default
The default body action is strip .
Command Modes
SBE header profile header configuration (config-sbc-sbe-sip-hdr-ele)
SBE parameter profile parameter configuration (config-sbc-sbe-sip-prm-ele)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
If a configuration is loaded on top of an active configuration, warnings are generated to notify that the configuration cannot be modified. If you must modify the entire configuration by loading a new one, please remove the existing configuration first.
Examples
The following example shows how to set the action for parameter element type user in parameter profile paramprof1 to add-not-present:
Router(config-sbc-sbe-sip-prm-ele)# action add-not-present value phone
The following example shows how to set the action for header element type To in parameter profile headerprof1 to as-profile:
Related Commands
|
|
|
|---|---|
activate (billing)
To activate billing once it is configured, use the activate command in SBE billing configuration mode.
Syntax Description
Command Default
Command Modes
SBE billing configuration (config-sbc-sbe-billing)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
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.
You can activate billing only after the RADIUS configuration has been activated.
Examples
The following example shows how to activate the billing functionality after configuration is committed:
Related Commands
|
|
|
|---|---|
Configures the time of day (local time) to run the Long Duration Check (LDR). |
|
activate (enum)
To activate ENUM client, use the activate command in ENUM configuration mode. To deactivate ENUM client, use the no form of this command.
Syntax Description
Command Default
Command Modes
ENUM configuration (config-sbc-sbe-enum)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to activate ENUM client:
Related Commands
activate (radius)
To activate the RADIUS client, use the activate command in the appropriate configuration mode. To disable this command, use the no form of this command.
Syntax Description
Command Default
Command Modes
Server accounting (config-sbc-sbe-acc)
Server authentication (config-sbc-sbe-auth)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to activate the RADIUS client .
Related Commands
Sets the maximum number of concurrent requests to the RADIUS server. |
activate (session border controller)
To start the Session Border Controller (SBC) service when all signaling border element (SBE) or data border element (DBE) address configuration have been successfully committed, use the activate command in the appropriate configuration mode. To deactivate the SBE service of the SBC, use the no form of this command.
Syntax Description
Command Default
Command Modes
DBE configuration (config-sbc-dbe)
SBE configuration (config-sbc-sbe)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
|
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
The command is not completed even when the CLI returns; there is an asynchronous process (activation or deactivation) going on and the new instruction is not actioned until the last one completes.
Examples
The following example shows how to activate the DBE on the service mySbc:
Router (config-sbc-dbe)# activate
The following example shows how to activate the SBE on the service mySbc:
Related Commands
|
|
|
|---|---|
cac-policy-set global
To activate the global call admission control (CAC) policy set within an signaling border element (SBE) entity, use the cac-policy-set global command in the SBE configuration mode.
cac-policy-set global policy-set-id
Syntax Description
Integer identifying the policy set that should be made global. Range is from 1 to 2147483647. |
Command Default
Command Modes
SBE configuration (config-sbc-sbe)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
|
This command was replaced by the cac-policy-set global command. |
Usage Guidelines
The active CAC policy set cannot be modified.
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of the modes required to run the command.
Examples
The following example shows how to activate policy set 1 on mySbc:
Related Commands
call-policy-set default
To activate a default policy set within a signaling border element (SBE) entity, use the call-policy-set default command in the SBE configuration mode. To deactivate a default policy set, use the no form of this command.
call-policy-set default policy-set-id
Syntax Description
Number that identifies the default call policy set. The range is from 1 to 2147483647. |
Command Default
Command Modes
SBE configuration (config-sbc-sbe)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
|
This command was replaced by the call-policy-set default command. |
Usage Guidelines
If another policy set was previously active, it is made inactive by executing this command. The SBE is created with no active routing policy set; an active routing policy set must be explicitly configured using this command.
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of the modes required to run the command.
Examples
The following example shows how to set policy set 1 as the default on mySbc:
Related Commands
active-script-set
To activate a script set, use the active-script-set command in the SBE configuration mode. To change the active script set to the inactive state, use the no form of this command. Only one script set can be active on the SBC at any given point in time. When you use the no form of this command, script-based editing is temporarily disabled.
active-script-set script-set-number
Syntax Description
Script set number. This is the number that you set when you run the script-set lua command. |
Command Default
Command Modes
SBE configuration (config-sbc-sbe)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
At any particular point of time, only one script can be in the active state on the SBC. When you run the active-script-set command for a particular script set, the script set that was previously active automatically goes to the inactive state. The editors in an inactive script set are not applied to SIP messages. You can switch an inactive script set to the active state by running the active script-set command on it. To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of the modes required to run this command.
Examples
In the following example, the active-script-set command is used to activate the script set with the number 10:
Related Commands
address ipv4 (session border controller)
To configure the address of the RADIUS server, use the address command in the Server accounting configuration mode. To deconfigure the active accounting server address, use the no form of this command.
Syntax Description
Command Default
Command Modes
Server accounting (config-sbc-sbe-acc-ser)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
Any number of accounting servers can be specified. Call Detail Reports are sent to the accounting server with the highest priority upon call termination.
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following command configures accounting servers castor and pollux on mySbc for Remote Authentication Dial-In User Service (RADIUS) client instance radius1:
address (session border controller)
To configure either an IP address or a host name to act as a redundant peer, use the address command in adjacency Session Initiation Protocol (SIP) peer configuration mode. To deconfigure an IP address or a host name, use the no form of this command.
Syntax Description
Command Default
Command Modes
Adjacency SIP peer configuration (config-sbc-sbe-adj-sip-peer)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section that follows shows the hierarchy of the modes required to run the command.
Examples
The following example shows how the address command is used to configure an IP address or a host name to act as a redundant peer on a SIP adjacency:
Related Commands
|
|
|
|---|---|
Configures either an IPv4 or IPv6 network in a redundant peer. |
|
adjacency
To configure an adjacency for an Session Border Controller (SBC) service, use the adjacency command in SBE configuration mode. To deconfigure the adjacency, use the no form of this command.
adjacency { sip | h323 } adjacency-name
no adjacency { sip | h323 } adjacency-name
Syntax Description
Command Default
Command Modes
SBE configuration (config-sbc-sbe)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section below shows the hierarchy of modes required to run the command.
Examples
The following example shows how the adjacency command configures a SIP adjacency named sipGW, and enters into adjacency sip mode.
adjacency h248
To configure an H.248 Border Access Controller (BAC) access adjacency and core adjacency, use the adjacency h248 command in the H248 BAC configuration mode. To unconfigure an H.248 BAC access adjacency and core adjacency, use the no form of this command.
adjacency h248 {access access-adjacency name}
adjacency h248 {core core-adjacency name}
no adjacency h248 {access access-adjacency name} | {core core-adjacency name}
Syntax Description
Command Default
Command Modes
H248 BAC configuration (config-h248-bac)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
When you configure an access adjacency, the adjacency h248 command enters the access adjacency submode.
When you configure a core adjacency, the adjacency h248 command enters the core adjacency submode.
Examples
The following example shows how the adjacency h248 command is used to configure an H.248 BAC access adjacency:
The following example shows how the adjacency h248 command is used to configure an H.248 BAC core adjacency:
Related Commands
|
|
|
|---|---|
Binds an H.248 BAC core djacency with its corresponding H.248 BAC access adjacency. |
adjacency timeout
To configure the adjacency retry timeout interval, use the adjacency timeout command in the appropriate configuration mode. To return to the default value, use the no form of this command.
Syntax Description
Specifies the timeout period in milliseconds. Valid values are from 10000 to 30000. The default value is 30 seconds. |
Command Default
Command Modes
Adjacency H.323 configuration (config-sbc-sbe-adj-h323)
H.323 configuration (config-sbc-sbe-h323)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how the adjacency timeout command configures adjacency retry timeout in adjacency H.323 configuration mode:
The following example shows how the adjacency timeout command configures adjacency retry timeout in H.323 configuration mode.
admin-domain
To configure an administrative domain, use the admin-domain command in the Signaling border element (SBE) configuration mode. To deconfigure an administrative domain, use the no form of this command.
Syntax Description
Command Default
Command Modes
SBE configuration mode (config-sbc-sbe)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of the modes required to run the command.
The command enables the user to enter into the administrative domain mode. The policy set that is to be used for an administrative domain is defined in the administrative domain mode. A user can specify only one CAC policy set to be used for the administrative domain. A user can also define separate call policy sets for inbound number analysis, routing policy, and outbound number analysis. If the policies are not specified, the default call policy set is used.
The policy sets must be in a complete state before they can be assigned to an administrative domain. A default call policy set must be configured before the administrative domain mode can be entered.
Examples
The following example shows how to configure an administrative domain in the SBE configuration mode:
Related Commands
admin-domain (adjacency)
To associate an administrative domain to an adjacency, use the admin-domain command in the Session Initiation Protocol (SIP) adjacency and an H.323 adjacency configuration mode. To remove the association of an administrative domain from an adjacency, use the no form of this command.
Syntax Description
Command Default
Command Modes
SIP adjacency mode (config-sbc-sbe-adj-sip)
H.323 adjacency mode (config-sbc-sbe-adj-h323)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of the modes required to run the command.
In the SIP and H.323 adjacency modes, the user can configure up to two optional administrative domains on an adjacency. A separate admin-domain command is configured for every administrative domain. An administrative domain can be configured for both the SIP adjacency and the H323 adjacency. However, the H.323 adjacency must be unattached in order to be able to add, delete, or modify the administrative domain.
Examples
The following example shows how to assign the administrative domain to a SIP adjacency:
Related Commands
alias (session border controller)
To configure the endpoint alias of an H.323 adjacency, use the alias command in adjacency H.323 configuration mode. To remove this configuration, use the no form of this command.
Syntax Description
Command Default
Command Modes
Adjacency H.323 configuration (config-sbc-sbe-adj-h323)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to configure the H.323 adjacency h323ToIsp42 endpoint alias to end1:
Related Commands
|
|
|
|---|---|
allow diff-med-sig-vpn
To allow media and signaling to use different VPN IDs in a call leg, use the allow diff-med-sig-vpn command in the session border controller (SBC) configuration mode. To allow media and signaling to use the same VPN ID in a call leg, use the no form of this command.
Syntax Description
Command Default
Command Modes
SBC configuration (config-sbc)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
Ensure that the SBC is deactivated before running the allow diff-med-sig-vpn command.
If the SBC is active and you run the allow diff-med-sig-vpn command, the system issues a warning message, asking you to first deactivate the SBC. You can reactivate the SBC using the activate command.
Use the show run command to display the output of the allow diff-med-sig-vpn command.
Examples
The following example shows how the allow diff-med-sig-vpn command allows media and signaling to use different VPN IDs in a call leg:
allow private info
To configure an H.323 adjacency to allow private information on messages sent out by the adjacency, use the allow private info command in the adjacencyH.323 configuration mode. To disallow private information on messages sent out by the adjacency, use the no form of this command.
Syntax Description
Command Default
By default, the H.323 adjacency does not send private information.
Command Modes
Adjacency H.323 configuration (config-sbc-sbe-adj-h323)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Please note that if you configure the H.323 adjacency to allow private information, then it will allow private information on messages even if the CAC policy is configured to apply privacy service or the user requests privacy service.
Examples
The following example shows how the allow private info command is used to configure an H.323 adjacency to allow private information on messages sent by the adjacency.
Related Commands
|
|
|
|---|---|
Configures an H.323 adjacency to apply privacy restriction on outbound messages if the user requests it. |
associate dspfarm profile
To associate the session border controller (SBC) with a digital signal processor (DSP) farm profile, use the associate dspfarm profile command in the SBC and SBC-DBE configuration modes. To remove the association with a DSP farm profile, use the no form of this command.
associate dspfarm profile { profile-number | all }
no associate dspfarm profile { profile-number | all }
Syntax Description
The SBC picks one of the DSP farm profiles associated with the SBC for its transcoding session. |
Command Default
Command Modes
SBC and SBC-DBE configuration (config-sbc-dbe)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section that follows shows the hierarchy of the modes required to run the command.
Examples
The following example shows how to associate the SBC with a DSP farm profile using the associate dspfarm profile command in the SBC-DBE mode:
attach-controllers (session border controller)
To configure a DBE to attach to an H.248 controller, use the attach-controllers command in VDBE configuration mode. To detach the DBE from its controller, use the no form of this command.
Syntax Description
Command Default
Command Modes
VDBE configuration mode (config-sbc-dbe-vdbe)
Command History
|
|
|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
The attachment and detachment of the DBE from its controller does not always complete immediately. To view the current attachment status, use the show sbc dbe controllers command.
Examples
In a configuration where the DBE has been created and controllers have been configured, the following example shows how to attach the DBE to a controller in VDBE configuration mode:
Related Commands
|
|
|
|---|---|
Configures a virtual data border element (vDBE) and enters the VDBE configuration mode. |
|
Lists the media gateway controllers configured on each vDBE and its controller address. |
attach (H.248 BAC)
To set the Border Access Controller (BAC) adjacency state to Attached, use the attach command in the H248 BAC adjacency configuration mode. To set the BAC adjacency state to Detached, use the no form of this command.
Syntax Description
Command Default
Command Modes
H248 BAC adjacency configuration (config-h248-bac-adj)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Examples
The following example shows how the attach command is used to set the BAC adjacency state:
attach (Rf billing)
To attach an origin realm or an origin host to a Rf billing on an Element (SBE), use the attach command in the SBC SBE billing Rf configuration mode. To detach an origin realm or an origin host to a Rf billing on an SBE, use the no form of this command.
Syntax Description
Defaults
Command Modes
SBC SBE billing Rf configuration (config-sbc-sbe-billing-rf)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Examples
The following example shows how to attach the an origin realm to an Rf billing on an SBE:
attach (session border controller)
To attach an adjacency to an account on an SBE, use the attach command in the appropriate configuration mode. To detach the adjacency from an account on an SBE, use the no form of this command.
no attach force [abort | normal]
Syntax Description
Command Default
Command Modes
Adjacency H.323 configuration (config-sbc-sbe-adj-h323)
Adjacency SIP configuration (config-sbc-sbe-adj-sip)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
You can only modify adjacencies when the adjacency is detached. Before modifying an adjacency, you can detach the adjacency first with the no attach command. The adjacency stays in the going down state when a call is active or when the ping enable feature is running. During this state, existing calls are not torn down and new calls are not accepted. The adjacency does not go to detached state until all calls have ended. An adjacency cannot be attached until the adjacency is in detached state.
If you wish to override the option to wait till active calls on the adjacency end, the adjacency can be detached immediately using the following commands:
- no attach force abort—Executes a forced detach, tearing down calls without signaling their end.
- no attach force normal—Executes a forced detach, tearing down calls gracefully.
To check the state of the adjacency, you can use the show sbc sbe adjacencies command.
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to attach the H.323 adjacency to h323ToIsp42:
audit (H.248 BAC)
To force the Border Access Controller (BAC) to send an audit to an H.248 terminal device, ignoring the audit initiated by the H.248 terminal device, use the audit force command in the H248 BAC adjacency configuration mode. To auto audit (default), which means the BAC will not send an audit to an H.248 terminal device if the audit initiated by the H.248 terminal device is received within the audit interval, use the no form of this command.
To change the audit interval in the BAC, use the audit interval command in the H248 BAC adjacency configuration mode. To return to the default value, use the no form of this command.
no audit {force | interval idle time }
Syntax Description
Forces the H.248 BAC to send an audit to the terminal devices. Default is auto audit. |
|
Audit time interval, in seconds. The range is from 0 to 3600. The default value is 60. |
Command Default
Command Modes
H248 BAC adjacency configuration (config-h248-bac-adj)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
This command can be configured only in the access adjacency submode and not in the core adjacency submode.
Examples
The following example shows how the audit force command forces the BAC to send an audit to the H.248 terminal devices:
The following example shows how the audit interval command is used to change the audit interval in the BAC:
authentication mode (session border controller)
To configure the authentication mode for a SIP adjacency, use the authentication mode command in the adjacency SIP configuration mode. To deconfigure the authentication mode, use the no form of this command.
authentication mode { local | remote }
no authentication mode { local | remote }
Syntax Description
Command Default
Command Modes
Adjacency SIP configuration (config-sbc-sbe-adj-sip)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how the authentication mode command is used to configure the SIP adjacency for local authentication:
Related Commands
|
|
|
|---|---|
Configures the authentication nonce timeout for a SIP adjacency. |
authentication (session border controller)
To configure the H.323 adjacency authentication, use the authentication command in the adjacency H.323 configuration mode. To deconfigure the H.323 adjacency authentication mode, use the no form of this command.
Syntax Description
The authentication type; currently this can only be endpoint. |
Command Default
Command Modes
Adjacency H.323 configuration (config-sbc-sbe-adj-h323)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
This command causes the SBC to authenticate itself with a Gatekeeper. The gatekeeper is responsible for performing the endpoint authentication.
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following command sets H.323 adjacency "h323ToIsp42" to use endpoint authentication.
bandwidth-fields mandatory
To set the bandwidth description of Session Description Protocol (SDP) as mandatory, use the bandwidth-fields mandatory command in Virtual Data Border Element (VDBE) configuration mode. To set the bandwidth description as optional, use the no form of this command.
Syntax Description
Command Default
The default behaviour is that the bandwidth description of SDP is optional.
Command Modes
VDBE configuration (config-sbc-dbe-vdbe)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in a user group that is associated with a task group that includes the proper task IDs. To use this command, you must be in the correct configuration mode and submode. The Examples section that follows shows the hierarchy of the modes and submodes required to run the command.
Examples
The following example shows how to set the bandwidth description of the SDP as mandatory in the VDBE configuration mode:
Related Commands
|
|
|
|---|---|
bandwidth (session border controller)
To configure the maximum and minimum bandwidth limits for media calls, use the bandwidth command in codec definition mode mode. To return the bandwidth to the default value, use the no form of this command.
bandwidth bandwidth-value [ min bandwidth-value ]
no bandwidth bandwidth-value [ min bandwidth-value ]
Syntax Description
Command Default
Command Modes
Codec definition mode (config-sbc-sbe-codec-def)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
This command configures the bandwidth for the analog-to-digital codec (enCOder/DECoder) hardware. The codec name must be one of the system codecs that SBC can recognize. To see a list of the system codecs, use the show sbc sbc sbe codecs command.
The minimum bandwidth setting is for use with the media police degrade command. It specifies the minimum acceptable bandwidth for the video codec. If the available bandwidth is smaller than the configured min bandwidth-value , the call is rejected under the degrade policy. The minimum bandwidth setting applies only to the unidirectional bandwidth of the media stream, and does not include the packet overhead.
The bandwidth min command specifies the unidirectional, minimum bandwidth limit bandwidth and does not include packet overhead.
Examples
The following example shows how to configure the maximum bandwidth limit to 400,000 bps for media calls:
The following example shows how to configure the minimum bandwidth limit to 328,000 bps, specifically for video type media calls:
Related Commands
batch-size
To configure the batching or grouping of RADIUS messages sent to a RADIUS server, use the batch command in the packetcable-em configuration mode. To disable the batch, use the no form of this command.
Syntax Description
Specifies the batch size in bytes. The range is 0 through 4096. |
Command Default
Command Modes
Packet-cable em configuration (config-sbc-sbe-billing-packetcable-em)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
A value of 0 indicates no batching. A platform may choose to set a non-zero default value (this may increase performance.)
Examples
The following example shows how to configure the maximum size of a batch of CDRs:
Related Commands
batch-time
To configure the maximum number of milliseconds for which any record is held before the batch is sent, use the batch-time command in the packetcable-em configuration mode. To disable the waiting period, use the no form of this command.
Syntax Description
Specifies the batch time in milliseconds. The range is 1 through 3600000. |
Command Default
Command Modes
Packet-cable em configuration (config-sbc-sbe-billing-packetcable-em)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to configure the maximum number of milliseconds for which any record is held before the batch is sent:
Related Commands
bgp additional-paths select
To have the system calculate a second BGP bestpath, use the bgp additional-paths select command in address family configuration mode. To remove this mechanism for calculating a second bestpath, use the no form of the command.
bgp additional-paths select { best-external [ backup ] | backup }
no bgp additional-paths select
Syntax Description
(Optional) Calculates a second bestpath from among those received from external neighbors. Configure this keyword on a PE or RR. This keyword enables the BGP Best External feature on an RR. |
|
Command Default
Command Modes
Address family configuration (config-router-af)
Command History
|
|
|
|---|---|
Usage Guidelines
The BGP Diverse Path feature can be enabled on a route reflector to calculate a bestpath and an additional path per address family.
Computation of a diverse path per address family is triggered by any of the following commands:
The bgp additional-paths install command will install the type of path that is specified in the bgp additional-paths select command Either the best-external keyword or the backup keyword is required; both keywords can be specified. If both keywords ( best-external and backup ) are specified, the system will install a backup path.
Examples
In the following example, the system computes a second best path from among those received from external neighbors:
Related Commands
bgp bestpath igp-metric ignore
To have the system ignore the Interior Gateway Protocol (IGP) metric during BGP best path selection, use the bgp bestpath igp-metric ignore command in address family configuration mode. To remove the instruction to ignore the IGP metric, use the no form of this command.
bgp bestpath igp-metric ignore
no bgp bestpath igp-metric ignore
Syntax Description
Command Default
Command Modes
Address family configuration (config-router-af)
Command History
|
|
|
|---|---|
Usage Guidelines
The IGP metric is a configurable metric for EIGRP, IS-IS, or OSPF that is related to distance. The bgp bestpath igp-metric ignore command can be used independently, or in conjunction with the BGP Diverse Path feature. This command does not enable the BGP Diverse Path feature.
Similarly, enabling the BGP Diverse Path feature does not necessarily require that the IGP metric be ignored. If you enable the BGP Diverse Path feature and the RR and its shadow RR are not co-located, this command must be configured on the RR, shadow RR, and PE routers.
This command is supported in the following address families:
Note
This command is not supported per VRF; if you use it per VRF, it is at your own risk. This command is not supported per VRF; if you use it per VRF, it is at your own risk.
This command applies per VRF as follows (which is consistent with the BGP PIC/Best External feature):
- When configured under address-family vpnv4 or vpnv6, it applies to all VRFs, but it will be nvgened only under vpnv4/vpnv6 global.
- When configured under a particular VRF, it applies only to that VRF and will be nvgened only for that VRF.
- When configured under vpnv4 or vpnv6 global, this command can be disabled for a particular VRF by specifying no bgp bestpath igp-metric ignore . The no form will be nvgened under that VRF, while under vpnv4 or vpnv6 bgp bestpath igp-metric ignore is nvgened and the command applies to all other VRFs.
Examples
In the following example, the IGP metric is ignored during calculation of the BGP best path:
Related Commands
|
|
|
|---|---|
bgp consistency-checker
To enable the BGP Consistency Checker feature, use the bgp consistency-checker command in router configuration mode. To disable the BGP Consistency Checker feature, use the no form of this command.
bgp consistency-checker { error-message | auto-repair } [ interval minutes ]
Syntax Description
Command Default
Command Modes
Router configuration (config-router)
Command History
|
|
|
|---|---|
Usage Guidelines
A BGP route inconsistency with a peer occurs when an update or a withdraw is not sent to a peer, and black-hole routing can result. The BGP consistency checker feature is a low-priority process created to address this issue. This feature performs nexthop-label, RIB-out, and aggregation consistency checks. When BGP consistency checker is enabled, it is performed for all address families. Once the process identifies such an inconsistency:
- If the error-message keyword is specified, the system will report the inconsistency with a syslog message, and will also perform forceful aggregation reevaluation in the case of an aggregation inconsistency.
- If the auto-repair keyword is specified, the system will report the inconsistency with a syslog message and also take appropriate action, such as a route refresh request or an aggregation reevaluation, depending on the type of inconsistency.
Examples
In the following example, BGP consistency checker is enabled. If a BGP route inconsistency is found, the system will send a syslog message and take appropriate action.
Related Commands
|
|
|
|---|---|
Displays routes that have nexthop-label inconsistency found by BGP consistency checker. |
bgp refresh max-eor-time
To cause the router to generate a Route-Refresh End-of-RIB (EOR) message if it was not able to generate one due to route flapping, use the bgp refresh max-eor-time command in router configuration mode. To disable the timer, use the no form of this command.
bgp refresh max-eor-time seconds
Syntax Description
Number of seconds after which, if the router was unable to generate a Route-Refresh EOR message due to route flapping, the router generates a Route-Refresh EOR message. |
Command Default
Command Modes
Router configuration (config-router)
Command History
|
|
|
|---|---|
Usage Guidelines
The BGP Enhanced Route Refresh feature is enabled by default. The bgp refresh max-eor-time command is not needed under normal circumstances. You might configure the bgp refresh max-eor-time command in the event of continuous route flapping, when the router is unable to generate a Route-Refresh EOR message, in which case a Route-Refresh EOR is generated after the timer expires.
Examples
In the following example, if no Route-Refresh EOR message is received after 800 seconds, stale routes will be removed from the BGP table. If no Route-Refresh EOR message is generated after 800 seconds, one is generated.
Related Commands
|
|
|
|---|---|
Causes the router to remove stale routes from the BGP table even if the router does not receive a Route-Refresh EOR message. |
bgp refresh stalepath-time
To cause the router to remove stale routes from the BGP table even if the router does not receive a Route-Refresh EOR message, use the bgp refresh stalepath-time command in router configuration mode. To disable the timer, use the no form of this command.
bgp refresh stalepath-time seconds
Syntax Description
Number of seconds the router waits to receive a Route-Refresh End-of-RIB (EOR) message, and then removes the stale paths from BGP table if the router hasn’t received an EOR message. |
Command Default
Command Modes
Router configuration (config-router)
Command History
|
|
|
|---|---|
Usage Guidelines
The BGP Enhanced Route Refresh feature is enabled by default. The bgp refresh stalepath-time command is not needed under normal circumstances. You might configure the bgp refresh stalepath-time command in the event of continuous route flapping, when the router does not receive a Route-Refresh EOR after an Adj-RIB-Out, in which case the router removes the stale routes from the BGP table after the timer expires. The stale path timer is started when the router receives a Route-Refresh SOR.
Examples
In the following example, if no Route-Refresh EOR message is received after 800 seconds, stale routes will be removed from the BGP table. If no Route-Refresh EOR message is generated after 800 seconds, one is generated.
Related Commands
|
|
|
|---|---|
Causes the router to generate a Route-Refresh EOR message if it was not able to generate one due to route churn. |
billing
To configure billing, use the billing command in SBE configuration mode. Use the no form of this command to remove all the billing configuration.
Syntax Description
Command Default
Command Modes
SBE configuration (config-sbc-sbe)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to enter the billing mode for mySbc:
Related Commands
|
|
|
|---|---|
Activates the billing functionality after configuration is committed. |
|
Configures the time of day (local time) to run the Long Duration Check (LDR). |
|
billing (CAC)
To configure billing, use the billing command in the CAC table entry configuration mode. To unconfigure the billing configuration, use the no form of this command.
billing { filter { disable | enable } | methods { packetcable-em | xml }}
no billing { filter | methods { packetcable-em | xml }}
Syntax Description
Specifies whether the billing filter scheme is enabled or disabled. |
|
Specifies the billing methods that are allowed for calls relating to different adjacencies. |
|
Command Default
Command Modes
CAC table entry configuration (config-sbc-sbe-cacpolicy-cactable-entry)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to enter the billing mode for mySbc:
Related Commands
blacklist
To enter the mode for configuring the event limits of a given source, use the blacklist command in the SBE configuration mode. To return the event limits to the default values, use the no form of this command.
[ no ] blacklist [ critical ] global [address-default | { ipv4 { addr } | ipv6 { addr }} [ tcp { tcp-port } | udp { udp-port } | default-port-limit] ]
[ no ] blacklist [ critical ] vpn { vpn-name } [ address-default [ address-family { ipv4 | ipv6 }] | address-family { ipv4 | ipv6 } | ipv4 addr [ tcp { tcp-port } | udp { udp-port } | default-port-limit ] | ipv6 addr [ tcp { tcp-port } | udp { udp-port } | default-port-limit ] ]
Syntax Description
Command Default
Command Modes
SBE configuration (config-sbc-sbe)
Command History
Usage Guidelines
For IPv4, either “global” or “vpn_name” must be specified for the blacklist. However, if a vpn_name is entered, a VPN token is required.
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how the vpn keyword and the VPN token of 800 are used to enter the mode for configuring the event limits for the VPN test:
The following example shows how to enter the mode for configuring the default event limits for all addresses:
The following example shows how to enter the mode for configuring blacklisting to apply to all addresses:
The following example shows how to enter the mode for applying blacklisting options to a single IPv4 IP address:
The following example shows how to enter the mode for applying blacklisting options to a single IPv6 IP address:
The following example shows how to enter the mode for applying blacklisting options to an IPv6 address family in a VPN:
Related Commands
blacklist (profile)
To set a profile to be blacklisted, use the blacklist command in the appropriate profile configuration mode. To remove blacklist from this profile, use the no form of this command.
Syntax Description
Command Default
Command Modes
SIP Method Profile configuration (config-sbc-sbe-mep-mth)
SIP Option Profile configuration (config-sbc-sbe-mep-opt)
SIP Header Profile configuration (config-sbc-sbe-mep-hdr)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of the modes required to run the command.
Examples
The following example shows how to blacklist an option profile:
The following example shows how to blacklist a method profile:
The following example shows how to blacklist a header profile:
Related Commands
|
|
|
|---|---|
blacklist (sip-opt)
To set profile to be blacklisted, use the blacklist command in SIP option mode. Use the no form of this command to remove blacklist from this profile.
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command:
Examples
The following example shows how to add an option to the profile.
blended-codec-list
To add a blended codec list, use the blended-codec-list command in SBC SBE CAC policy CAC table entry configuration mode. To remove a blended codec list, use the no form of this command.
blended-codec-list blended-codec-li st
no blended-codec-list blended-codec-li st
Syntax Description
Case-sensitive, unique name for a blended codec list. The maximum length is 63 characters. |
Defaults
Command Modes
SBC SBE CAC policy CAC table entry configuration mode (config-sbc-sbe-cacpolicy-cactable-entry)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Examples
The following example shows how to configure a blended codec list:
Related Commands
|
|
|
|---|---|
blended-transcode
To enable the Blended Transcoding feature, use the blended-transcode command in the SBC SBE CAC policy CAC table entry configuration mode. To disable the Blended Transcode feature, use the no form of this command.
Syntax Description
Defaults
Command Modes
SBC SBE CAC policy CAC table entry configuration mode (config-sbc-sbe-cacpolicy-cactable-entry)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Examples
The following example shows how to enable the Blended Transcode feature:
Related Commands
|
|
|
|---|---|
body-editor
To associate a body editor to a SIP adjacency to cause the body editor to act on the incoming and outgoing SIP messages, use the body-editor command in the Adjacency SIP configuration mode. To remove a body editor, use the no form of this command.
body-editor [inbound | outbound] {editor-name}
no body-editor [inbound | outbound] {editor-name}
Syntax Description
Command Default
Command Modes
Adjacency SIP configuration (config-sbc-sbe-adj-sip)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of the modes required to run the command.
Examples
The following example shows how to associate two body editors, inbound editor2 and outbound editor1, at a SIP adjacency level for the adj-1 adjacency:
Related Commands
|
|
|
|---|---|
Sets the action to be taken on a body type in a SIP body editor for a non-SDP message body. |
|
body-editor (method)
To add a body editor to act on a method, use the body-editor command in the signaling border element (SBE) SIP method element configuration mode. To remove a body editor, use the no form of this command.
Syntax Description
Command Default
Command Modes
SBE SIP method element configuration (config-sbc-sbe-mep-mth-ele)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of the modes required to run the command.
Examples
The following example shows how the body-editor command adds a body editor to act on a method:
Related Commands
|
|
|
|---|---|
body-profile
To associate a body profile to a method profile to cause the body profile to act on incoming and outgoing SIP messages, use the body-profile command in SBE method profile element configuration mode. To remove the body profile, use the no body-profile command.
no body-profile {profile_name}
Syntax Description
Command Default
Command Modes
SBE method profile element configuration mode (config-sbc-sbe-sip-mth-ele)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
After creating a body profile with the sip body-profile {profile_name} command, you can associate the body profile at the following additional levels and configuration modes:
- At the SIP signaling entity level (ingress or egress), under SBE mode, using the sip default body-profile [[inbound|outbound] {profle_name}] command. The body profile is associated for the entire signlaing instance (that is all messages, either ingress or egress, passing through the SBC).
- SIP adjacency level, under SIP adjacency mode, using the body-profile [[inbound|outbound] {profle_name}] command. The body profile is associated to an adjacency.
SBC uses a body profile that you create and associate to filter non-SDP bodies from incoming and outgoing SIP messages, based on the Content-Type header field. A body profile allows a message containing a specific non-SDP body to be either passed (without altering the message), stripped of the body (and pass the rest of the message), or be rejected.
Examples
The following example describes how to associate body profile, bodyprofile1, to a method profile:
Related Commands
body-profile (sip adj)
To associate a body profile to a SIP adjacency to cause the body profile to act on incoming and outgoing SIP messages, use the body-profile (sip adj) command in adjacency SIP configuration mode. To remove the body profile, use the no body-profile (sip adj) command.
body-profile [inbound | outbound] {profile_name}
no body-profile [inbound | outbound] {profile_name}
Syntax Description
Command Default
Command Modes
Adjacency SIP configuration (config-sbc-sbe-adj-sip)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
After creating a body profile with the sip body-profile {profile_name} command, you can associate the body profile at the following additional levels and configuration modes:
- At the SIP signaling entity level (ingress or egress), under SBE mode, using the sip default body-profile [[inbound|outbound] {profle_name}] command. The body profile is associated for the entire signlaing instance (that is all messages, either ingress or egress, passing through the SBC).
- At SIP method profile level, under method profile mode, using the body-profile {profle_name} command. The body profile is associated to a method profile.
SBC uses a body profile that you create and associate to filter non-SDP bodies from incoming and outgoing SIP messages, based on the Content-Type header field. A body profile allows a message containing a specific non-SDP body to be either passed (without altering the message), stripped of the body (and pass the rest of the message), or be rejected.
Examples
The following example describes how to associate two body profiles, inbound profile2 and outbound profile1, at the SIP adjacency level for adjacency adj-1:
Related Commands
body
To name the body type or content header type for a non-SDP message body that is part of the body profile, use the body command in SBE SIP Body configuration mode. To remove the body type or content header type, use the no body command.
Syntax Description
Command Default
Command Modes
SBE SIP Body configuration (config-sbc-sbe-sip-body)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
This command describes the body type or content header type for SBC to act on messages with the specified body type or content header type.
The body command is used in conjunction with the sip body-profile command that is used to create the body profile.
The body name must be in the form of <media-type>/<media-sub-type>, for example, application/ISUP. The body name field is case-insensitive.
Asterisk (*) is used to match all non-SDP body types. Note that * is also interpreted as a string by the CLI, and is just a token used to indicate wild-card match.
The following Content-Type descriptions are not allowed: application/sdp and multipart/mixed
Only one body element with such a wildcard can co-exist with other bodies per body profile. The wildcard body is applied if there is no other matching body in that profile. The body name is matched using regular ‘string compare.’ Note that there is no provision to match body names using any regular expression matching techniques.
Examples
The following example does the following: creates a body profile named bodyprofile1; describes the body type, that is to act on messages with Content-Type header “application/ISUP”; and instructs SBC to strip that particular message body and pass the rest of the message:
Related Commands
body (editor)
To name a body type or content header type for a non-SDP message body that is a part of the body editor, use the body command in the signaling border element (SBE) session initiation protocol (SIP) body configuration mode. To remove a body type or content header type, use the no form of this command.
Syntax Description
Command Default
Command Modes
SIP Body Editor configuration (config-sbc-sbe-mep-bdy)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
This command describes the body type or content header type for the SBC to act on messages of the specified body type or content header type.
The body command is used in conjunction with the sip body-editor command that is used to create the body editor.
The body name must be in the form <media-type>/<media-sub-type>, for example, application/ISUP. The body name field is case-insensitive.
Asterisk (*) is used to match all the non-SDP body types. Note that * is also interpreted as a string by the CLI, and is a token used to indicate wildcard match.
Examples
The following example shows how to create a body editor named bodyeditor1 and describe the body type as application/ISUP:
Related Commands
|
|
|
|---|---|
Creates a body editor to filter the non-SDP message bodies from the incoming and outgoing SIP messages. |
branch bandwidth-field
To configure the SBC such that it converts a specific bandwidth line format into another bandwidth line format in the outbound Session Description Protocol (SDP) sent to a caller or a callee, use the branch bandwidth-field command in the CAC table entry configuration mode. To unconfigure the conversion of the bandwidth line format, use the no form of this command.
branch bandwidth-field {as-to-tias | tias-to-as}
no branch bandwidth-field {as-to-tias | tias-to-as}
Syntax Description
Command Default
The default is that the format of bandwidth lines is not converted.
Command Modes
CAC table entry configuration (config-sbc-sbe-cacpolicy-cactable-entry)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
The SBC applies the outgoing bandwidth line format that you configure. If the offerer-side adjacency is configured to apply a specific style of bandwidth line format in the SDP, this command causes the SBC to convert the answer to the specified format before it is sent back to the offerer. If there are multiple bandwidth lines, only the first line is converted into the specified bandwidth line and the remaining lines are ignored.
Note As mentioned earlier, the default is that the bandwidth line is not converted from one format to another. However, if the callee is configured to convert the bandwidth, and the message is converted, the response that is sent back to the caller is converted back even if this command is not configured for the caller.
Examples
The following example shows how to configure the SBC such that it converts an AS bandwidth line format into a TIAS bandwidth line format in the outbound SDP sent to a caller or a callee:
Related Commands
branch codec
To configure the codec options for a caller or a callee, use the branch codec command in the CAC table entry configuration mode. To unconfigure the codec options, use the no form of this command.
branch codec {convert | profile profile-name }
no caller codec {convert | profile }
Syntax Description
Command Default
By default, codec variant conversion is disabled, and no codec variant profile is specified.
Command Modes
CAC table entry configuration (config-sbc-sbe-cacpolicy-cactable-entry)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of the modes required to run the command.
Examples
The following example shows how to configure the codec options for a caller using the branch codec command:
Related Commands
|
|
|
|---|---|
branch codec-list
To specify the codecs that the caller or the callee of a call can use, use the branch codec-list command in the CAC table entry configuration mode. To delete a codec list, use the no form of this command.
no branch codec-list list-name
Syntax Description
Command Default
Command Modes
CAC table entry configuration (config-sbc-sbe-cacpolicy-cactable-entry)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to enter a mode to create the test codec list:
Related Commands
|
|
|
|---|---|
branch hold-setting
To specify the caller hold settings or the callee hold settings, use the branch hold-setting command in the CAC table entry configuration mode. To remove the caller hold settings or the callee hold settings, use the no form of this command.
branch hold-setting {hold-c0 | hold-c0-inactive | hold-c0-sendonly | hold-sendonly | standard}
no branch hold-setting {hold-c0 | hold-c0-inactive | hold-c0-sendonly | hold-sendonly | standard}
Syntax Description
Command Default
Command Modes
CAC table entry configuration (config-sbc-sbe-cacpolicy-cactable-entry)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to use the branch hold-setting command:
Related Commands
|
|
|
|---|---|
branch inband-dtmf-mode
To configure the dual-tone multifrequency (DTMF) in-band mode for the caller side or the callee side, use the branch inband-dtmf-mode command in the CAC table entry configuration mode. To unconfigure the DTMF in-band mode, use the no form of this command.
branch inband-dtmf-mode { always | inherit | maybe | never }
Syntax Description
Command Default
Command Modes
CAC table entry configuration (config-sbc-sbe-cacpolicy-cactable-entry)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of the modes required to run the command.
Examples
The following example shows how to configure the DTMF in-band mode for the caller side using the caller inband-dtmf-mode command in the CAC table entry configuration mode so that the endpoint never uses the inband DTMF mode:
Related Commands
|
|
|
|---|---|
branch inbound-policy
To configure a caller inbound SDP policy table or a callee inbound SDP policy table, use the branch inbound-policy command in the CAC table entry configuration mode. To unconfigure an inbound SDP policy table, use the no form of this command.
branch inbound-policy sdp-policy-table-name
no branch inbound-policy sdp-policy-table-name
Syntax Description
Command Default
Command Modes
CAC table entry configuration (config-sbc-sbe-cacpolicy-cactable-entry)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to use the branch inbound-policy command to configure an inbound SDP policy table:
Related Commands
|
|
|
|---|---|
branch media bypass
To enable or disable the Multiple SBC Media Bypass feature on the caller side or the callee side, use the branch media bypass command in the CAC table entry configuration mode. To unconfigure the Multiple SBC Media Bypass feature, use the no form of this command.
branch media bypass { enable | disable }
Syntax Description
Enables the Multiple SBC Media Bypass feature on the caller side or the callee side. |
|
Disables the Multiple SBC Media Bypass feature on the caller side or the callee side. |
Command Default
Command Modes
CAC table entry configuration (config-sbc-sbe-cacpolicy-cactable-entry)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of the modes required to run the command.
Examples
The following example shows how to use the branch media bypass command to enable the Multiple SBC Media Bypass feature:
Related Commands
|
|
|
|---|---|
branch media-caps
To configure a codec list used to announce media capabilities on behalf of a SIP caller or SIP callee in a SIP-to-H.323 or H.323-to-SIP interworking call, use the branch media-caps command in the CAC table entry configuration mode. To unconfigure the codec list, use the no form of this command.
branch media-caps media-caps-list-name
no branch media-caps media-caps-list-name
Syntax Description
Command Default
Command Modes
CAC table entry configuration (config-sbc-sbe-cacpolicy-cactable-entry)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
This command configures a codec list and assigns the list to a CAC table. After a codec list is assigned, it must not be deleted before it is removed from the CAC table. A codec list must exist before it can be assigned to an entry in a CAC table.
Examples
The following example shows how to configure the caller-media-caps-list codec list and assign the list to the cac-tbl-1 CAC table in entry 1:
Related Commands
branch media-description disabled
To configure how the SBC handles disabled media descriptions for a caller or a callee, use the branch media-description disabled command in the CAC table entry configuration mode. To unconfigure how the SBC handles disabled media descriptions for a caller or a callee, use the no form of this command.
branch media-description disabled {strip {answer | offer {all | new}} | {pad offer}}
no branch media-description disabled {strip {answer | offer {all | new}} |{pad offer}}
Syntax Description
Strips the disabled media description lines from offers when this keyword is used with the strip keyword. Pads offers with dummy disabled media description lines when used with pad. |
|
Command Default
Command Modes
CAC table entry configuration (config-sbc-sbe-cacpolicy-cactable-entry)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to configure the removal of disabled media streams from new forwarded offers:
The following example shows how to configure the removal of disabled media streams from forwarded offers, regardless of whether it is known to the recipient of the offer:
The following example shows how to configure the removal of disabled media streams from forwarded answers:
The following example shows how to configure the SBC so that it does not pad forwarded offers with disabled media streams:
Related Commands
|
|
|
|---|---|
Configures how the SBC handles disabled media descriptions for a callee. |
|
Configures how the SBC handles disabled media descriptions for a caller. |
branch media-type
To configure the media address type settings for a caller or a callee, use the branch media-type command in the CAC table entry configuration mode. To unconfigure the media address type settings for a caller, use the no form of this command.
branch media-type { ipv4 | ipv6 | inherit | both }
no branch media-type { ipv4 | ipv6 | inherit | both }
Syntax Description
Specifies that the supported media IP address type from earlier CAC policy entries must be inherited. This is the default setting. |
|
Specifies that both IPv4 and IPv6 media addresses are supported. |
Command Default
The default is that the supported media IP address type from earlier CAC policy entries must be inherited.
Command Modes
CAC table entry configuration (config-sbc-sbe-cacpolicy-cactable-entry)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to use the branch media-type command to specify that only IPv4 media addresses are supported:
Related Commands
|
|
|
|---|---|
branch outbound-policy
To configure an outbound Session Description Protocol (SDP) policy table for a caller or a callee, use the branch outbound-policy command in the CAC table entry configuration mode. To unconfigure an outbound SDP policy table, use the no form of this command.
branch outbound-policy table-name
no branch outbound-policy table-name
Syntax Description
Command Default
Command Modes
CAC table entry configuration (config-sbc-sbe-cacpolicy-cactable-entry)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to configure an outbound SDP policy table for a caller:
Related Commands
|
|
|
|---|---|
branch port-range-tag
To configure the port range tag for a caller or a callee that is used when selecting a media address and port, use the branch port-range-tag command in the CAC table entry configuration mode. To unconfigure the port range tag, use the no form of this command.
branch port-range-tag { adjacency-name | none | string tag-string }
Syntax Description
Prompts the SBC to not use a port range tag for calls matching the CAC entry, and removes any previously found strings. |
|
Command Default
Command Modes
CAC table entry configuration (config-sbc-sbe-cacpolicy-cactable-entry)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of the modes required to run the command.
Examples
The following example shows how to use the branch port-range-tag command to configure a port range tag:
Related Commands
|
|
|
|---|---|
branch privacy edit-privacy-request
To edit and update privacy indications provided by a user, use the branch privacy edit-privacy-request command in the CAC table configuration mode. To remove the indications, use the no form of this command.
branch privacy edit-privacy-request { pass | strip | insert | replace | sip { strip { all | critical | header | id | none | session | token word | user } | insert { critical | header | id | none | session | token word | user }}}
no branch privacy edit-privacy-request { pass | strip | insert | replace | sip { strip { all | critical | header | id | none | session | token word | user } | insert { critical | header | id | none | session | token word | user }}}
Syntax Description
Command Default
Command Modes
CAC table configuration (config-sbc-sbe-cacpolicy-cactable)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to configure an entry to remove all the privacy restrictions from the SIP and H323 adjacencies in the MyCacTable admission control table:
Related Commands
|
|
|
|---|---|
Edits and updates privacy indications provided by a user, from the callee side. |
|
Edits and updates privacy indications provided by a user, from the caller side. |
branch privacy privacy-service
To apply privacy settings according to RFC3323, RFC3325, and the H.323 presentation restriction settings in the admission control table, use the branch privacy privacy-service command in the CAC table configuration mode. To unconfigure the privacy settings, use the no form of this command.
branch privacy privacy-service { adj-trust-boundary | always | never }
no branch privacy privacy-service
Syntax Description
Command Default
Command Modes
CAC table configuration (config-sbc-sbe-cacpolicy-cactable)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to configure an entry to provide privacy service indefinitely in the MyCacTable admission control table:
Related Commands
branch ptime
To configure the packetization time on the caller side or the callee side, use the branch ptime command in the CAC table configuration mode. To unconfigure the packetization time setting, use the no form of this command.
branch ptime packetization-time
no branch ptime packetization-time
Syntax Description
Packetization time, in milliseconds. The range is from 0 to 100. The default is 0. |
Command Default
The default packetization time is 0 milliseconds. This value indicates that transrating must not be performed.
Command Modes
CAC table entry configuration (config-sbc-sbe-cacpolicy-cactable-entry)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of the modes required to run the command.
Examples
The following example shows how to configure the packetization time to 30 milliseconds by using the branch ptime command:
Related Commands
|
|
|
|---|---|
branch secure-media
To apply the granular-level Secure Media feature on the caller side or the callee side, use the branch secure-media command in the CAC table entry configuration mode. To remove the granular-level Secure Media feature, use the no form of this command.
Syntax Description
Command Default
By default, the granular-level (Unsignaled) Secure Media feature is disabled.
Command Modes
CAC table entry configuration (config-sbc-sbe-cacpolicy-cactable-entry)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of the modes required to run the command.
We recommend that you use the granular-level Secure Media feature instead of enabling Secure Media globally. The granular-level feature enables you to specify the calls and adjacencies at the location where you want to use secure media.
Examples
The following example shows an Unsignaled Secure Media configuration where the two SIP adjacencies for both legs of the call are configured for security trusted-unencrypted, and both the caller and the callee sides are configured for secure media in a CAC table entry:
Related Commands
|
|
|
|---|---|
Configures the granular-level Secure Media feature on the callee side. |
|
Configures the granular-level Secure Media feature on the caller side. |
branch sig-qos-profile
To configure the Quality of Service (QoS) profile to be used for signaling packets sent to the original caller or callee, use the branch sig-qos-profile command in the CAC table entry configuration mode. To unconfigure the QoS profile, use the no form of this command.
caller-sig-qos-profile profile-name
no caller-sig-qos-profile profile-name
Syntax Description
Command Default
Command Modes
CAC table entry configuration (config-sbc-sbe-cacpolicy-cactable-entry)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
This command can be run only at the per-call scope. The CAC policy will not be activated if this command is configured in any other scope.
Packet marking will not be applied until the CAC decision process is run. This means that some initial signaling packets sent to the caller, for example, the SIP 100 provisional response, will not receive any particular Differentiated Services Codepoint (DSCP) marking.
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following command shows how to configure calls from the acme account to use the voice QoS profile enterprise for signaling packets sent from the SBC to the original caller or callee:
Related Commands
branch tel-event payload type
To configure the payload type to be used for the caller or the callee in H.323-SIP interworking calls, use the branch tel-event payload-type command in the CAC entry configuration mode. To unconfigure the payload type setting, use the no form of this command.
branch tel-event payload type payload-type
no branch tel-event payload type
Syntax Description
See RFC 2833 for detailed information about the values of payload-type . The range is from 96 to 127. The default is 101. |
Command Default
Command Modes
CAC entry configuration (config-sbc-cac-entry)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
The branch tel-event payload type command enables support for dual tone multifrequency (DTMF) H.323-SIP interworking. The telephone-event payload type configured by this command is used by the SBC only in situations where the payload type information is not provided by the other side in an H.323-SIP interworking call.
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to use the branch tel-event payload-type command to set the payload type to 101:
Related Commands
|
|
|
|---|---|
Configures the payload type to be used for the callee in H.323-SIP interworking calls. |
|
Configures the payload type to be used for the caller in H.323-SIP interworking calls. |
branch video-qos-profile
To configure the QoS profile to be used for the media packets sent to the original caller or original callee, use the branch video-qos-profile command in the CAC table configuration mode. To remove this configuration, use the no form of this command.
branch video-qos-profile profile-name
no branch video-qos-profile profile-name
Syntax Description
Command Default
Command Modes
CAC table configuration (config-sbc-sbe-cacpolicy-cactable)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command. The branch video-qos-profile command can be executed only in the per-call scope. The CAC policy is not activated if this command is configured in any other scope.
Examples
The following example shows how to configure calls from the acme account to use the video QoS profile enterprise for the packets sent from the SBC to the original caller:
Related Commands
|
|
|
|---|---|
Configures the QoS profile to be used for the media packets sent to the original callee. |
|
Configures the QoS profile to be used for the packets sent to the original caller. |
branch voice-qos-profile
To configure the QoS profile to be used for the media packets sent to the original caller or the original callee, use the branch voice-qos-profile command in the CAC table configuration mode. To unconfigure the QoS profile, use the no form of this command.
branch voice-qos-profile profile-name
Syntax Description
Command Default
Command Modes
CAC table configuration (config-sbc-sbe-cacpolicy-cactable)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command. This command can be run only in the per-call scope. The CAC policy is not activated if this command is configured in any other scope.
Examples
The following example shows how to configure the calls from the acme account to use the voice QoS profile enterprise for the packets sent from the SBC:
Related Commands
|
|
|
|---|---|
Configures the QoS profile to be used for the media packets sent to the original callee. |
|
Configures the QoS profile to be used for the media packets sent to the original caller. |
cac-policy-set
To create a new call admission control (CAC) policy set, copy an existing complete policy set, swap the references of a complete policy set to another policy set, or set the averaging period for rate calculations in a CAC policy set, use the cac-policy-set command in the Signaling border element (SBE) configuration mode. To remove a policy set or deconfigure the averaging period, use the no form of this command.
cac-policy-set { policy-set-id | copy { source policy-set-id destination policy-set-id } | swap { source policy-set-id destination policy-set-id } | averaging-period { avg-number avg-period }
no cac-policy-set { policy-set-id | averaging-period { avg-number }}
Syntax Description
Command Default
Command Modes
SBE configuration (config-sbc-sbe)
Command History
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of the modes required to run the command.
Changes are not permitted to the configuration of a global policy set. Also, a policy set cannot be removed if it is a global policy set.
Examples
The following command creates a policy set 1 on mySbc:
Router(config-sbc-sbe)# cac-policy-set swap source 12 destination 22
The following example shows how to set the averaging period for rate calculations in a CAC policy set:
Router(config-sbc-sbe)# cac-policy-set averaging-period 1 100
Related Commands
|
|
|
|---|---|
Lists detailed information pertaining to a CAC policy table. |
cac-policy-set (admin-domain)
To configure the call admission control (CAC) policy set for an administrative domain, use the cac-policy-set command in the Administrative domain configuration mode. To remove a policy set from the administrative domain , use the no form of this command.
Syntax Description
The integer, ranging from 1 to 2147483647, that identifies a complete policy set. |
Command Default
Command Modes
Administrative domain configuration (config-sbc-sbe-ad)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of the modes required to run the command.
A user can specify only one CAC policy set for an administrative domain.
Examples
The following example shows how to configure the CAC policy set for the administrative domain ADMIN1 using the call-policy-set command in an administrative domain configuration mode:
Related Commands
cac-policy-set global
To activate the global call admission control (CAC) policy set within an signaling border element (SBE) entity, use the cac-policy-set global command in the SBE configuration mode.
cac-policy-set global policy-set-id
Syntax Description
Integer identifying the policy set that should be made global. Range is from 1 to 2147483647. |
Command Default
Command Modes
SBE configuration (config-sbc-sbe)
Command History
Usage Guidelines
The active CAC policy set cannot be modified.
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of the modes required to run the command.
Examples
The following example shows how to activate policy set 1 on mySbc:
cac-table
To create or configure an admission control table, use the cac-table command in CAC-policy-set configuration mode. To delete the admission control table , use the no form of this command.
Syntax Description
Command Default
Command Modes
CAC-policy-set configuration (config-sbc-sbe-cacpolicy)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to create the admission control table MyCacTable:
Related Commands
cache-lifetime
To configure the lifetime of any DNS entry, use the cache-lifetime command in the DNS configuration mode. To disable the lifetime, use the no form of this command.
Syntax Description
Command Default
Command Modes
DNS configuration (config-sbc-sbe-dns)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to configure the lifetime of any DNS entry,:
Related Commands
|
|
|
|---|---|
Configures the maximum number of entries that are permitted in the DNS cache. |
|
cache-limit
To configure the maximum number of entries that are permitted in the DNS cache, use the cache-limit command in the DNS configuration mode. To set the limit to 100, use the no form of this command.
Syntax Description
Command Default
Command Modes
DNS configuration (config-sbc-sbe-dns)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to configure limits on DNS entries:
Related Commands
|
|
|
|---|---|
cache (session border controller)
To enable caching and configure call detail record caching parameters on a local disk, use the cache command in the SBE Billing configuration mode. To disable caching and local cache parameters, use the no form of this command.
cache [ path {WORD} | alarm [critical VAL] [major VAL] [minor VAL] | max-size {0-4194303}]
no cache [ path {WORD} | alarm [critical VAL] [major VAL] [minor VAL] | max-size {0-4194303}]
Syntax Description
Command Default
Command Modes
SBE Billing configuration (config-sbc-sbe-billing)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
The Cisco ASR 1000 Series Routers have a local disk where records and event messages can be stored on a local cache. Local cache support is a significant advantage because call detail records and event messages (EMs) are not lost when a billing server is unavailable.
Use the cache command configures parameters for storing call detail records and EMs on local disk as part of Cisco Unified Border Element (SP Edition)’s integrated billing system in the unified model.
The cache path command enables caching and the no cache path command disables caching. You can use the other optional keywords to specify alarm thresholds and how large the cache size is in kilobytes.
Examples
The following example configures billing and enables caching of call detailed records and EMs on the designated hard disk:
The following configuration example shows that the cache file alarm thresholds and maximum size of the local CDR cache file are configured:
The following configuration example shows that caching is enabled on the hard disk:
Related Commands
|
|
|
|---|---|
Activates the billing functionality after configuration is committed. |
|
packetcable-em method-index transport radius RADIUS-client-name |
|
cac-policy-set global
To activate the global call admission control (CAC) policy set within an signaling border element (SBE) entity, use the cac-policy-set global command in the SBE configuration mode. To deactivate the global CAC policy, use the no form of the command.
cac-policy-set global policy-set-id
Syntax Description
Integer identifying the policy set that should be made global. Range is from 1 to 2147483647. |
Command Default
Command Modes
SBE configuration (config-sbc-sbe)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. It replaces the cac-policy-set global command. |
Usage Guidelines
From Release 3.5S onward, an active CAC policy set can be modified.
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of the modes required to run the command.
Examples
The following example shows how to activate policy set 1 on mySbc:
Related Commands
cac-scope
To allow you to choose the scope in which CAC limits are to be applied within each entry in a policy set table, use the cac-scope command in the CAC table entry configuration mode. To unconfigure the scope, use the no form of this command.
cac-scope { list of scope options }
no cac-scope { list of scope options }
Syntax Description
Command Default
Command Modes
CAC table entry configuration (config-sbc-sbe-cacpolicy-cactable-entry)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
|
The sub-category , sub-category-pfx , and subscriber scope options were added. |
|
Usage Guidelines
The cac-scope command allows you to choose a scope in which CAC limits are to be applied within each entry. This command is available only to the entries defined within a Policy Set table type. You can define more than one cac-scope command within an entry.
Use the table-type command to configure a Policy Set table type.
Some CAC scopes can be combined to create compound scopes. The global scope and call scope cannot be combined.
When policy-set is defined as the table type for a CAC table, you must define cac-scope and cac-scope-prefix-len within the entry, for example:
cac-scope sub-category-pfx prefix-len
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to configure the call event at which limits are applied in the TAB1 CAC policy-set table:
Related Commands
|
|
|
|---|---|
Configures a CAC table type that enables the priority of the call to be used as a criterion in the CAC policy. |
calc-moscqe
To specify the percentage of calls that must be used to calculate the MOS-CQE score, use the calc-moscqe command in the adjacency H.323 configuration mode or adjacency SIP configuration mode. To remove this configuration, use the no form of this command.
Syntax Description
Percentage of calls. The range is from 0 to 1000. For example, if you enter 205 as the value of call-percentage , the SBC uses 20.5 percent of the calls for measuring local jitter. |
Command Default
Command Modes
Adjacency H.323 configuration (config-sbc-sbe-adj-h323)
Adjacency SIP configuration (config-sbc-sbe-adj-sip)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of the modes required to run this command.
Examples
In the following example, the calc-moscqe command is used to specify that 20.5 percent of the calls must be used to calculate the MOS-CQE score:
Related Commands
call-policy-set
To create a new policy set, copy an existing complete policy set, or swap the references of a complete policy set to another policy set, use the call-policy-set command in the Signaling border element (SBE) configuration mode. To delete a policy set , use the no form of this command.
call-policy-set { policy-set-id | copy { source policy-set-id destination policy-set-id } | swap { source policy-set-id destination policy-set-id }}
no call-policy-set policy-set-id
Syntax Description
The integer, ranging from 1 to 2147483647, for a call policy set. |
|
Swaps the existing references of a complete policy set to another policy set. |
|
Command Default
Command Modes
SBE configuration (config-sbc-sbe)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
|
This command was modified. The copy-and-swap function was added to this command. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of the modes required to run the command.
Examples
The following example shows how to create policy set 1 on mySbc:
The following example shows how to copy an existing complete policy set and swap its references to a new policy set:
Router(config-sbc-sbe-rtgpolicy)# first-inbound-na-table InTable
Router(config-sbc-sbe-rtgpolicy)# first-outbound-na-table OutTable
Related Commands
call-policy-set (admin-domain)
To configure the inbound and outbound number analysis and routing policy set for an administrative domain, use the call-policy-set command in the Administrative domain configuration mode. To remove a policy set from an administrative domain , use the no form of this command.
call-policy-set { inbound-na policy-set-id | outbound-na policy-set-id | rtg policy-set-id } [ priority priority-id ]
no call-policy-set { inbound-na | outbound-na | rtg }
Syntax Description
Command Default
If the policy sets are not configured, an administrative domain uses the values defined within the default call policy set.
Command Modes
Administrative domain configuration (config-sbc-sbe-ad)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of the modes required to run the command.
Examples
The following example shows how to configure an inbound and outbound number analysis and routing policy set for the administrative domain ADMIN1, and allocate priority to the policy sets using the call-policy-set command in the Administrative domain configuration mode:
Related Commands
|
|
|
|---|---|
Lists the administrative domains on the SBC and per adjacency. |
call-policy-set default
To activate a default policy set within an signaling border element (SBE) entity, use the call-policy-set default command in the SBE configuration mode. To deactivate a default policy set, use the no form of this command.
call-policy-set default policy-set-id [ priority priority-value ]
Syntax Description
Command Default
Command Modes
SBE configuration (config-sbc-sbe)
Command History
Usage Guidelines
If another policy set was previously active, it is made inactive by executing this command. The SBE is created with no active routing policy set; an active routing policy set must be explicitly configured using this command.
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of the modes required to run the command.
Examples
The following example shows how to set policy set 1 as the default on mySbc:
Related Commands
callee-bandwidth-field
To configure the SBC to convert a specific bandwidth line format into another bandwidth line format in an outbound Session Description Protocol (SDP) sent to the callee, use the callee-bandwidth-field command in CAC table entry configuration mode. To remove the specific style of bandwidth line format, use the no callee-bandwidth-field command.
callee-bandwidth-field [as-to-tias | tias-to-as]
no callee-bandwidth-field [as-to-tias | tias-to-as]
Syntax Description
Command Default
The default is that the bandwidth line is not translated from one format to another.
Command Modes
CAC table entry configuration (config-sbc-sbe-cacpolicy-cactable-entry)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
The SBC follows whichever outgoing bandwidth line format is configured. If the outgoing adjacency is configured to prefer a specific style of bandwidth line, then the preferred format is used, and any b=AS or b=TIAS lines are translated to that format.
If the answerer-side adjacency is configured to prefer a specific style of bandwidth line format in the SDP, this command causes the SBC to convert the offer to the specified format before being sent to the answerer. If there are multiple bandwidth lines, only the first is converted into the specified bandwidth line and the rest are ignored.
NoteThe default is that the bandwidth line is not translated from one format to another. However, if the callee is configured to convert the bandwidth, and the message is converted, then the response back to the caller is converted back even if the caller-bandwidth-field option is not provisioned. The default is that the bandwidth line is not translated from one format to another. However, if the callee is configured to convert the bandwidth, and the message is converted, then the response back to the caller is converted back even if the caller-bandwidth-field option is not provisioned.
Examples
The following example shows the SBC is configured to convert an AS bandwidth line format into a TIAS bandwidth line format in an outbound SDP sent to the callee:
Related Commands
|
|
|
|---|---|
Configures the SBC to convert a specific bandwidth line format into another bandwidth line format in an outbound Session Description Protocol (SDP) sent to the caller. |
callee-codec-list
To list the codecs which the callee leg of a call is allowed to use, use the callee- codec-list command in the CAC table entry configuration mode. To delete a codec list, use the no form of this command.
no callee-codec-list list-name
Syntax Description
Command Default
Command Modes
CAC table entry configuration (config-sbc-sbe-cacpolicy-cactable-entry)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to enter a mode to create a codec list using the name test:
callee-hold-setting
To configure the callee hold settings that are supported, use the callee-hold-setting command in CAC table entry configuration mode. To deconfigure the callee hold settings, use the no form of this command.
callee-hold-setting {hold-c0 | hold-c0-inactive | hold-c0-sendonly | hold-sendonly | standard}
no callee-hold-setting {hold-c0 | hold-c0-inactive | hold-c0-sendonly | hold-sendonly | standard}
Syntax Description
Callee supported; requires c=0.0.0.0 and either a=forward-direction capability. |
Command Default
Command Modes
CAC table entry configuration (config-sbc-sbe-cacpolicy-cactable-entry)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to configure the callee hold settings:
Related Commands
|
|
|
|---|---|
callee-inbound-policy
To configure a callee inbound SDP policy table, use the callee-inbound-policy command in CAC table entry configuration mode. To, use the no form of this command.
Syntax Description
Specifies the name of the SDP policy table. The maximum size is 30 characters. |
Command Default
Command Modes
CAC table entry configuration (config-sbc-sbe-cacpolicy-cactable-entry)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to create the admission control table MyCacTable:
Related Commands
|
|
|
|---|---|
callee-media-caps
To configure a codec list used to announce media capabilities on behalf of a SIP callee in a SIP to H.323 or H.323 to SIP interworking call, use the callee-media-caps command in CAC table entry configuration mode. To remove the codec list, use the no callee-media-caps command.
callee-media-caps {code-list-name}
no callee-media-caps {code-list-name}
Syntax Description
This is a string text of a maximum length of 30 characters. Describes the extra codecs that a SIP callee can announce to the H.323 side. |
Command Default
Command Modes
CAC table entry configuration (config-sbc-sbe-cacpolicy-cactable-entry)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
This command configures a codec list and assigns the list to a CAC table.
Once a codec list has been assigned, it may not be deleted until it is removed from the CAC table entry. A codec list must exist before it can be assigned to an entry in a CAC table.
For a description of “H.323 TCS Codecs,” see the “Codec Handling” chapter in the Cisco Unified Border Element (SP Edition) Configuration Guide: Unified Model .
Examples
The following example configures a codec list called “callee-media-caps-list” and assigns that list to the CAC table “cac-tbl-1” in entry 1 to announce that T.38 was added as a callee SIP media capabilities.
Related Commands
callee-outbound-policy
To configure a callee outbound SDP policy table, use the callee-outbound-policy command in CAC table entry configuration mode. To, use the no form of this command.
no callee-outbound-policy WORD
Syntax Description
Specifies the name of the SDP policy table. The maximum size is 30 characters. |
Command Default
Command Modes
CAC table entry configuration (config-sbc-sbe-cacpolicy-cactable-entry)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to create the admission control table MyCacTable:
Related Commands
|
|
|
|---|---|
callee-privacy edit-privacy-request
To edit and update privacy indications provided by the user, use the callee-privacy edit-privacy-request command in CAC table configuration mode. To remove the indications, use the no form of this command.
callee-privacy edit-privacy-request { pass | strip | insert | replace | sip { strip { all | critical | header | id | none | session | token word | user } | insert { critical | header | id | none | session | token word | user }}}
no callee-privacy edit-privacy-request { pass | strip | insert | replace | sip { strip { all | critical | header | id | none | session | token word | user } | insert { critical | header | id | none | session | token word | user }}}
Syntax Description
Command Default
Command Modes
CAC table configuration (config-sbc-sbe-cacpolicy-cactable)
Command History
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to configure the entry to remove all privacy restrictions from SIP and H323 adjacencies in the new admission control table MyCacTable:
Related Commands
callee-privacy privacy-service
To apply privacy settings according to RFC3323, RFC3325, and/or setting of H.323 presentation restriction settings in the given entry in the admission control table, use the callee-privacy privacy-service command in CAC table configuration mode. To remove the privacy settings, use the no form of this command.
callee-privacy privacy-service { adj-trust-boundary | always | never }
no callee-privacy privacy-service
Syntax Description
Specifies the adjacency privacy trust level to determine if the privacy service is required. |
|
Never provides privacy service even if requested by the user. |
Command Default
Command Modes
CAC table configuration (config-sbc-sbe-cacpolicy-cactable)
Command History
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to configure the entry to provide privacy service always as requested by the user in the new admission control table MyCacTable:
Related Commands
|
|
|
|---|---|
Configures a CAC table type that enables the priority of the call to be used as a criterion in CAC policy. |
callee-sig-qos-profile
To configure the QoS profile to be used for signaling packets sent to the original callee , use the callee-sig-qos-profile command in the CAC table entry configuration mode. To deconfigure the QoS profile , use the no form of this command.
callee-sig-qos-profile profile-name
no callee-sig-qos-profile profile-name
Syntax Description
Command Default
Command Modes
CAC table entry configuration (config-sbc-sbe-cacpolicy-cactable-entry)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how the callee-sig-qos-profile command is used to configure the QoS profile named enterprise to be used for signaling packets sent to the original callee:
callee tel-event payload type
To configure the payload type to be used for the callee in H.323-SIP interworking calls, use the callee tel-event payload-type command in the CAC entry configuration mode. To unconfigure the payload type setting, use the no form of this command.
callee tel-event payload type payload-type
no callee tel-event payload type
Syntax Description
See RFC 2833 for detailed information about the values of payload-type . The range is from 96 to 127. The default is 101. |
Command Default
Command Modes
CAC entry configuration (config-sbc-cac-entry)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers in a release earlier than Release 3.1S. |
Usage Guidelines
The callee tel-event payload type command enables support for dual tone multifrequency (DTMF) H.323-SIP interworking. The telephone-event payload type configured by this command is used by the SBC only in situations where the payload type information is not provided by the other side in an H.323-SIP interworking call.
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to use the callee tel-event payload-type command to set the payload type to 101:
Related Commands
callee-video-qos-profile
To configure the QoS profile to use for media packets sent to the original callee, use the callee-video-qos-profile command in CAC table entry configuration mode. To return to the default behavior, use the no form of this command.
callee-video-qos-profile profile-name
Syntax Description
Command Default
Command Modes
CAC table entry configuration (config-sbc-sbe-cacpolicy-cactable-entry)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
NoteThe The callee-video-qos-profile can be executed only at the per-call scope. CAC policy does not activate if configured at any other scope.
Examples
The following example shows how to configure calls from the acme account to use the video QoS profile enterprise for packets sent from the SBC to the original callee:
callee-voice-qos-profile
To configure the QoS profile to use for media packets sent to the original callee, use the callee-voice-qos-profile command in CAC table entry configuration mode. To return to the default behavior, use the no form of this command.
callee-voice-qos-profile profile-name
Syntax Description
Command Default
Command Modes
CAC table entry configuration (config-sbc-sbe-cacpolicy-cactable-entry)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
NoteThis command can be executed only at the per-call scope. CAC policy does not activate if this command is configured at any other scope. This command can be executed only at the per-call scope. CAC policy does not activate if this command is configured at any other scope.
Examples
The following example shows how to configure calls from the acme account to use the voice QoS profile enterprise for packets sent from the SBC to the original callee.
callee codec
To configure the codec options for a callee, use the callee codec command in the CAC table entry configuration mode. To deconfigure the codec options, use the no form of this command.
callee codec {convert | profile profile-name }
no callee codec {convert | profile }
Syntax Description
Command Default
By default, codec variant conversion is disabled, and no codec variant profile is specified.
Command Modes
CAC table entry configuration (config-sbc-sbe-cacpolicy-cactable-entry)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section that follows shows the hierarchy of the modes required to run the command.
Examples
The following example shows how to configure the codec options for a callee using the callee codec command in the CAC table entry mode:
callee inband-dtmf-mode
To configure the dual tone multifrequency (DTMF) in-band mode for the callee side, use the callee inband-dtmf-mode command in the CAC table entry configuration mode.To deconfigure the DTMF in-band mode for the callee side, use the no form of this command.
callee inband-dtmf-mode { always | inherit | maybe | never }
Syntax Description
Command Default
Command Modes
CAC table entry configuration (config-sbc-sbe-cacpolicy-cactable-entry)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section that follows shows the hierarchy of the modes required to run the command.
Examples
The following example shows how to configure the DTMF in-band mode for the callee side using the callee inband-dtmf-mode command in the CAC table entry configuration mode so that the in-band DTMF tones are always in use by the endpoint:
Related Commands
|
|
|
|---|---|
callee media-description disabled
To configure how Cisco Unified Border Element (SP Edition) handles disabled media descriptions for a callee, use the callee media-description disabled command in the CAC table entry configuration mode.
callee media-description disabled {strip {answer | offer {all | new}} | {pad offer}}
no callee media-description disabled {strip {answer | offer {all | new}} |{pad offer}}
Syntax Description
Strips disabled media description lines from offers when used with strip. Pad offers with dummy disabled media description lines when used with pad. |
|
Command Default
Command Modes
CAC table entry configuration (config-sbc-sbe-cacpolicy-cactable-entry)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to remove disabled media streams in forwarded offers which are new:
The following example shows how to remove all disabled media streams from forwarded offers, whether known to the recipient of the offer or not.
The following example shows how to remove all disabled media streams from forwarded answers.
The following example shows how to stop SBC from padding forwarded offers with disabled media streams.
callee media-type
To configure the media address type settings for a callee on the Cisco Unified Border Element (SP Edition), use the callee media-type command in the CAC table entry configuration mode. Use the no form of this command to disable the media address type settings for a callee.
callee media-type { ipv4 | ipv6 | inherit | both }
no callee media-type { ipv4 | ipv6 | inherit | both }
Syntax Description
Inherit the supported media IP address type from earlier CAC policy entries (default). |
|
Command Default
Command Modes
CAC table entry configuration (config-sbc-sbe-cacpolicy-cactable-entry)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to remove disabled media streams in forwarded offers which are new:
callee media bypass
To enable or disable the Multiple SBC Media Bypass feature on the callee side, use the callee media bypass command in the CAC table entry configuration mode. To deconfigure the Multiple SBC Media Bypass feature, use the no form of this command.
callee media bypass { enable | disable }
Syntax Description
Enables the Multiple SBC Media Bypass feature on the callee side. |
|
Disables the Multiple SBC Media Bypass feature on the callee side. |
Command Default
Command Modes
CAC table entry configuration (config-sbc-sbe-cacpolicy-cactable-entry)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of the modes required to run the command.
Examples
The following example shows how to enable the Multiple SBC Media Bypass feature on the callee side:
Related Commands
callee port-range-tag
To configure the port range tag for a callee that is used when selecting a media address and port, use the callee port-range-tag command in the CAC table entry configuration mode. To deconfigure the port range tag, use the no form of this command.
callee port-range-tag { adj-name | none | string tag-string }
Syntax Description
Prompts the SBC to not use a port range tag for calls matching the CAC entry, and removes any previously found strings. |
|
Command Default
Command Modes
CAC table entry configuration (config-sbc-sbe-cacpolicy-cactable-entry)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of the modes required to run the command.
Examples
The following example shows how to configure a port-range tag:
Related Commands
|
|
|
|---|---|
Adds an IPv4 and IPv6 address to the set of addresses that can be used by the DBE as a local media address. |
callee ptime
To configure the packetization time on the callee side, use the callee ptime command in the CAC table configuration mode.To deconfigure the packetization time on the callee side, use the no form of this command.
Syntax Description
Command Default
By default, 0 ms is configured. This means that no transrating occurs.
Command Modes
CAC table entry configuration (config-sbc-sbe-cacpolicy-cactable-entry)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section that follows shows the hierarchy of the modes required to run the command.
Examples
The following example shows how to configure the packetization time on the callee side using the callee ptime command in the CAC table configuration mode:
Related Commands
|
|
|
|---|---|
callee secure-media
To configure granular-level Secure Media on the callee side, use the callee secure-media command in CAC table entry configuration mode. To remove granular-level Secure Media, use the no callee secure-media command.
Syntax Description
Command Default
Granular-level (Unsignaled) Secure Media is disabled by default.
Command Modes
CAC table entry configuration (config-sbc-sbe-cacpolicy-cactable-entry)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
Restriction—Both caller and callee sides of the call need to be configured. If only one leg of the call has granular secure media configured, then the call will fail.
We recommend you use unsignaled (also called granular-level) Secure Media configuration because, instead of turning on Secure Media globally, you can specify the calls and adjacencies where you want to use Secure Media.
Examples
The following example shows an Unsignaled Secure Media configuration where the two SIP adjacencies for both legs of the call are configured for “security trusted-unencrypted” and both the caller and callee sides are configured for Secure Media in a CAC table entry:
The following configuration example shows how to configure Unsignaled Secure Media where an adjacency is untrusted by using the transport srtp allowed command on the untrusted adjacency in a CAC policy table:
The following configuration example shows that SIP adjacencies ‘client’ and ‘server’ are configured as “security trusted-unencrypted” and that CAC table entry 1 is configured for Secure Media on both the caller and callee sides:
Related Commands
|
|
|
|---|---|
Configures transport-level security (TLS) on a SIP adjacency. |
caller-bandwidth-field
To configure the SBC to convert a specific bandwidth line format into another bandwidth line format in an outbound Session Description Protocol (SDP) sent to the caller, use the caller-bandwidth-field command in CAC table entry configuration mode. To remove the specific style of bandwidth line format, use the no caller-bandwidth-field command.
caller-bandwidth-field [as-to-tias | tias-to-as]
no caller-bandwidth-field [as-to-tias | tias-to-as]
Syntax Description
Command Default
The default is that the bandwidth line is not translated from one format to another.
Command Modes
CAC table entry configuration (config-sbc-sbe-cacpolicy-cactable-entry)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
The SBC follows whichever outgoing bandwidth line format is configured. If the outgoing adjacency is configured to prefer a specific style of bandwidth line, then the preferred format is used, and any b=AS or b=TIAS lines are translated to that format.
If the offerer-side adjacency is configured to prefer a specific style of bandwidth line format in the SDP, this command causes the SBC to convert the answer to the specified format before being sent back to the offerer. If there are multiple bandwidth lines, only the first is converted into the specified bandwidth line and the rest are ignored.
NoteThe default is that the bandwidth line is not translated from one format to another. However, if the callee is configured to convert the bandwidth, and the message is converted, then the response back to the caller is converted back even if the caller-bandwidth-field option is not provisioned. The default is that the bandwidth line is not translated from one format to another. However, if the callee is configured to convert the bandwidth, and the message is converted, then the response back to the caller is converted back even if the caller-bandwidth-field option is not provisioned.
Examples
The following example shows the SBC is configured to convert an AS bandwidth line format into a TIAS bandwidth line format in an outbound SDP sent to the caller:
Related Commands
|
|
|
|---|---|
Configures the SBC to convert a specific bandwidth line format into another bandwidth line format in an outbound Session Description Protocol (SDP) sent to the callee. |
caller-codec-list
To list the codecs which the caller leg of a call is allowed to use, use the caller- codec-list command in the CAC table entry configuration mode. To delete a codec list, use the no form of this command.
no caller-codec-list list-name
Syntax Description
Command Default
Command Modes
CAC table entry configuration (config-sbc-sbe-cacpolicy-cactable-entry)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to enter a mode to create a codec list using the name test:
caller-hold-setting
To configure the caller hold settings that are supported, use the caller-hold-setting command in CAC table entry configuration mode. To cancel caller hold settings, use the no form of this command.
caller-hold-setting {hold-c0 | hold-c0-inactive | hold-c0-sendonly | hold-sendonly | standard}
no caller-hold-setting {hold-c0 | hold-c0-inactive | hold-c0-sendonly | hold-sendonly | standard}
Syntax Description
Command Default
Command Modes
CAC table entry configuration (config-sbc-sbe-cacpolicy-cactable-entry)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to configure the caller hold settings:
Related Commands
|
|
|
|---|---|
caller-inbound-policy
To configure a caller inbound SDP policy table, use the caller-inbound-policy command in CAC table entry configuration mode. To deconfigure a caller inbound SDP policy table, use the no form of this command.
Syntax Description
Specifies the name of the SDP policy table. The maximum size is 30 characters. |
Command Default
Command Modes
CAC table entry configuration (config-sbc-sbe-cacpolicy-cactable-entry)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to configure a caller inbound SDP policy table:
Router(config-sbc-sbe-cacpolicy-cactable-entry)# caller-inbound-policy test
Related Commands
|
|
|
|---|---|
caller-media-caps
To configure a codec list used to announce media capabilities on behalf of a SIP caller in a SIP to H.323 or H.323 to SIP interworking call, use the caller-media-caps command in CAC table entry configuration mode. To remove the codec list, use the no caller-media-caps command.
caller-media-caps {code-list-name}
no caller-media-caps {code-list-name}
Syntax Description
This is a string text of a maximum length of 30 characters. Describes the extra codecs that a SIP caller can announce to the H.323 side. |
Command Default
Command Modes
CAC table entry configuration (config-sbc-sbe-cacpolicy-cactable-entry)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
This command configures a codec list and assigns the list to a CAC table.
Once a codec list has been assigned, it may not be deleted until it is removed from the CAC table entry. A codec list must exist before it can be assigned to an entry in a CAC table.
For a description of “H.323 TCS Codecs,” see the “Codec Handling” chapter in the Cisco Unified Border Element (SP Edition) Configuration Guide: Unified Model .
Examples
The following example configures a codec list called “caller-media-caps-list” and assigns that list to the CAC table “cac-tbl-1” in entry 1 to announce that T.38 is added as a caller SIP media capabilities:
Related Commands
caller-outbound-policy
To configure a caller outbound SDP policy table, use the caller-outbound-policy command in CAC table entry configuration mode. To deconfigure a caller outbound SDP policy table, use the no form of this command.
caller-outbound-policy table_name
no caller-outbound-policy table_name
Syntax Description
Specifies the name of the SDP policy table. The maximum size is 30 characters. |
Command Default
Command Modes
CAC table entry configuration (config-sbc-sbe-cacpolicy-cactable-entry)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to configure a caller outbound SDP Limit table:
Router(config-sbc-sbe-cacpolicy-cactable-entry)# caller-outbound-policy test
|
|
|
|---|---|
caller-privacy edit-privacy-request
To edit and update privacy indications provided by the user, use the caller-privacy edit-privacy-request command in CAC table configuration mode. To remove the indications, use the no form of this command.
caller-privacy edit-privacy-request { pass | strip | insert | replace | sip { strip { all | critical | header | id | none | session | token word | user } | insert { critical | header | id | none | session | token word | user }}}
no caller-privacy edit-privacy-request { pass | strip | insert | replace | sip { strip { all | critical | header | id | none | session | token word | user } | insert { critical | header | id | none | session | token word | user }}}
Syntax Description
Command Default
Command Modes
CAC table configuration (config-sbc-sbe-cacpolicy-cactable)
Command History
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to configure the entry to remove all privacy restrictions from SIP and H323 adjacencies in the new admission control table MyCacTable:
Related Commands
caller-privacy privacy-service
To apply privacy settings according to RFC3323, RFC3325, and/or setting of H.323 presentation restriction settings in the given entry in the admission control table, use the caller-privacy privacy-service command in CAC table configuration mode. To remove the privacy settings, use the no form of this command.
caller-privacy privacy-service { adj-trust-boundary | always | never }
no caller-privacy privacy-service
Syntax Description
Specifies the adjacency privacy trust level to determine if the privacy service is required. |
|
Never provides privacy service even if requested by the user. |
Command Default
Command Modes
CAC table configuration (config-sbc-sbe-cacpolicy-cactable)
Command History
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to configure the entry to provide privacy service always as requested by the user in the new admission control table MyCacTable:
Related Commands
|
|
|
|---|---|
Configures a CAC table type that enables the priority of the call to be used as a criterion in CAC policy. |
caller-sig-qos-profile
To configure the QoS profile to use for signaling packets sent to the original caller, use the caller-sig-qos-profile command in the CAC table entry configuration mode. To deconfigure the QoS profile , use the no form of this command.
caller-sig-qos-profile profile-name
no caller-sig-qos-profile profile-name
Syntax Description
Command Default
Command Modes
CAC table entry configuration (config-sbc-sbe-cacpolicy-cactable-entry)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
This command can only be executed at the per-call scope. CAC policy will not activate if this command is configured at any other scope.
Packet marking will not be applied until the CAC decision process is run. This means that some initial signaling packets sent to the caller (for example, the SIP 100 provisional response) will not receive any particular DSCP marking.
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following command configures calls from the acme account to use the voice QoS profile enterprise for signaling packets sent from the SBC to the original caller:
caller tel-event payload type
To configure the payload type to be used for the caller in H.323-SIP interworking calls, use the caller tel-event payload-type command in the CAC entry configuration mode. To unconfigure the payload type setting, use the no form of this command.
caller tel-event payload type payload-type
no caller tel-event payload type
Syntax Description
See RFC 2833 for detailed information about the values of payload-type . The range is from 96 to 127. The default is 101. |
Command Default
Command Modes
CAC entry configuration (config-sbc-cac-entry)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers in a release earlier than Release 3.1S. |
Usage Guidelines
The caller tel-event payload type command enables support for dual tone multifrequency (DTMF) H.323-SIP interworking. The telephone-event payload type configured by this command is used by the SBC only in situations where the payload type information is not provided by the other side in an H.323-SIP interworking call.
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
Examples
The following example shows how to use the caller tel-event payload-type command to set the payload type to 101:
Related Commands
caller-video-qos-profile
To configure the QoS profile to use for media packets sent to the original caller, use the caller-video-qos-profile command in CAC table configuration mode. To remove this configuration, use the no form of this command.
caller-video-qos-profile profile-name
no caller-video-qos-profile profile-name
Syntax Description
Command Default
Command Modes
CAC table configuration (config-sbc-sbe-cacpolicy-cactable)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
NoteThe The caller-video-qos-profile command can be executed only at the per-call scope. CAC policy does not activate if this command is configured at any other scope.
Examples
The following example shows how to configure calls from the acme account to use the video QoS profile enterprise for packets sent from the SBC to the original caller:
caller-voice-qos-profile
To configure the QoS profile to use for media packets sent to the original caller, use the caller-voice-qos-profile command in CAC table configuration mode. To remove this configuration, use the no form of this command.
caller-voice-qos-profile profile-name
Syntax Description
Command Default
Command Modes
CAC table configuration (config-sbc-sbe-cacpolicy-cactable)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section shows the hierarchy of modes required to run the command.
NoteThis command can be executed only at the per-call scope. CAC policy does not activate if this command is configured at any other scope. This command can be executed only at the per-call scope. CAC policy does not activate if this command is configured at any other scope.
Examples
The following example shows how to configure calls from the acme account to use the voice QoS profile enterprise for packets sent from the SBC to the original caller:
caller codec
To configure the codec options for a caller, use the caller codec command in the CAC table entry configuration mode. To deconfigure the codec options, use the no form of this command.
caller codec {convert | profile profile-name }
no caller codec {convert | profile }
Syntax Description
Command Default
By default, codec variant conversion is disabled, and no codec variant profile is specified.
Command Modes
CAC table entry configuration (config-sbc-sbe-cacpolicy-cactable-entry)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. |
Usage Guidelines
To use this command, you must be in the correct configuration mode. The Examples section that follows shows the hierarchy of the modes required to run the command.
Examples
The following example shows how to configure the codec options for a caller using the caller codec command in the CAC table entry mode:
caller inband-dtmf-mode
To configure the dual tone multifrequency (DTMF) in-band mode for the caller side, use the caller inband-dtmf-mode command in the CAC table entry configuration mode.To deconfigure the DTMF in-band mode for the caller side, use the no form of this command.
caller inband-dtmf-mode { always | inherit | maybe | never }