[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 14:43 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).
====================================================================== 

---------------------------------------------------------------------- 
 ibc - 11-19-07 14:43  
---------------------------------------------------------------------- 
oej, Asterisk behaviour for OPTIONS is not at described in section 11.2 of
RFC 3261 as you suggest.

In that section it said that an in-dialog OPTIONS should be considered as
an initial request OPTIONS, so just reply with 200 OK if the
extension/username called exists and accepts calls.

Ok, this explaines why if I send an in-dialog OPTIONS to asterisk at IP I
receive a 404 (in case "asterisk" is not a valid extension for me).

But now note the new attached file
"debug-OPTIONS-wrong-tags-indialog-481-pedantic-yes.txt" in which Twinkle
(200) calls to Asterisk (51):

- During the call I send an in-dialog OPTION with a Ruby code I've done
(respecting RURI, Call-ID and From/To tags of the extablished dialog) and
Asterisk replies me 200 OK.

- But later during the same call I change the Call-ID (or From/To tags) in
my Ruby program and send an in-dialog OPTIONS. In this case Asterisk
replies me with 481 (in pedantic=yes) or 404 (in pedantic=no).

Why?? it makes no sense. If Asterisk's behaviour is as in 11.2 section it
should reply 200 OK because the extension of the RURI in the in-dialog
OPTIONS exists, regardless of the values of Call-ID and From/To tags.

So we can expect a totally 11.2 compliant behaviour (alway reply 200 OK)
or a "maybe not so RFC specs compliant" behavior and allowing in-dialog
OPTIONS to monitorize dialog status by repling 200 OK (if that dialog
exists) or 481 (if not). The last behaviour is used by Cisco gateways at
least (and I think by Nortel too). 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
11-19-07 14:43  ibc            Note Added: 0074002                          
======================================================================