<div dir="ltr"><pre style="margin-top:0px;margin-bottom:0px"><span style="color:rgb(34,34,34);font-size:small;font-family:arial,sans-serif">Hi Alex,</span></pre><pre style="margin-top:0px;margin-bottom:0px"><span style="color:rgb(34,34,34);font-size:small;font-family:arial,sans-serif">RFC 3261, section </span><span style="font-family:arial,sans-serif">"6. Choosing the best response" states:</span></pre><pre style="margin-top:0px;margin-bottom:0px"><span style="color:rgb(34,34,34);font-size:small;font-family:arial,sans-serif"><br></span></pre>"A proxy which receives a 503 (Service Unavailable) response<br>SHOULD NOT forward it upstream unless it can determine that any<br>subsequent requests it might proxy will also generate a 503.<br>In other words, forwarding a 503 means that the proxy knows it<br>cannot service any requests, not just the one for the Request-<br>URI in the request which generated the 503. If the only<br>response that was received is a 503, the proxy SHOULD generate<br>a 500 response and forward that upstream."<div><br></div><div>So Kamailio (the TM module) is doing right there. In recent versions of kamailio the TM module has a remap_503_500 parameter to control this behavior (<a href="http://www.kamailio.org/docs/modules/devel/modules/tm.html#remap_503_500" target="_blank">http://www.kamailio.org/docs/modules/devel/modules/tm.html#remap_503_500</a>), but not in the 1.5.x branch (<a href="http://kamailio.org/docs/modules/1.5.x/tm.html" target="_blank">http://kamailio.org/docs/modules/1.5.x/tm.html</a>). </div><div><br></div><div>Hope this helps...to convince your customer to upgrade ;-)</div><div><br></div><div>Cheers, </div><div><br></div><div>Federico</div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Apr 14, 2016 at 4:14 AM, Alex Balashov <span dir="ltr"><<a href="mailto:abalashov@evaristesys.com" target="_blank">abalashov@evaristesys.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
I've got an installation that is still running Kamailio 1.5.x. Yes, I know: "They're running WHAT?" As far as I'm concerned, it was EOL'd in early 2010. Nevertheless, that doesn't stop the customer from running it. They're probably the most change-resistant customer in the history of IP telecom, and, knowing this industry, that's a high bar. There's not much I can do about it.<br>
<br>
Anyway, I have a bit of a mystery:<br>
<br>
GW Proxy PBX<br>
==================================================<br>
<br>
------- INVITE ------><br>
<br>
<---- 100 Trying ----<br>
<br>
-------- INVITE --------><br>
<br>
<------ 100 Trying ------<br>
<br>
<- 503 Service Unavailable<br>
<br>
---------- ACK ---------><br>
<br>
<- 500 Service Una...<br>
<br>
-------- ACK --------><br>
<br>
<br>
There is no basis in the configuration for the translation of the "503 Service Unavailable" reply to "500 Service Unavailable", so I'm thinking it has to be rooted in some default module behaviour.<br>
<br>
Any insight would be appreciated!<br>
<br>
-- Alex<br>
<br>
-- <br>
Alex Balashov | Principal | Evariste Systems LLC<br>
1447 Peachtree Street NE, Suite 700<br>
Atlanta, GA 30309<br>
United States<br>
<br>
Tel: <a href="tel:%2B1-800-250-5920" value="+18002505920" target="_blank">+1-800-250-5920</a> (toll-free) / <a href="tel:%2B1-678-954-0671" value="+16789540671" target="_blank">+1-678-954-0671</a> (direct)<br>
Web: <a href="http://www.evaristesys.com/" rel="noreferrer" target="_blank">http://www.evaristesys.com/</a>, <a href="http://www.csrpswitch.com/" rel="noreferrer" target="_blank">http://www.csrpswitch.com/</a><br>
<br>
_______________________________________________<br>
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list<br>
<a href="mailto:sr-users@lists.sip-router.org" target="_blank">sr-users@lists.sip-router.org</a><br>
<a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users" rel="noreferrer" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a><br>
</blockquote></div><br></div></div>