[SR-Users] how to use fix_nated_sdp("2") with multiple media types

[Daniel-Constantin Mierla]

Hello,

I understood that Marina is looking for the option of being able to use 
different IP addresses for updating various c= lines in SDP.

fix_nated_sdp(...) can work only with one IP address given as second 
parameter (or taken for source address of the packet).

Perhaps fix_nated_sdp(...) can be easily extended to support a list of 
ip addresses in the second parameter. For now the solution is to use 
rtpproxy to rewrite all the IP addresses in c= lines with the IP address 
of the rtpproxy. RTPProxy will then dispatch RTP to the right IP address 
assigned for each media stream.

Regarding the patch sent by Vicente, I just replied on sr-dev mailing list.

Cheers,
Daniel

On 10/8/12 3:25 PM, Vicente Hernando wrote:
> Hello Marina,
>
> there is a bug in sdp parser about c IPs which are not correctly reset 
> for non existent c values in streams.
>
> I have still not uploaded it to master branch, sorry.
>
> May be it is related to your issue, in this link you have the attached 
> patch.
>
> http://lists.sip-router.org/pipermail/sr-dev/2012-September/016440.html
>
>
> Kind regards,
> Vicente.
>
> On 10/08/2012 01:18 PM, MARINA SERRANO MONTES wrote:
>> Hi,
>>
>> I have a doubt about how to use "fix_nated_sdp("2")" function when we 
>> have an scenario with multiple media types (audio and video) and the 
>> param "c" in sdp for each media type has a different IP.
>> We are using a SCOPIA 400 MCU to multi-party in a call, and it will 
>> set up different IP to send RTP depend on media type.
>>
>> I have tested this function, but it rewrites always all the "c" 
>> parameter with the same value.
>>
>> Is there any option to use the function or to rewrite "c" value for 
>> each media type independently?
>>
>> Many thanks.
>>
>> Br,
>> Marina
>>
>> ------------------------------------------------------------------------
>>
>> Este mensaje se dirige exclusivamente a su destinatario. Puede 
>> consultar nuestra política de envío y recepción de correo electrónico 
>> en el enlace situado más abajo.
>> This message is intended exclusively for its addressee. We only send 
>> and receive email on the basis of the terms set out at:
>> http://www.tid.es/ES/PAGINAS/disclaimer.aspx
>>
>>
>> _______________________________________________
>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
>> sr-users at lists.sip-router.org
>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>
>
>
> _______________________________________________
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users at lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

-- 
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Training, Berlin, Nov 5-8, 2012 - http://asipto.com/u/kat
Kamailio Advanced Training, Miami, USA, Nov 12-14, 2012 - http://asipto.com/u/katu

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20121008/9483484e/attachment.htm>