[asterisk-bugs] [Asterisk 0012569]: [branch] Receiving Text from res_jabber

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12569 
====================================================================== 
Reported By:                eech55
Assigned To:                phsultan
====================================================================== 
Project:                    Asterisk
Issue ID:                   12569
Category:                   Resources/res_jabber
Reproducibility:            always
Severity:                   feature
Priority:                   normal
Status:                     ready for testing
Asterisk Version:           SVN 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 115340 
Request Review:              
====================================================================== 
Date Submitted:             2008-05-02 00:38 CDT
Last Modified:              2009-02-17 14:48 CST
====================================================================== 
Summary:                    [branch] Receiving Text from res_jabber
Description: 
Hello,

So far, chan_gtalk sends text to GTalk clients only. There is no way to
hear input from them which limit us a lot.

It will be awesome if we are able to receive text from GTalk users, to
provide extra services such as:

1) Voice menus. The user can select menus by sending corresponding keys
2) Or, "text" menus by which the chan_gtalk replies by text messages
instead of voice

I am glad that phsultan thought about it, however very disappointed that
it was canceled.
http://bugs.digium.com/bug_view_advanced_page.php?bug_id=8659


======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0008659 [patch] Add a jabber text receiver appl...
====================================================================== 

---------------------------------------------------------------------- 
 (0100268) jtodd (administrator) - 2009-02-17 14:48
 http://bugs.digium.com/view.php?id=12569#c100268 
---------------------------------------------------------------------- 
Also: I recall a discussion about caching pre-responses for some period of
time to account for slow Asterisk systems.  In other words, what happens if
a user sends a command prior to ${JABBER_RECEIVE} being ready to accept it?
 I think we should have some configurable cache that allows one or more
messages to pre-date the ${JABBER_RECEIVE} command.   It could be
configured in jabber.conf in [general], or perhaps a per-peer setup would
be more flexible with a default in [general].  Something like "cache=3"
which would save received messages for 3 seconds and ditch them if no
${JABBER_RECEIVE} requested/matched them in that time period.

This is important when this method starts to be used as an API-like tool
between automated systems.  The reply may come back from the remote system
with surprising speed, and it would be bad if it was lost because the
dialplan was busy with some task that took a few seconds to do.

Asterisk -> User: "Send your command"
[Dialplan does other things for 10 seconds]
User -> Asterisk: "Hang up"
[Dialplan finally gets around to ${JABBER_RECEIVE}, but user has already
sent command.  Now what?] 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-02-17 14:48 jtodd          Note Added: 0100268                          
======================================================================