Can't Port from a Particular Rate Center
I first asked on a list much more narrow in scope, but failing to get sufficient data points, I've expanded my scope. Assuming the number isn't held by someone exempt from porting, what would prevent someone from being able to port a number from a particular rate center in a LATA they have coverage in? We picked up a particular carrier for our out-of-area needs and the first thing we throw at them in a LATA we know they have coverage in, they can't do. They have a non-useful reason why. It doesn't appear to have moved to a state where they contacted the losing provider as the response was very fast, so my provider rejected the port, not theirs. When I started at this company (where we do our own porting), I made sure to port a bunch of numbers from all over our LATA to see what would happen. All successful. That seems to indicate that it doesn't matter which xLEC or tandem currently serves that number, it can move elsewhere. ----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com Midwest-IX http://www.midwest-ix.com
Coming from another one of their customers? Shane Ronan
On Jun 9, 2021, at 4:32 PM, Mike Hammett <nanog@ics-il.net> wrote:
I first asked on a list much more narrow in scope, but failing to get sufficient data points, I've expanded my scope.
Assuming the number isn't held by someone exempt from porting, what would prevent someone from being able to port a number from a particular rate center in a LATA they have coverage in?
We picked up a particular carrier for our out-of-area needs and the first thing we throw at them in a LATA we know they have coverage in, they can't do. They have a non-useful reason why. It doesn't appear to have moved to a state where they contacted the losing provider as the response was very fast, so my provider rejected the port, not theirs.
When I started at this company (where we do our own porting), I made sure to port a bunch of numbers from all over our LATA to see what would happen. All successful. That seems to indicate that it doesn't matter which xLEC or tandem currently serves that number, it can move elsewhere.
----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com
Midwest-IX http://www.midwest-ix.com
Naw, the losing carrier is a major cable company. ----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com Midwest-IX http://www.midwest-ix.com ----- Original Message ----- From: sronan@ronan-online.com To: "Mike Hammett" <nanog@ics-il.net> Cc: "NANOG Operators' Group" <nanog@nanog.org> Sent: Wednesday, June 9, 2021 3:46:03 PM Subject: Re: Can't Port from a Particular Rate Center Coming from another one of their customers? Shane Ronan On Jun 9, 2021, at 4:32 PM, Mike Hammett <nanog@ics-il.net> wrote: <blockquote> I first asked on a list much more narrow in scope, but failing to get sufficient data points, I've expanded my scope. Assuming the number isn't held by someone exempt from porting, what would prevent someone from being able to port a number from a particular rate center in a LATA they have coverage in? We picked up a particular carrier for our out-of-area needs and the first thing we throw at them in a LATA we know they have coverage in, they can't do. They have a non-useful reason why. It doesn't appear to have moved to a state where they contacted the losing provider as the response was very fast, so my provider rejected the port, not theirs. When I started at this company (where we do our own porting), I made sure to port a bunch of numbers from all over our LATA to see what would happen. All successful. That seems to indicate that it doesn't matter which xLEC or tandem currently serves that number, it can move elsewhere. ----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com Midwest-IX http://www.midwest-ix.com </blockquote>
I had this happen to me recently. Customer came in with a number that had very little coverage, but our carrier had a 1,000 block in the same ratecenter, so we held out some hope. Once we dug into it, the 1,000 block was designated for a different "service offering" with the carrier. They were not offering portability in that Ratecenter, despite having coverage, or even hardware or leased hardware there. So we had to send the customer off. There really were only about 5 carriers serving the Ratecenter, 3 of them wireless, one very local, and our carrier. If your carrier decides not to port a number, even when they seem to be present in the ratecenter in question, they are not required by any law or rule to port, AFAIK. If a company will port in, the other carrier must (IMHO) port out. If not, then you can't port. There may be some subtleties to that, but this is my understanding. Fun! Beckman On Wed, 9 Jun 2021, Mike Hammett wrote:
I first asked on a list much more narrow in scope, but failing to get sufficient data points, I've expanded my scope.
Assuming the number isn't held by someone exempt from porting, what would prevent someone from being able to port a number from a particular rate center in a LATA they have coverage in?
We picked up a particular carrier for our out-of-area needs and the first thing we throw at them in a LATA we know they have coverage in, they can't do. They have a non-useful reason why. It doesn't appear to have moved to a state where they contacted the losing provider as the response was very fast, so my provider rejected the port, not theirs.
When I started at this company (where we do our own porting), I made sure to port a bunch of numbers from all over our LATA to see what would happen. All successful. That seems to indicate that it doesn't matter which xLEC or tandem currently serves that number, it can move elsewhere.
----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com
Midwest-IX http://www.midwest-ix.com
--------------------------------------------------------------------------- Peter Beckman Internet Guy beckman@angryox.com http://www.angryox.com/ ---------------------------------------------------------------------------
If there's wireless you can always try porting to wireless. We do that in a few rate centers ________________________________ Ray Orsini Chief Executive Officer OIT, LLC 305.967.6756 x1009 | 305.571.6272 ray@oit.co | www.oit.co oit.co/ray Headed to ASCII: Ohio on June 16th - 17th? Come meet the OITVOIP family! Find your city and register for FREE using code "OIT" https://go.oit.co/ASCII2021 From: NANOG <nanog-bounces+ray=oit.co@nanog.org> on behalf of Peter Beckman <beckman@angryox.com> Sent: Thursday, June 10, 2021 12:33:45 AM To: Mike Hammett <nanog@ics-il.net> Cc: NANOG Operators' Group <nanog@nanog.org> Subject: EXTERNAL: Re: Can't Port from a Particular Rate Center CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. If you are unsure, please forward this email to the CSE team for review. I had this happen to me recently. Customer came in with a number that had very little coverage, but our carrier had a 1,000 block in the same ratecenter, so we held out some hope. Once we dug into it, the 1,000 block was designated for a different "service offering" with the carrier. They were not offering portability in that Ratecenter, despite having coverage, or even hardware or leased hardware there. So we had to send the customer off. There really were only about 5 carriers serving the Ratecenter, 3 of them wireless, one very local, and our carrier. If your carrier decides not to port a number, even when they seem to be present in the ratecenter in question, they are not required by any law or rule to port, AFAIK. If a company will port in, the other carrier must (IMHO) port out. If not, then you can't port. There may be some subtleties to that, but this is my understanding. Fun! Beckman On Wed, 9 Jun 2021, Mike Hammett wrote:
I first asked on a list much more narrow in scope, but failing to get sufficient data points, I've expanded my scope.
Assuming the number isn't held by someone exempt from porting, what would prevent someone from being able to port a number from a particular rate center in a LATA they have coverage in?
We picked up a particular carrier for our out-of-area needs and the first thing we throw at them in a LATA we know they have coverage in, they can't do. They have a non-useful reason why. It doesn't appear to have moved to a state where they contacted the losing provider as the response was very fast, so my provider rejected the port, not theirs.
When I started at this company (where we do our own porting), I made sure to port a bunch of numbers from all over our LATA to see what would happen. All successful. That seems to indicate that it doesn't matter which xLEC or tandem currently serves that number, it can move elsewhere.
----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com
Midwest-IX http://www.midwest-ix.com
--------------------------------------------------------------------------- Peter Beckman Internet Guy beckman@angryox.com http://www.angryox.com/ ---------------------------------------------------------------------------
Another trick I've used is to use a separate number and forward the old number to the new. Set the caller ID to the original number, test 911. You may want to run the 911 with the new number instead though. With this setup, you can try porting again down the road, but at least you have a solution in the current time. On 6/10/21 7:32 AM, Ray Orsini wrote:
If there's wireless you can always try porting to wireless. We do that in a few rate centers OIT Website <https://www.oit.co/> Ray Orsini Chief Executive Officer OIT, LLC
*305.967.6756 x1009* <tel:305.967.6756%20x1009> | *305.571.6272* <fax:305.571.6272>
*ray@oit.co* <mailto:ray@oit.co> | https://www.oit.co <https://www.oit.co/> * www.oit.co* <https://www.oit.co/>
oit.co/ray
Facebook <https://go.oit.co/facebook>
LinkedIn <https://go.oit.co/linkedin>
Twitter <https://go.oit.co/twitter>
YouTube <https://go.oit.co/youtube>
*Headed to ASCII: Ohio on June 16th - 17th?Come meet the OITVOIP family! Find your city and register for FREE using code "OIT" https://go.oit.co/ASCII2021* <https://go.oit.co/ASCII2021>
------------------------------------------------------------------------ *From:* NANOG <nanog-bounces+ray=oit.co@nanog.org> on behalf of Peter Beckman <beckman@angryox.com> *Sent:* Thursday, June 10, 2021 12:33:45 AM *To:* Mike Hammett <nanog@ics-il.net> *Cc:* NANOG Operators' Group <nanog@nanog.org> *Subject:* EXTERNAL: Re: Can't Port from a Particular Rate Center CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. If you are unsure, please forward this email to the CSE team for review.
I had this happen to me recently.
Customer came in with a number that had very little coverage, but our carrier had a 1,000 block in the same ratecenter, so we held out some hope.
Once we dug into it, the 1,000 block was designated for a different "service offering" with the carrier. They were not offering portability in that Ratecenter, despite having coverage, or even hardware or leased hardware there.
So we had to send the customer off. There really were only about 5 carriers serving the Ratecenter, 3 of them wireless, one very local, and our carrier.
If your carrier decides not to port a number, even when they seem to be present in the ratecenter in question, they are not required by any law or rule to port, AFAIK.
If a company will port in, the other carrier must (IMHO) port out. If not, then you can't port. There may be some subtleties to that, but this is my understanding.
Fun!
Beckman
On Wed, 9 Jun 2021, Mike Hammett wrote:
I first asked on a list much more narrow in scope, but failing to get sufficient data points, I've expanded my scope.
Assuming the number isn't held by someone exempt from porting, what would prevent someone from being able to port a number from a particular rate center in a LATA they have coverage in?
We picked up a particular carrier for our out-of-area needs and the first thing we throw at them in a LATA we know they have coverage in, they can't do. They have a non-useful reason why. It doesn't appear to have moved to a state where they contacted the losing provider as the response was very fast, so my provider rejected the port, not theirs.
When I started at this company (where we do our own porting), I made sure to port a bunch of numbers from all over our LATA to see what would happen. All successful. That seems to indicate that it doesn't matter which xLEC or tandem currently serves that number, it can move elsewhere.
----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com <http://www.ics-il.com>
Midwest-IX http://www.midwest-ix.com <http://www.midwest-ix.com>
--------------------------------------------------------------------------- Peter Beckman Internet Guy beckman@angryox.com http://www.angryox.com/ <http://www.angryox.com/> ---------------------------------------------------------------------------
participants (5)
-
Jason Canady -
Mike Hammett -
Peter Beckman -
Ray Orsini -
sronan＠ronan-online.com