ejabberd - Comments for "dispatcher"

Clients send the history, or use MUC

mfoss — Tue, 10 May 2011 22:39:24 +0000

fei wrote:

If worker5 handles the conversation, then later transfers to worker6. How to enable worker6 to see all the history conversation between the client and worker5?

ejabberd doesn't store history of private chats. Two ideas:

A) Your worker5 client, or the asking client, stores all the conversation and sends it to worker6.

B) Or, instead of private conversations, use MUC roomsin some way: ejabberd stores the last 20 messages of a room (you can configure that to 9999...), and sends that history to clients that join the room.

badlop, I have a follow up

fei — Thu, 05 May 2011 14:27:17 +0000

badlop,
I have a follow up question. If worker5 handles the conversation, then later transfers to worker6. How to enable worker6 to see all the history conversation between the client and worker5?

Thanks

badlop, Thanks for your

fei — Thu, 05 May 2011 14:11:31 +0000

badlop,
Thanks for your reply, and I greatly appreciated.

fei wrote: Should I write a

mfoss — Thu, 05 May 2011 11:54:41 +0000

fei wrote:

Should I write a BOT, and use this BOT as a dispatcher? So, user first talk with the BOT, and BOT does some logic and forward the chat to the right one. Then, user can chat with the chosen one to talk with.

Yes, this looks a good idea. Some proposals:

1. You can use mod_shared_roster to ensure anon users get the dispatcher as a contact. See example 3: http://www.ejabberd.im/shared-roster-all#example-3

2. Example: user1 talks to bot, bot decides that worker5 will handle the conversation, bot sends a special Message XMPP stanza to client, that contains this: <forward-to>worker5@example.org</forward-to>. You implement in your Strophe.js user client that when a stanza with forward-to is received, the client sends a new message to that worker JID.