cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
963
Views
10
Helpful
1
Replies

Jabber XMPP federation - issue with dialback

I am having issue with my XMPP federation on expressway. It stopped working from the day i changed my expressway cluster (made the secondary peer as primary since my primary went fail). 

 

 

 

  • Verified the ports required for the XMPP (cross verified with Expressway Port usage guide) and it all looks good. 
  • XMPP error showing dial back error for my domain

2021-06-17T23:38:03.971+01:00 dc2-expressway-e XCP_CM2[19056]: UTCTime="2021-06-17 22:38:03,970" ThreadID="139774316418624" Module="cm-2.dc2-expressway-e-mydomain-net" Level="INFO " CodeLocation="ConnInfoHistory" Detail="Connection state change: PENDING->DIALBACK_FAIL: (11a7e6bc-0819-48a6-9569-299f9c1bd16e, mydomain:remotepartydomain, OUT) state=DIALBACK_FAIL created=2021-06-17T22:33:33Z connected=(NULL) idle_since=(NULL) end=2021-06-17T22:38:03Z is_tls=0 is_sasl=0 tls_failed=0 bytes(in=0, out=0) stanzas(in=0, out=0) bounced_pkts(in=0, out=0) bounced_wblist_pkts(in=0, out=0) piggy_base_conn=(NULL) num_piggies=0"

 

but the dialback from the remote domain to my domain is passed: 

 

2021-06-17T23:38:50.818+01:00 dc2-expressway-e XCP_CM2[19056]: UTCTime="2021-06-17 22:38:50,818" ThreadID="139774383756864" Module="cm-2.dc2-expressway-e-mydomain-net" Level="INFO " CodeLocation="DBVerify.cpp:282" Detail="(2b113ab0-c792-4b8a-b170-c9904ab146da, mydomain:remotepartydomain, IN) DBVerify Packet Received <db:verify from='remotepartydomain' id='060E3D1A7' to='mydomain' type='valid'>544d87632b1fd0bdc1894bffbf1dbfac56e4615a</db:verify>"

2021-06-17T23:38:50.818+01:00 dc2-expressway-e XCP_CM2[19056]: UTCTime="2021-06-17 22:38:50,818" ThreadID="139774383756864" Module="cm-2.dc2-expressway-e-mydomain-net" Level="INFO " CodeLocation="DBVerify.cpp:301" Detail="(2b113ab0-c792-4b8a-b170-c9904ab146da, ggr.net:wes.gdst.net, IN) Passed dialback first stage. packet-from: remotepartydomain, stored-from:remotepartydomain, packet-to: mydomain-net, stored-to: mydomain-net, packet-id: 060E3D1A7, stored-id: 060E3D1A7"

 

kind of stuck and dont know how to proceed it further. Please let me know if anyone can shed some lights here. 

1 Reply 1

Update:- the dial back showing successful now.
The XMPP was enabled on the internal domain defined in expressway C, I disabled it for the internal domain and enabled it for only the external domain. Then restarted the XCP in IM and Presence nodes. Now I can see in the XMPP logs (Expressway-E) that dial back state moved from pending to connected for my external domain.
But the issue still there were unable to relay the presence status and failing to send the messages.

Regards,