estromlund

Joined 14 years ago

Karma
162
Submissions
38
Member since
Mar 14
Contact: @estromlund [email protected] https://www.erikstromlund.com

Founder & CEO @ FathomTel

View on Hacker News

Recent submissions

Comment · 4 years ago
I operate a telephony service (perhaps similar to the one you parked your number at) and we do thousands of ports a year from our service to major carriers. Porting is such a backwards pre-internet system and things go wrong all the time unfortunately.

My guess is that the port went through but US Mobile has lost it in their system.

One of the biggest issues I see is when porting from a VoIP service to a carrier. The carrier doesn't always know what to do since it is slightly outside normal; the majority of their customers are moving between major carriers. But now your number has been classified as a "wireline" (VoIP) number and US Mobile is probably confused.

Honestly, I bet it magically arrives at US Mobile after a bit of time. But if you can't wait, I'd engage the VoIP service again. They likely operate downstream from a provider such as Bandwidth, Twilio, or similar. Their team can ask their upstream provider for a "snapback" of the number - essentially they can go take it back. That will leave you with your number back at the VoIP service to try again when you're ready :)

With all that said, I do have access to these upstream systems and some more advanced lookup tools. Shoot me an email (in bio) with your number and I can do some research for you if you want. Good luck!

Comment · 5 years ago
Comment · 6 years ago
Thanks for using and recommending Unlisted! We added an Android version last year and both apps are under active development. I'm happy to answer any questions (or receive feedback about what we could do better) - [email protected]
Comment · 7 years ago
I’m the founder of Unlisted (https://www.unlistedapp.com) and this is exactly the problem I was aiming at when building our private number service.

Unfortunately today, however, many sites will detect VoIP numbers and refuse to send messages to them. There are two reasons: 1) The app detects that it is not a “real” number and blocks its entry, or 2) the number is accepted but no message is ever received. In the second case, the “call with a code” option does usually work though. The reason is that short code providers negotiate delivery outside of the normal framework that long code (“normal”) numbers use. Most apps like Unlisted are using Twilio as a provider and these agreements just aren’t in place.

I’ve been running Unlisted for over 6 years so have a bit of experience around this space. Am happy to answer any questions!

Comment · 9 years ago
Comment · 9 years ago
Comment · 9 years ago
Comment · 9 years ago
Comment · 9 years ago
Comment · 9 years ago
Comment · 9 years ago
Comment · 9 years ago
Comment · 9 years ago
Comment · 10 years ago

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton