|
|
Table Of Contents
network-locale (ephone-template)
network-locale (telephony-service)
night-service bell (ephone-dn)
notify redirect (voice-service)
number (voice user-profile and voice logout-profile)
Cisco Unified CME Commands: N
Last Updated: September 7, 2007First Published: February 27, 2006
This chapter contains commands to configure and maintain Cisco Unified Communications Manager Express (formally known as Cisco Unified CallManager Express). The commands are presented in alphabetical order. Some commands required for configuring Cisco Unified Communications Manager Express (Cisco Unified CME) may be found in other Cisco IOS command references. Use the command reference master index or search online to find these commands.
name (ephone-dn)
To associate a name with a Cisco CallManager Express (Cisco CME) extension (ephone-dn), use the name command in ephone-dn configuration mode. To disassociate a name from an extension, use the no form of this command.
name name
no name
Syntax Description
name
Name of the person associated with a given extension (ephone-dn). Name must follow the order specified in the directory (telephony-service) command, either first-name-first or last-name-first.
Defaults
No default behavior or values
Command Modes
Ephone-dn configuration
Command History
Usage Guidelines
The username argument is used to provide caller ID for calls originating from a Cisco CME extension. This command is also used to generate directory information for the local directory that is accessed from the Directories button on a Cisco IP phone.
Examples
The following example configures the username John Smith with the pattern first-name-first:
Router(config)# ephone-dn 1Router(config-ephone-dn) name John SmithThe following example configures the username Jane Smith with the pattern last-name-first:
Router(config)# ephone-dn 1Router(config-ephone-dn) name Smith, JaneRelated Commands
directory (telephony-service)
Defines the name order for the local directory of Cisco IP phone users.
ephone-dn
Enters ephone-dn configuration mode.
name (voice register dn)
To associate a name with a Cisco CallManager Express (Cisco CME) extension (directory number), use the name command in voice register dn configuration mode. To disassociate a name from an extension, use the no form of this command.
name name
no name
Syntax Description
name
Name of the person associated with a given extension. Name must follow the order specified in the directory (telephony-service) command, either first-name-first or last-name-first.
Defaults
No default behavior or values
Command Modes
Voice register dn configuration
Command History
Usage Guidelines
The name argument is used to provide caller ID for calls originating from a Cisco CME extension. This command is also used to generate directory information for the local directory that is accessed from the Directories button on a Cisco IP phone.
Examples
The following example shows how to configure the username John Smith with the pattern first-name-first:
Router(config)# voice register dn 1Router(config-register-dn) name John SmithThe following example shows how to configure the username Jane Smith with the pattern last-name-first:
Router(config)# voice register dn 1Router(config-register-dn) name Smith, JaneRelated Commands
network-locale (ephone-template)
To specify a locale tag identifier in an ephone template, use the network-locale command in ephone-template configuration mode. To use the default user locale, use the no form of this command.
user-locale language-tag
no user-locale
Syntax Description
language-tag
Language tag identifier that was assigned to an alternative network locale using the network-locale (telephony-service) command.
Command Default
The default network locale (network locale 0) is used.
Command Modes
Ephone-template configuration
Command History
12.4(4)XC
Cisco Unified CME 4.0
This command was introduced.
12.4(9)T
Cisco Unified CME 4.0
This command was integrated into Cisco IOS Release 12.4(9)T.
Usage Guidelines
To apply network locale tag identifiers to individual ephones, you must specify per-phone configuration files using the cnf-file perphone command and define the locale tags using the network-locale (telephony-service) command.
After creating an ephone template that contains a locale tag identifier, use the ephone-template (ephone) command to apply the template to individual ephones.
Examples
The following example defines three alternative locales: JP (Japan), FR (France), and ES (Spain). The default is US for all phones that do not have the alternatives applied using ephone templates. In this example, ephone 11 uses JP for its locales, ephone 12 uses FR, ephone 13 uses ES, and ephone 14 uses the default, US.
telephony-servicecnf-file location flash:cnf-file perphonecreate cnf-filesuser-locale 1 JPuser-locale 2 FRuser-locale 3 ESnetwork-locale 1 JPnetwork-locale 2 FRnetwork-locale 3 ESephone-template 1user-locale 1network-locale 1ephone-template 2user-locale 2network-locale 2ephone-template 3user-locale 3network-locale 3ephone 11button 1:25ephone-template 1ephone 12button 1:26ephone-template 2ephone 13button 1:27ephone-template 3ephone 14button 1:28Related Commands
network-locale (telephony-service)
To select a code for a geographically specific set of tones and cadences on supported phone types, use the network-locale command in telephony-service configuration mode. To disable selection of a code, use the no form of this command.
network-locale [network-locale-tag [user-defined-code]] locale-code
no network-locale network-locale-tag
Syntax Description
Command Default
The default locale code is US (United States).
Command Modes
Telephony-service configuration
Command History
Usage Guidelines
The show telephony-service tftp-bindings command displays the locale-specific call-progress tone files that are accessible to IP phones using TFTP.
This command must be followed by a complete phone reboot using the reset command.
Network locale 0 always holds the default locale, which is used for all phones that are not assigned alternative network locales or user-defined network locales. The system default is US, but you can define a different code to be the default, as shown in the " Examples" section.
Alternative Network Locales
The network-locale-tag argument allows you to specify up to five alternative network locales for use in a system using Cisco Unified CME 4.0 or a later release. For example, a company can specify network-locale France for phones A, B, and C; network-locale Germany for phones D, E, and F; and network-locale United States for phones G, H, and I.
Each one of the five alternative network locales that you can use in a multi-locale system is identified with a locale tag identifier. The identifier 0 always holds the default locale, although you can define this default to be any locale code that is supported in the system and is listed in the CLI help for the command. For example, if you define network locale 0 to be JP (Japanese), the default network locale for the router is JP. If you do not specify a locale for the identifier 0, the default is US (United States).
To apply alternative network locales to different phones, you must use the cnf-files command to specify per-phone configuration files. When you use per-phone configuration files, a phone's configuration file automatically uses the default locales in user locale 0 and network locale 0. You can override this default for individual ephones by assigning alternative locale tag identifiers to the alternative locale codes that you want to use and then creating ephone templates to assign the locale tag identifiers to individual ephones. For example, you can give the alternative locale tag of 2 to the locale code DK (Denmark).
After using the network-locale (telephony-service) command to associate a locale tag identifier with a locale code, use the network-locale command in ephone-template mode to apply the locale tag to an ephone template. Then use the ephone-template command in ephone configuration mode to apply the template to the ephones that should use the alternative network locale. For an example, see the Alternative Network Locale Example.
User-Defined Network Locales
XML files for user locales and network locales that are not currently provided in the system must be downloaded to use this feature. Beginning in Cisco Unified CME 4.0, you can install the files to support a particular user and network locale in flash, slot 0, or an external TFTP server. You cannot install these files in the system location. These user-locale and network-locale files can then be used as default or alternative locales for all or some phones.
For example, if you have a site at which the phones should use the displays and tones for Traditional Chinese, which is not one of the predefined locales, you must download and install the XML files for Traditional Chinese on the phones that need to use this locale.
Examples
The following example sets the default locale tag 0 to France:
telephony-servicenetwork-locale FRThe following example sets the default locale tag 0 to France. It shows another way to change the default network locale:
telephony-servicenetwork-locale 0 FRThe following example sets the alternative locale tag 1 to Germany:
telephony-servicenetwork-locale 1 DEAlternative Network Locale Example
The following example defines three alternative locales: JP (Japan), FR (France), and ES (Spain). The default is US for all phones that do not have the alternatives applied using ephone templates. In this example, ephone 11 uses JP for its locales, ephone 12 uses FR, ephone 13 uses ES, and ephone 14 uses the default, US.
telephony-servicecnf-file location flash:cnf-file perphoneuser-locale 1 JPuser-locale 2 FRuser-locale 3 ESnetwork-locale 1 JPnetwork-locale 2 FRnetwork-locale 3 EScreate cnf-filesephone-template 1user-locale 1network-locale 1ephone-template 2user-locale 2network-locale 2ephone-template 3user-locale 3network-locale 3ephone 11button 1:25ephone-template 1ephone 12button 1:26ephone-template 2ephone 13button 1:27ephone-template 3ephone 14button 1:28User-Defined Network Locale Example
The following example applies the alternative locale tag 4 to the user-defined code U1, which is defined as ZH. ZH is the code that represents Traditional Chinese in ISO 639, the Language Code Reference. Because the code for Traditional Chinese is not one of those is provided in the system, the user must download the appropriate XML files to support this language.
In addition to the user-defined code, the example also defines three alternative locales: JP (Japan), FR (France), and ES (Spain). The default is US for all phones that do not have the alternatives applied using ephone templates. In this example, ephone 11 uses JP for its locales; ephone 12 uses FR; ephone 13 uses ES; ephone 14 uses the default, US; and ephone 15 uses the user-defined language, ZH (Traditional Chinese).
telephony-servicecnf-file location flash:cnf-file perphoneuser-locale 1 JPuser-locale 2 FRuser-locale 3 ESuser-locale 4 U1 ZHnetwork-locale 1 JPnetwork-locale 2 FRnetwork-locale 3 ESnetwork-locale 4 U1 ZHcreate cnf-filesephone-template 1user-locale 1network-locale 1ephone-template 2user-locale 2network-locale 2ephone-template 3user-locale 3network-locale 3ephone-template 4user-locale 4network-locale 4ephone 11button 1:25ephone-template 1ephone 12button 1:26ephone-template 2ephone 13button 1:27ephone-template 3ephone 14button 1:28ephone 15button 1:29ephone-template 4Related Commands
night-service bell
To mark an IP phone to receive night-service bell notification when incoming calls are received on ephone-dns that are marked for night service during night-service time periods, use the night-service bell command in ephone or ephone-template configuration mode. To remove night-service notification capability from a phone, use the no form of this command.
night-service bell
no night-service bell
Syntax Description
This command has no arguments or keywords.
Command Default
A phone is not marked for night-service bell notification.
Command Modes
Ephone configuration
Ephone-template configurationCommand History
Usage Guidelines
When an ephone-dn is marked for night-service treatment using the night-service bell (ephone-dn) command, incoming calls that ring during the night-service time period on that ephone-dn send an alert indication to all IP phones that are marked to receive night-service bell notification with this command. The alert notification is in the form of a splash ring (not associated with any of the individual lines on the IP phone) and a visible display of the ephone-dn extension number. The phone user retrieves the call by pressing a PickUp or GPickUp soft key and dialing the appropriate digits.
Night-service periods are defined using the night-service date and night-service day commands. Night service can be manually disabled or reenabled from a phone configured with ephone-dns in night-service mode if the night-service code command has been set.
If you use an ephone template to apply a command to a phone and you also use the same command in ephone configuration mode for the same phone, the value that you set in ephone configuration mode has priority.
Examples
The following example designates the IP phone that is being configured as a phone that will receive night-service bell notification when ephone-dns marked for night service receive incoming calls during a night-service period:
Router(config)# ephone 4Router(config-ephone)# night-service bellRelated Commands
night-service bell (ephone-dn)
To mark an ephone-dn for night-service treatment, use the night-service bell command in ephone-dn configuration mode. To remove the night-service treatment from the ephone-dn, use the no form of this command.
night-service bell
no night-service bell
Syntax Description
This command has no arguments or keywords.
Defaults
An ephone-dn is not marked for night service.
Command Modes
Ephone-dn configuration
Command History
12.2(15)ZJ
3.0
This command was introduced.
12.3(4)T
3.0
This command was integrated into Cisco IOS Release 12.3(4)T.
Usage Guidelines
When an ephone-dn is marked for night-service treatment using this command, incoming calls that ring during the night-service time period on that ephone-dn send an alert indication to all IP phones that are marked to receive night-service bell notification using the night-service bell (ephone) command. The alert notification is in the form of a splash ring (not associated with any of the individual lines on the IP phone) and a visible display of the ephone-dn extension number. The phone user retrieves the call by pressing a PickUp or GPickUp soft key and dialing the appropriate digits.
Night-service periods are defined using the night-service date and night-service day commands. Night service can be manually disabled or reenabled from a phone configured with ephone-dns in night-service mode if the night-service code command has been set.
Examples
The following example marks an ephone-dn as a line that will ring on IP phones designated to receive night-service bell notification when incoming calls are received on this ephone-dn during night-service periods:
Router(config)# ephone-dn 16Router(config-ephone-dn)# night-service bellRelated Commands
night-service code
To define a code to disable or reenable night service on IP phones, use the night-service code command in telephony-service configuration mode. To remove the code, use the no form of this command.
night-service code digit-string
no night-service code digit-string
Syntax Description
Defaults
No code is defined.
Command Modes
Telephony-service configuration
Command History
Usage Guidelines
Night-service periods are defined with the night-service date and night-service day commands. When an ephone-dn is marked for night-service treatment using the night-service bell (ephone-dn) command, incoming calls that ring during the night-service time period on that ephone-dn send an alert indication to all IP phones that are marked to receive night-service bell notification using the night-service bell (ephone) command. The alert notification is in the form of a splash ring (not associated with any of the individual lines on the IP phone) and a visible display of the ephone-dn extension number. The phone user retrieves the call by pressing a PickUp or GPickUp soft key and dialing the appropriate digits.
When a night-service code has been defined using the night-service code command, night service for all night-service ephone-dns can be manually activated or deactivated from any phone that is configured with a night-service ephone-dn.
Examples
The following example defines a night-service code of *2985:
Router(config)# telephony-serviceRouter(config-telephony)# night-service code *2985Related Commands
night-service date
To define a recurring time period associated with a date during which night service is active, use the night-service date command in telephony-service configuration mode. To delete the defined time period, use the no form of this command.
night-service date month day start-time stop-time
no night-service date month day start-time stop-time
Syntax Description
Defaults
No time period based on date is defined for night service.
Command Modes
Telephony-service configuration
Command History
12.2(15)ZJ
3.0
This command was introduced.
12.3(4)T
3.0
This command was integrated into Cisco IOS Release 12.3(4)T.
Usage Guidelines
After you define night-service periods using this command and the night-service day command, use the night-service bell (ephone-dn) command to specify the extensions that will ring on other phones and the night-service bell (ephone) command to specify the phones on which the extensions will ring during the designated night-service periods.
Examples
The following example defines a night-service time period for the entire day of January 1:
Router(config)# telephony-serviceRouter(config-telephony)# night-service date jan 1 00:00 00:00Related Commands
night-service day
To define a recurring time period associated with a day of the week during which night service is active, use the night-service day command in telephony-service configuration mode. To delete the defined time period, use the no form of this command.
night-service day day start-time stop-time
no night-service day day start-time stop-time
Syntax Description
Defaults
No time period based on day of the week is defined for night service.
Command Modes
Telephony-service configuration
Command History
12.2(15)ZJ
3.0
This command was introduced.
12.3(4)T
3.0
This command was integrated into Cisco IOS Release 12.3(4)T.
Usage Guidelines
After you define night-service periods using this command and the night-service date command, use the night-service bell (ephone-dn) command to specify the extensions that will ring on other phones and the night-service bell (ephone) command to specify the phones on which the extensions will ring during the designated night-service periods.
Examples
The following example defines a night-service time period from Monday at 7 p.m. to Tuesday at 9 a.m.:
Router(config)# telephony-serviceRouter(config-telephony)# night-service day mon 19:00 09:00Related Commands
night-service everyday
To define a recurring time period during which night service is active every day, use the night-service everyday command in telephony-service configuration mode. To delete the defined time period, use the no form of this command.
night-service everyday start-time stop-time
no night-service everyday
Syntax Description
Command Default
No recurring night-service time period is defined for every day.
Command Modes
Telephony-service configuration
Command History
12.4(4)XC
Cisco Unified CME 4.0
This command was introduced.
Usage Guidelines
After you define recurring night-service time periods, use the night-service bell (ephone-dn) command to specify the extensions that will ring on other phones and the night-service bell (ephone) command to specify the phones on which the extensions will ring during the designated night-service periods.
Examples
The following example defines a night-service time period to be in effect every day from 7 p.m. to 8 a.m.:
Router(config)# telephony-serviceRouter(config-telephony)# night-service everyday 19:00 08:00Related Commands
night-service weekday
To define a recurring night-service time period to be in effect on all weekdays, use the night-service weekday command in telephony-service configuration mode. To delete the defined time period, use the no form of this command.
night-service weekday start-time stop-time
no night-service weekday
Syntax Description
Command Default
No recurring night-service time period is defined for weekdays.
Command Modes
Telephony-service configuration
Command History
12.4(4)XC
Cisco Unified CME 4.0
This command was introduced.
12.4(9)T
Cisco Unified CME 4.0
This command was integrated into Cisco IOS Release 12.4(9)T.
Usage Guidelines
Weekdays are defined as Monday, Tuesday, Wednesday, Thursday, and Friday.
After you define night-service periods, use the night-service bell (ephone-dn) command to specify the extensions that will ring on other phones and the night-service bell (ephone) command to specify the phones on which the extensions will ring during the designated night-service periods.
Examples
The following example defines a night-service time period every weekday from 5 p.m. to 9 a.m.:
Router(config)# telephony-serviceRouter(config-telephony)# night-service weekday 17:00 09:00Related Commands
night-service weekend
To define a recurring night-service time period to be active on weekends, use the night-service weekend command in telephony-service configuration mode. To delete the defined time period, use the no form of this command.
night-service weekend start-time stop-time
no night-service weekend
Syntax Description
Command Default
No recurring night-service time period is defined for weekends.
Command Modes
Telephony-service configuration
Command History
12.4(4)XC
Cisco Unified CME 4.0
This command was introduced.
12.4(9)T
Cisco Unified CME 4.0
This command was integrated into Cisco IOS Release 12.4(9)T.
Usage Guidelines
Weekend is defined as Saturday and Sunday.
After you define night-service periods, use the night-service bell (ephone-dn) command to specify the extensions that will ring on other phones and the night-service bell (ephone) command to specify the phones on which the extensions will ring during the designated night-service periods.
Examples
The following example defines a night-service time period for all day Saturdays and Sundays:
Router(config)# telephony-serviceRouter(config-telephony)# night-service weekend 00:00 00:00Related Commands
no-reg
To specify that the pilot number for a Cisco CallManager Express (Cisco CME) peer ephone hunt group not register with an H.323 gatekeeper, use the no-reg command in ephone-hunt configuration mode. To return to the default of the pilot number registering with an H.323 gatekeeper, use the no form of this command.
no-reg [both | pilot]
no no-reg [both | pilot]
Syntax Description
both
(Optional) Both the primary and secondary pilot numbers are not registered.
pilot
(Optional) Only the primary pilot number is not registered.
Defaults
If this command is not used, the pilot number registers with the H.323 gatekeeper. If this command is used but neither the both keyword nor the pilot keyword is used, only the secondary number is not registered.
Command Modes
Ephone-hunt configuration
Command History
Usage Guidelines
This command is valid only for Cisco CME peer ephone hunt groups.
Examples
The following example defines peer ephone hunt group 2 with a primary and secondary pilot number, and specifies that the secondary pilot number should not register with the H.323 gatekeeper:
Router(config)# ephone-hunt 2 peerRouter(config-ephone-hunt)# pilot 2222 secondary 4444Router(config-ephone-hunt)# no-regRelated Commands
no-reg (voice register dn)
To specify that a voice DN for a SIP phone line in a Cisco CallManager Express (Cisco CME) system not register with an external proxy server, use the no-reg command in voice register dn configuration mode. To return to the default, use the no form of this command.
no-reg
no no-reg
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Voice register dn configuration
Command History
Usage Guidelines
Use this command to specify that a particular voice DN not register with the external proxy server. Configure the no-reg command per line. The default is to register all SIP lines in the Cisco CME system.
Examples
The following example shows how to configure bulk registration for registering a block of phone numbers starting with 408555 with an external registrar and specify that directory number 1, number 4085550100 not register with the external registrar:
Router(config)# voice register globalRouter(voice-register-global)# mode cmeRouter(voice-register-global)# bulk 408555....Router(voice-register-global)# exitRouter(config)# voice register dn 1Router(config-register-dn)# number 408550100Router(config-register-dn)# no-regRelated Commands
notify redirect (dial-peer)
To send a redirect facility to the application handling the redirect request on a specific VoIP dial peer using the Cisco IOS voice gateway, use the notify redirect command in the dial-peer configuration mode. To return to the default, use the no form of this command.
notify redirect {ip2ip | ip2pots}
no notify redirect
Syntax Description
ip2ip
Sends redirect facility to the application handling redirect requests for IP-to-IP calls.
ip2pots
Sends redirect facility to the application handling redirect requests for IP-to-POTS calls.
Command Default
Disabled
Command Modes
Dial-peer configuration
Command History
12.4(4)T
Cisco CME 3.4
Cisco SIP SRST 3.4This command was introduced.
Usage Guidelines
The notify redirect command in dial-peer configuration mode must be configured on the inbound dial peer of the gateway. This command enables, on a per dial peer basis, IP-to-IP or IP-to-POTS notify redirection for the gateway.
When notify redirect is configured in dial-peer 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, use the notify redirect command in voice-service configuration mode.
Note
Use the notify redirect (dial-peer) command to configure Cisco SIP SRST 3.4 only after using the allow-connections command to enable B2BUA call flow on the SRST gateway.
Examples
The following is partial sample output from the show running-config command showing that notify redirect has been set up for IP-to-POTS calls on VoIP dial peer 8000:
dial-peer voice 8000 voip destination-pattern 80.. notify redirect ip2pots session protocol sipv2 session target ipv4:1.5.33.200 dtmf-relay rtp-nte codec g711ulaw !Related Commands
Related Commands
notify redirect (voice-service)
To send a redirect facility to the application handling redirect requests for all VoIp dial peers on the Cisco IOS voice gateway, use the notify redirect command in the voice-service configuration mode. To return to the default, use the no form of this command.
notify redirect {ip2ip | ip2pots}
no notify redirect
Syntax Description
ip2ip
Sends redirect facility to the application handling redirect requests for IP-to-IP calls.
ip2pots
Sends redirect facility to the application handling redirect requests for IP-to-POTS calls.
Command Default
Disabled
Command Modes
Voice-service configuration
Command History
12.4(4)T
Cisco CME 3.4
Cisco SIP SRST 3.4This command was introduced.
Usage Guidelines
Use this command to enable notify redirection globally on a gateway. Use the notify redirect command in dial-peer configuration mode to configure IP-to-IP or IP-to-POTS notify redirection on a specific inbound dial peer.
Note
Examples
The following is partial sample output from the show running-config command showing that notify redirect has been set up globally for IP-to-POTS calling:
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
ntp-server
To specify the IP address of the Network Time Protocol (NTP) server used by SIP phones in a Cisco Unified CME system, use the ntp-server command in voice register global configuration mode. To remove the NTP server, use the no form of this command.
ntp-server ip-address [mode {anycast | directedbroadcast | multicast | unicast}]
no ntp-server
Syntax Description
Command Default
An NTP server is not used.
Command Modes
Voice register global configuration
Command History
Usage Guidelines
This command synchronizes all SIP phones to the specified NTP server.
This command is not supported on the Cisco Unified IP Phone 7905, 7912, 7940, or 7960.
Examples
The following example shows the mode for the NTP server set to multicast:
Router(config)# voice register globalRouter(config-register-global)# ntp-server 10.10.10.1 mode multicastRelated Commands
number (ephone-dn)
To associate a telephone or extension number with an ephone-dn in a Cisco CallManager Express (Cisco CME) system, use the number command in ephone-dn configuration mode. To disassociate a number from an ephone-dn, use the no form of this command.
number number [secondary number] [no-reg [both | primary]]
no number
Syntax Description
Defaults
No primary or secondary phone number is associated with the ephone-dn.
Command Modes
Ephone-dn configuration
Command History
Usage Guidelines
This command defines a valid number for an ephone-dn (extension) that is to be assigned to an IP phone. The secondary keyword allows you to associate a second telephone number with an ephone-dn so that it can be called by dialing either the main or secondary phone number. The secondary number may contain wildcards; for example, 50.. (the number 50 followed by periods, which stand for wildcards).
The no-reg keyword causes an E.164 number in the dial peer not to register with the gatekeeper. If you do not specify both or primary after the no-reg keyword, only the secondary number does not register.
A number normally contains only numeric characters, which allow it to be dialed from any telephone keypad. However, in certain cases, such as intercom numbers, which are normally dialed only by the router, you can insert alphabetic characters into the number to prevent phone users from dialing it and using the intercom function without authorization.
A number can also contain one or more periods (.) as wildcard characters that will match any dialed number in that position. For example, 51.. rings when 5100 is dialed, when 5101 is dialed, and so forth.
After you use the number command, assign the ephone-dn to an ephone using the button command. Following the use of the button command, the restart command must be used to initiate a quick reboot of the phone to which this number is assigned.
Examples
The following example sets 5001 as the primary extension number for a Cisco IP phone and 0 as the secondary number. This configuration allows the telephone number 5001 to act as a regular extension number and also to act as the operator line such that callers who dial 0 are routed to the phone line with extension number 5001.
Router(config)# ephone-dn 1Router(config-ephone-dn)# number 5001 secondary 0The following example sets 5001 as the primary extension number for a Cisco IP phone and "500." (the number 500 followed by a period) as the secondary number. This configuration allows any calls to extension numbers from the range 5000 to 5009 to be routed to extension 5001 if the actual extension number dialed cannot be found. For example, IP phones may be active in the system with lines that correspond to 5001, 5002, 5004, 5005, and 5009. A call to 5003 would be unable to locate a phone with extension 5003, so the call would be routed to extension 5001.
Router(config-ephone-dn)# number 5001 secondary 500.The following example defines a pair of intercom ephone-dns that are programmed to call each other. The intercom numbers contain alphabetic characters to prevent anyone from dialing them from another phone. Ephone-dn 19 is assigned the number A5511 and is programmed to dial A5522, which belongs to ephone-dn 20. Ephone-dn 20 is programmed to dial A5511. No one else can dial these numbers.
Router(config)# ephone-dn 19Router(config-ephone-dn)# number A5511Router(config-ephone-dn)# name IntercomRouter(config-ephone-dn)# intercom A5522Router(config-ephone-dn)# exitRouter(config)# ephone-dn 20Router(config-ephone-dn)# number A5522Router(config-ephone-dn)# name IntercomRouter(config-ephone-dn)# intercom A5511Related Commands
number (voice register dn)
To associate a telephone or extension number with a SIP phone in a Cisco CallManager Express (Cisco CME) system, use the number command in voice register dn configuration mode. To disassociate a number, use the no form of this command.
number number
no number
Syntax Description
Defaults
No default behavior or values
Command Modes
Voice register dn configuration
Command History
12.4(4)T
Cisco CME 3.4 and Cisco SIP SRST 3.4
This command was introduced.
Usage Guidelines
This command defines a valid number for an extension that is to be assigned to a SIP phone. Use this command before using the other commands in voice register dn configuration mode.
A number normally contains only numeric characters which allows users to dial the number from any telephone keypad. However, in certain cases, such as the numbers for intercom extensions, you want to use numbers that can only be dialed internally from the Cisco CallManager Express router and not from telephone keypads.
The number command allows you to assign alphabetic characters to the number so that the extension can be dialed by the router for intercom calls but not by unauthorized individuals from other phones.
After you use the number command, use the reset command to initiate a quick reboot of the phone to which this number is assigned.
Note
Examples
The following example shows how to set 5001 as the extension number for directory number 1 on a SIP phone.
Router(config)# voice register dn 1Router(config-register-dn)# number 5001Related Commands
number (voice register pool)
To indicate the E.164 phone numbers that the registrar permits to handle the Register message from the Cisco SIP IP phone, use the number command in voice register pool configuration mode. To disable number registration, use the no form of this command.
number tag {number-pattern [preference value] [huntstop] | dn dn-tag}
no number tag
Syntax Description
Command Default
None (see the syntax description for syntax-level defaults)
Command Modes
Voice register pool configuration
Command History
Usage Guidelines
The number command indicates the phone numbers that are permitted by the registrar to handle the Register message from the SIP phone. The keywords and arguments of this command allow for more explicit setting of user preferences regarding what number patterns should match the voice register pool.
Note
Examples
The following example shows three directory numbers assigned to SIP phone 1 in Cisco Unified CME.
!voice register pool 1id mac 0017.E033.0284type 7961number 1 dn 10number 2 dn 12number 3 dn 13codec g711ulaw!The following example shows a telephone number pattern set to 95... in Cisco Unified SRST. This means all five-digit numbers beginning with 95 are permitted by the registrar to handle the Register message.
voice register pool 3id network 10.2.161.0 mask 255.255.255.0number 1 95... preference 1cor incoming call95 1 95011Related Commands
id (voice register pool)
Explicitly identifies a locally available individual Cisco SIP IP phone, or when running Cisco Unified SIP SRST, set of Cisco SIP IP phones.
number (voice user-profile and voice logout-profile)
To create line definitions in a voice-user profile or voice-logout profile to be downloaded to a Cisco Unified IP phone that is enabled for extension mobility, use the number command in voice user-profile configuration mode or voice logout-profile configuration mode. To remove line definition from a profile, use the no form of this command.
number number [,...number] type type
no number number [,...number] type type
Syntax Description
Command Default
No line definition is created.
Command Modes
Voice logout-profile configuration (config-logout-profile)
Voice user-profile configuration (config-user-profile)Command History
12.4(11)XW
Cisco Unified CME 4.2
This command was introduced.
Usage Guidelines
Use this command in voice user-profile configuration mode to create a line button definition in a user profile to be downloaded to the IP phone when the user is logged into an IP phone that is enabled for extension mobility.
Use this command in voice logout-profile configuration mode to create a line button definition in a default profile to be downloaded to an IP phone when no user is logged into an IP phone that is enabled for extension mobility.
For button appearance, extension mobility will associate line definitions in the voice-logout profile or voice-user profile to phone buttons in a sequential manner. If the profile contains more directory and speed-dial numbers than there are buttons on the physical phone to which the profile is downloaded, the remaining numbers in the profile are ignored.
On Cisco Unified IP phones, line definitions are assigned to available extension buttons before speed-dial definitions, in sequential order, starting with the lowest directory number first.
After creating or modifying a profile, use the reset (voice logout-profile or voice user-profile) command to reset all phones associated with the profile being configured to propagate the changes.
Type ? to list valid options for the type keyword. The following options are valid at the time that this document was written:
•
Beep but no ring. Audible ring is suppressed for incoming calls but call-waiting beeps are allowed. Visible cues are the same as those for a normal ring.
•
Differentiates incoming calls on a special line from incoming calls on other lines on the phone. The feature-ring cadence is a triple pulse, as opposed to a single-pulse ring for normal internal calls and a double-pulse ring for normal external calls.
•
A line button that is configured for monitor mode on one phone provides visual line status for a line that also appears on another phone. When monitor mode is set for a button with a shared line, the line status indicates that the shared line is either idle or in use. The line and line button are available in monitor mode for visual status only. Calls cannot be made or received using a line button that has been set in monitor mode. Incoming calls on a line button that is in monitor mode do not ring and do not display caller ID or call-waiting caller ID. Monitor mode is intended to be used only in the context of shared lines so that one user, such as a receptionist, can visually monitor the in-use status of several users' phone extensions (for example, as a busy-lamp field).
The line button for a monitored line can be used as a direct-station-select for a call transfer when the monitored line is in an idle state. In this case, the phone user who transfers a call from a normal line can press the Transfer button and then press the line button of the monitored line, causing the call to be transferred to the phone number of the monitored line.
•
You can configure silent ring on any type of phone. However, you typically set silent ring only on buttons of a phone with multiple lines, such as a Cisco Unified IP Phone 7940 or Cisco Unified IP Phone 7960 and 7960G. The only visible cue is a flashing icon in the phone display.
If you configure a button to have a silent ring, you will not hear a call-waiting beep or call-waiting ring regardless of whether the ephone-dn associated with the button is configured to generate a call-waiting beep or call-waiting ring.
Note
•
Overlay lines are directory numbers that share a single line button on a multibutton phone. When more than one incoming call arrives on lines that are set on a single button, the line (ephone-dn) that is the left most in the number command list is the primary line and is given the highest priority. If this call is answered by another phone or if the caller hangs up, the phone selects the next line in its overlay set to present as the ringing call. The caller ID display updates to show the caller ID for the currently presented call.
Directory numbers that are part of an overlay set can be single-line directory numbers or dual-line directory numbers, but the set must contain either all single-line or all dual-line directory numbers, and not a mixture of the two.
The primary directory number on each phone in a shared-line overlay set should be a unique ephone-dn. The unique ephone-dn guarantees that the phone will have a line available for outgoing calls, and ensures that the phone user can obtain dial-tone even when there are no idle lines available in the rest of the shared-line overlay set. Use a unique directory number in this manner to provide for a unique calling party identity on outbound calls made by the phone so that the called user can see which specific phone is calling.
The name of the first directory number in the overlay set is not displayed because it is the default directory number for calls to the phone, and the name or number is permanently displayed next to the phone's button. For example, if there are ten numbers in an overlay set, only the last nine numbers are displayed when calls are made to them.
•
The same configuration is used for overlaid lines both with and without call waiting.
Directory numbers can accept call interruptions, such as call waiting, by default. For call waiting to work, the default must be active. To ensure that this is the case, remove the no call-waiting beep accept command from the configurations of directory numbers for which you want to use call waiting.
Directory numbers that are part of a cw-overlay set can be single-line directory numbers or dual-line directory numbers, but the set must contain either all single-line or all dual-line directory numbers, and not a mixture of the two.
The Cisco Unified IP Phone 7931G cannot support overlays that contain directory numbers that are configured for dual-line mode.
Examples
The following example shows the configuration for a voice-user profile to be downloaded when the a phone user logs into a Cisco Unified IP phone that is enabled for extension mobility. The lines and speed-dial buttons in this profile that are configured on an IP phone after the user logs in depend on phone type. For example, if the user logs into a Cisco Unified IP Phone 7970, all buttons are configured according to voice-user profile1. However, if the phone user logs into a Cisco Unified IP Phone 7960, all six lines are mapped to phone buttons, and the speed dial is ignored because there is no button available for speed dial.
pin 12345user me password pass123number 2001 type silent-ringnumber 2002 type beep-ringnumber 2003 type feature-ringnumber 2004 type monitor-ringnumber 2005,2006 type overlaynumber 2007,2008 type cw-overlyspeed-dial 1 3001speed-dial 2 3002 blfRelated Commands
Posted: Fri Sep 7 08:09:54 PDT 2007
All contents are Copyright © 1992--2007 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
