This document describes problems that might occur when Jabber connects to Unity Connection. Jabber has the capability to connect to Unity Connection and for users to be notified of new messages and to check messages.
There are no specific requirements for this document.
The information in this document is based on these software versions:
Unity Connection Release 10.0.1
Unity Connection Release 9.1.x
Unity Connection Release 8.6.2
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.
When you run Jabber in Windows, Jabber reports an issue with not being able to check messages via the Jabber interface. If you restart Jabber, then you are notified of messages and can check messages for approximately 24 hours. After 24 hours, you are no longer notified of messages. If you restart Jabber again, the application works successfully for an additional day but does not work correctly after that day.
Restart Jabber when the notification does not work. This is a problem with Unity Connection. The issue is now addressed by a Unity Connection defect. See Cisco bug ID CSCuo46274.
You might need to open a TAC case to obtain an Engineering Special (ES) for your version until such time a Service Update is released that contains this fix. If you know the defect when you open the case, this should expedite the time it takes you to receive the fixed version.