[asterisk-bugs] [Asterisk 0012738]: Asterisk should reply "200 OK" to an in-dialog INFO with empty body

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12738 
====================================================================== 
Reported By:                ibc
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   12738
Category:                   Channels/chan_sip/Interoperability
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
Asterisk Version:           1.4.18 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             05-28-2008 09:00 CDT
Last Modified:              05-28-2008 09:46 CDT
====================================================================== 
Summary:                    Asterisk should reply "200 OK" to an in-dialog INFO
with empty body
Description: 
I've had problems using a carrier that uses Nortel CS2K softswitch because
the Nortel sends an in-dialog INFO with empty body to monitorize long
duration calls. AFAIK this method has been commonly used until now that we
have session timers (RFC 3311).
 
If Asterisk supports RFC 2976 (SIP INFO), it must return 200 instead of
4XX when INFO contains no body.
 
RFC 2976 section 2.2:

----------- 
 "A 200 OK response MUST be sent by a UAS for an INFO request with no
 message body if the INFO request was successfully received for an
 existing call."
 
 "A 481 Call Leg/Transaction Does Not Exist message MUST be sent by a
 UAS if the INFO request does not match any existing call leg."
------------

Asterisk replies with a 4XX (sorry, not sure of exact code now) so Nortel
hangs the call.
====================================================================== 

---------------------------------------------------------------------- 
 file - 05-28-08 09:46  
---------------------------------------------------------------------- 
There is already code present to do as you say, it was added in revision
88328 as a result of issue 5747 so the underlying issue is probably the one
you mentioned. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
05-28-08 09:46  file           Note Added: 0087426                          
======================================================================