VoiceOps
By thread
voiceops@voiceops.org
By month
Messages by month
- ----- 2026 -----
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2025 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2024 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2023 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2022 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2021 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2020 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2019 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2018 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2017 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2016 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2015 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2014 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2013 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2012 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2011 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2010 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2009 -----
- December
- November
- October
- September
- August
- July
July 2014
- 43 participants
- 96 messages
New Exchange 217/777
by paul@timmins.net
Level 3 is a big wholesale route for a lot of smaller IXC carriers and
VoIP providers, so when they fix it, you'll probably see immense
improvement.
On 07/15/2014 02:10 PM, Adam Vocks wrote:
> I'm really hoping Level3 is having a routing issue with our code. Some
> tried a call on level3 to us which failed. Odd things is that Level3 is
> directly connected to the Tandem we subtend. I wouldn't think Level3
> would send it off their network???
>
> Adam
>
> -----Original Message-----
> From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of Paul
> Timmins
> Sent: Tuesday, July 15, 2014 12:30 PM
> To: voiceops at voiceops.org
> Subject: Re: [VoiceOps] New Exchange 217/777
>
> What's worse really is not that you have to look at ILEC tandems out of
> area - they don't perform any route filtering, if the originating caller
> is calling out of area, it gets sent to their PIC/LPIC LD carrier.
>
> So what you really need is every IXC in the country to make sure they
> have a route to you either directly, through whatever tandem homing
> arrangements you have, or via another IXC (really common especially in
> rural areas to see a Level 3/Global Crossing hand off to
> Qwest/AT&T/Verizon for the final termination.).
>
> -Paul
>
> On 07/15/2014 10:52 AM, Adam Vocks wrote:
>> So, at the very least, I need to start looking at each of the ILEC's
>> tandems in a specific LATA?
>>
>> Adam
>>
>> -----Original Message-----
>> From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of
>> Alex Balashov
>> Sent: Tuesday, July 15, 2014 9:48 AM
>> To: voiceops at voiceops.org
>> Subject: Re: [VoiceOps] New Exchange 217/777
>>
>> On 07/15/2014 10:44 AM, Adam Vocks wrote:
>>
>>> :-)
>>>
>>> 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?
>> It would get kicked up to an ILEC tandem inside that LATA. There is
>> really no default gateway beyond that; at that point, you've already
>> exited into what the IP world would call "default route-free" or "Tier
>> 1" routing space.
>>
>> --
>> Alex Balashov - Principal
>> Evariste Systems LLC
>> Tel: +1-678-954-0670
>> Web: http://www.evaristesys.com/, http://www.alexbalashov.com/
>>
>> Please be kind to the English language:
>>
>> http://www.entrepreneur.com/article/232906
>> _______________________________________________
>> VoiceOps mailing list
>> VoiceOps at voiceops.org
>> https://puck.nether.net/mailman/listinfo/voiceops
>>
>> _______________________________________________
>> VoiceOps mailing list
>> VoiceOps at voiceops.org
>> https://puck.nether.net/mailman/listinfo/voiceops
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
July 15, 2014
New Exchange 217/777
by paul@timmins.net
Level 3 is a big wholesale route for a lot of smaller IXC carriers and
VoIP providers, so when they fix it, you'll probably see immense
improvement.
On 07/15/2014 02:10 PM, Adam Vocks wrote:
> I'm really hoping Level3 is having a routing issue with our code. Some
> tried a call on level3 to us which failed. Odd things is that Level3 is
> directly connected to the Tandem we subtend. I wouldn't think Level3
> would send it off their network???
>
> Adam
>
> -----Original Message-----
> From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of Paul
> Timmins
> Sent: Tuesday, July 15, 2014 12:30 PM
> To: voiceops at voiceops.org
> Subject: Re: [VoiceOps] New Exchange 217/777
>
> What's worse really is not that you have to look at ILEC tandems out of
> area - they don't perform any route filtering, if the originating caller
> is calling out of area, it gets sent to their PIC/LPIC LD carrier.
>
> So what you really need is every IXC in the country to make sure they
> have a route to you either directly, through whatever tandem homing
> arrangements you have, or via another IXC (really common especially in
> rural areas to see a Level 3/Global Crossing hand off to
> Qwest/AT&T/Verizon for the final termination.).
>
> -Paul
>
> On 07/15/2014 10:52 AM, Adam Vocks wrote:
>> So, at the very least, I need to start looking at each of the ILEC's
>> tandems in a specific LATA?
>>
>> Adam
>>
>> -----Original Message-----
>> From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of
>> Alex Balashov
>> Sent: Tuesday, July 15, 2014 9:48 AM
>> To: voiceops at voiceops.org
>> Subject: Re: [VoiceOps] New Exchange 217/777
>>
>> On 07/15/2014 10:44 AM, Adam Vocks wrote:
>>
>>> :-)
>>>
>>> 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?
>> It would get kicked up to an ILEC tandem inside that LATA. There is
>> really no default gateway beyond that; at that point, you've already
>> exited into what the IP world would call "default route-free" or "Tier
>> 1" routing space.
>>
>> --
>> Alex Balashov - Principal
>> Evariste Systems LLC
>> Tel: +1-678-954-0670
>> Web: http://www.evaristesys.com/, http://www.alexbalashov.com/
>>
>> Please be kind to the English language:
>>
>> http://www.entrepreneur.com/article/232906
>> _______________________________________________
>> VoiceOps mailing list
>> VoiceOps at voiceops.org
>> https://puck.nether.net/mailman/listinfo/voiceops
>>
>> _______________________________________________
>> VoiceOps mailing list
>> VoiceOps at voiceops.org
>> https://puck.nether.net/mailman/listinfo/voiceops
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
July 15, 2014
New Exchange 217/777
by paul@timmins.net
Level 3 is a big wholesale route for a lot of smaller IXC carriers and
VoIP providers, so when they fix it, you'll probably see immense
improvement.
On 07/15/2014 02:10 PM, Adam Vocks wrote:
> I'm really hoping Level3 is having a routing issue with our code. Some
> tried a call on level3 to us which failed. Odd things is that Level3 is
> directly connected to the Tandem we subtend. I wouldn't think Level3
> would send it off their network???
>
> Adam
>
> -----Original Message-----
> From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of Paul
> Timmins
> Sent: Tuesday, July 15, 2014 12:30 PM
> To: voiceops at voiceops.org
> Subject: Re: [VoiceOps] New Exchange 217/777
>
> What's worse really is not that you have to look at ILEC tandems out of
> area - they don't perform any route filtering, if the originating caller
> is calling out of area, it gets sent to their PIC/LPIC LD carrier.
>
> So what you really need is every IXC in the country to make sure they
> have a route to you either directly, through whatever tandem homing
> arrangements you have, or via another IXC (really common especially in
> rural areas to see a Level 3/Global Crossing hand off to
> Qwest/AT&T/Verizon for the final termination.).
>
> -Paul
>
> On 07/15/2014 10:52 AM, Adam Vocks wrote:
>> So, at the very least, I need to start looking at each of the ILEC's
>> tandems in a specific LATA?
>>
>> Adam
>>
>> -----Original Message-----
>> From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of
>> Alex Balashov
>> Sent: Tuesday, July 15, 2014 9:48 AM
>> To: voiceops at voiceops.org
>> Subject: Re: [VoiceOps] New Exchange 217/777
>>
>> On 07/15/2014 10:44 AM, Adam Vocks wrote:
>>
>>> :-)
>>>
>>> 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?
>> It would get kicked up to an ILEC tandem inside that LATA. There is
>> really no default gateway beyond that; at that point, you've already
>> exited into what the IP world would call "default route-free" or "Tier
>> 1" routing space.
>>
>> --
>> Alex Balashov - Principal
>> Evariste Systems LLC
>> Tel: +1-678-954-0670
>> Web: http://www.evaristesys.com/, http://www.alexbalashov.com/
>>
>> Please be kind to the English language:
>>
>> http://www.entrepreneur.com/article/232906
>> _______________________________________________
>> VoiceOps mailing list
>> VoiceOps at voiceops.org
>> https://puck.nether.net/mailman/listinfo/voiceops
>>
>> _______________________________________________
>> VoiceOps mailing list
>> VoiceOps at voiceops.org
>> https://puck.nether.net/mailman/listinfo/voiceops
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
July 15, 2014
New Exchange 217/777
by Jamie.Montgomery@comporium.com
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:voiceops-bounces at voiceops.org] On Behalf Of voiceops-request at voiceops.org
Sent: Tuesday, July 15, 2014 12:00 PM
To: voiceops at voiceops.org
Subject: VoiceOps Digest, Vol 61, Issue 10
Send VoiceOps mailing list submissions to
voiceops at voiceops.org
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
voiceops-request at voiceops.org
You can reach the person managing the list at
voiceops-owner at voiceops.org
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 <gfreeman at sungevity.com>
To: Adam Vocks <Adam.Vocks at cticomputers.com>
Cc: "<voiceops at voiceops.org>" <voiceops at voiceops.org>
Subject: Re: [VoiceOps] New Exchange 217/777
Message-ID: <723E94F6-3855-4D5C-865C-87E8DB2DA609 at sungevity.com>
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 <Adam.Vocks at 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 at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
July 15, 2014
New Exchange 217/777
by jared@compuwizz.net
I have a trouble ticket open with Hypercube. Their rate is super low for
this NPA/NXX and is the route has long PDD then fails. So I'm wondering if
once this route is fixed, if most everyone else's routes will get fixed.
I guess Level3 fixing it will help as well.
On Tue, Jul 15, 2014 at 11:10 AM, Adam Vocks <Adam.Vocks at cticomputers.com>
wrote:
> I'm really hoping Level3 is having a routing issue with our code. Some
> tried a call on level3 to us which failed. Odd things is that Level3 is
> directly connected to the Tandem we subtend. I wouldn't think Level3
> would send it off their network???
>
> Adam
>
> -----Original Message-----
> From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of Paul
> Timmins
> Sent: Tuesday, July 15, 2014 12:30 PM
> To: voiceops at voiceops.org
> Subject: Re: [VoiceOps] New Exchange 217/777
>
> What's worse really is not that you have to look at ILEC tandems out of
> area - they don't perform any route filtering, if the originating caller
> is calling out of area, it gets sent to their PIC/LPIC LD carrier.
>
> So what you really need is every IXC in the country to make sure they
> have a route to you either directly, through whatever tandem homing
> arrangements you have, or via another IXC (really common especially in
> rural areas to see a Level 3/Global Crossing hand off to
> Qwest/AT&T/Verizon for the final termination.).
>
> -Paul
>
> On 07/15/2014 10:52 AM, Adam Vocks wrote:
> > So, at the very least, I need to start looking at each of the ILEC's
> > tandems in a specific LATA?
> >
> > Adam
> >
> > -----Original Message-----
> > From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of
> > Alex Balashov
> > Sent: Tuesday, July 15, 2014 9:48 AM
> > To: voiceops at voiceops.org
> > Subject: Re: [VoiceOps] New Exchange 217/777
> >
> > On 07/15/2014 10:44 AM, Adam Vocks wrote:
> >
> >> :-)
> >>
> >> 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?
> > It would get kicked up to an ILEC tandem inside that LATA. There is
> > really no default gateway beyond that; at that point, you've already
> > exited into what the IP world would call "default route-free" or "Tier
>
> > 1" routing space.
> >
> > --
> > Alex Balashov - Principal
> > Evariste Systems LLC
> > Tel: +1-678-954-0670
> > Web: http://www.evaristesys.com/, http://www.alexbalashov.com/
> >
> > Please be kind to the English language:
> >
> > http://www.entrepreneur.com/article/232906
> > _______________________________________________
> > VoiceOps mailing list
> > VoiceOps at voiceops.org
> > https://puck.nether.net/mailman/listinfo/voiceops
> >
> > _______________________________________________
> > VoiceOps mailing list
> > VoiceOps at voiceops.org
> > https://puck.nether.net/mailman/listinfo/voiceops
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
July 15, 2014
New Exchange 217/777
by Adam.Vocks@cticomputers.com
I'm really hoping Level3 is having a routing issue with our code. Some
tried a call on level3 to us which failed. Odd things is that Level3 is
directly connected to the Tandem we subtend. I wouldn't think Level3
would send it off their network???
Adam
-----Original Message-----
From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of Paul
Timmins
Sent: Tuesday, July 15, 2014 12:30 PM
To: voiceops at voiceops.org
Subject: Re: [VoiceOps] New Exchange 217/777
What's worse really is not that you have to look at ILEC tandems out of
area - they don't perform any route filtering, if the originating caller
is calling out of area, it gets sent to their PIC/LPIC LD carrier.
So what you really need is every IXC in the country to make sure they
have a route to you either directly, through whatever tandem homing
arrangements you have, or via another IXC (really common especially in
rural areas to see a Level 3/Global Crossing hand off to
Qwest/AT&T/Verizon for the final termination.).
-Paul
On 07/15/2014 10:52 AM, Adam Vocks wrote:
> So, at the very least, I need to start looking at each of the ILEC's
> tandems in a specific LATA?
>
> Adam
>
> -----Original Message-----
> From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of
> Alex Balashov
> Sent: Tuesday, July 15, 2014 9:48 AM
> To: voiceops at voiceops.org
> Subject: Re: [VoiceOps] New Exchange 217/777
>
> On 07/15/2014 10:44 AM, Adam Vocks wrote:
>
>> :-)
>>
>> 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?
> It would get kicked up to an ILEC tandem inside that LATA. There is
> really no default gateway beyond that; at that point, you've already
> exited into what the IP world would call "default route-free" or "Tier
> 1" routing space.
>
> --
> Alex Balashov - Principal
> Evariste Systems LLC
> Tel: +1-678-954-0670
> Web: http://www.evaristesys.com/, http://www.alexbalashov.com/
>
> Please be kind to the English language:
>
> http://www.entrepreneur.com/article/232906
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops
July 15, 2014
New Exchange 217/777
by paul@timmins.net
What's worse really is not that you have to look at ILEC tandems out of
area - they don't perform any route filtering, if the originating caller
is calling out of area, it gets sent to their PIC/LPIC LD carrier.
So what you really need is every IXC in the country to make sure they
have a route to you either directly, through whatever tandem homing
arrangements you have, or via another IXC (really common especially in
rural areas to see a Level 3/Global Crossing hand off to
Qwest/AT&T/Verizon for the final termination.).
-Paul
On 07/15/2014 10:52 AM, Adam Vocks wrote:
> So, at the very least, I need to start looking at each of the ILEC's
> tandems in a specific LATA?
>
> Adam
>
> -----Original Message-----
> From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of Alex
> Balashov
> Sent: Tuesday, July 15, 2014 9:48 AM
> To: voiceops at voiceops.org
> Subject: Re: [VoiceOps] New Exchange 217/777
>
> On 07/15/2014 10:44 AM, Adam Vocks wrote:
>
>> :-)
>>
>> 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?
> It would get kicked up to an ILEC tandem inside that LATA. There is
> really no default gateway beyond that; at that point, you've already
> exited into what the IP world would call "default route-free" or "Tier
> 1" routing space.
>
> --
> Alex Balashov - Principal
> Evariste Systems LLC
> Tel: +1-678-954-0670
> Web: http://www.evaristesys.com/, http://www.alexbalashov.com/
>
> Please be kind to the English language:
>
> http://www.entrepreneur.com/article/232906
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
July 15, 2014
New Exchange 217/777
by nick.crocker@gmail.com
VZW out of Austin, TX successful call completion to the test TN
-Nick
On Tue, Jul 15, 2014 at 10:42 AM, Graham Freeman <gfreeman at sungevity.com>
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 <Adam.Vocks at 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 at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
>
July 15, 2014
New Exchange 217/777
by gfreeman@sungevity.com
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.Vocks at 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 at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
July 15, 2014
New Exchange 217/777
by Adam.Vocks@cticomputers.com
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
July 15, 2014