[cisco-voip] Telco, New PRI Questions

[Mark Holloway]

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.


On Jul 13, 2009, at 12:14 PM, Jeff Ruttman wrote:

> Greetings,
>
> 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.
>
> 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?
>
> Thanks
> jeff
>
> 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.
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20090713/7afcb38c/attachment.html>