[JDEV] About changing the S2S communication port

Riviere Stéphane Stephane.SR.Riviere at atosorigin.com
Thu Jul 26 08:27:02 CDT 2001


I have sent a mail on this subject a few weeks ago but I had no response,
so, let's try again :-)

I noticed the following about S2S communication :

- the jabber.xml file allows to change the LISTENING port of the server
for S2S communication (by default 5269) as for C2S communication

- when initializing the server in the dialback.c file the configured
listening port is correctly read in the conf file

- BUT in the dialback_out.c file, any outgoing connection is tried on the
5269 port of the distant server !

So, If I understood correctly this part of the server :

A server can be configured to listen on any port for S2S com BUT will always
try to connect on the 5269 port of other servers...

Everything is fine with clients and C2S communication because you can set
the server port in the client...

Imagine server myjabberX is configured to listen on 6666 instead of 5269,
how would my second server myjabberY could "know" ?
If I'm right, a new section should be added in the config file to add exotic
distant servers configurations. This section would be read in the
dialback_out.c file to use the correct port...

Something like :

<service id="s2s">
    <dialback xmlns='jabber:config:dialback'>

        <host name="myjabberX.com">6666</host>


I hope I was clear enough this time and get some feedback :-)


email : Stephane.sr.Riviere at atosorigin.com
tél : (0)

Ingénieur R&D
Equipe Grands Projets
Direction Recherche & Développement
ATOS ORIGIN Activité Multimédia

More information about the JDev mailing list