Thanks Alex but I'm not sure if I understood correctly your answer : do you mean that NATHelper only handle INVITE with a unique SDP part (application/sdp) ? If NATHelper processes my INVITE with multipart, does it modify only the SDP part ? -pascal On Fri, Jun 19, 2009 at 11:58 AM, Alex Balashov &lt;abalashov(a)evaristesys.com <mailto:abalashov@evaristesys.com>> wrote: Nathelper does not attempt to modify parts of SDP not pertinent to its mission. Pascal Maugeri wrote: Hi Does NATHelper support properly multipart SDP (eg. INVITE with application/sdp and application/resource-lists+xml) ? Regards, Pascal ------------------------------------------------------------------------ _______________________________________________ Kamailio (OpenSER) - Users mailing list Users(a)lists.kamailio.org <mailto:Users@lists.kamailio.org> http://lists.kamailio.org/cgi-bin/mailman/listinfo/users http://lists.openser-project.org/cgi-bin/mailman/listinfo/users -- Alex Balashov Evariste Systems Web : http://www.evaristesys.com/ Tel : (+1) (678) 954-0670 Direct : (+1) (678) 954-0671

Here is the errors I get when processing the INVITE: Jun 19 14:51:58 sandbox /usr/sbin/kamailio[15560]: ERROR:nathelper:check_content_type: invalid type for a message Jun 19 14:51:58 sandbox /usr/sbin/kamailio[15560]: ERROR:nathelper:extract_body: content type mismatching Jun 19 14:51:58 sandbox /usr/sbin/kamailio[15560]: ERROR:nathelper:force_rtp_proxy: can't extract body from the message is it familiar to you ? -pascal On Fri, Jun 19, 2009 at 12:25 PM, Alex Balashov &lt;abalashov(a)evaristesys.com&gt; wrote: _______________________________________________ Kamailio (OpenSER) - Users mailing list Users(a)lists.kamailio.org http://lists.kamailio.org/cgi-bin/mailman/listinfo/users http://lists.openser-project.org/cgi-bin/mailman/listinfo/users

I was checking the nathelper source code (nhelpr_func.c) and it looks that only a content-type of application/sdp is accepted.

I found the tracker in sip-router but nothing in Kamailio. Does it mean that this is a fix that will be applied only to sip-router module ?

Hi, Pascal... I opened the tracker... I also would like to have the fix applied to Kamailio, but as Daniel asked to open it on SR ( http://lists.kamailio.org/pipermail/users/2009-June/023707.html), I opened there. It seems that most/all programming force is concentrated on SR development.

As a workaround that I personally didn't try, is to use Mediaproxy, as suggested by Juha at the end of the mentioned thread ( http://lists.kamailio.org/pipermail/users/2009-June/023706.html).

Edson. Pascal Maugeri escreveu: _______________________________________________ Kamailio (OpenSER) - Users mailing list Users(a)lists.kamailio.org http://lists.kamailio.org/cgi-bin/mailman/listinfo/users http://lists.openser-project.org/cgi-bin/mailman/listinfo/users

I don't understand why you say that. Media proxy doesn't use nathelper module, but Kamailio "mediaproxy" module.

On Fri, Jun 19, 2009 at 3:49 PM, Edson - Lists &lt;4lists(a)gmail.com <mailto:4lists@gmail.com>> wrote: Hi, Pascal... I opened the tracker... I also would like to have the fix applied to Kamailio, but as Daniel asked to open it on SR (http://lists.kamailio.org/pipermail/users/2009-June/023707.html), I opened there. It seems that most/all programming force is concentrated on SR development. This is pretty bad news! As a workaround that I personally didn't try, is to use Mediaproxy, as suggested by Juha at the end of the mentioned thread (http://lists.kamailio.org/pipermail/users/2009-June/023706.html). I think it is useless I try mediaproxy (instead of rtpproxy) because the error comes from NATHelper module. Thanks all for your answers Pascal Edson. Pascal Maugeri escreveu: I found the tracker in sip-router but nothing in Kamailio. Does it mean that this is a fix that will be applied only to sip-router module ? -pascal On Fri, Jun 19, 2009 at 1:35 PM, Juha Heinanen &lt;jh(a)tutpro.com <mailto:jh@tutpro.com> <mailto:jh@tutpro.com <mailto:jh@tutpro.com>>> wrote: Pascal Maugeri writes: and it looks that this was discussed a couple of days ago and there is already a tracker item opened for it. -- juha ------------------------------------------------------------------------ _______________________________________________ Kamailio (OpenSER) - Users mailing list Users(a)lists.kamailio.org <mailto:Users@lists.kamailio.org> http://lists.kamailio.org/cgi-bin/mailman/listinfo/users http://lists.openser-project.org/cgi-bin/mailman/listinfo/users _______________________________________________ Kamailio (OpenSER) - Users mailing list Users(a)lists.kamailio.org <mailto:Users@lists.kamailio.org> http://lists.kamailio.org/cgi-bin/mailman/listinfo/users http://lists.openser-project.org/cgi-bin/mailman/listinfo/users

one is nathelper/mediaproxy module related and the other relates to textops/filter_body function. mediaproxy module's use_mediaproxy() function can extract application/sdp bodypart both in k 1.5 and sr.

except the one given as argument, but boundary string is properly extracted from Content-type param only in sr.

-- juha

Pascal Maugeri writes: you don't need to call filter_body if you use mediaproxy. i have never used engage_media_proxy() functions, because it makes some assumptions that are not generally true. i use use_media_proxy() instead. the using you don't need to do anything like that if you use use_media_proxy() function, because it does not remove anything.

-- juha

I tried to install mediaproxy but it looks tricky to install (many dependencies, including kernel specific configurations) :-( and I would like to stick to rtpproxy for performance reason. Do you believe the same workaround using textops/filter_body can be used using rtpproxy ? I think yes as these are two different things as said Juha. Regards, Pascal On Fri, Jun 19, 2009 at 9:26 PM, Pascal Maugeri &lt;pascal.maugeri(a)gmail.com <mailto:pascal.maugeri@gmail.com>> wrote: On Fri, Jun 19, 2009 at 9:13 PM, Juha Heinanen &lt;jh(a)tutpro.com <mailto:jh@tutpro.com>> wrote: Pascal Maugeri writes: the "plan" is: instead of you don't need to call filter_body if you use mediaproxy. i have never used engage_media_proxy() functions, because it makes some assumptions that are not generally true. i use use_media_proxy() instead. 1º) and relay the them back using you don't need to do anything like that if you use use_media_proxy() function, because it does not remove anything. Thanks Juha ! I can't wait for monday to test it :-) Have a nice week-end Pascal -- juha ------------------------------------------------------------------------ _______________________________________________ Kamailio (OpenSER) - Users mailing list Users(a)lists.kamailio.org http://lists.kamailio.org/cgi-bin/mailman/listinfo/users http://lists.openser-project.org/cgi-bin/mailman/listinfo/users

If I understood correctly you want me to test the patch nhelpr_func.c you've done in sr in kamailio ? This is what I've done and at least it compiles :-) (I also tried to compile sr, but I need to sudy it a bit more as I've never installed sr so far) Nevertheless, the ouput payload is wrong: Content-Type: application/sdp v=0 o=- 3454665275 3454665275 IN IP4 10.1.1.248 s=pjmedia c=IN IP4 88.29.163.14288.29.163.142 t=0 0 a=X-nat:0 m=audio 5191251912 RTP/AVP 115 [...] m=application 4198041980 udp TBCP The RTP and RTCP ports are wrong: 5191251912 and 4198041980 ?! Where could I have a look in nathelper source to see what is wrong ?

-pascal On Mon, Jun 22, 2009 at 11:36 AM, Daniel-Constantin Mierla &lt;miconda(a)gmail.com <mailto:miconda@gmail.com>> wrote: Hello Pascal, I have just committed support for multipart bodies in sip router, if works then I will backport to 1.5. http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=1f41271… Can you test it? Unfortunately I cannot do it these days properly due to traveling. Patch should work pretty straightforward with 1.5 though, if you want to test it directly there. Cheers, Daniel On 06/22/2009 11:30 AM, Pascal Maugeri wrote: I tried to install mediaproxy but it looks tricky to install (many dependencies, including kernel specific configurations) :-( and I would like to stick to rtpproxy for performance reason. Do you believe the same workaround using textops/filter_body can be used using rtpproxy ? I think yes as these are two different things as said Juha. Regards, Pascal On Fri, Jun 19, 2009 at 9:26 PM, Pascal Maugeri &lt;pascal.maugeri(a)gmail.com <mailto:pascal.maugeri@gmail.com> <mailto:pascal.maugeri@gmail.com <mailto:pascal.maugeri@gmail.com>>> wrote: On Fri, Jun 19, 2009 at 9:13 PM, Juha Heinanen &lt;jh(a)tutpro.com <mailto:jh@tutpro.com> <mailto:jh@tutpro.com <mailto:jh@tutpro.com>>> wrote: Pascal Maugeri writes: the "plan" is: module instead of you don't need to call filter_body if you use mediaproxy. need to i have never used engage_media_proxy() functions, because it makes some assumptions that are not generally true. i use use_media_proxy() instead. removed in 1º) and relay the and put them back using you don't need to do anything like that if you use use_media_proxy() function, because it does not remove anything. Thanks Juha ! I can't wait for monday to test it :-) Have a nice week-end Pascal -- juha ------------------------------------------------------------------------ _______________________________________________ Kamailio (OpenSER) - Users mailing list Users(a)lists.kamailio.org <mailto:Users@lists.kamailio.org> http://lists.kamailio.org/cgi-bin/mailman/listinfo/users http://lists.openser-project.org/cgi-bin/mailman/listinfo/users -- Daniel-Constantin Mierla http://www.asipto.com/

Hello Pascal, I have just committed support for multipart bodies in sip router, if works then I will backport to 1.5. http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=1f41271… Can you test it? Unfortunately I cannot do it these days properly due to traveling. Patch should work pretty straightforward with 1.5 though, if you want to test it directly there. Cheers, Daniel On 06/22/2009 11:30 AM, Pascal Maugeri wrote: -- Daniel-Constantin Mierla http://www.asipto.com/

please send me the original and the new invite so I can see how the body is changed afterwards. Cheers, Daniel On 06/22/2009 03:23 PM, Pascal Maugeri wrote:

This bug is fixed now with your patch Daniel! Thank you, I go ahead with my testing

Cheers, Pascal On Mon, Jun 22, 2009 at 5:34 PM, Daniel-Constantin Mierla &lt;miconda(a)gmail.com <mailto:miconda@gmail.com>> wrote: Can you check this patch I just committed? http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=caef5ac… Basically, you simply can get the extract_body() function from nathelper/nhelpr_funcs.c and replace it in kamailio. Let me know if works ok now. Thanks, Daniel On 06/22/2009 04:22 PM, Daniel-Constantin Mierla wrote: please send me the original and the new invite so I can see how the body is changed afterwards. Cheers, Daniel On 06/22/2009 03:23 PM, Pascal Maugeri wrote: With your patch there is a small bug when re-constructing the multipart payload: [...] --Genaker-boundary Content-Type: application/sdp v=0 [...] a=fmtp:TBCP queuing=0; tb_priority=1; timestamp=0; tb_granted=0; poc_sess_priority=1; poc_lock=0 *a=nortpproxy:yes--Genaker-boundary* Content-Type: application/resource-lists+xml <?xml version="1.0" encoding="UTF-8"?> <resource-lists xmlns="urn:ietf:params:xml:ns:resource-lists" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> [...] --Genaker-boundary-- Observe the line "a=nortpproxy:yes--Genaker-boundary" : there are CRLFs missing. And there two CRLF before "a=nortpproxy:yes". I guess you're adding the CRLF in the incorrect order. We're progressing ;-) -pascal On Mon, Jun 22, 2009 at 11:36 AM, Daniel-Constantin Mierla &lt;miconda(a)gmail.com <mailto:miconda@gmail.com> <mailto:miconda@gmail.com <mailto:miconda@gmail.com>>> wrote: Hello Pascal, I have just committed support for multipart bodies in sip router, if works then I will backport to 1.5. http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=1f41271… Can you test it? Unfortunately I cannot do it these days properly due to traveling. Patch should work pretty straightforward with 1.5 though, if you want to test it directly there. Cheers, Daniel On 06/22/2009 11:30 AM, Pascal Maugeri wrote: I tried to install mediaproxy but it looks tricky to install (many dependencies, including kernel specific configurations) :-( and I would like to stick to rtpproxy for performance reason. Do you believe the same workaround using textops/filter_body can be used using rtpproxy ? I think yes as these are two different things as said Juha. Regards, Pascal On Fri, Jun 19, 2009 at 9:26 PM, Pascal Maugeri &lt;pascal.maugeri(a)gmail.com <mailto:pascal.maugeri@gmail.com> <mailto:pascal.maugeri@gmail.com <mailto:pascal.maugeri@gmail.com>> <mailto:pascal.maugeri@gmail.com <mailto:pascal.maugeri@gmail.com> <mailto:pascal.maugeri@gmail.com <mailto:pascal.maugeri@gmail.com>>>> wrote: On Fri, Jun 19, 2009 at 9:13 PM, Juha Heinanen &lt;jh(a)tutpro.com <mailto:jh@tutpro.com> <mailto:jh@tutpro.com <mailto:jh@tutpro.com>> <mailto:jh@tutpro.com <mailto:jh@tutpro.com> <mailto:jh@tutpro.com <mailto:jh@tutpro.com>>>> wrote: Pascal Maugeri writes: me if I'm wrong) the "plan" is: MEDIAPROXY module instead of application/sdp\r\n"); not found\n"); you don't need to call filter_body if you use mediaproxy. relay if we need to i have never used engage_media_proxy() functions, because it makes some assumptions that are not generally true. i use use_media_proxy() instead. have been removed in 1º) and relay the part(s) in 1º) and put them back using you don't need to do anything like that if you use use_media_proxy() function, because it does not remove anything. Thanks Juha ! I can't wait for monday to test it :-) Have a nice week-end Pascal -- juha ------------------------------------------------------------------------ _______________________________________________ Kamailio (OpenSER) - Users mailing list Users(a)lists.kamailio.org <mailto:Users@lists.kamailio.org> <mailto:Users@lists.kamailio.org <mailto:Users@lists.kamailio.org>> http://lists.kamailio.org/cgi-bin/mailman/listinfo/users http://lists.openser-project.org/cgi-bin/mailman/listinfo/users -- Daniel-Constantin Mierla http://www.asipto.com/ ------------------------------------------------------------------------ _______________________________________________ Kamailio (OpenSER) - Users mailing list Users(a)lists.kamailio.org <mailto:Users@lists.kamailio.org> http://lists.kamailio.org/cgi-bin/mailman/listinfo/users http://lists.openser-project.org/cgi-bin/mailman/listinfo/users -- Daniel-Constantin Mierla http://www.asipto.com/ ------------------------------------------------------------------------ _______________________________________________ Kamailio (OpenSER) - Users mailing list Users(a)lists.kamailio.org http://lists.kamailio.org/cgi-bin/mailman/listinfo/users http://lists.openser-project.org/cgi-bin/mailman/listinfo/users

Daniel Are you sure that this source fragment (in nhelpr_funcs.c): /* no need for parse_headers(msg, EOH), get_body will * parse everything */ /*is the content type correct?*/ if((ret = check_content_type(msg))==1) { LM_ERR("content type mismatching\n"); goto error; } shouldn't be /* no need for parse_headers(msg, EOH), get_body will * parse everything */ /*is the content type correct?*/ if((ret = check_content_type(msg))== -1) { LM_ERR("content type mismatching\n"); goto error; } ? ( "==1" --> "==-1") Because now it gives me errors when processing INVITE with application/sdp payload. -pascal On Tue, Jun 23, 2009 at 10:59 AM, Daniel-Constantin Mierla &lt;miconda(a)gmail.com <mailto:miconda@gmail.com>> wrote: On 06/23/2009 10:16 AM, Pascal Maugeri wrote: This bug is fixed now with your patch Daniel! Thank you, I go ahead with my testing ok, I will backport to kamailio 1.5 in few days if there is no related bug reported meanwhile. Cheers, Daniel Cheers, Pascal On Mon, Jun 22, 2009 at 5:34 PM, Daniel-Constantin Mierla &lt;miconda(a)gmail.com <mailto:miconda@gmail.com> <mailto:miconda@gmail.com <mailto:miconda@gmail.com>>> wrote: Can you check this patch I just committed? http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=caef5ac… Basically, you simply can get the extract_body() function from nathelper/nhelpr_funcs.c and replace it in kamailio. Let me know if works ok now. Thanks, Daniel On 06/22/2009 04:22 PM, Daniel-Constantin Mierla wrote: please send me the original and the new invite so I can see how the body is changed afterwards. Cheers, Daniel On 06/22/2009 03:23 PM, Pascal Maugeri wrote: With your patch there is a small bug when re-constructing the multipart payload: [...] --Genaker-boundary Content-Type: application/sdp v=0 [...] a=fmtp:TBCP queuing=0; tb_priority=1; timestamp=0; tb_granted=0; poc_sess_priority=1; poc_lock=0 *a=nortpproxy:yes--Genaker-boundary* Content-Type: application/resource-lists+xml <?xml version="1.0" encoding="UTF-8"?> <resource-lists xmlns="urn:ietf:params:xml:ns:resource-lists" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> [...] --Genaker-boundary-- Observe the line "a=nortpproxy:yes--Genaker-boundary" : there are CRLFs missing. And there two CRLF before "a=nortpproxy:yes". I guess you're adding the CRLF in the incorrect order. We're progressing ;-) -pascal On Mon, Jun 22, 2009 at 11:36 AM, Daniel-Constantin Mierla &lt;miconda(a)gmail.com <mailto:miconda@gmail.com> <mailto:miconda@gmail.com <mailto:miconda@gmail.com>> <mailto:miconda@gmail.com <mailto:miconda@gmail.com> <mailto:miconda@gmail.com <mailto:miconda@gmail.com>>>> wrote: Hello Pascal, I have just committed support for multipart bodies in sip router, if works then I will backport to 1.5. http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=1f41271… Can you test it? Unfortunately I cannot do it these days properly due to traveling. Patch should work pretty straightforward with 1.5 though, if you want to test it directly there. Cheers, Daniel On 06/22/2009 11:30 AM, Pascal Maugeri wrote: I tried to install mediaproxy but it looks tricky to install (many dependencies, including kernel specific configurations) :-( and I would like to stick to rtpproxy for performance reason. Do you believe the same workaround using textops/filter_body can be used using rtpproxy ? I think yes as these are two different things as said Juha. Regards, Pascal On Fri, Jun 19, 2009 at 9:26 PM, Pascal Maugeri &lt;pascal.maugeri(a)gmail.com <mailto:pascal.maugeri@gmail.com> <mailto:pascal.maugeri@gmail.com <mailto:pascal.maugeri@gmail.com>> <mailto:pascal.maugeri@gmail.com <mailto:pascal.maugeri@gmail.com> <mailto:pascal.maugeri@gmail.com <mailto:pascal.maugeri@gmail.com>>> <mailto:pascal.maugeri@gmail.com <mailto:pascal.maugeri@gmail.com> <mailto:pascal.maugeri@gmail.com <mailto:pascal.maugeri@gmail.com>> <mailto:pascal.maugeri@gmail.com <mailto:pascal.maugeri@gmail.com> <mailto:pascal.maugeri@gmail.com <mailto:pascal.maugeri@gmail.com>>>>> wrote: On Fri, Jun 19, 2009 at 9:13 PM, Juha Heinanen &lt;jh(a)tutpro.com <mailto:jh@tutpro.com> <mailto:jh@tutpro.com <mailto:jh@tutpro.com>> <mailto:jh@tutpro.com <mailto:jh@tutpro.com> <mailto:jh@tutpro.com <mailto:jh@tutpro.com>>> <mailto:jh@tutpro.com <mailto:jh@tutpro.com> <mailto:jh@tutpro.com <mailto:jh@tutpro.com>> <mailto:jh@tutpro.com <mailto:jh@tutpro.com> <mailto:jh@tutpro.com <mailto:jh@tutpro.com>>>>> wrote: Pascal Maugeri writes: correct me if I'm wrong) the "plan" is: Kamailio MEDIAPROXY module instead of (filter_body("application/sdp") { application/sdp\r\n"); application/sdp not found\n"); you don't need to call filter_body if you use mediaproxy. relay if we need to i have never used engage_media_proxy() functions, because it makes some assumptions that are not generally true. i use use_media_proxy() instead. have been removed in 1º) and relay the part(s) in 1º) and put them back using you don't need to do anything like that if you use use_media_proxy() function, because it does not remove anything. Thanks Juha ! I can't wait for monday to test it :-) Have a nice week-end Pascal -- juha ------------------------------------------------------------------------ _______________________________________________ Kamailio (OpenSER) - Users mailing list Users(a)lists.kamailio.org <mailto:Users@lists.kamailio.org> <mailto:Users@lists.kamailio.org <mailto:Users@lists.kamailio.org>> <mailto:Users@lists.kamailio.org <mailto:Users@lists.kamailio.org> <mailto:Users@lists.kamailio.org <mailto:Users@lists.kamailio.org>>> http://lists.kamailio.org/cgi-bin/mailman/listinfo/users http://lists.openser-project.org/cgi-bin/mailman/listinfo/users -- Daniel-Constantin Mierla http://www.asipto.com/ ------------------------------------------------------------------------ _______________________________________________ Kamailio (OpenSER) - Users mailing list Users(a)lists.kamailio.org <mailto:Users@lists.kamailio.org> <mailto:Users@lists.kamailio.org <mailto:Users@lists.kamailio.org>> http://lists.kamailio.org/cgi-bin/mailman/listinfo/users http://lists.openser-project.org/cgi-bin/mailman/listinfo/users -- Daniel-Constantin Mierla http://www.asipto.com/ ------------------------------------------------------------------------ _______________________________________________ Kamailio (OpenSER) - Users mailing list Users(a)lists.kamailio.org <mailto:Users@lists.kamailio.org> http://lists.kamailio.org/cgi-bin/mailman/listinfo/users http://lists.openser-project.org/cgi-bin/mailman/listinfo/users -- Daniel-Constantin Mierla http://www.asipto.com/

I tried to install mediaproxy but it looks tricky to install (many dependencies, including kernel specific configurations) :-(

and I would like to stick to rtpproxy for performance reason.

[...] uses linux kernel to forward the packages and it is hard to do more efficiently. Good point.

[...]At the same time, the Kamailio leadership appears to have much more perspective and standardisation on rtpproxy, as well as whatever RTP forwarding module is being lifted from IPTel.org for SIP-Router.

Is it possible to set up SIPP or something like it (open source?) on two endpoints and make them set up calls between themselves with media in both directions?

Someone does need to do a study to see if kernel vs. userspace forwarding really makes that much of a difference, though. I suspect that although it does make a difference, it is not nearly as much of a difference as is commonly thought.

it is well known, but you can run one or two instances per core and load balance from the nathelper module. I usually start 2 per cpu core.

There are performance metrics that speak for kernel-based media relays (e.g. delay and jitter). It is a matter of what you expect from your media relay to do beside rtp relay (like media forking [LI?], call recording etc.).

On Wednesday 24 June 2009 22:23:27 Iñaki Baz Castillo wrote: I think he is speaking about LAW requirements about call-recording/call-interception

On Jun 25, 2009, at 12:24 AM, Iñaki Baz Castillo wrote: Because not every country allows telecom operators to record to WAV files on a generic machine and email/ftp/whatever every single file once a day to the authorities. Usually they want "realtime" access and in those cases you want to fork the media (and the signalling probably, I don't know for sure).

Hi, We did a benchmark (only cpu usage for now) comparing the standard rtpproxy with mediaproxy-ng, a proprietary implementation of Sipwise (implemented as iptables module based on the mediaproxy dispatcher protocol). The results should be pretty equal for mediaproxy2 and iptrtpproxy as well, although I don't know anything about their design. http://pub.sipwise.com/OpenSER.rtpproxy.benchmark.2009.06.24.pdf The machine is a Dual-CPU Intel(R) Xeon(TM) CPU 2.80GHz with 2GB of RAM. Test-Setup is done with sipp (rtp is sent via pre-recorded pcap and echoed via "-rtp-echo" option on UAS). Some observations we found: - rtpproxy seems to not take advantage of SMP

- jitter is reduced in mediaproxy-ng compared to rtpproxy because socket polling is eliminated in kernel - delay is reduced in kernel-space due to elimination of context switching - the peaks in mediaproxy-ng are a result of the mediaproxy-ng design (relaying is done in user-space until all ip/port information is available by receiving rtp packets from both sides, besides some other processing like packet inspection etc. [although cpu usage can be lowered even more by further optimizing the userspace part]) Andreas _______________________________________________ Kamailio (OpenSER) - Users mailing list Users(a)lists.kamailio.org http://lists.kamailio.org/cgi-bin/mailman/listinfo/users http://lists.openser-project.org/cgi-bin/mailman/listinfo/users

I was checking the nathelper source code (nhelpr_func.c) and it looks that only a content-type of application/sdp is accepted.