Hi Bogdan
I got it fixed. The problem is on this line:
if(!t_relay("0x05"))
if I change to if(!t_relay())
everything is ok. Don't know what is 0x05 mean.
Regards,
Halomoan
On 9/10/07, Halomoan Chow halomoan@gmail.com wrote:
Hi
My Openser version is openser-1.2.0-notls and the Mediaproxy is mediaproxy-1.9.0 I was using the openser.cfg that was generated from http://www.sipwise.com/wizard/ for Openser + Mediaproxy only.
Just only simple call from A to B cause segmentation fault.
I don't know how to locate the core file and get the backtrace :(
Regards,
Halomoan
On 9/10/07, Bogdan-Andrei Iancu bogdan@voice-system.ro wrote:
Hi Halomoan,
provide full details about your openser version - version, how did you get it (source, binaries, etc). also locate the core file and get the backtrace.
Regards, Bogdan
Halomoan Chow wrote:
Dear All
I'm running into segmentation fault error on Openser 1.2.x with Mediaproxy. What is the first thing I should take a look into to find out which line or which module causing this segmentation fault? Thank you.
Regards,
Halomoan
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Hi,
the 0x05 flag does not exist . See: http://www.openser.org/docs/modules/1.2.x/tm.html#AEN335
I will double check to see if this may cause a crash or not.
regards, bogdan
Halomoan Chow wrote:
Hi Bogdan
I got it fixed. The problem is on this line:
if(!t_relay("0x05"))
if I change to if(!t_relay())
everything is ok. Don't know what is 0x05 mean.
Regards,
Halomoan
On 9/10/07, *Halomoan Chow* <halomoan@gmail.com mailto:halomoan@gmail.com> wrote:
Hi My Openser version is openser-1.2.0-notls and the Mediaproxy is mediaproxy-1.9.0 I was using the openser.cfg that was generated from http://www.sipwise.com/wizard/ for Openser + Mediaproxy only. Just only simple call from A to B cause segmentation fault. I don't know how to locate the core file and get the backtrace :( Regards, Halomoan On 9/10/07, *Bogdan-Andrei Iancu* <bogdan@voice-system.ro <mailto:bogdan@voice-system.ro>> wrote: Hi Halomoan, provide full details about your openser version - version, how did you get it (source, binaries, etc). also locate the core file and get the backtrace. Regards, Bogdan Halomoan Chow wrote: > Dear All > > I'm running into segmentation fault error on Openser 1.2.x with > Mediaproxy. > What is the first thing I should take a look into to find out which > line or which module causing this segmentation fault? > Thank you. > > Regards, > > Halomoan > ------------------------------------------------------------------------ > > _______________________________________________ > Users mailing list > Users@openser.org <mailto:Users@openser.org> > http://openser.org/cgi-bin/mailman/listinfo/users >
Hi,
0x05 is just 0x01 (no 100 reply) and 0x04 (no DNS failover). It is used in sip:wizard configs, and there was a segfault in the tarball of 1.2.0 (see bug ##1729833).
This is fixed in SVN and 1.2.1.
Cheers, Andreas
Bogdan-Andrei Iancu wrote:
Hi,
the 0x05 flag does not exist . See: http://www.openser.org/docs/modules/1.2.x/tm.html#AEN335
I will double check to see if this may cause a crash or not.
regards, bogdan
Halomoan Chow wrote:
Hi Bogdan
I got it fixed. The problem is on this line:
if(!t_relay("0x05"))
if I change to if(!t_relay())
everything is ok. Don't know what is 0x05 mean.
Regards,
Halomoan
On 9/10/07, *Halomoan Chow* <halomoan@gmail.com mailto:halomoan@gmail.com> wrote:
Hi My Openser version is openser-1.2.0-notls and the Mediaproxy is mediaproxy-1.9.0 I was using the openser.cfg that was generated from http://www.sipwise.com/wizard/ for Openser + Mediaproxy only. Just only simple call from A to B cause segmentation fault. I don't know how to locate the core file and get the backtrace :( Regards, Halomoan On 9/10/07, *Bogdan-Andrei Iancu* <bogdan@voice-system.ro <mailto:bogdan@voice-system.ro>> wrote: Hi Halomoan, provide full details about your openser version - version, how did you get it (source, binaries, etc). also locate the core file and get the backtrace. Regards, Bogdan Halomoan Chow wrote: > Dear All > > I'm running into segmentation fault error on Openser 1.2.x with > Mediaproxy. > What is the first thing I should take a look into to find out which > line or which module causing this segmentation fault? > Thank you. > > Regards, > > Halomoan >
> > _______________________________________________ > Users mailing list > Users@openser.org <mailto:Users@openser.org> > http://openser.org/cgi-bin/mailman/listinfo/users >
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Hi Andreas,
thanks for the update and clarification. That is true - thanks for the help.
Halomoan, use opense 1.2.2 (see download section on the web page).
Regards, Bogdan
Andreas Granig wrote:
Hi,
0x05 is just 0x01 (no 100 reply) and 0x04 (no DNS failover). It is used in sip:wizard configs, and there was a segfault in the tarball of 1.2.0 (see bug ##1729833).
This is fixed in SVN and 1.2.1.
Cheers, Andreas
Bogdan-Andrei Iancu wrote:
Hi,
the 0x05 flag does not exist . See: http://www.openser.org/docs/modules/1.2.x/tm.html#AEN335
I will double check to see if this may cause a crash or not.
regards, bogdan
Halomoan Chow wrote:
Hi Bogdan
I got it fixed. The problem is on this line:
if(!t_relay("0x05"))
if I change to if(!t_relay())
everything is ok. Don't know what is 0x05 mean.
Regards,
Halomoan
On 9/10/07, *Halomoan Chow* <halomoan@gmail.com mailto:halomoan@gmail.com> wrote:
Hi My Openser version is openser-1.2.0-notls and the Mediaproxy is mediaproxy-1.9.0 I was using the openser.cfg that was generated from http://www.sipwise.com/wizard/ for Openser + Mediaproxy only. Just only simple call from A to B cause segmentation fault. I don't know how to locate the core file and get the backtrace :( Regards, Halomoan On 9/10/07, *Bogdan-Andrei Iancu* <bogdan@voice-system.ro <mailto:bogdan@voice-system.ro>> wrote: Hi Halomoan, provide full details about your openser version - version, how did you get it (source, binaries, etc). also locate the core file and get the backtrace. Regards, Bogdan Halomoan Chow wrote: > Dear All > > I'm running into segmentation fault error on Openser 1.2.xwith > Mediaproxy. > What is the first thing I should take a look into to find out which > line or which module causing this segmentation fault? > Thank you. > > Regards, > > Halomoan >
> > _______________________________________________ > Users mailing list > Users@openser.org <mailto:Users@openser.org> > http://openser.org/cgi-bin/mailman/listinfo/users >
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
-
Andreas Granig -
Bogdan-Andrei Iancu -
Halomoan Chow