Re: [OpenSIPS-Users] Help with sip trace errors please
Hi Ha,
ha do wrote:
> Hi Bogdan
>
> the scripts/dbtext/opensips/sip_trace works without creating new
> sip_trace when opensips stop and start again :)
>
cool :)
>
> the option modparam("db_text", "db_mode", 1) doesnt help on writing :(
>
I was expecting this..
>
> the db_flatstore does store real time message but the INVITE, RINGING,
> 200ok, ACK are stored in difference files(sip_trace_9.log,
> sip_trace_10.log,sip_trace_11.log,sip_trace_12.log)
>
> "For each table there will be several files, one file for every
> OpenSIPS process that wrote some data into that table"
>
Yes, this is correct - it is done like this to avoid sync between
multiple procs trying to access the same file. But you can simply merge
the files, import them into DB and get the date (via OpenSIPS CP),
Regards,
Bogdan
>
> Thank you very much
> Ha`
>
> --- On *Thu, 12/17/09, Bogdan-Andrei Iancu //*
> wrote:
>
>
> From: Bogdan-Andrei Iancu
> Subject: Re: [OpenSIPS-Users] Help with sip trace errors please
> To: "OpenSIPS users mailling list"
> Date: Thursday, December 17, 2009, 2:44 AM
>
> Hi Ha,
>
> ha do wrote:
> > Hi Bogdan
> >
> > you need to take the new sip_trace file that comes with 6439 -
> the table
> > format was changed, not the code in opensips.
> > >>>i cannt what to do, i did new complie the source and new install
> > the opensips, i do
> > |svn co
> https://opensips.svn.sourceforge.net/svnroot/opensips/branches/1.6
> opensips_1_6 on new machine
> > then do make , then do install
> > |
> >
> [bogdan]
>
> It is not about recompiling sources - you need to use the new
> sip_trace
> file with the definition of the table (from
> scripts/dbtext/opensips/sip_trace)
>
>
> > |
> > my question :|do you have a plan to make enhancement of
> sip_trace that logs all message without stop/start opensips how to
> admin opensips without log :((
> > example : our opensips works fine for everything, but after some
> days someone calls me and ask he cannot make call at 14:00PM
> yesterday and there is no log to check
> > so ask him to make a call for debugging but the call is fine at
> debugging time
> >
> > if the siptrace module works without stop
> > and start opensips, i will open the log to check what happen
> with him at this time :)
> >
> >
> [bogdan]
> probably you mean that, when using dbtext, you do not see the
> content of
> the table untill a restart of opensips, right ? if so may try using
> db_mode = 1 for db_text module
> (http://www.opensips.org/html/docs/modules/devel/db_text.html#id228234),
>
> but I'm not sure it this non-caching mode will affect the "write" ops
> also (and not only the "read" ops).
>
> Another solution is to use the db_flatstore driver (instead of
> db_text)
> -> this one does realtime writing on file.
>
>
> Regards,
> Bogdan
>
> > Thank you
> > Ha`
> >
> > --- On *Tue, 12/15/09, Bogdan-Andrei Iancu
> />/*
> > wrote:
> >
> >
> > From: Bogdan-Andrei Iancu >
> > Subject: Re: [OpenSIPS-Users] Help with sip trace errors please
> > To: "OpenSIPS users mailling list" >
> > Date: Tuesday, December 15, 2009, 12:47 AM
> >
> > Hi Ha,
> >
> > ha do wrote:
> > > Hi Bogdan
> > >
> > > i use the Checked out revision 6439.
> > > it is still issue when the sip_trace has content
> > >
> > you need to take the new sip_trace file that comes with 6439
> - the
> > table
> > format was changed, not the code in opensips.
> > >
> > > do you have a plan to make enhancement of sip_trace that
> logs all
> > > message without stop/start opensips
> > > how to admin opensips without log :((
> > >
> > I do not understand your question...could you rephrase ?
> >
> >
>
--
Bogdan-Andrei Iancu
www.voice-system.ro
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Help with sip trace errors please
Hi Bogdan
the scripts/dbtext/opensips/sip_trace works without creating new sip_trace when
opensips stop and start again :)
the option modparam("db_text", "db_mode", 1) doesnt help on writing :(
the db_flatstore does store real time message but the INVITE, RINGING, 200ok,
ACK are stored in difference files(sip_trace_9.log,
sip_trace_10.log,sip_trace_11.log,sip_trace_12.log)
"For each table there will be several
files, one file for every OpenSIPS process that wrote some data
into
that table"
Thank you very much
Ha`
--- On Thu, 12/17/09, Bogdan-Andrei Iancu wrote:
From: Bogdan-Andrei Iancu
Subject: Re: [OpenSIPS-Users] Help with sip trace errors please
To: "OpenSIPS users mailling list"
Date: Thursday, December 17, 2009, 2:44 AM
Hi Ha,
ha do wrote:
> Hi Bogdan
>
> you need to take the new sip_trace file that comes with 6439 - the table
> format was changed, not the code in opensips.
> >>>i cannt what to do, i did new complie the source and new install
> the opensips, i do
> |svn co https://opensips.svn.sourceforge.net/svnroot/opensips/branches/1.6
> opensips_1_6 on new machine
> then do make , then do install
> |
>
[bogdan]
It is not about recompiling sources - you need to use the new sip_trace
file with the definition of the table (from
scripts/dbtext/opensips/sip_trace)
> |
> my question :|do you have a plan to make enhancement of sip_trace that logs
> all message without stop/start opensips how to admin opensips without log :((
> example : our opensips works fine for everything, but after some days someone
> calls me and ask he cannot make call at 14:00PM yesterday and there is no log
> to check
> so ask him to make a call for debugging but the call is fine at debugging time
>
> if the siptrace module works without stop
> and start opensips, i will open the log to check what happen with him at
>this time :)
>
>
[bogdan]
probably you mean that, when using dbtext, you do not see the content of
the table untill a restart of opensips, right ? if so may try using
db_mode = 1 for db_text module
(http://www.opensips.org/html/docs/modules/devel/db_text.html#id228234),
but I'm not sure it this non-caching mode will affect the "write" ops
also (and not only the "read" ops).
Another solution is to use the db_flatstore driver (instead of db_text)
-> this one does realtime writing on file.
Regards,
Bogdan
> Thank you
> Ha`
>
> --- On *Tue, 12/15/09, Bogdan-Andrei Iancu //*
> wrote:
>
>
> From: Bogdan-Andrei Iancu
> Subject: Re: [OpenSIPS-Users] Help with sip trace errors please
> To: "OpenSIPS users mailling list"
> Date: Tuesday, December 15, 2009, 12:47 AM
>
> Hi Ha,
>
> ha do wrote:
> > Hi Bogdan
> >
> > i use the Checked out revision 6439.
> > it is still issue when the sip_trace has content
> >
> you need to take the new sip_trace file that comes with 6439 - the
> table
> format was changed, not the code in opensips.
> >
> > do you have a plan to make enhancement of sip_trace that logs all
> > message without stop/start opensips
> > how to admin opensips without log :((
> >
> I do not understand your question...could you rephrase ?
>
> Regards,
> Bogdan
>
>
>
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
--
Bogdan-Andrei Iancu
www.voice-system.ro
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Help with sip trace errors please
Hi Ha, ha do wrote: > Hi Bogdan > > you need to take the new sip_trace file that comes with 6439 - the table > format was changed, not the code in opensips. > >>>i cannt what to do, i did new complie the source and new install > the opensips, i do > |svn co https://opensips.svn.sourceforge.net/svnroot/opensips/branches/1.6 > opensips_1_6 on new machine > then do make , then do install > | > [bogdan] It is not about recompiling sources - you need to use the new sip_trace file with the definition of the table (from scripts/dbtext/opensips/sip_trace) > | > my question :|do you have a plan to make enhancement of sip_trace that logs > all message without stop/start opensips how to admin opensips without log :(( > example : our opensips works fine for everything, but after some days someone > calls me and ask he cannot make call at 14:00PM yesterday and there is no log > to check > so ask him to make a call for debugging but the call is fine at debugging time > > if the siptrace module works without stop > and start opensips, i will open the log to check what happen with him at > this time :) > > [bogdan] probably you mean that, when using dbtext, you do not see the content of the table untill a restart of opensips, right ? if so may try using db_mode = 1 for db_text module (http://www.opensips.org/html/docs/modules/devel/db_text.html#id228234), but I'm not sure it this non-caching mode will affect the "write" ops also (and not only the "read" ops). Another solution is to use the db_flatstore driver (instead of db_text) -> this one does realtime writing on file. Regards, Bogdan > Thank you > Ha` > > --- On *Tue, 12/15/09, Bogdan-Andrei Iancu //* > wrote: > > > From: Bogdan-Andrei Iancu > Subject: Re: [OpenSIPS-Users] Help with sip trace errors please > To: "OpenSIPS users mailling list" > Date: Tuesday, December 15, 2009, 12:47 AM > > Hi Ha, > > ha do wrote: > > Hi Bogdan > > > > i use the Checked out revision 6439. > > it is still issue when the sip_trace has content > > > you need to take the new sip_trace file that comes with 6439 - the > table > format was changed, not the code in opensips. > > > > do you have a plan to make enhancement of sip_trace that logs all > > message without stop/start opensips > > how to admin opensips without log :(( > > > I do not understand your question...could you rephrase ? > > Regards, > Bogdan > > > > > ___ > Users mailing list > Users@lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > -- Bogdan-Andrei Iancu www.voice-system.ro ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Help with sip trace errors please
Hi Bogdan you need to take the new sip_trace file that comes with 6439 - the table format was changed, not the code in opensips. >>>i cannt what to do, i did new complie the source and new install the >>>opensips, i do svn co https://opensips.svn.sourceforge.net/svnroot/opensips/branches/1.6 opensips_1_6 on new machine then do make , then do install my question :do you have a plan to make enhancement of sip_trace that logs all message without stop/start opensips how to admin opensips without log :(( example : our opensips works fine for everything, but after some days someone calls me and ask he cannot make call at 14:00PM yesterday and there is no log to check so ask him to make a call for debugging but the call is fine at debugging time if the siptrace module works without stop and start opensips, i will open the log to check what happen with him at this time :) Thank you Ha` --- On Tue, 12/15/09, Bogdan-Andrei Iancu wrote: From: Bogdan-Andrei Iancu Subject: Re: [OpenSIPS-Users] Help with sip trace errors please To: "OpenSIPS users mailling list" Date: Tuesday, December 15, 2009, 12:47 AM Hi Ha, ha do wrote: > Hi Bogdan > > i use the Checked out revision 6439. > it is still issue when the sip_trace has content > you need to take the new sip_trace file that comes with 6439 - the table format was changed, not the code in opensips. > > do you have a plan to make enhancement of sip_trace that logs all > message without stop/start opensips > how to admin opensips without log :(( > I do not understand your question...could you rephrase ? Regards, Bogdan ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Help with sip trace errors please
Hi Ha, ha do wrote: > Hi Bogdan > > i use the Checked out revision 6439. > it is still issue when the sip_trace has content > you need to take the new sip_trace file that comes with 6439 - the table format was changed, not the code in opensips. > > do you have a plan to make enhancement of sip_trace that logs all > message without stop/start opensips > how to admin opensips without log :(( > I do not understand your question...could you rephrase ? Regards, Bogdan > > Thank you > Ha` > > --- On *Mon, 12/14/09, Bogdan-Andrei Iancu //* > wrote: > > > From: Bogdan-Andrei Iancu > Subject: Re: [OpenSIPS-Users] Help with sip trace errors please > To: "OpenSIPS users mailling list" > Date: Monday, December 14, 2009, 5:38 AM > > Hi Ha, > > found the bug - there was an issue when loading the sip_trace file > with > content (some columns being NULL). > > I fixed the problem on SVN, so if you do an update and re-compile, > you > should not need to delete the file during restarts. > > Thanks and regards, > Bogdan > > ha do wrote: > > HI Bogdan > > > > it is clear now :) > > > > f the file has content (aside the first line), the siptrace module > > does not start ? > > no, the sip_trace module starts fine, i only need to replace new > > sip_trace file then the error is gone :) > > > > is there a module with the same function as sip_trace but no > need to > > shutdown opensips > > > > > > Thank you > > Ha` > > > > --- On *Fri, 12/11/09, Bogdan-Andrei Iancu > />/* > > wrote: > > > > > > From: Bogdan-Andrei Iancu > > > Subject: Re: [OpenSIPS-Users] Help with sip trace errors please > > To: "OpenSIPS users mailling list" > > > Date: Friday, December 11, 2009, 11:18 AM > > > > Hi Ha, > > > > Note that the DB content is updated only at shutdown. > > > > So, to synthesize - if the file has content (aside the first > > line), the > > siptrace module does not start ? > > > > Regards, > > Bogdan > > > > ha do wrote: > > > HI Brian > > > > > > [r...@localhost opensipsdb]# ls -ld /tmp/opensipsdb/ > > > drwxr-xr-x 2 root root 4096 Dec 11 14:56 /tmp/opensipsdb/ > > > [r...@localhost opensipsdb]# ls -ld /tmp/opensipsdb/sip_trace > > > -rw-r--r-- 1 root root 168 Dec 11 14:56 > /tmp/opensipsdb/sip_trace > > > [r...@localhost opensipsdb]# ps axu | grep opensips > > > root 2014 0.0 1.1 38072 2928 ?S > 14:56 0:00 > > > /usr/local/sbin/opensips > > > root 2016 0.0 0.3 38072 824 ?S > 14:56 0:00 > > > /usr/local/sbin/opensips > > > root 2017 0.0 0.3 38072 796 ?S > 14:56 0:00 > > > /usr/local/sbin/opensips > > > root 2018 0.0 0.3 38072 796 ?S > 14:56 0:00 > > > /usr/local/sbin/opensips > > > root 2019 0.0 0.3 38072 796 ?S > 14:56 0:00 > > > /usr/local/sbin/opensips > > > root 2020 0.0 0.6 38072 1712 ?S > 14:56 0:00 > > > /usr/local/sbin/opensips > > > root 2021 0.0 0.6 38072 1696 ?S > 14:56 0:00 > > > /usr/local/sbin/opensips > > > root 2022 0.0 0.6 38072 1724 ?S > 14:56 0:00 > > > /usr/local/sbin/opensips > > > root 2023 0.0 0.6 38072 1588 ?S > 14:56 0:00 > > > /usr/local/sbin/opensips > > > root 2024 0.0 0.2 38072 632 ?S > 14:56 0:00 > > > /usr/local/sbin/opensips > > > root 2025 0.0 0.3 38072 948 ?S > 14:56 0:00 > > > /usr/local/sbin/opensips > > > root 2026 0.0 0.3 38076 824 ?S > 14:56 0:00 > > > /usr/local/sbin/opensips > > > root 2027 0.0 0.3 38072 892 ?R > 14:56 0:00 > > > /usr/local/sbin/opensips > > > root 2028 0.0 0.3 38072 892 ?
Re: [OpenSIPS-Users] Help with sip trace errors please
Hi Bogdan i use the Checked out revision 6439. it is still issue when the sip_trace has content do you have a plan to make enhancement of sip_trace that logs all message without stop/start opensips how to admin opensips without log :(( Thank you Ha` --- On Mon, 12/14/09, Bogdan-Andrei Iancu wrote: From: Bogdan-Andrei Iancu Subject: Re: [OpenSIPS-Users] Help with sip trace errors please To: "OpenSIPS users mailling list" Date: Monday, December 14, 2009, 5:38 AM Hi Ha, found the bug - there was an issue when loading the sip_trace file with content (some columns being NULL). I fixed the problem on SVN, so if you do an update and re-compile, you should not need to delete the file during restarts. Thanks and regards, Bogdan ha do wrote: > HI Bogdan > > it is clear now :) > > f the file has content (aside the first line), the siptrace module > does not start ? > no, the sip_trace module starts fine, i only need to replace new > sip_trace file then the error is gone :) > > is there a module with the same function as sip_trace but no need to > shutdown opensips > > > Thank you > Ha` > > --- On *Fri, 12/11/09, Bogdan-Andrei Iancu //* > wrote: > > > From: Bogdan-Andrei Iancu > Subject: Re: [OpenSIPS-Users] Help with sip trace errors please > To: "OpenSIPS users mailling list" > Date: Friday, December 11, 2009, 11:18 AM > > Hi Ha, > > Note that the DB content is updated only at shutdown. > > So, to synthesize - if the file has content (aside the first > line), the > siptrace module does not start ? > > Regards, > Bogdan > > ha do wrote: > > HI Brian > > > > [r...@localhost opensipsdb]# ls -ld /tmp/opensipsdb/ > > drwxr-xr-x 2 root root 4096 Dec 11 14:56 /tmp/opensipsdb/ > > [r...@localhost opensipsdb]# ls -ld /tmp/opensipsdb/sip_trace > > -rw-r--r-- 1 root root 168 Dec 11 14:56 /tmp/opensipsdb/sip_trace > > [r...@localhost opensipsdb]# ps axu | grep opensips > > root 2014 0.0 1.1 38072 2928 ? S 14:56 0:00 > > /usr/local/sbin/opensips > > root 2016 0.0 0.3 38072 824 ? S 14:56 0:00 > > /usr/local/sbin/opensips > > root 2017 0.0 0.3 38072 796 ? S 14:56 0:00 > > /usr/local/sbin/opensips > > root 2018 0.0 0.3 38072 796 ? S 14:56 0:00 > > /usr/local/sbin/opensips > > root 2019 0.0 0.3 38072 796 ? S 14:56 0:00 > > /usr/local/sbin/opensips > > root 2020 0.0 0.6 38072 1712 ? S 14:56 0:00 > > /usr/local/sbin/opensips > > root 2021 0.0 0.6 38072 1696 ? S 14:56 0:00 > > /usr/local/sbin/opensips > > root 2022 0.0 0.6 38072 1724 ? S 14:56 0:00 > > /usr/local/sbin/opensips > > root 2023 0.0 0.6 38072 1588 ? S 14:56 0:00 > > /usr/local/sbin/opensips > > root 2024 0.0 0.2 38072 632 ? S 14:56 0:00 > > /usr/local/sbin/opensips > > root 2025 0.0 0.3 38072 948 ? S 14:56 0:00 > > /usr/local/sbin/opensips > > root 2026 0.0 0.3 38076 824 ? S 14:56 0:00 > > /usr/local/sbin/opensips > > root 2027 0.0 0.3 38072 892 ? R 14:56 0:00 > > /usr/local/sbin/opensips > > root 2028 0.0 0.3 38072 892 ? S 14:56 0:00 > > /usr/local/sbin/opensips > > root 2029 0.0 0.3 38072 892 ? S 14:56 0:00 > > /usr/local/sbin/opensips > > root 2030 0.0 0.3 38072 892 ? S 14:56 0:00 > > /usr/local/sbin/opensips > > root 2031 0.0 0.3 38072 880 ? S 14:56 0:00 > > /usr/local/sbin/opensips > > root 2044 0.0 0.2 3904 672 pts/0 R+ 15:00 0:00 > grep > > opensips > > > > let me describe my steps: > > step1 : create file sip_trace then insert with 1 line : > > id(int,auto) time_stamp(int) callid(string) traced_user(string) > > msg(string) method(string) status(string) fromip(string) > toip(string) > > fromtag(string) direction(string) > > > > step 2 : start opensips with sip_trace enable : > /etc/init.d/opensips > > start > > > > step 3 : use xlite softphone(2000) + eyebeam(8000) register and > > register successfull > > > > step 4 : make call from 2000 to 8000 then connected fine then hangup > > > >
Re: [OpenSIPS-Users] Help with sip trace errors please
Hi Ha, found the bug - there was an issue when loading the sip_trace file with content (some columns being NULL). I fixed the problem on SVN, so if you do an update and re-compile, you should not need to delete the file during restarts. Thanks and regards, Bogdan ha do wrote: > HI Bogdan > > it is clear now :) > > f the file has content (aside the first line), the siptrace module > does not start ? > no, the sip_trace module starts fine, i only need to replace new > sip_trace file then the error is gone :) > > is there a module with the same function as sip_trace but no need to > shutdown opensips > > > Thank you > Ha` > > --- On *Fri, 12/11/09, Bogdan-Andrei Iancu //* > wrote: > > > From: Bogdan-Andrei Iancu > Subject: Re: [OpenSIPS-Users] Help with sip trace errors please > To: "OpenSIPS users mailling list" > Date: Friday, December 11, 2009, 11:18 AM > > Hi Ha, > > Note that the DB content is updated only at shutdown. > > So, to synthesize - if the file has content (aside the first > line), the > siptrace module does not start ? > > Regards, > Bogdan > > ha do wrote: > > HI Brian > > > > [r...@localhost opensipsdb]# ls -ld /tmp/opensipsdb/ > > drwxr-xr-x 2 root root 4096 Dec 11 14:56 /tmp/opensipsdb/ > > [r...@localhost opensipsdb]# ls -ld /tmp/opensipsdb/sip_trace > > -rw-r--r-- 1 root root 168 Dec 11 14:56 /tmp/opensipsdb/sip_trace > > [r...@localhost opensipsdb]# ps axu | grep opensips > > root 2014 0.0 1.1 38072 2928 ?S14:56 0:00 > > /usr/local/sbin/opensips > > root 2016 0.0 0.3 38072 824 ?S14:56 0:00 > > /usr/local/sbin/opensips > > root 2017 0.0 0.3 38072 796 ?S14:56 0:00 > > /usr/local/sbin/opensips > > root 2018 0.0 0.3 38072 796 ?S14:56 0:00 > > /usr/local/sbin/opensips > > root 2019 0.0 0.3 38072 796 ?S14:56 0:00 > > /usr/local/sbin/opensips > > root 2020 0.0 0.6 38072 1712 ?S14:56 0:00 > > /usr/local/sbin/opensips > > root 2021 0.0 0.6 38072 1696 ?S14:56 0:00 > > /usr/local/sbin/opensips > > root 2022 0.0 0.6 38072 1724 ?S14:56 0:00 > > /usr/local/sbin/opensips > > root 2023 0.0 0.6 38072 1588 ?S14:56 0:00 > > /usr/local/sbin/opensips > > root 2024 0.0 0.2 38072 632 ?S14:56 0:00 > > /usr/local/sbin/opensips > > root 2025 0.0 0.3 38072 948 ?S14:56 0:00 > > /usr/local/sbin/opensips > > root 2026 0.0 0.3 38076 824 ?S14:56 0:00 > > /usr/local/sbin/opensips > > root 2027 0.0 0.3 38072 892 ?R14:56 0:00 > > /usr/local/sbin/opensips > > root 2028 0.0 0.3 38072 892 ?S14:56 0:00 > > /usr/local/sbin/opensips > > root 2029 0.0 0.3 38072 892 ?S14:56 0:00 > > /usr/local/sbin/opensips > > root 2030 0.0 0.3 38072 892 ?S14:56 0:00 > > /usr/local/sbin/opensips > > root 2031 0.0 0.3 38072 880 ?S14:56 0:00 > > /usr/local/sbin/opensips > > root 2044 0.0 0.2 3904 672 pts/0R+ 15:00 0:00 > grep > > opensips > > > > let me describe my steps: > > step1 : create file sip_trace then insert with 1 line : > > id(int,auto) time_stamp(int) callid(string) traced_user(string) > > msg(string) method(string) status(string) fromip(string) > toip(string) > > fromtag(string) direction(string) > > > > step 2 : start opensips with sip_trace enable : > /etc/init.d/opensips > > start > > > > step 3 : use xlite softphone(2000) + eyebeam(8000) register and > > register successfull > > > > step 4 : make call from 2000 to 8000 then connected fine then hangup > > > > step5 : check the /tmp/opensipsdb/sip_trace : cat > > /tmp/opensipsdb/sip_trace and result > > [r...@localhost opensipsdb]# cat /tmp/opensipsdb/sip_trace > > id(int,auto) time_stamp(int) callid(string) traced_user(string) > > msg(string) method(string) status(string) fromip(string) > toip(string) > > fromtag(string) direction(string) > > > > step 6: wait about 3 mins > > > > step 7: chec
Re: [OpenSIPS-Users] Help with sip trace errors please
HI Bogdan it is clear now :) f the file has content (aside the first line), the siptrace module does not start ?no, the sip_trace module starts fine, i only need to replace new sip_trace file then the error is gone :) is there a module with the same function as sip_trace but no need to shutdown opensips Thank youHa` --- On Fri, 12/11/09, Bogdan-Andrei Iancu wrote: From: Bogdan-Andrei Iancu Subject: Re: [OpenSIPS-Users] Help with sip trace errors please To: "OpenSIPS users mailling list" Date: Friday, December 11, 2009, 11:18 AM Hi Ha, Note that the DB content is updated only at shutdown. So, to synthesize - if the file has content (aside the first line), the siptrace module does not start ? Regards, Bogdan ha do wrote: > HI Brian > > [r...@localhost opensipsdb]# ls -ld /tmp/opensipsdb/ > drwxr-xr-x 2 root root 4096 Dec 11 14:56 /tmp/opensipsdb/ > [r...@localhost opensipsdb]# ls -ld /tmp/opensipsdb/sip_trace > -rw-r--r-- 1 root root 168 Dec 11 14:56 /tmp/opensipsdb/sip_trace > [r...@localhost opensipsdb]# ps axu | grep opensips > root 2014 0.0 1.1 38072 2928 ? S 14:56 0:00 > /usr/local/sbin/opensips > root 2016 0.0 0.3 38072 824 ? S 14:56 0:00 > /usr/local/sbin/opensips > root 2017 0.0 0.3 38072 796 ? S 14:56 0:00 > /usr/local/sbin/opensips > root 2018 0.0 0.3 38072 796 ? S 14:56 0:00 > /usr/local/sbin/opensips > root 2019 0.0 0.3 38072 796 ? S 14:56 0:00 > /usr/local/sbin/opensips > root 2020 0.0 0.6 38072 1712 ? S 14:56 0:00 > /usr/local/sbin/opensips > root 2021 0.0 0.6 38072 1696 ? S 14:56 0:00 > /usr/local/sbin/opensips > root 2022 0.0 0.6 38072 1724 ? S 14:56 0:00 > /usr/local/sbin/opensips > root 2023 0.0 0.6 38072 1588 ? S 14:56 0:00 > /usr/local/sbin/opensips > root 2024 0.0 0.2 38072 632 ? S 14:56 0:00 > /usr/local/sbin/opensips > root 2025 0.0 0.3 38072 948 ? S 14:56 0:00 > /usr/local/sbin/opensips > root 2026 0.0 0.3 38076 824 ? S 14:56 0:00 > /usr/local/sbin/opensips > root 2027 0.0 0.3 38072 892 ? R 14:56 0:00 > /usr/local/sbin/opensips > root 2028 0.0 0.3 38072 892 ? S 14:56 0:00 > /usr/local/sbin/opensips > root 2029 0.0 0.3 38072 892 ? S 14:56 0:00 > /usr/local/sbin/opensips > root 2030 0.0 0.3 38072 892 ? S 14:56 0:00 > /usr/local/sbin/opensips > root 2031 0.0 0.3 38072 880 ? S 14:56 0:00 > /usr/local/sbin/opensips > root 2044 0.0 0.2 3904 672 pts/0 R+ 15:00 0:00 grep > opensips > > let me describe my steps: > step1 : create file sip_trace then insert with 1 line : > id(int,auto) time_stamp(int) callid(string) traced_user(string) > msg(string) method(string) status(string) fromip(string) toip(string) > fromtag(string) direction(string) > > step 2 : start opensips with sip_trace enable : /etc/init.d/opensips > start > > step 3 : use xlite softphone(2000) + eyebeam(8000) register and > register successfull > > step 4 : make call from 2000 to 8000 then connected fine then hangup > > step5 : check the /tmp/opensipsdb/sip_trace : cat > /tmp/opensipsdb/sip_trace and result > [r...@localhost opensipsdb]# cat /tmp/opensipsdb/sip_trace > id(int,auto) time_stamp(int) callid(string) traced_user(string) > msg(string) method(string) status(string) fromip(string) toip(string) > fromtag(string) direction(string) > > step 6: wait about 3 mins > > step 7: check the sip_trace file : > [r...@localhost opensipsdb]# cat /tmp/opensipsdb/sip_trace > id(int,auto) time_stamp(int) callid(string) traced_user(string) > msg(string) method(string) status(string) fromip(string) toip(string) > fromtag(string) direction(string) > > > step 8 : stop opensips : /etc/init.d/opensips stop > > step 9: check the sip_trace file : at this time all logs are now in > the /tmp/opensipsdb/sip_trace > [r...@localhost opensipsdb]# cat /tmp/opensipsdb/sip_trace > id(int,auto) time_stamp(int) callid(string) traced_user(string) > msg(string) method(string) status(string) fromip(string) toip(string) > fromtag(string) direction(string) > 39:1260518390:MGRjYzNhYzQ0YTc2YTU0MWQyYzI4MTEyY2Q5NjcwYjI.::SIP/2.0 > 200 OK\r\nVia\: SIP/2.0/UDP > 192.168.237.1\:5592;received=192.168.237.1;branch=z9hG4bK-d8754z-5d41606f451fca7c-1---d8754z-;rport=5592\r\nContact\: > > \r\nTo\: > ;tag=5378ee52\r\nFrom\: > "2000";tag=aa323d0e\r\nCall-ID\: > MGRjYzNhYzQ0YTc2YTU0MWQyYzI4MTEyY2Q5NjcwYjI.\r\nCSeq\: 2 > BYE\r\nUser-Agent\: eyeBeam release
Re: [OpenSIPS-Users] Help with sip trace errors please
--- On Fri, 12/11/09, Bogdan-Andrei Iancu wrote: From: Bogdan-Andrei Iancu Subject: Re: [OpenSIPS-Users] Help with sip trace errors please To: "OpenSIPS users mailling list" Date: Friday, December 11, 2009, 11:18 AM Hi Ha, Note that the DB content is updated only at shutdown. So, to synthesize - if the file has content (aside the first line), the siptrace module does not start ? Regards, Bogdan ha do wrote: > HI Brian > > [r...@localhost opensipsdb]# ls -ld /tmp/opensipsdb/ > drwxr-xr-x 2 root root 4096 Dec 11 14:56 /tmp/opensipsdb/ > [r...@localhost opensipsdb]# ls -ld /tmp/opensipsdb/sip_trace > -rw-r--r-- 1 root root 168 Dec 11 14:56 /tmp/opensipsdb/sip_trace > [r...@localhost opensipsdb]# ps axu | grep opensips > root 2014 0.0 1.1 38072 2928 ? S 14:56 0:00 > /usr/local/sbin/opensips > root 2016 0.0 0.3 38072 824 ? S 14:56 0:00 > /usr/local/sbin/opensips > root 2017 0.0 0.3 38072 796 ? S 14:56 0:00 > /usr/local/sbin/opensips > root 2018 0.0 0.3 38072 796 ? S 14:56 0:00 > /usr/local/sbin/opensips > root 2019 0.0 0.3 38072 796 ? S 14:56 0:00 > /usr/local/sbin/opensips > root 2020 0.0 0.6 38072 1712 ? S 14:56 0:00 > /usr/local/sbin/opensips > root 2021 0.0 0.6 38072 1696 ? S 14:56 0:00 > /usr/local/sbin/opensips > root 2022 0.0 0.6 38072 1724 ? S 14:56 0:00 > /usr/local/sbin/opensips > root 2023 0.0 0.6 38072 1588 ? S 14:56 0:00 > /usr/local/sbin/opensips > root 2024 0.0 0.2 38072 632 ? S 14:56 0:00 > /usr/local/sbin/opensips > root 2025 0.0 0.3 38072 948 ? S 14:56 0:00 > /usr/local/sbin/opensips > root 2026 0.0 0.3 38076 824 ? S 14:56 0:00 > /usr/local/sbin/opensips > root 2027 0.0 0.3 38072 892 ? R 14:56 0:00 > /usr/local/sbin/opensips > root 2028 0.0 0.3 38072 892 ? S 14:56 0:00 > /usr/local/sbin/opensips > root 2029 0.0 0.3 38072 892 ? S 14:56 0:00 > /usr/local/sbin/opensips > root 2030 0.0 0.3 38072 892 ? S 14:56 0:00 > /usr/local/sbin/opensips > root 2031 0.0 0.3 38072 880 ? S 14:56 0:00 > /usr/local/sbin/opensips > root 2044 0.0 0.2 3904 672 pts/0 R+ 15:00 0:00 grep > opensips > > let me describe my steps: > step1 : create file sip_trace then insert with 1 line : > id(int,auto) time_stamp(int) callid(string) traced_user(string) > msg(string) method(string) status(string) fromip(string) toip(string) > fromtag(string) direction(string) > > step 2 : start opensips with sip_trace enable : /etc/init.d/opensips > start > > step 3 : use xlite softphone(2000) + eyebeam(8000) register and > register successfull > > step 4 : make call from 2000 to 8000 then connected fine then hangup > > step5 : check the /tmp/opensipsdb/sip_trace : cat > /tmp/opensipsdb/sip_trace and result > [r...@localhost opensipsdb]# cat /tmp/opensipsdb/sip_trace > id(int,auto) time_stamp(int) callid(string) traced_user(string) > msg(string) method(string) status(string) fromip(string) toip(string) > fromtag(string) direction(string) > > step 6: wait about 3 mins > > step 7: check the sip_trace file : > [r...@localhost opensipsdb]# cat /tmp/opensipsdb/sip_trace > id(int,auto) time_stamp(int) callid(string) traced_user(string) > msg(string) method(string) status(string) fromip(string) toip(string) > fromtag(string) direction(string) > > > step 8 : stop opensips : /etc/init.d/opensips stop > > step 9: check the sip_trace file : at this time all logs are now in > the /tmp/opensipsdb/sip_trace > [r...@localhost opensipsdb]# cat /tmp/opensipsdb/sip_trace > id(int,auto) time_stamp(int) callid(string) traced_user(string) > msg(string) method(string) status(string) fromip(string) toip(string) > fromtag(string) direction(string) > 39:1260518390:MGRjYzNhYzQ0YTc2YTU0MWQyYzI4MTEyY2Q5NjcwYjI.::SIP/2.0 > 200 OK\r\nVia\: SIP/2.0/UDP > 192.168.237.1\:5592;received=192.168.237.1;branch=z9hG4bK-d8754z-5d41606f451fca7c-1---d8754z-;rport=5592\r\nContact\: > > \r\nTo\: > ;tag=5378ee52\r\nFrom\: > "2000";tag=aa323d0e\r\nCall-ID\: > MGRjYzNhYzQ0YTc2YTU0MWQyYzI4MTEyY2Q5NjcwYjI.\r\nCSeq\: 2 > BYE\r\nUser-Agent\: eyeBeam release 1004p stamp > 31962\r\nContent-Length\: > 0\r\n\r\n:BYE:200:udp\:192.168.237.131\:5060:udp\:192.168.237.1\:5592:aa323d0e:out > > step 10 : start opensips again : /etc/initd/opensips start - start > successfull without problem > > step 11 : register 2000 + 8000 again > > step 12: get er
Re: [OpenSIPS-Users] Help with sip trace errors please
Hi Ha, Note that the DB content is updated only at shutdown. So, to synthesize - if the file has content (aside the first line), the siptrace module does not start ? Regards, Bogdan ha do wrote: > HI Brian > > [r...@localhost opensipsdb]# ls -ld /tmp/opensipsdb/ > drwxr-xr-x 2 root root 4096 Dec 11 14:56 /tmp/opensipsdb/ > [r...@localhost opensipsdb]# ls -ld /tmp/opensipsdb/sip_trace > -rw-r--r-- 1 root root 168 Dec 11 14:56 /tmp/opensipsdb/sip_trace > [r...@localhost opensipsdb]# ps axu | grep opensips > root 2014 0.0 1.1 38072 2928 ?S14:56 0:00 > /usr/local/sbin/opensips > root 2016 0.0 0.3 38072 824 ?S14:56 0:00 > /usr/local/sbin/opensips > root 2017 0.0 0.3 38072 796 ?S14:56 0:00 > /usr/local/sbin/opensips > root 2018 0.0 0.3 38072 796 ?S14:56 0:00 > /usr/local/sbin/opensips > root 2019 0.0 0.3 38072 796 ?S14:56 0:00 > /usr/local/sbin/opensips > root 2020 0.0 0.6 38072 1712 ?S14:56 0:00 > /usr/local/sbin/opensips > root 2021 0.0 0.6 38072 1696 ?S14:56 0:00 > /usr/local/sbin/opensips > root 2022 0.0 0.6 38072 1724 ?S14:56 0:00 > /usr/local/sbin/opensips > root 2023 0.0 0.6 38072 1588 ?S14:56 0:00 > /usr/local/sbin/opensips > root 2024 0.0 0.2 38072 632 ?S14:56 0:00 > /usr/local/sbin/opensips > root 2025 0.0 0.3 38072 948 ?S14:56 0:00 > /usr/local/sbin/opensips > root 2026 0.0 0.3 38076 824 ?S14:56 0:00 > /usr/local/sbin/opensips > root 2027 0.0 0.3 38072 892 ?R14:56 0:00 > /usr/local/sbin/opensips > root 2028 0.0 0.3 38072 892 ?S14:56 0:00 > /usr/local/sbin/opensips > root 2029 0.0 0.3 38072 892 ?S14:56 0:00 > /usr/local/sbin/opensips > root 2030 0.0 0.3 38072 892 ?S14:56 0:00 > /usr/local/sbin/opensips > root 2031 0.0 0.3 38072 880 ?S14:56 0:00 > /usr/local/sbin/opensips > root 2044 0.0 0.2 3904 672 pts/0R+ 15:00 0:00 grep > opensips > > let me describe my steps: > step1 : create file sip_trace then insert with 1 line : > id(int,auto) time_stamp(int) callid(string) traced_user(string) > msg(string) method(string) status(string) fromip(string) toip(string) > fromtag(string) direction(string) > > step 2 : start opensips with sip_trace enable : /etc/init.d/opensips > start > > step 3 : use xlite softphone(2000) + eyebeam(8000) register and > register successfull > > step 4 : make call from 2000 to 8000 then connected fine then hangup > > step5 : check the /tmp/opensipsdb/sip_trace : cat > /tmp/opensipsdb/sip_trace and result > [r...@localhost opensipsdb]# cat /tmp/opensipsdb/sip_trace > id(int,auto) time_stamp(int) callid(string) traced_user(string) > msg(string) method(string) status(string) fromip(string) toip(string) > fromtag(string) direction(string) > > step 6: wait about 3 mins > > step 7: check the sip_trace file : > [r...@localhost opensipsdb]# cat /tmp/opensipsdb/sip_trace > id(int,auto) time_stamp(int) callid(string) traced_user(string) > msg(string) method(string) status(string) fromip(string) toip(string) > fromtag(string) direction(string) > > > step 8 : stop opensips : /etc/init.d/opensips stop > > step 9: check the sip_trace file : at this time all logs are now in > the /tmp/opensipsdb/sip_trace > [r...@localhost opensipsdb]# cat /tmp/opensipsdb/sip_trace > id(int,auto) time_stamp(int) callid(string) traced_user(string) > msg(string) method(string) status(string) fromip(string) toip(string) > fromtag(string) direction(string) > 39:1260518390:MGRjYzNhYzQ0YTc2YTU0MWQyYzI4MTEyY2Q5NjcwYjI.::SIP/2.0 > 200 OK\r\nVia\: SIP/2.0/UDP > 192.168.237.1\:5592;received=192.168.237.1;branch=z9hG4bK-d8754z-5d41606f451fca7c-1---d8754z-;rport=5592\r\nContact\: > > \r\nTo\: > ;tag=5378ee52\r\nFrom\: > "2000";tag=aa323d0e\r\nCall-ID\: > MGRjYzNhYzQ0YTc2YTU0MWQyYzI4MTEyY2Q5NjcwYjI.\r\nCSeq\: 2 > BYE\r\nUser-Agent\: eyeBeam release 1004p stamp > 31962\r\nContent-Length\: > 0\r\n\r\n:BYE:200:udp\:192.168.237.131\:5060:udp\:192.168.237.1\:5592:aa323d0e:out > > step 10 : start opensips again : /etc/initd/opensips start - start > successfull without problem > > step 11 : register 2000 + 8000 again > > step 12: get error from debug : > Dec 11 15:03:49 localhost /usr/local/sbin/opensips[2120]: > ERROR:db_text:dbt_insert: table does not exist! > Dec 11 15:03:49 localhost /usr/local/sbin/opensips[2120]: > ERROR:siptrace:sip_trace: error storing trace > > > what happen in your lab, Brian > does the log of sip_trace write down to /tmp/opensipsdb/sip_trace file > right away or you need to wait some times > > > Thank you > Ha > > Are you saying that when no /tmp/opensipsdb/sip_trace exists, and > you start opensips fresh, then no error appears in the lo
Re: [OpenSIPS-Users] Help with sip trace errors please
HI Brian [r...@localhost opensipsdb]# ls -ld /tmp/opensipsdb/ drwxr-xr-x 2 root root 4096 Dec 11 14:56 /tmp/opensipsdb/ [r...@localhost opensipsdb]# ls -ld /tmp/opensipsdb/sip_trace -rw-r--r-- 1 root root 168 Dec 11 14:56 /tmp/opensipsdb/sip_trace [r...@localhost opensipsdb]# ps axu | grep opensips root 2014 0.0 1.1 38072 2928 ? S 14:56 0:00 /usr/local/sbin/opensips root 2016 0.0 0.3 38072 824 ? S 14:56 0:00 /usr/local/sbin/opensips root 2017 0.0 0.3 38072 796 ? S 14:56 0:00 /usr/local/sbin/opensips root 2018 0.0 0.3 38072 796 ? S 14:56 0:00 /usr/local/sbin/opensips root 2019 0.0 0.3 38072 796 ? S 14:56 0:00 /usr/local/sbin/opensips root 2020 0.0 0.6 38072 1712 ? S 14:56 0:00 /usr/local/sbin/opensips root 2021 0.0 0.6 38072 1696 ? S 14:56 0:00 /usr/local/sbin/opensips root 2022 0.0 0.6 38072 1724 ? S 14:56 0:00 /usr/local/sbin/opensips root 2023 0.0 0.6 38072 1588 ? S 14:56 0:00 /usr/local/sbin/opensips root 2024 0.0 0.2 38072 632 ? S 14:56 0:00 /usr/local/sbin/opensips root 2025 0.0 0.3 38072 948 ? S 14:56 0:00 /usr/local/sbin/opensips root 2026 0.0 0.3 38076 824 ? S 14:56 0:00 /usr/local/sbin/opensips root 2027 0.0 0.3 38072 892 ? R 14:56 0:00 /usr/local/sbin/opensips root 2028 0.0 0.3 38072 892 ? S 14:56 0:00 /usr/local/sbin/opensips root 2029 0.0 0.3 38072 892 ? S 14:56 0:00 /usr/local/sbin/opensips root 2030 0.0 0.3 38072 892 ? S 14:56 0:00 /usr/local/sbin/opensips root 2031 0.0 0.3 38072 880 ? S 14:56 0:00 /usr/local/sbin/opensips root 2044 0.0 0.2 3904 672 pts/0 R+ 15:00 0:00 grep opensips let me describe my steps: step1 : create file sip_trace then insert with 1 line : id(int,auto) time_stamp(int) callid(string) traced_user(string) msg(string) method(string) status(string) fromip(string) toip(string) fromtag(string) direction(string) step 2 : start opensips with sip_trace enable : /etc/init.d/opensips start step 3 : use xlite softphone(2000) + eyebeam(8000) register and register successfull step 4 : make call from 2000 to 8000 then connected fine then hangup step5 : check the /tmp/opensipsdb/sip_trace : cat /tmp/opensipsdb/sip_trace and result [r...@localhost opensipsdb]# cat /tmp/opensipsdb/sip_trace id(int,auto) time_stamp(int) callid(string) traced_user(string) msg(string) method(string) status(string) fromip(string) toip(string) fromtag(string) direction(string) step 6: wait about 3 mins step 7: check the sip_trace file : [r...@localhost opensipsdb]# cat /tmp/opensipsdb/sip_trace id(int,auto) time_stamp(int) callid(string) traced_user(string) msg(string) method(string) status(string) fromip(string) toip(string) fromtag(string) direction(string) step 8 : stop opensips : /etc/init.d/opensips stop step 9: check the sip_trace file : at this time all logs are now in the /tmp/opensipsdb/sip_trace [r...@localhost opensipsdb]# cat /tmp/opensipsdb/sip_trace id(int,auto) time_stamp(int) callid(string) traced_user(string) msg(string) method(string) status(string) fromip(string) toip(string) fromtag(string) direction(string) 39:1260518390:MGRjYzNhYzQ0YTc2YTU0MWQyYzI4MTEyY2Q5NjcwYjI.::SIP/2.0 200 OK\r\nVia\: SIP/2.0/UDP 192.168.237.1\:5592;received=192.168.237.1;branch=z9hG4bK-d8754z-5d41606f451fca7c-1---d8754z-;rport=5592\r\nContact\: \r\nTo\: ;tag=5378ee52\r\nFrom\: "2000";tag=aa323d0e\r\nCall-ID\: MGRjYzNhYzQ0YTc2YTU0MWQyYzI4MTEyY2Q5NjcwYjI.\r\nCSeq\: 2 BYE\r\nUser-Agent\: eyeBeam release 1004p stamp 31962\r\nContent-Length\: 0\r\n\r\n:BYE:200:udp\:192.168.237.131\:5060:udp\:192.168.237.1\:5592:aa323d0e:out step 10 : start opensips again : /etc/initd/opensips start - start successfull without problem step 11 : register 2000 + 8000 again step 12: get error from debug : Dec 11 15:03:49 localhost /usr/local/sbin/opensips[2120]: ERROR:db_text:dbt_insert: table does not exist! Dec 11 15:03:49 localhost /usr/local/sbin/opensips[2120]: ERROR:siptrace:sip_trace: error storing trace what happen in your lab, Brian does the log of sip_trace write down to /tmp/opensipsdb/sip_trace file right away or you need to wait some times Thank you Ha Are you saying that when no /tmp/opensipsdb/sip_trace exists, and you start opensips fresh, then no error appears in the log and the sip_trace file is created normally? And are you saying that when a /tmp/opensipsdb/sip_trace exists, and you start opensips fresh, then a error appears in the log and the sip_trace file is not written to with new transactions? Please show the errors in the log file if this is the case. Also, please tell us the results of: [r...@localhost ~]# ls -ld /tmp/opensipsdb [r...@localhost ~]# ls -ld /tmp/opensip
Re: [OpenSIPS-Users] Help with sip trace errors please
Hello Ha, An jeu., déc 10, 2009, ha do schrieb: >i found the problem here when we using the db_text, i dont know how >the opensips will write the log to the text file(sip_trace) i just >stop then start opensips again and then i see all logs in the text >file(sip_trace) > >the problem here when i start the second time -- opensips doesnt >accept the old sip_trace text file, i need to create new sip_trace >text file > >my question how long opensips will write the log to text file ?? >why opensips doesnt accept the old sip_trace text file? is there >any enhancement to use the old text file > Are you saying that when no /tmp/opensipsdb/sip_trace exists, and you start opensips fresh, then no error appears in the log and the sip_trace file is created normally? And are you saying that when a /tmp/opensipsdb/sip_trace exists, and you start opensips fresh, then a error appears in the log and the sip_trace file is not written to with new transactions? Please show the errors in the log file if this is the case. Also, please tell us the results of: [r...@localhost ~]# ls -ld /tmp/opensipsdb [r...@localhost ~]# ls -ld /tmp/opensipsdb/sip_trace [r...@localhost ~]# ps aux | grep opensips ...in order to determine if you have a permissions problem easily solved in the opensips.cfg. Regards, Brian ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Help with sip trace errors please
Hi all
i found the problem here
when we using the db_text, i dont know how the opensips will write the log to
the text file(sip_trace)
i just stop then start opensips again and then i see all logs in the text
file(sip_trace)
the problem here when i start the second time -- opensips doesnt accept the old
sip_trace text file, i need to create new sip_trace text file
my question how long opensips will write the log to text file ??
why opensips doesnt accept the old sip_trace text file? is there any
enhancement to use the old text file
Thank you
Ha`
--- On Thu, 12/10/09, ha do wrote:
From: ha do
Subject: Re: [OpenSIPS-Users] Help with sip trace errors please
To: "OpenSIPS users mailling list"
Date: Thursday, December 10, 2009, 3:29 AM
Hi Brian
i follow your suggestion and it is successfully writing the log to text file
sip_trace
the opensips.cfg
loadmodule "db_text.so"
modparam("siptrace", "trace_flag", 22)
modparam("siptrace", "db_url", "text:///tmp/opensipsdb")
modparam("siptrace", "trace_on", 1)
modparam("siptrace", "enable_ack_trace", 1)
modparam("siptrace", "table", "sip_trace")
but when you enable debug=9 in the opensips.cfg
it say the error:
Dec 10 23:53:44 localhost /usr/local/sbin/opensips[1923]:
INFO:db_text:dbt_init: using database at: /tmp/opensipsdb
Dec 10 23:54:01 localhost /usr/local/sbin/opensips[1915]:
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Help with sip trace errors please
Hi Brian
i follow your suggestion and it is successfully writing the log to text file
sip_trace
the opensips.cfg
loadmodule "db_text.so"
modparam("siptrace", "trace_flag", 22)
modparam("siptrace", "db_url", "text:///tmp/opensipsdb")
modparam("siptrace", "trace_on", 1)
modparam("siptrace", "enable_ack_trace", 1)
modparam("siptrace", "table", "sip_trace")
but when you enable debug=9 in the opensips.cfg
it say the error:
Dec 10 23:53:44 localhost /usr/local/sbin/opensips[1923]:
INFO:db_text:dbt_init: using database at: /tmp/opensipsdb
Dec 10 23:54:01 localhost /usr/local/sbin/opensips[1915]:
ERROR:db_text:dbt_insert: table does not exist!
Dec 10 23:54:01 localhost /usr/local/sbin/opensips[1915]:
ERROR:siptrace:sip_trace: error storing trace
Dec 10 23:54:01 localhost /usr/local/sbin/opensips[1915]:
ERROR:db_text:dbt_insert: table does not exist!
Dec 10 23:54:01 localhost /usr/local/sbin/opensips[1915]:
ERROR:siptrace:trace_onreply_out: error storing trace
Dec 10 23:54:01 localhost /usr/local/sbin/opensips[1915]:
ERROR:db_text:dbt_insert: table does not exist!
Dec 10 23:54:01 localhost /usr/local/sbin/opensips[1915]:
ERROR:siptrace:sip_trace: error storing trace
[r...@localhost ~]# cat /tmp/opensipsdb/sip_trace
id(int,auto) time_stamp(int) callid(string) traced_user(string) msg(string)
method(string) status(string) fromip(string) toip(string) fromtag(string)
direction(string)
36:1260463989:YzJhOTE1OWFiNWVkMzM1ZTJlM2E5ZjI1NTc2NWQyM2Y.::SIP/2.0 200
OK\r\nVia\: SIP/2.0/UDP
192.168.237.1\:53352;received=192.168.237.1;branch=z9hG4bK-d87543-a60eba2316543c40-1--d87543-;rport=53352\r\nContact\:
\r\nTo\:
"2000";tag=6e5a5b08\r\nFrom\:
;tag=415aae68\r\nCall-ID\:
YzJhOTE1OWFiNWVkMzM1ZTJlM2E5ZjI1NTc2NWQyM2Y.\r\nCSeq\: 2 BYE\r\nUser-Agent\:
X-Lite release 1103k stamp 53621\r\nContent-Length\:
0\r\n\r\n:BYE:200:udp\:192.168.237.131\:5060:udp\:192.168.237.1\:53352:415aae68:out
35:1260463989:YzJhOTE1OWFiNWVkMzM1ZTJlM2E5ZjI1NTc2NWQyM2Y.::SIP/2.0 200
OK\r\nVia\: SIP/2.0/UDP 192.168.237.131;branch=z9hG4bKde3e.722ffa76.0\r\nVia\:
SIP/2.0/UDP
192.168.237.1\:53352;received=192.168.237.1;branch=z9hG4bK-d87543-a60eba2316543c40-1--d87543-;rport=53352\r\nContact\:
\r\nTo\:
"2000";tag=6e5a5b08\r\nFrom\:
;tag=415aae68\r\nCall-ID\:
YzJhOTE1OWFiNWVkMzM1ZTJlM2E5ZjI1NTc2NWQyM2Y.\r\nCSeq\: 2 BYE\r\nUser-Agent\:
X-Lite release 1103k stamp 53621\r\nContent-Length\:
0\r\n\r\n:BYE:200:udp\:192.168.237.1\:62174:udp\:192.168.237.131\:5060:415aae68:in
--- On Wed, 12/9/09, opensipsl...@encambio.com
wrote:
From: opensipsl...@encambio.com
Subject: Re: [OpenSIPS-Users] Help with sip trace errors please
To: users@lists.opensips.org
Date: Wednesday, December 9, 2009, 11:16 AM
Hello Bogdan,
On wed., dec 09, 2009, Bogdan-Andrei Iancu wrote:
>Field 0 is the "msg" field (used as DB_BLOB by siptrace) should be
>"STR" to work, but I already see it is set at string in your table
>definition... so I looked for a bug and found one in the db_text
>module - if you update from SVN, it should be ok.
>
That is great news, but sadly I might have been able to find and
correct the problem myself if the variable naming was not so cryptic.
But thanks to you indeed, the problem is solved. I've tested your
revision 6382:
Index: modules/db_text/dbt_lib.c
diff -Nau modules/db_text/dbt_lib.c.orig modules/db_text/dbt_lib.c
--- modules/db_text/dbt_lib.c.orig 2009-10-16 02:35:15.0 +0200
+++ modules/db_text/dbt_lib.c 2009-12-09 18:14:52.707887067 +0100
@@ -446,7 +446,7 @@
if(_t0==DB_STRING || _t0==DB_BLOB)
return 0;
case DB_BLOB:
- if(_t0==DB_STR)
+ if(_t0==DB_STR || _t0==DB_STRING)
return 0;
case DB_BITMAP:
if (_t0==DB_INT)
...and it works.
Regards,
Brian
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Help with sip trace errors please
Hi Brian, CoolThanks. This will be part of the new release on the 1.6 branch. Thanks for report and testing, Bogdan opensipsl...@encambio.com wrote: > Hello Bogdan, > > On wed., dec 09, 2009, Bogdan-Andrei Iancu wrote: > >> Field 0 is the "msg" field (used as DB_BLOB by siptrace) should be >> "STR" to work, but I already see it is set at string in your table >> definition... so I looked for a bug and found one in the db_text >> module - if you update from SVN, it should be ok. >> >> > That is great news, but sadly I might have been able to find and > correct the problem myself if the variable naming was not so cryptic. > > But thanks to you indeed, the problem is solved. I've tested your > revision 6382: > > Index: modules/db_text/dbt_lib.c > diff -Nau modules/db_text/dbt_lib.c.orig modules/db_text/dbt_lib.c > --- modules/db_text/dbt_lib.c.orig 2009-10-16 02:35:15.0 +0200 > +++ modules/db_text/dbt_lib.c 2009-12-09 18:14:52.707887067 +0100 > @@ -446,7 +446,7 @@ > if(_t0==DB_STRING || _t0==DB_BLOB) > return 0; > case DB_BLOB: > - if(_t0==DB_STR) > + if(_t0==DB_STR || _t0==DB_STRING) > return 0; > case DB_BITMAP: > if (_t0==DB_INT) > > ...and it works. > > Regards, > Brian > > ___ > Users mailing list > Users@lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > -- Bogdan-Andrei Iancu www.voice-system.ro ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Help with sip trace errors please
Hello Bogdan, On wed., dec 09, 2009, Bogdan-Andrei Iancu wrote: >Field 0 is the "msg" field (used as DB_BLOB by siptrace) should be >"STR" to work, but I already see it is set at string in your table >definition... so I looked for a bug and found one in the db_text >module - if you update from SVN, it should be ok. > That is great news, but sadly I might have been able to find and correct the problem myself if the variable naming was not so cryptic. But thanks to you indeed, the problem is solved. I've tested your revision 6382: Index: modules/db_text/dbt_lib.c diff -Nau modules/db_text/dbt_lib.c.orig modules/db_text/dbt_lib.c --- modules/db_text/dbt_lib.c.orig 2009-10-16 02:35:15.0 +0200 +++ modules/db_text/dbt_lib.c 2009-12-09 18:14:52.707887067 +0100 @@ -446,7 +446,7 @@ if(_t0==DB_STRING || _t0==DB_BLOB) return 0; case DB_BLOB: - if(_t0==DB_STR) + if(_t0==DB_STR || _t0==DB_STRING) return 0; case DB_BITMAP: if (_t0==DB_INT) ...and it works. Regards, Brian ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Help with sip trace errors please
Hi Brian, Field 0 is the "msg" field (used as DB_BLOB by siptrace) should be "STR" to work, but I already see it is set at string in your table definitionso I looked for a bug and found one in the db_text module - if you update from SVN, it should be ok. Thanks and regards, Bogdan opensipsl...@encambio.com wrote: > Hello again list, > > On tues., dec 08, 2009, opensipsl...@encambio.com wrote: > >> In my /pfx/var/opensips/db/sip_trace I have: >> >>id(int,auto) time_stamp(int) callid(string) traced_user(string) >> msg(string) method(string) status(string) fromip(string) toip(string) >> fromtag(string) direction(string) >> >> ...and I see in the log: >> >>Dec 08 23:04:06 name.host.tld opensips[14400]: >> ERROR:db_text:dbt_insert: incompatible types v[0] - c[4]! >> >> > Bogdan mentioned to a previous user reporting a similar problem with > 'incompatible types v[6] - c[1]' that the 'time_stamp(str)' field > should be of type 'int'. This is not my problem (it's already int), > but I see that maybe another value is the problem. > > ...but how to map v[N] and c[M] to db_text fields? The sourcecode is > horrible in this respect, and doesn't help at all. > > Can I presume that v[] is the datatype, and c[] the column number? > So I guess my problem is that datatype '0' is wrong for column '4' > (msg if using '0' as the starting column.) But what is the datatype > '0' mapped to, and what should the column 'msg' be? > > Thanks, > Brian > > ___ > Users mailing list > Users@lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > -- Bogdan-Andrei Iancu www.voice-system.ro ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Help with sip trace errors please
Hello list, On tues., dec 08, 2009, opensipsl...@encambio.com wrote: >On tues., dec 08, 2009, opensipsl...@encambio.com wrote: >>In my /pfx/var/opensips/db/sip_trace I have: >> >>id(int,auto) time_stamp(int) callid(string) traced_user(string) >> msg(string) method(string) status(string) fromip(string) toip(string) >> fromtag(string) direction(string) >> >>...and I see in the log: >> >>Dec 08 23:04:06 name.host.tld opensips[14400]: >> ERROR:db_text:dbt_insert: incompatible types v[0] - c[4]! >> >...but how to map v[N] and c[M] to db_text fields? > Any documentation for mapping of db_text source code fields 'v' and 'c' to columns and datatypes in the db_text tables? I still don't know what 'incompatible types v[0] - c[4]' means in the context of the error in the sip trace module, but I have the impression that the OpenSIPS 1.6.0 distribution ships with one of these columns/datatypes not in order. Which one is it? Thanks, Brian ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Help with sip trace errors please
Hello again list, On tues., dec 08, 2009, opensipsl...@encambio.com wrote: >In my /pfx/var/opensips/db/sip_trace I have: > >id(int,auto) time_stamp(int) callid(string) traced_user(string) > msg(string) method(string) status(string) fromip(string) toip(string) > fromtag(string) direction(string) > >...and I see in the log: > >Dec 08 23:04:06 name.host.tld opensips[14400]: > ERROR:db_text:dbt_insert: incompatible types v[0] - c[4]! > Bogdan mentioned to a previous user reporting a similar problem with 'incompatible types v[6] - c[1]' that the 'time_stamp(str)' field should be of type 'int'. This is not my problem (it's already int), but I see that maybe another value is the problem. ...but how to map v[N] and c[M] to db_text fields? The sourcecode is horrible in this respect, and doesn't help at all. Can I presume that v[] is the datatype, and c[] the column number? So I guess my problem is that datatype '0' is wrong for column '4' (msg if using '0' as the starting column.) But what is the datatype '0' mapped to, and what should the column 'msg' be? Thanks, Brian ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] Help with sip trace errors please
Hello List,
In my config file I have:
debug=20
loadmodule "siptrace.so"
modparam("siptrace", "db_url", "text:///pfx/var/opensips/db")
modparam("siptrace", "trace_on", 1)
modparam("siptrace", "trace_flag", 22)
modparam("siptrace", "table", "sip_trace")
modparam("siptrace", "enable_ack_trace", 0)
route {
sip_trace();
setflag(22);
setbflag(22);
In my /pfx/var/opensips/db/sip_trace I have:
id(int,auto) time_stamp(int) callid(string) traced_user(string) msg(string)
method(string) status(string) fromip(string) toip(string) fromtag(string)
direction(string)
...and I see in the log:
Dec 08 23:04:06 name.host.tld opensips[14400]:
DBG:core:_shm_resize: resize(0) called
Dec 08 23:04:06 name.host.tld opensips[14400]: DBG:tm:relay_reply:
sent buf=832dbd8: SIP/2.0 2..., shmem=ceb574d0: SIP/2.0 2
Dec 08 23:04:06 name.host.tld opensips[14400]:
DBG:tm:run_trans_callbacks: trans=ceb55540, callback type 256, id 2 entered
Dec 08 23:04:06 name.host.tld opensips[14400]:
DBG:siptrace:trace_onreply_out: dest [udp:80.190.139.22:5080]
Dec 08 23:04:06 name.host.tld opensips[14400]:
DBG:siptrace:trace_onreply_out: storing info...
Dec 08 23:04:06 name.host.tld opensips[14400]:
DBG:db_text:dbt_db_get_table: cache or mtime succeeded for [sip_trace]
** Here! ** Dec 08 23:04:06 name.host.tld opensips[14400]:
ERROR:db_text:dbt_insert: incompatible types v[0] - c[4]!
Dec 08 23:04:06 name.host.tld opensips[14400]:
ERROR:siptrace:trace_onreply_out: error storing trace
Dec 08 23:04:06 name.host.tld opensips[14400]:
DBG:tm:cleanup_uac_timers: RETR/FR timers reset
Dec 08 23:04:06 name.host.tld opensips[14400]: DBG:tm:t_unref:
UNREF_UNSAFE: after is 0
Dec 08 23:04:06 name.host.tld opensips[14400]:
DBG:core:destroy_avp_list: destroying list 0
Dec 08 23:04:06 name.host.tld opensips[14400]:
DBG:core:receive_msg: cleaning up
I'm using OpenSIPS 1.6.0 with TLS on Solaris x86 11 (nv-b91). Is the
sip trace module being maintained any more, or at least in working
condition with dbtext? Any idea what I'm doing wrong?
Thanks,
Brian
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
