ejabberd - Comments for "Rosters with external user IDs"

OK cool thanks for the update

DrSpud — Tue, 04 Jul 2017 13:53:28 +0000

OK cool thanks for the update and fix, will try this. The format I was told to use lately was:

[{<<"user1s">>, <<"localhost">>, <<"Workers">>, <<"User 1">>}]

But I will upgrade and will try this one first and see if I can register foreign ID's as well.

I've tested the

badlop — Thu, 08 Jun 2017 17:57:05 +0000

I've tested the push_roster_all command in ejabberd git, and it had a bug, but it reported an error message, not a timeout. In any case, I've fixed in git. I've fixed in git:
https://github.com/processone/ejabberd/commit/ee8bbccb2a2dcc8206b894f6ac...

I've also documented the file format:

[{"user1", "localhost", "Workers", "User 1"},
 {"user2", "localhost", "Workers", "User 2"}].

Just as a follow-up, did the

DrSpud — Wed, 07 Jun 2017 12:50:13 +0000

Just as a follow-up, did the jump from 15.11 to 17.04 since it was time do so. Still haven't tested the external ID thing yet as we've found the same error tacking place in just pushing the new roster with internal IDs only. Will follow-up if a solution is found but in short, we get a timeout using push_roster_all.

This time the push_roster_all

DrSpud — Wed, 12 Apr 2017 17:46:17 +0000

This time the push_roster_all command just fails with an eventual timeout.

Failed RPC connection to the node 'ejabberd@jabber1.something.org: timeout

Nothing stands out in the error.log

I see no reason for ejabberd

badlop — Mon, 10 Apr 2017 10:27:33 +0000

I see no reason for ejabberd to complain about that. I think it should work. Did you try with recent ejabberd and failed?