- VoiceOps - lists.voiceops.org

New Exchange 217/777
by Adam.Vocks＠cticomputers.com July 18, 2014

July 18, 2014

Can anyone report back to me with carriers who don?t have 217/777 in their rate deck? And, if any of you are out there who are some of these carriers, what would be a reason our code wouldn?t be in a rate deck? Thanks! Adam

1 0

Help with Incoming calls to 256-574-3285
by feby.francis＠crosstel.com July 17, 2014

July 17, 2014

All-, I need a big help, we just found out that our incoming calls to 256-912-0000 NPA_NXX/LRN is not properly delivered any more. Here is a test number I have set-up 256-574-3285 Can I get group members to call this number and report their results to me. This will help me to troubleshoot the problem more in depth. Thanks, Feby Francis

9 12

New Exchange 217/777
by Adam.Vocks＠cticomputers.com July 17, 2014

July 17, 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 >

5 15

shoretel/salesforce integration
by David.Hiers＠adp.com July 16, 2014

July 16, 2014

Hi, Does anyone have experience with the on-prem shoretel/salesforce integration? Thanks, David This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system.

1 0

New Exchange 217/777
by Jamie.Montgomery＠comporium.com July 15, 2014

July 15, 2014

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

1 0

New Exchange 217/777
by Adam.Vocks＠cticomputers.com July 15, 2014

July 15, 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

7 7

New Exchange 217/777
by Adam.Vocks＠cticomputers.com July 15, 2014

July 15, 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

1 0

New Exchange 217/777
by Adam.Vocks＠cticomputers.com July 15, 2014

July 15, 2014

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

2 1

Unallocated Number Behavior
by jared＠compuwizz.net July 11, 2014

July 11, 2014

Are there rules/guidelines on how an unallocated number should respond? We are seeing unallocated numbers on a Canadian LEC, ISP Telecom, that in the 183 response it plays back "Unallocated Number. Please check the number and try again. Unallocated Number. Please check the number and try again." then the call answers with "Hello" and plays music on hold indefinitely. A sample is 1-289-999-9348. ~Jared

4 3

PGW2200 consulting
by marylou＠backuptelecom.com July 8, 2014

July 8, 2014

Anyone know of a consultant that can help with setting up a PGW2200 to do interconnection trunking? Mary Lou Carey BackUP Telecom Consulting CLEC Consultant OFF: 615-791-9969

2 1