QUESTION About Anveo Direct

Ayoub

New Member
Joined
Aug 18, 2026
Messages
7
Reaction score
1
Hello everyone,
Please I have a question about the service you already recommended to me Anveo .
edt what there is not a problem if I used all the numbers created on the accounts checks 2fa .
Or do you have to use the incoming calls and the incoming voice?
Thanks in advance
 
Anveo has two services: Anveo Direct and Anveo. Anveo Direct can provide termination, origination or both. You do not need incoming DID's if you don't want them. I use them for making international calls and for overflow if another vendor's trunks go down.

You would want Anveo Direct for what you're looking to do.. https://www.anveodirect.com/
 
Anveo has two services: Anveo Direct and Anveo. Anveo Direct can provide termination, origination or both. You do not need incoming DID's if you don't want them. I use them for making international calls and for overflow if another vendor's trunks go down.

You would want Anveo Direct for what you're looking to do.. https://www.anveodirect.com/
Hi, I’ve already signed up for Anveo Direct and I’m currently evaluating it for my business.

My main goal is to rent a large number of DIDs, mainly US numbers, that support incoming SMS. The business model is similar to SMS-Man: we would rent the numbers and provide them to our customers for receiving verification/2FA SMS from services such as WhatsApp, Gmail, etc.

Do you know if Anveo Direct allows this type of usage, or are there any restrictions/problems with receiving OTP/2FA SMS from platforms like WhatsApp, Google/Gmail, Microsoft, etc.?

Also, if I need a large volume (for example 1,000+ numbers), is it possible to get better wholesale pricing or special rates?

I’m particularly interested in knowing whether there are any restrictions on using the numbers for SMS verification and whether Anveo Direct is suitable for a business that rents/resells these numbers to end customers.

Thanks!
 
You'll need to contact them to discuss that. I have no experience with such an operation or volume pricing.
 
It has become almost impossible to use voip based incoming sms for account verification in the US. Most (if not all) social media companies now expect you to have a real mobile phone DID to verify either by sms or by voice call. Institutional sites already made that transition (health care, government, financial, administrative). It's probably a programming bug if you manage to receive an account verification sms on a voip DID.
 
It has become almost impossible to use voip based incoming sms for account verification in the US.
This is not an accurate statement because VoIP is just a transport. Real carriers use VoIP for this, it's not about whether or not it's delivered by VoIP but who the Number Authority really is. ILEC/CLEC carriers like ATT, Verizon and even Telnyx/Bandwidth are trusted due to the amount of oversight and regulation along with own infrastructure. All my numbers are listed on Bandwidth's OCN so when verification services do a look up it passes because the number isn't classified as VoIP, it's "landline" or "mobile".

There was a point where Interconnected VoIP Providers could easily register as Number Authorities have have NPA-NXX pools assigned to them. That is much harder now, the rules have changed about it due to fraud and other problems. However, a carrier with no infrastructure like GoogleVoice or TextNow i.e. "Over-the-Top VoIP Carriers" are classified as such. They are able to meet the requirements to be a Number Authority but their pools will be listed as "VoIP" vs "landline" or "Mobile".

When these services look up the number they are looking for the current OCN/SPID, all over GoogleVoice's and TextNow's OCNs are automatically blocked, for example. They are going to look at the NPAC, LERG, RND and reputation of the number. If that number lives on a certain OCN/SPID or has a wonky history it will be blocked.

So Bob's VoIP Shack, who uses Bandwidth, has no issue with SMS verification but Larry's VoIPText uses TextNow which will have all sorts of issues as it will be blocked all over the place. Two voip based companies, two completely different results due to upstream connections.
 
This is not an accurate statement because VoIP is just a transport. Real carriers use VoIP for this, it's not about whether or not it's delivered by VoIP but who the Number Authority really is. ILEC/CLEC carriers like ATT, Verizon and even Telnyx/Bandwidth are trusted due to the amount of oversight and regulation along with own infrastructure. All my numbers are listed on Bandwidth's OCN so when verification services do a look up it passes because the number isn't classified as VoIP, it's "landline" or "mobile".

There was a point where Interconnected VoIP Providers could easily register as Number Authorities have have NPA-NXX pools assigned to them. That is much harder now, the rules have changed about it due to fraud and other problems. However, a carrier with no infrastructure like GoogleVoice or TextNow i.e. "Over-the-Top VoIP Carriers" are classified as such. They are able to meet the requirements to be a Number Authority but their pools will be listed as "VoIP" vs "landline" or "Mobile".

When these services look up the number they are looking for the current OCN/SPID, all over GoogleVoice's and TextNow's OCNs are automatically blocked, for example. They are going to look at the NPAC, LERG, RND and reputation of the number. If that number lives on a certain OCN/SPID or has a wonky history it will be blocked.

So Bob's VoIP Shack, who uses Bandwidth, has no issue with SMS verification but Larry's VoIPText uses TextNow which will have all sorts of issues as it will be blocked all over the place. Two voip based companies, two completely different results due to upstream connections.
Thank you for the detailed explanation. I understand now — especially the difference between the VoIP technology itself and the carrier/OCN/SPID behind the number.

That makes much more sense to me. I really appreciate you taking the time to explain it in detail!
 
... All my numbers are listed on Bandwidth's OCN so when verification services do a look up it passes because the number isn't classified as VoIP, it's "landline" or "mobile".
@Samot : Is there a way to get DIDs which are currently with BulkVS (hosted with Bandwidth) to be classified as "Mobile"?
 

Members online

Forum statistics

Threads
26,771
Messages
174,968
Members
20,333
Latest member
Sado1234
Get 3CX - Absolutely Free!

Link up your team and customers Phone System Live Chat Video Conferencing

Hosted or Self-managed. Up to 10 users free forever. No credit card. Try risk free.

3CX
A 3CX Account with that email already exists. You will be redirected to the Customer Portal to sign in or reset your password if you've forgotten it.
Back
Top