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
August 2023
- 15 participants
- 29 messages
TF CPR dip?
by paul@timmins.net
Follow up thought:
"But if it works like that, how does the ring-to work?"
Either the IXC that owns the CIC has a translation loaded (basically an RCF) pointing to the ring-to once it's on-net (often called wholesale switchless TF), or it passes it off via a wholesale connection with the actual terminating carrier, who then does the translation themselves and uses their own outbound LCR for the second leg (where appropriate, a lot of times the ring-to is already on-net on our switch so that leg is free and that's why the customer gets an aggressive rate on TF when they have a circuit with us for us to shoot it down).
I mention it in the context of wholesale because those who have CICs lit nationwide at this point (Inteliquent/Bandwidth/Peerless/Level (3) and the offshoots of Qwest LD and AT&T and Verizon) rarely* sell retail, except AT&T and Verizon. And unless you're tall enough to ride their ride, even those usually are wholesale through a smaller carrier who they'd rather negotiate with than you directly. (* shut up, you're the exception that proves the rule if anyone wants to bicker about that here.)
-Paul
> On Aug 9, 2023, at 11:26 PM, Paul Timmins via VoiceOps <voiceops at voiceops.org> wrote:
>
> (I am a RespOrg, entity code OG sends its love!)
>
> If you have access to TCAP queries via SS7 or SIP, you can fire the query yourself.
>
> Most records don't have a CPR, or have a very small one. if you're a RespOrg in the SOMOS database, you cannot see other people's CPRs unless the ownership is changed to you. You can see the basic fields on the CAD/PAD record.
>
> The vast majority of TFNs have either CAD/PAD that points at a single CIC/DIAL# destination.
>
> Then down from that, there's a few that might have exceptions for Canada and the Caribbean to say, use Level(3) US for domestic traffic, Level(3)'s Canadian CIC for LATA 888, and then Verizon for caribbean.
>
> Becoming more common, there will be an LCR of dozens or more CPRs that have labels in the LATA field, with different CIC/DIAL#, and a LAD record with a half dozen labels set up with dozens of CICs listed each, and a default toward a carrier.
>
> Super rare, you'll see CIC 0110 with a DIAL# that's a ring-to or a CIC that's a ring-to. It happens, but I have rarely seen it in practice in a few thousand records.
>
> -Paul
>
>
>> On Aug 9, 2023, at 11:18 PM, Nathan Anderson via VoiceOps <voiceops at voiceops.org> wrote:
>>
>> Jay,
>>
>> Thanks; yes, I understand that & thought I made that clear later on in my post.
>>
>> So to restate/rephrase:
>>
>> 1. How does direct (as opposed to call-forwarding-esque) TF origination work, exactly? As far as I can tell, all such numbers are still comprised of CPRs in the SMS/800 database, and ultimately (after consulting the table to account for originating number/LATA, time-of-day, etc.) every TF routing decision still boils down to a pairing of CIC + some valid 10-digit NANP number. Yes? So, for "direct" routed TFs, is the 10-digit destination just set to be equal to the TF number itself?
>>
>> 2. How does one look up the CPR for a given TF number? I have reason to believe that the particular TF numbers I'm interested in are not "direct-routed", but in any case, my questions about these numbers would be quickly answered if I could simply perform some kind of route look-up on the number(s). *Must* you be a RespOrg and onboarded to the SOMOS portal to be able to do this? There are all sorts of third-parties that provide LRN dip services...it's surprising to me that a similar market of services does not seem to exist for what I view as the analogue in the TF world. I really don't even care for the whole CPR: all I really want to do is basically perform the same look-up that would be made during an actual call, and know what the singular routing decision would be for that call to that TF number at that particular time of day and given a particular originating exchange.
>>
>> -- Nathan
>>
>> -----Original Message-----
>> From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of Jay Hennigan via VoiceOps
>> Sent: Wednesday, August 9, 2023 8:04 PM
>> To: voiceops at voiceops.org
>> Subject: Re: [VoiceOps] TF CPR dip?
>>
>> On 8/9/23 19:54, Nathan Anderson via VoiceOps wrote:
>>
>>> Is this even a thing? Is it possible to do a look-up on a TF number and know ultimately what local number a call to that TF number is going to be sent to?
>>
>> It may not go to a local number at all. It can terminate on an
>> old-school toll trunk (PRI) or be delivered by SIP as the native
>> toll-free number.
>>
>> "Switched" TF is translated to a local number by the provider and
>> delivered over the PSTN/VoIP on that local number. "Dedicated" TF is
>> delivered directly to the customer natively as the TF number.
>>
>> More complex schemes can be set up with routing based on originating
>> NPA/NXX, time of day, etc. as well.
>>
>> --
>> Jay Hennigan - jay at west.net
>> Network Engineering - CCIE #7880
>> 503 897-8550 - WB6RDV
>>
>> _______________________________________________
>> 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
>
Aug. 10, 2023
TF CPR dip?
by paul@timmins.net
(I am a RespOrg, entity code OG sends its love!)
If you have access to TCAP queries via SS7 or SIP, you can fire the query yourself.
Most records don't have a CPR, or have a very small one. if you're a RespOrg in the SOMOS database, you cannot see other people's CPRs unless the ownership is changed to you. You can see the basic fields on the CAD/PAD record.
The vast majority of TFNs have either CAD/PAD that points at a single CIC/DIAL# destination.
Then down from that, there's a few that might have exceptions for Canada and the Caribbean to say, use Level(3) US for domestic traffic, Level(3)'s Canadian CIC for LATA 888, and then Verizon for caribbean.
Becoming more common, there will be an LCR of dozens or more CPRs that have labels in the LATA field, with different CIC/DIAL#, and a LAD record with a half dozen labels set up with dozens of CICs listed each, and a default toward a carrier.
Super rare, you'll see CIC 0110 with a DIAL# that's a ring-to or a CIC that's a ring-to. It happens, but I have rarely seen it in practice in a few thousand records.
-Paul
> On Aug 9, 2023, at 11:18 PM, Nathan Anderson via VoiceOps <voiceops at voiceops.org> wrote:
>
> Jay,
>
> Thanks; yes, I understand that & thought I made that clear later on in my post.
>
> So to restate/rephrase:
>
> 1. How does direct (as opposed to call-forwarding-esque) TF origination work, exactly? As far as I can tell, all such numbers are still comprised of CPRs in the SMS/800 database, and ultimately (after consulting the table to account for originating number/LATA, time-of-day, etc.) every TF routing decision still boils down to a pairing of CIC + some valid 10-digit NANP number. Yes? So, for "direct" routed TFs, is the 10-digit destination just set to be equal to the TF number itself?
>
> 2. How does one look up the CPR for a given TF number? I have reason to believe that the particular TF numbers I'm interested in are not "direct-routed", but in any case, my questions about these numbers would be quickly answered if I could simply perform some kind of route look-up on the number(s). *Must* you be a RespOrg and onboarded to the SOMOS portal to be able to do this? There are all sorts of third-parties that provide LRN dip services...it's surprising to me that a similar market of services does not seem to exist for what I view as the analogue in the TF world. I really don't even care for the whole CPR: all I really want to do is basically perform the same look-up that would be made during an actual call, and know what the singular routing decision would be for that call to that TF number at that particular time of day and given a particular originating exchange.
>
> -- Nathan
>
> -----Original Message-----
> From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of Jay Hennigan via VoiceOps
> Sent: Wednesday, August 9, 2023 8:04 PM
> To: voiceops at voiceops.org
> Subject: Re: [VoiceOps] TF CPR dip?
>
> On 8/9/23 19:54, Nathan Anderson via VoiceOps wrote:
>
>> Is this even a thing? Is it possible to do a look-up on a TF number and know ultimately what local number a call to that TF number is going to be sent to?
>
> It may not go to a local number at all. It can terminate on an
> old-school toll trunk (PRI) or be delivered by SIP as the native
> toll-free number.
>
> "Switched" TF is translated to a local number by the provider and
> delivered over the PSTN/VoIP on that local number. "Dedicated" TF is
> delivered directly to the customer natively as the TF number.
>
> More complex schemes can be set up with routing based on originating
> NPA/NXX, time of day, etc. as well.
>
> --
> Jay Hennigan - jay at west.net
> Network Engineering - CCIE #7880
> 503 897-8550 - WB6RDV
>
> _______________________________________________
> 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
>
Aug. 10, 2023
TF CPR dip?
by nathana@fsr.com
Jay,
Thanks; yes, I understand that & thought I made that clear later on in my post.
So to restate/rephrase:
1. How does direct (as opposed to call-forwarding-esque) TF origination work, exactly? As far as I can tell, all such numbers are still comprised of CPRs in the SMS/800 database, and ultimately (after consulting the table to account for originating number/LATA, time-of-day, etc.) every TF routing decision still boils down to a pairing of CIC + some valid 10-digit NANP number. Yes? So, for "direct" routed TFs, is the 10-digit destination just set to be equal to the TF number itself?
2. How does one look up the CPR for a given TF number? I have reason to believe that the particular TF numbers I'm interested in are not "direct-routed", but in any case, my questions about these numbers would be quickly answered if I could simply perform some kind of route look-up on the number(s). *Must* you be a RespOrg and onboarded to the SOMOS portal to be able to do this? There are all sorts of third-parties that provide LRN dip services...it's surprising to me that a similar market of services does not seem to exist for what I view as the analogue in the TF world. I really don't even care for the whole CPR: all I really want to do is basically perform the same look-up that would be made during an actual call, and know what the singular routing decision would be for that call to that TF number at that particular time of day and given a particular originating exchange.
-- Nathan
-----Original Message-----
From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of Jay Hennigan via VoiceOps
Sent: Wednesday, August 9, 2023 8:04 PM
To: voiceops at voiceops.org
Subject: Re: [VoiceOps] TF CPR dip?
On 8/9/23 19:54, Nathan Anderson via VoiceOps wrote:
> Is this even a thing? Is it possible to do a look-up on a TF number and know ultimately what local number a call to that TF number is going to be sent to?
It may not go to a local number at all. It can terminate on an
old-school toll trunk (PRI) or be delivered by SIP as the native
toll-free number.
"Switched" TF is translated to a local number by the provider and
delivered over the PSTN/VoIP on that local number. "Dedicated" TF is
delivered directly to the customer natively as the TF number.
More complex schemes can be set up with routing based on originating
NPA/NXX, time of day, etc. as well.
--
Jay Hennigan - jay at west.net
Network Engineering - CCIE #7880
503 897-8550 - WB6RDV
_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops
Aug. 10, 2023
TF CPR dip?
by jay@west.net
On 8/9/23 19:54, Nathan Anderson via VoiceOps wrote:
> Is this even a thing? Is it possible to do a look-up on a TF number and know ultimately what local number a call to that TF number is going to be sent to?
It may not go to a local number at all. It can terminate on an
old-school toll trunk (PRI) or be delivered by SIP as the native
toll-free number.
"Switched" TF is translated to a local number by the provider and
delivered over the PSTN/VoIP on that local number. "Dedicated" TF is
delivered directly to the customer natively as the TF number.
More complex schemes can be set up with routing based on originating
NPA/NXX, time of day, etc. as well.
--
Jay Hennigan - jay at west.net
Network Engineering - CCIE #7880
503 897-8550 - WB6RDV
Aug. 10, 2023
TF CPR dip?
by nathana@fsr.com
So, I'm not a RespOrg (though I've considered it), thus have no access to SOMOS, and know extremely little about TF call routing; don't hurt me...
Is this even a thing? Is it possible to do a look-up on a TF number and know ultimately what local number a call to that TF number is going to be sent to?
>From the little Googling I've done so far, it's not clear to me if a CPR record actually contains the final destination (perhaps it does *sometimes*), or if the "destination" typically just represents a number belonging to the IXC that will finally complete the call (similar to LRN for routing a ported local number to the right switch). I'm guessing the latter? in which case it's impossible to know what the actual final destination of the call is just by consulting SMS/800...the destination would ultimately be proprietary information that only the long-distance provider responsible for those calls could know...?
(I'm guessing this is made even messier today by the existence of direct SIP TF origination, in which case there is no true "local" number that the TF is being forwarded to. Knowing that this is a thing is driving some of my assumptions here. Though perhaps I'm misunderstanding how this works under-the-hood...maybe a CPR does always contain the actual destination #, and what's happening in the case of direct SIP origination is that the CIC points at the SIP provider, and the "destination" is set to be the same as the actual TF number itself? Does that work / are you allowed to do that?)
Though I'd love to understand all of this more in-depth as a whole, the particular thing driving my query at the moment is that a prospective customer -- who is a local branch office of a national firm -- is asking us about issues with call quality and call completion that they have been experiencing when calling their HQ via the HQ's TF numbers (there are several, each of which apparently route to different departments at different destinations), when making those calls via ILEC, where ILEC is also their LD provider. They do not experience the same issues when calling those same TFs via mobile. They have tried to work with ILEC to try to resolve these issues to no end, and want to be assured that either they would not experience the same problem when sending those calls through us, or that if they do, we could (unlike the ILEC, apparently) actually work to solve the underlying issue / route around it. If we do run into the issue to these particular numbers, short of opening tickets with whomever we term the TF calls through, one thought I had would be to have end-user bypass the TF#s entirely, and to try direct-dialing the local number that they point to instead. The question is how to determine what those destination numbers actually are.
Thanks,
-- Nathan
Aug. 10, 2023
Dominican Republic LERG Data
by paul@timmins.net
Because all unassigned prefixes go to the local ILEC. Things don't have to be in the LERG to work when things work that way.
> On Aug 9, 2023, at 7:15 PM, Peter Beckman via VoiceOps <voiceops at voiceops.org> wrote:
>
> Yet I called them! How would that be possible if it was a typo?
>
>
> On Wed, 9 Aug 2023, Mary Lou Carey wrote:
>
>> I have direct access to BIRRDS and pulled all the blocks assigned from 849-4 NPA.There is nothing assigned to 849-472.
>>
>> When I pulled up a report on the NXXs from 849 in Local Calling Guide, I found lots of blocks from 849 NPA but 849-472 doesn't show up there either. I would say it probably is not assigned to anyone yet or they have a typo.
>>
>> MARY LOU CAREY
>> BackUP Telecom Consulting
>> Office: 615-791-9969
>> Cell: 615-796-1111
>>
>> On 2023-08-09 03:53 PM, Peter Beckman wrote:
>>> I checked there, +1 849 472 does not seem to show up.
>>> +1 829 472 and +1 809 472 DO show up though.
>>> It does show up in the PDF from INDOTEL, but trying to find the carrier of
>>> record for the specific DID is proving difficult.
>>> Is +1 849 472 NOT in the actual currently published LERG?
>>> I was able to call the full DID just now and spoke to the customer in DO,
>>> so it is clear to me that regardless of the LERG status, the number is
>>> functioning. Maybe there is some update or delay in getting the LERG
>>> updated? Usually I find the LERG and NANPA to be FAR ahead of the ball in
>>> announcing new NXX or NPA provisioning before they even go live.
>>> Beckman
>>> On Wed, 9 Aug 2023, Mary Lou Carey wrote:
>>>> By the way....you can find the NXX assignments for LATA 828 on localcallingguide.com. Its free and pulls information from NANPA.
>>>> MARY LOU CAREY
>>>> BackUP Telecom Consulting
>>>> Office: 615-791-9969
>>>> Cell: 615-796-1111
>>>> On 2023-08-07 02:24 PM, Peter Beckman via VoiceOps wrote:
>>>>> Customer states their DO Number is active with Claro.
>>>>> Twilio states that it is not active with any carrier.
>>>>> My LERG sources only have US and Canada NPANXX data.
>>>>> Where would I get Dominican Republic LERG data (area codes 809, 829, 849)
>>>>> without paying hundreds or thousands of dollars? Any lookup services?
>>>>> Beckman
>>>>> PS -- if you have access, email me privately and I'll send the number to
>>>>> check.
>>>>>
>>>>> ---------------------------------------------------------------------------
>>>>> Peter Beckman Internet Guy
>>>>> beckman at angryox.com https://www.angryox.com/
>>>>> ---------------------------------------------------------------------------
>>>>> _______________________________________________
>>>>> VoiceOps mailing list
>>>>> VoiceOps at voiceops.org
>>>>> https://puck.nether.net/mailman/listinfo/voiceops
>>> ---------------------------------------------------------------------------
>>> Peter Beckman Internet Guy
>>> beckman at angryox.com https://www.angryox.com/
>>> ---------------------------------------------------------------------------
>>
>
> ---------------------------------------------------------------------------
> Peter Beckman Internet Guy
> beckman at angryox.com <mailto:beckman at angryox.com> https://www.angryox.com/
> ---------------------------------------------------------------------------
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org <mailto:VoiceOps at voiceops.org>
> https://puck.nether.net/mailman/listinfo/voiceops
Aug. 10, 2023
Dominican Republic LERG Data
by marylou@backuptelecom.com
I have no idea....just saying it's not in BIRRDS which is the database
that NANPA enters all the assigned NXXs in and the one that the LERG
information comes from.
MARY LOU CAREY
BackUP Telecom Consulting
Office: 615-791-9969
Cell: 615-796-1111
On 2023-08-09 06:15 PM, Peter Beckman wrote:
> Yet I called them! How would that be possible if it was a typo?
>
>
> On Wed, 9 Aug 2023, Mary Lou Carey wrote:
>
>> I have direct access to BIRRDS and pulled all the blocks assigned from
>> 849-4 NPA.There is nothing assigned to 849-472.
>>
>> When I pulled up a report on the NXXs from 849 in Local Calling Guide,
>> I found lots of blocks from 849 NPA but 849-472 doesn't show up there
>> either. I would say it probably is not assigned to anyone yet or they
>> have a typo.
>>
>> MARY LOU CAREY
>> BackUP Telecom Consulting
>> Office: 615-791-9969
>> Cell: 615-796-1111
>>
>> On 2023-08-09 03:53 PM, Peter Beckman wrote:
>>> I checked there, +1 849 472 does not seem to show up.
>>>
>>> +1 829 472 and +1 809 472 DO show up though.
>>>
>>> It does show up in the PDF from INDOTEL, but trying to find the
>>> carrier of
>>> record for the specific DID is proving difficult.
>>>
>>> Is +1 849 472 NOT in the actual currently published LERG?
>>>
>>> I was able to call the full DID just now and spoke to the customer in
>>> DO,
>>> so it is clear to me that regardless of the LERG status, the number
>>> is
>>> functioning. Maybe there is some update or delay in getting the LERG
>>> updated? Usually I find the LERG and NANPA to be FAR ahead of the
>>> ball in
>>> announcing new NXX or NPA provisioning before they even go live.
>>>
>>> Beckman
>>>
>>> On Wed, 9 Aug 2023, Mary Lou Carey wrote:
>>>
>>>> By the way....you can find the NXX assignments for LATA 828 on
>>>> localcallingguide.com. Its free and pulls information from NANPA.
>>>>
>>>> MARY LOU CAREY
>>>> BackUP Telecom Consulting
>>>> Office: 615-791-9969
>>>> Cell: 615-796-1111
>>>>
>>>> On 2023-08-07 02:24 PM, Peter Beckman via VoiceOps wrote:
>>>>> Customer states their DO Number is active with Claro.
>>>>>
>>>>> Twilio states that it is not active with any carrier.
>>>>>
>>>>> My LERG sources only have US and Canada NPANXX data.
>>>>>
>>>>> Where would I get Dominican Republic LERG data (area codes 809,
>>>>> 829, 849)
>>>>> without paying hundreds or thousands of dollars? Any lookup
>>>>> services?
>>>>>
>>>>> Beckman
>>>>>
>>>>> PS -- if you have access, email me privately and I'll send the
>>>>> number to
>>>>> check.
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------------
>>>>> Peter Beckman
>>>>> Internet Guy
>>>>> beckman at angryox.com https://www.angryox.com/
>>>>>
>>>>> ---------------------------------------------------------------------------
>>>>> _______________________________________________
>>>>> VoiceOps mailing list
>>>>> VoiceOps at voiceops.org
>>>>> https://puck.nether.net/mailman/listinfo/voiceops
>>>>
>>>
>>> ---------------------------------------------------------------------------
>>> Peter Beckman
>>> Internet Guy
>>> beckman at angryox.com
>>> https://www.angryox.com/
>>> ---------------------------------------------------------------------------
>>
>
> ---------------------------------------------------------------------------
> Peter Beckman Internet
> Guy
> beckman at angryox.com
> https://www.angryox.com/
> ---------------------------------------------------------------------------
Aug. 9, 2023
Dominican Republic LERG Data
by beckman@angryox.com
Yet I called them! How would that be possible if it was a typo?
On Wed, 9 Aug 2023, Mary Lou Carey wrote:
> I have direct access to BIRRDS and pulled all the blocks assigned from 849-4
> NPA.There is nothing assigned to 849-472.
>
> When I pulled up a report on the NXXs from 849 in Local Calling Guide, I
> found lots of blocks from 849 NPA but 849-472 doesn't show up there either. I
> would say it probably is not assigned to anyone yet or they have a typo.
>
> MARY LOU CAREY
> BackUP Telecom Consulting
> Office: 615-791-9969
> Cell: 615-796-1111
>
> On 2023-08-09 03:53 PM, Peter Beckman wrote:
>> I checked there, +1 849 472 does not seem to show up.
>>
>> +1 829 472 and +1 809 472 DO show up though.
>>
>> It does show up in the PDF from INDOTEL, but trying to find the carrier of
>> record for the specific DID is proving difficult.
>>
>> Is +1 849 472 NOT in the actual currently published LERG?
>>
>> I was able to call the full DID just now and spoke to the customer in DO,
>> so it is clear to me that regardless of the LERG status, the number is
>> functioning. Maybe there is some update or delay in getting the LERG
>> updated? Usually I find the LERG and NANPA to be FAR ahead of the ball in
>> announcing new NXX or NPA provisioning before they even go live.
>>
>> Beckman
>>
>> On Wed, 9 Aug 2023, Mary Lou Carey wrote:
>>
>>> By the way....you can find the NXX assignments for LATA 828 on
>>> localcallingguide.com. Its free and pulls information from NANPA.
>>>
>>> MARY LOU CAREY
>>> BackUP Telecom Consulting
>>> Office: 615-791-9969
>>> Cell: 615-796-1111
>>>
>>> On 2023-08-07 02:24 PM, Peter Beckman via VoiceOps wrote:
>>>> Customer states their DO Number is active with Claro.
>>>>
>>>> Twilio states that it is not active with any carrier.
>>>>
>>>> My LERG sources only have US and Canada NPANXX data.
>>>>
>>>> Where would I get Dominican Republic LERG data (area codes 809, 829, 849)
>>>> without paying hundreds or thousands of dollars? Any lookup services?
>>>>
>>>> Beckman
>>>>
>>>> PS -- if you have access, email me privately and I'll send the number to
>>>> check.
>>>>
>>>>
>>>> ---------------------------------------------------------------------------
>>>> Peter Beckman Internet
>>>> Guy
>>>> beckman at angryox.com
>>>> https://www.angryox.com/
>>>>
>>>> ---------------------------------------------------------------------------
>>>> _______________________________________________
>>>> VoiceOps mailing list
>>>> VoiceOps at voiceops.org
>>>> https://puck.nether.net/mailman/listinfo/voiceops
>>>
>>
>> ---------------------------------------------------------------------------
>> Peter Beckman Internet Guy
>> beckman at angryox.com https://www.angryox.com/
>> ---------------------------------------------------------------------------
>
---------------------------------------------------------------------------
Peter Beckman Internet Guy
beckman at angryox.com https://www.angryox.com/
---------------------------------------------------------------------------
Aug. 9, 2023
Dominican Republic LERG Data
by marylou@backuptelecom.com
I have direct access to BIRRDS and pulled all the blocks assigned from
849-4 NPA.There is nothing assigned to 849-472.
When I pulled up a report on the NXXs from 849 in Local Calling Guide, I
found lots of blocks from 849 NPA but 849-472 doesn't show up there
either. I would say it probably is not assigned to anyone yet or they
have a typo.
MARY LOU CAREY
BackUP Telecom Consulting
Office: 615-791-9969
Cell: 615-796-1111
On 2023-08-09 03:53 PM, Peter Beckman wrote:
> I checked there, +1 849 472 does not seem to show up.
>
> +1 829 472 and +1 809 472 DO show up though.
>
> It does show up in the PDF from INDOTEL, but trying to find the carrier
> of
> record for the specific DID is proving difficult.
>
> Is +1 849 472 NOT in the actual currently published LERG?
>
> I was able to call the full DID just now and spoke to the customer in
> DO,
> so it is clear to me that regardless of the LERG status, the number is
> functioning. Maybe there is some update or delay in getting the LERG
> updated? Usually I find the LERG and NANPA to be FAR ahead of the ball
> in
> announcing new NXX or NPA provisioning before they even go live.
>
> Beckman
>
> On Wed, 9 Aug 2023, Mary Lou Carey wrote:
>
>> By the way....you can find the NXX assignments for LATA 828 on
>> localcallingguide.com. Its free and pulls information from NANPA.
>>
>> MARY LOU CAREY
>> BackUP Telecom Consulting
>> Office: 615-791-9969
>> Cell: 615-796-1111
>>
>> On 2023-08-07 02:24 PM, Peter Beckman via VoiceOps wrote:
>>> Customer states their DO Number is active with Claro.
>>>
>>> Twilio states that it is not active with any carrier.
>>>
>>> My LERG sources only have US and Canada NPANXX data.
>>>
>>> Where would I get Dominican Republic LERG data (area codes 809, 829,
>>> 849)
>>> without paying hundreds or thousands of dollars? Any lookup services?
>>>
>>> Beckman
>>>
>>> PS -- if you have access, email me privately and I'll send the number
>>> to
>>> check.
>>>
>>> ---------------------------------------------------------------------------
>>> Peter Beckman
>>> Internet Guy
>>> beckman at angryox.com
>>> https://www.angryox.com/
>>> ---------------------------------------------------------------------------
>>> _______________________________________________
>>> VoiceOps mailing list
>>> VoiceOps at voiceops.org
>>> https://puck.nether.net/mailman/listinfo/voiceops
>>
>
> ---------------------------------------------------------------------------
> Peter Beckman Internet
> Guy
> beckman at angryox.com
> https://www.angryox.com/
> ---------------------------------------------------------------------------
Aug. 9, 2023
Dominican Republic LERG Data
by beckman@angryox.com
I checked there, +1 849 472 does not seem to show up.
+1 829 472 and +1 809 472 DO show up though.
It does show up in the PDF from INDOTEL, but trying to find the carrier of
record for the specific DID is proving difficult.
Is +1 849 472 NOT in the actual currently published LERG?
I was able to call the full DID just now and spoke to the customer in DO,
so it is clear to me that regardless of the LERG status, the number is
functioning. Maybe there is some update or delay in getting the LERG
updated? Usually I find the LERG and NANPA to be FAR ahead of the ball in
announcing new NXX or NPA provisioning before they even go live.
Beckman
On Wed, 9 Aug 2023, Mary Lou Carey wrote:
> By the way....you can find the NXX assignments for LATA 828 on
> localcallingguide.com. Its free and pulls information from NANPA.
>
> MARY LOU CAREY
> BackUP Telecom Consulting
> Office: 615-791-9969
> Cell: 615-796-1111
>
> On 2023-08-07 02:24 PM, Peter Beckman via VoiceOps wrote:
>> Customer states their DO Number is active with Claro.
>>
>> Twilio states that it is not active with any carrier.
>>
>> My LERG sources only have US and Canada NPANXX data.
>>
>> Where would I get Dominican Republic LERG data (area codes 809, 829, 849)
>> without paying hundreds or thousands of dollars? Any lookup services?
>>
>> Beckman
>>
>> PS -- if you have access, email me privately and I'll send the number to
>> check.
>>
>> ---------------------------------------------------------------------------
>> Peter Beckman Internet Guy
>> beckman at angryox.com https://www.angryox.com/
>> ---------------------------------------------------------------------------
>> _______________________________________________
>> VoiceOps mailing list
>> VoiceOps at voiceops.org
>> https://puck.nether.net/mailman/listinfo/voiceops
>
---------------------------------------------------------------------------
Peter Beckman Internet Guy
beckman at angryox.com https://www.angryox.com/
---------------------------------------------------------------------------
Aug. 9, 2023