[VoiceOps] New Exchange 217/777

Tue Jul 15 11:33:18 EDT 2014

Thanks everyone for your help.  I hope to be able to pay it forward someday.

Adam

From: Kidd Filby [mailto:kidd.filby at corp.forethought.net] 
Sent: Tuesday, July 15, 2014 10:23 AM
To: Adam Vocks
Subject: Re: [VoiceOps] New Exchange 217/777

Just got off the phone with Verizon.  Funny... the call works now from Denver.  I'm guessing now but, I think it was an overflow/re-route issue I hit this morning.  While the call went through, their 2nd tier is investigating any re-routes that may have happened and will "call me back".  The point is, I believe Verizon's network is probably clean... this time.

I'll try to get envoy on the stick now.  This might be the needle....

Kidd

________________________________

From: "Adam Vocks" <Adam.Vocks at cticomputers.com>
To: "Kidd Filby" <kidd.filby at corp..forethought.net>
Sent: Tuesday, July 15, 2014 9:05:31 AM
Subject: RE: [VoiceOps] New Exchange 217/777

Thanks, that makes me feel better.  We just found out there’s a problem with Level3 that level3 is working backwards for us.

Adam

From: Kidd Filby [mailto:kidd.filby at corp.forethought.net] 
Sent: Tuesday, July 15, 2014 9:54 AM
To: Adam Vocks
Subject: Re: [VoiceOps] New Exchange 217/777

Adam;

No problem.  Glad to help.

In 30 years, I have never heard of such a wide-spread issue with a single code.  This leads me to believe there is a small group of carriers or even just one really LOW COST carrier out there who have/has not loaded your code and they seem to be in a lot of people's routing table within an LCR or similar.  Time of day, overflow, congestion... all of these can throw intermittent issues at you as well.

No... you wont have to test every cell tower.. it will just feel that way.  Honestly, its got to be a commonality as I mentioned above.  In an LD route, the originating switch is only going to look at NPA-NXX (Most of the time, sometimes just NPA) and route out to a carrier.  The carrier will route the call to the destination LATA (Most of the time) and the local LATA/interLATA (of the destination TN) tandem will route to the end office switch.  The local & interLATA tandems must be OK, since the call completes, sometimes.  Do you have any directly connected carriers the call does not work over?  That may be a route you can backwards troubleshoot with.

Good luck;
Kidd

________________________________

From: "Adam Vocks" <Adam.Vocks at cticomputers.com>
To: voiceops at voiceops.org
Sent: Tuesday, July 15, 2014 8:31:40 AM
Subject: Re: [VoiceOps] New Exchange 217/777

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

-- 

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

-- 

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

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