How To Register Ip Phones To Cisco Iad

Troubleshooting IP Phone Registration in Cisco Unified CME

Contents

Prerequisites

Brainstorm Here

All IP phones in a Cisco Unified CME system failed to successfully register

All IP phones of a single phone type failed to successfully register

Ane or more IP phones failed to successfully register

Additional References

Troubleshooting IP Telephone Registration in Cisco Unified CME

Final Updated: April 5, 2010
Start Published: March 26, 2008

During the phone bootup sequence, the IP phone requests and receives network configuration information and the configuration file, including the IP address of the Cisco Unified CME router, from the TFTP server.

At this point, the IP phone has plenty information to request registration from the Cisco Unified CME router to which it is connected. The router verifies the phone's configuration against the router'due south running configuration. If it is correct, the telephone successfully registers with Cisco Unified CME and downloads its phone specific information including telephone identification, telephone and extension numbers, telephone firmware upgrade - if required, and features. If the phone firmware is required, the telephone downloads the appropriate firmware files from the TFTP server and begins the phone bootup sequence again.

An IP telephone can register in Cisco Unified CME and not successfully download its configuration data. When this happens, soft keys can appear on the phone display only the extension, name, or characterization practice not appear on the phone brandish.

The following symptoms can indicate that an IP phone is not successfully registered with the Cisco Unified CME system to which it is connected or that an IP phone is registered with Cisco Unified CME but is non provisioned.

Symptoms

No extension number, name, or label or an wrong extension number, name, or label appears on the phone display.

•Prerequisites

•Begin Here

•All IP phones in a Cisco Unified CME system failed to successfully register

•All IP phones of a single phone type failed to successfully register

•I or more than IP phones failed to successfully register

•Additional References

•Obtaining Documentation, Obtaining Support, and Security Guidelines

Prerequisites

•You have access to a TFTP server for downloading files.

•The hardware and software to institute a physical console connectedness to the Cisco router using a last or PC running final emulation is bachelor and operational.

•Cisco router is configured for Cisco Unified CME.

•Phones, phone cables, and ports are operational.

Brainstorm Here

Annotation For information about private commands, see the Cisco Unified CME Control Reference.

To modify or correct the configuration file on the Cisco Unified CME router, see the Cisco Unified CME Arrangement Administrator Guide.

Pace 1 show ephone registered
show vocalization register statistics

For SCCP phones: Apply the prove ephone registered command to display the status of registered SCCP phones.

For SIP phones: Apply the show phonation register statistics command to display statistics associated with the registration event.

Step 2 Are i or more than phones registered in the Cisco Unified CME?

•Yeah—Go to next step.

•No—See "All IP phones in a Cisco Unified CME system failed to successfully register" department.

Stride three prove ephone
testify vox register all

For SCCP phones: Use the testify ephone command to display the status of SCCP phones that are non registered or are trying to annals.

For SIP phones: Use the testify voice register all command to display configuration and registration data for SIP phones in Cisco Unified CME.

Step 4 Are all phones that failed to successfully register using the SIP protocol?

•Yes—See "All IP phones in a Cisco Unified CME system failed to successfully register" section.

•No or don't know—Go to Step 5.

Step 5 Are all of the phones that neglect to successfully register of the aforementioned type, such equally all Cisco Unified IP Phone 7940s or all Cisco Unified IP Telephone 7905s?

•Yes—See "All IP phones of a unmarried phone type failed to successfully register" department.

•No or don't know—See "One or more IP phones failed to successfully register" section.

All IP phones in a Cisco Unified CME organization failed to successfully register

If this is a newly installed and configured Cisco Unified CME and all of the phones fail to annals, the configuration is incorrect or unavailable. If all IP phones have lost their registration, the network interface is the most likely source of the failure.

Step 1 Is this a brand new installation or configuration and all phones take failed to register?

•Yeah—Go to next step.

•No—If you have an external LAN switch, verify that the LAN switch has not been disabled or disconnected from the LAN, or has not failed, then become to the next step. If you have an internal EtherSwitch module, get to the adjacent step.

Step 2 prove running-config

Use the show running-config control to display the contents of the currently running configuration file on your Cisco Unified CME router. The following is a fractional sample output from the prove command including the configuration for an internal DHCP server and Ethernet switch network interface.

Router#            show running-config

 permit-connections h323 to sip

 allow-connections sip to h323

 allow-connections sip to sip

 registrar server expires max 600 min lx  !---<==== required for SIP phones in  Cisco Unified CME

ip dhcp excluded-address 192.0.2.12 192.0.two.12  !---<==== prevents IP address of Cisco  router from existence assigned to IP phones

ip dhcp pool vocalization  !---<==== configuration for internal DHCP

 network 190.0.two.0 255.255.255.0

 choice 150 ip 190.0.2.12  !---<==== IP address of the TFTP server

 default-router 190.0.ii.12  !---<==== Cisco router to which the IP phones are  connected

interface Ethernet0/0  !---<==== Connects router to network

 ip address 190.0.ii.12 255.255.255.0  !---<==== IP address of internal network  interface

Note The configuration for the DHCP server will non be included if you are using an external DHCP server. If you have an external DHCP server, Verify that the DHCP server is enabled or enable the DHCP server.

Step 3 Are all phones that failed to successfully register using the SIP protocol?

•Yep—Go to next stride.

•No—Become to Step 5.

Step four Does the running configuration include the registrar server command?

•Yes—Become to adjacent step.

•No—Correct the configuration.

Step 5 An wrong DHCP configuration tin prevent IP communications between phones and other devices on the LAN. Does the subnet mask in the DHCP configuration match the ane in the network interface?

•Yes—Become to next stride.

•No—Correct the configuration file.

Step 6 Is the IP address for the TFTP server, option 150 nether the dhcp configuration, correctly configured?

Tip If the Cisco Unified CME router is too the TFTP server and there is an internal Ethernet switch installed in the same router, the IP addresses for the TFTP server, the default-router, and network interface are identical.

•Yeah—Go to side by side step

•No—Correct the configuration file.

Step seven If the problem persists, contact technical back up at http://world wide web.cisco.com/techsupport.

All IP phones of a single phone type failed to successfully register

All Cisco Unified IP phones of a particular type can fail to register for one of the following reasons:

•The wrong or wrong Cisco telephone firmware filename is specified for a particular phone blazon.

•The phones cannot download the right Cisco phone firmware file from the TFTP server.

•Auto assign for a specified phone type is enabled and there are more phones of that type than at that place are available telephone or extension numbers.

Tip To identify telephone firmware filenames associated to specific Cisco Unified IP telephone types and compatible with the Cisco IOS release on the Cisco Unified CME router, encounter the appropriate Cisco Unified CME Supported Firmware, Platforms, Memory, and Voice Products.

Footstep one evidence running-config

Use the show running-config control to brandish the contents of the running configuration file on this Cisco Unified CME router.

Router#            show running-configuration

 allow-connections h323 to sip

 allow-connections sip to h323

 allow-connections sip to sip

 registrar server expires max 600 min 60  !---<==== required for SIP phones in  Cisco Unified CME

 Load 7960-7940 P00308000300  !---<==== configuration for load command

 Load 7941 SCCP41.8-three-1-21S

 Load 7961 SCCP41.eight-iii-1-21S

 Load 7971 SCCP70.8-3-1-21S

 Load 7970 SCCP70.8-three-i-21S

 ip source-address 200.200.200.1 port 2000

 motorcar-assign 1 to 10 type 7941  !---<==== auto-assign configuration

ip dhcp excluded-address 192.0.2.12 192.0.2.12  !---<==== prevents IP address of Cisco  router from being assigned to IP phones

 network 190.0.2.0 255.255.255.0

 selection 150 ip 190.0.2.12  !---<==== IP address of the TFTP server

 default-router 190.0.2.12

 ip source-accost 190.0.2.12 port 2000  !---<==== IP accost of the TFTP server

 Load 7960-7940 P0S3-08-02-00  !---<==== configuration for load command

Step 2 Does your running configuration include the motorcar-assign command?

•Yes—Go to next step

•No—Go to Footstep 6.

Pace 3 Examine the output for the car-assign control. Is a phone type specified in the automobile-assign configuration?

•Yeah—Go to next step

•No—Go to Pace v.

Footstep 4 Does the phone type specified in the machine-assign configuration match the phone blazon of the telephone to be registered?

•Yes—Go to side by side step

•No—Correct the configuration.

Step 5 Does the number specified in the car-assign configuration match or exceed the number of phones to be registered?

•Yes—Become to next stride

•No—Correct the configuration.

Pace 6 Examine the output for the load control. Is the phone type in the control correctly identified? Is the advisable telephone firmware filename, including version and protocol, specified for this phone type?

Note The firmware filename must non include the .sbin or .loads suffix for all phones except Cisco ATA and Cisco Unified IP Phone 7905 and 7912.

•Yeah—Go to next step

•No—Correct the configuration file.

Stride vii Is the IP address for the TFTP server, option 150 under the dhcp configuration, correctly configured?

Tip If the Cisco Unified CME router is likewise the TFTP server and there is an internal Ethernet switch installed in the same router, the IP addresses for the TFTP server, the default-router, and network interface are identical.

•Yes—Go to side by side step

•No—Correct the configuration file.

Step 8 If your Cisco Unified CME router too the TFTP server?

•Yes—Become to next pace.

•No—Go to Stride 12.

Pace nine show flash

Use the show flash control to display a list of files in wink retentivity. The following fractional sample output shows SCCP and SIP phone firmware filenames in the list of files

 24    333822    P00403020214.bin

 25    398244    P00305000300.sbin

 26    59222     P0S3-07-04-00.bin

 27    461       P0S3-07-04-00.loads

Step 10 Are the Cisco phone firmware files required for each phone type installed in wink memory?

•Yes—Go to adjacent step.

•No—See "Installing and Upgrading Cisco Unified CME Software" in the Cisco Unified CME Administrator Guide.

Step eleven Utilise the reset command to reboot the IP phones. The phone should upgrade its firmware to the new firmware mentioned in the configuration. Does the "File not Found" or "Error verifying configuration" fault message appear on the IP phone display?

•Yes—The telephone is unable to download the firmware file from the TFTP server. Use the tftp-server flash control to configure your Cisco Unified CME router or a Flash retentivity device on your router as a TFTP server, so generate the configuration file. Use the reset command to reboot this IP telephone.

•No—If the problem persists, contact technical support at http://www.cisco.com/techsupport.

Step 12 Verify that the tftp-path command is correctly configure for the external TFTP server.

Step xiii Verify that the external TFTP server is reachable. Ping the external TFTP server.

Footstep 14 Telnet into the external TFTP server and display a list files. Verify or install the appropriate Cisco phone firmware files on the external TFTP server.

Step 15 Use the reset command to reboot the IP phones. The phone should upgrade its firmware to the new firmware mentioned in the configuration. Does the "File non Plant" or "Error verifying configuration" error message appear on the IP phone brandish?

•Yes—The telephone is unable to download the firmware file from the TFTP server. Use the tftp-server wink command to configure your Cisco Unified CME router or a Flash memory device on your router equally a TFTP server, then generate the configuration file. Use the reset command to reboot this IP phone.

•No—If the problem persists, contact technical support at http://world wide web.cisco.com/techsupport.

One or more IP phones failed to successfully register

Typically, an individual Cisco Unified IP phone fails to successfully complete registration for any of the following reasons:

•The configuration file for this IP phone is wrong or empty.

•The IP telephone cannot download its configuration file.

•Motorcar annals is disabled and an individual phone is not explicitly configured.

•Auto assign is enabled and there are more IP phones than at that place are available telephone or extension numbers.

•The appropriate Cisco phone firmware is non or cannot be installed on this IP phone.

Stride ane show running-config

Use the show running-config command to display the contents of the running configuration file on this Cisco Unified CME router.

Router#            bear witness running-configuration

 allow-connections h323 to sip

 allow-connections sip to h323

 let-connections sip to sip

 registrar server expires max 600 min 60  !---<==== required for SIP phones in  Cisco Unified CME

 Load 7960-7940 P00308000300  !---<==== configuration for load command

 Load 7941 SCCP41.8-3-1-21S

 Load 7961 SCCP41.8-3-1-21S

 Load 7971 SCCP70.eight-3-ane-21S

 Load 7970 SCCP70.8-3-1-21S

 ip source-address 200.200.200.1 port 2000

 motorcar-assign 1 to 10 type 7941  !---<==== auto-assign configuration

Footstep 2 Is the phone that failed to successfully register using the SIP protocol?

•Yes—Go to next step.

•No—Become to Step iv.

Step 3 Does the running configuration include the registrar server command?

•Aye—Go to adjacent step.

•No—Correct the configuration.

Step 4 Has this IP phone successfully registered in Cisco Unified CME before today?

•Aye—Go to adjacent step.

•No—Go to Step 10.

Step 5 Does your running configuration include the auto-assign control?

•Yeah—Become to next pace

•No—Go to Step nine.

Step six Examine the output for the auto-assign control. Is a telephone type specified in the auto-assign configuration?

•Yes—Get to adjacent step

•No—Go to Step eight.

Step 7 Does the phone type specified in the auto-assign configuration friction match the telephone blazon of the telephone to be registered?

•Yes—Go to next step

•No—Right the configuration.

Footstep 8 Does the number specified in the machine-assign configuration match or exceeds the number of phones to be registered?

•Yes—Go to next stride

•No—Correct the configuration.

Stride 9 Prior to this registration endeavour, was this IP phone loaded with the same version of Cisco phone firmware as it is today; i.e., same protocol (SIP or SCCP) or the same release version firmware?

•Aye—Go to next step.

•No—See the "All IP phones of a single phone blazon failed to successfully register" section

Step x Identify the MAC address for this IP telephone. The MAC accost is located on a label on the rear of the phone.

Step 11 show telephony-service tftp-bindings
show voice register tftp-bin

For SCCP phones: Use the show telephony-service tftp-bindings command to display a list of files that were generated during configuration. The following is a partial sample output from the testify control.

Router(config)#            testify telephony-service tftp-bindings

 tftp-server system:/its/SEPDEFAULT.cnf

 tftp-server system:/its/SEPDEFAULT.cnf alias SEPDefault.cnf

 tftp-server arrangement:/its/XMLDefault.cnf.xml allonym XMLDefault.cnf.xml

 tftp-server organization:/its/ATADefault.cnf.xml

 tftp-server system:/its/XMLDefault7960.cnf.xml alias SEP00036B54BB15.cnf.xml

 tftp-server organization:/its/germany/7960-font.xml allonym German_Germany/7960-font.xml

 tftp-server system:/its/frg/7960-lexicon.xml alias   German_Germany/7960-lexicon.xml

 tftp-server system:/its/deutschland/7960-kate.xml alias German_Germany/7960-kate.xml

 tftp-server organisation:/its/frg/SCCP-lexicon.xml allonym   German_Germany/SCCP-dictionary.xml

 tftp-server system:/its/germany/7960-tones.xml alias Deutschland/7960-tones.xml

For SIP phones: Use the show vocalisation annals tftp-bind control to display a listing of files that were generated during configuration. The following is a partial sample output from the show command.

Router(config)#            show phonation register tftp-demark

 tftp-server SIPDefault.cnf url arrangement:/cme/sipphone/SIPDefault.cnf

 tftp-server syncinfo.xml url organization:/cme/sipphone/syncinfo.xml

 tftp-server SIP0009B7F7532E.cnf url organization:/cme/sipphone/SIP0009B7F7532E.cnf

 tftp-server SIP000ED7DF7932.cnf url organization:/cme/sipphone/SIP000ED7DF7932.cnf

 tftp-server SIP0012D9EDE0AA.cnf url arrangement:/cme/sipphone/SIP0012D9EDE0AA.cnf

 tftp-server gk123456789012 url system:/cme/sipphone/gk123456789012

 tftp-server gk123456789012.txt url system:/cme/sipphone/gk123456789012.txt

Step 12 Filenames of configuration files include the designated MAC address for the private IP telephone. Does the file list include a configuration file for the MAC accost of this phone?

•Yes—Become to next step.

•No—The create-cnf or create profile (phonation annals global) control was not issued. Use the advisable control to generate configuration files for this phone, so use the reset command to reboot this phone. If the problem persists, go to Step 15.

Step thirteen more arrangement: url

Use the more than system command to display the contents of the configuration profile for a particular Cisco Unified IP phone. The post-obit is sample output from this command displaying information in three different configuration files; SIP0009B7F7532E.cnf contains no information.

Router#            more arrangement:/cme/sipphone/XMLDefault.cnf.xml

Router#            more system:/cme/sipphone/SIP0012D9EDE0AA.cnf

image_version: "P0S3-07-4-00";

Router#            more than system:/cme/sipphone/SIP0009B7F7532E.cnf

Step fourteen Does the configuration file contain information required for this phone to annals?

•Yes—Go to next stride.

•No—The create-cnf file or create contour (voice annals global) command was not issued. Use the appropriate control to generate configuration files for this telephone, and then use the reset control to reboot this phone.

Step 15 evidence ephone
prove voice annals all

For SCCP phones: Utilize the bear witness ephone command to display information about the state of SCCP phones and locate the configuration information for this phone. The post-obit partial sample output shows registration information for the three IP phones.

ephone-ii Mac:000A.8A5C.5961 TCP socket:[1] activeLine:0 REGISTERED

mediaActive:0 offhook:0 ringing:0 reset:0 reset_sent:0 paging 0 debug:0

IP:192.168.0.50 50349 Telecaster 7940  keepalive 23738 max_line 2

button 1: dn 2  number 91450 CH1 IDLE      CH2 IDLE

ephone-5 Mac:123E.A432.987B TCP socket:[-one] activeLine:0 UNREGISTERED

mediaActive:0 offhook:0 ringing:0 reset:0 reset_sent:0 paging 0 debug:0

IP:192.168.0.51 52243 Unknown 0 keepalive 0 max_line 0

ephone-v Mac:1234.A432.987B TCP socket:[-1] activeLine:0 REGISTERED

mediaActive:0 offhook:0 ringing:0 reset:0 reset_sent:0 paging 0 debug:0

IP:192.168.0.52 50988 Telecaster 7940 keepalive 23 max_line 2

For SIP phones: Employ the show vocalism register all command to display data nearly SIP phones and locate the configuration data for this phone. The post-obit is a partial sample output showing vocalization register dn and vocalisation annals pool information for a telephone with the MAC address 123A.8A5C.5961.

Router#show phonation register all

VOICE REGISTER DN =================

VOICE REGISTER Pool ===================

Mac address is 123A.8A5C.5961

Proxy Ip accost is 0.0.0.0

keep-conference is enabled

Step 16 Locate the MAC address for this telephone in the command output. Is the correct MAC address configured for this telephone?

•Aye—Go to adjacent footstep.

•No—Right the configuration file.

Stride 17 Is the appropriate telephone or extension number associated with the (ephone) dn or pool tag for this phone?

•Aye—Utilize the restart command to reboot this phone. If the problem persists, go the next step.

•No—Right the configuration.

Stride 18 Copy and paste the valid configuration information, and then apply the reset command to reboot this telephone. If the problem persists:

a. Unplug this phone.

b. Delete the configuration for this individual phone.

c. Create a elementary, one-extension to ane-button, ephone or voice register pool configuration for this phone and then generate the configuration file.

d. Plug in this phone.

Pace 19 Did this phone successfully annals with Cisco Unified CME?

•Yes—Change the configuration for this telephone to add desired features and buttons.

•No—Contact technical support at http://www.cisco.com/techsupport.

Additional References

The following sections provide references related to Cisco Unified CallManger Express.

Technical Help


Description	Link
The Cisco Support website provides extensive online resource, including documentation and tools for troubleshooting and resolving technical bug with Cisco products and technologies. To receive security and technical information about your products, you can subscribe to various services, such as the Product Warning Tool (accessed from Field Notices), the Cisco Technical Services Newsletter, and Really Simple Syndication (RSS) Feeds. Access to near tools on the Cisco Support website requires a Cisco.com user ID and countersign.	http://www.cisco.com/techsupport

Obtaining Documentation, Obtaining Support, and Security Guidelines

For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and full general Cisco documents, run into the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at: http://world wide web.cisco.com/en/US/docs/general/whatsnew/whatsnew.html.

CCDE, CCENT, CCSI, Cisco Eos, Cisco Explorer, Cisco HealthPresence, Cisco IronPort, the Cisco logo, Cisco Nurse Connect, Cisco Pulse, Cisco SensorBase, Cisco StackPower, Cisco StadiumVision, Cisco TelePresence, Cisco TrustSec, Cisco Unified Calculating Organization, Cisco WebEx, DCE, Flip Channels, Flip for Good, Flip Mino, Flipshare (Design), Flip Ultra, Flip Video, Flip Video (Pattern), Instant Broadband, and Welcome to the Human being Network are trademarks; Changing the Way Nosotros Work, Live, Play, and Larn, Cisco Capital, Cisco Capital (Design), Cisco:Financed (Stylized), Cisco Store, Flip Souvenir Bill of fare, and One 1000000 Acts of Green are service marks; and Access Registrar, Aironet, AllTouch, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Lumin, Cisco Nexus, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, Continuum, EtherFast, EtherSwitch, Upshot Middle, Explorer, Follow Me Browsing, GainMaker, iLYNX, IOS, iPhone, IronPort, the IronPort logo, Laser Link, LightStream, Linksys, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, PCNow, PIX, PowerKEY, PowerPanels, PowerTV, PowerTV (Design), PowerVu, Prisma, ProConnect, ROSA, SenderBase, SMARTnet, Spectrum Proficient, StackWise, WebEx, and the WebEx logo are registered trademarks of Cisco and/or its affiliates in the Usa and sure other countries.

All other trademarks mentioned in this document or website are the property of their respective owners. The apply of the word partner does not imply a partnership human relationship between Cisco and any other visitor. (1002R)

Any Internet Protocol (IP) addresses used in this document are non intended to be actual addresses. Any examples, command display output, and figures included in the certificate are shown for illustrative purposes merely. Any use of actual IP addresses in illustrative content is unintentional and casual.
©2008-2010 Cisco Systems, Inc. All rights reserved.