[Pidgin] #16968: Jabber/XMPP rejoin room fails after disconnect (Prosody)

[Pidgin]

#16968: Jabber/XMPP rejoin room fails after disconnect (Prosody)
---------------------------------------+---------------------
 Reporter:  notavailable2              |       Owner:  deryni
     Type:  defect                     |      Status:  new
Milestone:                             |   Component:  XMPP
  Version:  2.10.12                    |  Resolution:
 Keywords:  room rejoin finch Prosody  |
---------------------------------------+---------------------
Changes (by notavailable2):

 * keywords:  room rejoin finch => room rejoin finch Prosody


Old description:

> Hi,
>
> beeing behind dial-up routers, if the ip of the router changes the
> reconnect to certain jabberservers works, but automatic rejoin into rooms
> not. Ejabberd seems fine, Prosody not.
> Also the list of in room present members does not show people that had
> been in the room before the disconnect. Only people who join afterwards
> will be displayed.
>
> If the other open/closed tickets (#10712, #15796) regarding this/related
> issues are right, than from my understanding there is a possibility that
> different server implementations send statusmessages in different order.
> If thats the case, I would suggest to add an option "use protocol order a
> instead of b" to the config, that gets used on dection of prosody on the
> other side. I assume the same goes for other implementations (have seen
> tickets to related issues, openfire etc)

New description:

 Hi,

 beeing behind dial-up routers, if the ip of the router changes the
 reconnect to certain jabberservers works, but automatic rejoin into rooms
 not. Ejabberd seems fine, Prosody not.
 Also the list of in room present members does not show people that had
 been in the room before the disconnect. Only people who join afterwards
 will be displayed.

 If the other open/closed tickets (#10712, #15796) regarding this/related
 issues are right, than from my understanding there is a possibility that
 different server implementations send statusmessages in different order.
 If thats the case, I would suggest to add an option "use protocol order a
 instead of b" to the config, that gets used on dection of prosody on the
 other side. I assume the same goes for other implementations (have seen
 tickets to related issues, openfire etc)


 Edit: tested Gajim with this server, rejoin on reconnect works.

--

--
Ticket URL: <https://developer.pidgin.im/ticket/16968#comment:1>
Pidgin <https://pidgin.im>
Pidgin