Ugh! I didn't make that easy, did I.. Yes, in failure route I t_reply (not relay) with a 503. They ignore the REPLY, there is no new branch. The UAC is ignoring my REPLY and the operator of that device is telling me that it's because the "To:" field doesn't match the RURI.<br>
<br><div class="gmail_quote">On Thu, Feb 12, 2009 at 1:26 AM, Bogdan-Andrei Iancu <span dir="ltr"><<a href="mailto:bogdan@voice-system.ro">bogdan@voice-system.ro</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi Brett,<div class="Ih2E3d"><br>
<br>
Brett Nemeroff wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
All,<br>
I'm having an issue with a customer's nextone sbc. They send a call out, I send it to my upstream. My upstream is broken (separate issue althogether). They send me 183..183.. 500. When I get the 500, I send a 503 to the originator of the request (my customer)<br>
</blockquote></div>
So, in failure_route you replace the received 500 with a 503 reply, right?<div class="Ih2E3d"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
.. and they ignore the request, so I retransmit it 4-5 times..<br>
</blockquote></div>
request? you said you already received the reply....I guess you retransmit the reply ? ..or maybe I'm missing something.<div class="Ih2E3d"><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I'm not doing anything weird. I'm using t_relay for the 503 in a failure route and I'm not rewriting anything other than the original request ruri. No funny business with tags.<br>
</blockquote></div>
you mean t_reply() ? I see no new branch in the flow you post.<br>
<br>
What the pseudo-trace shows is the UAC not accepting the 503 from your side, is this the issue?<br>
<br>
Regards,<br>
Bogdan<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="Ih2E3d">
<br>
During the transaction, other requests replies seem to work:<br>
<br></div>
60.793458 62.25.18.34 -> 75.82.100.5 SIP/SDP Request: INVITE <a href="mailto:sip%3A5216161079999@75.82.100.5" target="_blank">sip:5216161079999@75.82.100.5</a> <mailto:<a href="mailto:sip%253A5216161079999@75.82.100.5" target="_blank">sip%3A5216161079999@75.82.100.5</a>>;user=phone, with session description<div class="Ih2E3d">
<br>
<br>
60.796605 75.82.100.5 -> 62.25.18.34 SIP Status: 100 Giving a try<br>
<br></div>
60.796847 75.82.100.5 -> 202.152.59.3 SIP/SDP Request: INVITE <a href="mailto:sip%3A5216161079999@202.152.59.3" target="_blank">sip:5216161079999@202.152.59.3</a> <mailto:<a href="mailto:sip%253A5216161079999@202.152.59.3" target="_blank">sip%3A5216161079999@202.152.59.3</a>>, with session description<div class="Ih2E3d">
<br>
<br>
60.822516 202.152.59.3 -> 75.82.100.5 SIP Status: 100 Trying<br>
<br>
60.891115 202.152.59.3 -> 75.82.100.5 SIP/SDP Status: 183 Session Progress, with session description<br>
<br>
60.892837 75.82.100.5 -> 62.25.18.34 SIP/SDP Status: 183 Session Progress, with session description<br>
<br></div>
60.903312 62.25.18.34 -> 75.82.100.5 SIP Request: PRACK <a href="http://sip:5216161079999@202.152.59.3:5060" target="_blank">sip:5216161079999@202.152.59.3:5060</a> <<a href="http://sip:5216161079999@202.152.59.3:5060" target="_blank">http://sip:5216161079999@202.152.59.3:5060</a>><br>
<br>
60.905058 75.82.100.5 -> 202.152.59.3 SIP Request: PRACK <a href="http://sip:5216161079999@202.152.59.3:5060" target="_blank">sip:5216161079999@202.152.59.3:5060</a> <<a href="http://sip:5216161079999@202.152.59.3:5060" target="_blank">http://sip:5216161079999@202.152.59.3:5060</a>><div class="Ih2E3d">
<br>
<br>
60.919007 202.152.59.3 -> 75.82.100.5 SIP Status: 200 OK<br>
<br>
60.919730 75.82.100.5 -> 62.25.18.34 SIP Status: 200 OK<br>
<br>
66.324643 202.152.59.3 -> 75.82.100.5 SIP Status: 500 Internal Server Error<br>
<br></div>
66.325256 75.82.100.5 -> 202.152.59.3 SIP Request: ACK <a href="mailto:sip%3A5216161079999@202.152.59.3" target="_blank">sip:5216161079999@202.152.59.3</a> <mailto:<a href="mailto:sip%253A5216161079999@202.152.59.3" target="_blank">sip%3A5216161079999@202.152.59.3</a>><div class="Ih2E3d">
<br>
<br>
66.326427 75.82.100.5 -> 62.25.18.34 SIP Status: 503 Service Unavailable<br>
<br>
66.796377 75.82.100.5 -> 62.25.18.34 SIP Status: 503 Service Unavailable<br>
<br>
67.797229 75.82.100.5 -> 62.25.18.34 SIP Status: 503 Service Unavailable<br>
<br>
69.798014 75.82.100.5 -> 62.25.18.34 SIP Status: 503 Service Unavailable<br>
<br></div>
74.689429 62.25.18.34 -> 75.82.100.5 SIP Request: CANCEL <a href="mailto:sip%3A5216161070241@75.82.100.5" target="_blank">sip:5216161070241@75.82.100.5</a> <mailto:<a href="mailto:sip%253A5216161070241@75.82.100.5" target="_blank">sip%3A5216161070241@75.82.100.5</a>>;user=phone<div class="Ih2E3d">
<br>
<br>
74.690889 75.82.100.5 -> 62.25.18.34 SIP Status: 200 canceling<br>
<br>
<br>
See, that 503 at the bottom doesn't make it through.. <br>
Another bit of information. The "To:" header contains a prefix to the RURI. I don't care, I ignore the to header.. The 503 reply ALSO has the To Header. The customer, is telling me that the To: header in the 503 reply needs to match the RURI. I believe that I shouldn't ever touch the To: or From: headers and that they should match exactly what he sent me.<br>
<br>
<br>
Any ideas what's going on here? Am I off base?<br>
<br>
<br></div>
------------------------------------------------------------------------<div class="Ih2E3d"><br>
<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
<br>
</div></blockquote>
<br>
</blockquote></div><br>