topic I just picked up a service in Collaboration Applications

Jabber for Iphone update version 11.6.0.235651 64-bit - Unable to connect phone services internally

cgoodale2 — Mon, 18 Mar 2019 01:05:40 GMT

Dear All,

We have been using all versions of jabber clients for at least two years both internally and externally with expressway with little or no issues.

On May 3rd 2016 all the IPhones received the 11.6.0.235651 64-bit update and all of a sudden not one of them can connect to Phone services on the CUCM. Externally via expressway all works fine. Has anyone else seen an issue like this?

I just picked up a service

Joseph Hardy — Wed, 11 May 2016 17:57:09 GMT

I just picked up a service request with these same symptoms today. I have not diagnosed the cause of the problem yet. You are not the only one experiencing this symptom. I suggest opening a TAC service request and sending them a copy of the Jabber problem report. Do not send the problem report to this public forum :).

Make sure the "Clusterwide

john_byers — Thu, 12 May 2016 17:51:39 GMT

Make sure the "Clusterwide Domain Configuration" in enterprise parameters is either blank or set to the correct domain. This was not referenced on the older clients.

Make sure the "Clusterwide

john_byers — Thu, 12 May 2016 17:51:56 GMT

Make sure the "Clusterwide Domain Configuration" in enterprise parameters is either blank or set to the correct domain. This was not referenced on the older clients.

I have placed a TAC call but

cgoodale2 — Thu, 12 May 2016 19:05:08 GMT

I have placed a TAC call but not getting very far with support. They think its an iphone issue but I have the problem on many different iphones but the same jabber build.

Checked. I have had the

cgoodale2 — Thu, 12 May 2016 19:07:47 GMT

Checked. I have had the domain in there as I knew this was an issue from before. The only thing I can think is somewhere in the new ip6 options they have added or they are using a different DNS call.

that's the exact same problem

john_byers — Thu, 12 May 2016 19:08:59 GMT

that's the exact same problem I had. Changing the "Clusterwide Domain Configuration" fixed my issue on all clusters

Jut been told this morning...

cgoodale2 — Fri, 13 May 2016 16:58:56 GMT

Jut been told this morning...

And I quote "

There is an FQDN check with 11.6 so that most DNS lookups for telephony are done FQDN. "

We currently have the CUCMS using hostname. Will make a change over the weekend and see what happens.

So just to close this out.

cgoodale2 — Thu, 02 Jun 2016 15:46:20 GMT

So just to close this out.

The host name change did not help.

The fix since we have both MRA for external jabber as well as use internal jabber and we have two different domains (.net internal .com external) was in fact to change the Clusterwide Domain as mentioned above.

We needed to change the domain from the .com to the .net and then add the .net domain to the Expressway C for CM , IM and P to allow internal jabber to work

Note:- This did not break any certs that were in place, which was my next fear.

Thanks