Hi,
you can try this:
1) activate modpram trace_on_database 1
2) use sip_trace command instead of trace_dialog
3) if method INVITE && ! has_totag
2013/12/6 Alexander Mustafin
> Hello!
>
> I need to save initial INVITE - but in-dialog messages only in sip_trace
> table. Is it possible?
>
> Bes
Hi,
it's OK ;)
indeed, enable trace_flag it's good.
thanks
2013/12/6 Bogdan-Andrei Iancu
> Hi Mickael,
>
> I see you commented the "trace_flag" parameter in your modparm section -
> please enable it back. Even if you do not use it from script, it is
> internally used by the module.
>
> Best r
Hello!
I need to save initial INVITE - but in-dialog messages only in sip_trace table.
Is it possible?
Best regards,
Alexander Mustafin
mustafin.aleksa...@gmail.com
06 дек. 2013 г., в 15:25, Bogdan-Andrei Iancu написал(а):
> Hi Mickael,
>
> I see you commented the "trace_flag" parameter i
Hi Mickael,
I see you commented the "trace_flag" parameter in your modparm section -
please enable it back. Even if you do not use it from script, it is
internally used by the module.
Best regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 06.12
Hi Bigdan,
thanks for your answer.
I have modify my opensips code:
*my conf:*
setdebug(6);
trace_dialog();
setdebug();
*see below my opensips.log*
*Dec 6 08:38:22 core-sip-2 /usr/local/sbin/opensips[2054]:
DBG:dialog:build_new_dlg: new dialog 0x806aee888
(c=11043
Hello Mickael,
Try to place the trace_dialog() between a set_debug(6) and set_debug(),
to see what is going on inside the function. Maybe the debug logs will
give you an idea.
Best regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 05.12.2013 09
Hi list,
I have an issue with my siptrace module.
see below my extract of opensips.cfg.
I want duplicate dialogs's messages to the other server (10.84.8.201), no
DB.
But, it doesn't work... no sip message in my wireshark trace.
Have you an idea ?
Thanks in advance
*# --
: [OpenSIPS-Users] Siptrace Issue
Bogdan,
The patch did solve the error I was receiving, however, now I am
receiving a
new error "ERROR:siptrace:pipport2su: invalid port number; must
be in
[1024,65536]". I captured some information from the branch
route and I also
modified the error
-
From: users-boun...@lists.opensips.org
[mailto:users-boun...@lists.opensips.org] On Behalf Of Seth Schultz
Sent: Thursday, February 07, 2013 7:40 PM
To: Bogdan-Andrei Iancu
Cc: OpenSIPS users mailling list
Subject: Re: [OpenSIPS-Users] Siptrace Issue
Bogdan,
The patch did solve the error I
-Original Message-
From: users-boun...@lists.opensips.org
[mailto:users-boun...@lists.opensips.org] On Behalf Of Seth Schultz
Sent: Thursday, February 07, 2013 7:40 PM
To: Bogdan-Andrei Iancu
Cc: OpenSIPS users mailling list
Subject: Re: [OpenSIPS-Users] Siptrace Issue
Bogdan,
The patch did
-Andrei Iancu
Cc: OpenSIPS users mailling list
Subject: Re: [OpenSIPS-Users] Siptrace Issue
Bogdan,
The patch did solve the error I was receiving, however, now I am
receiving a
new error "ERROR:siptrace:pipport2su: invalid port number; must be in
[1024,65536]". I captured some informatio
, 2013 7:40 PM
To: Bogdan-Andrei Iancu
Cc: OpenSIPS users mailling list
Subject: Re: [OpenSIPS-Users] Siptrace Issue
Bogdan,
The patch did solve the error I was receiving, however, now I am
receiving a
new error "ERROR:siptrace:pipport2su: invalid port number; must be in
[1024,65536]".
high.
Wbr,
Alexandr
-Original Message-
From: users-boun...@lists.opensips.org
[mailto:users-boun...@lists.opensips.org] On Behalf Of Seth Schultz
Sent: Thursday, February 07, 2013 7:40 PM
To: Bogdan-Andrei Iancu
Cc: OpenSIPS users mailling list
Subject: Re: [OpenSIPS-Users] Siptrace Issue
-Original Message-
From: users-boun...@lists.opensips.org
[mailto:users-boun...@lists.opensips.org] On Behalf Of Seth Schultz
Sent: Thursday, February 07, 2013 7:40 PM
To: Bogdan-Andrei Iancu
Cc: OpenSIPS users mailling list
Subject: Re: [OpenSIPS-Users] Siptrace Issue
Bogdan,
The patch did
, February 07, 2013 7:40 PM
To: Bogdan-Andrei Iancu
Cc: OpenSIPS users mailling list
Subject: Re: [OpenSIPS-Users] Siptrace Issue
Bogdan,
The patch did solve the error I was receiving, however, now I am receiving a
new error "ERROR:siptrace:pipport2su: invalid port number; must be in
[1024,65536]
Bogdan,
The patch did solve the error I was receiving, however, now I am
receiving a new error "ERROR:siptrace:pipport2su: invalid port number;
must be in [1024,65536]". I captured some information from the branch
route and I also modified the error message to display the port number.
I als
Hi Seth,
Thanks a lot for your help - I found and hopefully fixed the bug - I
made the commit on SVN trunk only and I would ask you to test it first
(see the attached patch). Let me know if works fine for you and i will
do the backport .
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Dev
On Behalf Of Seth Schultz
Sent: Wednesday, February 06, 2013 12:09 AM
To: OpenSIPS users mailling list
Subject: [OpenSIPS-Users] Siptrace Issue
Hello,
Could someone please help me resolve the following error message
"ERROR:siptrace:pipport2su: no port specified". This error only happen
ginal Message-
From: users-boun...@lists.opensips.org
[mailto:users-boun...@lists.opensips.org] On Behalf Of Bogdan-Andrei Iancu
Sent: Wednesday, February 06, 2013 9:24 PM
To: Seth Schultz
Cc: OpenSIPS users mailling list
Subject: Re: [OpenSIPS-Users] Siptrace Issue
Thanks !
Looks like the a
xandr
-Original Message-
From: users-boun...@lists.opensips.org
[mailto:users-boun...@lists.opensips.org] On Behalf Of Bogdan-Andrei Iancu
Sent: Wednesday, February 06, 2013 9:24 PM
To: Seth Schultz
Cc: OpenSIPS users mailling list
Subject: Re: [OpenSIPS-Users] Siptrace Issue
Thanks !
Looks lik
Sent: Wednesday, February 06, 2013 12:09 AM
To: OpenSIPS users mailling list
Subject: [OpenSIPS-Users] Siptrace Issue
Hello,
Could someone please help me resolve the following error message
"ERROR:siptrace:pipport2su: no port specified". This error only happens on
some of the sip pack
mailling list
Subject: Re: [OpenSIPS-Users] Siptrace Issue
That's because you need to have "root" permissions to write into
/proc/sys/kernel/core_pattern (used for forcing the core file pattern).
You should comment in the init.d file the line for writting into that file.
Regards,
Bogd
loadmodule "db_mysql.so"
loadmodule "cfgutils.so"
loadmodule "avpops.so"
loadmodule "mi_fifo.so"
loadmodule "maxfwd.so"
loadmodule "nathelper.so"
loadmodule "tm.so"
loadmodule "dialplan.so"
loadmodule "sl.so"
loadmodule "rr.so"
loadmodule "dialog.so"
loadmodule "uri.so"
loadmodule "textops.so"
loa
I see...Could you send me the list of modules you are using ?
Thanks!
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 02/06/2013 10:29 PM, Seth Schultz wrote:
I have seen this error occur on both 1.8.2 and 1.9.0. Below is the
output from opensips -V on
I have seen this error occur on both 1.8.2 and 1.9.0. Below is the
output from opensips -V on both versions I am running. The trace I
provided came from 1.9.0-rc-notls.
Thanks,
Seth
(My development environment)
version: opensips 1.9.0-rc-notls (x86_64/linux)
flags: STATS: Off, USE_IPV6, USE_
Thanks !
Looks like the actual socket structure is altered :
sock_str = {s = 0x7f4818da11b8 "udp:172.16.1.115", len = 21}
length is 21, while only 16 chars are printed -> 5 are missing ( ':' + 4
for port) .
What exact opensips revision are you using ? I need to figure out a way
to see w
Here is the output:
#0 0x7f4820da1425 in raise () from /lib/x86_64-linux-gnu/libc.so.6
(gdb) f 5
#5 0x7f4815ef8a61 in trace_msg_out (msg=0x7f4817464340,
sbuf=, send_sock=, proto=1, to=out>) at siptrace.c:1053
1053if (save_siptrace(msg,avp,&avp_value,db_keys,db_vals) < 0) {
Cool :)
In gdb, please do :
f 5
p trace_local_ip
p send_sock
p to
f 6
p ((struct dest_info*)ps->extra2)->send_sock
p *((struct dest_info*)ps->extra2)->send_sock
Thanks,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 02/06/2013 09:48 PM, Seth Schultz w
Thanks for all your help. I was finally able to get the system to dump
a core file. Here is the output from the backtrace.
#0 0x7f4820da1425 in raise () from /lib/x86_64-linux-gnu/libc.so.6
#1 0x7f4820da4b8b in abort () from /lib/x86_64-linux-gnu/libc.so.6
#2 0x7f4815ee2d30 in p
That's because you need to have "root" permissions to write into
/proc/sys/kernel/core_pattern (used for forcing the core file pattern).
You should comment in the init.d file the line for writting into that file.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-s
Unfortunately I am having trouble getting the system to dump a core
file. Here is the error message I am getting once I enable core dumps.
/etc/init.d/opensips: 103: /etc/init.d/opensips: cannot create
/proc/sys/kernel/core_pattern: Permission denied
I have also tried starting opensips as th
yes, you have to, if using the debian init.d files.
The core will be dumped into the opensips working directory - if not
configured one, it will be in root file system "/".
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 02/06/2013 07:02 PM,
I assume I also need to set the following variable in /etc/default/opensips.
change
DUMP_CORE=no
to
DUMP_CORE=yes
This may be a silly question, but where will it dump the core file to?
Thanks,
Seth
Seth Schultz
E-Mail: sschu...@scholarchip.com
Phone: 212.255.8005 x 124
Fax: 212.255.8091
On 2/
Where you changed the LM_ERR() in code, after it, simply put : abort();
. Recompile and run again -> when you get the error, opensips should
stop by itself with a core dump. Once you get the core file, use gdb to
get a backtrace (run "bt" on gdb).
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founde
Bogdan-Andrei,
Thank you for the reply. I have seen this error occur in both 1.8.2 and
1.9.0. Would you please explain exactly how I can catch the error and
call abort()? Also, is there anything else I can enable which would
help us track down the cause?
Thanks,
Seth
Seth Schultz
E-Mail:
Hi Seth,
That is really strange - using 1.9 or 1.8 ?
Do make it short, could you put an "abort()" when the error is triggered
? -> we could look into backtrace to see where the faulty string comes from.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions
Hello,
Could someone please help me resolve the following error message
"ERROR:siptrace:pipport2su: no port specified". This error only happens
on some of the sip packets, but I can't determine why. When this error
occurs, the trace for those packets never make it to my homer capture
server
37 matches
Mail list logo
