[JDEV] About changing the S2S communication port
Riviere Stéphane
Stephane.SR.Riviere at atosorigin.com
Thu Jul 26 09:44:14 CDT 2001
Thanks for this precise answer.
So the only thing I have to do is to use DNS SRV. Good news.
Does this need any special configuration in the jabber.xml file or is it
jabber default behaviour to use such records ?
Stéphane
-----Message d'origine-----
De : Dave Smith [mailto:dave at jabber.org]
Envoyé : jeudi 26 juillet 2001 16:11
À : jdev at jabber.org
Objet : Re: [JDEV] About changing the S2S communication port
On Thu, Jul 26, 2001 at 03:27:02PM +0200, Riviere St?phane wrote:
> Hi,
>
> 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 !
Yup. There has to be _some_ default port that all jabber servers listen on.
This
is pretty standard..SMTP does the same thing.
If you wanted to have your jabber server listen on another port, you can use
DNS SRV records (versus the standard A record) so that other servers get the
port you are listening on when they do the DNS query. If you don't have a
SRV
record setup for your server, other servers will be default just use TCP
port 5269.
Diz
_______________________________________________
jdev mailing list
jdev at jabber.org
http://mailman.jabber.org/listinfo/jdev
More information about the JDev
mailing list