[asterisk-bugs] [Asterisk 0013984]: Incoming Gtalk calls fail

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13984 
====================================================================== 
Reported By:                jcovert
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   13984
Category:                   Channels/chan_gtalk
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
Asterisk Version:           SVN 
SVN Branch (only for SVN checkouts, not tarball releases): 1.6.0 
SVN Revision (number only!): 159700 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-11-27 16:48 CST
Last Modified:              2008-11-29 22:46 CST
====================================================================== 
Summary:                    Incoming Gtalk calls fail
Description: 
All incoming Gtalk calls are failing.

It appears that something about the responses Asterisk is sending back to
Gtalk are not making Gtalk happy; Gtalk responds with "unknown session".

The caller (see his Buddy info below) continues to hear ringing until
Gtalk finally abandons the call.

/john
        Buddy:  OnStateGTalkTest at gmail.com
                Resource: Talk.v10496F5B39E
                        node: http://www.google.com/xmpp/client/caps
                        version: 1.0.0.104
                        Jingle capable: yes
                Status: 3
                Priority: 24

====================================================================== 

---------------------------------------------------------------------- 
 (0095619) jcovert (reporter) - 2008-11-29 22:46
 http://bugs.digium.com/view.php?id=13984#c95619 
---------------------------------------------------------------------- 
I think I see the problem.

Asterisk's outgoing messages respond with "initiator=" set to the value in
the "from" field of the incoming messages rather than to the value of the
"initiator=" of the incoming messages.  "From" and "initiator" are not
necessarily the same; in particular, the "from=" seems to have mixed case
for some Google accounts, whereas the "initiator=" is all lowercase on the
original message from Google.  The response "initiator" doesn't match, and
this is probably causing Google to fail to match the session, resulting in
the "unknown session" error message.

The reason the newer account works is that it was set up all lower case.

Looks like Asterisk should be sending the incoming "initiator" back as the
outgoing "initiator", and the incoming "from" back as the outgoing "to".

/john 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-11-29 22:46 jcovert        Note Added: 0095619                          
======================================================================