[ejabberd] server dialback port

Alexey Shchepin alexey at sevcom.net
Wed May 18 03:51:16 MSD 2005

Hello, Gaston!

On Tue, 17 May 2005 13:23:48 -0300, you said:

 GD>  Hi, I'm trying to communicate another server with ejabberd 0.7.5 using
 GD> server dialback. Since I'm running both servers in the same PC I changed
 GD> the default ports to the following values:

 GD> Ejabberd: {5269, ejabberd_s2s_in, [{shaper, s2s_shaper}]}
 GD> {outgoing_s2s_port, 5369}

 GD> The other server: listening at 5369 for incoming connections

 GD> I now connect with a client (Exodus) to ejabberd and add a new contact to
 GD> the roster whose domain matches the domain of "the other server". I see
 GD> that ejabberd creates a socket to the other server and sends the key to
 GD> validate. The problem is that "the other server" tried to connect to the
 GD> port 5269 for validating the key and after it sent a "db:verify" packet to
 GD> ejabberd, ejabberd answered a bad-formed-xml stream error.

 GD> I'm now assuming that ejabberd is using the port 5269 for establishing new
 GD> server dialback connections and not to act as an Authoritative Server. So
 GD> my question is which port is ejabberd using when acting as the
 GD> Authoritative Server?

No, "xml-not-well-formed" is sended only when expat parser returns "parse
error".  So I think you should check for any XML errors in what "the other
server" sends to ejabberd.

More information about the ejabberd mailing list