<div>One thing to note here, the BTN is passed to the IXC, like Marks says, for billing purposes. If this is a number the IXC is unfamiliar with on your account for that circuit, the IXC will likely at some point start blocking those calls. For example, if you have two existing CO trunks with number 212-555-1212 and 212-555-1213, the IXC will bill to those numbers to the BTN on your account. If your BTN changes on the new circuit and the LEC is no longer sending 212-555-1212, or 1213 as the BTN, they might eventually classify the new calls as toll fraud and start blocking the calls. Long story short, make sure you long distance carriers knows the new BTN being used by the LEC. </div>
<div> </div>
<div>Additionally, if your customers have become familiar with the outbound caller id on calls from your office and you're NOT providing the outbound caller-id over the PRI using external number masks, or route lists, or if the provider doesn't let you override caller-id, it will likely go out as this new BTN. (just noticed this was Mark's point as well)</div>
<div> </div>
<div>hope that helps<br><br></div>
<div class="gmail_quote">On Mon, Jul 13, 2009 at 2:32 PM, Mark Holloway <span dir="ltr"><<a href="mailto:mh@markholloway.com">mh@markholloway.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div style="WORD-WRAP: break-word">Usually the "main" number is referred to the BTN and the LEC uses this for reference purposes in their own ordering system. In the end it doesn't really matter which number is the BTN. In rare cases the LEC may use the BTN for outbound CLID if you indicate your don't want unique CLID per DID.
<div><br></div>
<div><br>
<div>
<div>
<div></div>
<div class="h5">
<div>On Jul 13, 2009, at 12:14 PM, Jeff Ruttman wrote:</div><br></div></div>
<blockquote type="cite">
<div>
<div></div>
<div class="h5">
<div>
<div><font face="Arial" size="2"><span>Greetings,</span></font></div>
<div><font face="Arial" size="2"><span></span></font> </div>
<div><font face="Arial" size="2"><span>One of our sites is changing from inbound trunks and DIDs and pots lines to a PRI and our DIDs. I got a call from Verizon and they asked me what number I wanted on the PRI, and usually (They said.) that is the main number of the business. Well the main number out there is one of our DIDs, and that can't be assigned to the PRI.</span></font></div>
<div><font face="Arial" size="2"><span></span></font> </div>
<div><font face="Arial" size="2"><span>I don't care what number they put on the PRI, do I? Is this right: On telco's side, they point our DIDs to whatever number is assigned to the PRI, then Gateway\CCM et all route incoming calls from the PRI according to the DID that the caller dialed. So Verizon can assign any number they want, right?</span></font></div>
<div><font face="Arial" size="2"><span></span></font> </div>
<div><font face="Arial" size="2"><span>Thanks</span></font></div>
<div><font face="Arial" size="2"><span>jeff</span></font></div>
<div> </div>CONFIDENTIALITY NOTICE: The information contained in this email including attachments is intended for the specific delivery to and use by the individual(s) to whom it is addressed, and includes information which should be considered as private and confidential. Any review, retransmission, dissemination, or taking of any action in reliance upon this information by anyone other than the intended recipient is prohibited. If you have received this message in error, please reply to the sender immediately and delete the original message and any copy of it from your computer system. Thank you.</div>
</div></div>_______________________________________________<br>cisco-voip mailing list<br><a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br><a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
</blockquote></div><br></div></div><br>_______________________________________________<br>cisco-voip mailing list<br><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br><a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br></blockquote></div><br>