Belnet jabber problems caused by bug in jabberd14
Gepost op dinsdag 1 februari 2005 om 13:29 (tags: )
Now that Belnet has a jabber server, I created a JID there and I want to migrate my whole roster to Belnet as I think it would be more stable than amessage.be. Before moving all my contacts, I first tested out the service there. I added my amessage-JID to my Belnet roster, but never recieved an authorisation request in Gaim. Logging on to the GreenThumb applet, I see "pending" at my amessage-contact. Sander, a jabber contact and very active within jabber and ejabberd, told me that the problem is caused by an s2s-bug in jabberd14. I've sent an e-mail, let's hope they fix it soon or switch to ejabberd.
1 reactie
Recieved an answer from Belnet. They say that it's a known problem with amessage/charente servers. He pointed me to jabber.belnet.be where they've now put a message about those problems.
There are some problems when contacting jabber users on several servers (amongst these are the amessage and the charante servers). The Belnet Jabber server receives a IPv6 address for the other server, but the other server is not responding to the IPv6 connection. However, the connection is not blocked also, and it just times out, resulting in a 502 message. We are looking into this problem and searching for a solution.
Plaats een nieuwe reactie