Three Issues Preventing Presence Status in Jabber Contact List

BCD.

References: http://www.cisco.com/c/en/us/support/docs/voice-unified-communications/unified-presence/97443-cups-cupc-ts.html.

Jabber is an instant messaging and presence application that allows users to communicate and collaborate with each other. Presence status is an essential feature in Jabber that enables users to see the availability status of their contacts, such as whether they are available, busy, or offline.

However, there can be several issues that prevent a customer from seeing the presence status of a new contact in their Jabber contact list. The three most common issues are as follows:

A. Incoming Calling Search Space on SIP Trunk to IM&P: If the incoming calling search space on the SIP trunk to IM&P is not configured correctly, it can prevent the presence status of a new contact from being displayed in Jabber. The calling search space determines which partition or route pattern is used to route the call, and if it is not configured correctly, the presence status may not be displayed.

B. IM&P Incoming ACL Blocking Inbound Status: If the IM&P incoming ACL is blocking inbound status, it can prevent the presence status of a new contact from being displayed in Jabber. The ACL determines which IP addresses or subnets are allowed to connect to the IM&P server, and if it is blocking the incoming status, the presence status may not be displayed.

C. Subscribe Calling Search Space on SIP Trunk to IM&P: If the subscribe calling search space on the SIP trunk to IM&P is not configured correctly, it can prevent the presence status of a new contact from being displayed in Jabber. The subscribe calling search space determines which partition or route pattern is used to route the subscribe message, and if it is not configured correctly, the presence status may not be displayed.

D. PC Cannot Resolve the FQDN of IM&P: If the PC cannot resolve the Fully Qualified Domain Name (FQDN) of the IM&P server, it can prevent the presence status of a new contact from being displayed in Jabber. The FQDN is the complete domain name of the server, including the hostname and domain name, and if the PC cannot resolve it, the presence status may not be displayed.

E. Owner User ID is Not Set on Device: If the owner user ID is not set on the device, it can prevent the presence status of a new contact from being displayed in Jabber. The owner user ID is the unique identifier of the user, and if it is not set correctly, the presence status may not be displayed.

F. Primary DN is Not Set in End User Configuration for that User: If the primary directory number (DN) is not set in the end user configuration for that user, it can prevent the presence status of a new contact from being displayed in Jabber. The primary DN is the main telephone number assigned to the user, and if it is not set correctly, the presence status may not be displayed.

G. Subscriber Calling Search Space is Not Defined on User's Phone: If the subscriber calling search space is not defined on the user's phone, it can prevent the presence status of a new contact from being displayed in Jabber. The subscriber calling search space determines which partition or route pattern is used to route the call, and if it is not defined correctly, the presence status may not be displayed.