[jitsi-users] Bitlbee not receiving XMPP roster from jit.si


#1

Hi all,

Has the jit.si server somehow been set up to only accept connections
from the Jitsi client? (Fair enough if so!) The reason i ask is that i'm
unable to connect to the jit.si server from Bitlbee. After an XMPP
challenge-and-response, i receive:

    <success xmlns="urn:ietf:params:xml:ns:xmpp-sasl">[redacted]</success>

and Bitlbee then sends:

    <stream:stream to="jit.si" xmlns="jabber:client" xmlns:stream="http://etherx.jabber.org/streams" version="1.0">

to which it never receives a response from jit.si.

In comparison, when i use Bitlbee to connect to another XMPP server,
sending:

    <stream:stream to="[redacted]" xmlns="jabber:client"
xmlns:stream="http://etherx.jabber.org/streams" version="1.0">

results in a '<stream:features>' response from that server.

Alexis.


#2

Bump. Does the jit.si server only accept connections from the Jitsi
client?

Thanks!

Alexis <flexibeast@gmail.com> writes:

···

Hi all,

Has the jit.si server somehow been set up to only accept connections
from the Jitsi client? (Fair enough if so!) The reason i ask is that i'm
unable to connect to the jit.si server from Bitlbee. After an XMPP
challenge-and-response, i receive:

    <success xmlns="urn:ietf:params:xml:ns:xmpp-sasl">[redacted]</success>

and Bitlbee then sends:

    <stream:stream to="jit.si" xmlns="jabber:client" xmlns:stream="http://etherx.jabber.org/streams" version="1.0">

to which it never receives a response from jit.si.

In comparison, when i use Bitlbee to connect to another XMPP server,
sending:

    <stream:stream to="[redacted]" xmlns="jabber:client"
xmlns:stream="http://etherx.jabber.org/streams" version="1.0">

results in a '<stream:features>' response from that server.

Alexis.


#3

Hi Alexis,

Bump. Does the jit.si server only accept connections from the Jitsi
client?

There's no such limitations. I'm successfully connecting and communicating with my jit.si account from Adium for example.

Cheers,
Yana

···

On 23 Feb 2014, at 04:55, Alexis <flexibeast@gmail.com> wrote:

Thanks!

Alexis <flexibeast@gmail.com> writes:

Hi all,

Has the jit.si server somehow been set up to only accept connections
from the Jitsi client? (Fair enough if so!) The reason i ask is that i'm
unable to connect to the jit.si server from Bitlbee. After an XMPP
challenge-and-response, i receive:

   <success xmlns="urn:ietf:params:xml:ns:xmpp-sasl">[redacted]</success>

and Bitlbee then sends:

   <stream:stream to="jit.si" xmlns="jabber:client" xmlns:stream="http://etherx.jabber.org/streams" version="1.0">

to which it never receives a response from jit.si.

In comparison, when i use Bitlbee to connect to another XMPP server,
sending:

   <stream:stream to="[redacted]" xmlns="jabber:client"
xmlns:stream="http://etherx.jabber.org/streams" version="1.0">

results in a '<stream:features>' response from that server.

Alexis.

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users


#4

Yana Stamcheva <yana@jitsi.org> writes:

There's no such limitations. I'm successfully connecting and
communicating with my jit.si account from Adium for example.

*nod* Okay, thanks .... Will have to look for other reasons as to why
the jit.si server isn't sending a '<stream:features>' response to
Bitlbee.

Alexis.