CUP6+CUCM6 Presence: Away/DND/OnPhone status works, Available does not
Hey gang, I am trying to nail down this last gremlin in my CUPS build. CUCM 6.1 on MCS7800 with 7970 and 7960 phones: the IPPM works, status works, on hook BLF etc all good. CUPS 6.0.5 on VMWare: Troubleshooter all green, LDAP replication appears good (bound to AD, as is CUCM). CUP Client: logs in all green, can make calls, link to desk phone, etc. CUP client sees "On the Phone" status as well.
The problem is mainly that while "On the Phone" and "Away" and also custom "Away" messages work perfectly in CUP Client, and in IPPM. However, "Available" does not work on any CUP client (mac/windows). If i choose Available (on the Mac Client), it is displayed on the client for 5-10 seconds before reverting to "No Presence". The windows client will not let me choose Available at all.
I have been fiddling with the SIP trunk but it seems to work in both directions for all status except Available. Has anyone seen this?
Re: CUP6+CUCM6 Presence: Away/DND/OnPhone status works, Availabl
OK I managed to solve this today. It turns out there was an issue with the user-Agent config on the CUPS. The "reachability version" of my (recent) CUPC UAs was incorrectly set to version 1 rather than version 2. Once this change was made, all missing (available, idle) status info began updating properly.
Note this was for CUPC v1.2.3 (Mac) and CUPC v1.2.4 (Win32).
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...