Following up from chatroom conversation, where you mentioned the server is swissjabber.eu, the issue is probably that it does not send the <bind> feature we are relying on during the authentication procedure:
DATA <<< <stream:features xmlns:stream="http://etherx.jabber.org/streams"><register xmlns="http://jabber.org/features/iq-register"/><auth xmlns="http://jabber.org/features/iq-auth"/><starttls xmlns="urn:ietf:params:xml:ns:xmpp-tls"/></stream:features>
For comparison, this is what sameplace.cc sends:
DATA <<< <stream:features xmlns:stream="http://etherx.jabber.org/streams"><bind xmlns="urn:ietf:params:xml:ns:xmpp-bind"/><session xmlns="urn:ietf:params:xml:ns:xmpp-session"/></stream:features>
I'll check if I can support that without too much messing in the code...
Following up from chatroom conversation, where you mentioned the server is swissjabber.eu, the issue is probably that it does not send the <bind> feature we are relying on during the authentication procedure:
DATA <<< <stream:features xmlns:stream="http:// etherx. jabber. org/streams"><register xmlns="http:// jabber. org/features/ iq-register"/><auth xmlns="http:// jabber. org/features/ iq-auth"/><starttls xmlns=" urn:ietf: params: xml:ns: xmpp-tls" /></stream: features>
For comparison, this is what sameplace.cc sends:
DATA <<< <stream:features xmlns:stream="http:// etherx. jabber. org/streams"><bind xmlns=" urn:ietf: params: xml:ns: xmpp-bind" /><session xmlns=" urn:ietf: params: xml:ns: xmpp-session" /></stream: features>
I'll check if I can support that without too much messing in the code...