Answers for buyers, developers, and telecom operators.

VoiceTel is a telecommunications platform for teams that need real carrier services, programmable voice, messaging, numbers, SIP trunking, Hosted PBX, lookup APIs, and operational support from people who understand the network. Developers can use VoiceML and the REST APIs. Operators and integrators can use SIP trunks, the SDN appliance, Hosted PBX, numbers, messaging, and carrier-grade routing tools.

Developers, telecom engineers, MSPs, resellers, operators, and business buyers. The product surface is strongest for technical buyers, integrators, and businesses with real telecom needs. See the dedicated landing pages: For developers, For integrators and resellers, For larger organizations.

All of those, layered together. VoiceTel operates carrier services and exposes them through wholesale voice, programmable voice (VoiceML), SIP trunks, messaging, numbers, lookups (Caller and Carrier), Hosted PBX, and phone applications under one account.

VoiceML is for programmable call flows controlled by XML and webhooks. SIP Trunking connects your existing PBX, SBC, contact center, or voice platform to VoiceTel for inbound and outbound calling. Hosted PBX is a VoiceTel-managed business phone system with users, extensions, devices, call routing, voicemail, and apps. See VoiceML, SIP trunking, and Hosted PBX for product details.

VoiceTel publishes list rates where available. The pricing calculator can model estimated monthly spend, but final account pricing depends on KYC verification, capacity review, usage profile, and contract terms. Your customer portal displays the rates that apply to your account.

Volume pricing is based on real usage, service mix, capacity requirements, destination profile, minimum commitments, and contract terms. The public calculator and posted line items are useful for modeling. Final rates are confirmed after VoiceTel reviews the workload and account requirements.

The calculator may not include taxes, regulatory charges, carrier pass-through fees, registry fees, 10DLC campaign fees, payment processor fees, third-party speech providers, third-party storage providers, or account-specific contract terms. For production workloads, use the calculator as a model and confirm final pricing with VoiceTel.

No. The pricing calculator states that usage inputs remain client-side.

No. Carrier, registry, and pass-through fees for A2P 10DLC are listed separately from the base messaging segment rate. Plan for them as a distinct line item.

No. Customers bring their own speech-to-text, text-to-speech, and recording-storage vendors where applicable, and pay those providers directly. VoiceTel does not insert a platform markup on top of third-party speech or storage costs.

VoiceTel is a prepaid service. If your balance goes below zero, services are disabled until funds are added.

VoiceTel requires KYC before enabling production network access because voice, messaging, numbers, and emergency services can be abused if accounts are not verified. KYC helps protect customers, carriers, recipients, emergency-service systems, and the VoiceTel network from fraud, impersonation, spam, and unauthorized use.

For an individual account: name, physical address, and active telephone number — each with a supporting record (government identification, lease, utility statement, or similar); a description of goods or services offered, with verification of commercial presence (website, social-media account, or store front); and a contractual certification that the customer has not been the subject of an adverse final determination for violating state or federal robocall rules. Documents must be clear, current, and match the account name.

Yes. For a partnership or corporate account, VoiceTel collects legal business name, place of formation, proof of good standing dated within the last six months, U.S. Employer Identification Number or Business Registration Number where applicable, physical business address, and active telephone number — each with supporting records. The account also needs a description of goods or services offered with verification of commercial presence (website, social-media account, or store front), the name of the individual authorized to act on behalf of the customer, evidence of that authority (letter of authority, board minutes, or contractual representation and warranty), and the same contractual certification that the customer has not been the subject of an adverse final determination for violating state or federal robocall rules.

Some account exploration is available pre-KYC, but production traffic — calling, messaging, number provisioning, and emergency-service registration — is gated on a completed KYC review.

Common rejection reasons are an expired ID, an illegible photo, an address mismatch, a missing signature, or an unverifiable business. Re-submit clear, current documents that match the account name and address.

Yes. Meeting the documentation requirements is necessary but not sufficient. VoiceTel may decline any application at its discretion based on risk review, traffic-pattern analysis, downstream-carrier or registry constraints, prior compliance history, or any other factor VoiceTel determines relevant to network integrity, fraud prevention, or regulatory exposure. VoiceTel is not obligated to disclose the basis for a decline.

Yes. VoiceTel may suspend or restrict service for non-payment, fraud indicators, abusive traffic, invalid compliance information, regulatory risk, network-integrity issues, or violation of applicable terms. If service is restricted, review the notice in your account or contact support with the requested documentation.

Yes. KYC documents are used for verification and compliance and are not shared beyond what is required for account review and regulatory obligations.

Use account recovery on the portal to reset access to a known email address.

The pin is case-sensitive and time-sensitive. Verify your mobile number immediately after receiving the account activation email.

VoiceTel needs additional information. Obtain copies of your current utility or phone bill along with matching photo identification, then provide that documentation to customer support to manually validate your account.

Voice origination is inbound calling from the public telephone network to your VoiceTel account. When someone calls a phone number assigned to your account and VoiceTel delivers that call to your SIP trunk, VoiceML application, Hosted PBX, or routing destination, that is origination.

Voice termination is outbound calling from your VoiceTel account to the public telephone network. When your PBX, application, or SIP platform sends a call to VoiceTel and VoiceTel routes it to the destination carrier, that is termination.

Public voice rates are list rates and appear on the pricing page and in the calculator. Account-specific tiers or contract rates are confirmed after capacity review and shown in the customer portal once provisioning completes.

No. VoiceTel runs the carrier and call-control layer; you bring your own STT, TTS, and recording-storage vendors and pay them directly. There is no VoiceTel markup on those services.

VoiceTel can help review caller identity, STIR/SHAKEN signing, CNAM records, number usage patterns, and carrier response data. No carrier can guarantee that every analytics provider or mobile carrier will remove a spam or scam label immediately. Remediation depends on traffic history, caller behavior, analytics vendors, and downstream carrier policies.

Yes. VoiceTel can support SIP registration and IP authentication depending on the account, trunk type, and network design. SIP registration is useful when a PBX or device registers to VoiceTel with credentials. IP authentication is better for controlled PBX, SBC, carrier, and contact-center environments where traffic comes from known static IP addresses. See the SIP trunking product page for the wholesale trunk options.

One-way audio is usually caused by NAT, firewall policy, SIP ALG, RTP pinholes, codec negotiation, or direct-media behavior. Send support the call timestamp, calling number, called number, SIP Call-ID, SIP trace, and any RTP capture available from your PBX or SBC. The router and firewall guides cover the common SIP ALG and NAT fixes.

For the fastest review, send the call direction, timestamp with timezone, calling number, called number, SIP Call-ID, response code, SIP trace, and a short description of the expected behavior. For audio issues, include RTP details or a packet capture if available. Reach the team at contact.

VoiceML is VoiceTel's XML-based programmable voice runtime. It lets your application control calls with markup, webhooks, recordings, conferences, queues, prompts, and call-control instructions. It is designed for teams that want programmable voice without giving up carrier-grade routing, SIP visibility, and operational support.

Often, yes. If your application uses supported voice verbs, callbacks, parameters, and webhook patterns, you may be able to migrate by changing endpoints, credentials, and configuration instead of rewriting the call flow. Not every Twilio feature maps 1:1. Test one production call path first, compare callback behavior, and confirm unsupported verbs or attributes against the compatibility matrix before cutover.

VoiceTel's compatibility layer is focused on supported programmable voice workloads. Some Twilio products, verbs, attributes, or non-voice APIs may not be implemented. Before migration, compare your application against the VoiceML compatibility matrix and test the exact call flows you plan to move.

Paste your response markup into the VoiceML validator. It runs entirely in your browser, confirms the document is well-formed XML, and flags any element that is not a known verb or noun.

Supported text-to-speech integrations. Open-source engines run on VoiceTel infrastructure; cloud vendors are billed by you directly. Piper and Coqui TTS are open-source and self-hosted. OpenAI TTS, Amazon Polly, and Azure AI Speech are cloud vendors you sign up for and pay directly.

Bring your own speech-to-text provider and pay the vendor directly. Supported integrations: Deepgram, Google Cloud Speech-to-Text, AWS Transcribe, and Azure AI Speech.

Yes. VoiceTel Messaging supports A2P 10DLC workflows for business SMS and MMS traffic. Customers are responsible for accurate brand and campaign information, required disclosures, opt-in records, carrier or registry fees, and ongoing compliance. VoiceTel can help review the filing before submission, but approval is controlled by the registry, carriers, and downstream reviewers.

No. VoiceTel can help identify common rejection risks and prepare cleaner 10DLC submissions, but final approval is controlled by the registry, carriers, and downstream reviewers. Campaigns may be rejected for unverifiable business information, weak opt-in evidence, missing disclosures, prohibited content, public URL shorteners, mismatched sample messages, or use cases that do not match the sender's website or business model. The readiness checklist covers the common pre-flight fixes.

The customer. VoiceTel provides the platform and supports the filing workflow, but the customer is responsible for accurate brand information, campaign use case, opt-in evidence, consumer disclosures, carrier and registry fees, and ongoing compliance with CTIA and FCC rules. See the messaging compliance guide for the operational details.

Message filtering can happen even after registration. Common causes include content that does not match the approved campaign, missing consent, complaint activity, suspicious links, URL shorteners, prohibited content, high opt-out rates, or carrier-specific enforcement. See the operating rules for the day-to-day expectations. Send support the message body, timestamp, destination number, originating number, campaign ID, delivery receipt, and any carrier error code.

Yes — direct SMPP is available for high-volume traffic after compliance and use-case review. See Messaging for product details.

Yes. Hosted SMS allows you to keep voice with another carrier while VoiceTel handles messaging, subject to authorization and number eligibility.

Carrier pass-through fees are listed separately from base messaging rates so charges remain transparent.

Yes, when the numbers are portable and the losing carrier accepts the port request. Most porting delays are caused by mismatched account information, incorrect service address, missing PIN, pending orders, frozen accounts, or documents that do not match the losing carrier's records. The porting procedure walks through what we need from you.

No. Keep the existing service active until the port completes. Canceling service too early can cause a port rejection, service interruption, or number recovery issue. Wait until the number is confirmed active on VoiceTel before closing the old account.

Yes, in many cases. VoiceTel may be able to enable messaging for a number while voice service remains with the existing carrier. SMS enablement usually requires authorization, number eligibility, and proof that you control the number.

Common rejection reasons: name or address mismatch with the losing carrier's records, wrong account number, missing or incorrect PIN, a frozen account, a pending order on the number, or documentation that does not match the CSR. Fix the underlying mismatch and resubmit the port request. See retrieving porting PINs if that's the blocker.

Yes, where emergency calling is enabled, configured, and supported for the number and service type. Emergency calling requires accurate registered address information. VoIP emergency calling can be affected by internet outages, power loss, incorrect address records, unsupported number types, routing misconfiguration, or use from a location different from the registered address.

Usually, yes. If users are located at different physical addresses, each emergency-calling identity should be associated with the correct service location where supported. Customers are responsible for keeping emergency addresses accurate, especially for remote workers, branch offices, and users who move between locations.

VoiceTel Hosted PBX is a managed phone system for businesses, resellers, and multi-location teams. It can include users, extensions, call routing, voicemail, ring groups, business hours, devices, apps, and VoiceTel network services for inbound and outbound calling.

Often, yes, if the phones are SIP-compatible and can be provisioned for the VoiceTel environment. Support depends on the device model, firmware, provisioning method, network conditions, and whether the device is managed by VoiceTel or brought by the customer. See the per-vendor desk-phone setup guides.

Yes. Hosted PBX uses VoiceTel-managed inbound and outbound calling and assigned phone numbers natively.

VoiceTel Phone is a calling client for users who need access to VoiceTel voice services from a browser, desktop, or mobile device. Availability and features depend on the account, tenant, user configuration, and product plan.

CNAM lookup returns caller-name information associated with a telephone number when available from supported data sources. Results can help with caller display, call screening, fraud review, CRM enrichment, and routing decisions, but availability and freshness depend on upstream data sources. See Caller Lookup for the product details.

LRN lookup helps identify routing information for a number that may have been ported from one carrier to another. It is commonly used for portability-aware call routing, carrier analysis, rating workflows, and telecom troubleshooting. See Carrier Lookup for the product details.

The VoiceTel SDN appliance is a small network device used to stabilize SIP connectivity between a customer site and VoiceTel. It is useful when firewalls, NAT, SIP ALG, UDP timers, or RTP behavior make normal SIP trunking unreliable.

No. The SDN appliance does not replace your PBX. It sits on the customer network and provides a controlled path between your PBX or SIP devices and VoiceTel, reducing the common network problems that cause registration failures, one-way audio, and unstable call delivery.

Use API v2.2 for new builds. v2.1 is retained for legacy integrations, migration checks, and comparison against older endpoint behavior.

The API playground lets authorized users run supported requests from the browser, inspect live responses, and compare request shapes against the API reference. Use it for exploration and troubleshooting, not as a substitute for production integration tests.

API keys saved in the playground are stored locally in the browser on that device. Once saved, the key is not displayed in page output or generated examples. The key is used to authorize requests you choose to send. Replace or remove it if you no longer want that browser to use it. See credentials for how to retrieve or rotate the key.

Include the affected service, account, timestamp with timezone, examples, numbers involved, API request IDs, SIP Call-IDs, message IDs, recent configuration changes, and any traces or logs available. For voice issues, include SIP traces where possible. For messaging issues, include message IDs, campaign IDs, destination numbers, timestamps, and delivery receipts. Reach the team at contact.

Check the SIP username, password, domain or realm, registration server, source IP, firewall policy, NAT behavior, TLS settings if used, and registration interval. Also confirm that the account and trunk are active and that your PBX is not being blocked by a local firewall, SIP ALG, or failed authentication lockout. The router and firewall guides cover SIP ALG and NAT-traversal fixes; the PBX guides cover trunk-side configuration.

Confirm that your webhook endpoint is publicly reachable over HTTPS, presents a valid certificate, responds within the expected timeout, and returns a successful HTTP status. Check your application logs for slow database calls, blocked outbound requests, DNS issues, TLS errors, or deployment changes that occurred near the failure time.

Resellers and integrators are responsible for knowing and verifying their downstream customers, collecting accurate compliance information, and ensuring that customer traffic follows VoiceTel policies, carrier rules, and applicable law. VoiceTel may request additional documentation or restrict traffic if downstream use creates compliance, fraud, or network risk. The voice compliance and messaging compliance guides explain the operational baseline; the binding policy lives in Legal.

Each real sender generally needs accurate brand and campaign information. A reseller should not use one generic brand or campaign as a proxy for unrelated downstream businesses. Collect each customer's legal business information, website, opt-in flow, message samples, privacy policy, terms, and use case before submitting 10DLC registration. See the integrators landing page for the multi-tenant workflow.

The customer or sender is responsible for collecting, storing, and honoring valid consent for calls and messages. VoiceTel can provide platform tools and compliance guidance, but it does not replace the customer's obligation to follow applicable laws, carrier rules, registry requirements, and industry policies. The binding policy lives in Legal; operational guides are at voice compliance and messaging compliance.