Open GoogleCodeExporter opened 9 years ago
[deleted comment]
Here's an interesting note. I switched to Openfire server changed nothing in
the gtalksms (accept user name from <name@domain.net> to <name>) and it logs
right in. (although I have no muc)
So note to anyone wanting to run a server for gtalksms, openfire alot less
trouble than ejabberd.
I still have no clue why stock ejabbrad rejects gtalksms.
Original comment by swashbun...@gmail.com
on 9 Apr 2012 at 8:45
Indeed smack/gtalksms does not receive an auth challenge after login:
04-06 00:31:38.036 E/gtalksms( 987): xmpp login failed: No response from the
server.
It would be great, if you could get a trace of the xmpp stanzas of the login
sequence from gtalksms with ejabberd.
Original comment by fschm...@gmail.com
on 9 Apr 2012 at 5:46
No user feedback in months
Original comment by fschm...@gmail.com
on 11 Nov 2012 at 11:18
This is not done
Original comment by ivebeenl...@gmail.com
on 14 Nov 2012 at 8:41
Then we need (at least) some logs
http://code.google.com/p/gtalksms/wiki/GenerateAppLog
*and*
the trace of the XMPP stanzas that I request in #3
Original comment by fschm...@gmail.com
on 15 Nov 2012 at 9:25
I ran into the same issue. Cannot connect to ejabberd server. Openfire server
is ok.
I attached the asmack log.
ejabberd server is jappix.com
user: testabc@jappix.com
password: 123456
can login with pidgin
Original comment by hongbin....@gmail.com
on 23 Mar 2013 at 6:54
Attachments:
Reopen because we get these reports @ aSmack too. See
https://github.com/Flowdalic/asmack/issues/30
Original comment by fschm...@gmail.com
on 28 Mar 2013 at 12:39
Oh and thanks @hongbin.li87 for providing the log. Good job! :)
Original comment by fschm...@gmail.com
on 28 Mar 2013 at 12:45
@hongbin.li87 The server sends a not-authorized failure stanza after the SASL
challenge
<failure xmlns='urn:ietf:params:xml:ns:xmpp-sasl'>
<not-authorized/>
</failure>
That usually indicates a wrong username/password.
Original comment by fschm...@gmail.com
on 28 Mar 2013 at 1:26
I have had the same issue with ejabberd and simly used the local part (all
before the @ of the jid) as username and the password and changed the server in
the settings. this worked without any issue now. HTH
Original comment by ronny.bo...@googlemail.com
on 21 Feb 2014 at 9:43
Original issue reported on code.google.com by
swashbun...@gmail.com
on 6 Apr 2012 at 4:50Attachments: