Re: [asterisk-dev] Rules for binding with regards to RTP

2014-12-10 Thread Mark Michelson
On 12/09/2014 12:42 PM, Mark Michelson wrote: 5. If we are responding to a media_offer, and there is either no configured media_address on the endpoint or the media_address is of a different IP address family than the offerer's media address for the given stream, and the signaling address for

Re: [asterisk-dev] Rules for binding with regards to RTP

2014-12-09 Thread Joshua Colp
Mark Michelson wrote: On 12/09/2014 01:42 PM, Joshua Colp wrote: Mark Michelson wrote: So, yes. In an ICE scenario the code will provide candidates for all local addresses. If you are bound to only one then all the others will fail. This should be taken into account - but it ultimately (pote

Re: [asterisk-dev] Rules for binding with regards to RTP

2014-12-09 Thread Mark Michelson
On 12/09/2014 01:42 PM, Joshua Colp wrote: Mark Michelson wrote: So, yes. In an ICE scenario the code will provide candidates for all local addresses. If you are bound to only one then all the others will fail. This should be taken into account - but it ultimately (potentially) lessens t

Re: [asterisk-dev] Rules for binding with regards to RTP

2014-12-09 Thread Joshua Colp
Mark Michelson wrote: I propose the following algorithm as a fix for this issue: 1. If we are sending a media offer, and there is a configured media_address on the endpoint to which we are sending the offer, then bind the RTP stream to the media_address. This means that the rtp_ipv6 setting

[asterisk-dev] Rules for binding with regards to RTP

2014-12-09 Thread Mark Michelson
During some testing being performed at Digium, a bit of unexpected behavior was discovered. While testing local RTP native bridging (also known as packet-to-packet or P2P bridging), RTP packets sent from Asterisk had an unexpected source IP address. In the configuration, Asterisk was bound to 1