Hello,
I'm having a problem with my client's Cisco Jabber service. When I log in from the mobile app over the internet (via Expressway), I get the message "Cisco Jabber could not connect to the server, internal server error" (see "Expressway"). I've traced all routes, DNS records, and firewalls on the client, but to no avail. I'll explain the steps the app takes to access the CUCM servers.
- Jabber user on mobile >> Internet >>> Cloud flare Public DNS >>> DDOS security solution Server ( In Local Network ) >>> Expressway-E 192.168.150.1 ( External DMZ ) >192.168.150.33 ( Internal DMZ ) >>> Expressway-C 10.10.10.8 >>> CUCM 10.10.10.4 and IMP 10.10.10.10
The customer also has an internal domain (example.com) and several subdomains (for example, ad.example.com - ad.example.com) under the main internal domain (example.com). The internal domain (example.com) also has the same name as the external domain (example.com). Our customer uses Infoblox solutions to manage their internal DNS. Their domain is ad.example.com.I also noticed some inconsistencies in the CUCM server records. and SRV Record
CUCM records are registered under the subdomain ad.example.com, and Expressway records are registered under the internal domain example.com. For example, when performing an NS lookup on the address 10.10.10.4 i see cucm-pub.example.com , these records appear to be registered under example.com, when in fact they are registered under ad.example.com .
I tried to log in via Cisco Jabber Desktop by manually setting the Presence server address to the cucm local user
jabber1@example.com, but I was unable to log in. However, when I used the same user and changed the domain to jabber1@ad.example.com, I was able to log in, although the URI was jabber1@example.com
Also, our customer uses Office 365 for email, while their domain ad.example.com is running on-premises, not in the cloud.
Also, when I used Cisco's Expressway packet analysis tools or checked the logs, the results seemed to make perfect sense.
