> Hi All,
> 
> This query is regarding "Displaying the wrong message on the 
> chat window upon executing @call<sip/xmpp user>"
> 
> My Setup:
> ------------
> 1.Add two users  600,610 and 391
> 2.Add a User Group "Instant_Messaging" with the following settings: 
>               Enable IM account:Yes 
>               Add user group as IM group:Yes .
> Rest of the parameters set to default.
> 3.Register 600 and 610 to the two Pidgin client. 
> 4.Register 2 hard phones with respect to 600 and 610 Pidgin 
> clients.One hard phone wrt to user 391 On registering the 
> clients,The user group "Instant_Messaging" along with the 
> members is replicated on the respective clients. 
> Here, User 600 will have 610 as its buddy and vice versa. 
> 
> Steps:
> --------
> 1.From the TUI of the registered Pidgin client of user 
> 610,select the user 600 and double click on it.
> 2.Establish an IM chat between user 600 and 610.
> 3.On the chat window of the user 600 type @call 391 from the user 610.
> Screen shot:
>  
> Result:
>          On the chat window on the user 600 a false response 
> message " 600:Attempting to call 391" is displayed.Where as 
> user 600 is never trying to Attempt to call user 391.This 
> message gives a wrong impression for the users that 600 is 
> trying to call 391 which is not true.
> Note that the functionality *does not fail*.Its only the 
> message which is wrongly displayed .
> Upon executing this command, user phone 610 will ring 
> first.Answering the call, user phone 391 will start ringing 
> as expected.

So to summarize your observation, if I'm "IMing" with Mark and I type
'@call Simon', I'm going to get back: "Mark: attempting to call <Simon's
extension>" which suggests that Mark is telling me that he is trying to
call Simon's extension when in fact it is the system telling me that it
is attempting to call Simon's extension on my behalf.

I understand the confusion that this may create.  A better approach
would be for the IM entry to look like "{sipXecs]: attempting to call
<Simon's extension>" instead of "Mark: attempting to call <Simon's
extension>" but because this text is sent in the context of the
conversation between me and Mark, that is just not possible.  Here are a
couple of alternatives - I would like to get people's preference:

1- Do nothing - assume that the user will be capable of correlating the
"Mark: attempting to call <Simon's extension>" message it gets back with
the '@call Simon' command he issued milliseconds ago.

2- Make it explicit that the message is the @call response, e.g. "Mark:
[...@call result: attempting to call <Simon's extension>]"

3- Suppress feedback, i.e. @call command will not produce any text-based
response

4- Have the Personal assistant return the response in a new conversation
window.

The polls are open, please vote.

bob

_______________________________________________
sipx-dev mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
sipXecs IP PBX -- http://www.sipfoundry.org/

Reply via email to