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
