Hi,
o Andreas Granig [07/08/09 14:03]:
Hi,
While doing some more tests with 1.1.0, sipctrl and auth_b2b, the
following log entries popped up in some cases (only for BYE handling, as
far as I can tell, and only for some calls):
ERROR: [b7617bb0] handleSipMsg (AmSipDispatcher.cpp:53): unhandled
reply: [code:100 ...]
and
ERROR: [b7617bb0] handleSipMsg (AmSipDispatcher.cpp:50): unhandled
positive reply: [code:200 ...]
I can't tell so far under which circumstances these cases occur, and the
SIP routing looks fine even when this errors are reported. Looks like
these logs can be deactivated in the config file, so I was wondering
what this is all about, and if it does any harm?
this has been asked and answered a few times (e.g. look for a thread
from Feb 09 titled "AmSipDispatcher 'could not dispatch reply' error").
In short, the UA layer (AmSession) by default forgets the dialog/session
as soon as the BYE is sent, thus the transaction layer can not deliver
replies to the BYE. The question is what a proper handling of negative
reply to BYE would be - the only exception with this could be if a BYE
needs to be authenticated (401/407 reply), but i have never seen this in
reality. If you need it, you can code it in your application though
(don't call setStopped when sending BYE, catch replies to BYE cseq in
your onSipReply, and act on that properly, e.g. call setStopped only
when positive reply received or severly timeout...).
This has been added as faq entry. (http://www.iptel.org/sems/faq).
Stefan
Andreas
_______________________________________________
Sems mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/sems
--
Stefan Sayer
VoIP Services
[email protected]
www.iptego.com
IPTEGO GmbH
Wittenbergplatz 1
10789 Berlin
Germany
Amtsgericht Charlottenburg, HRB 101010
Geschaeftsfuehrer: Alexander Hoffmann
_______________________________________________
Sems mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/sems
