[asterisk-bugs] [JIRA] (ASTERISK-27477) Chan_pjsip does not support unauthenticated OPTIONS ping

[Sean Bright (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-27477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=242135#comment-242135 ] 

Sean Bright commented on ASTERISK-27477:
----------------------------------------

I am not sure that this is something that we actually want to "fix." If {{chan_sip}} is replying with a 200 OK when authentication is required, that is a bug in {{chan_sip}}. Per [RFC 3261|https://tools.ietf.org/html/rfc3261] [Section 11.2 Processing of OPTIONS Request|https://tools.ietf.org/html/rfc3261#section-11.2]:

{noformat}
The response to an OPTIONS is constructed using the standard rules
for a SIP response as discussed in Section 8.2.6.  The response code
chosen MUST be the same that would have been chosen had the request
been an INVITE.  That is, a 200 (OK) would be returned if the UAS is
ready to accept a call, a 486 (Busy Here) would be returned if the
UAS is busy, etc.  This allows an OPTIONS request to be used to
determine the basic state of a UAS, which can be an indication of
whether the UAS will accept an INVITE request.
{noformat}

I'm all for feature parity with {{chan_sip}}, but I don't think we should be introducing a bug in {{chan_pjsip}} to accomplish that.

> Chan_pjsip does not support unauthenticated OPTIONS ping
> --------------------------------------------------------
>
>                 Key: ASTERISK-27477
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27477
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_pjsip
>    Affects Versions: 13.18.3, GIT, 15.1.3
>         Environment: Fedora 23
> CentOS 7
>            Reporter: Ross Beer
>
> The chan_pjsip does not support replying to unauthenticated OPTIONS pings.
> If an older version of Asterisk sends OPTIONS pings to the chan_pjsip channel diver, an auth request is sent instead of a 200 reply.
> Other endpoints that do not support authentication on OPTION pings also do not receive the expected response.



--
This message was sent by Atlassian JIRA
(v6.2#6252)