This Question is Not Answered

1 "correct" answer available (10 pts) 2 "helpful" answers available (5 pts)
4 Replies Last post: Jun 9, 2008 10:21 PM by ffi  
ffi Bronze 5 posts since
Mar 3, 2008
Currently Being Moderated

Jun 5, 2008 8:43 PM

how to use xmpp client in lieu of webchat client for fastpath?

 

On the homepage of igniterealtime.org it says " Users can use their own XMPP client or the provided web client to initiate a chat request.".  I would very much like to use a XMPP client instead of the webchat client.

 

 

How is this done ?  For example, If I take an off-the-shelf xmpp client, the first thing it wants to do is authenticate to the server.  Well, we know that fastpath is anonymous login, so how do you work around that?  and then when you go to communicate with the fastpath, exactly how is that done?  I dont mind taking an open source xmpp client and stripping it down to work for my needs, but it would be nice if i could make it work easily with an off-the-shelf xmpp to prove the concept and then from there i can strip out all of the extra functionality.

 

 

 

 

 

 

Gaston Dombiak Jiver 3,771 posts since
Sep 26, 2001
Currently Being Moderated
Jun 6, 2008 12:23 AM in response to: ffi
Re: how to use xmpp client in lieu of webchat client for fastpath?

Hey ffi,

 

Let me describe the basic architecture of Fastpath to clarify some things. Fastpath has a server side component that is provided by the fastpath.jar plugin. The server side component is where the logic for queues and routing lives. Then we have agents that connect to the server using their XMPP account and register with their corresponding workgroup. Agents must use a client, like Spark, that follows the rules defined in XEP-0142: Workgroup Queues for registering with workgroups and responding to chat requests. The last part of the puzzle are the end users. End users may use the webchat client provided by the webchat.war application or they can use their XMPP client of choice (i.e. no need to support XEP-0142: Workgroup Queues). When using the web chat client, the server needs to have anonymous users enabled and end users do not need to provide any user credentials to make a chat/support request. On the other hand, users using an XMPP client may make a chat/support request from their client. They may be connected to the same Openfire server that provides the Fastpath service or they may even be connected to another remote server and still use the Fastpath service in your server. When using an XMPP client users will authenticate with their XMPP server the same way they always do it. In order to make a chat/support request they just need to send any message to the workgroup address (e.g. support@workgroup.server.com). The workgroup's bot will answer the message and guide the user. Users may even add a workgroup to their roster and see the workgroup's presence. The workgroup will be available when agents are connected and away if all agents are away or offline if all agents are not connected.

 

Hope that helps.

 

  -- Gato

Gaston Dombiak Jiver 3,771 posts since
Sep 26, 2001
Currently Being Moderated
Jun 6, 2008 1:14 AM in response to: ffi
Re: how to use xmpp client in lieu of webchat client for fastpath?

Hey ffi,

 

Anonymous logins do not provide a user/password but instead follow the rules defined in XEP-0175: Best Practices for Use of SASL ANONYMOUS. XMPP clients that implement XEP-175 will let you login as an anonymous user but afaik all XMPP clients do not support that functionality. However, if you are using the Smack library then you can use anonymous logins.

 

Regards,

 

  -- Gato

More Like This

  • Retrieving data ...