New CO Office Codes have a 45-60 day turn up period from the time the NeuStar/NANPA Part 3 form is approved. Technically, when the code administrator puts the NPA-NXX into the LERG, anybody with access to BIRRDS can look it up and program their switch accordingly, but it's not mandatory. We subscribe to LERG Updates quarterly, and would download the LERG files to parse out what is new for that quarter. We add the translations for new codes and remove them for disconnecting codes.
There may be automated ways of checking the LERG and updating translation tables, but it's still a manual process for most. Fat-fingering translations can cause big problems, so we tread lightly. For official numbering information, including the timeframes the numbering industry goes by, the ATIS website has links to numbering guidelines: http://www.atis.org/inc/incguides.asp - Central Office Code (NXX) Assignment Guidelines (COCAG) link and - Thousands-Block Number (NXX-X) Pooling Administration Guidelines (TBPAG). Jamie Montgomery | Comporium Network Facilities Engineering | Engineering Associate II The information contained in this e-mail message and any attachments thereto are confidential, privileged, or otherwise protected from disclosure, and are intended for the use of the individual or entity named above. Dissemination, distribution or copying of this message and any attachments by anyone other than the intended recipient, or an employee or agent responsible for delivering the message to the intended recipient, is prohibited. If you have received this communication in error, please immediately notify the sender by telephone or e-mail and destroy the original message, attachments, and all copies. -----Original Message----- From: VoiceOps [mailto:[email protected]] On Behalf Of [email protected] Sent: Tuesday, July 15, 2014 12:00 PM To: [email protected] Subject: VoiceOps Digest, Vol 61, Issue 10 Send VoiceOps mailing list submissions to [email protected] To subscribe or unsubscribe via the World Wide Web, visit https://puck.nether.net/mailman/listinfo/voiceops or, via email, send a message with subject or body 'help' to [email protected] You can reach the person managing the list at [email protected] When replying, please edit your Subject line so it is more specific than "Re: Contents of VoiceOps digest..." Today's Topics: 1. Re: New Exchange 217/777 (Graham Freeman) 2. Re: New Exchange 217/777 (Nick Crocker) ---------------------------------------------------------------------- Message: 1 Date: Tue, 15 Jul 2014 08:42:22 -0700 From: Graham Freeman <[email protected]> To: Adam Vocks <[email protected]> Cc: "<[email protected]>" <[email protected]> Subject: Re: [VoiceOps] New Exchange 217/777 Message-ID: <[email protected]> Content-Type: text/plain; charset="utf-8" Test results: Verizon Wireless in California: success Sonic Telecom: dead air Sprint (via Ting): dead air Graham Freeman Sent from my mobile > On 14 Jul 2014, at 15:09, Adam Vocks <[email protected]> wrote: > > Hi everyone, > > I stumbled on this list recently and have been reading through the archives. > Thanks for all the information you?ve all shared. > > We?re a CLEC in Illinois and are in the middle of building a FTTH network in > our home town. In December our exchange 217-777 was effective. We?re using > ANPI?s Tandem service for our Feature Group D traffic and using our ILEC > (Consolidated Communications) as our intralata/local tandem. > > No troubles on the Intralata/local terminating traffic, however, we?re having > more and more reports of different people out in the world that can?t call > our customers. > > It started with AT&T Cellular, that?s been resolved, then we heard from > Sprint PCS, that?s been resolved. Next was Comcast Business, that?s been > resolved. > > Latest example is a caller from Texas who is on Time Warner Cable: > > LRN: 12543004000 > OCN: 583C > LATA: 556 > CITY: WACO > STATE: TX > LEC: TIME WARNER CBLE INFO SVC (TX) DBA TIME WARNER CBL > > When they call us they just get dead air. > > I guess my questions are: How long after the effective date in the BIRRDS > database do all of the switches get updated? Is this a typical problem with > a new exchange/LRN? > > A follow up question: is there a service out there that will originate calls > from many different telcos and if they fail, open up a ticket with that > carrier? I?m running into roadblocks calling these carriers since I am not a > customer. > > I?ve got a test number set up on 217-777-0001, ?Thank you for Calling. You > have reached a test number. Your telephone number is? ? if there?s anyone > out there who wants to give it a test and report back, fine by me. It seems > the more information I have the better. > > Thanks for listening, > > Adam Vocks > > > _______________________________________________ > VoiceOps mailing list > [email protected] > https://puck.nether.net/mailman/listinfo/voiceops -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://puck.nether.net/pipermail/voiceops/attachments/20140715/a26b43cd/attachment-0001.html> ------------------------------ Message: 2 Date: Tue, 15 Jul 2014 10:58:28 -0500 From: Nick Crocker <[email protected]> To: "<[email protected]>" <[email protected]> Subject: Re: [VoiceOps] New Exchange 217/777 Message-ID: <cacw3o7g6cge_8mx9sx6wkjg36qdpx0tr7gr33obueeepk53...@mail.gmail.com> Content-Type: text/plain; charset="utf-8" VZW out of Austin, TX successful call completion to the test TN -Nick On Tue, Jul 15, 2014 at 10:42 AM, Graham Freeman <[email protected]> wrote: > Test results: > > Verizon Wireless in California: success > > Sonic Telecom: dead air > > Sprint (via Ting): dead air > > Graham Freeman > Sent from my mobile > > On 14 Jul 2014, at 15:09, Adam Vocks <[email protected]> wrote: > > Hi everyone, > > > > I stumbled on this list recently and have been reading through the > archives. Thanks for all the information you?ve all shared. > > > > We?re a CLEC in Illinois and are in the middle of building a FTTH > network in our home town. In December our exchange 217-777 was > effective. We?re using ANPI?s Tandem service for our Feature Group D > traffic and using our ILEC (Consolidated Communications) as our > intralata/local tandem. > > > > No troubles on the Intralata/local terminating traffic, however, we?re > having more and more reports of different people out in the world that > can?t call our customers. > > > > It started with AT&T Cellular, that?s been resolved, then we heard > from Sprint PCS, that?s been resolved. Next was Comcast Business, > that?s been resolved. > > > > Latest example is a caller from Texas who is on Time Warner Cable: > > > > LRN: 12543004000 > > OCN: 583C > > LATA: 556 > > CITY: WACO > > STATE: TX > > LEC: TIME WARNER CBLE INFO SVC (TX) DBA TIME WARNER CBL > > > > When they call us they just get dead air. > > > > I guess my questions are: How long after the effective date in the > BIRRDS database do all of the switches get updated? Is this a typical > problem with a new exchange/LRN? > > > > A follow up question: is there a service out there that will originate > calls from many different telcos and if they fail, open up a ticket > with that carrier? I?m running into roadblocks calling these carriers > since I am not a customer. > > > > I?ve got a test number set up on 217-777-0001, ?Thank you for Calling. > You have reached a test number. Your telephone number is? ? if > there?s anyone out there who wants to give it a test and report back, fine by > me. > It seems the more information I have the better. > > > > Thanks for listening, > > > > Adam Vocks > > > > > > _______________________________________________ > > VoiceOps mailing list > [email protected] > https://puck.nether.net/mailman/listinfo/voiceops > > > _______________________________________________ > VoiceOps mailing list > [email protected] > https://puck.nether.net/mailman/listinfo/voiceops > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://puck.nether.net/pipermail/voiceops/attachments/20140715/40ad1c42/attachment-0001.html> ------------------------------ Subject: Digest Footer _______________________________________________ VoiceOps mailing list [email protected] https://puck.nether.net/mailman/listinfo/voiceops ------------------------------ End of VoiceOps Digest, Vol 61, Issue 10 **************************************** _______________________________________________ VoiceOps mailing list [email protected] https://puck.nether.net/mailman/listinfo/voiceops
