<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 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;}
span.apple-tab-span
{mso-style-name:apple-tab-span;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>So is there anything other than industry best practice on this?<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Something official maybe from a LEC or IXC at least, FCC or NANPA would be even better. I’ve had this argument with customers again and again, and I can tell them what may happen, but I’ve never had any document from someone they’d believe to back it up.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> voiceops-bounces@voiceops.org [mailto:voiceops-bounces@voiceops.org] <b>On Behalf Of </b>Mark Holloway<br><b>Sent:</b> Wednesday, February 15, 2012 11:55 PM<br><b>To:</b> Darren Schreiber<br><b>Cc:</b> VoiceOps@voiceops.org<br><b>Subject:</b> Re: [VoiceOps] Terminating 800 traffic with Caller ID of an 800 #<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Some providers require a charge number to be present. They won't route the call if only the 800# exists. <o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>On Feb 15, 2012, at 4:29 PM, Darren Schreiber wrote:<o:p></o:p></p></div><p class=MsoNormal><br><br><o:p></o:p></p><div><div><div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif";color:black'>Hi folks,<o:p></o:p></span></p></div></div></div><div><p class=MsoNormal><span class=apple-tab-span><span style='font-size:10.5pt;font-family:"Calibri","sans-serif";color:black'> </span></span><span style='font-size:10.5pt;font-family:"Calibri","sans-serif";color:black'>We have a customer who is insisting on setting their outbound Caller ID to an 800 #. They are complaining that <i>they </i>can't call other 800 #s. Our testing reveals that many carriers are refusing to route the call when the Caller ID is set as an 800 #.<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif";color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span class=apple-tab-span><span style='font-size:10.5pt;font-family:"Calibri","sans-serif";color:black'> </span></span><span style='font-size:10.5pt;font-family:"Calibri","sans-serif";color:black'>In addition, if we try setting the ANI as one number via the From: header and then add a remote party ID header as Caller ID, it seems that most carriers use the From: and deliver that as the Caller ID to the alternate/receiving 800 #.<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif";color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span class=apple-tab-span><span style='font-size:10.5pt;font-family:"Calibri","sans-serif";color:black'> </span></span><span style='font-size:10.5pt;font-family:"Calibri","sans-serif";color:black'>Any thoughts on this? I am aware that it's up to the receiving 800 # to decide what NPAs to allow through and that what they're proposing complicates billing, so I suspect I just need to tell the client to deal, but they are insisting that this used to work on their PRI. My theory is that it did not work on their PRI but nobody ever noticed before.<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif";color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif";color:black'>- Darren<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif";color:black'><o:p> </o:p></span></p></div></div><p class=MsoNormal>_______________________________________________<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">https://puck.nether.net/mailman/listinfo/voiceops</a><o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p></div></div></body></html>