Expressway 8.5 adds the capability to add Unity Connection directly to the Expressway Unified Communications configuration. This gives Jabber mobile and remote access clients the ability to manage voicemail messages via HTTPS to the VMREST(CUMI) API.
In previous versions of Expressway we had to manually add the Unity Connection servers to the HTTP allow list. With this version once we add Unity Connection it automatically updates the HTTP allow list.
A caveat to be aware of similar to the CUCM and IM&P caveat is if you’re using host names or IP addresses for the “System -> Server” setting. In many cases your Unity Connection server is going to be defined by hostname which is default. The thing to note is if your Unity Connection is hostname only and you add this to Expressway your HTTP allow list is going to be incorrect. Expressway will detect hostname only and add only the hostname to the HTTP allow list.
So what’s the fix? Change your Unity Connection server value to FQDN. If you’re running a cluster this does have a little impact where you’ll need to restart services but if it is a single node you can make this change without impact.
Once Unity Connection server value is FQDN go ahead and add or refresh the server on Expressway and the HTTP allow list will update correctly. Just one of the little nuances if you head down this road on Expressway and Jabber MRA cannot connect to voice mail.