[VoiceOps] New Exchange 217/777

Adam Vocks Adam.Vocks at cticomputers.com
Mon Jul 14 18:09:44 EDT 2014


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

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20140714/e7d99b2a/attachment.html>


More information about the VoiceOps mailing list