Cisco Unified Communications Manager Administration Guide, Release 8.6(1)
Configuring Non-Cisco Phones That Are Running SIP
Downloads: This chapterpdf (PDF - 109.0KB) The complete bookPDF (PDF - 14.14MB) | Feedback

Configuring Non-Cisco Phones That Are Running SIP

Table Of Contents

Configuring Non-Cisco Phones That Are Running SIP

Configuration Checklist for Third-Party Phones That Are Running SIP

Configuration Differences for Phones That Are Running SIP

How Cisco Unified Communications Manager Identifies a Third-Party Phone

Third-Party Phones That Are Running SIP and TFTP

Enabling Digest Authentication for Third-Party Phones That Are Running SIP

DTMF Reception

Licensing for Third-Party Phones That Are Running SIP

Where to Find More Information


Configuring Non-Cisco Phones That Are Running SIP


Cisco Unified Communications Manager supports Cisco Unified IP Phones with SIP as well as RFC3261-compliant phones that are running SIP from third-party companies. This appendix describes how to configure the third-party phones that are running SIP by using Cisco Unified Communications Manager Administration.

This appendix contains the following sections:

Configuration Checklist for Third-Party Phones That Are Running SIP

Configuration Differences for Phones That Are Running SIP

How Cisco Unified Communications Manager Identifies a Third-Party Phone

Third-Party Phones That Are Running SIP and TFTP

Enabling Digest Authentication for Third-Party Phones That Are Running SIP

DTMF Reception

Licensing for Third-Party Phones That Are Running SIP

Where to Find More Information

Configuration Checklist for Third-Party Phones That Are Running SIP

Cisco Unified Communications Manager supports Cisco Unified IP Phones with SIP as well as RFC3261-compliant phones that are running SIP from third-party companies. Table B-1 provides steps to manually configure a third-party phone that is running SIP by using Cisco Unified Communications Manager Administration.

Table B-1 Configuration Checklist for Third-Party Phone That Is Running SIP  

Configuration Steps
Procedures and Related Topics

Step 1 

Gather the following information about the phone:

MAC address

Physical location of the phone

Cisco Unified Communications Manager user to associate with the phone

Partition, calling search space, and location information, if used

Number of lines and associated DNs to assign to the phone

 

Step 2 

Determine whether sufficient Device License Units are available. If not, purchase and install additional Device License Units. Third-Party SIP Devices (Basic) and (Advanced) consume three and six Device License Units each, respectively.

Calculating the Number of Required License Units, Cisco Unified Communications Manager Features and Services Guide

Obtaining a License File, Cisco Unified Communications Manager Features and Services Guide

Step 3 

Configure the end user that will be the Digest User.

Note If the third-party phone that is running SIP does not support an authorization ID (digest user), create a user with a user ID that matches the DN of the third-party phone. For example, create an end user named 1000 and create a DN of 1000 for the phone. Assign this user to the phone (see Step 9).

End User Configuration Settings

Step 4 

Configure the SIP Profile or use the default profile. The SIP Profile gets added to the phone that is running SIP by using the Phone Configuration window.

Note Third-party phones that are running SIP use only the SIP Profile Information section of the SIP Profile Configuration window.

SIP Profile Configuration Settings

Configuring Cisco Unified IP Phones

Step 5 

Configure the Phone Security Profile. To use digest authentication, you must configure a new phone security profile. If you use one of the standard, nonsecure SIP profiles that are provided for auto-registration, you cannot enable digest authentication.

Enabling Digest Authentication for Third-Party Phones That Are Running SIP

Phone Security Profile Configuration

Cisco Unified Communications Manager Security Guide

Step 6 

Add and configure the third-party phone that is running SIP by choosing Third-party SIP Device (Advanced) or (Basic) from the Add a New Phone Configuration window.

Note Third-party SIP Device (Basic) supports one line and consumes three license units, and Third-party SIP Device (Advanced) supports up to eight lines and video and consumes six license units.

Configuring Cisco Unified IP Phones

Step 7 

Add and configure lines (DNs) on the phone.

Directory Number Configuration

Step 8 

In the End User Configuration window, associate the third-party phone that is running SIP with the user by using Device Association and choosing the phone that is running SIP.

Associating Devices to an End User

Step 9 

In the Digest User field of the Phone Configuration window, choose the end user that you created in Step 3.

Configuring Speed-Dial Buttons or Abbreviated Dialing

Step 10 

Provide power, install, verify network connectivity, and configure network settings for the third-party phone that is running SIP.

See the administration guide that was provided with your phone that is running SIP.

Step 11 

Make calls with the third-party phone that is running SIP.

See the user guide that came with your third-party phone that is running SIP.

Configuration Differences for Phones That Are Running SIP

Table B-2 provides a comparison overview of the configuration differences between Cisco Unified IP Phones and third-party phones that are running SIP.

Table B-2 Model Configuration Comparison for Phones That Are Running SIP 

Phone That Is Running SIP
Integrated with Centralized TFTP
Sends MAC Address
Downloads Softkey File
Downloads Dial Plan File
Supports Cisco Unified Communications Manager Failover and Fallback
Supports Reset and Restart

Cisco Unified IP Phone 7911, 7941, 7961, 7970, 7971

Yes

Yes

Yes

Yes

Yes

Yes

Cisco Unified IP Phone 7940, 7960

Yes

Yes

No

Yes

Yes

Yes

Cisco Unified IP Phone 7905, 7912

Yes

Yes

No

No

Yes

Yes

Third-party phone that is running SIP

No

No

No

No

No

No


Use Cisco Unified Communications Manager Administration to configure third-party phones that are running SIP (see the "Where to Find More Information" section). The administrator must also perform configuration steps on the third-party phone that is running SIP; see following examples:

Ensure proxy address in the phone is the IP or Fully Qualified Domain Name (FQDN) of Cisco Unified Communications Manager.

Ensure directory number(s) in the phone match the directory number(s) that are configured for the device in Cisco Unified Communications Manager Administration.

Ensure digest user ID (sometimes referred to as Authorization ID) in the phone matches the Digest User ID in Cisco Unified Communications Manager Administration.

Consult the documentation that came with the third-party phone that is running SIP for more information.

How Cisco Unified Communications Manager Identifies a Third-Party Phone

Because third-party phones that are running SIP do not send a MAC address, they must identify themselves by using username.

The REGISTER message includes the following header:

Authorization: Digest username="swhite",realm="ccmsipline",nonce="GBauADss2qoWr6k9y3hGGVDAqnLfoLk5",uri="sip:172.18.197.224",algorithm=MD5,response="126c0643a4923359ab59d4f53494552e"

The username, swhite, must match an end user that is configured in the End User Configuration window of Cisco Unified Communications Manager Administration (see End User Configuration Settings). The administrator configures the SIP third-party phone with the user; for example, swhite, in the Digest User field of Phone Configuration window (see Configuring Cisco Unified IP Phones).


Note You can assign each end user ID to only one third-party phone (in the Digest User field of the Phone Configuration window). If the same end user ID is assigned as the Digest User for multiple phones, the third-party phones to which they are assigned will not successfully register.

Third-Party Phones That Are Running SIP and TFTP

Third-party phones that are running SIP do not get configured by using the Cisco Unified Communications Manager TFTP server. The customer configures them by using the native phone configuration mechanism (usually a web page or tftp file). The customer must keep the device and line configuration in the Cisco Unified Communications Manager database synchronized with the native phone configuration (for example, extension 1002 on the phone and 1002 in Cisco Unified Communications Manager). Additionally, if the directory number of a line is changed, ensure that it gets changed in both Cisco Unified Communications Manager Administration and in the native phone configuration mechanism.

Enabling Digest Authentication for Third-Party Phones That Are Running SIP

To enable digest authentication for third-party phones that are running SIP, the administrator must create a Phone Security Profile. (See the "Phone Security Profile Configuration" section for a general description and the Cisco Unified Communications Manager Security Guide for details.) On the Phone Security Profile Configuration window, check the Enable Digest Authentication check box. After the security profile is configured, the administrator must assign that security profile to the phone that is running SIP by using the Phone Configuration window. If this check box is not checked, Cisco Unified Communications Manager will use digest authentication for purposes of identifying the phone by the end user ID, and it will not verify the digest password. If the check box is checked, Cisco Unified Communications Manager will verify the password.


Note Cisco Unified Communications Manager does not support Transport Layer Security (TLS) from third-party phones that are running SIP.

DTMF Reception

To require DTMF reception, check the Require DTMF Reception check box that displays on the Phone Configuration window in Cisco Unified Communications Manager Administration.

Licensing for Third-Party Phones That Are Running SIP

Licensing of third-party phones that are running SIP enforces the following limitations:

Third-party SIP Device (Basic)—Video calls do not get supported. Video enforcement occurs as part of the offer/answer process. If video-related media is provided as part of an offer or answer from a SIP device that is not permitted to negotiate video, only the non-video-related parts of the call get extended to the destination party. Similarly, a SIP endpoint that is not permitted to negotiate media will not receive any video-related media in the SDP that is sent from Cisco Unified Communications Manager.

Third-party SIP Device (Advanced) and (Basic)—Cisco-specific SIP extensions do not get supported. Some Cisco-specific SIP extensions that are not supported include service URIs, header extensions, dialog subscriptions, and remote call control proprietary mime types. Cisco Unified Communications Manager will reject any request from a phone that is running SIP that is not permitted to use an advanced feature that uses a service request URI (such as Call Pickup URI, Meet Me Service URI). The SIP profile specifies service URIs. The profile gets assigned to SIP devices. Cisco Unified Communications Manager will block features that require the use of Cisco-specific SIP extensions.


Note Ensure that any wireless third-party SIP client or device is configured as a Third-Party SIP Device (Advanced) in conformance with Cisco Unified Communications Manager licensing policy.

For more information about Cisco SIP Extensions, contact your Cisco representative.

Where to Find More Information

Configuration Checklist for Third-Party Phones That Are Running SIP

Configuration Differences for Phones That Are Running SIP

Directory Number Configuration

Cisco Unified IP Phone Configuration

SIP Profile Configuration

End User Configuration

Cisco Unified IP Phones, Cisco Unified Communications Manager System Guide