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

[Daniel-Constantin Mierla]

Hello,

you should not set the second parameter of rtpproxy_manage(...), let it 
be the one returned by rtpproxy.

And yes, all the occurrences of IP addresses in c= lines will be 
replaced by the rtpproxy ip, but providing different ports for each 
media stream.

Practically the rtp streams are going from end device to rtpproxy and 
then based on port will be delivered to different IPs of the MCU. Also, 
the MCU will send from different IPs to RTPProxy on different ports and 
from there to the end device.

Cheers,
Daniel

On 10/8/12 6:05 PM, MARINA SERRANO MONTES wrote:
> Hi Daniel,
>
> I have tested using "rtpproxy_manage("", public IP), but in this case, 
> it replaces all the c= lines with this public IP, included c=lines in 
> media descriptions and then, the rtp traffic is not routing to the 
> right IP in MCU.
>
> Have I to set up any value/param….to route rtp traffic through 
> rtpproxy in sip server and then it will dispatch RTP packets to MCU?
>
> Thanks.
>
> Br,
> Marina
>
> From: Daniel-Constantin Mierla <miconda at gmail.com 
> <mailto:miconda at gmail.com>>
> Reply-To: "miconda at gmail.com <mailto:miconda at gmail.com>" 
> <miconda at gmail.com <mailto:miconda at gmail.com>>
> Date: lunes 8 de octubre de 2012 16:04
> To: "SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - 
> Users Mailing List" <sr-users at lists.sip-router.org 
> <mailto:sr-users at lists.sip-router.org>>
> Cc: Vicente Hernando <vhernando at systemonenoc.com 
> <mailto:vhernando at systemonenoc.com>>, Marina Serrano Montes 
> <marinas at tid.es <mailto:marinas at tid.es>>
> Subject: Re: [SR-Users] how to use fix_nated_sdp("2") with multiple 
> media types
>
> 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.orghttp://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.orghttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>
> -- 
> Daniel-Constantin Mierla -http://www.asipto.comhttp://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
>
> ------------------------------------------------------------------------
>
> 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

-- 
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/20121009/416d0c75/attachment.htm>