<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<tt>Hi Richard,</tt><tt><br>
</tt><tt><br>
</tt><tt>See rfc3261, chapter 6 </tt><tt>"Choosing the best
response", Page 111 :</tt><br>
<pre> A proxy which receives a 503 (Service Unavailable) response
SHOULD NOT forward it upstream unless it can determine that any
subsequent requests it might proxy will also generate a 503.
In other words, forwarding a 503 means that the proxy knows it
cannot service any requests, not just the one for the Request-
URI in the request which generated the 503. If the only
response that was received is a 503, the proxy SHOULD generate
a 500 response and forward that upstream.</pre>
<tt><br>
Still, this gives you access (at script level) to the 503 reply
(the change is done when sending it out), so you can investigate
the Reason hdr (if present).<br>
<br>
And yes, we got your other email.<br>
<br>
Regards,<br>
</tt>
<pre class="moz-signature" cols="72">Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a class="moz-txt-link-freetext" href="http://www.opensips-solutions.com">http://www.opensips-solutions.com</a></pre>
<div class="moz-cite-prefix">On 06.01.2017 17:14, Richard Robson
wrote:<br>
</div>
<blockquote
cite="mid:285ee3fa-b1f7-e6ae-8729-6c8e5300cc10@greenlightcrm.com"
type="cite">
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
<div class="moz-cite-prefix">hmm,<br>
<br>
both our suppliers translate an unavailable number
(Q.850;cause=41) as a 503. <br>
<br>
I Guess Im going to have to live with that.<br>
<br>
Did you see the other email this morning regarding opensips
crashing?<br>
I unhelpfully called the email opensipsp<br>
<br>
<br>
<br>
On 06/01/2017 14:41, Bogdan-Andrei Iancu wrote:<br>
</div>
<blockquote
cite="mid:6aa39dec-1b17-9eeb-40b8-e7b46f9fabe3@opensips.org"
type="cite">
<meta content="text/html; charset=utf-8"
http-equiv="Content-Type">
<tt>Hi Richard,<br>
<br>
Any incoming 503 reply is converted by OpenSIPS to a 500 reply
(as per RFC3261).<br>
<br>
Regards,<br>
</tt>
<pre class="moz-signature" cols="72">Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://www.opensips-solutions.com">http://www.opensips-solutions.com</a></pre>
<div class="moz-cite-prefix">On 06.01.2017 16:22, Richard Robson
wrote:<br>
</div>
<blockquote
cite="mid:736252ef-2076-e207-2119-0129158f163d@greenlightcrm.com"
type="cite">
<meta http-equiv="content-type" content="text/html;
charset=utf-8">
<p>Hi,</p>
<p><br>
</p>
<p>we are getting 503 messages back but when this is stored on
Homer as a 500. I'm not sure if its Opensips's sipcapture
module or Homer doing the translation</p>
<p><br>
</p>
<p>This is the packet captured in sngrep in the sip box</p>
<p>2017/01/06 14:13:59.210301 141.170.24.20:5060 ->
192.168.36.141:5060<br>
SIP/2.0 503 Service Unavailable<br>
Via: SIP/2.0/UDP
141.170.9.156:5060;branch=z9hG4bKd116.a30f9976.0<br>
From: <a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="sip:442035420637@192.168.36.68"><sip:442035420637@192.168.36.68></a>;tag=as55dfe54a<br>
To: <a moz-do-not-send="true" class="moz-txt-link-rfc2396E"
href="sip:+447910705624@141.170.24.20"><sip:+447910705624@141.170.24.20></a>;tag=gK00d54f0d<br>
Call-ID:
DLGCH_e0lXV2Z/MWR7SFYIMHFjZ3oSAwoyL2YwfkdXX2F5YGsPQVxcfXhma2FDU0BlcWpmf0ZV<br>
CSeq: 103 INVITE<br>
X-ISUPMtype:0c<br>
Reason: Q.850;cause=41;x-source=a<br>
Content-Length: 0<br>
<br>
</p>
<p>this is the same packet viewed in Homer</p>
<div class="tab-pane ng-scope active" ng-repeat="tab in tabs"
ng-class="{active: tab.active}"
uib-tab-content-transclude="tab">
<div id="sippath" ng-show="showSipMessage" class="sipmessage
ng-binding ng-scope">2017-01-06 14:13:59 +0000 :
141.170.24.20:5060 -> 192.168.36.141:5060</div>
<div id="sipmsg" ng-show="showSipMessage" class="sipmessage
ng-binding ng-scope" data-ng-bind-html="sipMessage">SIP/2.0
<font color="red"><b>500</b></font> Service Unavailable
Via: SIP/2.0/UDP 141.170.9.156:5060;branch=<font
color="green"><b>z9hG4bKd116.a30f9976.0</b></font> From:
<a moz-do-not-send="true" class="moz-txt-link-rfc2396E"
href="sip:442035420637@192.168.36.68"><sip:442035420637@192.168.36.68></a>;tag=<font
color="red"><b>as55dfe54a</b></font> To: <a
moz-do-not-send="true" class="moz-txt-link-rfc2396E"
href="sip:+447910705624@141.170.24.20"><sip:+447910705624@141.170.24.20></a>;tag=gK00d54f0d
Call-ID: <font color="blue"><b><a moz-do-not-send="true"
class="moz-txt-link-abbreviated"
href="mailto:492956a7483fc8345bfdaf6c17212008@192.168.36.68:5060">492956a7483fc8345bfdaf6c17212008@192.168.36.68:5060</a></b></font>
CSeq: 103 INVITE X-ISUPMtype:0c Reason:
Q.850;cause=41;x-source=a Content-Length: 0 </div>
</div>
<p>the sip code and the callid have been changed. the call id
is the same as the original call from the outbound asterisk
box<br>
</p>
<br>
Regards,<br>
<pre class="moz-signature" cols="72">--
Richard Robson
Greenlight Support
01382 843843
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:support@greenlightcrm.com">support@greenlightcrm.com</a></pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Users mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
</blockquote>
<br>
</blockquote>
<br>
<p><br>
</p>
<pre class="moz-signature" cols="72">--
Richard Robson
Greenlight Support
01382 843843
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:support@greenlightcrm.com">support@greenlightcrm.com</a></pre>
</blockquote>
<br>
</body>
</html>