Cisco Unified Communications Manager Express System Administrator Guide
Defining Network Parameters
Downloads: This chapterpdf (PDF - 458.0KB) The complete bookPDF (PDF - 16.04MB) | Feedback

Table of Contents

Defining Network Parameters

Contents

Prerequisites for Defining Network Parameters

Restrictions for Defining Network Parameters

Information About Defining Network Parameters

DHCP Service

Network Time Protocol for the Cisco Unified CME Router

Olson Timezones

DTMF Relay

SIP Register Support

Out-of-Dialog REFER

How to Define Network Parameters

Enabling Calls in Your VoIP Network

Restrictions

Defining DHCP

Defining a Single DHCP IP Address Pool

Defining a Separate DHCP IP Address Pool for Each DHCP Client

Defining a DHCP Relay

Enabling Network Time Protocol on the Cisco Unified CME Router

SCCP: Setting the Olson Timezone

Prerequisites

SIP: Setting the Olson Timezone

Prerequisites

Configuring DTMF Relay for H.323 Networks in Multisite Installations

What to Do Next

Configuring SIP Trunk Support

Verifying SIP Trunk Support Configuration

Changing the TFTP Address on a DHCP Server

Prerequisites

Restrictions

Enabling OOD-R

Prerequisites

Restrictions

Verifying OOD-R Configuration

Troubleshooting OOD-R

Configuration Examples for Network Parameters

NTP Server: Example

DTMF Relay for H.323 Networks: Example

OOD-R: Example

Where to Go Next

Additional References

Related Documents

Technical Assistance

Feature Information for Network Parameters

Defining Network Parameters

This chapter describes how to define parameters that enable Cisco Unified Communications Manager Express (Cisco Unified CME) to work with your network.

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 Network Parameters” section.

Prerequisites for Defining Network Parameters

  • IP routing must be enabled.
  • VoIP networking must be operational. For quality and security purposes, we recommend you have separate virtual LANs (VLANs) for data and voice. The IP network assigned to each VLAN should be large enough to support addresses for all nodes on that VLAN. Cisco Unified CME phones receive their IP addresses from the voice network, whereas all other nodes such as PCs, servers, and printers receive their IP addresses from the data network. For configuration information, see the “How to Configure VLANs on a Cisco Switch” section.
  • If applicable, PSTN lines are configured and operational.
  • If applicable, the WAN links are configured and operational.
  • Trivial File Transfer Protocol (TFTP) must be enabled on the router to allow IP phones to download phone firmware files.
  • To support IP phones that are running SIP to be directly connected to the Cisco Unified CME router, Cisco Unified CME 3.4 or later must be installed on the router. For installation information, see .
  • To provide voice-mail support for phones connected to the Cisco Unified CME router, install and configure voice mail on your network.

Restrictions for Defining Network Parameters

In Cisco Unified CME 4.0 and later versions, Layer-3-to-Layer-2 VLAN Class of Service (CoS) priority marking is not automatically processed. Cisco Unified CME 4.0 and later versions will continue to mark Layer 3, but Layer 2 marking is now only handled in the Cisco IOS software. Any Quality of Service (QoS) design that requires Layer 2 marking will have to be explicitly configured, either on a Catalyst switch that supports this capability or on the Cisco Unified CME router under the Ethernet interface configuration. For configuration information, see the Enterprise QoS Solution Reference Network Design Guide.

Information About Defining Network Parameters

To configure network parameters, you should understand the following concepts:

DHCP Service

When a Cisco Unified IP phone is connected to the Cisco Unified CME system, it automatically queries for a Dynamic Host Configuration Protocol (DHCP) server. The DHCP server responds by assigning an IP address to the Cisco Unified IP phone and providing the IP address of the TFTP server through DHCP option 150. Then the phone registers with the Cisco Unified CME server and attempts to get configuration and phone firmware files from the TFTP server.

For configuration information, perform only one of the following procedures to set up DHCP service for your IP phones:

Network Time Protocol for the Cisco Unified CME Router

Network Time Protocol (NTP) allows you to synchronize your Cisco Unified CME router to a single clock on the network, known as the clock master. NTP is disabled on all interfaces by default, but it is essential for Cisco Unified CME so you must ensure that it is enabled. For information about configuring NTP for the Cisco Unified CME router, see the “Enabling Network Time Protocol on the Cisco Unified CME Router” section.

Olson Timezones

Before Cisco Unified CME 9.0, some Cisco Unified SCCP IP phones and Cisco Unified SIP IP phones displayed exactly the same time as that of the Cisco Unified CME. For these phones, the correct time was displayed whenever the Cisco Unified CME time was set correctly. The clock timezone , clock summer-time , and clock set commands were the only commands used to set the Cisco Unified CME time correctly.

Other phones used only the time-zone command in telephony-service configuration mode and the timezone command in voice register global configuration mode to specify which time zone they were in so that the correct local time was displayed on Cisco Unified SCCP IP phones and Cisco Unified SIP IP phones, respectively. The phones calculated and displayed the time based on the Greenwich Mean Time (GMT) provided by the Cisco Unified CME or the Network Time Protocol server. The problem with this method is that every time a new country or new time zone was available or an old time zone was changed, the Cisco Unified CME time-zone and timezone commands and the phone loads had to be updated.

In Cisco Unified CME 9.0 and later versions, the Olson Timezone feature eliminates the need to update time zone commands or phone loads to accommodate a new country with a new time zone or an existing country whose city or state wants to change their time zone. Oracle’s Olson Timezone updater tool, tzupdater.jar, only needs to be current for you to set the correct time using the olsontimezone command in either telephony-service or voice register global configuration mode.

For Cisco Unified 3911 and 3951 SIP IP phones and Cisco Unified 6921, 6941, 6945, and 6961 SCCP and SIP IP phones, the correct Olson Timezone updater file is TzDataCSV.csv. The TzDataCSV.csv file is created based on the tzupdater.jar file.

To set the correct time zone, you must determine the Olson Timezone area/location where the Cisco Unified CME is located and download the latest tzupdater.jar or TzDataCSV.csv to a TFTP server that is accessible to the Cisco Unified CME, such as flash or slot 0.

After a complete reboot, the phone checks if the version of its configuration file is earlier or later than 2010o. If it is earlier, the phone loads the latest tzupdater.jar and uses that updater file to calculate the Olson Timezone.

To make the Olson Timezone feature backward compatible, both the time-zone and timezone commands are retained as legacy time zones. Because the olsontimezon e command covers approximately 500 time zones (Version 2010o of the tzupdater.jar file supports approximately 453 Olson Timezone IDs.), this command takes precedence when either the time-zone or the timezone command (that covers a total of 90 to 100 time zones only) is present at the same time as the olsontimezone command.

For more information on setting the time zone so that the correct local time is displayed on an IP phone, see the “SCCP: Setting the Olson Timezone” section or the “SIP: Setting the Olson Timezone” section.

DTMF Relay

IP phones connected to Cisco Unified CME systems require the use of out-of-band DTMF relay to transport DTMF (keypad) digits across VoIP connections. The reason for this is that the codecs used for in-band transport may distort DTMF tones and make them unrecognizable. DTMF relay solves the problem of DTMF tone distortion by transporting DTMF tones out-of-band, or separate, from the encoded voice stream.

For IP phones on H.323 networks, DTMF is relayed using the H.245 alphanumeric method, which is defined by the ITU H.245 standard. This method separates DTMF digits from the voice stream and sends them as ASCII characters in H.245 user input indication messages through the H.245 signaling channel instead of the RTP channel. For information about configuring a DTMF relay in a multisite installation, see the “Configuring DTMF Relay for H.323 Networks in Multisite Installations” section.

To use remote voice-mail or IVR applications on SIP networks from Cisco Unified CME phones, the DTMF digits used by the Cisco Unified CME phones must be converted to the RFC 2833 in-band DTMF relay mechanism used by SIP phones. The SIP DTMF relay method is needed in the following situations:

  • When SIP is used to connect a Cisco Unified CME system to a remote SIP-based IVR or voice-mail application.
  • When SIP is used to connect a Cisco Unified CME system to a remote SIP-PSTN voice gateway that goes through the PSTN to a voice-mail or IVR application.

The requirement for out-of-band DTMF relay conversion is limited to SCCP phones. SIP phones natively support in-band DTMF relay as specified in RFC 2833.

To use voice mail on a SIP network that connects to a Cisco Unity Express system, which uses a nonstandard SIP Notify format, the DTMF digits used by the Cisco Unified CME phones must be converted to the Notify format. Additional configuration may be required for backward compatibility with Cisco CME 3.0 and 3.1. For configuration information about enabling DTMF relay for SIP networks, see the “Configuring SIP Trunk Support” section.

SIP Register Support

SIP register support enables a SIP gateway to register E.164 numbers with a SIP proxy or SIP registrar, similar to the way that H.323 gateways can register E.164 numbers with a gatekeeper. SIP gateways allow registration of E.164 numbers to a SIP proxy or registrar on behalf of analog telephone voice ports (FXS) and IP phone virtual voice ports (EFXS) for local SCCP phones.

When registering E.164 numbers in dial peers with an external registrar, you can also register them with a secondary SIP proxy or registrar to provide redundancy. The secondary registration can be used if the primary registrar fails. For configuration information, see the “Basic SIP Configuration” chapter in the Cisco IOS SIP Configuration Guide .


NoteNo commands allow registration between the H.323 and SIP protocols.


By default, SIP gateways do not generate SIP Register messages, so the gateway must be configured to register the gateway’s E.164 telephone numbers with an external SIP registrar. For information about configuring the SIP gateway to register phone numbers with Cisco Unified CME, see the “Configuring SIP Trunk Support” section.


NoteWhen you configure SIP on a router, the ports on all its interfaces are open by default. This makes the router vulnerable to malicious attackers who can execute toll fraud across the gateway if the router has a public IP address and a public switched telephone network (PSTN) connection. To eliminate the threat, you should bind an interface to private IP address that is not accessible by untrusted hosts. In addition, you should protect any public or untrusted interface by configuring a firewall or an access control list (ACL) to prevent unwanted traffic from traversing the router.


Out-of-Dialog REFER

Out-of-dialog REFER (OOD-R) allows remote applications to establish calls by sending a REFER message to Cisco Unified CME without an initial INVITE. After the REFER is sent, the remainder of the call setup is independent of the application and the media stream does not flow through the application. The application using OOD-R triggers a call setup request that specifies the Referee address in the Request-URI and the Refer-Target in the Refer-To header. The SIP messaging used to communicate with Cisco Unified CME is independent of the end-user device protocol which can be SIP, SCCP, H.323, or POTS. Click-to-dial is an example of an application that can be created using OOD-R.

A click-to-dial application allows users to combine multiple steps into one click for a call setup. For example, a user can click a web-based directory application from their PC to look up a telephone number, off-hook their desktop phone, and dial the called number. The application initiates the call setup without the user having to out-dial from their own phone. The directory application sends a REFER message to Cisco Unified CME which sets up the call between both parties based on this REFER.

Figure 5-1 shows an example of OOD-R being used by a click-to-dial application. In this scenario, the following events occur (refer to the event numbers in the illustration):

1. Remote user clicks to dial.

2. Application sends out-of-dialog REFER to Cisco Unified CME 1.

3. Cisco Unified CME 1 connects to SIP phone 1 (Referee).

4. Cisco Unified CME 1 sends INVITE to Cisco Unified CME 2.

5. Cisco Unified CME 2 sends INVITE to SIP phone 2 (Refer-Target) and the call is accepted.

6. Voice path is created between the two SIP phones.

Figure 5-1 Click-to-Dial Application using Out-of-Dialog REFER

 

The initial OOD-R request can be authenticated and authorized using RFC 2617-based digest authentication. To support authentication, Cisco Unified CME retrieves the credential information from a text file stored in flash. This mechanism is used by Cisco Unified CME in addition to phone-based credentials. The same credential file can be shared by other services that require request-based authentication and authorization such as presence service. Up to five credential files can be configured and loaded into the system. The contents of these five files are mutually exclusive, meaning the username and password pairs must be unique across all the files. The username and password pairs must also be different than those configured for SCCP or SIP phones in a Cisco Unified CME system.

For configuration information, see the “Enabling OOD-R” section.

How to Define Network Parameters

This section contains the following tasks. You may not need to perform all of these procedures.

Enabling Calls in Your VoIP Network

To enable calls between endpoints in Cisco Unified CME, perform the following steps.

Restrictions

  • SIP endpoints are not supported on H.323 trunks. SIP endpoints are supported on SIP trunks only.
  • Cisco Unified CME 3.4 and later versions support Media Flow-through mode only; enabling SIP-to-SIP calls is required before you can successfully make SIP-to-SIP calls.
  • Media Flow-around configured with the media flow-around command is not supported by Cisco Unified CME with SIP phones.

SUMMARY STEPS

1. enable

2. configure terminal

3. voice service voip

4. allow-connections from - type to to - type

5. sip

6. registrar server [ expires [ max sec ] [ min sec ]

7. end

DETAILED STEPS

Command or Action
Purpose

Step 1

enable

 

Router> enable

Enables privileged EXEC mode.

  • Enter your password if prompted.

Step 2

configure terminal

 

Router# configure terminal

Enters global configuration mode.

Step 3

voice service voip

 

Router(config)# voice service voip

Enters voice service configuration mode and specifies Voice over IP (VoIP) encapsulation.

Step 4

allow-connections from - type to to - type

 

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

Router(config-voi-srv)# allow-connections h323 to SIP

Router(config-voi-srv)# allow-connections SIP to SIP

Enables calls between specific types of endpoints in a VoIP network.

  • A separate allow-connections command is required for each type of endpoint to be supported.

Step 5

sip

 

Router(config-voi-srv)# sip

(Optional) Enters SIP configuration mode.

  • Required if you are connecting IP phones running SIP directly in Cisco CME 3.4 and later.

Step 6

registrar server [ expires [ max sec ][ min sec ]]

 

Router(config-voi-sip)# registrar server expires max 600 min 60

(Optional) Enables SIP registrar functionality in Cisco Unified CME.

  • Required if you are connecting IP phones running SIP directly in Cisco CME 3.4 and later.

Note Cisco Unified CME does not maintain a persistent database of registration entries across reloads. Because SIP phones do not use a keepalive functionality, the SIP phones must register again. To decrease the amount of time after which the SIP phones register again, we recommend that you change the expiry.


  • max sec —(Optional) Range: 600 to 86400. Default: 3600. Recommended value: 600.

Note Ensure that the registration expiration timeout is set to a value smaller than the TCP connection aging timeout to avoid disconnection from the TCP.


  • min sec —(Optional) Range: 60 to 3600. Default: 60.

Step 7

exit

 

Router(config-voi-sip)# exit

Exits dial-peer configuration mode.

Step 8

sip-ua

 

Router(config)# sip-ua

Enters SIP user-agent configuration mode.

Step 9

notify telephone-event max-duration time

 

Router(config-sip-ua)# notify telephone-event max-duration 2000

Configures the maximum time interval allowed between two consecutive NOTIFY messages for a single DTMF event.

  • max-duration time —Range: 500 to 3000. Default: 2000.

Step 10

registrar { dns: host-name | ipv4: ip-address } expires seconds [ tcp ] [ secondary ]

 

Router(config-sip-ua)# registrar ipv4:10.8.17.40 expires 3600 secondary

Registers E.164 numbers on behalf of analog telephone voice ports (FXS) and IP phone virtual voice ports (EFXS) with an external SIP proxy or SIP registrar server.

Step 11

retry register number

 

Router(config-sip-ua)# retry register 10

Sets the total number of SIP Register messages that the gateway should send.

  • number —Number of Register message retries. Range: 1 to 10. Default: 10.

Step 12

timers register time

 

Router(config-sip-ua)# timers register 500

Sets how long the SIP user agent (UA) waits before sending Register requests.

  • time —Waiting time, in milliseconds. Range: 100 to 1000. Default: 500.

Step 13

end

 

Router(config-voi-sip)# end

Exits configuration mode and enters privileged EXEC mode.

Defining DHCP

To set up DHCP service for your DHCP clients, perform only one of the following procedures:

Defining a Single DHCP IP Address Pool

To create a shared pool of IP addresses for all DHCP clients, perform the following step.


NoteDonot perform this task if you already have a DHCP server on the LAN that can be used to provide addresses to the Cisco Unified CME phones. See the “Enabling Network Time Protocol on the Cisco Unified CME Router” section.


Prerequisites

Your Cisco Unified CME router is a DHCP server.

Restrictions

A single DHCP IP address pool cannot be used if non-IP-phone clients, such as PCs, must use a different TFTP server address.

SUMMARY STEPS

1. enable

2. configure terminal

3. ip dhcp pool pool-name

4. network ip-address [ mask | / prefix-length ]

5. option 150 ip ip-address

6. default-router ip-address

7. end

DETAILED STEPS

Command or Action
Purpose

Step 1

enable

 

Router> enable

Enables privileged EXEC mode.

  • Enter your password if prompted.

Step 2

configure terminal

 

Router# configure terminal

Enters global configuration mode.

Step 3

ip dhcp pool pool-name

 

Router(config)# ip dhcp pool mypool

Creates a name for the DHCP server address pool and enters DHCP pool configuration mode.

Step 4

network ip-address [ mask | / prefix-length ]

 
Router(config-dhcp)# network 10.0.0.0 255.255.0.0

Specifies the IP address of the DHCP address pool to be configured.

Step 5

option 150 ip ip-address

 
Router(config-dhcp)# option 150 ip 10.0.0.1

Specifies the TFTP server address from which the Cisco Unified IP phone downloads the image configuration file.

  • This is your Cisco Unified CME router’s address.

Step 6

default-router ip-address

 
Router(config-dhcp)# default-router 10.0.0.1

(Optional) Specifies the router that the IP phones will use to send or receive IP traffic that is external to their local subnet.

  • If the Cisco Unified CME router is the only router on the network, this address should be the Cisco Unified CME IP source address. This command can be omitted if IP phones need to send or receive IP traffic only to or from devices on their local subnet.
  • The IP address that you specify for default router will be used by the IP phones for fallback purposes. If the Cisco Unified CME IP source address becomes unreachable, IP phones will attempt to register to the address specified in this command.

Step 7

end

 

Router(config-dhcp)# end

Returns to privileged EXEC mode.

What to Do Next

Defining a Separate DHCP IP Address Pool for Each DHCP Client

To create a DHCP IP address pool for each DHCP client, including non-IP-phone clients such as PCs, perform the following steps.


NoteDonot perform this task if you already have a DHCP server on the LAN that can be used to provide addresses to the Cisco Unified CME phones. See the “Enabling Network Time Protocol on the Cisco Unified CME Router” section.


Prerequisites

Your Cisco Unified CME router is a DHCP server.

Restrictions

To use a separate DHCP IP address pool for each DHCP client, make an entry for each IP phone.

SUMMARY STEPS

1. enable

2. configure terminal

3. ip dhcp pool pool-name

4. host ip-address subnet-mask

5. client-identifier mac-address

6. option 150 ip ip-address

7. default-router ip-address

8. end

DETAILED STEPS

Command or Action
Purpose

Step 1

enable

 

Router> enable

Enables privileged EXEC mode.

  • Enter your password if prompted.

Step 2

configure terminal

 

Router# configure terminal

Enters global configuration mode.

Step 3

ip dhcp pool pool-name

 

Router(config)# ip dhcp pool pool2

Creates a name for the DHCP server address pool and enters DHCP pool configuration mode.

Step 4

host ip-address subnet-mask

 

Router(config-dhcp)# host 10.0.0.0 255.255.0.0

Specifies the IP address that you want the phone to get.

Step 5

client-identifier mac-address

 

Router(config-dhcp)# client-identifier 01238.380.3056

Specifies the MAC address of the phone, which is printed on a label on each Cisco Unified IP phone.

  • A separate client-identifier command is required for each DHCP client.
  • Add “01” prefix number before the MAC address.

Step 6

option 150 ip ip-address

 

Router(config-dhcp)# option 150 ip 10.0.0.1

Specifies the TFTP server address from which the Cisco Unified IP phone downloads the image configuration file.

  • This is your Cisco Unified CME router’s address.

Step 7

default-router ip-address

 
Router(config-dhcp)# default-router 10.0.0.1

(Optional) Specifies the router that the IP phones will use to send or receive IP traffic that is external to their local subnet.

  • If the Cisco Unified CME router is the only router on the network, this address should be the Cisco Unified CME IP source address. This command can be omitted if IP phones need to send or receive IP traffic only to or from devices on their local subnet.
  • The IP address that you specify for default router will be used by the IP phones for fallback purposes. If the Cisco Unified CME IP source address becomes unreachable, IP phones will attempt to register to the address specified in this command.

Step 8

end

 

Router(config-dhcp)# end

Returns to privileged EXEC mode.

What to Do Next

Defining a DHCP Relay

To set up DHCP relay on the LAN interface where the Cisco Unified IP phones are connected and enable the DHCP relay to relay requests from the phones to the DHCP server, perform the following steps.

Prerequisites

There is a DHCP server that is not on this Cisco Unified CME router on the LAN that can provide addresses to the Cisco Unified CME phones.

Restrictions

This Cisco Unified CME router cannot be the DHCP server.

SUMMARY STEPS

1. enable

2. configure terminal

3. service dhcp

4. interface type number

5. ip helper-address ip-address

6. end

DETAILED STEPS

Command or Action
Purpose

Step 1

enable

 

Router> enable

Enables privileged EXEC mode.

  • Enter your password if prompted.

Step 2

configure terminal

 

Router# configure terminal

Enters global configuration mode.

Step 3

service dhcp

 

Router(config)# service dhcp

Enables the Cisco IOS DHCP server feature on the router.

Step 4

interface type number

 

Router(config)# interface vlan 10

Enters interface configuration mode for the specified interface.

Step 5

ip helper-address ip-address

 

Router(config-if)# ip helper-address 10.0.0.1

Specifies the helper address for any unrecognized broadcast for TFTP server and DNS server requests.

  • A separate ip helper-address command is required for each server if the servers are on different hosts.
  • You can also configure multiple TFTP server targets by using the ip helper-address commands for multiple servers.

Step 6

end

 

Router(config-if)# end

Returns to privileged EXEC mode.

What to Do Next

Enabling Network Time Protocol on the Cisco Unified CME Router

To enable NTP for the Cisco Unified CME router, perform this task.

SUMMARY STEPS

1. enable

2. configure terminal

3. clock timezone zone hours-offset [ minutes-offset ]

4. clock summer-time zone recurring [ week day month hh : mm week day month hh : mm [ offset ]]

5. ntp server ip-address

6. end

DETAILED STEPS

Command or Action
Purpose

Step 1

enable

 

Router> enable

Enables privileged EXEC mode.

  • Enter your password if prompted.

Step 2

configure terminal

 

Router# configure terminal

Enters global configuration mode.

Step 3

clock timezone zone hours-offset [ minutes-offset ]

 

Router(config)# clock timezone pst -8

Sets the local time zone.

Step 4

clock summer-time zone recurring [ week day month hh : mm week day month hh : mm [ offset ]]

 

Router(config)# clock summer-time pdt recurring

(Optional) Specifies daylight savings time.

  • Default: summer time is disabled. If the clock summer-time zone recurring command is specified without parameters, the summer time rules default to United States rules. Default of the offset argument is 60.

Step 5

ntp server ip-address

 

Router(config)# ntp server 10.1.2.3

Synchronizes software clock of router with the specified NTP server.

Step 6

exit

 

Router(config-telephony)# end

Returns to privileged EXEC mode.

What to Do Next

SCCP: Setting the Olson Timezone

To set the Olson Timezone so that the correct local time is displayed on a Cisco Unified SCCP IP phone, perform the following steps.

Prerequisites

  • TzDataCSV.csv file is added to the configuration files of Cisco Unified 6921, 6941, 6945, and 6961 SCCP IP phones.
  • tzupdater.jar file is added to the configuration files of Cisco Unified 7961 SCCP IP phones.

SUMMARY STEPS

1. enable

2. configure terminal

3. tftp-server device: tzupdater.jar

4. tftp-server device: TZDataCSV.csv

5. telephony-service

6. olsontimezone timezone version number

7. create cnf-files

8. time-zone number

9. exit

10. clock timezone zone hours-offset

11. clock summer-time zone date date month year hh:mm date month year hh:mm

12. exit

13. clock set hh:mm:ss day month year

14. configure terminal

15. telephony-service

16. reset

17. end

DETAILED STEPS

Command or Action
Purpose

Step 1

enable

 

Router> enable

Enables privileged EXEC mode.

  • Enter your password if prompted.

Step 2

configure terminal

 

Router# configure terminal

Enters global configuration mode.

Step 3

tftp-server device: tzupdater.jar

 

Router(config)# tftp-server flash:tzupdater.jar

Enables access to the tzupdater.jar file on the TFTP server.

  • device —TFTP server that is accessible to the Cisco Unified CME, such as flash or slot 0.

Step 4

tftp-server device: TZDataCSV.csv

 

Router(config)# tftp-server flash:TZDataCSV.csv

Enables access to the TZDataCSV.csv file on the TFTP server.

  • device —TFTP server that is accessible to the Cisco Unified CME, such as flash or slot 0.

Step 5

telephony-service

 

Router(config)# telephony-service

Enters telephony-service configuration mode.

Step 6

olsontimezone timezone version number

 

Router(config-telephony)# olsontimezone America/Argentina/Buenos Aires version 2010o

Sets the Olson Timezone so that the correct local time is displayed on Cisco Unified SCCP IP phones or Cisco Unified SIP IP phones.

  • timezone —Olson Timezone names, which include the area (name of continent or ocean) and location (name of a specific location within that region, usually cities or small islands).
  • version number —Version of the tzupdater.jar or TzDataCSV.csv file. The version indicates whether the file needs to be updated or not.

Note In Cisco Unified CME 9.0, the latest version is 2010o.

Step 7

create cnf-files

 

Router(config-telephony)# create cnf-files

Builds the eXtensible Markup Language (XML) configuration files that are required for Cisco Unified SCCP IP phones in Cisco Unified CME.

Step 8

time-zone number

 

Router(config-telephony)# time-zone 21

Sets the time zone so that the correct local time is displayed on Cisco Unified SCCP IP phones.

  • number —Numeric code for a named time zone.

Step 9

exit

 

Router(config-telephony)# exit

Exits telephony-service configuration mode.

Step 10

clock timezone zone hours-offset

 

Router(config)# clock timezone CST -6

Sets the time zone for display purposes.

  • zone —Name of the time zone to be displayed when standard time is in effect. The length of the zone argument is limited to 7 characters.
  • hours-offset —Hours difference from UTC.

Step 11

clock summer-time zone date date month year hh:mm date month year hh:mm

 

Router(config)# clock summer-time CST date 12 October 2010 2:00 26 April 2011 2:00

(Optional) Configures the Cisco Unified CME system to automatically switch to summer time (daylight saving time).

  • zone —Name of the time zone (for example, “PDT” for Pacific Daylight Time) to be displayed when summer time is in effect. The length of the zone argument is limited to 7 characters.
  • date —Indicates that summer time should start on the first specific date listed in the command and end on the second specific date in the command.
  • date —Date of the month (1 to 31).
  • month —Month (January, February, and so on).
  • year —Year (1993 to 2035).
  • hh:mm —Time (24-hour format) in hours and minutes.

Step 12

exit

 

Router(config)# exit

Exits global configuration mode.

Step 13

clock set hh:mm:ss day month year

 

Router# clock set 19:29:00 13 May 2011

Manually sets the system software clock.

  • hh:mm:ss —Current time in hours (24-hour format), minutes, and seconds.
  • day —Current day (by date) in the month.
  • month —Current month (by name).
  • year —Current year (no abbreviation).

Step 14

configure terminal

 

Router# configure terminal

Enters global configuration mode.

Step 15

telephony-service

 

Router(config)# telephony-service

Enters telephony-service configuration mode.

Step 16

reset

 

Router(config-telephony)# reset

Performs a complete reboot of Cisco Unfiied SCCP IP phones associated with a Cisco Unified CME router.

Step 17

end

 

Router(config-telephony)# end

Exits to privileged EXEC mode.

SIP: Setting the Olson Timezone

To set the Olson Timezone so that the correct local time is displayed on a Cisco Unified SIP IP phone, perform the following steps.

Prerequisites

  • TzDataCSV.csv file is added to the configuration files of Cisco Unified 3911, 3951, 6921, 6941, 6945, and 6961 SIP IP phones.
  • tzupdater.jar file is added to the configuration files of Cisco Unified 7961 SIP IP phones.

SUMMARY STEPS

1. enable

2. configure terminal

3. tftp-server device : tzupdater.jar

4. tftp-server device : TZDataCSV.csv

5. voice register global

6. olsontimezone timezone version number

7. create profile

8. timezone number

9. exit

10. clock timezone zone hours-offset

11. clock summer-time zone date date month year hh:mm date month year hh:mm

12. exit

13. clock set hh:mm:ss day month year

14. configure terminal

15. voice register global

16. reset

17. end

DETAILED STEPS

Command or Action
Purpose

Step 1

enable

 

Router> enable

Enables privileged EXEC mode.

  • Enter your password if prompted.

Step 2

configure terminal

 

Router# configure terminal

Enters global configuration mode.

Step 3

tftp-server device : tzupdater.jar

 

Router(config)# tftp-server slot0:tzupdater.jar

Enables access to the tzupdater.jar file on the TFTP server.

  • device —TFTP server that is accessible to the Cisco Unified CME, such as flash or slot 0.

Step 4

tftp-server device : TZDataCSV.csv

 

Router(config)# tftp-server slot0:TZDataCSV.csv

Enables access to the TZDataCSV.csv file on the TFTP server.

  • device —TFTP server that is accessible to the Cisco Unified CME, such as flash or slot 0.

Step 5

voice register global

 

Router(config)# voice register global

Enters voice register global configuration mode.

Step 6

olsontimezone timezone version number

 

Router(config-register-global)# olsontimezone America/Argentina/Buenos Aires version 2010o

Sets the Olson Timezone so that the correct local time is displayed on Cisco Unified SCCP IP phones or Cisco Unified SIP IP phones.

  • timezone —Olson Timezone names, which include the area (name of continent or ocean) and location (name of a specific location within that region, usually cities or small islands).
  • version number —Version of the tzupdater.jar or tzdatacsv.csv file. The version indicates whether the file needs to be updated or not.

Note In Cisco Unified CME 9.0, the latest version is 2010o.

Step 7

create profile

 

Router(config-register-global)# create profile

Generates the configuration profile files required for Cisco Unified SIP IP phones.

Step 8

timezone number

 

Router(config-register-global)# timezone 21

Sets the time zone used for Cisco Unified SIP IP phones.

  • number —Range is 1 to 53. Default is 5, Pacific Standard/Daylight Time.

Step 9

exit

 

Router(config-register-global)# exit

Exits voice register global configuration mode.

Step 10

clock timezone zone hours-offset

 

Router(config)# clock timezone CST -6

Sets the time zone for display purposes.

  • zone —Name of the time zone to be displayed when standard time is in effect. The length of the zone argument is limited to 7 characters.
  • hours-offset —Hours difference from UTC.

Step 11

clock summer-time zone date date month year hh:mm date month year hh:mm

 

Router(config)# clock summer-time CST date 12 October 2010 2:00 26 April 2011 2:00

(Optional) Configures the Cisco Unified CME system to automatically switch to summer time (daylight saving time).

  • zone —Name of the time zone (for example, “PDT” for Pacific Daylight Time) to be displayed when summer time is in effect. The length of the zone argument is limited to 7 characters.
  • date —Indicates that summer time should start on the first specific date listed in the command and end on the second specific date in the command.
  • date —Date of the month (1 to 31).
  • month —Month (January, February, and so on).
  • year —Year (1993 to 2035).
  • hh:mm —Time (24-hour format) in hours and minutes.

Step 12

exit

 

Router(config)# exit

Exits global configuration mode.

Step 13

clock set hh:mm:ss day month year

 

Router# clock set 15:25:00 17 November 2011

Manually sets the system software clock.

  • hh:mm:ss —Current time in hours (24-hour format), minutes, and seconds.
  • day —Current day (by date) in the month.
  • month —Current month (by name).
  • year —Current year (no abbreviation).

Step 14

configure terminal

 

Router# configure terminal

Enters global configuration mode.

Step 15

voice register global

 

Router(config)# voice register global

Enters voice register global configuration mode.

Step 16

reset

 

Router(config-register-global)# reset

Performs a complete reboot of Cisco Unified SIP phones associated with a Cisco Unified CME router.

Step 17

end

 

Router(config-register-global)# end

Exits to privileged EXEC mode.

Configuring DTMF Relay for H.323 Networks in Multisite Installations

To configure DTMF relay for H.323 networks in a multisite installation only, perform the following steps.


NoteTo configure DTMF relay on SIP networks, see the“Configuring SIP Trunk Support” section.


SUMMARY STEPS

1. enable

2. configure terminal

3. dial-peer voice tag voip

4. dtmf-relay h245-alphanumeric

5. end

DETAILED STEPS

Command or Action
Purpose

Step 1

enable

 

Router> enable

Enables privileged EXEC mode.

  • Enter your password if prompted.

Step 2

configure terminal

 

Router# configure terminal

Enters global configuration mode.

Step 3

dial-peer voice tag voip

 

Router(config)# dial-peer voice 2 voip

Enters dial-peer configuration mode.

Step 4

dtmf-relay h245-alphanumeric

 

Router(config-dial-peer)# dtmf-relay h245-alphanumeric

Specifies the H.245 alphanumeric method for relaying dual tone multifrequency (DTMF) tones between telephony interfaces and an H.323 network.

Step 5

end

 

Router(config-dial-peer)# end

Returns to privileged EXEC mode.

What to Do Next

Configuring SIP Trunk Support

To enable DTMF relay on a dial-peer for a SIP gateway and set up the gateway to register phone numbers with Cisco Unified CME, perform the following steps.

SUMMARY STEPS

1. enable

2. configure terminal

3. dial-peer voice tag voip

4. dtmf-relay rtp-nte

5. dtmf-relay sip-notify

6. exit

7. sip-ua

8. notify telephone-event max-duration msec

9. registrar { dns: host-name | ipv4: ip-address } expires seconds [ tcp ] [ secondary ]

10. retry register number

11. timers register msec

12. end

DETAILED STEPS

Command or Action
Purpose

Step 1

enable

 

Router> enable

Enables privileged EXEC mode.

  • Enter your password if prompted.

Step 2

configure terminal

 

Router# configure terminal

Enters global configuration mode.

Step 3

dial-peer voice tag voip

 

Router(config)# dial-peer voice 2 voip

Enters dial-peer configuration mode.

Step 4

dtmf-relay rtp-nte

 

Router(config-dial-peer)# dtmf-relay rtp-nte

Forwards DTMF tones by using Real-Time Transport Protocol (RTP) with the Named Telephone Event (NTE) payload type and enables DTMF relay using the RFC 2833 standard method.

Step 5

dtmf-relay sip-notify

 

Router(config-dial-peer)# dtmf-relay sip-notify

Forwards DTMF tones using SIP NOTIFY messages.

Step 6

exit

 

Router(config-dial-peer)# exit

Exits dial-peer configuration mode.

Step 7

sip-ua

 

Router(config)# sip-ua

Enters SIP user-agent configuration mode.

Step 8

notify telephone-event max-duration msec

 

Router(config-sip-ua)# notify telephone-event max-duration 2000

Sets the maximum milliseconds allowed between two consecutive NOTIFY messages for a single DTMF event.

  • max-duration time —Range: 500 to 3000. Default: 2000.

Step 9

registrar { dns: host-name | ipv4: ip-address } expires seconds [ tcp ] [ secondary ]

 

Router(config-sip-ua)# registrar ipv4:10.8.17.40 expires 3600 secondary

Registers E.164 numbers on behalf of analog telephone voice ports (FXS) and IP phone virtual voice ports (EFXS) with an external SIP proxy or SIP registrar server.

Step 10

retry register number

 

Router(config-sip-ua)# retry register 10

Sets the total number of SIP Register messages that the gateway should send.

  • number —Number of Register message retries. Range: 1 to 10. Default: 10.

Step 11

timers register msec

 

Router(config-sip-ua)# timers register 500

Sets how long the SIP user agent (UA) waits before sending Register requests.

  • time —Waiting time, in milliseconds. Range: 100 to 1000. Default: 500.

Step 12

end

 

Router(config-sip-ua)# end

Returns to privileged EXEC mode.

Verifying SIP Trunk Support Configuration

To verify SIP trunk configuration, perform the following steps.

SUMMARY STEPS

1. show sip-ua status

2. show sip-ua timers

3. show sip-ua register status

4. show sip-ua statistics

DETAILED STEPS


Step 1 show sip-ua status

Use this command to display the time interval between consecutive NOTIFY messages for a telephone event. In the following example, the time interval is 2000 ms:

Router# show sip-ua status

SIP User Agent Status

SIP User Agent for UDP :ENABLED

SIP User Agent for TCP :ENABLED

SIP User Agent bind status(signaling):DISABLED

SIP User Agent bind status(media):DISABLED

SIP early-media for 180 responses with SDP:ENABLED

SIP max-forwards :6

SIP DNS SRV version:2 (rfc 2782)

NAT Settings for the SIP-UA

Role in SDP:NONE

Check media source packets:DISABLED

Maximum duration for a telephone-event in NOTIFYs:2000 ms

SIP support for ISDN SUSPEND/RESUME:ENABLED

Redirection (3xx) message handling:ENABLED

SDP application configuration:

Version line (v=) required

Owner line (o=) required

Timespec line (t=) required

Media supported:audio image

Network types supported:IN

Address types supported:IP4

Transport types supported:RTP/AVP udptl

Step 2 show sip-ua timers

This command displays the waiting time before Register requests are sent; that is, the value that has been set with the timers register command.

Step 3 show sip-ua register status

This command displays the status of local E.164 registrations.

Step 4 show sip-ua statistics

This command displays the Register messages that have been sent.


 

Changing the TFTP Address on a DHCP Server

To change the TFTP IP address after it has already been configured, perform the following steps.

Prerequisites

Your Cisco Unified CME router is a DHCP server.

Restrictions

If the DHCP server is on a different router than Cisco Unified CME, reconfigure the external DHCP server with the new IP address of the TFTP server.

SUMMARY STEPS

1. enable

2. configure terminal

3. ip dhcp pool pool-name

4. option 150 ip ip-address

5. end

DETAILED STEPS

Command or Action
Purpose

Step 1

enable

 

Router> enable

Enables privileged EXEC mode.

  • Enter your password if prompted.

Step 2

configure terminal

 

Router# configure terminal

Enters global configuration mode.

Step 3

ip dhcp pool pool-name

 

Router(config)# ip dhcp pool pool2

Enters DHCP pool configuration mode to create or modify a DHCP pool.

  • pool-name —Previously configured unique identifier for the pool to be configured.

Step 4

option 150 ip ip-address

 

Router(config-dhcp)# option 150 ip 10.0.0.1

Specifies the TFTP server IP address from which the Cisco Unified IP phone downloads the image configuration file, XmlDefault.cnf.xml.

Step 5

end

 

Router(config-dhcp)# end

Returns to privileged EXEC mode.

Enabling OOD-R

To enable OOD-R support on the Cisco Unified CME router, perform the following steps.

Prerequisites

  • Cisco Unified CME 4.1 or a later version.
  • The application that initiates OOD-R, such as a click-to-dial application, and its directory server must be installed and configured.

For information on the SIP REFER and NOTIFY methods used between the directory server and Cisco Unified CME, see RFC 3515 , The Session Initiation Protocol (SIP) Refer Method.

For information on the message flow Cisco Unified CME uses when initiating a session between the Referee and Refer-Target, see RFC 3725 , Best Current Practices for Third Party Call Control (3pcc).

Restrictions

  • The call waiting, conferencing, hold, and transfer call features are not supported while the Refer-Target is ringing.
  • In a SIP to SIP scenario, no ringback is heard by the Referee when Refer-Target is ringing.

SUMMARY STEPS

1. enable

2. configure terminal

3. sip-ua

4. refer-ood enable [ request-limit ]

5. exit

6. voice register global

7. authenticate ood-refer

8. authenticate credential tag location

9. end

DETAILED STEPS

Command or Action
Purpose

Step 1

enable

 

Router> enable

Enables privileged EXEC mode.

  • Enter your password if prompted.

Step 2

configure terminal

 

Router# configure terminal

Enters global configuration mode.

Step 3

sip-ua

 

Router(config)# sip-ua

Enters SIP user-agent configuration mode to configure the user agent.

Step 4

refer-ood enable [ request-limit ]

 

Router(config-sip-ua)# refer-ood enable 300

Enables OOD-R processing.

  • request-limit —Maximum number of concurrent incoming OOD-R requests that the router can process. Range: 1 to 500. Default: 500.

Step 5

exit

 

Router(config-sip-ua)# exit

Exits SIP user-agent configuration mode.

Step 6

voice register global

 

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 or Cisco Unified SRST environment.

Step 7

authenticate ood-refer

 

Router(config-register-global)# authenticate ood-refer

(Optional) Enables authentication of incoming OOD-R requests using RFC 2617-based digest authentication.

Step 8

authenticate credential tag location

 

Router(config-register-global)# authenticate credential 1 flash:cred1.csv

(Optional) Specifies the credential file to use for authenticating incoming OOD-R requests.

  • tag —Number that identifies the credential file to use for OOD-R authentication. Range: 1 to 5.
  • location —Name and location of the credential file in URL format. Valid storage locations are TFTP, HTTP, and flash memory.

Step 9

end

 

Router(config-register-global)# end

Exits to privileged EXEC mode.

Verifying OOD-R Configuration


Step 1 show running-config

This command verifies your configuration.

Router# show running-config

!

voice register global

mode cme

source-address 10.1.1.2 port 5060

load 7971 SIP70.8-0-1-11S

load 7970 SIP70.8-0-1-11S

load 7961GE SIP41.8-0-1-0DEV

load 7961 SIP41.8-0-1-0DEV

authenticate ood-refer

authenticate credential 1 tftp://172.18.207.15/labtest/cred1.csv

create profile sync 0004550081249644

.

.

.

sip-ua

refer-ood enable

Step 2 show sip-ua status refer-ood

This command displays OOD-R configuration settings.

Router# show sip-ua status refer-ood

Maximum allow incoming out-of-dialog refer 500

Current existing incoming out-of-dialog refer dialogs: 1

outgoing out-of-dialog refer dialogs: 0


 

Troubleshooting OOD-R


Step 1 debug ccsip messages

This command displays the SIP messages exchanged between the SIP UA client and the router.

Router# debug ccsip messages

SIP Call messages tracing is enabled

Aug 22 18:15:35.757: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Received:

REFER sip:1011@10.5.2.141:5060 SIP/2.0

Via: SIP/2.0/UDP 172.18.204.144:59607;branch=z9hG4bK1238

From: <sip:1011@172.18.204.144>;tag=308fa4ba-4509

To: <sip:1001@10.5.2.141>

Call-ID: f93780-308fa4ba-0-767d@172.18.204.144

CSeq: 101 REFER

Max-Forwards: 70

Contact: <sip:1011@172.18.204.144:59607>

User-Agent: CSCO/7

Timestamp: 814720186

Refer-To: sip:1001@10.5.2.141

Referred-By: <sip:root@172.18.204.144>

Content-Length: 0

Aug 22 18:15:35.773: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

SIP/2.0 202 Accepted

Via: SIP/2.0/UDP 172.18.204.144:59607;branch=z9hG4bK1238

From: <sip:1011@172.18.204.144>;tag=308fa4ba-4509

To: <sip:1001@10.5.2.141>;tag=56D02AC-1E8E

Date: Tue, 22 Aug 2006 18:15:35 GMT

Call-ID: f93780-308fa4ba-0-767d@172.18.204.144

Timestamp: 814720186

CSeq: 101 REFER

Content-Length: 0

Contact: <sip:1011@172.18.204.141:5060>

Step 2 debug voip application oodrefer

This command displays debugging messages for the OOD-R feature.

Router# debug voip application oodrefer

voip application oodrefer debugging is on

Aug 22 18:16:21.625: //-1//AFW_:/C_ServiceThirdParty_Event_Handle:

Aug 22 18:16:21.625: //-1//AFW_:/AFW_ThirdPartyCC_New:

Aug 22 18:16:21.625: //-1//AFW_:EE461DC520000:/C_PackageThirdPartyCC_NewReq: ThirdPartyCC module listened by TclModule_45F39E28_0_91076048

Aug 22 18:16:21.625: //-1//AFW_:EE461DC520000:/OCOpen_SetupRequest: Refer Dest1: 1011, Refer Dest2: 1001; ReferBy User: root

Aug 22 18:16:21.693: //-1//AFW_:EE461DC520000:/OCHandle_SignalEvent_1:

Aug 22 18:16:21.693: //-1//AFW_:/Third_Party_CC_Send_Notify: Third_Party_CC_Send_Notify: sending notify respStatus=2, final=FALSE, failureCause=16

Aug 22 18:16:21.693: //-1//AFW_:/Third_Party_CC_Send_Notify: AppNotify successful!

Aug 22 18:16:26.225: //-1//AFW_:EE461DC520000:/OCHandle_SignalEvent_1:

Aug 22 18:16:26.229: //-1//AFW_:EE461DC520000:/OCHandle_SignalEvent_1:

Aug 22 18:16:26.249: //-1//AFW_:EE461DC520000:/OCHandle_SignalEvent_2:

Aug 22 18:16:29.341: //-1//AFW_:EE461DC520000:/OCHandle_SignalEvent_2:

Aug 22 18:16:29.341: //-1//AFW_:/Third_Party_CC_Send_Notify: Third_Party_CC_Send_Notify: sending notify respStatus=4, final=TRUE, failureCause=16

Aug 22 18:16:29.341: //-1//AFW_:/Third_Party_CC_Send_Notify: AppNotify successful!

Aug 22 18:16:29.349: //-1//AFW_:EE461DC520000:/OCHandle_Handoff: BAG contains:

Aug 22 18:16:29.349: LEG[895 ][LEG_INCCONNECTED(5)][Cause(0)]

Aug 22 18:16:29.349: CON[7 ][CONNECTION_CONFED(2)] {LEG[895 ][LEG_INCCONNECTED(5)][Cause(0)],LEG[896 ][LEG_OUTCONNECTED(10)][Cause(0)]}

Aug 22 18:16:29.349: LEG[896 ][LEG_OUTCONNECTED(10)][Cause(0)]

Aug 22 18:16:29.365: //-1//AFW_:EE461DC520000:/OCAnyState_IgnoreEvent: Event Ignored

Aug 22 18:16:29.365: //-1//AFW_:/C_ServiceThirdParty_Event_Handle:

Aug 22 18:16:29.365: //-1//AFW_:EE461DC520000:/C_ServiceThirdParty_Event_Handle: Received event APP_EV_NOTIFY_DONE[174] in Main Loop

Aug 22 18:16:29.365: //-1//AFW_:EE461DC520000:/OCAnyState_IgnoreEvent: Event Ignored

Aug 22 18:16:29.365: //-1//AFW_:/C_ServiceThirdParty_Event_Handle:

Aug 22 18:16:29.365: //-1//AFW_:EE461DC520000:/C_ServiceThirdParty_Event_Handle: Received event APP_EV_NOTIFY_DONE[174] in Main Loop

Aug 22 18:16:29.369: //-1//AFW_:EE461DC520000:/OCHandle_SubscribeCleanup:

Aug 22 18:16:29.369: //-1//AFW_:EE461DC520000:/Third_Party_CC_Cleaner:

Aug 22 18:16:29.453: //-1//AFW_:EE461DC520000:/OCClosing_AnyEvent:

Aug 22 18:16:29.453: //-1//AFW_:EE461DC520000:/Third_Party_CC_Cleaner:

Aug 22 18:16:29.453: //-1//AFW_:EE461DC520000:/OCClosing_AnyEvent:

Aug 22 18:16:29.453: //-1//AFW_:EE461DC520000:/Third_Party_CC_Cleaner:


 

Configuration Examples for Network Parameters

NTP Server: Example

The following example defines the pst timezone as 8 hours offset from UTC, using a recurring daylight savings time called pdt, and synchronizes the clock with the NTP server at 10.1.2.3:

clock timezone pst -8

clock summer-time pdt recurring

ntp server 10.1.2.3

DTMF Relay for H.323 Networks: Example

The following excerpt from the show running-config command output shows a dial peer configured to use H.245 alphanumeric DTMF relay:

dial-peer voice 4000 voip

destination-pattern 4000

session target ipv4:10.0.0.25

codec g711ulaw

dtmf-relay h245-alphanumeric

OOD-R: Example

voice register global

mode cme

source-address 11.1.1.2 port 5060

load 7971 SIP70.8-0-1-11S

load 7970 SIP70.8-0-1-11S

load 7961GE SIP41.8-0-1-0DEV

load 7961 SIP41.8-0-1-0DEV

authenticate ood-refer

authenticate credential 1 tftp://172.18.207.15/labtest/cred1.csv

create profile sync 0004550081249644

.

.

.

sip-ua

authentication username jack password 021201481F

refer-ood enable

Where to Go Next

  • If you are configuring Cisco Unified CME for the first time on this router, you are ready to configure system-level parameters. See the “” section.
  • If you modified network parameters for an already configured Cisco Unified CME router, you are ready to generate the configuration file to save the modifications. See the “Generating Configuration Files for Phones” section

Additional References

The following sections provide references related to Cisco Unified CME features.

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.

To receive security and technical information about your products, you can subscribe to various services, such as the Product Alert Tool (accessed from Field Notices), the Cisco Technical Services Newsletter, and Really Simple Syndication (RSS) Feeds.

Access to most tools on the Cisco Support website requires a Cisco.com user ID and password.

http://www.cisco.com/techsupport

Feature Information for Network Parameters

Table 5-1 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/docs/voice_ip_comm/cucme/requirements/guide/33matrix.htm .

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.


NoteTable 5-1 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 5-1 Feature Information for Network Parameters

Feature Name
Cisco Unified CME Version
Modification

Olson Timezone

9.0

Eliminates the need to update time zone commands or phone loads to accommodate a new country with a new time zone or an existing country whose city or state wants to change their time zone, using the olsontimezone command in either telephony-service or voice register global configuration mode.

Out-of-Dialog Refer

4.1

Out-of Dialog REFER support was added.