[Kamailio-Devel] DialogState Information

[klaus.feichtinger at gmx.net]

Hello Klaus,

I've updated the trunk with your fixed version. Currently kamailio doesn't crash and is running stable. 

But I have a further question regarding dialog state information:
has anything changed in handling the dialog state feature of kamailio in general (configuration)? I've once again compared the newest version to another one from autumn 2008 - the old one always sends NOTIFY messages when the dialog of the watched UA changes (as expected), but the new one (PRE2 and several builds before) sends only one initial notification directly after the subscription. In the README files of the corresponding modules I haven't found any major change.....

Can you give me a hint what might be wrong in my environment?

regards,

Klaus F.

-------- Original-Nachricht --------
> Datum: Wed, 25 Feb 2009 18:04:58 +0100
> Von: Klaus Darilion <klaus.mailinglists at pernau.at>
> An: Klaus Feichtinger <klaus.feichtinger at gmx.net>
> CC: Daniel-Constantin Mierla <miconda at gmail.com>, devel at lists.kamailio.org
> Betreff: Re: [Kamailio-Devel] DialogState Information

> Hi Klaus!
> 
> I have just fixed a bug in SVN trunk. Please try again.
> 
> regards
> klaus
> 
> Klaus Feichtinger schrieb:
> > Hello,
> > 
> > for being sure to have the newest version I've made an update with SVN a
> few minutes before ;-)
> > 
> > Below you can find the backtrace of the core. And at the bottom the
> corresponding excerpt of the syslog.
> > 
> > regards,
> > 
> > Klaus F.
> > 
> > [...]
> > Reading symbols from /usr/lib/i686/cmov/libcrypto.so.0.9.8...done.
> > Loaded symbols for /usr/lib/i686/cmov/libcrypto.so.0.9.8
> > Reading symbols from /lib/tls/i686/cmov/libnss_files.so.2...done.
> > Loaded symbols for /lib/tls/i686/cmov/libnss_files.so.2
> > Reading symbols from /lib/tls/i686/cmov/libnss_dns.so.2...done.
> > Loaded symbols for /lib/tls/i686/cmov/libnss_dns.so.2
> > Core was generated by `/usr/local/sbin/kamailio -P
> /var/run/kamailio.pid'.
> > Program terminated with signal 11, Segmentation fault.
> > #0  0x080e14cf in parse_uri (buf=0x0, len=929247545, uri=0xbfe1e910) at
> parser/parse_uri.c:334
> > 334             scheme=buf[0]+(buf[1]<<8)+(buf[2]<<16)+(buf[3]<<24);
> > (gdb) bt
> > #0  0x080e14cf in parse_uri (buf=0x0, len=929247545, uri=0xbfe1e910) at
> parser/parse_uri.c:334
> > #1  0xb795843d in dialog_publish (state=0xb795a61a "early",
> entity=0xb583e7f0, peer=0xb583e7e8, callid=0xb583e7f8, initiator=0, lifetime=40,
> localtag=0xbfe1ea80, remotetag=0xb583e800) at dialog_publish.c:264
> > #2  0xb7959d62 in __dialog_sendpublish (dlg=0xb583fca0, type=128,
> _params=0xb7b16b7c) at pua_dialoginfo.c:233
> > #3  0xb7af2278 in run_dlg_callbacks (type=128, dlg=0xb583fca0,
> msg=0x818d630, dir=2, dlg_data=0x0) at dlg_cb.c:252
> > #4  0xb7afa8fe in dlg_onreply (t=0xb583d8e0, type=128, param=0xb7bcf7a8)
> at dlg_handlers.c:281
> > #5  0xb7ba1942 in run_trans_callbacks (type=128, trans=0xb583d8e0,
> req=0xb583ffb8, rpl=0x818d630, code=180) at t_hooks.c:240
> > #6  0xb7bbd3aa in relay_reply (t=0xb583d8e0, p_msg=0x818d630,
> branch=<value optimized out>, msg_status=180, cancel_bitmap=0xbfe1edd0) at
> t_reply.c:1219
> > #7  0xb7bbde08 in reply_received (p_msg=0x818d630) at t_reply.c:1463
> > #8  0x0806592b in forward_reply (msg=0x818d630) at forward.c:521
> > #9  0x0808c707 in receive_msg (
> >     buf=0x8158040 "SIP/2.0 180 Ringing\r\nDate: Wed, 25 Feb 2009
> 16:11:12 GMT\r\nAllow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE,
> REFER, SUBSCRIBE, NOTIFY\r\nFrom: test
> <sip:3002 at 10.16.48.203>;tag=359034363-3958"..., len=652, rcv_info=0xbfe1ef04) at receive.c:212
> > #10 0x080c3ce3 in udp_rcv_loop () at udp_server.c:449
> > #11 0x0806e354 in main (argc=3, argv=0xbfe1f0e4) at main.c:774
> > (gdb)
> > 
> > 
> > =============================
> > SYSLOG
> > ======
> > Feb 25 17:03:09 vmware /usr/local/sbin/kamailio[7829]:
> ERROR:core:parse_uri: uri too short: <Ãý<83>µ^U> (-1214936144)
> > Feb 25 17:03:09 vmware /usr/local/sbin/kamailio[7829]:
> ERROR:pua_dialoginfo:dialog_publish: failed to parse the entity URI
> > Feb 25 17:03:09 vmware /usr/local/sbin/kamailio[7846]:
> CRITICAL:core:receive_fd: EOF on 11
> > Feb 25 17:03:09 vmware /usr/local/sbin/kamailio[7824]:
> INFO:core:handle_sigs: child process 7829 exited by a signal 11
> > Feb 25 17:03:09 vmware /usr/local/sbin/kamailio[7824]:
> INFO:core:handle_sigs: core was generated
> > Feb 25 17:03:09 vmware /usr/local/sbin/kamailio[7824]:
> INFO:core:handle_sigs: terminating due to SIGCHLD
> > Feb 25 17:03:09 vmware /usr/local/sbin/kamailio[7846]:
> INFO:core:sig_usr: signal 15 received
> > Feb 25 17:03:09 vmware /usr/local/sbin/kamailio[7831]:
> INFO:core:sig_usr: signal 15 received
> > Feb 25 17:03:09 vmware /usr/local/sbin/kamailio[7828]:
> INFO:core:sig_usr: signal 15 received
> > Feb 25 17:03:09 vmware /usr/local/sbin/kamailio[7827]:
> INFO:core:sig_usr: signal 15 received
> > Feb 25 17:03:09 vmware /usr/local/sbin/kamailio[7826]:
> INFO:core:sig_usr: signal 15 received
> > Feb 25 17:03:09 vmware /usr/local/sbin/kamailio[7843]:
> INFO:core:sig_usr: signal 15 received
> > Feb 25 17:03:09 vmware /usr/local/sbin/kamailio[7842]:
> INFO:core:sig_usr: signal 15 received
> > Feb 25 17:03:09 vmware /usr/local/sbin/kamailio[7839]:
> INFO:core:sig_usr: signal 15 received
> > Feb 25 17:03:09 vmware /usr/local/sbin/kamailio[7836]:
> INFO:core:sig_usr: signal 15 received
> > Feb 25 17:03:09 vmware /usr/local/sbin/kamailio[7834]:
> INFO:core:sig_usr: signal 15 received
> > 
> > 
> > -------- Original-Nachricht --------
> >> Datum: Wed, 25 Feb 2009 17:36:40 +0200
> >> Von: Daniel-Constantin Mierla <miconda at gmail.com>
> >> An: klaus.feichtinger at gmx.net
> >> CC: devel at lists.kamailio.org
> >> Betreff: Re: [Kamailio-Devel] DialogState Information
> > 
> >> Hello,
> >>
> >> might be related to the updates I did few weeks ago. Can you send also 
> >> the back trace? I see there was a core...
> >>
> >> Thanks,
> >> Daniel
> >>
> >>
> >> On 02/25/2009 05:26 PM, klaus.feichtinger at gmx.net wrote:
> >>> Hi,
> >>>
> >>> Since a few weeks I have problems with the current version of DIALOG
> >> state information. The current version (= 1.5.0 PRE2) does not support
> dialog
> >> state information as in older builds. No NOTIFY messages are sent to
> the
> >> watchers and in the log file lot's of entries regarding parsing errors
> can be
> >> found. I think this has an influence to the missing notifications.
> >>> Nevertheless this malfunction is as bad, that kamailio crashes after a
> >> period of time with critical core error (see excerpt below). This
> problem
> >> does not occur, if the corresponding modules are not loaded.
> >>> For verification of my configuration I compiled an "old" developer
> >> version from end of september 2008 and with this version it works fine.
> >> Notifications are sent to the watchers and no entries regarding parsing
> errors etc.
> >> can be found in the log file.
> >>> Does anybody know this problem or can anybody give me any hint?
> >>>
> >>> Thanks and regards,
> >>>
> >>> Klaus F.
> >>>
> >>>
> >>> excerpt of the LOG file:
> >>> ========================
> >>>
> >>> Feb 25 13:54:24 vmware /usr/local/sbin/kamailio[28440]:
> >> ERROR:core:parse_uri: uri too short: <÷^?µ^U> (-1215218768)
> >>> Feb 25 13:54:24 vmware /usr/local/sbin/kamailio[28440]:
> >> ERROR:pua_dialoginfo:dialog_publish: failed to parse the entity URI
> >>> Feb 25 13:54:24 vmware /usr/local/sbin/kamailio[28438]:
> >> ERROR:core:parse_uri: uri too short: <÷^?µ^U> (-1215218768)
> >>> Feb 25 13:54:24 vmware /usr/local/sbin/kamailio[28438]:
> >> ERROR:pua_dialoginfo:dialog_publish: failed to parse the entity URI
> >>> Feb 25 13:54:24 vmware /usr/local/sbin/kamailio[28437]:
> >> ERROR:core:parse_uri: uri too short: <÷^?µ^U> (-1215218768)
> >>> Feb 25 13:54:24 vmware /usr/local/sbin/kamailio[28437]:
> >> ERROR:pua_dialoginfo:dialog_publish: failed to parse the entity URI
> >>> Feb 25 13:54:24 vmware /usr/local/sbin/kamailio[28439]:
> >> ERROR:core:parse_uri: uri too short: <÷^?µ^U> (-1215218768)
> >>> Feb 25 13:54:24 vmware /usr/local/sbin/kamailio[28439]:
> >> ERROR:pua_dialoginfo:dialog_publish: failed to parse the entity URI
> >>> Feb 25 13:54:27 vmware /usr/local/sbin/kamailio[28457]:
> >> CRITICAL:core:receive_fd: EOF on 8
> >>> Feb 25 13:54:27 vmware /usr/local/sbin/kamailio[28457]:
> >> CRITICAL:core:receive_fd: EOF on 10
> >>> Feb 25 13:54:27 vmware /usr/local/sbin/kamailio[28457]:
> >> CRITICAL:core:receive_fd: EOF on 9
> >>> Feb 25 13:54:27 vmware /usr/local/sbin/kamailio[28457]:
> >> CRITICAL:core:receive_fd: EOF on 11
> >>> Feb 25 13:54:27 vmware /usr/local/sbin/kamailio[28435]:
> >> INFO:core:handle_sigs: child process 28437 exited by a signal 11
> >>> Feb 25 13:54:27 vmware /usr/local/sbin/kamailio[28435]:
> >> INFO:core:handle_sigs: core was generated
> >>> Feb 25 13:54:27 vmware /usr/local/sbin/kamailio[28435]:
> >> INFO:core:handle_sigs: child process 28438 exited by a signal 11
> >>> Feb 25 13:54:27 vmware /usr/local/sbin/kamailio[28435]:
> >> INFO:core:handle_sigs: core was generated
> >>> Feb 25 13:54:27 vmware /usr/local/sbin/kamailio[28435]:
> >> INFO:core:handle_sigs: child process 28439 exited by a signal 11
> >>> Feb 25 13:54:27 vmware /usr/local/sbin/kamailio[28435]:
> >> INFO:core:handle_sigs: core was generated
> >>> Feb 25 13:54:27 vmware /usr/local/sbin/kamailio[28435]:
> >> INFO:core:handle_sigs: child process 28440 exited by a signal 11
> >>> Feb 25 13:54:27 vmware /usr/local/sbin/kamailio[28435]:
> >> INFO:core:handle_sigs: core was generated
> >>> Feb 25 13:54:27 vmware /usr/local/sbin/kamailio[28435]:
> >> INFO:core:handle_sigs: terminating due to SIGCHLD
> >>> Feb 25 13:54:27 vmware /usr/local/sbin/kamailio[28457]:
> >> INFO:core:sig_usr: signal 15 received
> >>> Feb 25 13:54:27 vmware /usr/local/sbin/kamailio[28442]:
> >> INFO:core:sig_usr: signal 15 received
> >>> Feb 25 13:54:27 vmware /usr/local/sbin/kamailio[28451]:
> >> INFO:core:sig_usr: signal 15 received
> >>> Feb 25 13:54:27 vmware /usr/local/sbin/kamailio[28450]:
> >> INFO:core:sig_usr: signal 15 received
> >>> Feb 25 13:54:27 vmware /usr/local/sbin/kamailio[28454]:
> >> INFO:core:sig_usr: signal 15 received
> >>> Feb 25 13:54:27 vmware /usr/local/sbin/kamailio[28447]:
> >> INFO:core:sig_usr: signal 15 received
> >>> Feb 25 13:54:27 vmware /usr/local/sbin/kamailio[28445]:
> >> INFO:core:sig_usr: signal 15 received
> >>>
> >>>   
> >> -- 
> >> Daniel-Constantin Mierla
> >> http://www.asipto.com
> > 

-- 
Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger01