[asterisk-bugs] [Asterisk 0018593]: RTCP conflict avoidance not handled

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=18593 
====================================================================== 
Reported By:                joscas
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   18593
Category:                   Channels/chan_gtalk
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
Asterisk Version:           1.8.1.1 
JIRA:                       SWP-2895 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2011-01-10 08:03 CST
Last Modified:              2011-01-12 10:51 CST
====================================================================== 
Summary:                    RTCP conflict avoidance not handled
Description: 
When trying to bridge a Gtalk outgoing call to a Gtalk incoming call that
uses the same IP address it fails.

The error it gives is:
[Jan 10 14:46:56] NOTICE[4520]: res_rtp_asterisk.c:2190 ast_rtp_read:
Unknown RTP codec 73 received from '95.21.226.219:58470'
====================================================================== 

---------------------------------------------------------------------- 
 (0130418) dvossel (administrator) - 2011-01-12 10:51
 https://issues.asterisk.org/view.php?id=18593#c130418 
---------------------------------------------------------------------- 
If you are using separate accounts, I'd expect this to work.  I am
unfamiliar with the payload range 72-76 so I can't comment on why Google is
sending that or what it could mean.

With chan_gtalk it is possible to set up a session between endpoints
behind the same LAN.  chan_gtalk is capable of sending out candidates for
both the internal address of an endpoint and the external address of the
endpoint.  When the remote side gets the candidate list from google it
first tries the internal address for connectivity, if that doesn't work
then the external address is tried.  If the endpoints are both behind the
same lan, the internal address will work. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2011-01-12 10:51 dvossel        Note Added: 0130418                          
======================================================================