Identify the product, account and integration version
TelVox Connect is Renav Limited’s programmable-voice product. Its trunk API can connect a PBX or SIP platform, create customer-specific trunks or create WSS agent seats. Keep Connect separate from the TelVox Dial, Desk, Chat and Publish products, and record the legal account, ordered services, numbers, trunk IDs, application owners and support contacts.
Connect is live, but its API is v0.x and field names may change before v1. Preserve the documentation date, request and response schema, deployment version and rollback plan. A marketing page, working dashboard or successful API request does not establish a stable contract for an unpinned integration.
Documented service facts
Reviewed 2026-10-16. Compare SIP trunk services →
API and SIP authentication
DocumentedTelVox documents two separate credentials: an unscoped Bearer API key for server-side REST requests and a generated SIP username and password for each trunk. API keys are shown once and should be separated by service and environment. The trunk connection response can include the SIP password, so neither secret belongs in logs, browser bundles or public configuration.
Registrar, transport and lifecycle
DocumentedThe connection object supplies the account-specific SIP domain, port, transport, username and password. Documented transports are TCP, TLS, UDP and WSS, but transport is fixed after creation. A new trunk is pending until TelVox marks it active; suspended and revoked are separate states. A successful API create is therefore not proof that SIP registration or calls work.
Inbound calls, numbers and webhooks
DocumentedA trunk can send arriving calls to a voice webhook, whose returned markup controls the call. TelVox also documents DIDs claimed from a dashboard pool, with no numbers API. Pool inventory, country coverage, portability, delivered SIP identity, webhook reachability and application behavior remain separate evidence for the selected account.
Routing and failover
Not verifiedThe reviewed sources do not define universal DNS target order, redundant registrar behavior, customer-edge failover, retry timing, alternate inbound routing or established-dialog survival. Webhook fallback and call-status callbacks are application controls, not proof of SIP-path resilience. Obtain and exercise the approved design before relying on an alternate path.
Service and number coverage
Not verifiedThe Calls reference says the documented outbound setup is for Indian numbers, while the pricing page publishes US starting rates and directs other destinations to sales. The number guide says DIDs come from a dashboard pool. Those page-scoped statements do not establish general availability, a particular country, rate centre, number type or porting eligibility.
Codecs, DTMF and RTP
Not verifiedTelVox documents keypad collection and SIP, PSTN and WebRTC paths, but the reviewed sources do not publish a complete trunk codec, packetization, DTMF transport, RTP address, SRTP keying or transcoding profile. Preserve each SIP offer and answer, RTP tuple and decoded result on the authorized path.
Fax and analogue dependencies
Not verifiedNo T.38, audio fax, modem, alarm, lift, door-entry, payment-terminal or analogue-adapter compatibility statement was verified. Inventory each non-voice dependency and retain a provider-approved replacement or representative acceptance result before retiring its existing service.
Signaling, media and secret protection
DocumentedThe trunk API accepts TLS and WSS transports, and TelVox says stored SIP secrets are encrypted and traffic uses TLS in transit. Those are capability and platform-control statements, not evidence of certificate identity, negotiated signaling protection, SRTP, protected carrier legs or end-to-end encryption. Verify the selected path and keep API and SIP secrets distinct.
Concurrency and call-start limits
Not verifiedThe account may limit the number of trunks, and the API returns 422 after that limit. The reviewed sources do not establish selected-account simultaneous calls, calls per second, inbound and outbound sharing, queue behavior or overload response. Obtain current limits and generate only authorized test traffic.
Emergency calling
Not verifiedNo selected-account emergency-number eligibility, registered-location workflow, callback identity, nomadic restrictions, failure behavior or approved test method was verified. Do not infer emergency service from an active trunk, DID or ordinary PSTN reachability; keep an accessible independent method until written scope and acceptance evidence exist.
Pricing, terms and API stability
DocumentedTelVox publishes usage pricing billed by the second, with US starting rates and separate meters for PSTN, SIP or WebRTC legs, numbers, recording, storage and conferences. It says other destinations are scoped with sales and the live API remains v0.x, so preserve the dated rate card, quote, invoice rules, contract and integration version instead of treating examples as a universal price.
Provisioning, callbacks and call evidence
DocumentedA trunk moves through pending, active, suspended and revoked states; revoke is a soft delete with no API undo. Call records separately expose initiated, ringing, in-progress and final outcomes, while callback delivery remains another observation. Monitor API provisioning, SIP registration, webhook receipt, callback response, call record and media outcome independently.
SMS and MMS
Not verifiedThe reviewed Connect trunk, call, number and pricing sources do not establish SMS or MMS service on voice DIDs. Treat messaging as a separate product until number eligibility, API behavior, registration, consent, throughput, filtering, retention and pricing are documented for the selected account.
Separate API authority from SIP registration credentials
Every REST request uses a Bearer API key. TelVox says keys have no scopes and each key can do everything the account can, so use one per service and environment, store it only on the server and rotate by creating, deploying and observing a replacement before deleting the old key. Do not ship it in a browser or mobile bundle.
Each trunk instead receives a generated endpoint name, SIP username and password plus a domain, port and transport. The connection response can reveal that SIP password. Store API keys and trunk secrets in different controls, redact both from logs and use the exact issued connection object rather than inferring a registrar from a public domain.
Treat provisioning state, registration and calls as separate gates
A create request returns a pending trunk. TelVox later sets it up on the SIP server and marks it active; suspended and revoked carry different meanings, and revocation has no API undo. Polling active is a provisioning observation, not evidence that a PBX loaded the credentials, registered successfully or completed a call.
Record the API response, current trunk state, loaded PBX object, resolver answers and REGISTER transaction where the design uses registration. Then trace one authorized inbound and outbound call through SIP response, destination alerting, answer, negotiated media and user outcome. Stop at the first divergence.
Bind webhooks and caller identity to observed outcomes
An arriving trunk call can be posted to a voice webhook whose returned XML controls the call. Caller-ID lookup has a five-second timeout and falls back to the configured default; an allowed-caller-ID list can refuse a lookup result. Those settings do not prove carrier authorization or destination presentation.
Status callbacks, call records and SIP messages are different observations. A configured callback URL is not proof of delivery, a 2xx response is not proof the consumer stored the event, and a completed call record is not proof of intended audio or business outcome. Correlate trunk ID, call SID, callback, SIP dialog and application record without logging secrets or unnecessary personal data.
Qualify numbers, media, recording and browser seats independently
DIDs are claimed from the dashboard pool, and the documentation exposes no numbers API. Pool visibility does not establish portability, current country coverage or eligibility for a specific number. Likewise, the reviewed sources do not publish a complete codec, DTMF transport, RTP, fax, emergency or messaging profile. Obtain those answers for the selected service and observe the negotiated media.
Dual-channel recording is an option, not proof that a legally authorized recording exists or is retrievable. WSS agent seats expose a long-lived SIP password to the browser, while TURN credentials are refreshed and expire. Give each agent a distinct seat, pass secrets only after authentication, keep them out of page source and logs, and rotate a leaked seat password.
Accept the commercial and operational service actually used
TelVox publishes usage dimensions and US starting rates, but other destinations are scoped with sales and invoices apply the actual rate. Preserve the dated rate card, destination and path, number rental, recording and storage terms, taxes, commitments, limits, support entitlement and contract. Do not reproduce a starting figure as a durable universal price.
Before production acceptance, verify only authorized flows: provisioning, credential rotation, registration, inbound and outbound routing, identity, webhook timeouts, callback retries, DTMF, media, recording controls, failure handling, revocation and rollback. No TelVox account, key, trunk, number, registration, webhook, recording, packet, media stream or call was tested for this guide.
Sources & applicability
Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.
- TelVox Connect SIP trunks API reference ↗
- TelVox Connect authentication and API keys ↗
- TelVox Connect Calls API reference ↗
- TelVox Connect phone numbers reference ↗
- TelVox Connect recordings API reference ↗
- TelVox Connect webhooks API reference ↗
- TelVox Connect pricing ↗
- TelVox security and compliance ↗
- Renav Limited TelVox products ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.