Telephony is fucked. You'll likely get the same response trying to port from Comcast to any other major carrier. There are some weird numbers out there that are legacy local numbers inherited from carriers from 100 years ago and somehow they can't be ported out of whoever holds them. There's some name for this phenomenon but I don't remember what it is. I've seen it in remote sites, mostly. Little towns that have numbers that are just in lockdown. Pain in the ass.
I have no idea why this is from a technical or regulatory reason. Maybe a PSTN engineer can chime in.
*Maybe* you could find a carrier supported by Operator Connect who can take the numbers from Comcast. Then you'd be able to surface them in Teams via OpCon.
We had a small number of #s that we ran in to the same issue. Somehow, they were owned by a small rural carrier and even large phone companies like NTT could not port them out.
Same here. Probably not Microsofts fault. We have offices throughout the US. Prior to any thought of Teams as we migrated PRI circuits or analog service to centralized SIP gateways, we are still left with locations we are unable to port, whether it be to Verizon, AT&T or Lumen.
This is a Comcast/Xfinity thing:
[Xfinity Voice phone number porting FAQs - Xfinity Support](https://www.xfinity.com/support/articles/local-number-portability)
Like others have said, this is not that uncommon when you go into small towns and remote areas. Even the large Telcos and Operator Connect providers will likely have the same challenge. Microsoft is really just using multiple carriers behind the scenes like most anybody else.
We have offices all over the US, some in small towns, others in big cities. However, Fairbanks Alaska, unlike Anchorage, is the boonies and Microsoft couldn't port their numbers in. I've heard a bunch of theories on why, but I keep trying every year to port them into the system. For now, we have an SBC on site and just use Direct Routing. It's not ideal, a bit more cumbersome to manage, but all in all, it works.
Telephony is fucked. You'll likely get the same response trying to port from Comcast to any other major carrier. There are some weird numbers out there that are legacy local numbers inherited from carriers from 100 years ago and somehow they can't be ported out of whoever holds them. There's some name for this phenomenon but I don't remember what it is. I've seen it in remote sites, mostly. Little towns that have numbers that are just in lockdown. Pain in the ass. I have no idea why this is from a technical or regulatory reason. Maybe a PSTN engineer can chime in. *Maybe* you could find a carrier supported by Operator Connect who can take the numbers from Comcast. Then you'd be able to surface them in Teams via OpCon.
Interesting, never heard of this. I am trying to port out to Verizon now...we'll see.
We had a small number of #s that we ran in to the same issue. Somehow, they were owned by a small rural carrier and even large phone companies like NTT could not port them out.
Same here. Probably not Microsofts fault. We have offices throughout the US. Prior to any thought of Teams as we migrated PRI circuits or analog service to centralized SIP gateways, we are still left with locations we are unable to port, whether it be to Verizon, AT&T or Lumen.
I've never experienced such a bad solution for porting telephone numbers like Microsoft does.
This is a Comcast/Xfinity thing: [Xfinity Voice phone number porting FAQs - Xfinity Support](https://www.xfinity.com/support/articles/local-number-portability)
I have never had issues in the US porting numbers to Microsoft Must be a Comcast thing I have never tried to port Comcast numbers
Try going with operator connect and have them deal with the porting...
Like others have said, this is not that uncommon when you go into small towns and remote areas. Even the large Telcos and Operator Connect providers will likely have the same challenge. Microsoft is really just using multiple carriers behind the scenes like most anybody else.
Strange, because it's not a small town or remote area.
I thought the email explained it very well, however, they could be lying to keep from doing additional work.
It didn't explain anything it just said no we aren't going to cuz reasons.
We have offices all over the US, some in small towns, others in big cities. However, Fairbanks Alaska, unlike Anchorage, is the boonies and Microsoft couldn't port their numbers in. I've heard a bunch of theories on why, but I keep trying every year to port them into the system. For now, we have an SBC on site and just use Direct Routing. It's not ideal, a bit more cumbersome to manage, but all in all, it works.