- A
- B
- cac master through call application stats
- call application voice through call denial
- call fallback through called-number (dial peer)
- caller-id (dial peer) through ccm-manager switchover-to-backup
- ccs connect (controller) through clear vsp statistics
- clid through credentials (sip-ua)
- default (auto-config application) through direct-inward-dial
- disable-early-media through dualtone
- E
- F
- G
- H
- icpif through irq global-request
- isdn bind-l3 through ixi transport http
- K
- L
- map q850-cause through mgcp package-capability
- mgcp persistent through mmoip aaa send-id secondary
- mode (ATM/T1/E1 controller) through mwi-server
- N
- O
- package through pattern
- periodic-report interval through proxy h323
- Q
- R
- sccp through service-type call-check
- session through sgcp tse payload
- show aal2 profile through show call filter match-list
- show call history fax through show debug condition
- show dial-peer through show gatekeeper zone prefix
- show gateway through show modem relay statistics
- show mrcp client session active through show sip dhcp
- show sip service through show trunk hdlc
- show vdev through show voice statistics memory-usage
- show voice trace through shutdown (voice-port)
- signal through srv version
- ss7 mtp2-variant through switchover method
- target carrier-id through timeout tsmax
- timeouts call-disconnect through timing clear-wait
- timing delay-duration through type (voice)
- U
- vad (dial peer) through voice-class sip encap clear-channel
- voice-class sip error-code-override through vxml version 2.0
- W
- Z
- name (dial peer cor custom)
- nat symmetric check-media-src
- nat symmetric role
- neighbor (annex g)
- neighbor (tgrep)
- network-clock base-rate
- network-clock-participate
- network-clock-select
- network-clock-switch
- non-linear
- notify (MGCP profile)
- notify redirect
- notify redirect (dial peer)
- notify telephone-event
- nsap
- null-called-number
- numbering-type
- num-exp
Cisco IOS Voice Commands:
N
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 command reference master index or search online to find these commands.
For detailed information on how to configure these applications and features, refer to the Cisco IOS Voice Configuration Guide.
name (dial peer cor custom)
To specify the name for a custom class of restrictions (COR), use the name command in dial peer COR custom configuration mode. To remove a specified COR, use the no form of this command.
name class-name
no name class-name
Syntax Description
class-name |
Name that describes the specific COR. |
Command Default
No default behavior or values.
Command Modes
Dial peer COR custom configuration
Command History
|
|
|
|---|---|
12.1(3)T |
This command was introduced. |
Usage Guidelines
The dial-peer cor custom and name commands define the names of capabilities on which to apply COR operation. Examples of names might include any of the following: call1900, call527, call9, or call 911. You must define the capabilities before you specify the COR rules.
You can define a maximum of 64 COR names.
Examples
The following example defines three COR names:
dial-peer cor custom
name 900_call
name 800_call
name catchall
Related Commands
|
|
|
|---|---|
dial-peer cor custom |
Specifies that named CORs apply to dial peers. |
nat symmetric check-media-src
To enable the gateway, to check the media source of incoming Real-time Transport Protocol (RTP) packets in symmetric Network Address Translation (NAT) environments, use the nat symmetric check-media-src command in SIP user agent configuration mode. To disable media source checking, use the no form of this command.
nat symmetric check-media-src
no nat symmetric check-media-src
Syntax Description
This command has no arguments or keywords.
Command Default
Media source checking is disabled.
Command Modes
SIP user agent configuration (sip-ua)
Command History
|
|
|
|---|---|
12.2(13)T |
This command was introduced. |
Usage Guidelines
This command provides the ability to enable or disable symmetric NAT settings for the Session Initiation Protocol (SIP) user agent. Use the nat symmetric check-media-src command to configure the gateway to check the media source address and port of the first incoming RTP packet. Checking for media packets is automatically enabled if the gateway receives the direction role "active or both".
Examples
The following example enables checking the media source:
Router(config)# sip-ua
Router(config-sip-ua)# nat symmetric check-media-src
Related Commands
|
|
|
|---|---|
nat symmetric role |
Defines endpoint settings to initiate or accept a connection for symmetric. |
nat symmetric role
To define endpoint settings to initiate or accept a connection for symmetric Network Address Translation (NAT) configuration, use the nat symmetric role command in SIP user agent configuration mode. To disable the nat symmetric role configuration, use the no form of this command.
nat symmetric role {active | passive}
no nat symmetric role {active | passive}
Syntax Description
Command Default
The endpoint settings to initiate or accept connections for NAT configuration are not defined..
Command Modes
SIP user agent configuration (sip-ua)
Command History
|
|
|
|---|---|
12.2(13)T |
This command was introduced. |
Usage Guidelines
This command provides the ability to specify symmetric NAT endpoint settings for the SIP user agent. If the gateway does not receive the direction role, use the nat symmetric role command to define endpoint settings to initiate or accept a connection for symmetric NAT configuration. This is achieved by setting the symmetric NAT endpoint role to active or passive, respectively. Cisco recommends that you use the nat symmetric role command under the following conditions:
•
Endpoints are aware of their presence inside or outside of NAT
•Endpoints parse and process direction:<role> in SDP
If the endpoints conditions are not satisfied, you may not achieve the desired results when you configure the nat symmetric role command.
Examples
The following example shows how to set the endpoint role in connection setup to active:
Router(config)# sip-ua
Router(config-sip-ua)# nat symmetric role active
Related Commands
|
|
|
|---|---|
nat symmetric check-media-src |
Enables source media checking for symmetric NAT. |
neighbor (annex g)
To configure the neighboring border elements (BEs) that interact with the local BE for the purpose of obtaining addressing information and aiding in address resolution, enter the neighbor command in Annex G configuration mode. To reset the default value, use the no form of this command.
neighbor ip-address
no neighbor
Syntax Description
ip-address |
IP address of the neighbor that is used for exchanging Annex G messages. |
Command Default
No default behavior or values
Command Modes
Annex G configuration
Command History
Examples
The following example configures a neighboring BE that has an IP address and border element ID:
Router(config)# call-router h323-annexg be20
Router(config-annexg)# neighbor 121.90.10.42
Router(config-annexg-neigh)# id be30
Router(config-annexg-neigh)# exit
Related Commands
neighbor (tgrep)
To create a TGREP session with another device, use the neighbor command in TGREP configuration mode. To disable a TRIP connection, use the no form of this command.
neighbor ip_address
no neighbor ip_address
Syntax Description
ip_address |
IP address of a peer device with which TGREP information will be exchanged. |
Command Default
No neighboring devices are defined
Command Modes
TGREP configuration
Command History
|
|
|
|---|---|
12.3(1) |
This command was introduced. |
Examples
The following example shows that the gateway with the IP address 192.116.56.10 is defined as a neighbor for ITAD 1234:
Router(config)# tgrep local-itad 1234
Router(config-tgrep)# neighbor 192.116.56.10
Related Commands
|
|
|
|---|---|
tgrep local-itad |
Enters TGREP configuration mode and defines an ITAD. |
network-clock base-rate
To configure the network clock base rate for universal I/O serial ports 0 and 1, use the network-clock base-rate command in global configuration mode. To disable the current network clock base rate, use the no form of this command.
network-clock base-rate {56k | 64k}
no network-clock base-rate {56k | 64k}
Syntax Description
56k |
Sets the network clock base rate to 56 kbps. |
64k |
Sets the network clock base rate to 64 kbps. |
Command Default
56 kbps
Command Modes
Global configuration
Command History
|
|
|
|---|---|
11.3(1)MA |
This command was introduced on the Cisco MC3810. |
Usage Guidelines
This command applies to Voice over Frame Relay and Voice over ATM.
Examples
The following example sets the network clock base rate to 64 kbps:
network-clock base-rate 64k
Related Commands
network-clock-participate
To allow the ports on a specified network module or voice/WAN interface card (VWIC) to use the network clock for timing, use the network-clock-participate command in global configuration mode. To restrict the device to use only its own clock signals, use the no form of this command.
network-clock-participate [slot slot-number | wic wic-slot | aim aim-slot-number]
no network-clock-participate [nm slot | wic wic-slot]
Syntax Description
Command Default
No network clocking is enabled, and interfaces are restricted to using the clocking generated on their own modules.
Command Modes
Global configuration
Command History
Usage Guidelines
This command is used for ATM segmentation and reassembly or digital signal processing and Cisco 3660, Cisco 3725, and Cisco 3745 routers.
This command applies to any network module with T1/E1 controllers to provide clocks from a central source (MIX module for the Cisco 3660) to the network module and to the port on the network module. Then that port can be selected as the clock source with the network-clock-select command to supply clock to other ports or network modules that choose to participate in network clocking with the network-clock-participate command. This command synchronizes the clocks for two ports.
On the Cisco 3700 series, you must use the network-clock-participate command and either the wic wic-slot keyword and argument or the slot slot-number keyword and argument.
Note If the AIM takes its clock signals from a T1 or E1 controller, it is mandatory to use the network-clock-select and network-clock-participate commands for ATM. The clocks for the ATM and voice interfaces do not need to be synchronous, but improved voice quality may result if they are.
Note The only VWICs that can participate in network clocking are digital T1/E1 packet voice trunk network modules (NM-HDV), and Fast Ethernet network modules (NM-2W, NM-1FE. and NM-2FE).
Note Beginning with Cisco IOS Release 12.4(15)T9, the network-clock-participate command can also be used for the NM-CEM-4SER modules. When the network-clock-participate command is configured, the clock is derived from the backplane. When the no network-clock-participate command is configured, the local oscillator clock is used.
Examples
The following example configures the network module in slot 5 to participate in network clocking on a Cisco 3660 with a MIX module:
network-clock-participate slot 5
network-clock-select 1 e1
The following example on a Cisco 3700 series router specifies that the AIM participates in network clocking and selects port E1 0/1 to provide the clock signals.
Router(config)# network-clock-participate wic 0
Router(config)# network-clock-participate aim 0
Router(config)# network-clock-select 2 E1 0/1
The following example on a Cisco 3660 specifies the slot number that participates in network clocking and selects port E1 5/0:
Router(config)# network-clock-participate slot 5
Router(config)# network-clock-select 1 E1 5/0
Related Commands
network-clock-select
To name a source to provide timing for the network clock and to specify the selection priority for this clock source, use the network-clock-select command in global configuration mode. To cancel the network clock selection, use the no form of this command.
network-clock-select priority {bri | atm | t1 | e1} slot/port
no network-clock-select priority {bri | atm | t1 | e1} slot/port
Syntax Description
Command Default
Cisco 2600 series and Cisco 2600XM
The network clock source is the Advanced Integration Module (AIM) phase-locked loop (PLL) with priority 5, which indicates that the network clock is in free running mode.
Cisco 3660, Cisco 3725, and Cisco 3745
The network clock source is the backplane PLL with priority 9, which indicates that the network clock is in free running mode.
Note Default clock values can fall outside the configurable range because they are derived from an external source.
Command Modes
Global configuration
Command History
Usage Guidelines
When an active clock source fails, the system chooses the next lower priority clock source specified by this command. When a higher-priority clock becomes available, the system automatically reselects the higher-priority clock source.
Cisco 2600 series and Cisco 3660
This command is used on Cisco 2600 series and Cisco 2600XM with AIMs installed or on the Cisco 3660 with Multiservice Interchange (MIX) modules installed. This command names a controller to provide clocking signals to the backplane, which then provides the names to all the network modules that are participating in network clocking.
Examples
The following example shows how to select the controller in slot 5, port 1, to provide the clock at priority 3:
network-clock-select 3 t1 5/1
Related Commands
network-clock-switch
To configure the switch delay time to the next priority network clock source when the current network clock source fails, use the network-clock-switch command in global configuration mode. To cancel the network clock delay time selection, use the no form of this command.
network-clock-switch [switch-delay | never] [restore-delay | never]
no network-clock-switch
Syntax Description
Command Default
10 seconds
Command Modes
Global configuration
Command History
|
|
|
|---|---|
11.3(1)MA |
This command was introduced on the Cisco MC3810. |
Usage Guidelines
This command applies to Voice over Frame Relay and Voice over ATM.
Examples
The following example switches the network clock source after 20 seconds and sets the delay time before the current network clock source recovers to 20 seconds:
network-clock-switch 20 20
Related Commands
|
|
|
|---|---|
network-clock-select |
Uses the network clock source to provide timing to the system backplane PCM bus. |
non-linear
To enable nonlinear processing (NLP) in the echo canceller and set its threshold or comfort-noise attenuation, use the non-linear command in voice-port configuration mode. To disable nonlinear processing, use the no form of this command.
non-linear [comfort-noise attenuation {0db | 3db | 6db | 9db} | threshold dB]
no non-linear [comfort-noise attenuation | threshold]
Syntax Description
Command Default
NLP is enabled; comfort-noise attenuation is disabled; threshold is -21 dB.
Command Modes
Voice-port configuration
Command History
Usage Guidelines
This command enables functionality that is also generally known as residual echo suppression. Use this command to shut off any signal if no near-end speech is detected. Enabling this command normally improves performance, although some users might perceive truncation of consonants at the end of sentences when this command is enabled.
Use the comfort-noise keyword if the comfort noise generated by the NLP sounds like hissing. Using this keyword makes the hissing sound less audible.
Note The echo-cancel enable command must be enabled for this command to take effect.
Examples
The following example enables nonlinear call processing on a Cisco 3600 series router:
voice-port 1/0/0
non-linear
The following example sets the attenuation level to 9 dB on a Cisco 3600 series router:
voice-port 1/0/0
non-linear comfort-noise attenuation 9db
Related Commands
|
|
|
|---|---|
echo-cancel enable |
Enables echo cancellation for voice that is sent and received on the same interface. |
notify (MGCP profile)
To specify the order in which automatic number identification (ANI) and dialed number identification service (DNIS) digits are reported to the Media Gateway Control Protocol (MGCP) call agent, use the notify command in MGCP profile configuration mode. To revert to the default, use the no form of this command.
notify {ani-dnis | dnis-ani}
no notify {ani-dnis | dnis-ani}
Syntax Description
ani-dnis |
ANI digits are sent in the first notify message, followed by DNIS. This is the default. |
dnis-ani |
DNIS digits are sent in the first notify message, followed by ANI. |
Command Default
The default order is ANI first and DNIS second.
Command Modes
MGCP profile configuration
Command History
|
|
|
|---|---|
12.4(4)T |
This command was introduced. |
Usage Guidelines
This command controls the order of ANI and DNIS when using the Feature Group D (FGD) Exchange Access North American (EANA) protocol on a T1 interface. Selecting the ani-dnis keyword causes the ANI digits to be sent in the first NTFY message to the MGCP call agent and the DNIS digits to be sent in a second NTFY message. Selecting the dnis-ani keyword causes the DNIS digits to be sent in the first NTFY message to the MGCP call agent and the ANI digits to be sent in a second NTFY message.
Examples
The following example sets the digit order to DNIS first and ANI second for the default MGCP profile:
Router(config)# mgcp profile default
Router(config-mgcp-profile)# notify dnis-ani
Related Commands
notify redirect
To enable application handling of redirect requests for all VoIP dial peers on a Cisco IOS voice gateway, use the notify redirect command in voice service VoIP configuration mode. To disable application handling of redirect requests on the gateway, use the no form of this command. To return the gateway to the default notify redirect command settings, use the default form of this command.
notify redirect {ip2ip | ip2pots}
no notify redirect {ip2ip | ip2pots}
default notify redirect {ip2ip | ip2pots}
Syntax Description
ip2ip |
Enables notify redirection for IP-to-IP calls. |
ip2pots |
Enables notify redirection for IP-to-IP calls for IP-to-POTS calls. |
Command Default
Notify redirection for IP-to-IP calls is enabled.
Notify redirection for IP-to-POTS calls is disabled.
Notify redirection for Session Initiation Protocol (SIP) phones registered to Cisco Unified Communications Manager Express (Cisco Unified CME) is enabled.
Command Modes
Voice service VoIP configuration (conf-voi-serv)
Command History
|
|
|
|---|---|
12.4(4)T |
This command was introduced. |
15.1(1)T |
This command was integrated into Cisco IOS Release 15.1(1)T. |
Usage Guidelines
Use this command to enable notify redirection globally on a gateway. Use the notify redirect command in dial peer voice configuration mode to configure notify redirection settings for IP-to-IPand IP-to-POTS calls on a specific inbound dial peer on a gateway.
Note This command is supported on Cisco Unified Communications Manager Express (Cisco Unified CME), release 3.4 and later releases and on Cisco Unified Session Initiation Protocol (SIP) Survivable Remote Site Telephony (SRST) release 3.4 and later releases. However, to use the notify redirect command in voice service VoIP configuration mode on compatible Cisco Unified SIP SRST devices, you must first use the allow-connections command to enable the corresponding call flows on the SRST gateway.
Examples
The following is partial sample output from the show running-config command showing that notify redirection has been set up globally for both IP-to-IP and IP-to-POTS calling (because support of IP-to-IP calls is enabled by default, the ip2ip setting does not appear in the output).
voice service voip
notify redirect ip2pots allow-connections h323 to h323 allow-connections h323 to sip allow-connections sip to sip no supplementary-service h450.2 no supplementary-service h450.3 sip registrar server expires max 600 min 60
Related Commands
notify redirect (dial peer)
To enable application handling of redirect requests on a specific VoIP dial peer on a Cisco IOS voice gateway, use the notify redirect command in dial peer voice configuration mode. To disable notify redirection on the gateway, use the no form of this command. To return the gateway to the default notify redirection settings, use the default form of this command.
notify redirect {ip2ip | ip2pots}
no notify redirect {ip2ip | ip2pots}
default notify redirect {ip2ip | ip2pots}
Syntax Description
ip2ip |
Enables notify redirect for IP-to-IP calls. |
ip2pots |
Enables notify redirect for IP-to-POTS calls. |
Command Default
Notify redirection for IP-to-IP is enabled.
Notify redirection for IP-to-POTS is disabled.
Notify redirection for Session Initiation Protocol (SIP) phones registered to Cisco Unified Communications Manager Express (Cisco Unified CME) is enabled.
Command Modes
Dial peer voice configuration (config-dial-peer)
Command History
|
|
|
|---|---|
12.4(4)T |
This command was introduced. |
15.1(1)T |
This command was integrated into Cisco IOS Release 15.1(1)T. |
Usage Guidelines
Use this command in dial peer configuration mode to configure IP-to-IP and IP-to-POTS calls on an inbound dial peer on a Cisco IOS voice gateway. This command configures notify redirection settings on a per-dial-peer basis.
When notify redirect is enabled in dial peer voice configuration mode, the configuration for the specific dial peer is activated only if the dial peer is an inbound dial peer. To enable notify redirect globally on a Cisco IOS voice gateway, use the notify redirect command in voice service VoIP configuration mode.
Note This command is supported on Cisco Unified Communications Manager Express (Cisco Unified CME), release 3.4 and later releases and Cisco Unified Session Initiation Protocol (SIP) Survivable Remote Site Telephony (SRST) release 3.4 and later releases. However, to use the notify redirect command in voice service VoIP configuration mode on compatible Cisco Unified SIP SRST devices, you must first use the allow-connections command to enable the corresponding call flows on the SRST gateway.
Examples
The following is partial sample output from the show running-config command showing that notify redirection is enabled for both IP-to-IP and IP-to-POTS calls on VoIP dial peer 8000 (because support of IP-to-IP calls is enabled by default, the ip2ip setting does not appear in the output):
dial-peer voice 8000 voip
destination-pattern 80..
notify redirect ip2pots
session protocol sipv2
session target ipv4:209.165.201.15
dtmf-relay rtp-nte
codec g711ulaw
!
Related Commands
notify telephone-event
To configure the maximum interval between two consecutive NOTIFY messages for a particular telephone event, use the notify telephone-event command in SIP UA configuration mode. To reset the interval to the default value, use the no form of this command.
notify telephone-event max-duration milliseconds
no notify telephone-event
Syntax Description
max-duration milliseconds |
Time interval between consecutive NOTIFY messages for a single DTMF event, in milliseconds. Range is from 40 to 3000. Default is 2000. |
Command Default
2000 milliseconds
Command Modes
SIP UA configuration (config-sip-ua)
Command History
Usage Guidelines
The notify telephone-event command works with the dtmf-relay sip-notify command. The dtmf-relay sip-notify command forwards out-of-band DTMF tones by using SIP NOTIFY messages. The notify telephone-event command sets the maximum time interval between consecutive NOTIFY messages for a single DTMF event. The maximum time is negotiated between two SIP endpoints and the lowest duration value is the one selected. This duration is negotiated during call establishment as part of negotiating the SIP-NOTIFY DTMF relay.
The originating gateway sends an indication of DTMF relay in an Invite message using the SIP Call-Info header. The terminating gateway acknowledges the message with an 18x/200 Response message, also using the Call-Info header. The set duration appears in the Call-Info header in the following way:
Call-Info: <sip: address>; method="Notify;Event=telephone-event;Duration=msec"
For example, if the maximum duration of gateway A is set to 1000 ms, and gateway B is set to 700 ms, the resulting negotiated duration would be 700 ms. Both A and B would use the value 700 in all of their NOTIFY messages for DTMF events.
Examples
The following example sets the maximum duration for a DTMF event to 40 ms.
Router(config)# sip-ua
Router(config-sip-ua)# notify telephone-event max-duration 40
Related Commands
|
|
|
|---|---|
dtmf-relay sip-notify |
Forwards DTMF tones using SIP NOTIFY messages. |
nsap
To specify the network service access point (NSAP) address for a local video dial peer, use the nsap command in dial peer configuration mode. To remove any configured NSAP address from the dial peer, use the no form of this command.
nsap nsap-address
no nsap
Syntax Description
nsap-address |
A 40-digit hexadecimal number; the number must be unique on the device. |
Command Default
No NSAP address for a video dial peer is configured
Command Modes
Dial peer configuration
Command History
|
|
|
|---|---|
12.0(5)XK |
This command was introduced for ATM video dial peer configuration on the Cisco MC3810. |
12.0(7)T |
This command was integrated into Cisco IOS Release 12.0(9)T. |
Usage Guidelines
The address must be unique on the router.
Examples
The following example sets up an NSAP address for the local video dial peer designated as 10:
dial-peer video 10 videocodec
nsap 47.0091810000000002F26D4901.333333333332.02
Related Commands
null-called-number
To substitute a user-defined number as the called number IE when an incoming H.323 setup message does not contain a called number IE, use the null-called-number command in voice service H.323 configuration mode. To disable the addition of the number used as the called number IE, use the no form of this command.
null-called-number override string
no null-called-number
Syntax Description
Command Default
The command behavior is disabled. H.323 setup messages missing the called number IE are disconnected.
Command Modes
Voice service h323 configuration (conf-serv-h323)
Command History
|
|
|
|---|---|
12.4(22)YB |
This command was introduced. |
15.0(1)M |
This command was integrated into Cisco IOS Release 15.0(1)M. |
Usage Guidelines
For a call connection to be completed the incoming H.323 setup messages must include the called number IE and the E.164 destination address. Calls lacking called number IE are disconnected. The null-called-number is a user-defined number used when the called number IE is missing to complete the call.
Examples
The following example shows the number 4567 configured as the user-defined number used to complete a call when the H.323 setup message is missing the called number IE:
Router(conf-serv-h323)# null-called-number override 4567
numbering-type
To match on a number type for a dial-peer call leg, use the numbering-type command in dial peer configuration mode. To remove the numbering type for a dial-peer call leg, use the no form of this command.
numbering-type {international | abbreviated | national | network | reserved | subscriber | unknown}
no numbering-type {international | abbreviated | national | network | reserved | subscriber | unknown}
Syntax Description
Command Default
No default behaviors or values
Command Modes
Dial peer configuration
Command History
Usage Guidelines
This command is supported for POTS, VoIP, VoFR, and VoATM dial peers. The numbering type options are implemented as defined by the ITU Q.931 specification.
Examples
The following example shows how to configure a POTS dial peer for network usage:
dial-peer voice 100 pots
numbering-type network
The following example shows how to configure a VoIP dial peer for subscriber usage:
dial-peer voice 200 voip
numbering-type subscriber
Related Commands
num-exp
To define how to expand a telephone extension number into a particular destination pattern, use the num-exp command in global configuration mode. To remove the configured number expansion, use the no form of this command.
num-exp extension-number expanded-number
no num-exp extension-number
Syntax Description
Command Default
No number expansion is defined.
Command Modes
Global configuration
Command History
Usage Guidelines
Use this command to define how to expand a particular set of numbers (for example, a telephone extension number) into a particular destination pattern. With this command, you can bind specific extensions and expanded numbers together by explicitly defining each number, or you can define extensions and expanded numbers using variables. You can also use this command to convert seven-digit numbers to numbers containing fewer than seven digits.
You can configure a maximum of 250 number extensions before the router sends an error message stating that the limit has been reached.
Use a period (.) as a variable or wildcard, representing a single number. Use a separate period for each number that you want to represent with a wildcard—for example, if you want to replace four numbers in an extension with wildcards, type in four periods.
Examples
The following example expands the extension number 50145 to the number 14085550145:
num-exp 50145 14085550145
The following example expands all five-digit extensions beginning with 5 such that the 5 is replaced with the digits 1408555 at the beginning of the extension number:
num-exp 5.... 1408555....
Feedback