[RTPproxy Devel] Automatic bridging for RTP proxy and advertised address for external NAT

[Emmanuel BUU]

Maxim Sobolev a écrit :
> Emmanuel BUU wrote:
>   
>> Maxim Sobolev a écrit :
>>     
>>> Emmanuel BUU wrote:
>>>                 
>>>> Hum great, maybe I can help with the NATHELPER module of OpenSIPS if you 
>>>> describe me what change have been made to the RTP proxy control protocol 
>>>> and provide me access to the source code.
>>>>     
>>>>         
>>> Yes, it should be possible. I will see what I can do in the next few days.
>>>   
>
> Emmanuel,
>
> The change is in CVS now, you are expected to provide either binding 
> address for media or expected remote media address for automatic local 
> address determination:
>
>  
>  >
>  >   Internally feature is implemented as an extension to the U/L command.
>  >   option "l" should be used for local addresses, or option "r" for 
> remote,
>  >   with IPv6 address enclosed into square brackets. For example:
>  >
>  >   Ul[abcd:efgh:0:1] callid remote_ip remote_port fromtag
>  >
>  >   Lr1.2.3.4 callid remote_ip remote_port fromtag totag
>  >
>  >   Changes to OpenSIPS, Kamalio/SER and Sippy B2BUA are to follow.
>
> Please let me know if you want to go ahead and make a patch for the 
> nathelper. It would involve extracting destination address from the RURI 
> for INVITE, and from upper Via for 200 OK.
>   
Well I have a question: if I extract the dest address from RURI, this 
may not be a numerical adress. Is the new RTPPROXY able to handle that?

Ex : Lrsip.external.com zegeryerzeyyr remote_ip 19874 fzepitzejnt lsdknglkt


> Regards,
>