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 <adam.vo...@cticomputers.com> 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
> VoiceOps@voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
_______________________________________________
VoiceOps mailing list
VoiceOps@voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops

Reply via email to