Hi Ovidiu,<br><br>Please let me know how to open a bug report (can't find it on the opensips page) ?<br><br><br><b>Version (all related modules are built from the trunk):</b><br><i>version: opensips 1.6.3-notls (x86_64/linux)<br>
flags: STATS: Off, USE_IPV6, USE_TCP, DISABLE_NAGLE, USE_MCAST, SHM_MEM, SHM_MMAP, PKG_MALLOC, F_MALLOC, FAST_LOCK-ADAPTIVE_WAIT<br>ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535<br>
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.<br>svnrevision: 2:7684M<br>@(#) $Id: main.c 7291 2010-10-14 14:12:44Z razvancrainea $<br>main.c compiled on 19:17:46 Jan 26 2011 with gcc 4.4.5</i><br><br>
<b>Opensips database:</b><br>
Postgres 8.4<br><br><br><b>File size:</b><br>-rwxrwxrwx 1 root root 3977899 Jan 26 19:18 opensips<br><b>Md5:</b> 7b04d2d0c2202f7452c08a59f76a8ff4<br><br><b>That is a VPS running on rackspace with Ubuntu 10.10:</b><br>Linux sms 2.6.35.4-rscloud #8 SMP Mon Sep 20 15:54:33 UTC 2010 x86_64 GNU/Linux<br>
<br><b>lsmod:</b><br>Module Size Used by<br>iptable_filter 1304 0<br>ip_tables 13634 1 iptable_filter<br>ipv6 222188 16<br>dm_mirror 11458 0<br>dm_region_hash 6184 1 dm_mirror<br>
dm_log 7317 2 dm_mirror,dm_region_hash<br>dm_snapshot 24027 0<br>dm_mod 50487 3 dm_mirror,dm_log,dm_snapshot<br><br><br><b>/proc/cpuinfo:</b><br>4 CPUs like this:<br>vendor_id : AuthenticAMD<br>
cpu family : 16<br>model : 4<br>model name : Quad-Core AMD Opteron(tm) Processor 2374 HE<br>stepping : 2<br>cpu MHz : 2226513.610<br>cache size : 512 KB<br>flags : fpu de tsc msr pae cx8 cmov pat clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt lm 3dnowext 3dnow constant_tsc rep_good nonstop_tsc pni cx16 popcnt lahf_lm cmp_legacy extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch<br>
<br><br><b>free:</b><br> total used free shared buffers cached<br>Mem: 1022536 1000164 22372 0 11120 797308<br>-/+ buffers/cache: 191736 830800<br>
Swap: 2097148 21124 2076024<br><br><br>Thanks<br>-- Kamen<br>
<br><br><div class="gmail_quote">On 10 February 2011 16:15, Ovidiu Sas <span dir="ltr"><<a href="mailto:osas@voipembedded.com">osas@voipembedded.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Please open a bug report and provide the version of opensips:<br>
opensips -V<br>
<br>
Also, please provide the platform details for your server (OS and hardware).<br>
<br>
<br>
Regards,<br>
<font color="#888888">Ovidiu Sas<br>
</font><div><div></div><div class="h5"><br>
On Thu, Feb 10, 2011 at 4:56 AM, Kamen Petrov <<a href="mailto:kamen.petrov@gmail.com">kamen.petrov@gmail.com</a>> wrote:<br>
> Ok, I tried with the example. It looks like it is outdated as I faced some<br>
> issues using it:<br>
><br>
> 1) The "brake" command from the example gives errors.<br>
><br>
> 2) The rtpproxy dies every time when the onreply_route hits to the<br>
> rtpproxy_answer:<br>
><br>
> Feb 10 09:47:41 sms kernel: [7047428.249279] rtpproxy[1934]: segfault at 0<br>
> ip 00000000004053e9 sp 00007fff5b36a060 error 4 in rtpproxy[400000+e000]<br>
><br>
><br>
> The full log is:<br>
> Feb 10 09:47:41 sms /root/opensips-1.6.4-tls/opensips[2099]:<br>
> DBG:core:parse_to: display={011359883327749},<br>
> ruri={<a href="mailto:sip%3A359883327749@69.25.128.234">sip:359883327749@69.25.128.234</a>}<br>
> Feb 10 09:47:41 sms rtpproxy[2083]: DBUG:handle_command: received command<br>
> "2099_5 UE <a href="mailto:649d55a2210e1409075b65c50fcef44d@69.25.128.234">649d55a2210e1409075b65c50fcef44d@69.25.128.234</a> 69.25.128.234 5652<br>
> as2facc0be;1"<br>
> Feb 10 09:47:41 sms rtpproxy[2083]: INFO:handle_command: new session<br>
> <a href="mailto:649d55a2210e1409075b65c50fcef44d@69.25.128.234">649d55a2210e1409075b65c50fcef44d@69.25.128.234</a>, tag as2facc0be;1 requested,<br>
> type strong<br>
> Feb 10 09:47:41 sms rtpproxy[2083]: INFO:handle_command: new session on a<br>
> port 35540 created, tag as2facc0be;1<br>
> Feb 10 09:47:41 sms rtpproxy[2083]: INFO:handle_command: pre-filling<br>
> caller's address with <a href="http://69.25.128.234:5652" target="_blank">69.25.128.234:5652</a><br>
> Feb 10 09:47:41 sms rtpproxy[2083]: DBUG:doreply: sending reply "2099_5<br>
> 35540 184.106.168.144#012"<br>
> Feb 10 09:47:41 sms /root/opensips-1.6.4-tls/opensips[2099]:<br>
> DBG:nathelper:force_rtp_proxy_body: proxy reply: 35540 184.106.168.144#012<br>
> ...<br>
> ...<br>
> Feb 10 09:47:41 sms /root/opensips-1.6.4-tls/opensips[2101]:<br>
> ERROR:nathelper:force_rtp_proxy: Unable to parse body<br>
> Feb 10 09:47:41 sms /root/opensips-1.6.4-tls/opensips[2101]: [PROXY](INVITE<br>
> - Trying)<br>
> Feb 10 09:47:41 sms kernel: [7047428.249279] rtpproxy[1934]: segfault at 0<br>
> ip 00000000004053e9 sp 00007fff5b36a060 error 4 in rtpproxy[400000+e000]<br>
><br>
><br>
><br>
><br>
> Please advise.<br>
><br>
><br>
><br>
><br>
><br>
><br>
> On 10 February 2011 05:50, Ovidiu Sas <<a href="mailto:osas@voipembedded.com">osas@voipembedded.com</a>> wrote:<br>
>><br>
>> In the source tree, there are some examples on how to engage rtpproxy<br>
>> (using nathelper module):<br>
>> see "modules/nathelper/examples/alg.cfg".<br>
>> You need to run opensips in proxy mode (this is the server that will<br>
>> control the rtpproxy) on one server and on a separate server you need<br>
>> to tun opensips in b2b mode. You need to separate servers.<br>
>> Hope this heps.<br>
>><br>
>> Regards,<br>
>> Ovidiu Sas<br>
>><br>
>> On Wed, Feb 9, 2011 at 7:26 PM, Kamen Petrov <<a href="mailto:kamen.petrov@gmail.com">kamen.petrov@gmail.com</a>><br>
>> wrote:<br>
>> > Hi Ovidiu,<br>
>> ><br>
>> > With that scenario, when exactly should I call<br>
>> > rtpproxy_offer/answer/engage<br>
>> > ?<br>
>> > Is it on the b2b:<br>
>> > local_route {<br>
>> > if (is_method("INVITE")) {<br>
>> > engage_rtp_proxy();<br>
>> > }<br>
>> > }<br>
>> ><br>
>> > Do I need anything else rtp related anywhere ?<br>
>> > The SIP goes ok with the scenario but the RTP does not and the audio is<br>
>> > missing.<br>
>> ><br>
>> > Also, do I need anything special to enable the DTMF relay with the top<br>
>> > hiding ?<br>
>> ><br>
>> > Thanks in advance.<br>
>> > --------------------------------------------<br>
>> > Kamen Petrov<br>
>> ><br>
>> ><br>
>> > On 6 February 2011 18:08, Ovidiu Sas <<a href="mailto:osas@voipembedded.com">osas@voipembedded.com</a>> wrote:<br>
>> >><br>
>> >> For now, best thing to do is to separate functionality:<br>
>> >> - one server doing topology hiding;<br>
>> >> - one server doing routing, accounting, rtp proxy, etc.<br>
>> >><br>
>> >><br>
>> >> Regards,<br>
>> >> Ovidiu Sas<br>
>> >><br>
>> >> On Sun, Feb 6, 2011 at 9:23 AM, Maciej Bylica <<a href="mailto:mbsip@gazeta.pl">mbsip@gazeta.pl</a>> wrote:<br>
>> >> > Hi,<br>
>> >> ><br>
>> >> >> I am running Opensips 1.6.3 and trying to do topology hiding.<br>
>> >> >> This is my scenario: Operator_1 ------ > my Opensips ------><br>
>> >> >> Operator_2<br>
>> >> >> The goal is not to convey any information of Operator_2 to<br>
>> >> >> Operator_1<br>
>> >> >> like Contact, User-Agent headers and so on and to do rtp proxying.<br>
>> >> >> For rtp proxying i've installed rtpproxy and it works fine.<br>
>> >> >> But still the question is about signalization and SDP (o= part)<br>
>> >> >> I ran through a few posts and found out that the answer is B2B<br>
>> >> >> functionality here - so B2B_LOGIC.<br>
>> >> >><br>
>> >> >> Are there any other wayouts or this is the only way i may follow.<br>
>> >> ><br>
>> >> > One more question.<br>
>> >> > Should I place b2bua separately or could i combine that functionality<br>
>> >> > with my current Opensips installation?<br>
>> >> > I am asking because as i understand there might be some problems with<br>
>> >> > proper call accounting (no radius is used in my case).<br>
>> >> > If positive then my scenario will look like following:<br>
>> >> > Operator_1 ------ > my Opensips (billing) -- Opensips b2bua (top<br>
>> >> > hiding) -- OS RTP Proxy ------> Operator_2.<br>
>> >> > or it is wrong assumption.<br>
>> >> ><br>
>> >> > Thanks,<br>
>> >> > Maciej.<br>
>> >> ><br>
>> >> > _______________________________________________<br>
>> >> > Users mailing list<br>
>> >> > <a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
>> >> > <a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
>> >> ><br>
>> >><br>
>> >> _______________________________________________<br>
>> >> Users mailing list<br>
>> >> <a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
>> >> <a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
>> ><br>
>> ><br>
>> > _______________________________________________<br>
>> > Users mailing list<br>
>> > <a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
>> > <a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
>> ><br>
>> ><br>
>><br>
>> _______________________________________________<br>
>> Users mailing list<br>
>> <a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
>> <a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
><br>
><br>
> _______________________________________________<br>
> Users mailing list<br>
> <a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
> <a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
><br>
><br>
<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
</div></div></blockquote></div><br>