Can't join jabber chatroom with 1.1.1dev

[bitlbee.org@…]

trying to connect into a jabber chatroom for work but can't... really odd behavior here...

<tekkub> join_chat 1 general-discussion@chat.asapwebsoft.net
  ** Nothing happens **
<tekkub> join_chat 1 general-discussion@chat.asapwebsoft.net
<root> Channel already exists: &general-discussion
/join &general-discussion
* &general-discussion :No such nick

The same happens both on my own hosted server and on testing.bitlbee.org. Connecting thru jabber with ssh turned on.

[wilmer]

The same thing happens here. That conference server just doesn't respond. Can you join it using a different client?

[wilmer]

Same thing happens with Gajim here. Also, after a few minutes my Jabber server does respond:

12:52:17  xmlconsol| TX: <presence to="general-discussion@chat.asapwebsoft.net/wilmer" id="BeeCQnLinZyRINea0003c"><x 
                     xmlns="http://jabber.org/protocol/muc"/></presence>
12:55:26  xmlconsol| RX: <presence from="general-discussion@chat.asapwebsoft.net/wilmer" to="wilmer@gaast.net/MainBee" 
                     type="error" id="BeeCQnLinZyRINea0003c"><x xmlns="http://jabber.org/protocol/muc"/><error code="404" 
                     type="cancel"><remote-server-not-found xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/></error></presence>

Looks like this is not a BitlBee bug. Except that it should cache packets a bit longer, because it failed to handle this error response, it forgot what it is about. Will fix that part.

[anonymous]

The server's not responding because it's not set to, it's an internal work server and all... supposed to be a private server.

I'll see if I can reproduce this on a public server, if not I can prolly get my boss to make you an account to test with.

[wilmer]

Or maybe you can enable xmlconsole? If you add a buddy "xmlconsole" (no @ or whatever) to your Jabber contact list you'll get an XML dump like what I pasted here, so you can see what you received exactly.

[anonymous]

<xmlconsole> TX: <presence to="general-discussion@chat.asapwebsoft.net/tekkub" id="BeeClvEboiSY/Tg50007c"><x xmlns="http://jabber.org/protocol/muc"/></presence>

That was it, nothing else ><

[wilmer]

If that's all, then I guess the server somehow still doesn't want to accept your connection. Maybe the room is password-protected?

Anyway, I changed the garbage collection code of cached packets to keep packets around a bit longer. This way, the error reported by your Jabber server after a few minutes will be handled properly. I'll remove the milestone now and keep the bug open a bit longer so we can see what's going on here.

[anonymous]

I don't believe there is a channel password, since he already restricts connections to accounts on the server. I'll see if I can get console output from Miranda (which can open the channels)... perhaps it will help.

[wilmer]

Resolved via e-mail.

[anonymous]

Could someone post the solution to this problem? i'm getting the exact same issue and I can't figure out what's wrong.

Thanks.

[anonymous]

My issue was that I forgot the "@conference." in the room name. I'm an idiot ><

[anonymous]

Sorry, I hate to be retarded, but what "@conference"? could you give an example of what you typed wrong and what was correct? I really don't want to end up just typing the wrong thing :P

Thanks

[anonymous]

general-discussion@… ---> general-discussion@…

[wilmer]

Which room are you trying to join? Does xmlconsole show the same thing?

[anonymous]

Ah you're a legend! (and I am a numpty) Thanks so much

problem solved >_> <_<

[anonymous]

Hey wilmer, I know you said that there was something like a 4-min timeout before the server sends back an error... maybe bitlbee should have a shorter timeout where it warns the user that the room may not exist... it would certainly help over the silent failure we get right now... something like:

<user> join_chat .... *5-sec delay* <root> no response from server, the room may not exist. Did you spell the chat room name correctly? Many servers host their rooms at <room>@conference.<server>

[anonymous]

damnit, stupid trac formatting always buggers up on me, and I can't go back and edit *stabs trac*

[wilmer]

Hmm, could do that, but I'm not sure how useful a log message exactly one minute after trying to join would be. Although right now the join_chat command does not generate any output at all, maybe that's bad. At least some "feedback" would hopefully convince the user that BitlBee is still alive.

Or what I can do is make it echo a "be patient, grasshopper" message if the user re-enters the same join_chat command. :-)