Bug known and fixed. Temporary solution

mfoss — Tue, 01 Jan 2008 11:17:27 +0000

Yes, this was a new bug included in ejabberd 2.0.0-beta1: Fixed behavior when outgoing_s2s_port option is not defined. It's already fixed in SVN.

As a temporary solution for ejabberd 2.0.0-beta1, add this to your ejabberd.cfg:

{outgoing_s2s_port, 5269}.

Once you get a fixed version, you can remove that line.

ejabberd - Comments for "default s2s port when SRV not present - how to do?"