<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><meta name="Generator" content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
span.hoenzb
{mso-style-name:hoenzb;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
mso-fareast-language:EN-CA;}
span.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang="EN-CA" link="blue" vlink="purple"><div class="WordSection1"><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Except… that in case of call centre traffic, this leads to repeated dialling of invalid numbers, leading to a ridiculous number of unnecessary calls. </span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">It is a pet peeve of mine and I wish there was a way to fix it. So that invalid numbers can get a permanent failure result and stop clogging up our network and ruining the connect rate. </span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">To illustrate the issue… if a call centre starts calling a monthly list which has 10-15% invalid numbers (typical). By the end of the month, they will be calling those numbers daily (or several times per day, since 503 is an error, not a valid attempt)… and as they deplete the list, those invalid numbers will be dialed more and more frequently. If they don’t have a maximum attempt limit, you are really screwed.</span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Even if they do, and is set to 10 or 15, these will be dialed the full number of attempts... If all other records complete in 3-4 attempts on average, these will go the full 15 (because of 503 or other temporary failure response)… so in the end… those 10% of invalid numbers will result in a much larger % of (unnecessary) dials. </span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">I think this is one of those things that’s waiting for a standard or a smart provider to come along and fix it. I’ve toyed with the idea of letting our CPA resources run against all 503s to see if we can sort out some of these based on early media/tri-tone/voice reject. Just haven’t had time to do it… and we do what everyone else does… just let the clients dial these and pass the crap to our downstream providers… </span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">In the meantime, we tell our call centre clients to go through their lists in power/preview mode towards the end… so they could scrub these NIS records. This is a half-ass solution in my opinion, but without a better one… it’s all they can do.</span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">I’ve tried raising the issue with our providers as well, to try to get better (more accurate) SIP responses… but here isn’t much they can do either… so… here we are. </span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Best Regards,</span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Ivan Kovacevic</span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Vice President, Client Services</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Star Telecom | <a href="http://www.startelecom.ca/">www.startelecom.ca</a> | SIP Based Services for Contact Centers | <a href="http://www.linkedin.com/company/star-telecom-www.startelecom.ca-?trk=top_nav_home">LinkedIn</a></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span></p><p class="MsoNormal"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> VoiceOps [mailto:<a href="mailto:voiceops-bounces@voiceops.org">voiceops-bounces@voiceops.org</a>] <b>On Behalf Of </b>Calvin Ellison<br><b>Sent:</b> Monday, October 12, 2015 3:46 PM<br><b>To:</b> Voiceops.org <<a href="mailto:voiceops@voiceops.org">voiceops@voiceops.org</a>><br><b>Subject:</b> Re: [VoiceOps] SIP return message on misdials - 487 or 500/503 or ?</span></p><p class="MsoNormal"> </p><div><p class="MsoNormal">+1 on Glen's answer.</p><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">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.</p></div></div><div><p class="MsoNormal"><br clear="all"></p><div><div><div><div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">Regards,</p><div><p class="MsoNormal"> </p></div><div><p style="margin:0in;margin-bottom:.0001pt"><strong><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif;color:black">Calvin Ellison</span></strong><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif;color:black"><br>Voice Services Engineer<br><a href="mailto:calvin.ellison@voxox.com" target="_blank"><span style="color:#0e7bae;text-decoration:none">calvin.ellison@voxox.com</span></a><br>+1 (213) 285-0555<br><br>-----------------------------------------------<br><strong><span style="font-family:"Helvetica",sans-serif"><a href="http://www.voxox.com/" target="_blank"><span style="color:#0e7bae;text-decoration:none">voxox.com</span></a> </span></strong><br>9276 Scranton Rd, Suite 200<br>San Diego, CA 92121</span></p><p class="MsoNormal"><img border="0" id="_x0000_i1025" src="http://cdn.voxox.com/img/voxox-logo.png" alt="Voxox"></p></div></div></div></div></div></div><p class="MsoNormal"> </p><div><p class="MsoNormal">On Mon, Oct 12, 2015 at 12:11 PM, Glen Gerhard <<a href="mailto:ggerhard@sansay.com" target="_blank">ggerhard@sansay.com</a>> wrote:</p><blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in"><div><p class="MsoNormal"><span style="font-size:13.5pt">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 style="color:#888888"><br><br><span class="hoenzb">~Glen</span></span></span></p><div><div><p class="MsoNormal" style="margin-bottom:12.0pt"> </p><div><p class="MsoNormal">On 10/5/2015 9:19 AM, Erick Bergquist wrote:</p></div><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><pre>Thanks for the replies.</pre><pre> </pre><pre>On the cause 41 I get a 503 which matches up.</pre><pre> </pre><pre>Getting cause 63 back for the ones where I see SIP 500 Internal Server</pre><pre>Failure which is default behavior.</pre><pre> </pre><pre> I guess I'm good then, just wish I wouldn't see 5xx level for</pre><pre>mis-dials. Yes, the numbers are valid E164 formatted numbers for US</pre><pre>which the provider wants to see in that format. I can't call these</pre><pre>numbers from other sytems either so they are indeed bad, un-allocated</pre><pre>numbers.</pre><pre> </pre><pre> </pre><pre>Thanks, Erick</pre><pre> </pre><pre>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 style="margin-top:5.0pt;margin-bottom:5.0pt"><pre>On 10/5/15 8:16 AM, Erick Bergquist wrote:</pre><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><pre>Hello,</pre><pre> </pre><pre>Just trying to get idea of what is normal on what providers should</pre><pre>return for a misdial, bad unknown number, etc.</pre><pre> </pre><pre>On one provider, I get a CANCEL and a 487 Request Terminated on mis-dials.</pre><pre> </pre><pre>On another provider, I get a 503 Service Unavailable and a 500</pre><pre>Internal Service Error back.</pre></blockquote><pre> </pre><pre>It depends. CANCEL and 487 Request Terminated typically comes from the</pre><pre>originator and means that you hung up before the call completed. Carrier was</pre><pre>in post-dial delay and hadn't returned anything (yet).</pre><pre> </pre><pre>503 means that the carrier can't or won't process the call. Could be a</pre><pre>misdial where the number can't be parsed as in not enough or too many</pre><pre>digits, prefix starts with 1 or 0, etc. Could also be that you tried to dial</pre><pre>a valid number that the carrier doesn't handle, such as international,</pre><pre>900/976, etc. Could also mean that you didn't pay your bill or are coming</pre><pre>from an IP address that isn't a customer of that carrier.</pre><pre> </pre><pre>For a number that is in the correct format but isn't in service, you might</pre><pre>see 503 or also 404 or 604.</pre><pre> </pre><pre>500 internal service error is usually a technical problem with the carrier</pre><pre>and not a misdial.</pre><pre> </pre><pre>Different carriers map ISDN/SS7 cause codes to SIP differently. See:</pre><pre> </pre><pre><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></pre><pre> </pre><pre>--</pre><pre>Jay Hennigan - CCIE #7880 - Network Engineering - <a href="mailto:jay@impulse.net" target="_blank">jay@impulse.net</a></pre><pre>Impulse Internet Service - <a href="http://www.impulse.net/" target="_blank">http://www.impulse.net/</a></pre><pre>Your local telephone and internet company - <a href="tel:805%20884-6323" target="_blank">805 884-6323</a> - WB6RDV</pre><pre> </pre><pre>_______________________________________________</pre><pre>VoiceOps mailing list</pre><pre><a href="mailto:VoiceOps@voiceops.org" target="_blank">VoiceOps@voiceops.org</a></pre><pre><a href="https://puck.nether.net/mailman/listinfo/voiceops" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a></pre></blockquote><pre>_______________________________________________</pre><pre>VoiceOps mailing list</pre><pre><a href="mailto:VoiceOps@voiceops.org" target="_blank">VoiceOps@voiceops.org</a></pre><pre><a href="https://puck.nether.net/mailman/listinfo/voiceops" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a></pre></blockquote><p class="MsoNormal"> </p></div></div></div><p class="MsoNormal" style="margin-bottom:12.0pt"><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" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a></p></blockquote></div><p class="MsoNormal"> </p></div></div></body></html>