Hi All,
Issue:http://track.sipfoundry.org/browse/XX-7374 is raised against the
query posted below.
Thanks,
Chitralekha.
Chitralekha wrote:
Hi All,
This query is regarding sending a message to the offline
recipient(configured for the External IM account)
Steps:
--------------
1.Add user 200 with the IM ID enabled.
2.Login as the end user 200 and navigate to the MyInformation
tab>>Instant Messaging.
3.Click on the "Add External Im Account " link and add Google talk or
any External User Im Account available in the drop down list and click
on apply and OK button.
For eg: an account "patest123" for Google talk is added as the
External IM Account.
4.Click the "Apply" button available on the "Instant Messaging" page
where the an External IM account(Google talk or any other protocol)
is added to the "External IM accounts" table.
5.Register the Pidgin client with the user 200.
After step5,
On the pidgin client "Google Talk Transports" gets added under the
header "Transports".All the buddies(both Online and Offline buddies)
of the the External IM Account "patest123" are listed on the Pidgin
Client user 200.
A transparency is created to chat between the gtalk user's
buddy(patest123) and sipX user 200 without needing to sign up for, or
sign in with, each service.
Please refer the bellow image:
Query:
--------
Now click on the offline buddy [email protected] separate
transparency chat window appears to chat with the recipient
"[email protected]" through the sipX user 200.
Type a message "Will be out of station for 2days" and send the message.
Current behavior :
On sending a message to the offline user "[email protected]"
from user 200,a reply message "Will be out of station for 2days" is
displayed at the same time from the offline user
[email protected] , which I think is bug
Please refer the below image:
IMHO I think an error message like "/The user 'xyz' is offline.Your
message will not be received to the user/" should be displayed to the
message sender.
Kindly advice if this is a design intent or an Improvement request
should be raised against the current behavior.
Thanks in Advance,
Chitralekha.
------------------------------------------------------------------------
_______________________________________________
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/
_______________________________________________
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/
