![]() |
Cisco IOS Voice Command Reference - A through C
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
clid through credentials (sip-ua)
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Contents
clid through credentials (sip-ua) clidTo preauthenticate calls on the basis of the Calling Line IDentification (CLID) number, use the clid command in AAA preauthentication configuration mode. To remove the clid command from your configuration, use the no form of this command.
clid
[if-avail | required]
[accept-stop]
[password password]
no
clid
[if-avail | required]
[accept-stop]
[password password]
Syntax Description
Command DefaultThe if-avail and required keywords are mutually exclusive. If the if-avail keyword is not configured, the preauthentication setting defaults to required. Usage GuidelinesYou may configure more than one of the authentication, authorization and accounting (AAA) preauthentication commands (clid, ctype, dnis) to set conditions for preauthentication. The sequence of the command configuration decides the sequence of the preauthentication conditions. For example, if you configure dnis, then clid, then ctype, in this order, then this is the order of the conditions considered in the preauthentication process. In addition to using the preauthentication commands to configure preauthentication on the Cisco router, you must set up the preauthentication profiles on the RADIUS server. ExamplesThe following example specifies that incoming calls be preauthenticated on the basis of the CLID number: aaa preauth group radius clid required Related Commands
clid (dial peer)To control the presentation and use of calling-line ID (CLID) information, use the clid command in dial peer configuration mode. To remove CLID controls, use the no form of this command.
clid
{network-number number [second-number strip] | network-provided | override rdnis | restrict | strip [name | pi-restrict [all] ] | substitute name}
no
clid
{network-number number [second-number strip] | network-provided | override rdnis | restrict | strip [name | pi-restrict [all] ] | substitute name}
Syntax DescriptionUsage GuidelinesThe overriderdnis keywords are supported only for POTS dial peers. CLID is the collection of information about the billing telephone number from which a call originated. The CLID value might be the entire phone number, the area code, or the area code plus the local exchange. It is also known as caller ID. The various keywords to this command manage the presentation, restriction, or stripping of the various CLID elements. The clidnetwork-number command sets the presentation indicator to "y" and the screening indicator to "network-provided." The second-numberstrip keyword strips from the H.225 source-address field the original calling-party number, and is valid only if a network number was previously configured. The clidoverriderdnis command overrides the CLID with the RDNIS if it is available. The clidrestrict command causes the calling-party number to be present in the information element, but the presentation indicator is set to "n" to prevent its presentation to the called party. The clidstrip command causes the calling-party number to be null in the information element, and the presentation indicator is set to "n" to prevent its presentation to the called party. ExamplesThe following example sets the calling-party network number to 98765 for POTS dial peer 4321: Router(config)# dial-peer voice 4321 pots Router(config-dial-peer)# clid network-number 98765 An alternative method of accomplishing this result is to enter the second-numberstrip keywords as part of the clidnetwork-number command. The following example sets the calling-party network number to 56789 for VoIP dial peer 1234 and also prevents the second network number from being sent: Router(config)# dial-peer voice 1234 voip Router(config-dial-peer)# clid network-number 56789 second-number strip The following example overrides the calling-party number with RDNIS if available:
Router(config-dial-peer)# clid override rdnis
The following example prevents the calling-party number from being presented:
Router(config-dial-peer)# clid restrict
The following example removes the calling-party number from the CLID information and prevents the calling-party number from being presented:
Router(config-dial-peer)# clid strip
The following example strips the name from the CLID information and prevents the name from being presented:
Router(config-dial-peer)# clid strip name
The following example strips the calling party number when PI is set to restrict clid strip from the CLID information and prevents the calling party number from being presented:
Router(config-dial-peer)# clid strip pi-restrict
The following example strips calling party name and number when the PI is set to the restrict all clid strip from the CLID information and prevents the calling party name and number from being presented:
Router(config-dial-peer)# clid strip pi-restrict all
The following example substitutes the calling party number into the display name:
Router(config-dial-peer)# clid substitute name
The following example allows you to set the screening indicator to reflect that the number was provided by the network:
Router(config-dial-peer)# clid network-provided
Related Commands
clid (voice service voip)To pass the network-provided ISDN numbers in an ISDN calling party information element screening indicator field, and remove the calling party name and number from the calling-line identifier in voice service voip configuration mode, or allow a presentation of the calling number by substituting for the missing Display Name field in the Remote-Party-ID and From headers use the clid command in voice service voip configuration mode. To return to the default configuration, use the no form of this command.
clid
{network-provided | strip pi-restrict all | substitute name}
no
clid
{network-provided | strip pi-restrict all | substitute name}
Syntax Description
Command DefaultThe clid command passes along user-provided ISDN numbers in an ISDN calling party information element screening indicator field. Usage GuidelinesUse the clidnetwork-provided keyword to pass along network-provided ISDN numbers in an ISDN calling party information element screening indicator field. Use the clidstrippi-restrictall keyword to remove the Calling Party Name and Calling Party Number from the CLID. Use the clidsubstitutename keyword to allow a presentation of the Display Name field in the Remote-Party-ID and From headers. The Calling Number is substituted for the Display Name field. ExamplesThe following example passes along network-provided ISDN numbers in an ISDN calling party information element screening indicator field:
Router(conf-voi-serv)# clid network-provided
The following example passes along user-provided ISDN numbers in an ISDN calling party information element screening indicator field:
Router(conf-voi-serv)# no clid network-provided
The following example removes the calling party name and number from the calling-line identifier (CLID):
Router(conf-voi-serv)# clid strip pi-restrict all
The following example does not remove the calling party name and number from the CLID:
Router(conf-voi-serv)# no clid strip pi-restrict all
The following example allows the presentation of the calling number to be substituted for the missing Display Name field in the Remote-Party-ID and From headers:
Router(conf-voi-serv)# clid substitute name
The following example disallows the presentation of the calling number to be substituted for the missing Display Name field in the Remote-Party-ID and From headers:
Router(conf-voi-serv)# no clid substitute name
clid stripTo remove the calling-party number from calling-line-ID (CLID) information and to prevent the calling-party number from being presented to the called party, use the clidstrip command in dial-peer configuration mode. To remove the restriction, use the no form of this command. Usage GuidelinesIf the clidstrip command is issued, the calling-party number is null in the information element, and the presentation indicator is set to "n" to prevent the presentation of the number to the called party. If you want to remove both the number and the name, you must issue the command twice, once with the name keyword. ExamplesThe following example removes the calling-party number from the CLID information and prevents the calling-party number from being presented:
Router(config-dial-peer)# clid strip
The following example removes both the calling-party number and the calling-party name from the caller-ID display: Router(config-dial-peer)# clid strip Router(config-dial-peer)# clid strip name Related Commands
clid strip reasonTo remove the calling-line ID (CLID) reason code and to prevent it from being displayed on the phone, use the clidstripreason command in dial peer voice configuration mode. To disable the configuration, use the no form of this command. Usage GuidelinesWhen the caller-idenablecommand is enabled on the gateway so that the gateway forwards information depending on the preference of the caller, client layer interface port (CLIP), or calling line identification restriction (CLIR), an "unavailable" message is displayed on the terminating phone. An "unavailable" message is a standard message that indicates the reason for the absence of calling party name. You can use the clidstripreason command to remove the message and have only the call parameters forwarded. ExamplesThe following example shows how to remove the CLID reason code: Router# configure terminal Router(config)# dial-peer voice 88 voip Router(config-dial-peer)# clid strip reason Related Commands
clock-rate (codec-profile)To set the clock rate, in Hz, for the codec, use the clock-rate command in codec-profile configuration mode. To return to the default value, use the no form of this command. clock-selectTo establish the sources and priorities of the requisite clocking signals for the OC-3/STM-1 ATM Circuit Emulation Service network module, use the clock-select command in CES configuration mode. Usage GuidelinesThis command is used on Cisco 3600 series routers that have OC-3/STM-1 ATM CES network modules. To support synchronous or synchronous residual time stamp (SRTS) clocking modes, you must specify a primary reference source to synchronize the flow of constant bit rate (CBR) data from its source to its destination. You can specify up to four clock priorities. The highest priority active interface in the router supplies primary reference source to all other interfaces that require network clock synchronization services. The fifth priority is the local oscillator on the network module. Use the showcesclock-selectcommand to display the currently configured clock priorities on the router. cm-current-enhanceTo improve immunity to extreme levels of longitudinal noise present in wiring that includes long cable lengths, use the cm-current-enhance command in Voice-port configuration mode. To return to the default configuration, use the no form of this command. Usage GuidelinesThis command should not be used under normal conditions. It should be used only to improve immunity to noise in cases of extreme levels of longitudinal noise on the wiring. The command is available on the following platforms, in the modes indicated:
Mode of action: When the cm-current-enhance mode is activated, REG 73 of the Silab chip (Si324x) is programmed to 1 to enhance the immunity to common-mode current noise. Change of signaling type: The command is effective for the current signaling type value. The command state is not saved and applied after a change of signaling type. codec (dial peer)To specify the voice coder rate of speech for a dial peer, use the codec command in dial peer configuration mode. To reset command settings to the default value, use the no form of this command. Cisco 1750 and Cisco 1751 Modular Access Routers, Cisco AS5300 and AS5800 Universal Access Servers, and Cisco MC3810 Multiservice Concentrators
codec
codec
[bytes payload-size]
[fixed-bytes]
[mode {independent | adaptive}]
[bit-rate value]
[framesize {30 | 60} [fixed] ]
no
codec
codec
[bytes payload-size]
[fixed-bytes]
[mode {independent | adaptive}]
[bit-rate value]
[framesize {30 | 60} [fixed] ]
Cisco 2600, 3600, 7200, and 7500 Series Routers
codec
{codec [bytes payload-size] | transparent}
[fixed-bytes]
[mode {independent | adaptive}]
[bit-rate value]
[framesize {30 | 60} [fixed] ]
no codec
{codec [bytes payload-size] | transparent}
[fixed-bytes]
[mode {independent | adaptive}]
[bit-rate value]
[framesize {30 | 60} [fixed] ]
Syntax DescriptionCommand Defaultg729r8, 30-byte payload for Voice over Frame Relay (VoFR) and Voice over ATM (VoATM). g729r8, 20-byte payload for Voice over IP (VoIP). See the second table below for valid entries and default values for codecs. Command History
Usage GuidelinesUse thiscommand to define a specific voice coder rate of speech and payload size for a VoIP or VoFR dial peer. This command is also used for VoATM.
A specific codec type can be configured on the dial peer as long as the codec is supported by the setting used with the codeccomplexity voice-card configuration command. The codeccomplexity command is voice-card specific and platform specific. The codeccomplexity voice-card configuration command is set to either high or medium. If the codeccomplexity command is set to high, the following keywords are available: g711alaw, g711ulaw,g722-64, g723ar53, g723ar63, g723r53, g723r63, g726r16, g726r24, g726r32, g728, g729r8, and g729br8. If the codeccomplexity command is set to medium, the following keywords are available: g711alaw, g711ulaw, g726r16, g726r24, g726r32, g729r8, and g729br8. The codec dial peer configuration command is particularly useful when you must change to a small-bandwidth codec. Large-bandwidth codecs, such as G.711, do not fit in a small-bandwidth link. However, the g711alaw and g711ulaw codecs provide higher quality voice transmission than other codecs. The g729r8 codec provides near-toll quality with considerable bandwidth savings. The transparent keyword is available with H.323 to H.323 call connections beginning in Cisco IOS Release 12.2(13)T3. Support for the keyword in H.32 to SIP call connections begins in Cisco IOS Release 12.4(11)XJ2. If codec values for the dial peers of a connection do not match, the call fails. You can change the payload of each VoIP frame by using the byteskeyword; you can change the payload of each VoFR frame by using the bytes keyword with the payload-size argument. However, increasing the payload size can add processing delay for each voice packet. The table below describes the voice payload options and default values for the codecs and packet voice protocols.
For toll quality, use the g711alaw or g711ulawkeyword. These values provide high-quality voice transmission but use a significant amount of bandwidth. For nearly toll quality (and a significant savings in bandwidth), use the g729r8keyword.
ExamplesThe following example shows how to configure a voice coder rate that provides toll quality voice with a payload of 120 bytes per voice frame on a router that acts as a terminating node. The sample configuration begins in global configuration mode and is for VoFR dial peer 200. dial-peer voice 200 vofr codec g711ulaw bytes 240 The following example shows how to configure a voice coder rate for VoIP dial peer 10 that provides toll quality but uses a relatively high amount of bandwidth: dial-peer voice 10 voip codec g711alaw The following example shows how to configure the transparent codec used by the Cisco Unified Border Element: dial-peer voice 1 voip incoming called-number .T destination-pattern .T session target ras codec transparent codec (dsp)To specify call density and codec complexity based on a particular codec standard, use the codec command in DSP interface DSP farm configuration mode. To reset the card type to the default, use the no form of the command. Usage GuidelinesThis command is supported on only the Cisco 7200 series and Cisco 7500 series routers. Codec complexity refers to the amount of processing required to perform compression. Codec complexity affects the number of calls, referred to as call density, that can take place on the DSPfarm interfaces. The greater the codec complexity, the fewer the calls that are handled. For example, G.711 requires less DSP processing than G.728, so as long as the bandwidth is available, more calls can be handled simultaneously by using the G.711 standard than by using G.728. The DSPinterface dspfarm codec complexity setting affects the options available for the codecdialpeerconfiguration command. To change codec complexity, you must first remove any configured-channel associated signaling (CAS) or DS0 groups and then reinstate them after the change.
codec (DSP farm profile)To specify the codecs that are supported by a digital signal processor (DSP) farm profile, use the codec command in DSP farm profile configuration mode. To remove the codec, use the no form of this command.
codec
{codec-type [resolution] | [frame-rate framerate] | [bitrate bitrate] | [rfc-2190] | pass-through}
no
codec
{codec-type [resolution] | [frame-rate framerate] | [bitrate bitrate] | [rfc-2190] | pass-through}
Syntax Description
TranscodingThe following transcoding default apply when you are configuring audio profiles only. When you configure video transcoding, you must specify the audio codecs. Command History
Usage GuidelinesOnly one codec is supported for each MTP profile. To support multiple codecs, you must define a separate MTP profile for each codec. For homogeneous video profiles, only one video format is supported For heterogeneous and heterogeneous guaranteed-audio video profiles, multiple video formats and audio codecs are supported. To change the configured codec in the profile, you must first enter a nomaximumsessioncommand. The table below shows the relationship between DSP farm functions and codecs.
Hardware MTPs support only G.711 a-law and G.711 mu-law. If you configure a profile as a hardware MTP and you want to change the codec to other than G.711, you must first remove the hardware MTP by using thenomaximumsessionshardware command. The pass-through keyword is supported for transcoding and MTP profiles only; the keyword is not supported for conferencing profiles. To support the Resource Reservation Protocol (RSVP) agent on a Skinny Client Control Protocol (SCCP) device, you must use the codecpass-through command. In the pass-through mode, the SCCP device processes the media stream by using a pure software MTP, regardless of the nature of the stream, which enables video and data streams to be processed in addition to audio streams. When the pass-through mode is set in a transcoding profile, no transcoding is done for the session; the transcoding device performs a pure software MTP function. The pass-through mode can be used for secure Real-Time Transport Protocol (RTP) sessions. ExamplesThe following example shows how to set the call density and codec complexity to g729abr8: Router(config)# dspfarm profile 123 transcode Router(config-dspfarm-profile)# codec g729abr8 The following example shows how to set up a video conference with guaranteed-audio. Router(config)# dspfarm profile 99 conference video guaranteed-audio Router(config-dspfarm-profile)# codec h264 4cif Router(config-dspfarm-profile)# codec h264 cif Router(config-dspfarm-profile)# maximum conference-participants 8 Related Commands
codec (voice-card)To specify call density and codec complexity according to the codec standard that is being used or to increase processing frequency for the G.711 codec, use the codeccommand in voice-card configuration mode. To reset the flex complexity default or to disable configured values, use the no form of this command.
codec
{complexity {flex [reservation-fixed {high | medium}] | high | medium | secure} | sub-sample}
no
codec
complexity
Syntax Description
Command DefaultThe default type of codec complexity is flex. The default value for the G.711 codec is 10 milliseconds (ms). Command History
Usage GuidelinesCodec complexity refers to the amount of processing required to perform voice compression. Codec complexity affects the call density--the number of calls reconciled on the DSPs. With higher codec complexity, fewer calls can be handled. Select a higher codec complexity if that is required to support a particular codec or combination of codecs. Select a lower codec complexity to support the greatest number of voice channels, provided that the lower complexity is compatible with the particular codecs in use. For codec complexity to change, all of the DSP voice channels must be in the idle state. When you have specified the flexkeyword, you can connect (or configure in the case of DS0 groups and PRI groups) more voice channels to the module than the DSPs can accommodate. If all voice channels should go active simultaneously, the DSPs become oversubscribed, and calls that are unable to allocate a DSP resource fail to connect. The flex keyword allows the DSP to process up to 16 channels. In addition to continuing support for configuring a fixed number of channels per DSP, theflex keyword enables the DSP to handle a flexible number of channels. The total number of supported channels varies from 6 to 16, depending on which codec is used for a call. Therefore, the channel density varies from 6 per DSP (high-complexity codec) to 16 per DSP (g.711 codec). The high keyword selects a higher codec complexity if that is required to support a particular codec or combination of codecs. When you use the codeccomplexityhigh command to change codec complexity, the system prompts you to remove all existing DS0 or PRI groups using the specified voice card, then all DSPs are reset, loaded with the specified firmware image, and released. The medium keyword selects a lower codec complexity to support the greatest number of voice channels, provided that the lower complexity is compatible with the particular codecs in use. The secure keyword restricts the number of TI-549 DSP channels to 2, which is the lower codec complexity required to support Secure Real-Time Transport Protocol (SRTP) package capability on the NM-HDV and enable media authentication and encryption. If the secure command is not configured then the gateway will not advertise secure capability to Cisco CallManager, resulting in nonsecure calls. You do not need to use any command to specify secure codec complexity for TI-5510 DSPs, which support SRTP capability in all modes. Use the mgcppackage-capabilitysrtp-packagecommand to enable MGCP gateway capability to process SRTP packages. Use the showvoicedsp command to display codec complexity status. Voice quality issues may occur when there are more than 15 G.711 channels on one 5510 DSP. To resolve the voice-quality issue, change the processing period (or segment size) of the G.711 codec from 5 ms to 10 ms. (The segment size of most voice codecs is 10 ms.) However, a voice call with 10-ms segment size has longer end-to-end delay (+ 5ms to 10 ms) than a call with 5-ms segment size. Beginning in Cisco IOS Release 12.4(22)T1, the sub-sample keyword is added for applications that have strict requirements for round-trip delay times for VoIP. You can now accept the default G.711 (10 ms with lower MIPS) or enter the codecsub-sample command to select 5-ms G.711 (lower delay with higher MIPS). The sub-sample keyword is enabled only for the 5510 DSP. The codecsub-sample command enables 5-ms processing for the G.711 codec inside the DSP to reduce the delay. However, this reduces the channel density of G.711 channels from 16 to 14. There is no difference in secure channel density when this mode is enabled. ExamplesThe following example sets the codec complexity to high on voice card 1 installed on a router, and configures local calls to bypass the DSP: voice-card 1 codec complexity high local-bypass The following example sets the codec complexity to secure on voice card 1 installed on the NM-HDV, and configures it to support SRTP package processing, media authentication, and encryption: voice-card 1 codec complexity secure The following example shows how to enable 5-ms processing for the G.711 codec inside the 5510 DSP: voice-card 1 codec sub-sample codec aal2-profileTo set the codec profile for a digital signal processor (DSP) on a per-call basis, use the codecaal2-profile command in dial peer configuration mode. To restore the default codec profile, use the no form of this command. Syntax Description
Command History
Usage GuidelinesUse this command to configure the DSP to operate with a specified profile type and codecs. You must enter the sessionprotocolaal2-trunk command before configuring the codec ATM adaptation Layer 2 (AAL2) profile. This command is used instead of the codec(dialpeer) command for AAL2 trunk applications. ExamplesThe following example sets the codec AAL2 profile type to ITU-T and configures a profile number of 7, enabling codec G.729ar8: dial-peer voice 100 voatm session protocol aal2-trunk codec aal2-profile itut 7 g729ar8 The following example sets the codec AAL2 profile type to custom and configures a profile number of 100, enabling codec G.726r32: dial-peer voice 200 voatm session protocol aal2-trunk codec aal2-profile custom 100 g726r32 codec gsmamr-nbTo specify the Global System for Mobile Adaptive Multi-Rate Narrow Band (GSMAMR-NB) codec for a dial peer, use the codecgsmamr-nbcommand in dial peer voice configuration mode. To disable the GSMAMR-NB codec, use the no form of this command.
codec
gsmamr-nb
[packetization-period 20]
[encap rfc3267]
[frame-format {bandwidth-efficient | octet-aligned [crc | no-crc]}]
[modes modes-value]
no
codec
gsmamr-nb
Syntax Description
Command DefaultPacketization period is 20 ms. Encapsulation is rfc3267. Frame format is octet-aligned. CRC is no-crc. Modes value is 0-7. Usage GuidelinesThe codecgsmamr-nb command configures the GSMAMR-NB codec and its parameters on the Cisco AS5350XM and Cisco AS5400XM platforms. codec ilbcTo specify the voice coder rate of speech for a dial peer using the internet Low Bandwidth Codec (iLBC), use the codecilbccommand in dial-peer configuration mode. To reset the default value, use the no form of this command.
codec
ilbc
[mode frame_size [bytes payload_size]]
no
codec
ilbc
[mode frame_size [bytes payload_size]]
Syntax Description
Usage GuidelinesUse thiscommand to define a specific voice coder rate of speech and payload size for a VoIP dial peer using an iLBC codec. If codec values for the dial peers of a connection do not match, the call fails. You can change the payload of each VoIP frame by using the byteskeyword. However, increasing the payload size can add processing delay for each voice packet. codec preferenceTo specify a list of preferred codecs to use on a dial peer, use the codecpreference command in voice-class configuration mode. To disable this functionality, use the no form of this command.
codec
preference
value
codec-type
[mode {independent | adaptive}]
[frame-size {20 | 30 | 60 | fixed}]
[bit rate value]
[bytes payload-size]
[packetization-period 20]
[encap rfc3267]
[frame-format {bandwidth-efficient | octet-aligned [crc | no-crc]}]
[modes modes-value]
no
codec
preference
value
codec-type
Syntax Description
Command DefaultIf this command is not entered, no specific types of codecs are identified with preference. If you enter the gsmamr-nb keyword, the default values are as follows: Packetization period is 20 ms. Encap is rfc3267. Frame format is octet-aligned. CRC is no-crc. Modes value is 0-7. If you enter the isac keyword, the default values are as follows: Mode is independent. Target bit-rate is 32000bps. Framesize is 30ms. Command History
Usage GuidelinesThe routers at opposite ends of the WAN may have to negotiate the codec selection for the network dial peers. Thecodecpreference command specifies the order of preference for selecting a negotiated codec for the connection. The table below describes the voice payload options and default values for the codecs and packet voice protocols.
ExamplesThe following example show how to set the codec preference to the GSMAMR-NB codec and specify parameters:
Router(config-voice-class)# codec preference 1 gsmamr-nb packetization-period 20 encap rfc3267 frame-format octet-aligned crc
The following example shows how to create codec preference list 99 and applies it to dial peer 1919: voice class codec 99 codec preference 1 g711alaw codec preference 2 g711ulaw bytes 80 codec preference 3 g723ar53 codec preference 4 g723ar63 bytes 144 codec preference 5 g723r53 codec preference 6 g723r63 bytes 120 codec preference 7 g726r16 codec preference 8 g726r24 codec preference 9 g726r32 bytes 80 codec preference 10 g729br8 codec preference 11 g729r8 bytes 50 end dial-peer voice 1919 voip voice-class codec 99 The following example shows how to configure the transparent codec used by the Cisco Unified Border Element: voice class codec 99 codec preference 1 transparent
The following example shows how to configure the iLBC codec used by the Cisco Unified Border Element: voice class codec 99 codec preference 1 ilbc mode 30 bytes 200 Related Commands
codec profileTo define video capabilities needed for video endpoints, use the codecprofile command in telephony-service configuration mode. To disable the codec profile, use the no form of this command. Usage GuidelinesFor the Cisco Unified Customer Voice Portal solution, only h263 and h263+ are supported profile options. ExamplesThe following example shows the codec tagged 116 assigned to the H263 profile. codec profile 116 H263 clockrate 90000 fmtp "fmtp:120 SQCIF=1;QCIF=1;CIF=1;CIF4=2;MAXBR=3840;I=1" The codec profile can then be added to a voice class codec list, or the VoIP dial peer: voice class codec 998 codec preference 1 g711ulaw video codec h263 profile 116 comfort-noiseTo generate background noise to fill silent gaps during calls if voice activity detection (VAD) is activated, use the comfort-noise command in voice-port configuration mode. To provide silence when the remote party is not speaking and VAD is enabled at the remote end of the connection, use the no form of this command. Usage GuidelinesUse the comfort-noisecommand to generate background noise to fill silent gaps during calls if VAD is activated. If the comfort-noise command is not enabled, and VAD is enabled at the remote end of the connection, the user hears dead silence when the remote party is not speaking. The configuration of the comfort-noise command affects only the silence generated at the local interface; it does not affect the use of VAD on either end of the connection or the silence generated at the remote end of the connection. compand-typeTo specify the companding standard used to convert between analog and digital signals in pulse code modulation (PCM) systems, use the compand-type command in voice-port configuration mode. To disable the compand type, use the no form of this command. Usage GuidelinesThe Cisco 2660 and the Cisco 3640 routers do not require configuration of the compand-typea-law command. However, if you request a list of commands, the compand-typea-law command displays.
conferenceTo define a Feature Access Code (FAC) to initiate a three-party conference in feature mode on analog phones connected to FXS ports, use the conference command in STC application feature-mode call-control configuration mode. To return the code to its default, use the no form of this command. Usage GuidelinesThis command changes the value of the FAC for the Call Conference feature from the default (#3) to the specified value. If you attempt to configure this command with a value that is already configured for another FAC in feature mode, you receive a message. This message will not prevent you from configuring the feature code. If you configure a duplicate FAC, the system implements the first feature it matches in the order of precedence as determined by the value for each FAC (#1 to #5). If you attempt to configure this command with a value that precludes or is precluded by another FAC in feature mode, you receive a message. If you configure a FAC to a value that precludes or is precluded by another FAC in feature mode, the system always executes the call feature with the shortest code and ignores the longer code. For example, 1 will always preclude 12 and 123. These messages will not prevent you from configuring the feature code. You must configure a new value for the precluded code in order to enable phone user access to that feature. ExamplesThe following example shows how to change the value of the feature code for Call Conference from the default (#3). With this configuration, a phone user presses hook flash to get the first dial tone, then dials an extension number to connect to a second call. When the second call is established, the user presses hook flash to get the feature tone and then dials 33 to initiate a three-party conference. Router(config)# stcapp call-control mode feature Router(config-stcapp-fmcode)# conference 33 Router(config-stcapp-fmcode)# exit Related Commands
conference-join custom-cptoneTo associate a custom call-progress tone to indicate joining a conference with a DSP farm profile, use the conference-joincustom-cptone command in DSP farm profile configuration mode. To remove the custom call-progress tone association and disable the tone for the conference profile, use the no form of this command. Command DefaultNo custom call-progress tone to indicate joining a conference is associated with the DSP farm profile. Usage GuidelinesTo have a tone played when a party joins a conference, define the join tone, then associate it with the DSP farm profile for that conference.
ExamplesThe following example defines a custom call-progress tone to indicate joining a conference and associates that join tone to a DSP farm profile defined for conferencing. Note that the custom call-progress tone names in the voiceclasscustom-cptone and conference-joincustom-cptone commands must be the same. Router(config)# voice class custom-cptone jointone Router(cfg-cptone)# dualtone conference Router(cfg-cp-dualtone)# frequency 500 500 Router(cfg-cp-dualtone)# cadence 100 100 100 100 100 ! Router(config)# dspfarm profile 1 conference Router(config-dspfarm-profile)# conference-join custom-cptone jointone Related Commands
conference-leave custom-cptoneTo associate a custom call-progress tone to indicate leaving a conference with a DSP farm profile, use the conference-leavecustom-cptone command in DSP farm profile configuration mode. To remove the custom call-progress tone association and disable the tone for the conference profile, use the no form of this command. Command DefaultNo custom call-progress tone to indicate leaving a conference is is associated with the DSP farm profile. Usage GuidelinesFor a tone to be played when a party leaves a conference, define the leave tone, then associate it with the DSP farm profile for that conference. Use the voiceclasscustom-cptone command to create a voice class for defining custom call-progress tones to indicate leaving a conference. Use the cadence and frequency commands to define the characteristics of the leave tone. Use the conference-joincustom-cptone command to associate the leave tone to the DSP farm profile for that conference. Use the showdspfarmprofilecommand to display the DSP farm profile. ExamplesThe following example defines a custom call-progress tone to indicate leaving a conference and associates that leave tone to a DSP farm profile defined for conferencing. Note that the custom call-progress tone names in the voiceclasscustom-cptone and conference-joincustom-cptone commands must be the same. Router(config)# voice class custom-cptone leavetone Router(cfg-cptone)# dualtone conference Router(cfg-cp-dualtone)# frequency 500 500 Router(cfg-cp-dualtone)# cadence 100 100 100 100 100 ! Router(config)# dspfarm profile 1 conference Router(config-dspfarm-profile)# conference-join custom-cptone leavetone Related Commands
conditionTo manipulate the signaling format bit-pattern for all voice signaling types, use the condition command in voice-port configuration mode. To turn off conditioning on the voice port, use the no form of this command.
condition
{tx-a-bit | tx-b-bit | tx-c-bit | tx-d-bit}
{rx-a-bit | rx-b-bit | rx-c-bit | rx-d-bit}
{on | off | invert}
no
condition
{tx-a-bit | tx-b-bit | tx-c-bit | tx-d-bit}
{rx-a-bit | rx-b-bit | rx-c-bit | rx-d-bit}
{on | off | invert}
Command DefaultThe signaling format is not manipulated (for all sent or received A, B, C, and D bits). Usage GuidelinesUse the condition command to manipulate the sent or received bit patterns to match expected patterns on a connected device. Be careful not to destroy the information content of the bit pattern. For example, forcing the a-bit on or off prevents Foreign Exchange Office (FXO) interfaces from being able to generate both an on-hook and off-hook state. The condition command is applicable to digital voice ports only. ExamplesThe following example manipulates the signaling format bit pattern on digital voice port 0:5: voice-port 0:5 condition tx-a-bit invert condition rx-a-bit invert The following example manipulates the signaling format bit pattern on voice port 1/0:0: voice-port 1/0:0 condition tx-a-bit invert condition rx-a-bit invert connect (channel bank)To define connections between T1 or E1 controller ports for the channel bank feature, use the connectcommand in global configuration mode. To restore default values, use the no form of this command.
connect
connection-id
voice-port
voice-port-number
{t1 | e1}
controller-number
ds0-group-number
no
connect
connection-id
voice-port
voice-port-number
{t1 | e1}
controller-number
ds0-group-number
Syntax Description
Usage GuidelinesThe connect command creates a named connection between two DS0 groups associated with voice ports on T1 or E1 interfaces where the groups have been defined by the ds0-group command. ExamplesThe following example shows how to configure a channel bank connection for FXS loop-start signaling: Router(config)# controller t1 1/0 Router(config-controller)# ds0-group 1 timeslot 0 type fxo-loop-start Router(config-controller)# exit Router(config)# voice-port 1/1/0 Router(config-voiceport)# signal-type fxs-loop-start Router(config-voiceport)# exit Router(config)# connect connection1 voice-port 1/1/0 t1 1/0 0 Related Commands
connect (drop-and-insert)To define connections among T1 or E1 controller ports for drop-and-insert (also called TDM cross-connect), use the connect command inglobal configuration mode. To restore default values, use the no form of this command.
connect
connection-id
{t1 | e1}
slotport-1
tdm-group-no-1
{t1 | e1}
slotport-2
tdm-group-no-2
no
connect
connection-id
{t1 | e1}
slotport-1
tdm-group-no-1
{t1 | e1}
slotport-2
tdm-group-no-2
Syntax Description
Command History
Usage GuidelinesThe connect command creates a named connection between two TDM groups associated with drop-and-insert ports on T1 or E1 interfaces where you have already defined the groups by using the tdm-group command. Once TDM groups are created on two different physical ports, use the connect command to start the passage of data between the ports. If a crosspoint switch is provided in the AIM slot, the connections can extend between ports on different cards. Otherwise, the connection is restricted to ports on the same VWIC. The VWIC can make a connection only if the number of time slots at the source and destination are the same. For the connection to be error-free, the two ports must be driven by the same clock source; otherwise, slips occur. ExamplesThe following example shows a fractional T1 terminated on port 0 using time slots 1 through 8, a fractional T1 is terminated on port 1 using time slots 2 through 12, and time slots 13 through 20 from port 0 are connected to time slots 14 through 21 on port 1 by using the connect command: controller t1 0/0 channel-group 1 timeslots 1-8 tdm-group 1 timeslots 13-20 exit controller t1 0/1 channel-group 1 timeslots 2-12 tdm-group 2 timeslot 14-21 exit connect exampleconnection t1 0/0 1 t1 0/1 2 connect atmTo define connections between T1 or E1 controller ports and the ATM interface, enter the connectatmcommand in global configuration mode. Use the no form of this command to restore the default values.
connect connection-id atm slot/port-1{virtual-circuit-namevpi/vci{atm | T1 | E1}}slot/port-2 TDM-group-number{virtual-circuit-name | vpi/vci}
connect connection-id atm slot/port-1{virtual-circuit-namevpi/vci{atm | T1 | E1}}slot/port-2 TDM-group-number{virtual-circuit-name | vpi/vci}
Syntax Description
Usage GuidelinesThis command is used on Cisco 2600, Cisco 3600, and Cisco 3700 series routers to provide connections between T1/E1 and ATM interfaces. This command is used after all interfaces are configured. After TDM groups are created on two different physical ports, you can use the connectatmcommand to start the passage of data between the ports. If a crosspoint switch is provided in the advanced integration module (AIM) slot, the connections can extend between ports on different cards. Otherwise, the connection is restricted to ports on the same VWIC card. The VWIC can make a connection only if the number of time slots at the source and destination are the same. For the connection to be error free, the two ports must be driven by the same clock source; otherwise, slips occur. connect intervalTo specify the amount of time that a given digital signal processor (DSP) farm profile waits before attempting to connect to a Cisco Unified CallManager when the current Cisco Unified CallManager fails to connect, use the connectintervalcommand in SCCP Cisco Unified CallManager configuration mode. To reset to the default value, use the no form of this command. Usage GuidelinesThe optimum setting for this command depends on the platform and your individual network characteristics. Adjust the connect interval value to meet your needs. ExamplesThe following example specifies that the profile attempts to connect to another Cisco Unified CallManager after 1200 seconds (20 minutes) when the current Cisco Unified CallManager connection fails:
Router(config-sccp-ccm)# connect interval 1200
Related Commands
connect retriesTo specify the number of times that a digital signal processor (DSP) farm attempts to connect to a Cisco Unified CallManager when the current Cisco Unified CallManager connections fails, use the connectretriescommand in SCCP Cisco Unified CallManager configuration mode. To reset this number to the default value, use the no form of this command. Usage GuidelinesThe value of this command specifies the number of times that the given DSP farm attempts to connect to the higher-priority Cisco Unified CallManager before it gives up and attempts to connect to the next Cisco Unified CallManager. The optimum setting for this command depends on the platform and your individual network characteristics. Adjust the connect retries value to meet your needs. ExamplesThe following example allows a DSP farm to make five attempts to connect to the Cisco Unified CallManager before giving up and attempting to connect to the next Cisco Unified CallManager specified in the group:
Router(config-sccp-ccm)# connect retries 5
Related Commands
connectionTo specify a connection mode for a voice port, use the connection command in voice-port configuration mode. To disable the selected connection mode, use the no form of this command.
{connection {plar | tie-line | plar opx [cut-through-wait | immediate]} phone-number | trunk phone-number [answer-mode] }
no {connection {plar | tie-line | plar opx [cut-through-wait | immediate]} phone-number | trunk phone-number [answer-mode] }
Syntax Description
Command DefaultNo connection mode is specified, and the standard session application outputs a dial tone when the interface goes off-hook until enough digits are collected to match a dial peer and complete the call. Command History
Usage GuidelinesUse the connection command to specify a connection mode for a specific interface. For example, use the connectionplar command to specify a PLAR interface. The string you configure for this command is used as the called number for all incoming calls over this connection. The destination peer is determined by the called number. The connectionplaropximmediate option enables FXO ports to set up calls with no ring discrepancy for Caller ID between the caller and the called party. To implement the FXO Delayed Caller ID Delivery feature, you must have a configured network with a Cisco 2800 or Cisco 3800 series integrated services router running Cisco IOS Release 12.4(11)XW. The integrated services router must have at least one voice interface card. Cisco CallManager Release 4.2.3 SR1 or later releases must be installed on the network to support this feature. The two figures below show the network topology and call flow for the FXO Delayed Caller ID feature. The caller is in the PSTN, and the call arrives via an FXO port at the gateway. In the figure below, the gateway is connected via H.323 to Cisco CallManager. Cisco CallManager extends the call to the called party which is a SCCP-based IP phone (Cisco 7941). In the figure below, the gateway is on the same router as the figure above, and Survivable Remote Site Telephony (SRST) is active. SRST extends the call to the called party, which is a Skinny Client Control Protocol (SCCP)-based IP phone (Cisco 7941). Use the connectiontrunk command to specify a permanent tie-line connection to a PBX. VoIP simulates a trunk connection by creating virtual trunk tie lines between PBXs connected to Cisco devices on each side of a VoIP connection (see Virtual Trunk Connection Figure). In this example, two PBXs are connected using a virtual trunk. PBX-A is connected to Router A via an E&M voice port; PBX-B is connected to Router B via an E&M voice port. The Cisco routers spoof the connected PBXs into believing that a permanent trunk tie line exists between them. When configuring virtual trunk connections in VoIP, the following restrictions apply:
To configure one of the devices in the trunk connection to act as slave and only receive calls, use the answer-mode option with the connectiontrunk command when configuring that device.
VoIP establishes the trunk connection immediately after configuration. Both ports on either end of the connection are dedicated until you disable trunking for that connection. If for some reason the link between the two switching systems goes down, the virtual trunk reestablishes itself after the link comes back up. Use the connectiontie-line command when the dial plan requires you to add digits in front of any digits dialed by the PBX, and the combined set of digits is used to route the call onto the network. The operation is similar to the connectionplar command operation, but in this case, the tie-line port waits to collect thedigits from the PBX. Tie-line digits are automatically stripped by a terminating port. ExamplesThe following example shows PLAR as the connection mode with a destination telephone number of 555-0100: voice-port 1/0/0 connection trunk 5550100 The following example shows the tie-line as the connection mode with a destination telephone number of 555-0100: voice-port 1/1 connection tie-line 5550100 The following example shows a PLAR off-premises extension connection with a destination telephone number of 555-0100: voice-port 1/0/0 connection plar-opx 5550100 The following example shows a trunk connection configuration that is established only when the trunk receives an incoming call: voice-port 1/0/0 connection trunk 5550100 answer-mode The following example shows a PLAR off-premises extension connection with a destination telephone number of 0199. The router waits for the off-hook signal before cutting through the audio path: voice-port 2/0/0 connection plar opx 0199 cut-through-wait The following examples show configuration of the routers on both sides of a VoIP connection (as illustrated in the figure above) to support trunk connections. Router Avoice-port 1/0/0 connection trunk +15105550190 dial-peer voice 10 pots destination-pattern +13085550181 port 1/0/0 dial-peer voice 100 voip session-target ipv4:172.20.10.10 destination-pattern +15105550190 Router Bvoice-port 1/0/0 connection trunk +13085550180 dial-peer voice 20 pots destination-pattern +15105550191 port 1/0/0 dial-peer voice 200 voip session-target ipv4:172.19.10.10 destination-pattern +13085550180 Related Commands
connection-timeoutTo configure the time in seconds for which a connection is maintained after completion of a communication exchange, use the connection-timeout command in settlement configuration mode. To return to the default value, use the no form of this command. Usage GuidelinesThe router maintains the connection for the configured period in anticipation of future communication exchanges to the same server. ExamplesThe following example shows a connection configured to be maintained for 3600 seconds after completion of a communications exchange: settlement 0 connection-timeout 3600 Related Commands
copy flash vfcTo copy a new version of VCWare from the Cisco AS5300 universal access server motherboard to voice feature card (VFC) flash memory, use the copyflashvfccommand inprivileged EXEC mode. Usage GuidelinesUse the copyflashvfccommand to use the standard copy user interface in order to copy a new version of VCWare from the Cisco AS5300 universal access server motherboard to VFC flash memory. The VFC is a plug-in feature card for the Cisco AS5300 universal access server and has its own Flash memory storage for embedded firmware. For more information about VFCs, refer to Voice-over-IP Card. Once the VCWare file has been copied, use the unbundlevfc command to uncompress and install VCWare. copy tftp vfcTo copy a new version of VCWare from a TFTP server to voice feature card (VFC) flash memory, use the copytftpvfccommand in privileged EXEC mode. Usage GuidelinesUse the copytftpvfccommand to copy a new version of VCWare from a TFTP server to VFC flash memory. The VFC is a plug-in feature card for the Cisco AS5300 universal access server and has its own flash storage for embedded firmware. For more information about VFCs, refer to Voice-over-IP Card. Once the VCWare file has been copied, use the unbundlevfc command to uncompress and install VCWare. corlist incomingTo specify the class of restrictions (COR) list to be used when a specified dial peer acts as the incoming dial peer, use the corlistincoming command in dial peer configuration mode. To clear the previously defined incoming COR list in preparation for redefining the incoming COR list, use the no form of this command. Usage GuidelinesThe dial-peercorlist and member commands define a set of capabilities (a COR list). These lists are used in dial peers to indicate the capability set that a dial peer has when it is used as an incoming dial peer (the corlistincoming command) or to indicate the capability set that is required for an incoming dial peer to make an outgoing call through the dial peer (the corlistoutgoing command). For example, if dial peer 100 is the incoming dial peer and its incoming COR list name is list100, dial peer 200 has list200 as the outgoing COR list name. If list100 does not include all the members of list200 (that is, if list100 is not a superset of list200), it is not possible to have a call from dial peer 100 that uses dial peer 200 as the outgoing dial peer. ExamplesIn the following example, incoming calls from 526.... are blocked from being switched to outgoing calls to 1900.... because the COR list for the incoming dial peer (list2) is not a superset of the COR list for the outgoing dial peer (list1): dial-peer list list1 member 900call dial-peer list list2 member 800call member othercall dial-peer voice 526 pots answer-address 408555.... corlist incoming list2 direct-inward-dial dial-peer voice 900 pots destination pattern 1900....... direct-inward-dial trunkgroup 101 prefix 333 corlist outgoing list1 corlist outgoingTo specify the class of restrictions (COR) list to be used by outgoing dial peers, use the corlistoutgoingcommand in dial peer configuration mode. To clear the previously defined outgoing COR list in preparation for redefining the outgoing COR list, use the no form of this command. Usage GuidelinesIf the COR list for the incoming dial peer is not a superset of the COR list for the outgoing dial peer, calls from the incoming dial peer cannot use that outgoing dial peer. ExamplesIn the following example, incoming calls from 526.... are blocked from being switched to outgoing calls to 1900.... because the COR list for the incoming dial peer (list2) is not a superset of the COR list for the outgoing dial peer (list1): dial-peer list list1 member 900call dial-peer list list2 member 800call member othercall dial-peer voice 526 pots answer-address 408555.... corlist incoming list2 direct-inward-dial dial-peer voice 900 pots destination pattern 1900....... direct-inward-dial trunk group 101 prefix 333 corlist outgoing list1 cptoneTo specify a regional analog voice-interface-related tone, ring, and cadence setting for a voice port, use the cptone command in voice-port configuration mode. To disable the selected tone, use the no form of this command. Command DefaultThe default keyword is us for all supported gateways and interfaces in Cisco IOS Release 12.0(4)T and later releases. Command History
Usage GuidelinesThis command defines the detection of call-progress tones generated at the local interface. It does not affect any information passed to the remote end of a connection, and it does not define the detection of tones generated at the remote end of a connection. Use the cptone command to specify a regional analog voice interface-related default tone, ring, and cadence setting for a specified voice port. If your device is configured to support E1 R2 signaling, the E1 R2 signaling type (whether ITU, ITU variant, or local variant as defined by the cas-customcommand) must match the appropriate pulse code modulation (PCM) encoding type as defined by the cptone command. For countries for which a cptone value has not yet been defined, you can try the following:
The table below lists valid entries for the locale argument.
1 Automatically configured the first time the XML file is downloaded to the gateway.
2 Automatically configured the first time the XML file is downloaded to the gateway.
cptone call-waiting repetition intervalTo set the call-waiting alert pattern on analog endpoints that are connected to Foreign Exchange Station (FXS) ports, use the cptonecall-waitingrepetitioninterval command in supplementary-service voice-port configuration mode. To return to the default behavior, use the no form of this command. Usage GuidelinesUse the cptonecall-waitingrepetitioninterval command to set the call-waiting alert pattern on analog endpoints that are connected to FXS ports on a Cisco IOS voice gateway, such as a Cisco Integrated Services Router (ISR) or Cisco VG224 Analog Phone Gateway. When configured, the ringtone periodically repeats with configured interval until either the user switches to the new call or the calling party hangs up. ExamplesThe following example shows how to set the call-waiting alert pattern on analog endpoints connected to port 2/0 on a Cisco VG224: Router(config)# stcapp supplementary-services Router(config-stcapp-suppl-serv)# port 2/0 Router(config-stcapp-suppl-serv-port)# cptone call-waiting repetition interval 20 Router(config-stcapp-suppl-serv-port)# end credential loadTo reload a credential file into flash memory, use the credentialload command in privileged EXEC mode. Usage GuidelinesThis command provides a shortcut to reload credential files that were defined with the authenticatecredential command. Up to five .csv files can be configured and loaded into the system. The contents of these five files are mutually exclusive, that is, the username/password pairs must be unique across all the files. For Cisco Unified CME, these username/password pairs cannot be the same ones defined for SCCP or SIP phones with the usernamecommand. Related Commands
credentials (SIP UA)To configure a Cisco IOS Session Initiation Protocol (SIP) time-division multiplexing (TDM) gateway, a Cisco Unified Border Element (Cisco UBE), or Cisco Unified Communications Manager Express (Cisco Unified CME) to send a SIP registration message when in the UP state, use the credentials command in SIP UA configuration mode. To disable SIP digest credentials, use the no form of this command.
credentials
{dhcp | number number username username}
password
[0 | 7]
password
realm
realm
no
credentials
{dhcp | number number username username}
password
[0 | 7]
password
realm
realm
Syntax Description
Command History
Usage GuidelinesThe following configuration rules are applicable when credentials are enabled:
The dhcp keyword in the command signifies that the primary number is obtained via DHCP and the Cisco IOS SIP TDM gateway, Cisco UBE, or Cisco Unified CME on which the command is enabled uses this number to register or unregister the received primary number. ExamplesThe following example shows how to configure SIP digest credentials without specifying the password encryption type: Router> enable Router# configure terminal Router(config)# sip-ua Router(config-sip-ua)# credentials dhcp password MyPassword realm example.com The following example shows how to configure SIP digest credentials using the encrypted format: Router> enable Router# configure terminal Router(config)# sip-ua Router(config-sip-ua)# credentials dhcp password 7 095FB01AA000401 realm example.com The following example shows how to disable SIP digest credentials where the encryption type was specified: Router> enable Router# configure terminal Router(config)# sip-ua Router(config-sip-ua)# no credentials dhcp password 7 095FB01AA000401 realm example.com The following example shows how to configure SIP digest credentials for two different realms without specifying the encryption type: Router> enable Router# configure terminal Router(config)# sip-ua Router(config-sip-ua)# credentials number 1111 username MyUser password MyPassword realm MyLocation1.example.com Router(config-sip-ua)# credentials number 1111 username MyUser password MyPassword realm MyLocation2.example.com Related Commands
1 Automatically configured the first time the XML file is downloaded to the gateway.
2 Automatically configured the first time the XML file is downloaded to the gateway.
© 2012 Cisco Systems, Inc. All rights reserved.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|