[Spce-user] response to SIP OPTIONS 200 Alive instead of 200 OK

[Daniel Grotti]

Hi,
from RFC3261:

7.2 Responses

    SIP responses are distinguished from requests by having a Status-Line
    as their start-line.  A Status-Line consists of the protocol version
    followed by a numeric Status-Code and its associated textual phrase,
    with each element separated by a single SP character.

    No CR or LF is allowed except in the final CRLF sequence.

       Status-Line  =  SIP-Version SP Status-Code SP Reason-Phrase CRLF

    The Status-Code is a 3-digit integer result code that indicates the
    outcome of an attempt to understand and satisfy a request.  The
    Reason-Phrase is intended to give a short textual description of the
    Status-Code. *The Status-Code is intended for use by automata,**
**   whereas the Reason-Phrase is intended for the human user.* *A client**
**   is not required to examine or display the Reason-Phrase.
*

    *While this specification suggests specific wording for the reason 
phrase, implementations MAY choose other text*...

*
*


the reason phrase has no routing meaning and it is not even required to 
be parsed.
The Status-code is the important  part.

So, a SIP response 200 Alive is fully compliant.

-- 
Daniel Grotti
Head of Customer Support
Sipwise GmbH, Campus 21/Europaring F15
AT-2345 Brunn am Gebirge

Office: +43(0)130120332
Email: dgrotti at sipwise.com
Website: https://www.sipwise.com

On 11/12/18 9:55 AM, qabane me wrote:
> Hi
>
> On 6.4.1 the response to SIP OPTIONS is 200 Alive. One of my peers is 
> complaining about this as their equipment expects a 200 OK (which I 
> think is the standard)l.
>
> On previous versions we send a 200 OK.
>
> Is there a specific reason why it was changed to 200 Alive, and more 
> importantly is 200 Alive SIP compliant? If it is I can tell our peer 
> this and they should deal with it on their side.
>
> If they cannot deal with it, can it be changed?
>
> Cheers
>
>
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20181112/7f7fc07f/attachment-0001.html>