[asterisk-bugs] [Asterisk 0011264]: Asterisk doesn't reply well to in-dialog OPTIONS in pedantic mode
noreply at bugs.digium.com
noreply at bugs.digium.com
Mon Nov 19 01:23:19 CST 2007
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=11264
======================================================================
Reported By: ibc
Assigned To: oej
======================================================================
Project: Asterisk
Issue ID: 11264
Category: Channels/chan_sip/Interoperability
Reproducibility: always
Severity: minor
Priority: normal
Status: assigned
Asterisk Version: 1.4.13
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Disclaimer on File?: N/A
Request Review:
======================================================================
Date Submitted: 11-15-2007 14:04 CST
Last Modified: 11-19-2007 01:23 CST
======================================================================
Summary: Asterisk doesn't reply well to in-dialog OPTIONS in
pedantic mode
Description:
A way to monitorize a SIP dialog is by sending in-dialog OPTIONS so the
UAC/UAS replies with 200 OK if that dialog exists or 404 if not.
Asterisk with pedantic=no replies a "404 Not Found" correctly but in
pedantic=yes it replies with a "481 Call/Transaction Does Not Exist".
I'm not 100% sure (I'll try to confirm it) but I think it should reply
with a 404 instead of 481 in this case (OPTIONS in-dialog).
======================================================================
----------------------------------------------------------------------
oej - 11-19-07 01:23
----------------------------------------------------------------------
Thanks. However, you only have the debug output here, I need it all -
verbose and the actual SIP messages too. Set verbose and debug to 5, turn
sip debug on and capture again. Sorry for the extra work.
I think the issue here is not the 404, because you propably don't have an
extension called "asterisk", it's that it causes the call to hang up on a
non-fatal in-dialog transaction. We are always requested to answer to
OPTIONs as if it was an INVITE, regardless if it's in-dialog or not.
I need to see more output though, before I start working on a patch and
try to fix this. Thanks for your patience.
Issue History
Date Modified Username Field Change
======================================================================
11-19-07 01:23 oej Note Added: 0073891
======================================================================
More information about the asterisk-bugs
mailing list