[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 review
Asterisk Version:           SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 115340 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-05-02 00:38 CDT
Last Modified:              2008-12-11 15:26 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...
====================================================================== 

---------------------------------------------------------------------- 
 (0096262) jtodd (administrator) - 2008-12-11 15:26
 http://bugs.digium.com/view.php?id=12569#c96262 
---------------------------------------------------------------------- 
My question is this: does this application understand the concept of
multiple XMPP instances registered to multiple XMPP servers?  There does
not seem to be the ability to specify what XMPP account is being used to
receive inbound messages.  The only thing specified is the user from which
messages are received. 

This is not a problem now, but imagine if someone clever decides to modify
this code and create a regular expression capability.  It quickly becomes
impossible to tell what is the destination of the XMPP messages, so I can't
tell if people were sending a command to "sales at foo.com" or
"support at foo.com" if both accounts are valid and listening in jabber.conf
for this server.  I could come up with quite a few examples of how this
would be useful, but I'll save the space here and let everyone envision it
themselves over a cup of coffee.

I would strongly suggest that the command includes and uses the name of
the Jabber stanza so that separate instances can be comprehended by the
dialplan administrator.  This will (hopefully) prevent
backwards-compatibility problems in the future when it is determined that
really, this was a useful feature.  :-)

Ideally, it WOULD look like this:

*CLI> core show application JabberReceive 

  -= Info about application 'JabberReceive' =- 

[Synopsis]
JabberReceive(Variable)

[Description]
JabberReceive(account,JID,Variable[,timeout])
  account - the local named account to listen on (specified in
jabber.conf)
  JID - Jabber ID of the buddy to receive message from
  Variable - Variable to store message in
  timeout - Defaults to 20s

*CLI> 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-12-11 15:26 jtodd          Note Added: 0096262                          
======================================================================