Filter
Top Products
B-4
Cisco Unified Communications Manager Administration Guide
OL-18611-01
Appendix B Configuring Non-Cisco Phones That Are Running SIP
Configuration Differences for Phones That Are Running SIP
The username, swhite, must match an end user that is configured in the End User Configuration window
of Cisco Unified Communications Manager Administration (see
Configuring an End User, page 114-9).
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, page 91-27).
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
Phone Security Profile Configuration in the Cisco Unified
Communications Manager Administration Guide.) 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.