Table Of Contents
Configuring System-Level Parameters
Contents
Prerequisites for System-Level Parameters
Information About Configuring System-Level Parameters
Network Time Protocol for SIP Phones
Per-Phone Configuration Files
Redundant Cisco Unified CME Router
Timeouts
How to Configure System-Level Parameters
Configuring Bulk Registration
SCCP: Setting Up Cisco Unified CME
SCCP: Setting Date and Time Parameters
SCCP: Blocking Automatic Registration
SCCP: Defining Per-Phone Configuration Files and Alternate Location
SCCP: Changing Defaults for Time Outs
SCCP: Configuring a Redundant Router
SIP: Setting Up Cisco Unified CME
SIP: Setting Date and Time Parameters
SIP: Setting Network Time Protocol
SIP: Changing Session-Level Application for SIP Phones
Configuration Examples for System-Level Parameters
System-Level Parameters: Example
Blocking Automatic Registration: Example
Redundant Router: Example
Where to Go Next
Additional References
Related Documents
Technical Assistance
Feature Information for System-Level Parameters
Configuring System-Level Parameters
Last Updated: September 25, 2007
This chapter describes the system-level settings to configure before you add devices and configure Cisco Unified Communications Manager Express (Cisco Unified CME) features.
Note 
If you used Cisco Unified Communications Express - QCT to generate a basic telephony configuration, you can skip this module.
Finding Feature Information in This Module
Your Cisco Unified CME version may not support all of the features documented in this module. For a list of the versions in which each feature is supported, see the "Feature Information for System-Level Parameters" section.
Contents
• Prerequisites for System-Level Parameters
• Information About Configuring System-Level Parameters
• How to Configure System-Level Parameters
• Configuration Examples for System-Level Parameters
• Where to Go Next
• Additional References
• Feature Information for System-Level Parameters
Prerequisites for System-Level Parameters
•To support Cisco Unified IP phones that are running SIP to be connected directly to the Cisco Unified CME router, Cisco CME 3.4 or a later version must be installed on the router. For installation information, see "Installing and Upgrading Cisco Unified CME Software" on page 87.
•Cisco Unified CME must be configured to work with your IP network. For configuration information, see "Defining Network Parameters" on page 109.
Information About Configuring System-Level Parameters
To configure system-level parameters, you should understand the following concepts:
• Network Time Protocol for SIP Phones
• Per-Phone Configuration Files
• Redundant Cisco Unified CME Router
• Timeouts
Network Time Protocol for SIP Phones
SIP phones registered to a Cisco Unified CME router can synchronize to an NTP server. SIP phones can synchronize to the Cisco Unified CME router, however some routers can lose their clock after a reboot causing phones to display the wrong time. Synchronizing to an NTP server ensures that SIP phones maintain the correct time. You enable NTP for all SIP phones by using the ntp-server command in voice register global configuration mode. For configuration information, see the "SIP: Setting Network Time Protocol" section.
Per-Phone Configuration Files
In Cisco Unified CME 4.0 and later versions, you can use an external TFTP server to offload the TFTP server function on the Cisco Unified CME router. You can also use flash memory or slot 0 on the Cisco Unified CME router for this purpose. This additional storage capacity allows you to use different configuration files for each phone type or for each phone, which allows you to specify different user locales and network locales for different phones. Before this version, you could specify only a single default user and network locale for a Cisco Unified CME system.
You can specify one of the following four locations to store configuration files:
•System—This is the default. When the system is the storage location, there can be only one default configuration file and it is used for all phones in the system. All phones, therefore, use the same user locale and network locale. User-defined locales are not supported. To use the system location, either do not use the cnf-file location command to specify a location or use the no cnf-file location {flash: | slot0: | tftp url} command to reset the option from a previous, different location.
•Flash or slot 0—When flash or slot 0 memory on the router is the storage location, you can create additional configuration files to apply per phone type or per individual phone. Up to five user and network locales can be used in these configuration files. To store configuration files in flash or slot 0, use the cnf-file location flash: or cnf-file location slot0: command.
Note When the storage location chosen is flash and the file system type on this device is Class B (LEFS), check free space on the device periodically and use the squeeze command to free the space used up by deleted files. Unless you use the squeeze command, the space used by the moved or deleted configuration files cannot be used by other files. Rewriting flash memory space during the squeeze operation may take several minutes. We recommend using this command during scheduled maintenance periods or off-peak hours.
•TFTP—When an external TFTP server is the storage location, you can create additional configuration files that can be applied per phone type or per individual phone. Up to five user and network locales can be used in these configuration files. To store configuration files on an external TFTP server, use the cnf-file location tftp url command.
You can then specify one of the following ways to create configuration files:
•Per system—This is the default. All phones use a single configuration file. The default user and network locale in a single configuration file are applied to all phones in the Cisco Unified CME system. Multiple locales and user-defined locales are not supported. To use the per-system option, either do not use the cnf-file command or use the no cnf-file command to reset the option from a different configuration.
•Per phone type—This setting creates separate configuration files for each phone type. For example, all Cisco Unified IP Phone 7960s use XMLDefault7960.cnf.xml, and all Cisco Unified IP Phone 7905s use XMLDefault7905.cnf.xml. All phones of the same type use the same configuration file, which is generated using the default user and network locale. To create configuration files per phone type, use the cnf-file perphonetype command. This option is not supported if you store the configuration files in the system location.
•Per phone—This setting creates a separate configuration file for each phone, by MAC address. For example, a Cisco Unified IP Phone 7960 with the MAC address 123.456.789 creates the per-phone configuration file SEP123456789.cnf.xml. The configuration file for a phone generates with the default user and network locale unless a different user and network locale is applied to the phone using an ephone template. To create configuration files per phone type, use the cnf-file perphone command. This option is not supported if you store the configuration files in the system location.
For configuration information, see the "SCCP: Defining Per-Phone Configuration Files and Alternate Location" section.
Redundant Cisco Unified CME Router
A second Cisco Unified CME router can be configured to provide call-control services if the primary Cisco Unified CME router fails. The secondary Cisco Unified CME router takes over and provides services seamlessly until the primary router becomes operational again.
When a phone registers to the primary router, it receives a configuration file from the primary router. Along with other information, the configuration file contains the IP addresses of the primary and secondary Cisco Unified CME routers. The phone uses these addresses to initiate a keepalive (KA) message to each router. The phone sends a KA message after every KA interval (30 seconds by default) to the router with which it is registered and after every two KA intervals (60 seconds by default) to the other router. The KA interval can be adjusted with the keepalive command.
If the primary router fails, a phone will not receive an acknowledgment (ACK) to its KA message to the primary router. If the phone does not get an ACK from the primary router for three consecutive KAs, it registers with the secondary Cisco Unified CME router.
During the time that the phone is registered to the secondary router, it keeps sending a KA probe to the primary router to see if it has come back up, now every 60 seconds by default or two times the normal KA interval. After the primary Cisco Unified CME router is operating normally, the phone starts receiving ACKs for its probes. After the phone receives ACKs from the primary router for three consecutive probes, it switches back to the primary router and reregisters with it. The reregistration of phones with the primary router is also called rehoming.
The physical setup for redundant Cisco Unified CME routers is as follows. The FXO line from the PSTN is split using a splitter. From the splitter, one line goes to the primary Cisco Unified CME router and the other goes to the secondary Cisco Unified CME router. When a call comes in on the FXO line, it is presented to both the primary and secondary Cisco Unified CME routers. The primary router is configured by default to answer the call immediately. The secondary Cisco Unified CME router is configured to answer the call after three rings using the voice-port ring number 3 command. If the primary router is operational, it answers the call immediately and changes the call state so that the secondary router does not try to answer it. If the primary router is unavailable and does not answer the call, the secondary router sees the new call coming in and answers after three rings.
The secondary Cisco Unified CME router should be connected in some way on the LAN, either through the same switch or through another switch that may or may not be connected to the primary Cisco Unified CME router directly. As long as both routers and the phones are connected on the LAN with the appropriate configurations in place, the phones can register to whichever router is active.
Configure primary and secondary Cisco Unified CME routers identically, with the exception that the FXO voice port from the PSTN on the secondary router should be configured to answer after more rings than the primary router, as previously explained. The ip source-address command is used on both routers to specify the IP addresses of the primary and secondary routers.
Timeouts
The following system-level timeout parameters have default values that are generally adequate:
•Busy Timeout—Amount of time that can elapse after a transferred call reaches a busy signal before the call is disconnected.
•Interdigit Timeout—Amount of time that can elapse between the receipt of individual dialed digits before the dialing process times out and is terminated. If the timeout ends before the destination is identified, a tone sounds and the call ends. This value is important when using variable-length dial-peer destination patterns (dial plans). For more information, see Dial Peer Configuration on Voice Gateway Routers.
•Ringing Timeout—Amount of time a phone can ring with no answer before returning a disconnect code to the caller. This timeout is used only for extensions that do not have no-answer call forwarding enabled. The ringing timeout prevents hung calls received over interfaces such as FXO that do not have forward-disconnect supervision.
•Keepalive—Interval determines how often a message is sent between the router and Cisco Unified IP phones, over the session to ensure that the keepalive timeout is not exceeded. If no other traffic is sent over the session during the interval, a keepalive message is sent.
How to Configure System-Level Parameters
• Configuring Bulk Registration (optional)
SCCP
• SCCP: Setting Up Cisco Unified CME (required)
• SCCP: Setting Date and Time Parameters (required)
• SCCP: Blocking Automatic Registration (optional)
• SCCP: Defining Per-Phone Configuration Files and Alternate Location (optional)
• SCCP: Changing Defaults for Time Outs (optional)
• SCCP: Configuring a Redundant Router (optional)
SIP
• SIP: Setting Up Cisco Unified CME (required)
• SIP: Setting Date and Time Parameters (required)
• SIP: Setting Network Time Protocol (required)
• SIP: Changing Session-Level Application for SIP Phones (optional)
Configuring Bulk Registration
To configure bulk registration for registering a block of phone numbers with an external registrar so that calls can be routed to Cisco Unified CME from a SIP network, follow the steps in this section.
Numbers that match the defined number pattern can register with the external registrar. The block of numbers that is registered can include any phone that is attached to Cisco Unified CME using SIP or SCCP, or any analog phone that is directly attached to an FXS port on a Cisco Unified CME router.
Note To specify that an individual directory number not register with the external registrar by using this command. For configuration information, see the "SIP: Disabling SIP Proxy Registration for a Directory Number" section on page 192.
Prerequisites
Cisco Unified CME 3.4 or a later version.
SUMMARY STEPS
1. enable
2. configure terminal
3. voice register global
4. mode cme
5. bulk number
6. exit
7. sip-ua
8. registrar {dns:address | ipv4:destination-address} expires seconds [tcp] [secondary] no registrar [secondary]
9. end
DETAILED STEPS
| |
Command or Action
|
Purpose
|
Step 1
|
enable
Example:
Router> enable
|
Enables privileged EXEC mode.
•Enter your password if prompted.
|
Step 2
|
configure terminal
Example:
Router# configure terminal
|
Enters global configuration mode.
|
Step 3
|
voice register global
Example:
Router(config)# voice register global
|
Enters voice register global configuration mode to set parameters for all supported SIP phones in Cisco Unified CME.
|
Step 4
|
mode cme
Example:
Router(config-register-global)# mode cme
|
Enables mode for provisioning SIP phones in Cisco Unified CME.
|
Step 5
|
bulk number
Example:
Router(config-register-global)# bulk 408526....
|
Sets bulk registration for E.164 numbers that will register with SIP proxy server.
•number—Unique sequence of up to 32 characters including wild cards and patterns that represents E.164 n umbers that will register with Sip proxy server.
|
Step 6
|
exit
Example:
Router(config-register-pool)# exit
|
Exits configuration mode to the next highest mode in the configuration mode hierarchy.
|
Step 7
|
sip-ua
Example:
Router(config)# sip-ua
|
Enters Session Initiation Protocol (SIP) user agent (ua) configuration mode for configuring the user agent.
|
Step 8
|
registrar {dns:address |
ipv4:destination-address} expires seconds [tcp]
[secondary] no registrar [secondary]
Example:
Router(config-sip-ua)# registrar server
ipv4:1.5.49.240
|
Enables SIP gateways to register E.164 numbers with SIP proxy server.
|
Step 9
|
end
Example:
Router(config-sip-ua)# end
|
Exits configuration mode and enters privileged EXEC mode.
|
Examples
The following example shows that all phone numbers that match the pattern "408555.." can register with a SIP proxy server (IP address 1.5.49.240):
voice register global
mode cme
bulk 408555....
sip-ua
registrar ipv4:1.5.49.240
SCCP: Setting Up Cisco Unified CME
To identify filenames and location of phone firmware for phone types to be connected, specify the port for phone registration, and specify number of phones and directory numbers to be supported, perform the following steps.
SUMMARY STEPS
1. enable
2. configure terminal
3. tftp-server flash:filename
4. telephony-service
5. load phone-type firmware-file
6. max-ephones max-phones
7. max-dn max-directory-numbers [preference preference-order] [no-reg primary | both]
8. ip source-address ip-address port port [any-match | strict-match]
9. end
DETAILED STEPS
| |
Command or Action
|
Purpose
|
Step 1
|
enable
Example:
Router> enable
|
Enables privileged EXEC mode.
•Enter your password if prompted.
|
Step 2
|
configure terminal
Example:
Router# configure terminal
|
Enters global configuration mode.
|
Step 3
|
tftp-server flash:filename
Example:
Router(config)# tftp-server
flash:P00307020300.bin
|
Permits IP phones served by the Cisco Unified CME router to access the specified file in flash memory.
•A separate tftp-server flash command is required for each phone type.
|
Step 4
|
telephony-service
Example:
Router(config)# telephony-service
|
Enters telephony-service configuration mode.
|
Step 5
|
load phone-type firmware-file
Example:
Router(config-telephony)# load 7960-7940
P00307020300
|
Identifies a Cisco Unified IP phone firmware file to be used by phones of the specified type when they register.
•A separate load command is required for each phone type.
Note If you are loading a firmware file larger than 384 KB, you must first load a file for that phone type that is smaller than 384 KB, then load the larger file.
|
Step 6
|
max-ephones max-phones
Example:
Router(config-telephony)# max-ephones 24
|
Limits number of phones to be supported by this router.
•Maximum number is platform and version-specific. Type? for value.
|
Step 7
|
max-dn max-directory-numbers [preference
preference-order] [no-reg primary | both]
Example:
Router(config-telephony)# max-dn 200 no-reg
primary
|
Limits number of directory numbers to be supported by this router.
•Maximum number is platform and version-specific. Type? for value.
|
Step 8
|
ip source-address ip-address [port port] [any-match
| strict-match]
Example:
Router(config-telephony)# ip source-address
10.16.32.144
|
Identifies the IP address and port number that the Cisco Unified CME router uses for IP phone registration.
•port port—(Optional) TCP/IP port number to use for SCCP. Range is 2000 to 9999. Default is 2000.
•any-match—(Optional) Disables strict IP address checking for registration. This is the default.
•strict-match—(Optional) Instructs the router to reject IP phone registration attempts if the IP server address used by the phone does not exactly match the source address.
|
Step 9
|
end
Example:
Router(config-telephony)# end
|
Returns to privileged EXEC mode.
|
SCCP: Setting Date and Time Parameters
To specify the format of the date and time that appears on all SCCP phones in Cisco Unified CME, follow the steps in this section.
SUMMARY STEPS
1. enable
2. configure terminal
3. telephony-service
4. date-format {mm-dd-yy | dd-mm-yy | yy-dd-mm | yy-mm-dd}
5. time-format {12 | 24}
6. time-zone number
7. end
DETAILED STEPS
| |
Command or Action
|
Purpose
|
Step 1
|
enable
Example:
Router> enable
|
Enables privileged EXEC mode.
•Enter your password if prompted.
|
Step 2
|
configure terminal
Example:
Router# configure terminal
|
Enters global configuration mode.
|
Step 3
|
telephony-service
Example:
Router(config)# telephony-service
|
Enters telephony-service configuration mode.
|
Step 4
|
date-format {mm-dd-yy | dd-mm-yy | yy-dd-mm |
yy-mm-dd}
Example:
Router(config-telephony)# date-format yy-dd-mm
|
(Optional) Sets the date format for phone display.
•Default: mm-dd-yy.
|
Step 5
|
time-format {12 | 24}
Example:
Router(config-telephony)# time-format 24
|
(Optional) Selects a 12 or 24-hour clock for the time display format on phone display.
•Default: 12.
|
Step 6
|
time-zone number
Example:
Router(config-telephony)# time-zone 2
|
Sets time zone used for all SCCP phones.
•Required for Cisco Unified IP Phone 7970G and 7971G-GE.
•Default: 5, Pacific Standard/Daylight Time (-480).
|
Step 7
|
end
Example:
Router(config-telephony)# end
|
Returns to privileged EXEC mode.
|
SCCP: Blocking Automatic Registration
To prevent Cisco Unified IP phones that are not explicitly configured in Cisco Unified CME from registering with the Cisco Unified CME router, perform the following steps.
Prerequisite
Cisco Unified CME 4.0 or a later version.
SUMMARY STEPS
1. enable
2. configure terminal
3. telephony-service
4. auto-reg-ephone
5. end
DETAILED STEPS
| |
Command or Action
|
Purpose
|
Step 1
|
enable
Example:
Router> enable
|
Enables privileged EXEC mode.
•Enter your password if prompted.
|
Step 2
|
configure terminal
Example:
Router# configure terminal
|
Enters global configuration mode.
|
Step 3
|
telephony-service
Example:
Router(config)# telephony-service
|
Enters telephony-service configuration mode.
|
Step 4
|
auto-reg-ephone
Example:
Router(config-telephony)# no auto-reg-ephone
|
Enables all Cisco Unified IP phones that are running SCCP to register regardless of whether the phone is explicitly configured in Cisco Unified CME.
•Default: Enabled
|
Step 5
|
end
Example:
Router(config-telephony)# end
|
Returns to privileged EXEC mode.
|
SCCP: Defining Per-Phone Configuration Files and Alternate Location
To define a location other than system for storing configuration files and to specify what type of configuration files to generate, perform the following steps. To use multiple network and user locales, or user-defined locales, you must define per-phone or per-phone type configuration files
Prerequisites
Cisco Unified CME 4.0 or a later version.
Restrictions
•Externally stored and per-phone configuration files are not supported on the Cisco Unified IP Phone 7902G, 7910, 7910G, or 7920, or the Cisco Unified IP Conference Station 7935 and 7936.
•TFTP does not support file deletion. When configuration files are updated, they overwrite any existing configuration files with the same name. If you change the configuration file location, files are not deleted from the TFTP server.
•Generating configuration files on flash or slot 0 can take up to a minute, depending on the number of files being generated.
•For smaller routers such as Cisco 2600 series routers, you must manually enter the squeeze command to erase files after changing the configuration file location or entering any commands that trigger the deletion of configuration files. Unless you use the squeeze command, the space used by the moved or deleted configuration files is not usable by other files.
SUMMARY STEPS
1. enable
2. configure terminal
3. telephony-service
4. cnf-file location {flash: | slot0: | tftp tftp-url}
5. cnf-file {perphonetype | perphone}
6. end
DETAILED STEPS
| |
Command or Action
|
Purpose
|
Step 1
|
enable
Example:
Router> enable
|
Enables privileged EXEC mode.
•Enter your password if prompted.
|
Step 2
|
configure terminal
Example:
Router# configure terminal
|
Enters global configuration mode.
|
Step 3
|
telephony-service
Example:
Router(config)# telephony-service
|
Enters telephony-service configuration mode.
|
Step 4
|
cnf-file location {flash: | slot0: | tftp
tftp-url}
Example:
Router(config-telephony)# cnf-file location
flash:
|
Specifies a location other than system:/its for storing phone configuration files.
•Required for per-phone or per-phone type configuration files.
|
Step 5
|
cnf-file {perphonetype | perphone}
Example:
Router(config-telephony)# cnf-file perphone
|
Specifies whether to use a separate file for each type of phone or for each individual phone.
|
Step 6
|
end
Example:
Router(config-telephony)# end
|
Returns to privileged EXEC mode.
|
What to Do Next
If you changed the configuration file storage location, use the option 150 ip command to update the address. See "Changing the TFTP Address on a DHCP Server" on page 127.
SCCP: Changing Defaults for Time Outs
To configure values for system-level intervals for which default values are typically adequate, perform the following steps:
SUMMARY STEPS
1. enable
2. configure terminal
3. telephony-service
4. timeouts busy seconds
5. timeouts interdigit seconds
6. timeouts ringing seconds
7. keepalive seconds
8. end
DETAILED STEPS
| |
Command or Action
|
Purpose
|
Step 1
|
enable
Example:
Router> enable
|
Enables privileged EXEC mode.
•Enter your password if prompted.
|
Step 2
|
configure terminal
Example:
Router# configure terminal
|
Enters global configuration mode.
|
Step 3
|
telephony-service
Example:
Router(config)# telephony-service
|
Enters telephony-service configuration mode.
|
Step 4
|
timeouts busy seconds
Example:
Router(config-telephony)# timeouts busy 20
|
(Optional) Sets the amount of time after which calls that are transferred to busy destinations are disconnected.
•seconds—Number of seconds. Range is 0 to 30. Default is 10.
|
Step 5
|
timeouts interdigit seconds
Example:
Router(config-telephony)# timeouts interdigit
30
|
(Optional) Configures the interdigit timeout value for all Cisco Unified IP phones attached to the router.
•seconds—Number of seconds before the interdigit timer expires. Range is 2 to 120. Default is 10.
|
Step 6
|
timeouts ringing seconds
Example:
Router(config-telephony)# timeouts ringing 30
|
(Optional) Sets the duration, in seconds, for which the Cisco Unified CME system allows ringing to continue if a call is not answered. Range is 5 to 60000. Default is 180.
|
Step 7
|
keepalive seconds
Example:
Router(config-telephony)# keepalive 45
|
(Optional) Sets the time interval, in seconds, between keepalive messages that are sent to the router by Cisco Unified IP phones.
•The default is usually adequate. If the interval is set too large, it is possible that notification will be delayed when a system goes down.
•Range: 10 to 65535. Default: 0.
|
Step 8
|
end
Example:
Router(config-telephony)# end
|
Returns to privileged EXEC mode.
|
SCCP: Configuring a Redundant Router
To configure a secondary Cisco Unified CME router to act as a backup if the primary router fails, perform the following steps on both the primary and secondary Cisco Unified CME routers.
Prerequisites
•Cisco Unified CME 4.0 or a later version.
•The secondary router must have a running configuration identical to that of the primary router.
•The physical configuration of the secondary router must be as described in the "Redundant Cisco Unified CME Router" section.
•Phones that use this feature must be configured with the type command, which guarantees that the appropriate phone configuration file will be present.
SUMMARY STEPS
1. enable
2. configure terminal
3. telephony-service
4. ip source-address ip-address port port [secondary ip-address [rehome seconds]] [any-match | strict-match]
5. exit
6. voice-port slot-number/port
7. signal ground-start
8. incoming alerting ring-only
9. ring number number
10. end
DETAILED STEPS
| |
Command or Action
|
Purpose
|
Step 1
|
enable
Example:
Router> enable
|
Enables privileged EXEC mode.
•Enter your password if prompted.
|
Step 2
|
configure terminal
Example:
Router# configure terminal
|
Enters global configuration mode.
|
Step 3
|
telephony-service
Example:
Router(config)# telephony-service
|
Enters telephony-service configuration mode.
|
Step 4
|
ip source-address ip-address [port port] [secondary
ip-address [rehome seconds]] [any-match |
strict-match]
Example:
Router(config-telephony)# ip source-address
10.0.0.1 secondary 10.2.2.25
|
Identifies the IP address and port number that the Cisco Unified CME router uses for IP phone registration.
•ip-address—Address of the primary Cisco Unified CME router.
•port port—(Optional) TCP/IP port number to use for SCCP. Range is 2000 to 9999. Default is 2000.
•secondary ip-address—Indicates a backup Cisco Unified CME router.
•rehome seconds—Not used by Cisco Unified CME. Used only by phones registered to Cisco Unified SRST.
•any-match—(Optional) Disables strict IP address checking for registration. This is the default.
•strict-match—(Optional) Router rejects IP phone registration attempts if the IP server address used by the phone does not exactly match the source address.
|
Step 5
|
exit
Example:
Router(config-telephony)# exit
|
Exits telephony-service configuration mode.
|
Step 6
|
voice-port slot-number/port
Example:
Router(config)# voice-port 2/0
|
Enters voice-port configuration mode for the FXO voice port for DID calls from the PSTN.
|
Step 7
|
signal ground-start
Example:
Router(config-voiceport)# signal ground-start
|
Specifies ground-start signaling for a voice port.
|
Step 8
|
incoming alerting ring-only
Example:
Router(config-voiceport)# incoming alerting
ring-only
|
Instructs the FXO ground-start voice port to detect incoming calls by detecting incoming ring signals.
|
Step 9
|
ring number number
Example:
Router(config-voiceport)# ring number 3
|
(Required only for the secondary router) Sets the maximum number of rings to be detected before answering an incoming call over an FXO voice port.
•number—Number of rings detected before answering the call. Range is 1 to 10. Default is 1.
Note For an incoming FXO voice port on a secondary Cisco Unified CME router, set this value higher than is set on the primary router. We recommend setting this value to 3 on the secondary router.
|
Step 10
|
end
Example:
Router(config-voiceport)# end
|
Returns to privileged EXEC mode.
|
SIP: Setting Up Cisco Unified CME
To identify filenames and location of phone firmware for phone types to be connected, specify the port for phone registration, and specify the number of phones and directory numbers to be supported, perform the following steps.
Note If your Cisco Unified CME system supports SCCP and SIP phones, do not connect your SIP phones to your network until after you have verified the configuration profile for the SIP phone.
Prerequisites
•Cisco CME 3.4 or a later version.
Restrictions
•SIP endpoints are not supported on H.323 trunks. SIP endpoints are supported on SIP trunks only.
•Certain Cisco Unified IP phones, such as the Cisco Unified IP Phone 7911G, 7941G, 7941GE, 7961G, 7961GE, 7970G, and 7971GE, are supported only in Cisco Unified CME 4.1 and later.
SUMMARY STEPS
1. enable
2. configure terminal
3. voice register global
4. mode cme
5. source-address ip-address
6. load phone-type firmware-file
7. tftp path {system: | flash: | slot0: | tftp tftp-url}
8. max-pool max-phones
9. max-dn max-directory-numbers
10. authenticate [all] [realm string]
11. end
DETAILED STEPS
| |
Command or Action
|
Purpose
|
Step 1
|
enable
Example:
Router> enable
|
Enables privileged EXEC mode.
•Enter your password if prompted.
|
Step 2
|
configure terminal
Example:
Router# configure terminal
|
Enters global configuration mode.
|
Step 3
|
voice register global
Example:
Router(config)# voice register global
|
Enters voice register global configuration mode to set parameters for all supported SIP phones in Cisco Unified CME.
|
Step 4
|
mode cme
Example:
Router(config-register-global)# mode cme
|
Enables mode for provisioning SIP phones in Cisco Unified CME.
|
Step 5
|
source-address ip-address [port port]
Example:
Router(config-register-global)# source-address
10.6.21.4
|
Enables the Cisco Unified CME router to receive messages from SIP phones through the specified IP address and port.
•port—(Optional) TCP/IP port number. Range: 2000 to 9999. Default: 2000.
|
Step 6
|
load phone-type firmware-file
Example:
Router(config-register-global)# load 7960-7940
P0S3-07-3-00
|
Associates a phone type with a phone firmware file.
•A separate load command is required for each phone type.
|
Step 7
|
tftp-path {system: | flash: | slot0: | tftp:
tftp-url}
Example:
Router(config-register-global)# tftp-path
http://mycompany.com/files
|
Defines the location from which the SIP phones will download configuration profile files.
•Default: system.
|
Step 8
|
max-pool max-phones
Example:
Router(config-register-global)# max-pool 10
|
Limits number of SIP phones to be supported by the Cisco Unified CME router.
•Default: 0.
|
Step 9
|
max-dn max-directory-numbers
Example:
Router(config-register-global)# max-dn 20
|
(Optional) Limits number of directory numbers for SIP phones to be supported by the Cisco Unified CME router.
•Default: 150 or maximum allowed on platform, by version. Type ? for value.
|
Step 10
|
authenticate [all][realm string]
Example:
Router(config-register-global)# authenticate
all realm company.com
|
(Optional) Enables authentication for registration requests in which the MAC address of the SIP phone cannot be identified by using other methods.
|
Step 11
|
end
Example:
Router(config-register-global)# end
|
Exits configuration mode and enters privileged EXEC mode.
|
SIP: Setting Date and Time Parameters
To specify the format of the date and time that appears on all SIP phones in Cisco Unified CME, follow the steps in this section.
Prerequisites
•Cisco CME 3.4 or a later version.
•The mode cme command is enabled.
SUMMARY STEPS
1. enable
2. configure terminal
3. voice register global
4. timezone number
5. date-format [d/m/d | m/d/y | y-d-m | y/d/m | y/m/d | yy-m-d]
6. time-format {12 | 24}
7. dst auto-adjust
8. end
DETAILED STEPS
| |
Command or Action
|
Purpose
|
Step 1
|
enable
Example:
Router> enable
|
Enables privileged EXEC mode.
•Enter your password if prompted.
|
Step 2
|
configure terminal
Example:
Router# configure terminal
|
Enters global configuration mode.
|
Step 3
|
voice register global
Example:
Router(config)# voice register global
|
Enters voice register global configuration mode to set parameters for all supported SIP phones in Cisco Unified CME.
|
Step 4
|
timezone number
Example:
Router(config-register-global)# timezone 8
|
Selects the time zone used for SIP phones in Cisco Unified CME.
•Default: 5, Pacific Standard/Daylight Time. Type ? to display a list of time zones.
|
Step 5
|
date-format [d/m/y | m/d/y | y-m-d | y/d/m |
y/m/d | yy-m-d]
Example:
Router(config-register-global)# date-format
yy-m-d
|
(Optional) Selects the date display format on SIP phones in Cisco Unified CME.
•Default: m-d-y.
|
Step 6
|
time-format {12 | 24}
Example:
Router(config-register-global)# time-format 24
|
(Optional) Selects the time display format on SIP phones in Cisco Unified CME.
•Default: 12.
|
Step 7
|
dst auto-adjust
Example:
Router(config-register-global)# dst auto-adjust
|
(Optional) Enables automatic adjustment of daylight savings time on SIP phones in Cisco Unified CME.
•To modify start and stop times for daylight savings time, use the dst command.
|
Step 8
|
dst {start | stop} month [day day-of-month |
week week-number | day day-of-week] time
hour:minutes
Example:
Router(config-register-global)# dst start jan
day 1 time 00:00
Router(config-register-global)# dst stop mar
day 31 time 23:59
|
(Optional) Sets the time period for daylight savings time on SIP phones in Cisco Unified CME.
•Required if automatic adjustment of daylight savings time is enabled by using the dst auto-adjust command.
•Default is Start: First week of April, Sunday, 2:00 a.m and Stop: Last week of October, Sunday 2:00 a.m.
|
Step 9
|
end
Example:
Router(config-register-global)# end
|
Exits configuration mode and enters privileged EXEC mode.
|
SIP: Setting Network Time Protocol
To enable NTP for Java-based phones, such as the Cisco Unified IP Phone 7911G, 7941G, 7941GE, 7961G, 7961GE, 7970G, and 7971GE, connected to Cisco Unified CME running SIP, perform this task.
Prerequisites
•Cisco Unified CME 4.1 or a later version.
•The firmware load 8.2(1) or a later version is installed for SIP phones to download. For upgrade information, see the "SIP: Upgrading or Downgrading Phone Firmware Between Versions" section on page 95.
SUMMARY STEPS
1. enable
2. configure terminal
3. voice register global
4. ntp-server ip-address [mode {anycast | directedbroadcast | multicast | unicast}]
5. end
DETAILED STEPS
| |
Command or Action
|
Purpose
|
Step 1
|
enable
Example:
Router> enable
|
Enables privileged EXEC mode.
•Enter your password if prompted.
|
Step 2
|
configure terminal
Example:
Router# configure terminal
|
Enters global configuration mode.
|
Step 3
|
voice register global
Example:
Router(config)# voice register global
|
Enters voice register global configuration mode to set global parameters for all supported SIP phones in a Cisco Unified CME environment.
|
Step 4
|
ntp-server ip-address [mode {anycast |
directedbroadcast | multicast | unicast}]
Example:
Router(config-register-global)# ntp-server 10.1.2.3
|
Clock on this router is synchronized with the specified NTP server.
|
Step 5
|
end
Example:
Router(config-register-global)# end
|
Returns to privileged EXEC mode.
|
SIP: Changing Session-Level Application for SIP Phones
To change a the default session-level application for all SIP phones, perform the following steps.
Prerequisites
•Cisco CME 3.4 or a later version.
SUMMARY STEPS
1. enable
2. configure terminal
3. voice register global
4. application application-name
5. end
DETAILED STEPS
| |
Command or Action
|
Purpose
|
Step 1
|
enable
Example:
Router> enable
|
Enables privileged EXEC mode.
•Enter your password if prompted.
|
Step 2
|
configure terminal
Example:
Router# configure terminal
|
Enters global configuration mode.
|
Step 3
|
voice register global
Example:
Router(config)# voice register global
|
Enters voice register global configuration mode to set parameters for all supported SIP phones in Cisco Unified CME.
|
Step 4
|
application application-name
Example:
Router(config-register-global)# application
sipapp2
|
(Optional) Changes the default application for all dial peers associated with the SIP phones in Cisco Unified CME to the specified application.
Note The application command in voice register pool configuration mode takes precedence over this command in voice register global configuration mode.
|
Step 5
|
end
Example:
Router(config-register-global)# end
|
Exits configuration mode and enters privileged EXEC mode.
|
Configuration Examples for System-Level Parameters
This section contains the following examples:
• System-Level Parameters: Example
• Blocking Automatic Registration: Example
• Redundant Router: Example
System-Level Parameters: Example
The following example shows the system-level configuration for a Cisco Unified CME that can support up to 500 directory numbers on 100 phones. It sets up TFTP file sharing for phone firmware files for Cisco Unified IP Phone 7905, 7912, 7914, 7920, 7940, and 7960 phone types and loads those files.
tftp-server flash:ATA030100SCCP040211A.zup
! ATA 186/188 firmware
tftp-server flash:CP7902080001SCCP051117A.sbin
! 7902 firmware
tftp-server flash:CP7905080001SCCP051117A.sbin
! 7905 firmware
tftp-server flash:CP7912080001SCCP051117A.sbin
! 7912 firmware
tftp-server flash:cmterm_7920.4.0-02-00.bin
! 7914 firmware
tftp-server flash:P00503010100.bin
! 7920 firmware
tftp-server flash:S00104000100.sbn
! 7935 firmware
tftp-server flash:cmterm_7936.3-3-5-0.bin
! 7936 firmware
tftp-server flash:P0030702T023.bin
tftp-server flash:P0030702T023.loads
tftp-server flash:P0030702T023.sb2
! 7960/40 firmware
!
telephony-service
max-ephones 100
max-dn 500
load ata ATA030100SCCP040211A
load 7902 CP7902080001SCCP051117A
load 7905 CP7905080001SCCP051117A
load 7912 CP7912080001SCCP051117A
load 7914 S00104000100
load 7920 cmterm_7920.4.0-02-00
load 7935 P00503010100
load 7936 cmterm_7936.3-3-5-0
load 7960-7940 P0030702T023
ip source-address 10.16.32.144 port 2000
create cnf-files version-stamp Jan 01 2002 00:00:00
transfer-system full-consult
Cisco Unified IP Phone 7911, 7941, 7941-GE, 7961, 7961-GE, 7970, and 7971 require multiple files to be shared using TFTP. The following configuration example adds support for these phones.
tftp-server flash:SCCP11.7-2-1-0S.loads
tftp-server flash:term11.default.loads
tftp-server flash:apps11.1-0-0-72.sbn
tftp-server flash:cnu11.3-0-0-81.sbn
tftp-server flash:cvm11.7-2-0-66.sbn
tftp-server flash:dsp11.1-0-0-73.sbn
tftp-server flash:jar11.7-2-0-66.sbn
! 7911 firmware
!
tftp-server flash:TERM41.7-0-3-0S.loads
tftp-server flash:TERM41.DEFAULT.loads
tftp-server flash:TERM61.DEFAULT.loads
tftp-server flash:CVM41.2-0-2-26.sbn
tftp-server flash:cnu41.2-7-6-26.sbn
tftp-server flash:Jar41.2-9-2-26.sbn
! 7941/41-GE, 7961/61-GE firmware
!
tftp-server flash:TERM70.7-0-1-0s.LOADS
tftp-server flash:TERM70.DEFAULT.loads
tftp-server flash:TERM71.DEFAULT.loads
tftp-server flash:CVM70.2-0-2-26.sbn
tftp-server flash:cnu70.2-7-6-26.sbn
tftp-server flash:Jar70.2-9-2-26.sbn
! 7970/71 firmware
!
telephony-service
load 7911 SCCP11.7-2-1-0S
load 7941 TERM41.7-0-3-0S
load 7961 TERM41.7-0-3-0S
load 7941GE TERM41.7-0-3-0S
load 7961GE TERM41.7-0-3-0S
load 7970 TERM70.7-0-1-0s
load 7971 TERM70.7-0-1-0s
create cnf-files version-stamp Jan 01 2002 00:00:00
.
.
.
Blocking Automatic Registration: Example
The following example shows how to disable automatic ephone registration, display a log of attempted registrations, and then clear the log.
Router(config)# telephony-service
Router(config-telephony)# no auto-reg-ephone
Router(config-telephony)# exit
Router(config)# exit
Router# show ephone attempted-registrations
Attempting Mac address:
Num Mac Address DateTime DeviceType
-----------------------------------------------------------------------------
1 C863.8475.5417 22:52:05 UTC Thu Apr 28 2005 SCCP Gateway (AN)
2 C863.8475.5408 22:52:05 UTC Thu Apr 28 2005 SCCP Gateway (AN)
.....
25 000D.28D7.7222 22:26:32 UTC Thu Apr 28 2005 Telecaster 7960
26 000D.BDB7.A9EA 22:25:59 UTC Thu Apr 28 2005 Telecaster 7960
...
47 C863.94A8.D40F 22:52:17 UTC Thu Apr 28 2005 SCCP Gateway (AN)
48 C863.94A8.D411 22:52:18 UTC Thu Apr 28 2005 SCCP Gateway (AN)
49 C863.94A8.D400 22:52:15 UTC Thu Apr 28 2005 SCCP Gateway (AN)
Router# clear telephony-service ephone-attempted-registrations
Redundant Router: Example
The following example is configured on the primary Cisco Unified CME router. It establishes the router at 10.5.2.78 as a secondary router. The voice port 3/0/0 is the FXO port for incoming calls from the PSTN. It is set to use ground-start signaling and detect incoming calls by counting incoming ring signals.
telephony-service
ip source-address 10.0.0.1 port 2000 secondary 10.5.2.78
voice-port 3/0/0
signal ground-start
incoming alerting ring-only
The secondary Cisco Unified CME router is configured with the same commands, except that the ring number command is set to 3 instead of using the default of 1.
telephony-service
ip source-address 10.0.0.1 port 2000 secondary 10.5.2.78
voice-port 3/0/0
signal ground-start
incoming alerting ring-only
ring number 3
Where to Go Next
After configuring system-level parameters, you are ready to configure phones in Cisco Unified CME for making basic calls. See "Configuring Phones to Make Basic Calls" on page 165.
Additional References
The following sections provide references related to Cisco Unified CME features.
Related Documents
Technical Assistance
Description
|
Link
|
The Cisco Support website provides extensive online resources, including documentation and tools for troubleshooting and resolving technical issues with Cisco products and technologies. Access to most tools on the Cisco Support website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a user ID or password, you can register on Cisco.com.
|
http://www.cisco.com/techsupport
|
Feature Information for System-Level Parameters
Table 10 lists the features in this module and enhancements to the features by version.
To determine the correct Cisco IOS release to support a specific Cisco Unified CME version, see the Cisco Unified CME and Cisco IOS Software Version Compatibility Matrix at http://www.cisco.com/en/US/products/sw/voicesw/ps4625/products_documentation_roadmap09186a0080189132.html.
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Note Table 10 lists the Cisco Unified CME version that introduced support for a given feature. Unless noted otherwise, subsequent versions of Cisco Unified CME software also support that feature.
Table 10 Feature Information for System-Level Parameters
Feature Name
|
Cisco Unified CME
Versions
|
Feature Information
|
Blocking Automatic Registration
|
4.0
|
IP phones that are not explicitly configured in Cisco Unified CME are blocked from registering.
|
Bulk Registration
|
3.4
|
Bulk registration for registering a block of phone numbers with an external registrar was introduced.
|
Network Time Protocol for SIP Phones
|
4.1
|
SIP phones can synchronize to an NTP server.
|
Per-Phone Configuration Files and Alternate Location
|
4.0
|
Defines a location other than system for storing configuration files and specifies the type of configuration files to generate.
|
Redundant Router
|
4.0
|
Redundant router capability was introduced.
|
SIP phones in Cisco Unified CME
|
3.4
|
Support for SIP endpoints directly connected to Cisco Unified CME was introduced.
|
