CMS xmpp server connection error

[danny.yf_li]

Hi all

      I have a single combined CMS VM. When I set the xmpp  server setting on webadmin page, the xmpp server address must be filled in ,in order to get xmpp server connected. In Cisco deployment guide, it says that if the xmpp server field is  blank, the cms will make a dns srv record query for _xmpp-client._tcp

and find the xmpp server automatcailly. I do have the srv record on my dns server. I made dns query for the SRV record via cms cli with no problem. But everytime, if I clear the xmpp server address field, the xmpp connection fails.  What could be the root cause?

Thanks!

[Stephen Carr]

what domain is the callbridge querying under? Does it match the xmpp SRV record DNS entry's domain.

ex:

"_xmpp-client._tcp. cms.domain.com 86400 IN SRV 10 20 5222 xmpp.cms.domain.com"

where xmpp.cms.domain.com is the A record for your xmpp IP\interface and cms.domain.com is your XMPP domain

Steve

[danny.yf_li]

hi Steve

    Thanks for your comment. The SRV record is _xmpp-client._tcp.conf.demo.com (under sub domain) and this record resolve to A record xmpp.demo.com (xmpp / call bridge ) on primary domain.

I used "DNS lookup SRV _xmpp-client._tcp.conf.demo.com" in cli and cms can resolve the A record and the ip address of my (xmpp/call bridge) server ip address.

So I think the SRV and A record are both correct . But it just doesn't work if I leave XMPP server address field blank under xmpp server configuration on webadmin page.

If I specify the xmpp server address as 127.0.01:5223 or the FQDN of  cms server . say xmpp.demo.com ,the xmpp connection will be successful immediately.

[Stephen Carr]

It looks like you aren't using the sub domain for your xmpp server itself. They need to match
Steve

[danny.yf_li]

Thanks steve!!

[Jaime Valencia · Accepted solution]

That's because you're using the wrong SRV, _xmpp-client is used by CMA and Web Bridge to locate a server running XMPP, not by Call Bridge to locate the XMPP server to register to.

See page 83

https://www.cisco.com/c/dam/en/us/td/docs/conferencing/ciscoMeetingServer/Deployment_Guide/Version-2-2/Cisco-Meeting-Server-2-2-Scalable-and-Resilient-Deployments.pdf

If you only have one server, there is really no point in doing it the way you want, and just adds an unnecesary failure point, not pointing to the XMPP statically in the config.

[danny.yf_li]

Thanks  Jamie,

            The SRV record _xmpp-component._tcp  works.  

[Jaime Valencia]

Can you let me know which guide you were following that said to use the SRV for the single combined server?

[Hafthor Hilmarsson O'Connor]

---

@Jaime Valencia wrote:

Can you let me know which guide you were following that said to use the SRV for the single combined server?

---

Not sure if there is one, but I found out that if the xmpp-client is missing in the DNS , CMS 2.6 atleast give you an error in logs and says.

No DNS A or AAAA records for _xmpp-component._tcp.example.com

not sure if the _xmpp-component. part is needed in the new deployments , however I have never used them in a single deployment pre 2.6