Ensure user is associated with the line number In CUCM, browse to the CSF device (or desk phone) which is being controlled in Jabber Open its properties and click into the line numbers properties Ensure the user is correctly associated with the line (scroll to bottom of page) Ensure SIP trunk from CUCM to CUP exists Under CUCM – Device – Trunk, ensure a SIP trunk to CUP server exists If not, add one Possible DNS issue…? In  CUP, hostnames are used in the ‘incoming ACL’ and ‘Outgoing ACL’  sections to add security exceptions for ports used for CUCM  communication (including off hook presence). Eg. Browse to: System->Security-> Incoming ACL System->Security-> Outgoing ACL And  in each you will see a DNS name entry for your CUCM server. If there  are issues resolving these DNS names on your network, the security  exceptions will be ignored, so you need to ensure that if you ping the  name of your CUCM server from CUP, it is resolved to the correct IP. More  importantly, you need to ensure that a reverse lookup can be performed  on the IP address and the correct DNS name is returned. Explanation from CUP server point of view why off hook presence might not be working: The SIP Proxy on CUP will perform a reverse lookup of the source IP address of the CUCM publish to get it’s DNS hostname It then uses this to find a matching entry in the ACL list. If it does not find a matching entry then the request will not be accepted. If all else fails.. On CUP, go to: System->Security-> Incoming ACL System->Security-> Outgoing ACL You should see a list of your existing ‘address patterns’, one of which will be the DNS name of your CUCM server Instead of using the DNS name, change this to the IP address of your CUCM server If  this works, this proves that there is a DNS issue, and you should  ideally resolve this rather than using this as a permanent solution ... View more

Problem description Audio and video calls automatically terminate. Problem details A known bug exists with Microsoft Windows 7 or Windows Server 2008 R2 that causes the network profile to change unexpectedly. This change in the network profile closes certain network ports that Cisco Jabber requires for calls. As a result, if you are on a call when the network profile changes, that call terminates automatically. Resolution Apply the hotfix available from the Microsoft support site at: http://support.microsoft.com/kb/2524478/en-us ... View more

Problem description Audio and video calls automatically terminate every 20 to 30 minutes. Problem details A known bug exists with Microsoft Windows 7 or Windows Server 2008 R2 that causes the network profile to change from Domain to Public. This change in the network profile closes certain network ports that Cisco Jabber requires for calls. Resolution Apply the hotfix available from the Microsoft support site at: http://support.microsoft.com/kb/2524478/en-us ... View more