Beat “VoIP not allowed” rejects with MNO-registered non-VoIP numbers — carrier line-type metadata apps trust, not internet-telephony DIDs. Pay after delivery.
This hub is only about line type. Strict apps run CNAM/MNO and third-party scoring that labels consumer VoIP and cloud DIDs as internet telephony. A non-VoIP number must register as a mobile subscriber on that lookup — geography and “temporary vs disposable” are secondary questions answered on other pages.
Come here when the failure mode is literally “VoIP not allowed,” “wireless number required,” or a silent drop after a known Google Voice / TextNow / SIP range. If you mainly want a console inbox (product form), use the virtual phone number hub. If you run team queues, use the SMS verification service hub.
Line-type friction shows up most on messengers and fintech: WhatsApp, Google, PayPal, and similar graphs already fingerprint recycled VoIP ranges. NonVoipOtp’s handset pools are curated for verification-only workflows — not a business phone, not a monthly SIP trunk.
Diagnose before you retry blindly: if the app accepted foreign SIMs last week but blocks cloud numbers today, you have a line-type problem. If it only accepts +1, you have a geography problem — open the USA phone number hub instead.
Billing note: metered OTP capture (often from $0.02), wallet timeouts credit back automatically — reserve a line, enter it on the app, read the code in console. Catalog spans 2,200+ apps across 200+ countries where stock exists. Avoid public SMS inboxes; they recycle numbers across strangers.
“Virtual” is delivery: SMS in a console, not a plastic SIM. “Non-VoIP” is what the carrier lookup returns. This page argues line type; the virtual hub argues product form.
Copy that mentions VoIP, internet telephony, landline, or “use a mobile number” after you tried Google Voice, TextNow, or a cloud DID. Country-only rejects belong on the USA hub.
No. Scoring databases update constantly. Fresh handset-class inventory matters more than a number that merely looks like a mobile format in the UI.
No. Inventory is verification-only. Voice trunks, call forwarding, and standing DIDs are out of scope — use a telephony vendor for those jobs.