I have two running ejabberd servers and am trying to test federation (s2s) between the two of them. Lets call them server A and B and assume they serve domains A and B respectively.
Server B is running, has ejabberd_s2s_in started on port 5269 and I have setup the relevant SRV records. I added domain B to the list of hosts in server A but, when connecting to server A and trying to send packets directed at a user on domain B, I am not seeing any trace indicating that server A is attempting to initiate an s2s connection. I am sure there is some obvious problem here but, I can't for the life of me figure out what it is. Is there some config option that needs to be present in the config for server A other than adding domain B to its list of hosts? Any help would be appreciated
Realized I was doing a few
Realized I was doing a few things wrong here. I didnt have SRV records for both domains and I didnt have s2s_in started for both. I've fixed this and I see it getting further but, still not working. When ther I am logged into tries to send a message to the other server, I see the following line of trace over and over again:
2013-11-14 04:30:36.529 [info] <0.2139.0>@ejabberd_logger:info_msg:11 (actually from ejabberd_s2s_out:352) Closing s2s connection: beta-xmpp-barker.beta.djrd.dowjones.net -> beta-xmpp-barker-djx.beta.djrd.dowjones.net (close in wait_for_stream)
Ive confirmed through telnet that I can connect to 5269 from one machine to the other. I also believe the certs to correct and match the domain. Anyone know whats wrong?