Cisco IOS Voice Command Reference

Cisco IOS Voice Commands:
A

This chapter contains commands to configure and maintain Cisco IOS voice applications. The commands are presented in alphabetical order. Some commands required for configuring voice may be found in other Cisco IOS command references. Use the Cisco IOS Master Commands List online to find these commands.

For detailed information on how to configure these applications and features, refer to the Cisco IOS Voice Configuration Library.

aal2-profile custom

To specify custom numbers and user-to-user information (UUI) code points for ATM adaptation layer 2 (AAL2) profiles and codecs, use the aal2-profile custom command in global configuration mode. To disable the configuration, use the no form of this command.

aal2-profile custom number number number {clear-channel | g711alaw | g711ulaw | g726r32 | g729br8 | g720r8 | llcc} packet-length minimum-UUI-codepoint maximum-UUI-codepoint

no aal2-profile custom number

Syntax Description

Command Default

One of the predefined International Telecommunication Union - Telecommunication Standardization Sector (ITU-T) profiles can be used.

Command Modes

Global configuration (config)

Command History

Usage Guidelines

AAL2 custom profiles are used to define additional profiles that are not present in the ITU-T specifications.

After defining a custom profile, apply that profile under a Voice over ATM (VoATM) dial peer for it to take affect using the codec aal2-profile command. The codec aal2-profile command can be used only if the session protocol is "aal2-trunk".

Examples

The following example shows how to specify custom numbers and UUI cod epoints for AAL2 profiles and codecs:

Router# configure terminal

Router(config)# aal2-profile custom  2 1 1 g711ulaw 6 3 3

aaa nas port voip

To send out the standard NAS-port attribute (RADIUS IETF Attribute 5) on voice interfaces, use the aaa nas port voip command in global configuration mode. To disable the command, use the no form of the command.

aaa nas port voip

no aaa nas port voip

Syntax Description

This command has no arguments or keywords.

Command Default

Disabled

Command Modes

Global configuration

Command History

Usage Guidelines

This command brings back the original behavior of the Authentication, Authorization, and Accounting (AAA). NAS-Port on VoIP interfaces. By default this feature is disabled.

Examples

The following example shows how to return to the original behavior of the AAA NAS-Port:

aaa nas port voip

Related Commands

aaa username

To determine the information with which to populate the username attribute for Authentication, Authorization, and Accounting (AAA). billing records, use the aaa username command in SIP UA configuration mode. To achieve default capabilities, use the no form of this command.

aaa username {calling-number | proxy-auth}

no aaa username

Syntax Description

Command Default

calling-number

Command Modes

SIP UA configuration

Command History

Usage Guidelines

Parsing the Proxy-Authorization header, decoding the PUID and password, and populating the username attribute with the PUID must be enabled through this command. If this command is not issued, the Proxy-Authorization header is ignored.

The keyword proxy-auth is a nonstandard implementation, and Session Initiation Protocol (SIP) gateways do not normally receive or process the Proxy-Authorization header.

Examples

The following example enables the processing of the SIP username from the Proxy-Authorization header:

Router(config)# sip-ua

Router(config-sip-ua)# aaa username proxy-auth

Related Commands

access-list (voice source-group)

To assign an access list to a voice source group, use the access-list command in voice source-group configuration mode. To delete the access list, use the no form of this command.

access-list access-list-number

no access-list access-list-number

Syntax Description

Command Default

No default behavior or values

Command Modes

Voice source-group configuration

Command History

Usage Guidelines

An access list defines a range of IP addresses for incoming calls that require additional scrutiny. Two related commands are used for voice source groups:

•Use the access-list access-list-number {deny | permit} source [source-wildcard] [log] command in global configuration mode to define the contents of the access list.

•Use the access-list access-list-number command in voice source-group configuration mode to assign the defined access list to the voice source group.

The terminating gateway uses the source IP group to identify the source of the incoming VoIP call before selecting an inbound dial peer. If the source is found in the access list, then the call is accepted or rejected, depending on how the access list is defined.

The terminating gateway uses the access list to implement call blocking. If the call is rejected, the terminating gateway returns a disconnect cause to the source. Use the disconnect-cause command to specify a disconnect cause to use for rejected calls.

Use the show access-lists privileged EXEC command to display the contents of all access lists.

Use the show ip access-list privileged EXEC command to display the contents of one access list.

Examples

The following example assigns access list 1 to voice source-group alpha. Access list 1 was defined previously using another command. An incoming source IP group call is checked against the conditions defined for access list 1 and is processed based on the permit or deny conditions of the access list.

Router(config)# voice source-group alpha

Router(cfg-source-grp)# access-list 1 

Related Commands

access-policy

To require that a neighbor be explicitly configured in order for requests to be accepted, use the access-policy command in Annex G configuration mode. To reset the configuration to accept all requests, use the no form of this command.

access-policy [neighbors-only]

no access-policy

Syntax Description

Command Default

Border elements accept any and all requests if service relationships are not configured.

Command Modes

Annex G configuration

Command History

Usage Guidelines

Border elements accept any and all requests if service relationships are not configured. The access-policy command eliminates arbitrary requests from unknown border elements, and is a required prerequisite for configuring service relationships.

Examples

The following example shows how to enable the service relationship between border elements:

Router(config-annexg)# access-policy neighbors-only

Related Commands

accounting (gatekeeper)

To enable and define the gatekeeper-specific accounting method, use the accounting command in gatekeeper configuration mode. To disable gatekeeper-specific accounting, use the no form of this command.

accounting {username h323id | vsa}

no accounting

Syntax Description

Command Default

Accounting is disabled.

Command Modes

Gatekeeper configuration

Command History

Usage Guidelines

To collect basic start-stop connection accounting data, the gatekeeper must be configured to support gatekeeper-specific H.323 accounting functionality. The accounting command enables you to send accounting data to the RADIUS server via IETF RADIUS or VSA attriibutes.

Specify a RADIUS server before using the accounting command.

There are three different methods of accounting. The H.323 method sends the call detail record (CDR) to the RADIUS server, the syslog method uses the system logging facility to record the CDRs, and the VSA method collects VSAs.

Examples

The following example enables the gateway to report user activity to the RADIUS server in the form of connection accounting records:

aaa accounting connection start-stop group radius

gatekeeper

 accounting

The following example shows how to enable VSA accounting:

aaa accounting connection start-stop group radius

gatekeeper

 accounting exec vsa

The following example configures H.323 accounting using IETF RADIUS attributes:

Router(config-gk)# accounting username h323id 

The following example configures H.323 accounting using VSA RADIUS attributes:

Router(config-gk)# accounting vsa

Related Commands

accounting method

To set an accounting method at login for calls that come into a dial peer, use the accounting method command in voice class AAA configuration mode. To disable the accounting method set at login, use the no form of this command.

accounting method MethListName [out-bound]

no accounting method MethListName [out-bound]

Syntax Description

Command Default

When this command is not used to specify an accounting method, the system uses the aaa accounting connection h323 command as the default. If the method list name is not specified, the outbound call leg uses the same method list name as the inbound call leg

Command Modes

Voice class AAA configuration

Command History

Usage Guidelines

This command sets the accounting method for dial peers in voice class AAA configuration mode. To initially define a method list, refer to the Cisco IOS Security Configuration Guide, Release 12.2.

If the outbound option is specified, the outbound call leg on the dial peer uses the method list name specified in the command. If the method list name is not specified, by default, the outbound call leg uses the same method list name as the inbound call leg.

Examples

The following example sets the dp-out method for the outbound leg:

voice class aaa 1 

 accounting method dp-out out-bound 

Related Commands

accounting suppress

To disable accounting that is automatically generated by a service provider module for a specific dial peer, use the accounting suppress command in voice class AAA configuration mode. To allow accounting to be automatically generated, use the no form of this command.

accounting suppress [in-bound | out-bound]

no accounting suppress [in-bound | out-bound]

Syntax Description

Command Default

Accounting is automatically generated by the service provider module.

Command Modes

Voice class AAA configuration

Command History

Usage Guidelines

If a call leg option is not specified by the command, accounting is disabled for both inbound and outbound calls. For accounting to be automatically generated in the service provider module, you must first configure gw-accounting aaa command in global configuration mode before configuring dial-peer-based accounting in voice class AAA configuration mode.

Examples

In the example below, accounting is suppressed for the incoming call leg.

voice class aaa 1

 accounting suppress in-bound 

Related Commands

accounting template

To allow each dial peer to choose and send a customized accounting template to the RADIUS server, use the accounting template command in voice class AAA configuration mode. To disable the dial peer from choosing and sending a customized accounting template, use the no form of this command.

accounting template acctTempName [out-bound]

no accounting template acctTempName [out-bound]

Syntax Description

Command Default

The dial peer does not choose and send a customized accounting template to the RADIUS server.

Command Modes

Voice class AAA configuration

Command History

Usage Guidelines

By default, non-RFC-mandatory vendor-specific attributes (VSAs) are not included in accounting records if you do not configure the accounting template. The accounting template enables you to manage accounting records at a per-VSA level. When an accounting template is used for customizing the accounting record, the VSA name release source has to be included in the template file so that it is included in the accounting record and sent to the RADIUS server.

This command overrides the acct-template command in gateway accounting AAA configuration mode when a customized accounting template is used.

If you use a Tool Command Language (Tcl) script, the Tcl verb aaa accounting start [-t acctTempName] takes precedence over the accounting template command in voice class AAA configuration mode.

Examples

The following example sets the template temp-dp for the outbound leg

voice class aaa 1

 accounting template temp-dp out-bound

Related Commands

acc-qos

To define the acceptable quality of service (QoS) for any inbound and outbound call on a VoIP dial peer, use the acc-qos command in dial peer configuration mode. To restore the default QoS setting, use the no form of this command.

acc-qos {best-effort | controlled-load | guaranteed-delay} [audio | video]

no acc-qos

Syntax Description

Command Default

best-effort

Command Modes

Dial peer configuration

Command History

Usage Guidelines

This command is applicable only to VoIP dial peers.

When VoIP dial peers are used, the Cisco IOS software uses RSVP to reserve a certain amount of bandwidth so that the selected QoS can be provided by the network. Call setup is aborted if the RSVP resource reservation does not satisfy the acceptable QoS for both peers.

To select the most appropriate value for this command, you need to be familiar with the amount of traffic this connection supports and what kind of impact you are willing to have on it. The Cisco IOS software generates a trap message when the bandwidth required to provide the selected quality of service is not available.

If audio or video is not configured, the bearer capability information element (IE) is not checked against max values during SETUP.

You must use the ip rsvp bandwidth command to enable RSVP on an IP interface before you can specify RSVP QoS.

In order to use this command, you have to have the req-qos statement present.

Examples

The following example selects guaranteed-delay as the acceptable QoS for inbound and outbound audio calls on VoIP dial peer 10:

dial-peer voice 10 voip

 acc-qos guaranteed-delay

The following example selects controlled-load as the acceptable QoS for audio and video:

dial-peer voice 100 voip

 acc-qos controlled-load audio

 acc-qos controlled-load video

Related Commands

acct-template

To select a group of voice attributes to collect in accounting records, use the acct-template command in gateway accounting AAA or gateway accounting file configuration mode. To disable collection of a group of voice attributes, use the no form of this command.

acct-template {template-name | callhistory-detail}

no acct-template {template-name | callhistory-detail}

Syntax Description

Command Default

No voice attributes are collected.

Command Modes

Gateway accounting AAA configuration (config-gw-accounting-aaa)
Gateway accounting file configuration (config-gw-accounting-file)

Command History

Usage Guidelines

Use this command to collect only the voice attributes that are defined in an accounting template. The accounting template is a text file that you create by selecting specific attributes that are applicable to your billing needs. Use the call accounting-template voice command to define your accounting template before using the acct-template command.

The show call accounting-template voice master command displays all the voice attributes that can be filtered by accounting templates.

Use the callhistory-detail keyword to send all voice VSAs to the accounting server. For a description of supported voice VSAs, see the "VSAs Supported by Cisco Voice Products" section in the RADIUS VSA Voice Implementation Guide.

When you send only those VSAs defined in your accounting template, the default call-history records that are created by the service provider are automatically suppressed.

Examples

The example below uses the acct-template command to specify temp-global, a custom template.

gw-accounting aaa

 acct-template temp-global

Related Commands

activation-key

To define an activation key that can be dialed by phone users to activate Call Back on Busy on an analog phone, use the activation-key command in STC application feature callback configuration mode. To return the code to its default, use the no form of this command.

activation-key string

no activation-key

Syntax Description

Command Default

Callback activation key is #1.

Command Modes

STC application feature callback configuration (config-stcapp-callback)

Command History

Usage Guidelines

This command changes the value of the callback activation key for Call Back on Busy from the default (#1) to the specified value.

To display information about the Call Back configuration, use the show stcapp feature codes command.

Examples

The following example shows how to change the value of the callback activation key sequence from the default (#1) to a new value (*22).

Router(config)# stcapp feature callback

Router(config-stcapp-callback)# activation-key *22

Router(config-stcapp-callback)# 

The following partial output from the show stcapp feature codes command displays values for the call back feature:

Router# show stcapp feature codes 

.

.

.

  stcapp feature callback

    key *1

    timeout 30

Related Commands

address-family (tgrep)

To set the global address family to be used on all dial peers, use the address-family command in TGREP configuration mode. To change back to the default address family, use the no form of this command.

address family {e164 | decimal | penta-decimal}

no address family {e164 | decimal | penta-decimal}

Syntax Description

Command Default

E.164 address family

Command Modes

TGREP configuration

Command History

Usage Guidelines

The E. 164 address family is used if the telephony network is a public telephony network. Decimal and pentadecimal options can be used to advertise private dial plans. For example, if a company wants to use TRIP in within its enterprise telephony network using five-digit extensions, then the gateway would advertise the beginning digits of the private numbers as a decimal address family. These calls cannot be sent out of the company's private telephony network because they are not E.164-compliant.

The pentadecimal family allows numbers 0 through 9 and alphabetic characters A through E and can be used in countries where letters are also carried in the called number.

Examples

The following example shows that the address family for itad 1234 is set for E.164 addresses:

Router(config)# tgrep local-itad 1234

Router(config-tgrep)# address family e164

Related Commands

address-hiding

To hide signaling and media peer addresses from endpoints other than the gateway use the address-hidding command in voice-service configuration mode. To allow the peer address known to all endpoints, use the no form of this command.

address-hiding

no address-hiding

Syntax Description

There are no keywords or aruguments.

Command Default

Signaling and media addresses are visable to all endpoints.

Command Modes

Voice-service configuration mode

Command History

Usage Guidelines

All SIP methods/messages should terminate at IP-to-IP gateway and re-originate with IP-to-IP gateway address, address hiding makes the peer address known only to the IP-to-IP gateway. Hiding address in flow-through mode is required for SIP-to-SIP in an IP-to-IP gateway network.

Note Distinctive ringing headers include ringing information and server address where the ring tone can be optained. These headers will be forwarded as is to the peer side even if address hiding is enabled.

Examples

The following example show address-hiding being configured for all VoIP calls:

Router(config)# voice service voip 

Router(config-voi-serv) address-hiding 

Related Commands

advertise (annex g)

To control the types of descriptors that the border element (BE) advertises to its neighbors, use the advertise command in Annex G configuration mode. To reset this command to the default value, use the no form of this command.

advertise [static | dynamic | all]

no advertise

Syntax Description

Defaults

Static

Command Modes

Annex G configuration

Command History

Examples

The following example configures a BE that advertises both static and dynamic descriptors to its neighbors:

Router(config)# call-router h323-annexg be20

Router(config-annexg)# advertise all

Related Commands

advertise (tgrep)

To turn on reporting for a specified address family, use the advertise command in TGREP configuration mode. To turn off reporting for a specified address family, use the no form of this command.

advertise {e164 | decimal | penta-decimal }[csr][ac][tc][trunk-group | carrier]

advertise {trunk-group | carrier}[csr][ac][tc]

no advertise {e164 | decimal | penta-decimal | trunk-group | carrier}

Syntax Description

Command Default

No attributes for address families are advertised.

Command Modes

TGREP configuration

Command History

Usage Guidelines

If you specify e164, decimal or penta-decimal for the address family, you can stipulate whether the related carrier or trunk-group parameters are advertised. If you stipulate carrier or trunk-group for the address family, you can stipulate that the related address family prefix is advertised. If you stipulate carrier or trunk-group for the address family, you cannot stipulate carrier or trunk-group attributes for advertising.

When the no version of this command is used, it turns off the advertisement of that particular address family altogether.

Examples

The following example shows that the E.164 address family with call success rate, available circuits, total circuits, and trunk group attributes is being advertised for ITAD 1234:

Router(config)# tgrep local-itad 1234

Router(config-tgrep)# advertise e164 csr ac tc trunk-group

Related Commands

alarm-trigger

To configure a T1 or E1 controller to send an alarm to the public switched telephone network (PSTN) or switch if specified T1 or E1 DS0 groups are out of service, use the alarm-trigger command in controller configuration mode. To configure a T1 or E1 controller not to send an alarm, use the no form of this command.

alarm-trigger blue ds0-group-list

no alarm-trigger

Syntax Description

Command Default

No alarm is sent

Command Modes

Controller configuration

Command History

Usage Guidelines

Any monitored time slot can be used for either permanent trunk connections or switched connections. Permanent virtual circuits (PVCs) and switched virtual circuits (SVCs) can be combined on a T1 or E1 controller and monitored for alarm conditioning.

An alarm is sent only if all of the time slots configured for alarm conditioning on a T1 or E1 controller are out of service. If one monitored time slot remains in service or returns to service, no alarm is sent.

Examples

The following example configures T1 0 to send a blue (AIS) alarm if DS0 groups 0 and 1 are out of service:

controller t1 0 

 alarm-trigger blue 0,1

 exit

Related Commands

alias static

To create a static entry in the local alias table, use the alias static command in gatekeeper configuration mode. To remove a static entry, use the no form of this command.

alias static ip-signaling-addr [port] gkid gatekeeper-name [ras ip-ras-addr port] [terminal | mcu | gateway {h320 | h323-proxy | voip}] [e164 e164-address] [h323id h323-id]

no alias static ip-signaling-addr [port] gkid gatekeeper-name [ras ip-ras-addr port] [terminal | mcu | gateway {h320 | h323-proxy | voip}] [e164 e164-address] [h323id h323-id]

Syntax Description

Command Default

No static aliases exist.

Command Modes

Gatekeeper configuration

Command History

Usage Guidelines

The local alias table can be used to load static entries by performing as many of the commands as necessary. Aliases for the same IP address can be added in different commands, if required.

Typically, static aliases are needed to access endpoints that do not belong to a zone (that is, they are not registered with any gatekeeper) or whose gatekeeper is inaccessible.

Examples

The following example creates a static terminal alias in the local zone:

zone local gk.zone1.com zone1.com

alias static 192.168.8.5 gkid gk.zone1.com terminal e164 14085551212 h323id terminal1

allow-connections

To allow connections between specific types of endpoints in a VoIP network, use the allow-connections command in voice service configuration mode. To refuse specific types of connections, use the no form of this command.

allow-connections from-type to to-type

no allow-connections from-type to to-type

Syntax Description

Command Default

Cisco IOS Release 12.3(4)T, Cisco IOS Release 12.3, and Earlier Releases

H.323-to-H.323 connections are enabled by default and cannot be changed, and POTS-to-any and any-to-POTS connections are disabled.

Cisco IOS Release 12.3(7)T and Later Releases

H.323-to-H.323 connections are disabled by default and can be changed, and POTS-to-any and any-to-POTS connections are enabled.

H.323-to-SIP Connections

H.323-to-SIP and SIP-to-H.323 connections are disabled by default, and POTS-to-any and any-to-POTS connections are enabled.

SIP-to-SIP Connections

SIP-to-SIP connections are disabled by default, and POTS-to-any and any-to-POTS connections are enabled.

Command Modes

Voice service configuration

Command History

Usage Guidelines

Cisco IOS Release 12.3(4)T, Cisco IOS Release 12.3, and Earlier Releases

This command is used to allow connections between specific types of endpoints in a Cisco multiservice IP-to-IP gateway. The command is enabled by default and cannot be changed. Connections to or from POTS endpoints are not allowed. Only H.323-to-H.323 connections are allowed.

Cisco IOS Release 12.3(7)T and Later Releases

This command is used with Cisco Unified Communications Manager Express 3.1 or later systems and with the Cisco Multiservice IP-to-IP Gateway feature. In Cisco Unified Communications Manager Express, the allow-connections command enables the VoIP-to-VoIP connections used for hairpin call routing or routing to an H.450 tandem gateway.

Examples

The following example specifies that connections between H.323 and SIP endpoints are allowed:

Router(config-voi-serv)# allow-connections h323 to sip

The following example specifies that connections between H.323 endpoints are allowed:

Router(config-voi-serv)# allow-connections h323 to h323

The following example specifies that connections between SIP endpoints are allowed:

Router(config-voi-serv)# allow-connections sip to sip

Related Commands

allow subscribe

To allow internal watchers to monitor external presentities, use the allow subscribe command in presence configuration mode. To disable external watching, use the no form of this command.

allow subscribe

no allow subscribe

Syntax Description

This command has no arguments or keywords.

Command Default

Only internal presentities can be watched when presence is enabled.

Command Modes

Presence configuration (config-presence)

Command History

Usage Guidelines

This command allows internal watchers to receive Busy Lamp Field (BLF) status notification for external directory numbers on a remote router connected through a SIP trunk. An external directory number must be enabled as a presentity with the allow watch command.

The router sends SUBSCRIBE requests through the SIP trunk to an external presence server on behalf of the internal watcher and returns presence status to the watcher. To permit the external directory numbers to be watched, you must enable the watcher all command on the remote router.

Examples

The following example shows how to enable internal watchers to monitor external presentities:

Router(config)# presence

Router(config-presence)# allow subscribe

Related Commands

alt-dial

To configure an alternate dial-out string for dial peers, use the alt-dial command in dial peer configuration mode. To delete the alternate dial-out string, use the no form of this command.

alt-dial string

no alt-dial string

Syntax Description

Command Default

No alternate dial-out string is configured

Command Modes

Dial Peer configuration

Command History

Usage Guidelines

This command applies to plain old telephone service (POTS), Voice over Frame Relay (VoFR), and Voice  ATM (VoATM) dial peers.

The alt-dial command is used for the on-net-to-off-net alternative dialing function. The string replaces the destination-pattern string for dialing out.

Examples

The following example configures an alternate dial-out string of 95550188:

alt-dial 95550188

anat

To enable Alternative Network Address Types (ANAT) on a Session Initiation Protocol (SIP) trunk, use the anat command in voice service voip-sip configuration mode or dial peer configuration mode. To ANAT on SIP trunks, use the no form of this command.

anat

no anat

Syntax Description

This command has no arguments or keywords.

Command Default

ANAT is enabled on SIP trunks.

Command Modes

Voice service voip-sip configuration
Dial peer configuration

Command History

Usage Guidelines

Both the Cisco IOS SIP gateway and the Cisco Unified Border Element are required to support Session Description Protocol (SDP) ANAT semantics for SIP IPv6 sessions. SDP ANAT semantics are intended to address scenarios that involve different network address families (for example, different IP versions). Media lines grouped using ANAT semantics provide alternative network addresses of different families for a single logical media stream. The entity creating a session description with an ANAT group must be ready to receive or send media over any of the grouped "m" lines.

By default, ANAT is enabled on SIP trunks. However, if the SIP gateway is configured in IPv4-only or IPv6-only mode, the gateway will not use ANAT semantics in its SDP offer.

Examples

The following example enables ANAT on a SIP trunk:

router(conf-serv-sip)# anat

ani mapping

To preprogram the Numbering Plan Area (NPA), or area code, into a single Multi Frequency (MF) digit, use the ani mapping command in voice-port configuration mode. To disable Automatic Number Identification (ANI) mapping, use the no form of this command.

ani mapping npd-value npa-number

no ani mapping

Syntax Description

Command Default

No default behavior or values

Command Modes

Voice-port configuration

Command History

Usage Guidelines

The ani mapping command table translates the NPA into a single MF digit. The number of NPDs programmed is determined by local policy as well as by the number of NPAs that the public service answering point (PSAP) serves. Repeat this command until all NPDs are configured or until the NPD maximum range is reached.

Examples

The following example shows the voice port preprogramming the NPA into a single MF digit:

voice-port 1/1/0

 timing digit 100

 timing inter-digit 100

 ani mapping 1 408

 signal cama KP-NPD-NXX-XXXX-ST

!

voice-port 1/1/1

 timing digit 100

 timing inter-digit 100

 ani mapping 1 408

 signal cama KP-NPD-NXX-XXXX-ST

Related Commands

answer-address

To specify the full E.164 telephone number to be used to identify the dial peer of an incoming call, use the answer-address command in dial peer configuration mode. To disable the configured telephone number, use the no form of this command.

answer-address [+]string[T]

no answer-address

Syntax Description

+	(Optional) Character that indicates an E.164 standard number.
string	Series of digits that specify a pattern for the E.164 or private dialing plan telephone number. Valid entries are the digits 0 through 9, the letters A through D, and the following special characters: •The asterisk (*) and pound sign (#) that appear on standard touch-tone dial pads. •Comma (,), which inserts a pause between digits. •Period (.), which matches any entered digit (this character is used as a wildcard). •Percent sign (%), which indicates that the preceding digit occurred zero or more times; similar to the wildcard usage. •Plus sign (+), which indicates that the preceding digit occurred one or more times. Note The plus sign used as part of a digit string is different from the plus sign that can be used in front of a digit string to indicate that the string is an E.164 standard number. •Circumflex (^), which indicates a match to the beginning of the string. •Dollar sign ($), which matches the null string at the end of the input string. •Backslash symbol (\), which is followed by a single character, and matches that character. Can be used with a single character with no other significance (matching that character). •Question mark (?), which indicates that the preceding digit occurred zero or one time. •Brackets ( [ ] ), which indicate a range. A range is a sequence of characters enclosed in the brackets; only numeric characters from 0 to 9 are allowed in the range. •Parentheses ( ( ) ), which indicate a pattern and are the same as the regular expression rule.
T	(Optional) Control character that indicates that the destination-pattern value is a variable-length dial string. Using this control character enables the router to wait until all digits are received before routing the call.

Command Default

The default value is enabled with a null string

Command Modes

Dial peer voice configuration

Command History

Usage Guidelines

Use the answer-address command to identify the origin (or dial peer) of incoming calls from the IP network. Cisco IOS software identifies the dial peers of a call in one of two ways: by identifying either the interface through which the call is received or the telephone number configured with the answer-address command. In the absence of a configured telephone number, the peer associated with the interface is associated with the incoming call.

For calls that come in from a plain old telephone service (POTS) interface, the answer-address command is not used to select an incoming dial peer. The incoming POTS dial peer is selected on the basis of the port configured for that dial peer.

There are certain areas in the world (for example, certain European countries) where valid telephone numbers can vary in length. Use the optional control character T to indicate that a particular answer-address value is a variable-length dial string. In this case, the system does not match the dialed numbers until the interdigit timeout value has expired.

Note Cisco IOS software does not check the validity of the E.164 telephone number; it accepts any series of digits as a valid number.

Examples

The following example shows the E.164 telephone number 555-0104 as the dial peer of an incoming call being configured:

dial-peer voice 10 pots

 answer-address +5550104

Related Commands

application (dial peer)

To enable a specific application on a dial peer, use the application command in dial peer configuration mode. To remove the application from the dial peer, use the no form of this command.

application application-name [out-bound]

no application application-name [out-bound]

Syntax Description

Command Default

No default behavior or values

Command Modes

Dial peer voice configuration

Command History

Usage Guidelines

Use this command when configuring interactive voice response (IVR) or any of the IVR-related features to associate a predefined session application with an incoming POTS dial peer and an outgoing Multimedia Mail over IP (MMoIP) dial peer. Calls that use the incoming POTS dial peer and the outgoing MMoIP dial peer are handed off to the specified predefined session application.

Note In Cisco IOS Release 12.2(15)T and later releases, the application name default refers to the application new version of the default session application that supports OSP, call transfer, and call forwarding. The default session application in Cisco IOS Release 12.2(13)T and earlier releases has been renamed default.old.c and can still be configure for specific dial peers through the application command or globally configured for all inbound dial peers through the call application global command.

For Media Gateway Control Protocol (MGCP) and Simple Gateway Control Protocol (SGCP) networks, enter the application name in uppercase characters. For example, for MGCP networks, you would enter MGCPAPP for the application-name argument. The application can be applied only to POTS dial peers. Note that SGCP dial peers do not use dial-peer hunting.

Note In Cisco IOS Release 12.2, you cannot mix SGCP and non-SGCP endpoints in the same T1 controller, nor can you mix SGCP and non-SGCP endpoints in the same DS0 group.

Note MGCP scripting is not supported on the Cisco 1750 router or on Cisco 7200 series routers.

For H.323 networks, the application is defined by a Tool Command Language/interactive voice response (Tcl/IVR) filename and location. Incoming calls that use POTS dial peers and outgoing calls that use MMoIP dial peers are handed off to this application.

For Session Initiation Protocol (SIP) networks, use this command to associate a predefined session application. The default Tcl application (from the Cisco IOS image) for SIP is session and can be applied to both VoIP and POTS dial peers.

Examples

The following example defines an application and applies it to an outbound MMoIP dial peer for the fax on-ramp operation:

call application voice fax_on_vfc_onramp http://santa/username/clid_4digits_npw_3.tcl

dial-peer voice 3 mmoip

 application fax_on_vfc_onramp out-bound

 destination-pattern 57108..

 session target mailto:$d$@mail-server.cisco.com

The following example applies the MGCP application to a dial peer:

dial-peer voice 1 pots

 application MGCPAPP

The following example applies a predefined application to an incoming POTS dial peer:

dial-peer voice 100 pots

 application c4

The following example applies a predefined application to an outbound MMoIP dial peer for the on-ramp operation:

dial-peer voice 3 mmoip

 application fax_on_vfc_onramp_ap out-bound

 destination-pattern 57108..

 session target mailto:$d$@mail-server.cisco.com

The following example applies the predefined SIP application to a dial peer:

dial-peer voice 10 pots

 application session

For Cisco IOS Release 12.2(15)T, MCID was added as a valid application-name argument. The following is a sample configuration using the MCID application name:

call application voice mcid http://santa/username/app_mcid_dtmf.2.0.0.28.tcl

dial-peer voice 3 pots

 application mcid

 incoming called-number 222....

 direct-inward-dial

 port 1:D

Related Commands

application (global)

To enter application configuration mode to configure applications, use the application command in global configuration mode.

application

Syntax Description

This command has no keywords or arguments.

Command Default

No default behavior or values

Command Modes

Global configuration

Command History

Usage Guidelines

Use this command to enter application configuration mode. Related commands are used in application configuration mode to configure standalone applications (services) and linkable functions (packages).

Examples

The following example shows how to enter application configuration mode and configure a debit card service:

Enter application configuration mode to configure applications and services:

Router(config)# application

Load the debit card script:

Router(config-app)# service debitcard 
tftp://server-1/tftpboot/scripts/app_debitcard.2.0.2.8.tcl

Configure language parameters for the debit card service:

Router(config-app-param)# paramspace english language en

  paramspace english index 1

  paramspace english prefix en

  paramspace english location tftp://server-1/tftpboot/scripts/au/en/

Related Commands

arq reject-resource-low

To configure the gatekeeper to send an Admission Reject (ARJ) message to the requesting gateway if destination resources are low, use the arq reject-resource-low command in gatekeeper configuration mode. To disable the gatekeeper from checking resources, use the no form of this command.

arq reject-resource-low

no arq reject-resource-low

Syntax Description

This command has no arguments or keywords.

Command Default

No default behavior or values

Command Modes

Gatekeeper configuration

Command History

Examples

The following example shows that the gatekeeper is configured to send an ARJ message to the requesting gateway if destination resources are low:

gatekeeper

 arq reject-resource-low

Related Commands

arq reject-unknown-prefix

To enable the gatekeeper to reject admission requests (ARQs) for zone prefixes that are not configured, use the arq reject-unknown-prefix command in gatekeeper configuration mode. To reenable the gatekeeper to accept and process all incoming ARQs, use the no form of this command.

arq reject-unknown-prefix

no arq reject-unknown-prefix

Syntax Description

This command has no arguments or keywords

Command Default

The gatekeeper accepts and processes all incoming ARQs.

Command Modes

Gatekeeper configuration

Command History

Usage Guidelines

Use the arq reject-unknown-prefix command to configure the gatekeeper to reject any incoming ARQs for a destination E.164 address that does not match any of the configured zone prefixes.

When an endpoint or gateway initiates an H.323 call, it sends an ARQ to its gatekeeper. The gatekeeper uses the configured list of zone prefixes to determine where to direct the call. If the called address does not match any of the known zone prefixes, the gatekeeper attempts to hairpin the call out through a local gateway. If you do not want your gateway to do this, then use the arq reject-unknown-prefix command. (The term hairpin is used in telephony. It means to send a call back in the direction from which it came. For example, if a call cannot be routed over IP to a gateway that is closer to the target phone, the call is typically sent back out through the local zone, back the way it came.)

This command is typically used to either restrict local gateway calls to a known set of prefixes or deliberately fail such calls so that an alternate choice on a gateway's rotary dial peer is selected.

Examples

Consider a gatekeeper configured as follows:

zone local gk408 cisco.com

zone remote gk415 cisco.com 172.21.139.91

zone prefix gk408 1408.......

zone prefix gk415 1415.......

In this example configuration, the gatekeeper manages a zone containing gateways to the 408 area code, and it knows about a peer gatekeeper that has gateways to the 415 area code. Using the zone prefix command, the gatekeeper is then configured with the appropriate prefixes so that calls to those area codes hop off in the optimal zone.

If the arq request-unknown-prefix command is not configured, the gatekeeper handles calls in the following way:

•A call to the 408 area code is routed out through a local gateway.

•A call to the 415 area code is routed to the gk415 zone, where it hops off on a local gateway.

•A call to the 212 area code is routed to a local gateway in the gk408 zone.

If the arq reject-unknown-prefix command is configured, the gatekeeper handles calls in the following way:

•A call to the 408 area code is routed out through a local gateway.

•A call to the 415 area code is routed to the gk415 zone, where it hops off on a local gateway.

•A call to the 212 area code is rejected because the destination address does not match any configured prefix.

Related Commands

as

To define an application server for backhaul, use the as command in IUA configuration mode. To disable the backhaul ability from an application server, use the no form of this command.

as as-name {localip1 [localip2]} [local-sctp-port] [fail-over-timer] [sctp-startup-rtx] [sctp-streams] [sctp-t1init]

no as name

Syntax Description

Command Default

No application server is defined.

Command Modes

IUA configuration

Command History

Usage Guidelines

A maximum of two local IP addresses can be specified. (Note that SCTP has built-in support for multihomed machines.)

Note All of the ASPs in an application server must be removed before an application server can be unconfigured.

The default value of the SCTP streams is determined by the hardware that you have installed. The value of the failover timer is found in the show iua as all command output.

The number of streams to assign to a given association is implementation dependent. During the initialization of the IUA association, you need to specify the total number of streams that can be used. Each D channel is associated with a specific stream within the association. With multiple trunk group support, every interface can potentially be a separate D channel.

At startup, the IUA code checks for all the possible T1, E1, or T3 interfaces and sets the total number of inbound and outbound streams supported accordingly. In most cases, there is only a need for one association between the gateway (GW) and the Media Gateway Controller (MGC). For the rare case that you are configuring multiple AS associations to various MGCs, the overhead from the unused streams would have minimal impact. The NFAS D channels are configured for one or more interfaces, where each interface is assigned a unique stream ID.

The total number of streams for the association needs to include an additional stream for the SCTP management messages. So during startup, the IUA code adds one to the total number of interfaces (streams) found.

You have the option to manually configure the number of streams per association. In the backhaul scenario, if the number of D channel links is limited to one, allowing the number of streams to be configurable avoids the unnecessary allocation of streams in an association that is never used. For multiple associations between a GW and multiple MGCs, the configuration utility is useful in providing only the necessary number of streams per association. The overhead from the streams allocated but not used in the association is negligible.

If the number of streams is manually configured through the CLI, the IUA code cannot distinguish between a startup event, which automatically sets the streams to the number of interfaces, or if the value is set manually during runtime. If you are configuring the number of SCTP streams manually, you must add one plus the number of interfaces using the sctp-streams keyword. Otherwise, IUA needs to always add one for the management stream, and the total number of streams increments by one after every reload.

When you set the SCTP stream with the CLI, you cannot change the inbound and outbound stream support once the association is established with SCTP. The value takes effect when you first remove the IUA AS configuration and then configure it back as the same application server or a new one. The other option is to reload the router.

Examples

An application server and the application server process (ASP) should be configured first to allow a National ISDN-2 with Cisco extensions (NI2+) to be bound to this transport layer protocol. The application server is a logical representation of the SCTP local endpoint. The local endpoint can have more than one IP address but must use the same port number.

The following is an example of an application server configuration on a gateway. The configuration shows that an application server named as5400-3 is configured to use two local IP addresses and a port number of 2577:

Router(config-iua)# as as5400-3 10.1.2.34 10.1.2.35 2577

The following output shows that the application server (as1) is defined for backhaul:

AS as1 10.21.0.2 9900

Related Commands

asp

To define an application server process (ASP) for backhaul, use the asp command in IUA configuration mode. To disable the ASP, use the no form of this command.

asp asp-name as as-name {remoteip1 [remoteip2]} [remote-sctp-port] [ip-precedence [sctp-keepalives] [sctp-max-associations] [sctp-path-retransmissions] [sctp-t3-timeout]

no asp asp-name

Syntax Description

Command Default

No ASP is defined.

Command Modes

IUA configuration

Command History

Usage Guidelines

Note All of the ASPs in an application server must be removed before an application serever can be unconfigured.

You can configure the precedence value in IUA in the range of 0 to 7 for a given IP address. Within IUA, the upper three bits representing the IP precedence in the ToS byte (used in the IP header) is set based on the user input before passing down the value to SCTP. In turn, SCTP passes the ToS byte value to IP. The default value is 0 for "normal" IP precedence handling.

The asp-name argument specifies the name of this ASP. The ip-precedence keyword sets the precedence and ToS field. The remote-ip-address argument specifies the IP address of the remote end-point (the address of MGC, for example). The number argument can be any IP precedence bits in the range 1 to 255.

The no form of the command results in precedence bits not being explicitly set by SCTP.

In the case of a hot-standby Cisco PGW2200 pair, from the gateway (GW) perspective there is usually one ASP active and another in the INACTIVE state. The ASP_UP message is used to bring the ASP state on the GW to the INACTIVE state, followed by the ASPTM message, ASP_ACTIVE to ready the IUA link for data exchange. (Eventually the QPTM Establish Request message actually initiates the start of the D channel for the given interface.) In the event that the GW detects a failure on the active ASP, it can send a NTFY message to the standby ASP to request that it become active.

Examples

An ASP can be viewed as a local representation of an SCTP association because it specifies a remote endpoint that is in communication with an AS local endpoint. An ASP is defined for a given AS. For example, the following configuration defines a remote signaling controller asp-name at two IP addresses for AS as1. The remote SCTP port number is 2577:

Router(config-iua)# as as1 10.4.8.69, 10.4.9.69 2477

Router(config-iua)# asp asp1 as as1 10.4.8.68 10.4.9.68 2577

Multiple ASPs can be defined for a single AS for the purpose of redundancy, but only one ASP can be active. The ASPs are inactive and only become active after fail-over.

In the Cisco Media Gateway Controller (MGC) solution, a signaling controller is always the client that initiates the association with a gateway. During the initiation phase, you can request outbound and inbound stream numbers, but the gateway only allows a number that is at least one digit higher than the number of interfaces (T1/E1) allowed for the platform.

The following example specifies the IP precedence level on the specified IP address. This example uses IP precedence level 7, which is the maximum level allowed:

Router(config-iua)# asp asp1 as ip-precedence 10.1.2.345 7

The following example specifies the IP address to enable and disable keepalives:

Router(config-iua)# asp asp1 as sctp-keepalive 10.1.2.34

The following example specifies the keepalive interval in milliseconds. In this example, the maximum value of 60000 ms is used:

Router(config-iua)# asp asp1 as sctp-keepalive 10.10.10.10 60000

The following example specifies the IP address for the SCTP maximum association and the maximum association value. In this example, a maximum value of 20 is used:

Router(config-iua)# asp asp1 as sctp-max-association 10.10.10.10 20

The following example specifies the IP address for the SCTP path retransmission and the maximum path retransmission value. In this example, a maximum value of 20 is used:

Router(config-iua)# asp asp1 as sctp-path-retransmissions 10.10.10.10 10

The following example specifies the IP address for SCTP T3 timeout and specifies the T3 timeout value in milliseconds. In this example, the maximum value of 60000 is used:

Router(config-iua)# asp asp1 as sctp-t3-timeout 10.10.10.10 60000

Related Commands

asserted-id

To set the privacy level and enable either P-Asserted-Identity (PAI) or P-Preferred-Identity (PPI) privacy headers in outgoing SIP requests or response messages, use the asserted-id command in voice service voip-sip configuration mode or on a dial peer. To remove the privacy level of either PAI or PPI, use the no form of this command.

asserted-id [pai | ppi]

no asserted-id

Syntax Description

Command Default

The command is disabled.

Command Modes

Voice service voip-sip configuration
Dial-peer configuration

Command History

Usage Guidelines

Enter SIP configuration mode from voice-service configuration mode, as shown in the example.

If you configure the asserted-id pai command, the gateway builds a P-Asserted-Identity header into the common SIP stack. The asserted-id pai command has a priority over the Remote-Party-ID (RPID) header and removes this header from any outbound message, even if the router is configured to use the RPID header.

If you configure the asserted-id ppi command, the gateway builds a P-Preferred-Identity header into the common SIP stack. The asserted-id ppi command has a priority over the Remote-Party-ID (RPID) header and removes this header from any outbound message, even if the router is configured to use the RPID header.

Examples

The following example shows how to set the P-Asserted Identity in the privacy header:

router> enable 

router# configure terminal

router(config)# voice service voip 

router(conf-voi-serv)# sip

router(conf-serv-sip)# asserted-id pai

Related Commands

associate application

To associate an application to the digital signal processor (DSP) farm profile, use the associate application command in DSP farm profile configuration mode. To remove the protocol, use the no form of this command.

associate application {cube | sbc | sccp} profile-description-text

no associate application sccp

Syntax Description

Command Default

No application is associated with the DSP farm profile.

Command Modes

DSP farm profile configuration

Command History

Usage Guidelines

Use the associate application command to associate an application to a predefinded DSP farm profile.

Examples

The following example associates SCCP to the DSP farm profile:

Router(config-dspfarm-profile)# associate application sccp 

The following example associates Cisco Unified Border Element to the DSP farm profile:

Router(config-dspfarm-profile)# associate application cube 

Related Commands

associate ccm

To associate a Cisco Unified CallManager with a Cisco CallManager group and establish its priority within the group, use the associate ccm command in the SCCP Cisco CallManager configuration mode. To disassociate a Cisco Unified CallManager from a Cisco CallManager group, use the no form of this command.

associate ccm identifier-number priority priority-number

no associate ccm identifier-number priority priority-number

Syntax Description

Command Default

No default behavior or values

Command Modes

SCCP Cisco CallManager configuration

Command History

Examples

The following example associates Cisco Unified CallManager 125 with Cisco CallManager group 999 and sets the priority of the Cisco Unified CallManager within the group to 2:

Router(config)# sccp ccm group 999

Router(config-sccp-ccm)# associate ccm 125 priority 2

Related Commands

associate profile

To associate a digital signal processor (DSP) farm profile with a Cisco CallManager group, use the associate profile command in SCCP Cisco CallManager configuration mode. To disassociate a DSP farm profile from a Cisco Unified CallManager, use the no form of this command.

associate profile profile-identifier register device-name

no associate profile profile-identifier register device-name

Syntax Description

Command Default

This command is not enabled.

Command Modes

SCCP Cisco CallManager configuration

Command History

Usage Guidelines

The device name must match the name configured in Cisco UnifiedCallManager; otherwise the profile is not registered to Cisco Unified CallManager.

Note Each profile can be associated to only one Cisco CallManager group.

Examples

The following example associates DSP farm profile abgz12345 to Cisco CallManager group 999:

Router(config)# sccp ccm group 999 

Router(conif-sccp-ccm)# associate profile 1 register abgz12345

Related Commands

associate registered-number

To associate the preloaded route and outbound proxy details with the registered number, use the associate registered-number command in voice service VoIP SIP configuration mode. To remove the association, use the no form of this command.

associate registered-number number

no associate registered-number

Syntax Description

Command Default

The preloaded route and outbound proxy details are not associated with the registered number by default.

Command Modes

Voice service VoIP SIP configuration (conf-serv-sip)

Command History

Examples

The following example shows how to associate a registered number in the SIP configuration mode:

Router> enable 

Router# configure terminal

Router(config)# voice service voip 

Router(conf-voi-serv)# sip

Router(conf-serv-sip)# associate registered-number 5

Related Commands

asymmetric payload

To configure Session Initiation Protocol (SIP) asymmetric payload support, use the asymmetric payload command in SIP configuration mode. To disable asymmetric payload support, use the no form of this command.

asymmetric payload {dtmf | dynamic-codecs | full | system}

no asymmetric payload

Syntax Description

Command Default

This command is disabled.

Command Modes

Voice service SIP configuration (conf-serv-sip)

Command History

Usage Guidelines

Enter SIP configuration mode from voice-service configuration mode, as shown in the example.

For the Cisco UBE the SIP asymmetric payload-type is supported for audio/video codecs, DTMF, and NSE. Hence, dtmf and dynamic-codecs keywords are internally mapped to the full keyword to provide asymmetric payload-type support for audio/video codecs , DTMF, and NSE.

Examples

The following example shows how to set up a full asymmetric payload globally on a SIP network for both DTMF and dynamic codecs:

Router(config)# voice service voip

Router(conf-voi-serv)# sip

Router(conf-serv-sip)# asymmetric payload full

Related Commands

atm scramble-enable

To enable scrambling on E1 links, use the atm scramble-enable command in interface configuration mode. To disable scrambling, use the no form of this command.

atm scramble-enable

no atm scramble-enable

Syntax Description

This command has no arguments or keywords.

Command Default

By default, payload scrambling is set off

Command Modes

Interface configuration

Command History

Usage Guidelines

Enable scrambling on E1 links only. On T1 links, the default binary 8-zero substitution (B8ZS) line encoding normally ensures sufficient reliability. Scrambling improves data reliability on E1 links by randomizing the ATM cell payload frames to avoid continuous nonvariable bit patterns and to improve the efficiency of the ATM cell delineation algorithms.

The scrambling setting must match that of the far end.

Examples

The following example shows how to set the ATM0 E1 link to scramble payload:

interface atm0

 atm scramble-enable

atm video aesa

To set the unique ATM end-station address (AESA) for an ATM video interface that is using switched virtual circuit (SVC) mode, use the atm video aesa command in ATM interface configuration mode. To remove any configured address for the interface, use the no form of this command.

atm video aesa [default | esi-address]

no atm video aesa

Syntax Description

Command Default

default

Command Modes

ATM Interface configuration

Command History

Usage Guidelines

You cannot specify the ATM interface NSAP address in its entirety. The system creates either all of the address or part of it, depending on how you use this command.

Examples

The following example shows the ATM interface NSAP address set automatically:

interface atm0

 atm video aesa default

The following example shows the ATM interface NSAP address set to a specific ESI value:

interface atm0/1

 atm video aesa 444444444444

Related Commands

attribute acct-session-id overloaded

To overload the acct-session-id attribute with call detail records, use the attribute acct-session-id overloaded command in gateway accounting AAA configuration mode. To disable overloading the acct-session-id attribute with call detail records, use the no form of this command.

attribute acct-session-id overloaded

no attribute acct-session-id overloaded

Syntax Description

This command has no arguments or keywords.

Command Default

The acct-session-id attribute is not overloaded with call detail records.

Command Modes

Gateway accounting AAA configuration

Command History

Usage Guidelines

•The attribute acct-session-id overloaded command replaces the gw-accounting h323 command.

•The acct-session-id attribute is RADIUS attribute 44. For more information on this attribute, see the document RADIUS Attribute 44 (Accounting Session ID) in Access Requests.

•Attributes that cannot be mapped to standard RADIUS attributes are packed into the acct-session-id attribute field as ASCII strings separated by the forward slash ("/") character.

•The Accounting Session ID (acct-session-id) attribute contains the RADIUS account session ID, which is a unique identifier that links accounting records associated with the same login session for a user. This unique identifier makes it easy to match start and stop records in a log file.

•Accounting Session ID numbers restart at 1 each time the router is power-cycled or the software is reloaded.

Examples

The following example shows the acct-session-id attribute being overloaded with call detail records:

gw-accounting aaa

 attribute acct-session-id overloaded 

Related Commands

attribute h323-remote-id resolved

To resolve the h323-remote-id attribute, use the attribute h323-remote-id resolved command in gateway accounting AAA configuration mode. To keep the h323-remote-id attribute unresolved, use the no form of this command.

attribute h323-remote-id resolved

no attribute h323-remote-id resolved

Syntax Description

This command has no arguments or keywords.

Command Default

The h323-remote-id attribute is not resolved.

Command Modes

gateway accounting aaa configuration

Command History

Usage Guidelines

In Cisco IOS Release 12.2(11)T, the attribute h323-remote-id resolved command replaces the gw-accounting h323 resolve command, and the h323-remote-id attribute has been added as a Cisco vendor-specific attribute (VSA). This attribute is a string that indicates the Domain Name System (DNS) name or locally defined host name of the remote gateway.

You can obtain the value of the h323-remote-id attribute by doing a DNS lookup of the h323-remote-address attribute. The h323-remote-address attribute indicates the IP address of the remote gateway.

Examples

The following example sets the h323-remote-id attribute to resolved:

gw-accounting aaa

 attribute h323-remote-id resolved 

Related Commands

audio

To enable the incoming and outgoing IP-IP call gain/loss feature for audio volume control on the incoming dial peer and the outgoing dial peer, enter the audio command in dial-peer configuration mode. To disable this feature, use the no form of this command.

audio {incoming | outgoing} level adjustment value

no audio {incoming | outgoing} level adjustment value

Syntax Description

Command Default

This command is disabled by default, and there is no volume control available.

Command Modes

Dial-peer configuration (config-dialpeer)

Command History

Usage Guidelines

This feature enables the adjustment of the audio volume within a Cisco Unified Border Element (Cisco UBE) call. As with codec repacketization, dissimilar networks that have different built-in loss/gain characteristics may experience connectivity problems. By adding the ability to control the loss/gain within the Cisco UBE, you can more easily connect your networks.

The DSP requires one level for each stream, so the value for audio incoming level-adjustment and the value for audio outgoing level-adjustment will be added together. If the combined values are outside of the limit the DSP can perform, the value sent to the DSP will be either the minimum (-27) or maximum (+16) supported by the DSP.

Caution For gain/loss control, be aware that adding gain in a network with echo can generate feedback loud enough to cause hearing damage. Always exercise extreme caution when configuring gain into your network.

To configure IP-IP Call Gain/Loss Control on a voice gateway, you must configure the incoming and outgoing VoIP dial peers.

Examples

The following example shows how to configure audio incoming level to 5 and the audio outgoing level to -5:

Router(config-dialpeer)# audio incoming level-adjustment 5

Router(config-dialpeer)# audio outgoing level-adjustment -5

Related Commands

audio-prompt load

To initiate loading the selected audio file (.au), which contains the announcement prompt for the caller, from Flash memory into RAM, use the audio-prompt load command in privileged EXEC mode. This command does not have a no form.

audio-prompt load name

Syntax Description

Command Default

No default behavior or values

Command Modes

Privileged EXEC

Command History

Usage Guidelines

The first time the interactive voice response (IVR) application plays a prompt, it reads it from the URL (or the specified location for the .au file, such as Flash or FTP) into RAM. Then it plays the script from RAM. An example of the sequence of events follows:

•When the first caller is asked to enter the account and personal identification numbers (PINs), the enter_account.au and enter_pin.au files are loaded into RAM from Flash memory.

•When the next call comes in, these prompts are played from the RAM copy.

•If all callers enter valid account numbers and PINs, the auth_failed.au file is not loaded from Flash memory into RAM.

The router loads the audio file only when the script initially plays that prompt after the router restarts. If the audio file is changed, you must run this privileged EXEC command to reread the file. This generates an error message if the file is not accessible or if there is a format error.

Examples

The following example shows how to load the enter_pin.au audio file from Flash memory into RAM:

audio-prompt load flash:enter_pin.au

The following example shows how to load the hello.au audio file from an HTTPS server into RAM:

audio-prompt load https://http-server1/audio/hello.au

authenticate redirecting-number

To enable a Cisco IOS voice gateway to authenticate and pass Session Initiation Protocol (SIP) credentials based on the redirecting number when available instead of the calling number of a forwarded call, use the authenticate redirecting-number command in voice service SIP configuration mode. To return a Cisco IOS voice gateway to the default setting so that the gateway uses only the calling number for SIP credentials, use the no form of this command.

authenticate redirecting-number

no authenticate redirecting-number

Syntax Description

This command has no arguments or keywords.

Command Default

The Cisco IOS voice gateway uses only the calling number of a forwarded call for SIP credentials even when the redirecting number information is available for that call.

Command Modes

Voice service SIP configuration (conf-serv-sip)

Command History

Usage Guidelines

When an INVITE message sent out by the gateway is challenged, it must respond with the appropriate SIP credentials before the call is established. The default global behavior for the gateway is to authenticate and pass SIP credentials based on the calling number and all dial peers on a gateway default to the global setting. However, for forwarded calls, it is sometimes more appropriate to use the redirecting number and this can be specified at either the global or dial peer level (configuring behavior for a specific dial peer supersedes the global setting).

Use the authenticate redirecting-number command in voice service SIP configuration mode to globally enable a Cisco IOS voice gateway to authenticate and pass SIP credentials based on the redirecting number when available. Use the no form of this command to configure the gateway to authenticate and pass SIP credentials based only on the calling number of forwarded calls unless otherwise configured at the dial peer level:

•Use the voice-class sip authenticate redirecting-number command in dial peer voice configuration mode to supersede global settings and force a specific dial peer on the gateway to authenticate and pass SIP credentials based on the redirecting number when available.

•Use the no form of the voice-class sip authenticate redirecting-number command in dial peer voice configuration mode to supersede global settings and force a specific dial peer on the gateway to authenticate and pass SIP credentials based only on the calling number regardless of the global setting.

The redirecting number is present only in the headers of forwarded calls. When this command is disabled or the redirecting number is not available (nonforwarded calls), the gateway uses the calling number for SIP credentials.

Examples

The following example shows how to globally enable a Cisco IOS voice gateway to authenticate and pass the redirecting number of a forwarded call when a SIP INVITE message is challenged:

Router> enable 

Router# configure terminal

Router(config)# voice service voip 

Router(conf-voi-serv)# sip

Router(conf-serv-sip)# authenticate redirecting-number

Related Commands

authentication (dial peer)

To enable SIP digest authentication on an individual dial peer, use the authentication command in dial peer voice configuration mode. To disable SIP digest authentication, use the no form of this command.

authentication username username password [0 | 7] password [realm realm [challenge]]

no authentication username username [password [0 | 7] password [realm realm [challenge]]]

Syntax Description

Command Default

SIP digest authentication is disabled.

Command Modes

Dial peer voice configuration (config-dial-peer)

Command History

Usage Guidelines

The following configuration rules are applicable when enabling digest authentication:

•Only one username can be configured per dial peer. Any existing username configuration must be removed before configuring a different username.

•A maximum of five password or realm arguments can be configured for any one username.

The username and password arguments are used to authenticate a user. An authenticating server/proxy issuing a 407/401 challenge response includes a realm in the challenge response and the user provides credentials that are valid for that realm. Because it is assumed that a maximum of five proxy servers in the signaling path can try to authenticate a given request from a user-agent client (UAC) to a user-agent server (UAS), a user can configure up to five password and realm combinations for a configured username.

Note The user provides the password in plain text but it is encrypted and saved for 401 challenge response. If the password is not saved in encrypted form, a junk password is sent and the authentication fails.

•The realm specification is optional. If omitted, the password configured for that username applies to all realms that attempt to authenticate.

•Only one password can be configured at a time for all configured realms. If a new password is configured, it overwrites any previously configured password.

This means that only one global password (one without a specified realm) can be configured. If you configure a new password without configuring a corresponding realm, the new password overwrites the previous one.

•If a realm is configured for a previously configured username and password, that realm specification is added to that existing username and password configuration. However, once a realm is added to a username and password configuration, that username and password combination is valid only for that realm. A configured realm cannot be removed from a username and password configuration without first removing the entire configuration for that username and password—you can then reconfigure that username and password combination with or without a different realm.

•In an entry with both a password and realm, you can change either the password or realm.

Examples

The following example shows how to enable the digest authentication:

Router> enable

Router# configure terminal

Router(config)# dial-peer voice 1 pots

Router(config-dial-peer)# authentication username MyUser password 7 MyPassword realm 
MyRealm.example.com

The following example shows how to remove a previously configured digest authentication:

Router> enable

Router# configure terminal

Router(config)# dial-peer voice 1 pots

Router(config-dial-peer)# no authentication username MyUser password MyPassword

Related Commands

authentication (SIP UA)

To enable SIP digest authentication, use the authentication command in SIP UA configuration mode. To disable SIP digest authentication, use the no form of this command.

authentication username username password [0 | 7] password [realm realm]

no authentication username username [password [0 | 7] password [realm realm]]

Syntax Description

Command Default

SIP digest authentication is disabled.

Command Modes

SIP UA configuration (config-sip-ua)

Command History

Usage Guidelines

The following configuration rules are applicable when enabling digest access authentication:

•Only one username can be configured globally in SIP UA configuration mode. Any existing username configuration must be removed before configuring a different username.

•A maximum of five password or realm arguments are allowed for a given username argument.

The username and password arguments are used to authenticate a user. An authenticating server/proxy issuing a 407/401 challenge response includes a realm in the challenge response and the user provides credentials that are valid for that realm. Because it is assumed that a maximum of five proxy servers in the signaling path can try to authenticate a given request from a user-agent client (UAC) to a user-agent server (UAS), a user can configure up to five password and realm combinations for a configured username.

•The realm specification is optional. If omitted, the password configured for that username applies to all realms that attempt to authenticate.

•Only one password can be configured at a time for all configured realms. If a new password is configured, it overwrites any previously configured password.

This means that only one global password (one without a specified realm) can be configured. If you configure a new password without configuring a corresponding realm, the new password overwrites the previous one.

•If a realm is configured for a previously configured username and password, that realm specification is added to that existing username and password configuration. However, once a realm is added to a username and password configuration, that username and password combination is valid only for that realm. A configured realm cannot be removed from a username and password configuration without first removing the entire configuration for that username and password—you can then reconfigure that username and password combination with or without a different realm.

•In an entry with both a password and realm, you can change either the password or realm.

Examples

The following example shows how to enable digest access authentication:

Router> enable

Router# configure terminal

Router(config)# sip-ua

Router(config-sip-ua)# authentication username MyUser password MyPassword realm 
example.com

The following example shows how to remove a previously configured digest access authentication:

Router> enable

Router# configure terminal

Router(config)# sip-ua

Router(config-sip-ua)# no authentication username MyUser password MyPassword realm 
example.com

Related Commands

authentication method

To set an authentication method at login for calls that come into a dial peer, use the authentication method command in voice class AAA configuration mode. To disable the authentication method set at login, use the no form of this command.

authentication method MethListName

no authentication method MethListName

Syntax Description

Command Default

When this command is not used to specify a login authentication method, the system uses the aaa authentication login h323 command as the default.

Command Modes

Voice class AAA configuration

Command History

Usage Guidelines

This command is used to direct authentication requests to a RADIUS server based on dialed number information service (DNIS) or trunk grouping.

This command is used for directing dial-peer-based authentication requests. The method list must be defined during initial authentication setup.

Examples

In the example below, "dp" is the method list name used for authentication. The method list name is defined during initial authentication setup.

voice class aaa 1

 authentication method dp

Related Commands

authorization method

To set an authorization method at login for calls that are into a dial peer, use the authorization method command in voice class AAA configuration mode. To disable the authorization method set at login, use the no form of this command.

authorization method MethListName

no authorization method MethListName

Syntax Description

Command Default

When this command is not used to specifiy a login authorization method, the system uses the aaa authorization exec h323 command as the default.

Command Modes

Voice class AAA configuration

Command History

Usage Guidelines

This command is used to direct authentication requests to a RADIUS server based on dialed number information service (DNIS) or trunk grouping.

This command is used for directing dial-peer-based authentication requests. The method list must be defined during initial authentication setup.

Examples

The following example set an authorization method of "dp":

voice class aaa 1

 authorization method dp 

Related Commands

auto-config

To enable auto-configuration or to enter auto-config application configuration mode for the Skinny Client Control Protocol (SCCP) application, use the auto-config command in global configuration mode. To disable auto-configuration, use the no form of this command.

auto-config [application sccp]

no auto-config

Syntax Description

Command Default

Auto-configuration is disabled.

Command Modes

Global configuration

Command History

Examples

The following example shows the auto-config command used to enter auto-configuration application configuration mode for the SCCP application and the no shutdown command used to enable the SCCP application for download:

Router(config)# auto-config application sccp

Router(auto-config-app)# no shutdown

Related Commands

auto-cut-through

To enable call completion when a PBX does not provide an M-lead response, use the auto-cut-through command in voice-port configuration mode. To disable the auto-cut-through operation, use the no form of this command.

auto-cut-through

no auto-cut-through

Syntax Description

This command has no arguments or keywords.

Command Default