[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-13 10:39 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'
====================================================================== 

---------------------------------------------------------------------- 
 (0130457) lmadsen (administrator) - 2011-01-13 10:39
 https://issues.asterisk.org/view.php?id=18593#c130457 
---------------------------------------------------------------------- 
joscas: I think you're going to have to better clarify how your network is
setup. You're showing the physical connections, but you're mentioning
different LAN segments and such. I think there is something non-standard
about what you're trying to do here.

Additionally, you'll have to provide console output of the debug messages
when all of this is happening. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2011-01-13 10:39 lmadsen        Note Added: 0130457                          
======================================================================