IM and Presence Service now supports the advertisement of XMPP stream features/services to the clients connecting over Cisco
Expressway's Mobile and Remote Access.
This new functionality enables deployments with mixed IM and Presence Service versions, for example some clusters on 11.5(1)SU8
and some other clusters on 12.5(1)SU3, to work with Cisco Expressway so that Cisco Jabber clients can discover the correct
capabilities applicable to it based on the IM and Presence Service home cluster it is assigned to.
For this mechanism to work, the minimum deployment requirement is to have Cisco Expressway running version X12.7 or higher
and have at least one IM and Presence cluster in the intercluster mesh running version 11.5(1)SU9 or 12.5(1)SU4 and above.
Depending on your current IM and Presence Service version mix, you may need to enable or disable push notifications feature
using FCM service flag on the Expressway as per the information given in the following table:
xConfiguration XCP Config FcmService: On/Off
Note |
Apple Push Notification Service (APNS) is not affected by the FCM service flag status.
|
Table 1. Solution Matrix from the Perspective of Expressway CLI Enable/Disable Command for Android Push Notifications (FCM)
Mixed Versions IM and Presence Clusters
|
Expected Status of FCM Flag on Expressway X12.7
|
Comment
|
Any 11.5(1)SU with
12.5(1)SU2 and lower
|
OFF
|
Android Push (FCM) NOT supported.
|
11.5(1)SU8 (and lower) or 12.5(1)SU2 (and lower) with 12.5(1)SU3
|
OFF
|
Android push (FCM) NOT supported
|
11.5(1)SU8 (and lower) or 12.5(1)SU2 (and lower) with 12.5(1)SU4 (and higher)
|
OFF
|
Android push (FCM) supported on 12.5(1)SU4 (or newer) versions
|
11.5(1)SU9 (and higher) or 12.5(1)SU4 (and higher) with 12.5(1)SU3
|
ON
|
Android push (FCM) supported on version 12.5(1)SU3 and higher
|
11.5(1)SU9 (and higher) with 12.5(1)SU4 (and higher)
|
Flag not required
(Expressway 12.7 relies fully on the new discovery mechanism)
|
Android push (FCM) supported on 12.5(1)SU4 (or newer) versions
|