SIP/2.0 415 Unsupported Media Type after upgrade to 20.6.0

Asterisk Asterisk Support
2

I believe the behavior comes from:

commit e12244153a245d19d7ebd32cb17208104c64f443
Author: Torrey Searle <torrey@voxbone.com>
Date:   Thu Mar 19 10:34:42 2020 +0100

    res_pjsip_session: implement processing of Content-Disposition
    
    RFC5621 requires any content type with a Content-Disposition
    with handling=required to be rejected with a 415 response
    
    ASTERISK-28782 #close
    
    Change-Id: Iad969df75936730254b95c1a8bc3b48497070bb4

Or issue:

https://issues-archive.asterisk.org/ASTERISK-28782

Previous versions ignored it, while that change added support for actually respecting it. In the given multipart there is:

Content-Disposition: signal; handling=required
Content-Type: application/isup; version=ansi88; base=ansi88

Which since Asterisk doesn’t support application/isup would not be handled, and cause the 415 to be sent. There is no option to disable obeying this standard.

There is no immediate “fix” for this aside from having that content removed from the message. Otherwise reverting the change would do it, or adding an option to disable obeying the standard.

2 Likes