So we have 7-digit dialing in place for NANP destinations. The implementation is really stupid-simple: if 7 digits are dialed, take the originating number's area code and tack it on to the front of the dialed number. I am pretty sure this is how most commercial ITSPs do it (as tested also on Vonage and Packet8). But for certain areas, this doesn't properly mimic the 7-digit dialing that people who still have a POTS circuit from their LEC are used to. Take ours for example: I'm in Moscow, ID (NPA 208). We sit smack-dab on the WA/ID state border. 8 miles to the west of us is Pullman, WA (NPA 509). Both cities have the same ILEC: Frontier (f/k/a Verizon f/k/a GTE). There has been an understanding here since (I think) the mid-80s that calls between Moscow and Pullman are and will remain local. But on top of that, if you dial a Pullman NXX from Moscow or a Moscow NXX from Pullman as 7-digits, the call is patched through even though the NPA is different and even though (in some cases) both NPAs have NXXes that overlap with each other (although the corresponding NXX in the same NPA as the caller would be considered a long-distance call in all cases I can think of). The ILEC phone switch still does the "right" thing. It's been this way for YEARS, and people here are used to it. Now say I wanted to implement something like that for our customers. I know what the special exceptions are for this local market, and could probably make it work on our switch. But I only know about them because I've lived here and know the drill as a result. And I don't know how common or not this kind of thing is in other areas where you might be on the geographical edge of one's NPA(s). So the question I have is, is there some kind of central resource/authority that I can go to in order to find out what the dialing rules are for a given rate center (mandatory 10-digits/7-digits only within your own NPA/7-digits for certain local NPA-NXX outside your own NPA)? ...or is the only way to know for sure to find out from the locals? -- Nathan
http://www.nanpa.com/nas/public/npa_query_step1.do?method=resetNpaReportMode... Plus the ilec tariffs may tell you most of it. Often the state PUC will know these strange little quirks, or can tell you where they exist. I don't think they're catalogued in any one place. -Paul On 01/12/2012 04:35 PM, Nathan Anderson wrote:
So we have 7-digit dialing in place for NANP destinations. The implementation is really stupid-simple: if 7 digits are dialed, take the originating number's area code and tack it on to the front of the dialed number. I am pretty sure this is how most commercial ITSPs do it (as tested also on Vonage and Packet8).
But for certain areas, this doesn't properly mimic the 7-digit dialing that people who still have a POTS circuit from their LEC are used to. Take ours for example: I'm in Moscow, ID (NPA 208). We sit smack-dab on the WA/ID state border. 8 miles to the west of us is Pullman, WA (NPA 509). Both cities have the same ILEC: Frontier (f/k/a Verizon f/k/a GTE). There has been an understanding here since (I think) the mid-80s that calls between Moscow and Pullman are and will remain local. But on top of that, if you dial a Pullman NXX from Moscow or a Moscow NXX from Pullman as 7-digits, the call is patched through even though the NPA is different and even though (in some cases) both NPAs have NXXes that overlap with each other (although the corresponding NXX in the same NPA as the caller would be considered a long-distance call in all cases I can think of). The ILEC phone switch still does the "right" thing. It's been this way for YEARS, and people here are used to it.
Now say I wanted to implement something like that for our customers. I know what the special exceptions are for this local market, and could probably make it work on our switch. But I only know about them because I've lived here and know the drill as a result. And I don't know how common or not this kind of thing is in other areas where you might be on the geographical edge of one's NPA(s).
So the question I have is, is there some kind of central resource/authority that I can go to in order to find out what the dialing rules are for a given rate center (mandatory 10-digits/7-digits only within your own NPA/7-digits for certain local NPA-NXX outside your own NPA)? ...or is the only way to know for sure to find out from the locals?
-- Nathan _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
The NANP link that Paul posted is a good start because it at least tells you where 7-digit is allowed, etc. Not sure if the local calling data that you can get from CCMI (et al) gives you this info. You'd think, although my experience with any of those is that they are fraught with errors. The proper thing (IMO) is that everywhere go 10 digits. It's only 3 more digits, people! On Thu, Jan 12, 2012 at 5:11 PM, Paul Timmins <paul at timmins.net> wrote:
http://www.nanpa.com/nas/**public/npa_query_step1.do?** method=resetNpaReportModel<http://www.nanpa.com/nas/public/npa_query_step1.do?method=resetNpaReportMode...>
Plus the ilec tariffs may tell you most of it.
Often the state PUC will know these strange little quirks, or can tell you where they exist. I don't think they're catalogued in any one place. -Paul
On 01/12/2012 04:35 PM, Nathan Anderson wrote:
So we have 7-digit dialing in place for NANP destinations. The implementation is really stupid-simple: if 7 digits are dialed, take the originating number's area code and tack it on to the front of the dialed number. I am pretty sure this is how most commercial ITSPs do it (as tested also on Vonage and Packet8).
But for certain areas, this doesn't properly mimic the 7-digit dialing that people who still have a POTS circuit from their LEC are used to. Take ours for example: I'm in Moscow, ID (NPA 208). We sit smack-dab on the WA/ID state border. 8 miles to the west of us is Pullman, WA (NPA 509). Both cities have the same ILEC: Frontier (f/k/a Verizon f/k/a GTE). There has been an understanding here since (I think) the mid-80s that calls between Moscow and Pullman are and will remain local. But on top of that, if you dial a Pullman NXX from Moscow or a Moscow NXX from Pullman as 7-digits, the call is patched through even though the NPA is different and even though (in some cases) both NPAs have NXXes that overlap with each other (although the corresponding NXX in the same NPA as the caller would be considered a long-distance call in all cases I can think of). The ILEC phone switch still does the "right" thing. It's been this way for YEARS, and people here are used to it.
Now say I wanted to implement something like that for our customers. I know what the special exceptions are for this local market, and could probably make it work on our switch. But I only know about them because I've lived here and know the drill as a result. And I don't know how common or not this kind of thing is in other areas where you might be on the geographical edge of one's NPA(s).
So the question I have is, is there some kind of central resource/authority that I can go to in order to find out what the dialing rules are for a given rate center (mandatory 10-digits/7-digits only within your own NPA/7-digits for certain local NPA-NXX outside your own NPA)? ...or is the only way to know for sure to find out from the locals?
-- Nathan ______________________________**_________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/**mailman/listinfo/voiceops<https://puck.nether.net/mailman/listinfo/voiceops>
______________________________**_________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/**mailman/listinfo/voiceops<https://puck.nether.net/mailman/listinfo/voiceops>
Local calling areas are noted in each of the LEC tariffs by rate centers. They are based on what other rate centers you can call from a particular rate center. I live in the Franklin TN and while Nashville TN is in my EAS area and Murfreesboro TN is also in the Nashville TN EAS area, Franklin is not in the EAS area of Murfreesboro and visa versa, so you can't make the assumption that just because Franklin and Murfreesboro can both call Nashville that they are EAS to each other. To set up your switch with the correct EAS areas, you have to pull a list of NXXs that are local or EAS to that rate center and program your switch to know that if a call is made to any of these NXXs it is considered local. The best free source to find this information is in localcallingguide.com Mary Lou Carey BackUP Telecom Consulting CLEC Consultant OFF: 615-791-9969 From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of PE Sent: Thursday, January 12, 2012 4:23 PM To: voiceops at voiceops.org Subject: Re: [VoiceOps] Local calling areas & 7-digit dialing (NANP) The NANP link that Paul posted is a good start because it at least tells you where 7-digit is allowed, etc. Not sure if the local calling data that you can get from CCMI (et al) gives you this info. You'd think, although my experience with any of those is that they are fraught with errors. The proper thing (IMO) is that everywhere go 10 digits. It's only 3 more digits, people! On Thu, Jan 12, 2012 at 5:11 PM, Paul Timmins <paul at timmins.net> wrote: http://www.nanpa.com/nas/public/npa_query_step1.do?method=resetNpaReportMode l Plus the ilec tariffs may tell you most of it. Often the state PUC will know these strange little quirks, or can tell you where they exist. I don't think they're catalogued in any one place. -Paul On 01/12/2012 04:35 PM, Nathan Anderson wrote: So we have 7-digit dialing in place for NANP destinations. The implementation is really stupid-simple: if 7 digits are dialed, take the originating number's area code and tack it on to the front of the dialed number. I am pretty sure this is how most commercial ITSPs do it (as tested also on Vonage and Packet8). But for certain areas, this doesn't properly mimic the 7-digit dialing that people who still have a POTS circuit from their LEC are used to. Take ours for example: I'm in Moscow, ID (NPA 208). We sit smack-dab on the WA/ID state border. 8 miles to the west of us is Pullman, WA (NPA 509). Both cities have the same ILEC: Frontier (f/k/a Verizon f/k/a GTE). There has been an understanding here since (I think) the mid-80s that calls between Moscow and Pullman are and will remain local. But on top of that, if you dial a Pullman NXX from Moscow or a Moscow NXX from Pullman as 7-digits, the call is patched through even though the NPA is different and even though (in some cases) both NPAs have NXXes that overlap with each other (although the corresponding NXX in the same NPA as the caller would be considered a long-distance call in all cases I can think of). The ILEC phone switch still does the "right" thing. It's been this way for YEARS, and people here are used to it. Now say I wanted to implement something like that for our customers. I know what the special exceptions are for this local market, and could probably make it work on our switch. But I only know about them because I've lived here and know the drill as a result. And I don't know how common or not this kind of thing is in other areas where you might be on the geographical edge of one's NPA(s). So the question I have is, is there some kind of central resource/authority that I can go to in order to find out what the dialing rules are for a given rate center (mandatory 10-digits/7-digits only within your own NPA/7-digits for certain local NPA-NXX outside your own NPA)? ...or is the only way to know for sure to find out from the locals? -- Nathan _______________________________________________ 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
participants (4)
-
marylou＠backuptelecom.com -
nathana＠fsr.com -
paul＠timmins.net -
peeip989＠gmail.com