External error Jabber clients - Cannot communicate with the server

[sprocket10]

We have had jabber working externally for clients and on mobiles. Recently we decommissioned a DC which seems to have caused issues so we recommissioned the DC again but since then Jabber is still not working externally for clients but will work internally. I am not sure if the DC was a cause for this issue or just a coincidence. I have gone through all the settings and everything seems to be correct.

[Mohammed al Baqari]

Can you specify what is not working?

[sprocket10]

When users try to use Jabber externally they get the error "Cannot communicate with the server"

Works internally though, and was working externally.

[Muaaz El Kamali]

You need to check firewall ports and external DNS SRV records.

Also Expressways zones and unified communication status

Regards,

Muaaz

[Christopher.Williams1]

I also have this issue where external users are getting the error "unable to communicate with the server". I checked the DNS records, and they are all still intact. I checked to make sure the server could talk to my internal network and that it could connect to the internet and that is all fine. Service records are also still intact. At this point the only alarm on the Expressway-E is a call license limit reached for traversal call licenses. That alarm is from 10/3/2016, so it isn’t recent.

[Muaaz El Kamali]

You can see in Expressway E logs if the users is hitting or not?