[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
Tue Jul 1 06:44:36 CDT 2008
The following issue has been RESOLVED.
======================================================================
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: resolved
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:
Resolution: fixed
Fixed in Version:
======================================================================
Date Submitted: 11-15-2007 14:04 CST
Last Modified: 07-01-2008 06:44 CDT
======================================================================
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).
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
related to 0012738 Asterisk should reply "200 OK"...
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
07-01-08 06:44 svnbot Status assigned => resolved
07-01-08 06:44 svnbot Resolution reopened => fixed
======================================================================
More information about the asterisk-bugs
mailing list