[cisco-voip] CUPC - Unable to go into deskphone control mode and unable to chat
Jeffrey Girard
jeffrey.girard at girardinc.com
Fri Mar 14 18:11:31 EDT 2014
Home Lab - learning Presence
CUCM 9
CUPS 9 (not 8.6 as virtually all of the help and discussion forums, documents, etc are for)
CUPC 8.6 (3 copies running on 3 different laptops)
4 users configured in CUCM for Presence capabilities
No LDAP integration
Current status:
Presence indicators for phones works fine, no issues
3 users can log into their CUPC clients and Presence information from their own associated deskphone displays correctly (ie if User 1 takes his deskphone offhook, the CUPC for User 1 shows as "On the Phone"
Users can place phone calls with each other by typing the DN in the "Search for name or number" field
I have two different issues that I have not been able to solve all day - they may be related to each other.
The first issue: I am unable to go into deskphone mode. Although the checkbox is visible - it appears to be greyed out and clicking in it does nothing.
The second issue: I am unable to start a chat session. I highlite a contact (that I manually entered), right click, and select chat. I get an error message that says "Failed to start conversation. Invalid parameter"
I have scoured the Cisco site for docs and most of them pertain to CUPS 8.6 and not 9. There is a difference in that v9 does not have the Application -> IP Phone Messenger selection.
My current configs:
CUCM
4 application users - CUPS-AXL (with Stand CCM SuperUsers permissions), CUPS-Deskphone, CUPS-CTIGW, and CUPS-PhoneMSG (all with Standard CTI Allow control of all devices).
3 end users - From top to bottom, all users have passwords and digest credentials. Under Service Settings, all users have the "Enable user for Unified CM IM and Presence" checked. This is the replacement for the assigning license capabilities from version 8.6. Also under Service Settings, all users have a UC Service Profile assigned. The UC Service Profile has two UC service settings - a Presence and IM Profile and a CTI Profile. Under Device Information - all user have been associated to two different devices (their hardphone and the CUPC client). Under the Directory Number Association portion - each user has their own primary line selected from the drop down box. Under the Permissions Information section - each user has Standard CCM End Users and Standard CTI Enabled permissions.
Devices - each user has a 7960 hard phone and a CUPC. For each device (both types) at the Device Level -> Owner User ID, Protocol Specific Information -> BLF Presence Group, SUBSCRIBE CSS are all set. Under the line for each device (both types) - Allow control of device from CTI is checked, in the Associated Devices window is the MAC and UPC<name> of the devices, Under Users Associated with Line is the correct user
Under System -> Application Server, the CUP server is configured.
Under System -> Licensing, all users and devices are licensed. There is no Capabilities Assignment in version 9
CUPS
Under Diagnostics -> System Troubleshooter -> all green except for the things not configured, LDAP, 3rd party, etc
User Management -> End User -> are licensed for IM and Presence and have Microsoft RCC enabled. They also show 2 devices
Under Application - this is where its different from v8 to v9.
Application -> Legacy Clients -> Settings. I have set the TFTP server IP to the CUCM
Application -> Legacy Clients -> CCMCIP Profile. I created a new profile, set the Primary and Secondary CCMCIP Host to be the IP Address of the CUCM Publisher. For Server Certification Verfication, I selected Any Certificate from the drop down. I assigned this profile to all 4 of my users.
Application -> Microsoft RCC settings. Application status = on. For Application Username and password, I have tried using CUPS-Deskphone and CUPS-CTIGW with their appropriate passwords. There is not difference in using either one of them. CUCM address is address of my Pub. I assigned this Microsoft RCC service to all 4 of my users.
So, as I said, I have been working on this all day today burning my fingers and my mouse up on Google. To no avail.
Any ideas anyone?
Jeff
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20140314/341969d2/attachment.html>
More information about the cisco-voip
mailing list