<div dir="ltr">+1 on Glen's answer.<div><br></div><div>Intermediate carriers deal with enough FAS and other garbage that they cannot trust every 404 or 604. We've determined that it's better to 503 a possibly invalid number for the customer to later retry, than falsely 404 a valid number and get complaints about how we trashed their expensive number list. So long as there is no pre-session media before the 404/604 (i.e. 180/183 tri-tone, voice reject, busy, etc.), we and/or the customer can still route advance and potentially connect that call.</div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><br></div><div dir="ltr"><br></div><div dir="ltr">Regards,<div><br></div><div><p style="font-family:helvetica,arial,sans-serif;font-size:12px;margin:0px;padding:0px 0px 20px;color:rgb(0,0,0)"><strong>Calvin Ellison</strong><br>Voice Services Engineer<br><a href="mailto:calvin.ellison@voxox.com" style="text-decoration:none;color:rgb(14,123,174)" target="_blank">calvin.ellison@voxox.com</a><br>+1 (213) 285-0555<br><br>-----------------------------------------------<br><strong><a href="http://www.voxox.com/" style="text-decoration:none;color:rgb(14,123,174)" target="_blank">voxox.com</a> </strong><br>9276 Scranton Rd, Suite 200<br>San Diego, CA 92121<br></p><img src="http://cdn.voxox.com/img/voxox-logo.png" alt="Voxox" style="color:rgb(0,0,0);font-family:'Times New Roman';font-size:medium"><br></div></div></div></div></div></div>
<br><div class="gmail_quote">On Mon, Oct 12, 2015 at 12:11 PM, Glen Gerhard <span dir="ltr"><<a href="mailto:ggerhard@sansay.com" target="_blank">ggerhard@sansay.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<font size="+1">Hi Erick,<br>
<br>
the only carrier who knows the number is invalid is the LEC/CLEC
that owns the block. They probably will send back a 404 Not Found
or 604 in most cases. However unless you are directly connected
to them you may not get that response returned to you. The
intermediate carriers will generally be configured to return a 503
in case of any failure.<br>
<br>
Also the Cancels you see may be due to the termination carrier
playing an inband ring media that is a tri-tone "your call cannot
be completed as dialed" message. Since it is during the ring
phase the caller (or dialer app) will Cancel the call resulting in
a 487 cause code. For dialer apps this is a benefit since the
good ones will recognize the tri-tone and remove the number from
their calling list.<span class="HOEnZb"><font color="#888888"><br>
<br>
~Glen<br>
</font></span></font><div><div class="h5"><br>
<br>
<div>On 10/5/2015 9:19 AM, Erick Bergquist
wrote:<br>
</div>
<blockquote type="cite">
<pre>Thanks for the replies.
On the cause 41 I get a 503 which matches up.
Getting cause 63 back for the ones where I see SIP 500 Internal Server
Failure which is default behavior.
I guess I'm good then, just wish I wouldn't see 5xx level for
mis-dials. Yes, the numbers are valid E164 formatted numbers for US
which the provider wants to see in that format. I can't call these
numbers from other sytems either so they are indeed bad, un-allocated
numbers.
Thanks, Erick
On Mon, Oct 5, 2015 at 10:51 AM, Jay Hennigan <a href="mailto:jay@west.net" target="_blank"><jay@west.net></a> wrote:
</pre>
<blockquote type="cite">
<pre>On 10/5/15 8:16 AM, Erick Bergquist wrote:
</pre>
<blockquote type="cite">
<pre>Hello,
Just trying to get idea of what is normal on what providers should
return for a misdial, bad unknown number, etc.
On one provider, I get a CANCEL and a 487 Request Terminated on mis-dials.
On another provider, I get a 503 Service Unavailable and a 500
Internal Service Error back.
</pre>
</blockquote>
<pre>
It depends. CANCEL and 487 Request Terminated typically comes from the
originator and means that you hung up before the call completed. Carrier was
in post-dial delay and hadn't returned anything (yet).
503 means that the carrier can't or won't process the call. Could be a
misdial where the number can't be parsed as in not enough or too many
digits, prefix starts with 1 or 0, etc. Could also be that you tried to dial
a valid number that the carrier doesn't handle, such as international,
900/976, etc. Could also mean that you didn't pay your bill or are coming
from an IP address that isn't a customer of that carrier.
For a number that is in the correct format but isn't in service, you might
see 503 or also 404 or 604.
500 internal service error is usually a technical problem with the carrier
and not a misdial.
Different carriers map ISDN/SS7 cause codes to SIP differently. See:
<a href="https://www.google.com/search?q=isdn+cause+code+to+sip+mapping" target="_blank">https://www.google.com/search?q=isdn+cause+code+to+sip+mapping</a>
--
Jay Hennigan - CCIE #7880 - Network Engineering - <a href="mailto:jay@impulse.net" target="_blank">jay@impulse.net</a>
Impulse Internet Service - <a href="http://www.impulse.net/" target="_blank">http://www.impulse.net/</a>
Your local telephone and internet company - <a href="tel:805%20884-6323" value="+18058846323" target="_blank">805 884-6323</a> - WB6RDV
_______________________________________________
VoiceOps mailing list
<a href="mailto:VoiceOps@voiceops.org" target="_blank">VoiceOps@voiceops.org</a>
<a href="https://puck.nether.net/mailman/listinfo/voiceops" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a>
</pre>
</blockquote>
<pre>_______________________________________________
VoiceOps mailing list
<a href="mailto:VoiceOps@voiceops.org" target="_blank">VoiceOps@voiceops.org</a>
<a href="https://puck.nether.net/mailman/listinfo/voiceops" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a>
</pre>
</blockquote>
<br>
</div></div></div>
<br>_______________________________________________<br>
VoiceOps mailing list<br>
<a href="mailto:VoiceOps@voiceops.org">VoiceOps@voiceops.org</a><br>
<a href="https://puck.nether.net/mailman/listinfo/voiceops" rel="noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a><br>
<br></blockquote></div><br></div>