AREAS OF TROUBLESHOOTING:=========================1)CALL MANAGER2)VOICE CLIENTS3)NETWORK INFRASTRUCTURE4)UNITYCALL MANAGER:==============Troublshooting is done in Cisco unified servicabilityAlarm:=======Alarm is found in main tab in unified serviceabilityAlarm has two sub tabsConfiguration:--------------Set an alarm and define the alarmwhich server --->Subscriber or Publisher.Servic Group---->e.g CM servicesservice -------->e.g Cisco Call ManagerLocal syslog :Is for Local system and set the Alarm Event LevelIn Alaram Event level ----> serveral options -->1)Debug 2)Emergency 3)Error 4)Warning 5)Notice 6)Informational 7)criticalRemote Syslog:This for remote server.SDI Trace:ALARM DEFINITION:=================you can define the Alarn in the definition.TRACE:======Trace found in main tab in unified serviceabilityyou can download the traces:ANALYZER:=========Any service Activation can be done by go to Uified servicability ---->tools ----------> service Activation.Go in Unified serviceability ----->Tools-------->Service Activation---->cisco Dialed number AnalyzerTools------>Analyzer----> u can set the calling party and then set the Dialed digit settingsWhen u set calling party all the properties are inherited(i.e COR)CONTROL CENTRE:===============You can restart , stop and start the service. It also tell you how much time the service is up.SYSTEM CLI TROUBLESHOOTING:===========================utils system shutdownand there is commnads for system statsVoice log Translator ---> a free available tool for analyzing the logs----> it will state the protocol information.After collecting the SDI Trace open it with the voice log translator.IP-PHONE BOOT PROCESS:======================Switch is going to detect the unpowered phone by the two methods below and supply powerINLINE POWER802.3af POEPhone boots the software imageSwitch provides the VLAN information for the ip-phone by CDP.Phone sends the DHCP request which is broadcasted in the VLAN.DHCP server receving it responds with the ip address, default gateway, TFT IP Address(DHCP option 150 shpould be set).Phone retrieves the configuration file for the phone from the TFTP.Phone contacts the CCM server configured in the configuration file.How to check in the switch the phones connected:================================================show cdp neighbours-----> this will tell u the phones connected.show cdp entry SEP* --->this will list out the configuration file and the phone typeTROUBLESHOOTING STEPS IN END POINT REGISTRATION:================================================1)Network configuration ----check in the switch phones connected using cdp.2)IP configuration problem(Manual or DHCP based) ----> sh run | begin dhcp---> check default router, dns server, tftp server ip address is set3)TFTP server---> check in Tools ---> service activation --->tftp server activated.4)Call manager service5)Bad configurfation file or firmware-------> go to the Cico unified CM administration website--->Device--->Device settings-->device defaults-->check the load information.6) All the above steps u have checked but a particular phone is not registering then delete the phone configuration and create the configuration again.TROUBLESHOOTING FROM THE PHONE:===============================1)Reboot the phone using **#** and for unlocking the phone use **# used for setting the ip.2)Watch the status messages --->settings------>status.(status messages are used to troubleshoot the phones)search the cisco ip phone status messages in google--->in the cisco website they will give reason for the status messages.3)Verify the IP Address.In the network settings u can check the VALN. Which VLAN the phone is?4)RESET the configuration---->select the Network settings and unlock the phone--->u will get an option Erase then it will erase the Network configuration.(in some phones)NOTE: Cisco CallManager disables auto-registration by default in order to prevent unauthorized connections to your network. If you must turn on auto-registration, complete the steps that the Auto-Registration guide outlines.If your IP phones still fail to auto-register after you complete the instructions in the Auto-Registration guide, reset the IP phone back to factory defaults:1. Press **# in order to unlock Network Configuration on the phone.2. Press Settings.3. Press 3 on the keypad (or scroll down) for Network Configuration.4. Press 33 on the keypad (or scroll down) for Erase Configuration.5. Press the Yes softkey.6. Press the Save softkey.TROUBLESHOOTING FROM THE CALL MANAGER:======================================1) Ping the phone from the call managerfrom cli:utils network ping ip-addressfrom gui:cisco unified OS administration---->services--->ping2)Restart the service--call Manager3)Create New configuration filedelete the phone and recreate it.TROUBLESHOOT SIP DEVICES:=========================Ensure that SIP device using the SIP firmware.CALL MANAGER SERVER OPERATION TROUBLESHOOTING:===============================================in cli of Call Manager:show perf query counter process "% CPU Time %" --show the process and its utilization.CALL MANAGER SERVER IS SLOW:============================CHeck in siwcth for speed and duplex mismatches.Check for process utitlization and memory leaks--Rebooting the server may fix the problemCheck for potential dos attack on the server---->using wireshark.DATABASE REPLICATION ISSUES:=============================CALL MANAGER 3 -->SQL 7 databaseCALL MANAGER 4---->SQL 2000CALL MANAGER 5,6,7 --->IBM INFORMIX In CM 3 and 4 --->subscriber database is Read only and publisher database is Read and Write.wheras in 5,6,7--->user features are made read and write in Subscriber alsotat is partially read and write for subscriber database.One more difference: every request is received in subscriber is forwarded to publisher for verifying in call manager 3,4 not in 5,6,7HOW TO IDENTIFY DATABASE REPLICATION IS NOT HAPPENING:======================================================1)Changes to the ip phone configuration doest not apply.2)Call forwarding doest not work3)Speed dial doest not work.4)EXtension mobility doest not work.TOOLS FOR TROUBLESHOOTING:==========================call amanger 4 --Sql toolsCall manager 5,6,7 --Real time monitoring tool and the CLIIn the Real time monitoring tool --->performance--->Number of replicates created.in the CLI--->utils dbreplication status--->This command should be run from the publisher server.it will be dispalyed like the status is the file.To view the file u need to use the below command.file view activelog filepath/name.txtdb replication repair ---it will repair database relation with the subscriber.MONITOR A PORT IN SWITCH USING ANOTHER PORT:============================================Scenario is PC connected to port 0/23 in switch and Voice router is connected to port 0/6to Monitor the port 0/6 and send it to port 0/23 use the commnadsmonitor session 1 source interface 0/6monitor session 1 destination interface 0/23.TROUBLESHOOTING COMMON ISSUES:==============================TROUBLESHOOTING IN CLI:-----------------------show status --->uptimeshow perf query class Memory or Prosessorshow perf query counter Process % CPU Timeshow perf query counter Process Process Statusshow perf query counter Partition % Used --disk usageNetworking commands:--------------------show network status --network statusDatabase commands:------------------show tech databaseshow tech dbinuseshow tech tables Basic Utilities:----------------utils system restart --reboot the server.checking the trace files from the CLI:---------------------------------------file list activelog cm --->this commnad will list the directories in the cmfile list activelog cm/trace/ccm/sdi/ --->this directory contains the sdi traces.Cisco Unified Serviceability provides trace tools to assist you in troubleshooting issues with your voice application. Cisco Unified Serviceability supports SDI (System Diagnostic Interface) trace, SDL (Signaling Distribution Layer) trace (for Cisco CallManager and the Cisco CTIManager services), and Log4J trace (for Java applications). RTMT(Real time Monitoring tool)===============================Installation:In Cisco Unified CM administration --->Application-->plugins--->RTMTSystem history Log:-------------------You can access the system history log by using the CLI file command; for example: file view install system-history.log file get install system-history.logDifferent types of traces:--------------------------TracesThis section is where you configure the traces that can assist you in troubleshooting. They are trace configurations and troubleshooting traces. You can configure three types of traces: SDI, SDL, and Log4j. The trace configuration option you pick has a big impact on the information you will receive and how much time you will probably spend during problem resolution. The files can be viewed in RTMT: You are probably wondering how to choose between a trace and troubleshooting trace. The following table lists the main difference between these two.Trace types include the following:stem diagnostic interface (SDI) or signal distribution layer (SDL) trace log files SDI:-------- Runtime events for the related software IP address Time stamp Device name SDL:------- Call processing from Unified Communications Manager and Cisco CTI Manager Services. Used by Cisco TAC engineers. Normal administrators provide this information to them only upon request. NOTE Traces affect system performance, so use them only for troubleshooting purposes. If you want to practice traces, use a nonproduction system. In addition, SDL traces can be more difficult to read than SDI. Therefore, you usually start with SDI traces to find logs related to CUCM issues. Log4J:----------- Used for Java applications To configure a trace, follow these steps: Select the server. Select the service group from the drop-down. Select the service. Check the trace boxes you want. Click Save.SDI AND SDL:------------An SDL Trace log file contains call-processing information from services such as Cisco CallManager, Cisco CTIManager, and Cisco TFTP. The system traces the signal distribution layer of the call and logs state transitions into a log file.An SDI Trace log file contains information for all Cisco Unified CallManager services. The system traces system diagnostic interface information from the services and logs run-time events and traces to a log file. Cisco Call Manager Problems:============================Device Issues:--------------1) Voice quality:=================check the codec used and also the VAD is enabled or notDisable the VAD or Silence compression in voice gatewayDisable the service in Cisco Unified Communications Manager Administration, and choose System > Service Parameters --->silent suppression2) One way voice:=================An improperly configured Cisco IOS gateway, a firewall, or a routing or default gateway problem, among other things, can cause this problem.Action: Make Sure IP Routing is Enabled on Cisco IOS Gateway/Routersvoice-ios-gwy(config)#ip routingCheck the following conditions:-------------------------------Default gateways configured at the end stationsIP routes on the default gateways, mentioned above, leading to the destination networksOther conditions needs to be checked in gateway:------------------------------------------------Bind the H.323 Signaling to a Specific IP Address on Cisco IOS Gateway/RoutersWhen the Cisco IOS gateway has multiple active IP interfaces, some of the H.323 signaling may use one IP address for course, and other parts of it may reference a different source addressesh323-gateway voip bind srcaddr . Configure this command under the interface with the IP address to which the Cisco Unified Communications Manager pointsNoteIf your Cisco Unified Communications Manager is using a TCP port for skinny signaling that differs from the default 2000, you need to adjust the NAT router with the ip nat service skinny tcp port global configuration command.Disable voice-fastpath on AS5350 and AS5400--------------------------------------------no voice-fastpath enable --for disablingWhen enabled, this command caches the IP address and UDP port number information for the logical channel that is opened for a specific call and prevents the RTP stream from getting to the application layer, but rather forwards the packets at a lower layer. This helps marginally reduce CPU utilization in high-call-volume scenarios.When supplementary services, such as hold or transfer are used, the voice-fastpath command causes the router to stream the audio to the cached IP address and UDP port, disregarding the new logical channel information that was generated after a call on hold was resumed or a transfer was completed.Verification:-------------A useful command to verify packet flow specifies debug cch323 rtp. This command displays packets that the router transmits (X) and receives (R). An uppercase character indicates successful transmission/reception whereas a lowercase character indicates a dropped packet. See the following example:3) Echo:--------input gain on the voice port4)Codec and Region mismatches: when a call goes from one device to another check the region and the codecs assigned between them.5)Dropped calls:---------------Determine whether this problem is isolated to one phone or to a group of phonesCheck the Syslog Viewer in the Cisco Real-Time Monitoring Tool (RTMT) for phone or gateway resets.You will see one Warning and one Error message for each phone that resets. This indicates that the phone cannot keep its TCP connection to the Cisco Unified Communications Manager alive, so the Cisco Unified Communications Manager resets the connection.If the call is going out of a gateway to the PSTN, you can use the CDR to determine which side is hanging up the call.6)Voice Messaging Stops After 30 Seconds----------------------------------------To resolve this problem, verify that the Media Gateway Control Protocol (MGCP) is being used on the voice gateway.If the MGCP is being used, add the no mgcp timer receive-rtcp commandIf MGCP is not on the voice gateway, enable Skinny traces for the Cisco Unity server and Cisco Communications Manager traces.7)Call Manager Features and services:-------------------------------------Call park issues:The call park number does not display long enough for the user. set the parameter( System ---->Service parameters---->Call Park Display Timer = )User cannot park calls. When the user presses the Park softkey or feature button, the call does not get parked.Soln: Ensure that a unique call park number is assigned to each Cisco Unified Communications Manager in the clusterThe partition that is assigned to the call park number does not match the partition that is assigned to the phone directory number.Key is not active:Configure a voice-messaging pilot in the user voice-messaging profile.