Hello again. I've made a diff between two SEMS core/ sources - a working sources ( is a current folder ) and a latest from git that isn't working ( a ../sems_last/core folder ) Please take a look on it http://pastebin.com/7QBGREfD
WBR, Anton Zagorskiy VoIP Developer, Oyster Telecom Phone.: +7 812 601-0666 Fax: +7 812 601-0593 [email protected] www.oyster-telecom.ru > -----Original Message----- > From: [email protected] [mailto:sems- > [email protected]] On Behalf Of Anton Zagorskiy > Sent: Monday, March 21, 2011 4:05 PM > To: 'Raphael Coeffic' > Cc: [email protected] > Subject: Re: [Sems] early_announce > > Hi Raphael. > > I've tried run SEMS in gdb (with fork=no in the conf) : > > [root@ssw /home/amberovsky/src/sems-1.4.0]# gdb --args > /usr/local/sbin/sems > -f /usr/local/etc/sems/sems.conf -u sems -g softswitch -P > /var/run/softswitch/sems.pid > GNU gdb 6.1.1 [FreeBSD] > Copyright 2004 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and > you are > welcome to change it and/or distribute copies of it under certain > conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for > details. > This GDB was configured as "amd64-marcel-freebsd"... > (gdb) set follow-fork-mode child > (gdb) run > Starting program: /usr/local/sbin/sems -f /usr/local/etc/sems/sems.conf > -u > sems -g softswitch -P /var/run/softswitch/sems.pid > [New LWP 100399] > [New Thread 8010041c0 (LWP 100399)] > Configuration: > log level: DEBUG (3) > log to stderr: no > configuration file: /usr/local/etc/sems/sems.conf > plug-in path: /usr/local/lib/sems/plug-in/ > daemon mode: no > daemon UID: sems > daemon GID: softswitch > application: early_announce > > [New Thread 80100ae40 (LWP 100383)] > [New Thread 80100ac80 (LWP 100420)] > [New Thread 80100aac0 (LWP 100421)] > [New Thread 80100a900 (LWP 100422)] > [New Thread 80100a740 (LWP 100423)] > [New Thread 80100a580 (LWP 100424)] > [New Thread 80100a3c0 (LWP 100433)] > [New Thread 80100a200 (LWP 100461)] > [New Thread 80100a040 (LWP 100495)] > [New Thread 801009e80 (LWP 100517)] > [New Thread 801009cc0 (LWP 100521)] > [New Thread 801009b00 (LWP 100524)] > > > When I'm calling to SEMS it just adds threads - 2 for a first call and > 1 for > each next: > > First: > [New Thread 802a59c80 (LWP 100525)] > [New Thread 802c70c80 (LWP 100526)] > (Call was ended) > > Second: > [New Thread 802a9cac0 (LWP 100528)] > (Call was ended) > > Third: > [New Thread 802a9c900 (LWP 100529)] > > ... > > > As you can see there are no any exceptions. I didn't find SEMS core > file. Is > there a option to point SEMS to a directory where it should place core > file? > > > > WBR, Anton Zagorskiy > VoIP Developer, Oyster Telecom > Phone.: +7 812 601-0666 > Fax: +7 812 601-0593 > [email protected] > www.oyster-telecom.ru > > > > > -----Original Message----- > > From: Raphael Coeffic [mailto:[email protected]] > > Sent: Wednesday, March 16, 2011 2:32 PM > > To: Anton Zagorskiy > > Cc: [email protected] > > Subject: Re: [Sems] early_announce > > > > Anton, > > > > there is a little chance that some unknown exception is triggered and > > thus kills the session thread. You might try letting SEMS run in gdb, > > or > > using ulimit -c unlimited before to allow for a core dump to be > > generated. Once you have a core dump, or gdb stopped at that place, > you > > could get a stack trace, thread list, etc... > > > > Thanks > > Raphael. > > > > On 16.03.11 12:04, Raphael Coeffic wrote: > > > Hi Anton, > > > > > > your trace really looks strange.... I have to take a deeper look at > > > it. Please stay tuned ;-) > > > > > > Cheers > > > Raphael. > > > > > > > > > On 16.03.11 11:43, Anton Zagorskiy wrote: > > >> Hi Raphael, > > >> > > >> There are nothing more in the log. I've made a more longest log: > > >> http://pastebin.com/4xjU5EcM > > >> > > >> In conf I wrote: > > >> loglevel=3 > > >> log_sessions=yes > > >> log_events=yes > > >> unhandled_reply_loglevel=debug > > >> log_raw_messages=yes > > >> log_parsed_messages=yes > > >> > > >> > > >> > > >> > > >> > > >> WBR, Anton Zagorskiy > > >> VoIP Developer, Oyster Telecom > > >> Phone.: +7 812 601-0666 > > >> Fax: +7 812 601-0593 > > >> [email protected] > > >> www.oyster-telecom.ru > > >> > > >> > > >> > > >>> -----Original Message----- > > >>> From: [email protected] [mailto:sems- > > >>> [email protected]] On Behalf Of Raphael Coeffic > > >>> Sent: Wednesday, March 16, 2011 1:35 PM > > >>> To: [email protected] > > >>> Subject: Re: [Sems] early_announce > > >>> > > >>> On 16.03.11 11:10, Anton Zagorskiy wrote: > > >>>> Hi Alex, > > >>>> > > >>>> In SEMS conf I wrote: 'application = early_announce' > > >>>> In INVITE request I added 'P-App-Name: early_announce' > > >>>> > > >>>> Does it enough? > > >>>> > > >>> In fact, it is almost too much ;-) > > >>> > > >>> All you need is either: > > >>> > > >>> in sems.conf: application = early_announce > > >>> > > >>> Or: > > >>> > > >>> in sems.conf: $(apphdr) > > >>> and then, append the 'P-App-Name: early_announce' to your > messages > > sent > > >>> to SEMS. > > >>> > > >>> But still, that probably does not resolve your issue. From I > could > > see, > > >>> it seems that parts of the debug log are missing, for example, > I'd > > like > > >>> to see whether SEMS tries to send any SIP message anywhere. > > >>> > > >>> -Raphael. > > >>> > > >>>> > > >>>> WBR, Anton Zagorskiy > > >>>> VoIP Developer, Oyster Telecom > > >>>> Phone.: +7 812 601-0666 > > >>>> Fax: +7 812 601-0593 > > >>>> [email protected] > > >>>> www.oyster-telecom.ru > > >>>> > > >>>> > > >>>> > > >>>>> -----Original Message----- > > >>>>> From: [email protected] [mailto:sems- > > >>>>> [email protected]] On Behalf Of Alex Balashov > > >>>>> Sent: Wednesday, March 16, 2011 12:47 PM > > >>>>> To: [email protected] > > >>>>> Subject: Re: [Sems] early_announce > > >>>>> > > >>>>> Hi Anton, > > >>>>> > > >>>>> How have you ensured that SIP calls received by SEMS are routed > > to > > >>> the > > >>>>> early_announce plugin? Are you using app_mapping? If this has > > not > > >>>>> been explicitly dealt with, that could be your problem. > > >>>>> > > >>>>> -- Alex > > >>>>> > > >>>>> -- > > >>>>> Alex Balashov - Principal > > >>>>> Evariste Systems LLC > > >>>>> 260 Peachtree Street NW > > >>>>> Suite 2200 > > >>>>> Atlanta, GA 30303 > > >>>>> Tel: +1-678-954-0670 > > >>>>> Fax: +1-404-961-1892 > > >>>>> Web: http://www.evaristesys.com/ > > >>>>> _______________________________________________ > > >>>>> Sems mailing list > > >>>>> [email protected] > > >>>>> http://lists.iptel.org/mailman/listinfo/sems > > >>>> _______________________________________________ > > >>>> Sems mailing list > > >>>> [email protected] > > >>>> http://lists.iptel.org/mailman/listinfo/sems > > >>> _______________________________________________ > > >>> Sems mailing list > > >>> [email protected] > > >>> http://lists.iptel.org/mailman/listinfo/sems > > > > > > _______________________________________________ > > > Sems mailing list > > > [email protected] > > > http://lists.iptel.org/mailman/listinfo/sems > > > _______________________________________________ > Sems mailing list > [email protected] > http://lists.iptel.org/mailman/listinfo/sems _______________________________________________ Sems mailing list [email protected] http://lists.iptel.org/mailman/listinfo/sems
