[OpenSIPS-Users] Topology hiding - B2B_LOGIC

Kamen Petrov kamen.petrov at gmail.com
Thu Feb 10 15:44:18 CET 2011


I noticed my opensips daemon is not updated according to the trunk.

I just did a new:
-rwxrwxrwx 1 root   root   3977907 Feb 10 14:33 opensips

Compare to the old:
-rwxr-xr-x 1 root   root   3977899 Feb 10 14:33 opensips.old


I will play with it tonight and provide feedback if the issue still exists.

In the meantime, if it makes any sense, here is what is on the core:
*Core was generated by `/root/opensips-1.6.4-tls/opensips -f
/etc/b2b-opensips.cfg'.
Program terminated with signal 11, Segmentation fault.
#0  0x00007fd9af72a4cc in engage_rtp_proxy2_f (msg=0x7fd9b0837540,
param1=0x7ae1b0 "e", param2=0x7ae248 "184.106.168.144") at nathelper.c:3003
3003            parse_to(msg->to->body.s,msg->to->body.s + msg->to->body.len
+ 1, &TO);
(gdb) bt
#0  0x00007fd9af72a4cc in engage_rtp_proxy2_f (msg=0x7fd9b0837540,
param1=0x7ae1b0 "e", param2=0x7ae248 "184.106.168.144") at nathelper.c:3003
#1  0x000000000040fcdc in do_action (a=0x7ae2e0, msg=0x7fd9b0837540) at
action.c:1200
#2  0x000000000040e41e in run_action_list (a=<value optimized out>,
msg=0x7fd9b0837540) at action.c:141
#3  0x0000000000411c72 in do_action (a=0x7aed40, msg=0x7fd9b0837540) at
action.c:824
#4  0x000000000040e41e in run_action_list (a=<value optimized out>,
msg=0x7fd9b0837540) at action.c:141
#5  0x00000000004138b0 in run_actions (a=0x7adcc0, msg=0x7fd9b0837540) at
action.c:121
#6  run_top_route (a=0x7adcc0, msg=0x7fd9b0837540) at action.c:184
#7  0x00007fd9b061719d in t_uac (method=0x7fff31b2c280, headers=<value
optimized out>, body=<value optimized out>, dialog=0x7fff31b2c0e0, cb=<value
optimized out>, cbp=<value optimized out>,
    release_func=0x7fd9ae081171 <shm_free_param>) at uac.c:301
#8  0x00007fd9ae07df2f in client_new (ci=0x7fff31b2c280, b2b_cback=<value
optimized out>, add_dlginfo=<value optimized out>, param=<value optimized
out>) at client.c:234
#9  0x00007fd9ade5b20b in create_top_hiding_entities (msg=0x30, cbf=<value
optimized out>, cb_param=<value optimized out>, cb_mask=<value optimized
out>, custom_hdrs=<value optimized out>) at logic.c:2099
#10 0x00007fd9ade5bbb7 in init_request (msg=0x7ba220, scenario_struct=0x0,
args=0x7fff31b2c4d0, cbf=0, cb_param=0x0, cb_mask=0, custom_hdrs=0x0) at
logic.c:2638
#11 0x00007fd9ade5bcd5 in b2b_init_request (msg=0x7ba220, arg1=0x0,
arg2=0x0, arg3=0x0, arg4=<value optimized out>, arg5=<value optimized out>,
arg6=0x0) at logic.c:2706
#12 0x000000000040fcdc in do_action (a=0x7b3260, msg=0x7ba220) at
action.c:1200
#13 0x000000000040e41e in run_action_list (a=<value optimized out>,
msg=0x7ba220) at action.c:141
#14 0x0000000000411c72 in do_action (a=0x7b3788, msg=0x7ba220) at
action.c:824
#15 0x000000000040e41e in run_action_list (a=<value optimized out>,
msg=0x7ba220) at action.c:141
#16 0x00000000004138b0 in run_actions (a=0x7b0098, msg=0x7ba220) at
action.c:121
#17 run_top_route (a=0x7b0098, msg=0x7ba220) at action.c:184
#18 0x000000000046d3ec in receive_msg (
    buf=0x77aba0 "INVITE
sip:17864776626 at 184.106.168.144:5061SIP/2.0\r\nRecord-Route:
<sip:184.106.168.144;lr=on;ftag=as6983ba1f;did=13e.4092d931>\r\nVia:
SIP/2.0/UDP 184.106.168.144;branch=z9hG4bK10d6.48a6c472.0\r\nVia: SI"...,
len=1167, rcv_info=0x7fff31b2cf30) at receive.c:162
#19 0x00000000004c13b8 in udp_rcv_loop () at udp_server.c:492
#20 0x000000000042c72d in main_loop (argc=<value optimized out>, argv=<value
optimized out>) at main.c:824
#21 main (argc=<value optimized out>, argv=<value optimized out>) at
main.c:1393*






Thanks
-- Kamen





On 10 February 2011 16:32, Ovidiu Sas <osas at voipembedded.com> wrote:

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


More information about the Users mailing list