A company-wide rollout of any new application including Cisco Jabber can be fraught with challenges that may or may not be readily apparent to the organization. Even small issues can potentially jeopardize the success of an entire project. For this article, we will look at how proper planning and modeling can help eliminate these issues before they become big.
In this third article, we will expand upon what we learned in part 1 and part 2 regarding Jabber and how to renew your CA-signed certificates. In this final article, we will examen the certification process within Cisco Expressway.
It is important to note that for Jabber Mobile and Remote Access (MRA) feature as well as for Business to Business calls (B2B), it is mandatory to have a CA-signed certificate on the Expressway-Edge node. On the other hand, there is no such requirement for Expressway-Core. However, Stack8 recommends a CA-signed certificate to be used on both Expressway servers.
Another requirement is to cross upload all Root and Intermediate certificates on both nodes in order for the Secure Traversal Zone to be active and communication between two Expressway nodes to work.
Do not forget to verify, every time you renew your certificates, if there is a change on the Root or any of the Intermediate certificates and Upload all new chain certs in the Trusted Certificates section of the server.
Cisco Jabber gives you and your team the freedom to be productive from anywhere, on any device. Jabber enables you to access presence, instant messaging (IM), voice, video, voice messaging, desktop sharing, and conferencing Instantly.
Apple is scheduled to introduce in its next major iOS release (after iOS 10 anticipated September 2017), a significant change that removes APIs that are required for handling calls and IM’s when the application is running in the background. What this means is that if Jabber is not opened in the foreground, the user will not be notified of incoming calls and IM messages.