Jabber for Windows 10.5 and global redundancy

[gabriel.caclin]

Hi All,

I implement J4W 10.5 in a full redundant environment, that contains:

- 3 x CUCM 10.5

- 2 x Unity Connection 10.5

- 2 x IM&P 10.5

- 2 x Expressway-C 8.2.2

- 2 x Expressway-E 8.2.2

After testing, I notice that the redundancy/failover does not act the same way depending the product, sometime no.

As it is not clearly stated in the documentation, what is clearly supported as automatic failover, and what's not, when using Jabber for Windows 10.5?

In my first test, I saw that Jabber does not support failover with UnityConnection: if the primary peer is down, no more voicemail on Jabber.

If jabber run in Mobile and Remote Access, and the Expressway where it's conencted goes down, it doesn't switch to the other peer.

It will be good to have a document that relate all the redundancy and failover support with Jabber, what can we expect during the failover process.

It will help a lot of people.

Thanks

Gabriel

[Jaime Valencia]

You should reach your SE/AM about this so it's considered.

[gabriel.caclin]

Yep, that's what I did now.

But keep in mind this is not really explained, even if crossing all the documentations.

There is no document explaining what behaviour to expect in Jabber in case of redundancy of all the UC components.

For the CUCM, it's not clear, and nothing is mentionned in case of MRA.

IM&P is documented, but nothing for MRA.

Expressays states about redundancy, but the behaviour to expect is not. Same for XMPP federation, no idea.

UnityConnection as well, nothing is explained.