[cisco-voip] Jabber via MRA failover from one CUCM node to another

[Pawlowski, Adam]

They occasionally leak things through there but they’ve been pretty good about that lately.

I wanted to test and confirm the MRA failover between UCM nodes but we are rebuilding a part of our lab and MRA isn’t running right now.

Maybe later today.

I know for a fact that if you shut down the primary CM in the CMGroup the Jabber clients are assigned to, they won’t register. My guess is that this is not so much a Jabber limitation but one with the way the registration proxy works and how it configures itself for the client based on data it receives. The Expressway E doesn’t know about the state of the zones on the C back towards the UCM cluster.

But, like we’ve all figured out from trial and many, many errors, these things don’t always work in a way that makes sense, and then they’ve been developed into a hole that is hard to get out of.

That being said with Jabber’s development pretty much done, are they using JabberWerx with Webex Teams or are they spending more time on that code? The latter implies that this is why we don’t have multiline there yet, but who knows.

From: cisco-voip <cisco-voip-bounces at puck.nether.net> On Behalf Of Lelio Fulgenzi
Sent: Thursday, July 30, 2020 10:22 PM
To: Anthony Holloway <avholloway+cisco-voip at gmail.com>
Cc: cisco-voip voyp list <cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] Jabber via MRA failover from one CUCM node to another


What document is that?

Title?

Don’t share the confidential footer!

;)
Sent from my iPhone


On Jul 30, 2020, at 9:32 PM, Anthony Holloway <avholloway+cisco-voip at gmail.com<mailto:avholloway+cisco-voip at gmail.com>> wrote:

CAUTION: This email originated from outside of the University of Guelph. Do not click links or open attachments unless you recognize the sender and know the content is safe. If in doubt, forward suspicious emails to IThelp at uoguelph.ca<mailto:IThelp at uoguelph.ca>

Do you have access to this document?  It's limited to who can view it.

https://salesconnect.cisco.com/#/content-detail/8da1f8a8-1f29-4e56-bc09-eb43175a3bba

On Thu, Jul 30, 2020 at 7:20 PM Anthony Holloway <avholloway+cisco-voip at gmail.com<mailto:avholloway%2Bcisco-voip at gmail.com>> wrote:
" This is a surprise to me that this fundamental feature is still not supported after many years."

Are you new to working with Cisco solutions?

On Wed, Jul 29, 2020 at 12:02 AM Gerence Guan <cisco.guan at gmail.com<mailto:cisco.guan at gmail.com>> wrote:
Hi All,

I found this old post from Cisco community.
https://community.cisco.com/t5/ip-telephony-and-phones/jabber-softphone-via-mra-does-not-fall-over-to-secondary-cucm/td-p/2807099

Is this still true for Jabber 12.8, MRA 12.5 and CUCM 12.5?

In the MRA 12.6 deployment guide it says
Cisco Jabber clients support IM and Presence Service failover over MRA. However, they don't support any other type of MRA-related redundancy or failover—including SIP, voicemail, and User Data Services (UDS). Clients use a single UDS server only.
https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/expressway/config_guide/X12-6/exwy_b_mra-expressway-deployment-guide/exwy_b_mra-expressway-deployment-guide_chapter_01.html


In the Jabber 12.8 planning guide, it says High Availability(failover) of audio and video service is not supported
https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/12_8/cjab_b_planning-guide-cisco-jabber-128/cjab_b_planning-guide-cisco-jabber-128_chapter_010.html

If anyone has a MRA lab, can you please help to test it buy just disconnect the first cucm node in the jabber's ccm group and verify whether jabber can register to the second node in the ccm group?

This is a surprise to me that this fundamental feature is still not supported after many years.

Best Regards
Guan

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20200731/2b6faf83/attachment.htm>