[asterisk-bugs] [Asterisk 0016186]: [patch] T.38 reinvite fails after receiving "415 Unsupported media type" when it could continue in audio mode

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16186 
====================================================================== 
Reported By:                atis
Assigned To:                file
====================================================================== 
Project:                    Asterisk
Issue ID:                   16186
Category:                   Channels/chan_sip/Interoperability
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     closed
Asterisk Version:           1.6.1.6 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             2009-11-05 07:54 CST
Last Modified:              2009-12-02 10:49 CST
====================================================================== 
Summary:                    [patch] T.38 reinvite fails after receiving "415
Unsupported media type" when it could continue in audio mode
Description: 
Our SIP provider is responding with "415 Unsupported media type" if it
can't switch to T.38 for inbound fax.

After receiving that, chan_sip terminates call, and app_fax terminates
with "WARNING[29097] app_fax.c: Transmission error".

According to RFC3261 section 8.1.3.5:

The UAC SHOULD retry sending the request, this time only using content
with types listed in the Accept header field in the response, with
encodings listed in the Accept-Encoding header field in the response, and
with languages listed in the Accept-Language in the response.

I tried handling the 415 response exactly the same way as 488 response is
being handled (patch attached), and our provider accepts that and allows
call to be continued in audio mode.


====================================================================== 

---------------------------------------------------------------------- 
 (0114527) svnbot (reporter) - 2009-12-02 10:49
 https://issues.asterisk.org/view.php?id=16186#c114527 
---------------------------------------------------------------------- 
Repository: asterisk
Revision: 232346

_U  branches/1.6.0/
U   branches/1.6.0/channels/chan_sip.c

------------------------------------------------------------------------
r232346 | file | 2009-12-02 10:49:30 -0600 (Wed, 02 Dec 2009) | 14 lines

Merged revisions 232345 via svnmerge from 
https://origsvn.digium.com/svn/asterisk/trunk

........
  r232345 | file | 2009-12-02 12:40:14 -0400 (Wed, 02 Dec 2009) | 7 lines
  
  Add support for handling the 415 Unsupported media type response like we
do for a 488 Not acceptable here response.
  
  (closes issue https://issues.asterisk.org/view.php?id=16186)
  Reported by: atis
  Patches:
        sip_t38_response_415.patch uploaded by atis (license 242)
........

------------------------------------------------------------------------

http://svn.digium.com/view/asterisk?view=rev&revision=232346 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-12-02 10:49 svnbot         Checkin                                      
2009-12-02 10:49 svnbot         Note Added: 0114527                          
======================================================================