[asterisk-bugs] [Asterisk 0008659]: [patch] Add a jabber text receiver application, and make Asterisk a Gtalk to phone gateway

[noreply at bugs.digium.com]

The following issue has been CLOSED 
====================================================================== 
http://bugs.digium.com/view.php?id=8659 
====================================================================== 
Reported By:                phsultan
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   8659
Category:                   Resources/res_jabber
Reproducibility:            always
Severity:                   feature
Priority:                   normal
Status:                     closed
Asterisk Version:            SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 59290 
Disclaimer on File?:        Yes 
Request Review:              
Resolution:                 open
Fixed in Version:           
====================================================================== 
Date Submitted:             12-22-2006 07:41 CST
Last Modified:              08-27-2007 11:00 CDT
====================================================================== 
Summary:                    [patch] Add a jabber text receiver application, and
make Asterisk a Gtalk to phone gateway
Description: 
Hi Matthew and other people working on jabber,

I'd like to submit two features to your acceptance, that make Asterisk a
jabber gateway to dial extensions from a jabber user client. Here is the
implemented behaviour (tested with GoogleTalk clients and a SIP gateway) :
- make a Gtalk call to Asterisk (needs a GoogleTalk account)
- Asterisk answers and plays a file
- Asterisk sends a text message asking the user for a number to dial
- Asterisk dials the number and makes the remote GoogleTalk client talk
with the corresponding POTS phone (through a SIP gateway in our case)

Two applications are used to achieve this :
- JabberReceive Dial plan application
  * waits for incoming jabber text messages, and stores received text in a
channel variable

JabberReceive relies on aji_handle_message to find a running Gtalk channel
that matches with the received jid (uid part), and pass a text frame that
contains the body of the jabber message to the channel on success. On the
channel side, the received text frame is stored in a channel variable
(defined in the dialplan).
JabberReceive needs to find a caller ID, so that this feature depends on
bug http://bugs.digium.com/view.php?id=8536 (new patch will be provided to allow
SIP extensions dialing).

- JabberAuthorize Dial plan application
  * sends a text message to the jid that started a Gtalk channel with
Asterisk in order to welcome and authorize a user to dial extensions
through Asterisk

JabberAuthorize relies on Asterisk's jabber client's buddy list to achieve
access control. In the future, we might prompt the user either through a
chat or form window (if the remote jabber client supports it) to provide
credentials for example.

Notes :
- you can also have Asterisk registered as a component rather than a user,
in this case, you'll need to fix Asterisk as per bug
http://bugs.digium.com/view.php?id=8409.
- also tested this with a jingle enabled client (jabbin), this needs some
hacking though.

JabberReceive is attached in trunk-aji_recv-1.diff (as it is closed to
JabberSend, I included it in res_jabber).
JabberAuthorize is attached in app_jabberauthorize.c

Enjoy the ending year celebration, and merry christmas!
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
parent of           0008536 [patch] Caller ID not set in CDR
====================================================================== 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
08-27-07 11:00  phsultan       Status                   ready for testing =>
closed
======================================================================