<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<tt>In case you want to change that, you can change Alive to OK in
the
/etc/ngcp-config/templates/etc/kamailio/proxy/kamailio.cfg.customtt.tt2:<br>
<br>
sl_send_reply("200", "<b>Alive</b>");<br>
xlog("L_NOTICE", "Sending reply S=200 <b>Alive</b> fs='$Ri:$Rp'
du='$si:$sp' - [% logreq -%]\n");<br>
<br>
<br>
Cheers,<br>
<br>
<br>
</tt>
<pre class="moz-signature" cols="72">--
Daniel Grotti
Head of Customer Support
Sipwise GmbH, Campus 21/Europaring F15
AT-2345 Brunn am Gebirge
Office: +43(0)130120332
Email: <a class="moz-txt-link-abbreviated" href="mailto:dgrotti@sipwise.com">dgrotti@sipwise.com</a>
Website: <a class="moz-txt-link-freetext" href="https://www.sipwise.com">https://www.sipwise.com</a>
</pre>
<div class="moz-cite-prefix">On 11/12/18 10:05 AM, Daniel Grotti
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:5812c086-7af5-7130-16c4-d486009fbb15@sipwise.com">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<tt>Hi,<br>
from RFC3261:<br>
<br>
7.2 Responses<br>
<br>
SIP responses are distinguished from requests by having a
Status-Line<br>
as their start-line. A Status-Line consists of the protocol
version<br>
followed by a numeric Status-Code and its associated textual
phrase,<br>
with each element separated by a single SP character.<br>
<br>
No CR or LF is allowed except in the final CRLF sequence.<br>
<br>
Status-Line = SIP-Version SP Status-Code SP
Reason-Phrase CRLF<br>
<br>
The Status-Code is a 3-digit integer result code that
indicates the<br>
outcome of an attempt to understand and satisfy a request.
The<br>
Reason-Phrase is intended to give a short textual description
of the<br>
Status-Code. <b> The Status-Code is intended for use by
automata,</b><b><br>
</b><b> whereas the Reason-Phrase is intended for the human
user.</b> <b>A client</b><b><br>
</b><b> is not required to examine or display the
Reason-Phrase.<br>
</b></tt><br>
<pre style="color: rgb(0, 0, 0); font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration-style: initial; text-decoration-color: initial; overflow-wrap: break-word; white-space: pre-wrap;"> <b>While this specification suggests specific wording for the reason
phrase, implementations MAY choose other text</b>...</pre>
<tt><b><br>
</b><br>
<br>
<br>
the reason phrase has no routing meaning and it is not even
required to be parsed.<br>
The Status-code is the important part.<br>
<br>
So, a SIP response 200 Alive is fully compliant.<br>
<br>
</tt>
<pre class="moz-signature" cols="72">--
Daniel Grotti
Head of Customer Support
Sipwise GmbH, Campus 21/Europaring F15
AT-2345 Brunn am Gebirge
Office: +43(0)130120332
Email: <a class="moz-txt-link-abbreviated" href="mailto:dgrotti@sipwise.com" moz-do-not-send="true">dgrotti@sipwise.com</a>
Website: <a class="moz-txt-link-freetext" href="https://www.sipwise.com" moz-do-not-send="true">https://www.sipwise.com</a>
</pre>
<div class="moz-cite-prefix">On 11/12/18 9:55 AM, qabane me wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CADDwb0p5siZH-DyCwHpo9zvDhs=y9Mkx7dx5yQu1bYmQeBVn-g@mail.gmail.com">
<meta http-equiv="content-type" content="text/html;
charset=UTF-8">
<div dir="ltr">
<div>Hi</div>
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>On previous versions we send a 200 OK.</div>
<div><br>
</div>
<div>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. <br>
</div>
<div><br>
</div>
<div>If they cannot deal with it, can it be changed?</div>
<div><br>
</div>
<div>Cheers</div>
<div><br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Spce-user mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Spce-user@lists.sipwise.com" moz-do-not-send="true">Spce-user@lists.sipwise.com</a>
<a class="moz-txt-link-freetext" href="https://lists.sipwise.com/listinfo/spce-user" moz-do-not-send="true">https://lists.sipwise.com/listinfo/spce-user</a>
</pre>
</blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Spce-user mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Spce-user@lists.sipwise.com">Spce-user@lists.sipwise.com</a>
<a class="moz-txt-link-freetext" href="https://lists.sipwise.com/listinfo/spce-user">https://lists.sipwise.com/listinfo/spce-user</a>
</pre>
</blockquote>
<br>
</body>
</html>