[VoiceOps] New Exchange 217/777
Adam Vocks
Adam.Vocks at cticomputers.com
Tue Jul 15 10:44:42 EDT 2014
:-)
Take Kidd's call from Verizon in Colorado. If there isn't our exchange
in their local switch, do they forward the call on to another switch in
hopes that it will know where to send it? Similar to a default gateway
in IP world?
Adam
-----Original Message-----
From: Blake Dunlap [mailto:ikiris at gmail.com]
Sent: Tuesday, July 15, 2014 9:39 AM
To: Adam Vocks
Subject: Re: [VoiceOps] New Exchange 217/777
Welcome to the wonderful world of CLEC =)
-Blake
On Tue, Jul 15, 2014 at 9:31 AM, Adam Vocks
<Adam.Vocks at cticomputers.com> wrote:
> Thanks Kidd,
>
>
>
> Here's a question for the group.
>
>
>
> Verizon cell here locally works find, am I going to have to test every
> single Verizon cell tower in the country??? Geesh, there's got to be
> a better way to get these codes out to people.
>
>
>
> Adam
>
>
>
> From: Kidd Filby [mailto:kidd.filby at corp.forethought.net]
> Sent: Tuesday, July 15, 2014 9:28 AM
> To: Adam Vocks
> Subject: Re: [VoiceOps] New Exchange 217/777
>
>
>
> Verizon cell in Colorado says the number's been disconnected. Envoy,
> I get fast busy. AT&T cell in Colorado is good.
>
> ________________________________
>
> From: "Adam Vocks" <Adam.Vocks at cticomputers.com>
> To: voiceops at voiceops.org
> Sent: Monday, July 14, 2014 4:09:44 PM
>
>
> Subject: [VoiceOps] New Exchange 217/777
>
>
> 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 at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
>
> --
>
> Thanks and have a GREAT day!!
>
> Kidd Filby
> FORETHOUGHT.Net
> Dir. Voice Networks
> O: 303.815.1837
> E: kidd.filby at forethought.net
> C: 661.557.5640
>
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
More information about the VoiceOps
mailing list