<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix"><br>
What about the text portion? Should that never be sent? I was
indeed sending the '1', and I will remove that to see if it solves
my problem, but I also have the company name in there. I feel
like a newb asking such questions, but I've never had this issue
before :)<br>
<br>
"Company" <1NXXNXXXXXX><br>
<br>
Cheers,<br>
<br>
j<br>
<br>
On 08/20/2014 09:46 AM, Eric Wieling wrote:<br>
</div>
<blockquote
cite="mid:616B4ECE1290D441AD56124FEBB03D082D1DF69271@mailserver2007.nyigc.globe"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<meta name="Generator" content="Microsoft Word 12 (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:Tahoma;
panose-1:2 11 6 4 3 5 4 4 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";
color:black;}
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.EmailStyle17
{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]-->
<div class="WordSection1">
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:Consolas;color:#1F497D">NXXNXXXXXX
is the correct format of CallerID numbers in NANPA. The
leading 1 is not part of any NANPA phone number. Toll
free “area codes” are also not valid for CallerID.<o:p></o:p></span></p>
</div>
<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";color:windowtext">From:</span></b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext">
<a class="moz-txt-link-abbreviated" href="mailto:asterisk-users-bounces@lists.digium.com">asterisk-users-bounces@lists.digium.com</a>
[<a class="moz-txt-link-freetext" href="mailto:asterisk-users-bounces@lists.digium.com">mailto:asterisk-users-bounces@lists.digium.com</a>] <b>On
Behalf Of </b>Jeff LaCoursiere<br>
<b>Sent:</b> Wednesday, August 20, 2014 2:41 PM<br>
<b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:asterisk-users@lists.digium.com">asterisk-users@lists.digium.com</a><br>
<b>Subject:</b> Re: [asterisk-users] PRI timing settings<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On 08/20/2014 07:58 AM, Scott L. Lykens
wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<p class="MsoNormal">On Aug 19, 2014, at 5:56 PM, Jeff
LaCoursiere <<a moz-do-not-send="true"
href="mailto:jeff@jeff.net">jeff@jeff.net</a>>
wrote:<o:p></o:p></p>
</div>
<p class="MsoNormal"><br>
<br>
<o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:9.0pt;font-family:"Helvetica","sans-serif";background:white">I
wrote earlier today about a new PRI installation in the
Caribbean, where all outbound calls are functioning fine
*except* calls to Sprint phone numbers, which get
rejected immediately as "busy".</span><o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">I don’t know what expectations for CLID
your carrier might have, or for that matter the upstream
carrier, however, we found through our CLEC here in the US
that while the CLEC was happy to take e.164 formatted
numbers from us as CLID, Global Crossing would reject them
further upstream resulting in our calls to many toll frees
being rejected.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Switching to 10 digit CLID on all
outbound calls through that PRI solved the problem.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I don’t know if this is your problem
but be sure your CLID is in the most simple format
possible for your region to help rule it out.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">sl<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</blockquote>
<p class="MsoNormal"><br>
This makes me curious... what *is* the simplest format
possible for NANPA numbers? I'm sure there must be a spec to
conform to. Can anyone point me to it?<br>
<br>
Cheers,<br>
<br>
j<o:p></o:p></p>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
</blockquote>
<br>
</body>
</html>