Jabber Failed Update over MRA

[Ammar Saood]

Jabber on Windows 11.x used to update perfectly over MRA in X8.7.

after upgrading Expressway to x8.8 or x8.9 jabber devices over MRA are unable to update. it fetches the Jabber-update.xml  file and pops up that there is an update available but the update process does not start.

even tried moving CiscoJabberSetup.msi and Jabber-update.xml file to CUCM TFTP server still no luck.

even ports 6970 and 6972 ports are allowed in HTTP allow list.

can anyone help me what ports jabber uses to download and update ciscojabbersetup.msi file or what exactly need to be allowed on Expressway C allow list to make it happen ?

Thanks

[ruudvanstrijp]

I have exactly the same issue. Update.xml is in the same folder as CiscoJabberSetup.msi, and since the XML file can be read by the external Jabber (11.8.0), it seems the Expressway (8.9.2) HTTP rules are configured properly.

Jabber.log throws the following error:

2017-04-04 09:10:54,356 INFO [0x0000266c] [ls\src\http\BasicHttpClientImpl.cpp(452)] [csf.httpclient] [csf::http::executeImpl] - *-----* HTTP response code 0 for request #44 to http://100.64.8.60/JabberUpdate/CiscoJabberSetup.msi
2017-04-04 09:10:54,356 ERROR [0x0000266c] [ls\src\http\BasicHttpClientImpl.cpp(457)] [csf.httpclient] [csf::http::executeImpl] - There was an issue performing the call to curl_easy_perform for request #44: HOST_UNREACHABLE_ERROR

I have a feeling it's not properly tunneling this download through MRA but it's trying to reach the IP address directly. I cannot install Wireshark on this remote machine, so I cannot test this theory.

[Sankar Voleti]

If the issue still persists, please add <AllowUpdatesViaExpressway>true</AllowUpdatesViaExpressway> in jabber-config.xml file and try again. We have seen this issue lately and it seems that the above parameter needs to be added mandatorily in xml file for auto updates from versions 11.7 and above via MRA.

[j.huizinga]

The statement has to be added to the xml file used for updates

And on expressway C you have to whitelist this server

[j.house]

this resolved my issue...thanks

[nmartinez3]

There are significant changes in behavior when upgrading collaboration edge to x8.8. The release  notes state that Reverse DNS is Required for UC Nodes and Expressway-E Nodes. If you haven't already done so, can you try adding a Reverse DNS record for the VCSE on Internal DNS and then Flushing the DNS Cache on the Expressway-C.

[ruudvanstrijp]

Thanks, but (reverse) DNS is set up properly on my side, else the rest of MRA would fail as well.

[Paul Freiberg]

Hi @ruudvanstrijp

do you resolved the issue?

I added the parameter <AllowUpdatesViaExpressway>true</AllowUpdatesViaExpressway> to me jabberconfig.xml but without access.

I added the Server, which is my CUCM and is whitelisted because of the CUCM dicovery, with an explicit and later with a prefix match without success.

I installed a very old Jabber version and found the access on the update file in the expressway logs.

With 11.8.x or 11.9.x I do not see it in the logs. It seems that the client does not use the MRA tunnel to access the file.

[ruudvanstrijp]

Hi Paul,

Our Jabber-config.xml only contains the update URL:

<UpdateUrl>http://10.11.12.13/JabberUpdate/update.xml</UpdateUrl>

This update.xml file contains the AllowUpdatesViaExpressway setting:

<?xml version="1.0" encoding="utf-8"?>
<JabberUpdate>
<LatestBuildNum>57740</LatestBuildNum>
<LatestVersion>11.9.2</LatestVersion>
<DownloadURL>http://10.11.12.13/JabberUpdate/CiscoJabberSetup.msi</DownloadURL>
<AllowUpdatesViaExpressway>true</AllowUpdatesViaExpressway>
</JabberUpdate>

The update.xml file is hosted on a third-party server, not on CUCM itself.

Our Expressway has an Editable inbound rule for http traffic to this 10.11.12.13 host on port 80, with Prefix as type and /JabberUpdate/ as path.

Hope this helps :)

[Paul Freiberg]

Many thanks,

yes finally it works.

I had to add to add

<AllowUpdatesViaExpressway>true</AllowUpdatesViaExpressway>

 to the jabber-update.xml. And here between the Windows App part.

<App name="JabberWin">
<LatestBuildNum>55740</LatestBuildNum>
<LatestVersion>11.9.2</LatestVersion>
-<Message>
<![CDATA[ For more information click <a target="_blank" href="http://cisco.com/go/jabber">here</a>. ]]>
</Message>
<DownloadURL> https://publisher.mydomain.com:6972/CiscoJabberSetup_11_9_2.msi </DownloadURL>
<AllowUpdatesViaExpressway>true</AllowUpdatesViaExpressway>
</App>
</JabberUpdate>

[Slavik Bialik]

This post is intrigued my curiosity. What is it about? Upgrading Jabber over MRA, what does it mean? I'm not even familiar that there's an option to upgrade Jabbers in the organization (if that's what it is about).

I hate not knowing something that has to do with Expressways and MRA, heh.

Is there some documents about it?

Thanks.

[Paul Freiberg]

Hi @Slavik Bialik,

I think you know the common way to update your Jabber 4 Win und 4 Mac.

https://www.cisco.com/c/en/us/support/docs/unified-communications/unified-communications-manager-callmanager/200119-Configure-CUCM-TFTP-for-Jabber-Automatic.html

Now, your TFTP Server is in a private network which is not NATed. In the jabber-config.xml you just added the URL to that Server, how should your client remote reach your network if it do not use a VPN connection.

https://www.cisco.com/c/dam/en/us/td/docs/voice_ip_comm/expressway/config_guide/X8-10/Mobile-Remote-Access-via-Expressway-Deployment-Guide-X8-10.pdf

Page 36 - About the HTTP Allow List on Expressway-C

And I cannot open the jabber-config.xml in the Jabber diagnostic window (STRG + Shift + D) because it is also linked to the Server in a not NATed private network...