Closed GoogleCodeExporter closed 8 years ago
Thats odd because the resource is hard-coded to "GTalkSMS".
Which version have you installed?
Original comment by fschm...@gmail.com
on 7 Feb 2011 at 7:05
Could be an openfire (or some other xmpp server) that changes the resource to
same random string if there is a resource conflict, which happens on reconnect.
If you have contact to your xmpp server admin, ask him about this.
Original comment by fschm...@gmail.com
on 7 Feb 2011 at 7:06
Hey, its the Version 1.8 on my mobile
and as for the second question, I'm the admin of my own ejabberd jabber server.
I didn't think about that possibility but if you are sure about the fixed
string that would be an explanation, I will tell you my findings.
Another Question, is it normal that gTalkSMS reconnects after a call or this
also something my mobile does wrong?
Original comment by ThDietri...@gmail.com
on 7 Feb 2011 at 7:26
I just cleanly disconnected and connected gTalkSMS and it still has a bad
resource-string, this time it is "GTalkSMS7202D849". So this clearly not a
ejabberd Problem... i think.
Original comment by ThDietri...@gmail.com
on 7 Feb 2011 at 7:36
I've got the same issue but not only with GTalkSMS... It's the same thing with
my account in pidgin.
Original comment by Florent....@gmail.com
on 7 Feb 2011 at 7:59
Resource conflicts happen exactly WHEN you reconnect (disconnect and then
connect). GtalkSMS tries to set the presence to "Gtalksms" but the server has
the power to override this setting. That is also why some users (like florent
and you) experience this problem and some don't.
We can nothing do about if, even if we add a option to let the user set the
presence, the resource conflict will happen and you will end up with a
presence string like "GTalkSMS7202D849"
PS: If you have access to the server, you can take an capture of the xmpp
negotiation. It will show that the server sets the presence.
Original comment by fschm...@gmail.com
on 8 Feb 2011 at 2:25
I miss the option to set a custom resource name, because i own more then one
android device. Yes, i can use a new jabber account for every device, but a
simple resource name fix this problem and made this app more usefull, why do
you hardcode this?
Original comment by lucke...@gmail.com
on 13 Apr 2013 at 11:46
We will not support multiple devices over the same jabber account. This would
mean heavy code changes for a very special use case where I don't see the
benefit.
Simply add one account for every device. Accounts are free. I think that this
is a workaround that is reasonable for a user.
Original comment by fschm...@gmail.com
on 14 Apr 2013 at 12:10
Original issue reported on code.google.com by
ThDietri...@gmail.com
on 7 Feb 2011 at 6:22