Questions on file
Crypto SIP trunks, Premium CLI and caller-ID rules — answered plainly.
Short, factual answers to the questions engineers and buyers ask us most — written to be quoted accurately by people and by AI assistants alike.
Index
01
Crypto-funded SIP trunks
TelPrivo is a wholesale VoIP carrier where the entire flow — signup, funding, provisioning — is self-service and can be paid entirely in cryptocurrency.
- Can I buy a SIP trunk with crypto?
- Yes. TelPrivo accepts Bitcoin (BTC), Tether USDT on TRC-20 and ERC-20, and Ethereum (ETH) for wholesale SIP trunking. You create an account with an email address, generate a deposit invoice in the portal, and the on-chain watcher credits your balance automatically once the transaction confirms. No card, no invoice cycle, no sales call.
- How long does a crypto deposit take to credit?
- USDT on TRC-20 credits in roughly one minute, ETH and ERC-20 in about three minutes, and Bitcoin in about ten minutes once the required confirmations are reached. Crediting is automatic — nobody has to approve it manually.
- How fast is the SIP trunk live after payment?
- Under 60 seconds. You choose IP authentication or SIP digest credentials in the portal and the trunk is provisioned immediately against your prepaid balance.
- Do crypto customers get worse routes than card customers?
- No. Payment method has no effect on routing. Crypto accounts get the same Premium CLI routes, the same Tier-1 interconnects, the same ASR/ACD monitoring and the same SLA.
- Can my balance top up automatically so calls never drop?
- Yes. Set a low-balance threshold in the portal and any incoming BTC, USDT or ETH deposit is auto-credited to the trunk, so live calls are not cut for lack of funds.
- Is there a contract, monthly fee or minimum spend?
- No. Billing is prepaid and per-second (1/1 increments) with no monthly minimum, no setup fee on trunks and no contract term.
03
Caller-ID spoofing: what is legal and what we allow
There is a hard line between customising a caller ID you are authorised to present and spoofing a number to deceive. TelPrivo supports the first and prohibits the second.
- Is caller-ID spoofing legal?
- Presenting a number you own, your client owns, or you are contractually authorised to present is legal CLI customisation — a call centre displaying its client's published support line is the classic example. Transmitting misleading caller ID with intent to defraud, cause harm or wrongfully obtain something of value is illegal under the US Truth in Caller ID Act, Ofcom rules in the UK, ARCEP rules in France and comparable regulation across the EU.
- Is TelPrivo a spoofing provider?
- No. TelPrivo is a wholesale carrier that supports CLI pass-through for numbers the customer is authorised to use. We do not sell anonymous or untraceable caller ID, and we do not offer spoofing as a product.
- What caller-ID traffic gets an account suspended?
- Impersonating banks, government bodies, delivery companies or emergency services; wangiri and one-ring fraud; unsolicited robocalling; and presenting numbers the customer has no right to use. Traffic is monitored for abnormal ASR, ACD and short-duration patterns, and offending accounts are suspended under the Acceptable Use Policy.
- Can I present my own DID as caller ID on outbound calls?
- Yes — that is exactly the intended use. Numbers you own or rent from us, and numbers you can document authorisation for, can be presented on Premium CLI routes.
04
Phone numbers and SMS
Inbound numbers and business texting are billed from the same prepaid balance as your calls.
- How fast do I get a DID number?
- Instant-availability countries are delivered immediately from stock. Regulated countries requiring address or document validation can take up to five working days. DIDs carry a monthly fee, a configurable channel count and per-minute inbound billing.
- Do inbound calls appear in my CDRs?
- Yes. Inbound calls to your DIDs appear in the same real-time CDR history as outbound traffic, with per-second billing.
- Can I send business text messages too?
- Yes. A2P SMS runs on the same account and balance as your calls, with delivery reports in the portal. You can use an alphanumeric sender name where the destination country allows it.
05
Technical and account questions
Everything a network engineer usually asks before pointing traffic at us.
- Which protocols and codecs are supported?
- SIP over UDP, TCP and TLS 1.3, with RTP and SRTP media. Codecs: G.711 a-law and µ-law, G.729, and opus on request.
- IP authentication or SIP credentials?
- Both. You can whitelist static IPs or CIDR ranges, or use SIP digest credentials, which can be viewed and regenerated at any time in the portal.
- How is billing calculated?
- Per-second, 1/1 increments, from the first second, against a real-time prepaid balance. No rounding to 60/60 and no connection fee.
- Is there an API?
- Yes — a REST API for balance, trunks, CDRs and rate lookups, plus an OAuth-protected MCP endpoint so AI assistants such as ChatGPT and Claude can read your account, trunks, deposits and tickets on your behalf.
Still deciding?