After installing Cisco UAC Advanced the Cisco Unified Attendant Server is stuck at initializing, then reverts to service stopped. You will also just see the Engineering and Help Menu when logged in via Web Console.
Resolution
1. Run the TSP install, this should be located in the Desktop. (The installation process places this file here)
2. Restart the Server.
3. After restart the Cisco Unified Attendant Server service should be in a running state.
Calling Party’s Name is not passed through carriers, only the Calling Party’s phone number is passed through. This results in having the caller-id display as a phone number on an Internal Phone. In some cases I’ve had requests to setup a handful of key PSTN/Mobile phone numbers to resolve from phone number to display name. Below is how an example configuration piece on a Cisco IOS Gateway that I configure to resolve phone numbers to display names.
voice class sip-profiles 10
request INVITE sip-header Remote-Party-ID modify “(<sip:00408842426@.*>)(.*)” “\”Ben Morgan\” \1\2″
dial-peer voice 9500 voip
description Mobile-Name-Conversion
destination-pattern ^4… *** Internal Extension Range
session protocol sipv2
session target ipv4:192.168.0.1 **** CUCM Subscriber Host
voice-class codec 1
voice-class sip profiles 10 **** References above SIP Profile
dtmf-relay rtp-nte
no vad
I come across an issue within a CUCM 10.5 environment with a 7945/65 IP Phone. The UC Cluster has a range of phone models varying from 7940/60s to 8851′s.
When the Phone Services button was pressed on a 7945 or 7965 IP Phone, the phone service subscriptions would list correctly, however the phone continued to request for subscriptions, the phone display would show “requesting…”, eventually timing out and displaying a “Host Cannot be Found” error.
However, if the phones services button was pressed on a 7940 phone, the phone service subscriptions would list and the request would complete. This was the same for 7941, 7942, 7962 etc.. Also the 8851 phones would also display the subscriptions correctly under the Settings Menu.
I captured the packets between the 7945 IP Phone and CUCM to see what was going on. The phone was sending a secure request over port 8443. However in the Enterprise Parameters page, the secure URL for Phones Services was entered as http:// and not https://. Normally this would fine except the tcp port also entered was 8443 and not 8080 (non-secure). I changed the Secure Phones Services URL to https:// and the 7945 and 7965 IP Phones would then display the correct Phones Services subscriptions and the requesting service would complete with no errors.
Since the introduction of Cisco’s Collaboration Edge environment, I’m seeing more of a requirement to modify the Ring No Answer Duration timer under the Users Line to a timer above 20 seconds. This is because, by the time the signalling routes to the Jabber Mobile Device, the default Ring No Answer Duration timer has a couple of seconds remaining before expiring and forwards the call to an alternate destination, which is voicemail in most cases. I have found between 20 – 24 seconds is a balanced ground between, not having the phone ring too long at the desk and allowing the Jabber Mobile Device enough time for the user to answer the call.
To change the default the Ring No Answer Duration in CUCM, go to the Service Parameters and navigate to ‘Forward No Answer Duration’. Default is 12 seconds. Modify this parameter to 20 seconds.
To download Music on Hold WAV files from CUCM follow the below CLI commands. This will download all MoH WAV files on the CUCM to your SFTP Server. Once downloaded, you are able use the ‘ulaw’ wav file to upload to a different CUCM Server.
admin:file list activelog mohprep
CiscoMOHSourceReport.xml Test-AudioTrack_01_2009.alaw.wav
Test-AudioTrack_01_2009.g729.wav Test-AudioTrack_01_2009.ulaw.wav
Test-AudioTrack_01_2009.wb.wav Test-AudioTrack_01_2009.xml
Test-AudioTrack_17_2009.alaw.wav Test-AudioTrack_17_2009.g729.wav
Test-AudioTrack_17_2009.ulaw.wav Test-AudioTrack_17_2009.wb.wav
Test-AudioTrack_17_2009.xml Test-IPCCHold_20secs_2009.alaw.wav
Test-IPCCHold_20secs_2009.g729.wav Test-IPCCHold_20secs_2009.ulaw.wav
Test-IPCCHold_20secs_2009.wb.wav Test-IPCCHold_20secs_2009.xml
SampleAudioSource.alaw.wav SampleAudioSource.g729.wav
SampleAudioSource.ulaw.wav SampleAudioSource.wb.wav
SampleAudioSource.xml
dir count = 0, file count = 21
admin:file get activelog mohprep
Please wait while the system is gathering files info …done.
Sub-directories were not traversed.
Number of files affected: 21
Total size in Bytes: 44978093
Total size in Kbytes: 43923.918
Would you like to proceed [y/n]? y
SFTP server IP: 172.20.20.20
SFTP server port [22]:
User ID: ben
Password: ********
Download directory: /
The authenticity of host ’172.20.20.21 (172.21.30.31)’ can’t be established.
RSA key fingerprint is 0c:86:dd:98:e4:76:52:ac:a6:92:d8:97:8c:8c:df:31.
Are you sure you want to continue connecting (yes/no)? yes
…………………
Transfer completed.
UCCX Agent receives the below error ” Login failed due to a configuration error with your phone and JTAPI or Unified CM. Contact your Administrator” when logging into UCCX.
All CUCM and UCCX configuration looks to be correct, the user was successfully logged into CAD the day before. The Agents phone is currently logged in and registered.
Collect the MIVR Logs using RTMT. To do this open RTMT Tool against the UCCX Server and Select Traces and Alerts. Then select Collect Traces. Select the ‘CCX Engine’ for the log type and ‘All UCCX Server’. Click Next twice and select an appropriate location to download the logs too.
Unzip the .gz log files using 7zip application. Then open the MIVR Logs using Notepad++. Search for the Agent’s username. You should see similar output to the below. (username is bdodd)
Cause:
This is caused by an Agent moving between phones. The DEVICE NAME is the above trace output is not the phone the Agent is logged onto today. The CTI or JTAPI caches the Device the Agent successfully logged onto last. If the Agent is an Extension Mobility user, its best to only add the Device Profile to the RMCM Application User’s CTI Controlled Device list.
To Resolve:
Remove the old device from the RMCM Application user. You may also have to resync JTAPI in UCCX and restart the CTI Manager to force the change if the problem continues.
Just a quick note for deploying UC Applications on Windows 2012 within VMware environment. The NIC type E1000e which is the default when configuring a Virtual Machine will cause intermittent networking issues with a Windows 2012 Server.
When deploying the Virtual Machine, you will need to select the NIC type VMXNET3. This NIC type will work well with Windows 2012.
Cannot log into Jabber from any device, the “please enter you password for webex” prompt appears in Jabber even though you are attempting to log into a local presence domain.
PC Jabber logs Snippet.
INFO [0x00001a04] [s\impl\system\CredentialsSyncer.cpp(116)] [CredentialsSyncer] [CredentialsSyncer::Impl::syncCredentials] – sync Credentials for : WebEx
If Jabber finds its given Domain in the WebEx Cloud, then it will only attempt to register to the WebEx Cloud for IM and Presence and not the Local IM and Presence Cluster. This is how Jabber is designed.
To resolve the issue, the given Domain name must be removed/unregistered from Webex Cloud. If this cannot be done for any reason then follow one or more of below methods to overcome the issue.
1) Use EXCLUDED_SERVICES=WEBEX during the Jabber for Windows client installation with the MSI:
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/10_6/CJAB_BK_C56DE1AB_00_cisco-jabber-106-deployment-and-installation-guide/CJAB_BK_C56DE1AB_00_cisco-jabber-106-deployment-and_chapter_01011.html#JABW_RF_A47E40C4_
e.g.
msiexec.exe /i CiscoJabberSetup.msi /quiet CLEAR=1 EXCLUDED_SERVICES=WEBEX
2) A mobile Jabber client can click on the following URL (from an Email for example):
ciscojabber://provision?ServicesDomain=resmed.com&ServiceDiscoveryExcludedServices=WEBEX
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/11_0/CJAB_BK_D657A25F_00_deployment-installation-guide-jabber-110/CJAB_BK_D657A25F_00_deployment-installation-guide-jabber-110_chapter_0100.html#CJAB_TK_C0B6538A_00
3) Use ServiceDiscoveryExcludedServices, and specify WEBEX, in a configuration file (group or the global jabber-config.xml file):
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/11_0/CJAB_BK_D657A25F_00_deployment-installation-guide-jabber-110/CJAB_BK_D657A25F_00_deployment-installation-guide-jabber-110_chapter_01010.html#CJAB_RF_CAA78385_00
e.g.
<?xml version=”1.0″ encoding=”utf-8″?>
<config version=”1.0″>
<Policies>
<ServiceDiscoveryExcludedServices>WEBEX</ServiceDiscoveryExcludedServices>
</Policies>
</config>
Download the correct version for the AU Language Pack from the Microsoft website.
Have access to the Exchange install files and ensure the install files are the correct SP version of Exchange.
Restart the Microsoft Exchange Unified Messaging service.
Navigate to the Dialplan properties in Exchange UM Role.
Navigate to the settings tab, then select the Default Language drop down box and select English Australia.
After configuring Cisco Unity Connection 10.5 with Single Inbox (Exchange 2007). The exchange CAS Server starting throwing the event log ”
Unable to send a notification for subscription GwBhdTJlbWwyazcwMS5jb3JwLnJlc21lZC5vcmcQAAAABimsqT/fhkiUE13QqEeQVA==. (Send attempts: 4)” every second. This then starting causing performance issues in relation to the EWS and WEB service with Exchange.
Also, when leaving a voice message, the initial wav attachment would be delivered successfully, however, no updates could be sent. Example, If the voice message was read, or deleted from both Unity Connection or Outlook.
All Exchange permissions were confirmed, local rights, impersonation etc. All these looked to correct. The Unity Connection Unified Messaging configuration was checked, again everything seemed to be correct.
The notification packets were indeed leaving the Exchange Server toward the Unity Connection, however what was discovered with the notification packet was the Cisco Unity Server labelled “netbios_name” and not the FQDN of the Cisco Unity Connection Server. Therefore the Cisco Unity Connection server was not responding to the notification from Exchange as it could not resolve its own name (netbios_name).
Straight to the Cluster Configuration Menu to check the server names.. And as I suspected the server names were not in FQDN format.. I corrected these server names and rebooted the two Cisco Unity Connections to be flush out the cache.
I then configured the CsMbxsync Trace settings from 10 to 22 in Cisco Unity Connection Serviceability page. Downloaded the Mailbox Sync logs from RTMT and verified messages were passing to and from Exchange and Unity Connection. Ran a test voicemail and sync in both directions worked ok.
EVENT in Application Log
==============================================
Unable to send a notification for subscription GwBhdTJlbWwyazcwMS5jb3JwLnJlc21lZC5vcmcQAAAABimsqT/fhkiUE13QqEeQVA==. (Send attempts: 4)
==============================================
Log Name: Application
Source: MSExchange Web Services
Date: 8/20/2015 9:39:13 AM
Event ID: 6
Task Category: Core
Level: Warning
Keywords: Classic
User: N/A
Computer: SERVERNAME.Domain.org
Description:
Unable to send a notification for subscription GwBhdTJlbWwyazcwMS5jb3JwLnJlc21lZC5vcmcQAAAABimsqT/fhkiUE13QqEeQVA==. (Send attempts: 4) Event Xml:
<Event xmlns=”http://schemas.microsoft.com/win/2004/08/events/event”>
<System>
<Provider Name=”MSExchange Web Services” />
<EventID Qualifiers=”32768″>6</EventID>
<Level>3</Level>
<Task>1</Task>
<Keywords>0×80000000000000</Keywords>
<TimeCreated SystemTime=”2015-08-19T23:39:13.000Z” />
<EventRecordID>12558510</EventRecordID>
<Channel>Application</Channel>
<Computer>SERVERNAME.Domain.org</Computer>
<Security />
</System>
<EventData>
<Data>GwBhdTJlbWwyazcwMS5jb3JwLnJlc21lZC5vcmcQAAAABimsqT/fhkiUE13QqEeQVA==</Data>
<Data>4</Data>
</EventData>
</Event>