[ejabberd] Re: server dialback port

Gaston Dombiak gaston at jivesoftware.com
Thu May 19 07:57:51 MSD 2005

Hey Alexey,

Thanks for your reply. This is the sequence of stanzas between my server and

SENT: <stream:stream xmlns:stream="http://etherx.jabber.org/streams"
xmlns="jabber:server" xmlns:db="jabber:server:dialback"">

RECV: <stream:stream xmlns:stream='http://etherx.jabber.org/streams'
xmlns='jabber:server' xmlns:db='jabber:server:dialback' id='133927854'>

SENT: <db:verify from="localhost" to=""

RECV: <stream:error

Do you see something wrong in the db:verify packet that I'm sending? This is
the packet format defined by the spec:

    from='Receiving Server'
    to='Originating Server'

Thanks for your help,

  -- Gato

"Alexey Shchepin" <alexey at sevcom.net> wrote in message 
news:87ekc5tob9.fsf at alex.sevcom.net...
> 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