[asterisk-bugs] [Asterisk 0011264]: Asterisk doesn't reply well to in-dialog OPTIONS in pedantic mode

[noreply at bugs.digium.com]

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 17:20 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).
====================================================================== 

---------------------------------------------------------------------- 
 jesusr - 11-19-07 17:20  
---------------------------------------------------------------------- 
Dear Olle,

I agree with Iñaki that Asterisk behavior regarding OPTIONS in-dialog is
wrong. 

Following your arguments, point 11.2 of the rfc3261:

"The response code chosen MUST be the same that would have been chosen had
the request been an INVITE".

Keeping in mind that you are sending an OPTIONS with a To tag, you must
reply with a 200OK if the dialog exists or with a "481 Call/Transaction
Does Not Exist" as you would do for a (re-)INVITE with a To tag that does
(not) exist in the UAS.

Also, 12.2.2 UAS Behavior (requests within a dialog) states:

If the UAS wishes to reject the request because it does not wish to 
recreate the dialog, it MUST respond to the request with a 481 
(Call/Transaction Does Not Exist) status code and pass that to the 
server transaction.

OPTIONS in-dialog is becoming a very common keepalive mechanism used by
VoIP providers and vendors to check that calls (dialogs) are alive both in
users and gateways/softswitches and avoid, specially, billing problems and
would be great if Asterisk has the right behavior.

Regards. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
11-19-07 17:20  jesusr         Note Added: 0074014                          
======================================================================