/mcpThird-party phones that are running AS-SIP do not get configured through the Cisco Unified Communications Manager TFTP server. The customer must configure 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). Also, if the directory number of a line is changed, the customer must ensure that it gets changed in both Cisco Unified CM Administration and in the native phone configuration mechanism. Identification of Third-Party Phones The 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 a user that is configured in the End User Configuration window of Cisco Unified CM Administration. The administrator configures the SIP third-party phone with the user; for example, swhite, in the Digest User field of Phone Configuration window. You can assign each user ID to only one third-party phone. If the same user ID is assigned as the Digest User for multiple phones, the third-party phones to which they are assigned will not successfully register. Note Configuration of Third Party AS-SIP Phones and Cisco IP Phones The following table provides a comparison overview of the configuration differences between Cisco Unified IP Phones and third-party phones that are running AS-SIP. Table 83: Comparison of the Configuration Differences Between Cisco IP Phones and Third-Party Phones Supports Reset and Restart Supports Unified Communications Manager Failover and Fallback Downloads Dial Plan File Downloads Softkey File Sends MAC Address Integrated with Centralized TFTP Phone Running AS-SIP Yes Yes Yes Yes Yes Yes Cisco IP Phone No No No No No No Third-party AS-SIP device Not all Cisco IP Phones support AS-SIP. See the phone administration guide for your phone model for support information Note Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs 814 QoS Management Third-Party AS-SIP Phones