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 <[email protected]> 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 <[email protected]> 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 <[email protected]> >> 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:[email protected]} >> > Feb 10 09:47:41 sms rtpproxy[2083]: DBUG:handle_command: received >> > command >> > "2099_5 UE [email protected] 69.25.128.234 >> > 5652 >> > as2facc0be;1" >> > Feb 10 09:47:41 sms rtpproxy[2083]: INFO:handle_command: new session >> > [email protected], 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 <[email protected]> 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 <[email protected]> >> >> 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 <[email protected]> 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 <[email protected]> >> >> >> 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 >> >> >> > [email protected] >> >> >> > http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> >> >> > >> >> >> >> >> >> _______________________________________________ >> >> >> Users mailing list >> >> >> [email protected] >> >> >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> >> > >> >> > >> >> > _______________________________________________ >> >> > Users mailing list >> >> > [email protected] >> >> > http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> >> > >> >> > >> >> >> >> _______________________________________________ >> >> Users mailing list >> >> [email protected] >> >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> > >> > >> > _______________________________________________ >> > Users mailing list >> > [email protected] >> > http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> > >> > >> >> _______________________________________________ >> Users mailing list >> [email protected] >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > _______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
