This document describes the steps to troubleshoot the upgrade failure from version 8.6.x to 10.5.x Trace analysis and troubleshooting. Analyse the Install logs for the below mentioned snippet. ******************************* 02/12/2015 22:31:07 ntp_one_shot.sh|ntpdate query response: server 10.12.224.20, stratum 16, offset -28803.414297, delay 0.02576 12 Feb 22:31:07 ntpdate[26957]: no server suitable for synchronization found (rc=1).|<LVL::Info> 02/12/2015 22:31:07 ntp_one_shot.sh|File:/usr/local/bin/base_scripts/n tp_one_shot.sh:286, Function: ntpdateError(), NTP server sviucmpb01 did not reply as expected.  'ntpdate -q' failed (ntpdate rc=1).|<LVL::Error> 02/12/2015 22:31:07 networkFaultTolerance.sh|-d|<LVL::Debug> 02/12/2015 22:31:07 ntp_one_shot.sh|File:/usr/local/bin/base_scripts/n tp_one_shot.sh:611, Function: setTime(), The primary node NTP server, sviucmpb01, did not respond (rc=1).|<LVL::Error> 02/12/2015 22:31:07 InstallWizard|runScriptPassive: 512 = system("/usr/local/bin/base_scripts/ntp_one_shot.s h")|<LVL::Debug> ******************************* 02/12/2015 22:31:09 InstallWizard|runScriptPassive: correcting rc per system/script call; returning rc=50|<LVL::Debug> 02/12/2015 22:31:09 InstallWizard|Error 50 occurred while adding sviucmpb01.|<LVL::Warn> 02/12/2015 22:31:09 InstallWizard|Security password = Passed -- L2|<LVL::Info> ******************************* 02/12/2015 22:31:10 InstallWizard|Security configuration OK|<LVL::Info> 02/12/2015 22:31:10 InstallWizard|Internal Error, File:installWizMain.c:697, Function: main(), /usr/local/platform/conf//platformConfig.xml field validation failed during a system upgrade|<LVL::Critical> 02/12/2015 22:31:10 post_install|Exiting with result 1|<LVL::Info> *******************************   This is because one of the NTP server in CUCM is not reachable.   As a work around we need to remove the multiple NTP server entries from CUCM and keep only one good entry. Once the upgrade is done, we can add the remaining good entries as this only affects the upgrade. ... View more

Introduction This document describes the steps to troubleshoot Computer Telephony integration (CTI) device registration issue in Cisco Unified Attendant Console Advanced edition server.   Requirement Cisco recommends that you have knowledge of the following topics. Cisco Unified Attendant Console Cisco Unified Communication Manager.   Component Used All devices used for testing were configured with clear and default configurations in LAB environment. Cisco Unified Attendant Console Advanced Edition Release 10.5.2 Cisco unified Call Manager Release 10.5.2   Troubleshooting steps:-   AC Webadmin page CUCM connection test under AC webadmin>>Engineering>>CUCM Connectivity should succeed.   CTI port and template information should be populated under AC webadmin>>System Configuration>>Queue Device Group>>System Device Management.   The maximum internal device digit length should be set as per the CTI device plan. AC webadmin page>>User Configuration>>General Properties.   Attendant Console Server TAPI Service Provide (TSP) should be updated as per the current Call manager version.     Account information should be populated correctly with the application user created in Call manager and should match to AC webadmin page>> Engineering>>CUCM Connectivity.     CTI manager information should match the Call manager IP address.     The above CTI Manager preference sholud be based on the Call Manager group preference set on the CTI template, Call Manager GUI>>Device>>Phone>>Search for CTI template>>Device Pool details>>Call Manager Group.   Recommended New Media driver should have the correct should have the correct UDP port range (50000 to 51019).     Remove the wave driver if installed under System>>Device Manager.     Enable DEP for essential Windows programs and services only under Control Panel>>System and Security>>System>>Advanced System Settings>>System Propertis>>Advanced>>Performance>>Settings>>Performance Option>>Data Execution Prevention.     Telephony should be set to Automatic under Services.   Firewall should be turned off under Control Panel>>All Control Panel Items>>Windows Firewall. Go to Run>>Dialer>>Tools>>Connect Using, if the CTI ports are not present under Line drop down menu then the TSP is faulty.   Cisco Unified Communications Manager (CallManager) 1) Under User Management>>Application User, Application User Configuration should have the following roles:- Standard AXL API Access Standard CTI Allow Calling Number Modification Standard CTI Allow Call Park Monitoring Standard CTI Allow Control of All Devices Standard CTI Allow Control of Phones supporting Connected Xfer and conf* Standard CTI Allow Control of Phones supporting Rollover Mode* Standard CTI Allow Reception of SRTP Key Material Standard CTI Enabled     2) CTI template used for the CTI devices should have a unique not registered DN assigned to it.   3) Common Device Configuration assigned to the CTI template should have the IP addressing mode set to IPv4 only.   NOTE:- After checking the above steps, please run Synchronize with CUCM from AC webadmin page>>System Configuration>>Synchronize with CUCM.   If this does not resolves the issue and registers the CTI ports and route points.   Please Uninstall TSP from AC (Windows server)   Download the correct version of TSP from Call manager GUI>>Application>>Plugins   Delete the CTI port DN’s from CUCM GUI>>Call Routing>>Directory Number   Delete the CTI ports from CUCM>>Device>>Phone   Delete the CTI route points from CUCM GUI>>Device>>CTI Route Point   Install TSP in Attendant Console (Windows server)   Run Synchronize with CUCM from AC webadmin page>>System Configuration>>Synchronize with CUCM. ... View more