[ejabberd] outgoing s2s connections broken?
alexey at sevcom.net
Wed Sep 3 00:04:41 MSD 2003
On Mon, 1 Sep 2003 13:59:21 -0700, you said:
>> I usually use "tcpflow" tool (not sure that it works on non-linux OSes),
>> any other traffic sniffer is also can be useful. I have no problem
>> connecting to psg.com from my ejabberd, but I can't connect to jabber.com.
>> It seems this is my error, I'll try to fix it tommorow (it seems this is
>> because of absence of "id" attribute in stream header).
MR> i've got a packet monitor here. since there are relatively few different
MR> implementations of jabber servers out there (compared to clients), maybe
MR> just adding the "id" will clear it up for the rest...
OK, I add temporary hack to fix this (hack because "id" atrribute have constant
value), try it. Will commit good solution in few next days after some testing.
More information about the ejabberd