Chapter 13 Maintaining and Troubleshooting Cisco Unified CME

Techniques you need to master:

image

Set up Cisco Unified CME to provide TFTP and FTP backup and restore capabilities

image

Activate, deactivate, and view Cisco Unified CME CLI debug commands

image

Use show commands to verify call-agent operation

After Cisco Unified CME is installed and operating, administrators must be able to identify and correct problems incurred for adds, moves, and changes. This chapter describes the protocols used to back up the Cisco Unified CME configuration.

This chapter also describes the use of show and debug commands. Using the CLI debug commands can impact call processing and should be used during low-call-volume periods and disabled when the troubleshooting issue is resolved.

Backup and Restore

There are two different protocols that you can use to back up Cisco Unified Communications Manager Express (CME): TFTP and FTP. Figure 13.1 is a typical setup for maintaining configuration backups.

Figure 13.1 Maintain and manage Cisco Unified CME configurations.

image

There are several TFTP and FTP freeware packages available to provide the TFTP and FTP services on a local PC. Listing 13.1 shows the interactive backup process.

Listing 13.1 Interactive Backup Process

CUCME# copy running-config tftp

Address or name of remote host []? 192.168.10.148
Destination filename [cucme-confg]?
!!
16123 bytes copied in 2.776 secs (5808 bytes/sec)
CUCME#


Listing 13.2 shows a single command to back up the configuration. This is useful for building configuration backup scripts for multiple devices. Make sure that you add two extra carriage return/line feed (CR/LF) combinations after the single line to bypass the host name and filename verifications.

Listing 13.2 Back Up the Configuration with a Single Command

srvrsw# copy running-config tftp://192.168.10.148/cucme-config-11-11-2008

Address or name of remote host [192.168.10.148]?
Destination filename [cucme-config-11-11-2008]?
!!
4553 bytes copied in 0.792 secs (5749 bytes/sec)
srvrsw#


You can use FTP to back up Cisco Unified CME configurations. As shown in Listing 13.3, the file transfer fails if you do not create an FTP username and password before attempting a transfer.

Listing 13.3 Failed FTP Backup

CUCME# copy running-config ftp

Address or name of remote host []? 192.168.10.148
Destination filename [cucme`-confg]?
%Error opening ftp://192.168.10.148/cmex-confg (Incorrect Login/Password)


You must create a valid FTP username and password and run it again, as shown in Listing 13.4.

Listing 13.4 Successful FTP Backup

CUCME (config)# ip ftp user backup
CUCME(config)# ip ftp password backup00!
CUCME(config)# ^Z
CUCME# copy running-config ftp

Address or name of remote host []? 192.168.10.148
Destination filename [cucme-confg]?
Writing cucme-confg !
16130 bytes copied in 8.460 secs (1907 bytes/sec)
CUCME#


Tip

Use the FTP service when you are uploading new IOS versions; the upload time is greatly reduced.

Exam Alert

Remember to use the FTP username and password for backing up and restoring configurations.

Troubleshooting the Cisco Unified CME Installation

Cisco Unified CME tends to operate without intervention after the appropriate installation features and functions have been configured, tested, and verified. In this section, we cover tools that you can use to make troubleshooting the installation much easier.

Initial IP Phone Activation and Registration Issues

One of the most common issues is to complete all the correct setups for telephony service, add the correct ephone-dns and ephones, and copy all the appropriate IP phone operating files to flash—and the phones still won’t operate. The debug tftp events command is one of the clearest methods for tracking the initial registration process. Listing 13.5 shows the output generated by an IP phone attempting and failing to retrieve its configuration file.

Listing 13.5 Debug TFTP Events

CUCME# terminal monitor
CUCME# debug tftp events

TFTP Event debugging is on
Sep 20 20:37:47.887: TFTP: Looking for CTLSEP00036BAAC71D.tlv
Sep 20 20:37:47.959: TFTP: Looking for SEP00036BAAC71D.cnf.xml
Sep 20 20:37:48.055: TFTP: Looking for XMLDefault.cnf.xml
Sep 20 20:37:49.399: TFTP: Opened system:/its/XMLDefault.cnf.xml, fd 7,

image size 2679 for process 65
Sep 20 20:37:49.419: TFTP: Finished system:/its/XMLDefault.cnf.xml, time 

image00:00:00 for process 65
Sep 20 20:37:49.555: %IPPHONE-6-REG_ALARM: 13: Name=SEP00036BAAC71D 

imageLoad=8.0(9.0) Last=CM-aborted-TCP
CUCME# no debug all


Exam Alert

If you telnet into the Cisco Unified CME router, don’t forget to use the terminal monitor command before entering your debug command. Use the terminal no monitor command and either the no debug all command or the undebug all command when you have solved the issue.

The four most common issues that prevent the IP phones from registering relate to the omitting the following commands, which are covered in more detail in Chapter 10, “Configuring Cisco Unified CME to Support Endpoints”:

image The load command under telephony-service

image The ip source command under telephony-service

image The create cnf-files command under telephony-service

image The tftp-server global commands for all the files required to activate the IP phone

The show telephony-service command can be used to verify the first three of the preceding issues, and the show run command can be used to verify the last issue.

Exam Alert

Verify these four issues because they typically are responsible for 80 percent of all IP phone registration errors when installing a Cisco Unified CME platform, either through omission or incorrect configuration.

The load command identifies the IP phone software image that is compatible with the current version of IOS software on the router:

telephony-service
. . .
 load 7931 SCCP31.8-3-3S
 load 7961 SCCP41.8-3-3S


Caution

These load commands reference a .loads file that must be configured to initiate the synchronization of the Cisco Unified CME IOS and the IP phone.

The ip source command creates the contact point for all TFTP and registration requests on the Cisco Unified CME host:

telephony-service
. . .
 ip source-address 10.6.150.1 port 2000


The create cnf-files and cnf-file perphone commands should be used to create a specific file for each phone to simplify troubleshooting a specific IP phone:

telephony-service
. . .
 cnf-file perphone
 create cnf-files


The tftp-server command activates the Cisco Unified CME TFTP process for a specific file. The newer Cisco IP phones have complex operating system files that are downloaded individually based on the instructions in the .loads file. Listing 13.6 shows the files required for a Cisco 7931 IP Phone.

Listing 13.6 Files Required for a Cisco 7931 IP Phone

tftp-server flash:/apps31.8-3-2-27.sbn alias apps31.8-3-2-27.sbn
tftp-server flash:/cnu31.8-3-2-27.sbn alias cnu31.8-3-2-27.sbn
tftp-server flash:/cvm31sccp.8-3-2-27.sbn alias cvm31sccp.8-3-2-27.sbn
tftp-server flash:/dsp31.8-3-2-27.sbn alias dsp31.8-3-2-27.sbn
tftp-server flash:/jar31sccp.8-3-2-27.sbn alias jar31sccp.8-3-2-27.sbn
tftp-server flash:/SCCP31.8-3-3S.loads alias SCCP31.8-3-3S.loads
tftp-server flash:/term31.default.loads alias term31.default.loads


Note

Verify these files using the release notes on Cisco.com for the Cisco Unified CME IOS version.

Common show Commands Used to Verify CUCME Operations

The following are samples of show commands used to troubleshoot and verify Cisco Unified CME operation.

show ephone

The show ephone command can provide basic or detailed information about an individual phone, all phones of a specific type, just the registered phone, and many other options. In Listing 13.7, not all phone types are shown to reduce the list of options for this command. Listings 13.7 through 13.9 show variations of the show ephone command.

Listing 13.7 The show ephone Command Option Output

CME# show ephone ?

. . .
  7911                     Cisco IP Phone 7911
. . .
  7941                     Cisco IP Phone 7941
. . .
  7961                     Cisco IP Phone 7961
  7961GE                   Cisco IP Phone 7961GE
  7962                     Cisco IP Phone 7962
  7965                     Cisco IP Phone 7965
. . .

  CIPC                     Cisco IP Communicator
  H.H.H                    mac address
  anl                      SCCP Gateway (AN)
  ata                      ATA  phone emulation for analog phone
  attempted-registrations  Attempted ephone list
  bri                      SCCP Gateway (BR)
  cfa                      registered ephones with call-forward-all set
  dn                       Dn with tag assigned
  dnd                      registered ephones with do-not-disturb set
  login                    phone login status
  offhook                  Offhook phone status
  overlay                  registered ephones with overlay DNs
  phone-load               Ephone phoneload information
  registered               Registered ephone status
  remote                   non-local phones (with no arp entry)
  ringing                  Ringing phone status
  sockets                  Active ephone sockets
  summary                  Summary of all ephone
  tapiclients              Ephone status of tapi client
  telephone-number         Telephone number assigned
  unregistered             Unregistered ephone status
  vgc-phone                vg248 phone emulation for analog phone
  |                        Output modifiers
  <cr>


Listing 13.8 The show ephone Command Output

CME# show ephone

ephone-1[0] Mac:001E.7AC3.9460 TCP socket:[1] activeLine:0 REGISTERED in 

imageSCCP ver 12/9
mediaActive:0 offhook:0 ringing:0 reset:0 reset_sent:0 paging 0 debug:0 

imagecaps:8
IP:10.1.3.34 49759 7961  keepalive 14383 max_line 6
button 1: dn 1  number 2101 CH1   IDLE         CH2   IDLE
Preferred Codec: g711ulaw
Username: abrown Password: cisco

ephone-3[2] Mac:001B.D508.6693 TCP socket:[3] activeLine:0 REGISTERED in 

imageSCCP ver 12/9
mediaActive:0 offhook:0 ringing:0 reset:0 reset_sent:0 paging 0 debug:0 

imagecaps:9
IP:10.1.3.32 52326 7931  keepalive 14457 max_line 24
button 1: dn 3  number 2103 CH1   IDLE
Preferred Codec: g711ulaw
Username: asmith Password: 123


ephone-4[3] Mac:4000.0000.1234 TCP socket:[-1] activeLine:0 UNREGISTERED
mediaActive:0 offhook:0 ringing:0 reset:0 reset_sent:0 paging 0 debug:0

 imagecaps:0
IP:0.0.0.0 0 Unknown 0  keepalive 0 max_line 0
Preferred Codec: g711ulaw


Listing 13.9 The show ephone registered Command Output

CME# show ephone registered

ephone-1[0] Mac:001E.7AC3.9460 TCP socket:[1] activeLine:0 REGISTERED in

image SCCP ver 12/9
mediaActive:0 offhook:0 ringing:0 reset:0 reset_sent:0 paging 0 debug:0
image caps:8
IP:10.1.3.34 49759 7961  keepalive 14385 max_line 6
button 1: dn 1  number 2101 CH1   IDLE         CH2   IDLE
Preferred Codec: g711ulaw
Username: abrown Password: cisco

ephone-3[2] Mac:001B.D508.6693 TCP socket:[3] activeLine:0 REGISTERED in

image SCCP ver 12/9
mediaActive:0 offhook:0 ringing:0 reset:0 reset_sent:0 paging 0 debug:0
image caps:9
IP:10.1.3.32 52326 7931  keepalive 14459 max_line 24
button 1: dn 3  number 2103 CH1   IDLE
Preferred Codec: g711ulaw
Username: asmith Password: 123


show ephone-dn

The show ephone-dn command provides detailed information on the configuration of each directory number assigned in the Cisco Unified CME to phones and features. Listings 13.10 through 13.12 show variations of the show ephone-dn command.

Listing 13.10 The show ephone-dn Command Options Output

CME# show ephone-dn ?

  <1-144>     dn tag
  callback    Show ephone-dn with pending callback set
  conference  Show ephone-dn in conference mode
  loopback    Show ephone-dn in loopback mode
  park        Show ephone-dn configured as park-slots
  statistics  Show ephone-dn most recent call statistics
  summary     Summary of all ephone-dn
  |           Output modifiers
  <cr>


Listing 13.11 The show ephone-dn Command Output

CME# show ephone-dn

50/0/1 CH1   IDLE         CH2   IDLE

EFXS 50/0/1 Slot is 50, Sub-unit is 0, Port is 1
 Type of VoicePort is EFXS
 Operation State is DORMANT
 Administrative State is UP
 No Interface Down Failure
 Description is not set
 Noise Regeneration is enabled
 Non Linear Processing is enabled
 Non Linear Mute is disabled
 Non Linear Threshold is -21 dB
 Music On Hold Threshold is Set to -38 dBm
 In Gain is Set to 0 dB
 Out Attenuation is Set to 0 dB
 Echo Cancellation is enabled
 Echo Cancellation NLP mute is disabled
 Echo Cancellation NLP threshold is -21 dB
 Echo Cancel Coverage is set to 8 ms
 Echo Cancel worst case ERL is set to 6 dB
 Playout-delay Mode is set to adaptive
 Playout-delay Nominal is set to 60 ms
         . . .


Listing 13.12 The show ephone-dn statistics Command Output

CME1# show ephone-dn 1 statistics

DN 1 chan 1 incoming 1 answered 0 outgoing 19 answered 14 busy 0
Far-end disconnect at: connect 1 alert 0 hold 0 ring 1
Last 64 far-end disconnect cause codes
0 16 28 19 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
local phone on-hook


The following URL defines cause codes:

http://www.quintum.com/support/xplatform/ivr_acct/webhelp/Disconnect_Cause_Codes.htm

show telephony-service

The show telephony-service command is used to verify the operation of the Cisco Unified CME call-agent. Listings 13.13 through 13.15 show variations of the show telephony-service command.

Listing 13.13 The show telephony-service Command Options Output

CME# show telephony-service ?

  admin                Show telephony-service admin username and password
  all                  Show telephony-service details
  bulk-speed-dial      Show Bulk Speed dial Info
  conference           Show telephony-service conferences
  dial-peer            Show telephony-service dialpeers
  directory-entry      Show telephony-service directory-entry
  ephone               Show ephone configuration
  ephone-dn            Show ephone-dn configuration
  ephone-dn-template   Show ephone-dn-template configuration
  ephone-template      Show ephone-template configuration
  fac                  Show Feature Access Code List
  tftp-bindings        Show telephony-service tftp-server bindings
  user-defined-locale  Show User Defined Locales
  voice-port           Show telephony-service voice ports
  |                    Output modifiers
  <cr>


Listing 13.14 The show telephony-service voice-port Command Output

CME# show telephony-service voice-port

voice-port 50/0/1
! Slot 50 is used to create EFXS ports to
 station-id number 2101
! represent ephone-dns.
 timeout ringing 10
!
voice-port 50/0/3
 station-id number 2103
 timeout ringing 10
!
voice-port 50/0/4
 station-id number 2104
!


Listing 13.15 The show telephony-service Command Output

CME# show telephony-service

CONFIG (Version=4.3(0))
=====================
Version 4.3(0)
Cisco Unified Communications Manager Express
For on-line documentation please see:
www.cisco.com/univercd/cc/td/doc/product/access/ip_ph/ip_ks/index.htm

ip source-address 10.1.150.1 port 2000
no auto-reg-ephone
load 7931 SCCP31.8-3-3S
load 7961 SCCP41.8-3-3S
max-ephones 42
max-dn 100
max-conferences 8 gain -6
dspfarm units 0
dspfarm transcode sessions 0
conference software
privacy
no privacy-on-hold
hunt-group report delay 1 hours
hunt-group logout DND
max-redirect 5
voicemail 2190
 —More—


Exam Alert

Use the show telephony-service command to verify the Cisco Unified CME version number because the additional phone image files and scripting files must be synchronized to this version.

Exam Prep Questions

1.

Which of the following commands is used to generate configuration files for the IP phones connected to a Cisco Unified CME host?

image

A.

config-generate

image

B.

create-cnf

image

C.

cnf-file perphone

image

D.

tftp-server <url>

image

E.

load <phone type> <filename>

2.

Which of the following protocols can be used to back up a Cisco Unified CME configuration to an external device? (Choose two.)

image

A.

FTP

image

B.

SCCP

image

C.

SMTP

image

D.

SIP

image

E.

TFTP

3.

If you turn on debugging from the CLI of the Cisco Unified CME and no output appears on the screen, which of the following commands could help?

image

A.

show debug output

image

B.

terminal monitor

image

C.

debug ephone

image

D.

show ephone

4.

Which of the following commands provides a list of all the Cisco Unified CME–registered IP phones?

image

A.

show ephone registered

image

B.

terminal monitor

image

C.

debug ephone registration

image

D.

show debug output

5.

Which of the following IOS CLI commands displays the Cisco Unified CME version number?

image

A.

show debug output

image

B.

show version

image

C.

show ephone

image

D.

show telephony-service

image

E.

show ephone-dn

6.

Which of the following commands are used to verify features programmed on ephone-dns? (Choose two.)

image

A.

show ephone-dn feature

image

B.

show ephone-dn park

image

C.

show ephone park

image

D.

show telephony-service

image

E.

show ephone-dn conference

7.

Which of the following commands can be used to verify three of the most common issues encountered during IP phone registration problems?

image

A.

show ephone-dn

image

B.

show voice-port

image

C.

show ephone registered

image

D.

show telephony-service

image

E.

show ephone unregistered

8.

Which of the following commands permits the user to view debug output over a Telnet connection the Cisco Unified CME device?

image

A.

telnet

image

B.

terminal no monitor

image

C.

tftp

image

D.

terminal monitor

Answers to Exam Prep Questions

1.

B. The create-cnf command under telephony-service generates configuration files for the IP phones connected to a Cisco Unified CME host. Answer A is an invalid command, answer C defines the type of configuration files generated, answer D provides access to the phone image files stored in flash, and answer E directs phones to the correct image control file that defines which image files should be downloaded, so these answers are incorrect.

2.

A and E. You can use FTP and TFTP to back up a Cisco Unified CME configuration to an external device. Answer C is incorrect because SMTP is an email protocol. Answers B and D, SCCP and SIP, are used for IP phone call control and are incorrect.

3.

B. The terminal monitor command helps you determine why no output appears on-screen. Answer A is an invalid command; answer C is used to troubleshoot ephone registration operations, and answer D is used to verify current ephone operational status as well as many other options and are incorrect.

4.

A. The show ephone registered command provides a list of all the Cisco Unified CME–registered IP phones. Answer D is an invalid command, answer B activates console message output for Telnet sessions, and answer C is used to troubleshoot ephone registration operations and are incorrect.

5.

D. The show ephone-dns command displays the Cisco Unified CME version number. Answer A is an invalid command, answer B displays the IOS version but not the Cisco Unified CME version, answer C displays the current information on all configured ephones, and answer E displays the information for all configured ephone-dns and are incorrect.

6.

B and E. These commands display the ephone-dns assigned to the conference and park features. Answers A and C are invalid commands, and answer D is used for an overview of all features, so these answers are incorrect.

7.

D. This command highlights the source IP address, phone load information, and the configuration file generation status. Answer A shows directory numbers, answer B is used for PSTN connections, answer C shows registered ephones, and answer E is an invalid command and they are all incorrect.

8.

D. The terminal monitor command is correct. Answer A is incorrect because it is used to establish the connection, answer B is incorrect because it is used to initiate a file transfer, and answer C is incorrect because it disables displaying debug output on a Telnet session.

..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset
3.149.252.238