Jabber for MAC - 11.9.3 - AutoUpdate via MRA fails

[Matthew Miktus]

Hi All,

Been struggling with this for a few days now. We're not using an IIS server. We're using a docker instance and have verified the escape characters are not an issue as far as I can tell.

Users inside the office both MAC and PC can use the AutoUpdate process without issue.  have had 30 successful Windows updates and 7 successful MAC updates.

Users outside the office, on Windows machines, via MRA, can use the AutoUpdate process without issue.  Have had 20 successful updates via MRA.

Users outside the office, on MAC, via MRA, fail outright.  

The files are hosted in the same repository, in the same directory.  The url is not publicly accessible.  It relies on MRA transmit the traffic from the outside.

Do I have to enable anything on the Expressway C http allow list to explicitly permit the installer by name?  or should the prefix "https://XXX-app-web01.XXX.com/jabber/distribution/" suffice?

Just can't figure out why only the MAC's are failing.

+++++++++++++++++ LOGS-n-STUFF +++++++++++++

SparkleUpdateLog.Log:

2018-04-24 16:07:28 +0000: Error: An error occurred while downloading the update. Please try again later. (null) (URL https://XXX-app-web01.XXX.com/jabber/distribution/Install_Cisco-Jabber-Mac-11.9.3.260116-70527108-MCwCFA5sCfezWL38rsAC8gYGbmA2RvvkAhQouAvlEacaNffPrh9+0hbEkbmxAg!!.zip)

Jabber-Update.XML:

<JabberUpdate>
<App name="JabberMac">
<LatestBuildNum>260116</LatestBuildNum>
<LatestVersion>11.9.3</LatestVersion>
<Message>
<![CDATA[<b>This will upgrade your client to the latest xxx Approved version. Please download and install this update at your earliest convenience. If you have any issues, please email <a href="mailto:help@xxx.com?Subject=Jabber 11.9.3 Upgrade Problem" target="_top">help@xxx.com</a> and open a service request. Thank you.]]>
</Message>
<DownloadURL>https://xxx-app-web01.xxx.com/jabber/distribution/Install_Cisco-Jabber-Mac-11.9.3.260116-70527108-MCwCFA5sCfezWL38rsAC8gYGbmA2RvvkAhQouAvlEacaNffPrh9+0hbEkbmxAg!!.zip</DownloadURL>
<AllowUpdatesViaExpressway>true</AllowUpdatesViaExpressway>
</App>
<App name="JabberWin">
<LatestBuildNum>60004</LatestBuildNum>
<LatestVersion>11.9.3</LatestVersion>
<Message>
<![CDATA[<b>This will upgrade your client to the latest xxx Approved version. Please download and install this update at your earliest convenience. If you have any issues, please email <a href="mailto:help@xxx.com?Subject=Jabber 11.9.3 Upgrade Problem" target="_top">help@xxx.com</a> and open a service request. Thank you.]]>
</Message>
<DownloadURL>https://xxx-app-web01.xxx.com/jabber/distribution/CiscoJabberSetup.msi</DownloadURL>
<AllowUpdatesViaExpressway>true</AllowUpdatesViaExpressway>
</App>
</JabberUpdate>

Help. 
Please and Thanks.

[Adam Pawlowski · Accepted solution]

I deployed this using the TFTP on the UCM to serve the files (:6972 HTTPS) and it seems to work appropriately over MRA. Perhaps it is something with the URL length or a character that's being encoded incorrectly via the Expressway? It would have to be allowed via the HTTP allow list, but, since you're indicating that your Windows clients are updating correctly then it seems like that must already be there?

[Matthew Miktus]

the HTTPS allow is already there, and the same host location is in use for both MAC and Win clients.  It has to be something the Expressway c/e is doing to the URL for mac's specifically. 

I really didn't want to use the CUCM TFTP for this but I guess I can give that a whirl.

Thanks for the response

[Matthew Miktus]

i'm going to mark this as a solution, and it works, but it's not the way I want to go.

So, thank you for your input here. I appreciate it.