Separate outbound identity from inbound delivery
Voxbeam's current getting-started material uses the customer's authorized public IP for outbound calls and names sbc.voxbeam.com as the server. Inbound DIDs are delivered by SIP to a trunk-level IP or SIP URI, with a per-DID endpoint override documented in the FAQ. These are different controls: an authorized outbound source does not establish where a purchased number will be sent.
Record the account, public source address, DNS name, every DID destination, request-URI format and owner. A completed IP authorization does not create a registration binding, and an inbound destination does not grant outbound permission.
Documented service facts
Reviewed 2026-09-27. Compare SIP trunk services →
Outbound authentication
DocumentedVoxbeam's current getting-started material authorizes outbound service by customer source IP. The account Settings area is used to add that address; this is a network identity control, not a SIP username-and-password claim.
SIP registration
DocumentedThe current help page describes IP authorization, and Voxbeam's published FreeSWITCH guide sets registration to false. Treat that guide as a legacy configuration example and confirm the current account model; do not use a REGISTER indicator as the sole health signal for an IP-authenticated path.
Inbound delivery
DocumentedInbound DIDs are delivered by SIP. The FAQ documents a default trunk-level IP or SIP URI and a per-DID SIP endpoint override. Record the exact destination and request-URI format instead of transferring outbound authentication assumptions to inbound routing.
Inbound failover
Not verifiedVoxbeam publishes provider-network redundancy and hot-standby claims, but the reviewed pages do not establish an ordered set of customer SIP destinations or its failure triggers. Provider infrastructure claims do not prove customer PBX, access-circuit, DNS or active-call failover.
Number and regional availability
Not verifiedVoxbeam publishes DID search and porting paths, while exact number inventory, documents, portability, activation timing, caller-identity handling and route reach vary by market, number, account and date. Confirm the selected order before migration.
Audio codecs
DocumentedThe help page lists G.729a and G.723 across its routes and G.711 mu-law, G.711 A-law and G.726 for most destinations. Preserve the PBX allow list and inspect actual SDP because route-level publication does not establish every downstream carrier path.
T.38 fax
Not verifiedThe DID page lists T.38, but it does not establish universal number, direction, carrier, renegotiation, error-correction or fallback behavior. Pilot each selected number, endpoint, page profile and audio fallback separately.
Signaling and media encryption
Not verifiedThe reviewed current product, help, FAQ and network pages do not establish one customer-facing TLS and SRTP trunk workflow. Source-IP authorization controls network identity; it must not be represented as signaling or media encryption.
Call-start capacity
DocumentedVoxbeam distinguishes DID-only service, which publishes two concurrent calls per DID and an incoming-minute cap, from a capacity package with shared purchased channels. A DID cannot exceed the trunk's channel count. These are active-call controls; current CPS and burst response remain separate account checks.
Emergency calling
Not verifiedThe reviewed first-party pages do not document an emergency-calling enrollment, registered-location, calling-identity, dispatch or approved test workflow for this service. Obtain a written account-specific procedure or retain a separately validated route before deployment.
Pricing model
Not verifiedPublic pages distinguish outbound route classes, DID-only service and channel-based inbound capacity. Exact rates, increments, number charges, minimums, taxes, surcharges, support and contract terms require the current account portal or a dated quote.
Administration and support
DocumentedThe account material covers IP authorization, DID destination configuration and contact-based support. Configuration consulting, response targets, escalation, maintenance notice, log retention and change ownership remain operating-agreement questions.
SMS and MMS
Not verifiedThe FAQ describes SMS on some US DIDs and excludes toll-free numbers from the published scope. It does not establish MMS, universal eligibility, sender registration, throughput, API behavior, retention or pricing; evaluate messaging separately from voice.
Treat no-REGISTER examples as versioned evidence
The current help page describes IP authorization rather than credentialed registration. Voxbeam's published FreeSWITCH guide explicitly sets registration to false, while its Asterisk guide uses legacy chan_sip syntax. These documents support the service-model distinction but are not current FreePBX or PJSIP interoperability guarantees.
Use the installed PBX's supported configuration path, preserve current account instructions and confirm DNS, transport, port, From identity and presented caller identity in a pilot. Do not interpret an absent REGISTER indicator as a failed IP-authenticated trunk, and do not copy legacy driver syntax into a current deployment.
Preserve the outbound route-class prefix
The help page documents an E.164-format destination combined with a prefix for the selected Platinum, Gold, Silver or Call Center route. Record the current account's route selection and exact normalized number before constructing the request URI. A route label is a commercial and routing choice, not a measured quality score or an assurance for one destination.
Test permitted and denied destinations, caller identity, DTMF, a long call and the failure response for an invalid format. Keep dialplan normalization before the trunk boundary so emergency, internal and restricted calls cannot inherit a wholesale route by accident.
Keep DID-only limits separate from shared capacity
Voxbeam describes two inbound models. DID-only service publishes two concurrent calls per DID and an incoming-minute cap, with capacity not shared across numbers. Its DID-with-capacity model uses purchased shared channels and the FAQ says a DID limit cannot exceed the trunk's channel count. These are active-call allocations, not published calls-per-second guarantees.
Confirm the current account's DID type, per-number limit, shared channel count, CPS, burst handling and rejection response. Test busy and overflow behavior without inferring a universal provider ceiling from one package description.
Scope codecs, fax and messaging to the selected path
The help page lists G.729a and G.723 across routes and G.711 mu-law, G.711 A-law and G.726 for most destinations. Preserve the PBX codec policy and capture actual SDP because a provider list does not prove every downstream path. The DID page lists T.38, but each number, carrier, direction, endpoint, page count and fallback needs a fax pilot.
The FAQ says SMS is available on some US DIDs and excludes toll-free numbers from the published scope. Confirm number eligibility, sender registration, API behavior, throughput, retention, MMS and current terms separately from voice.
Close resilience, security and emergency gaps
Voxbeam publishes provider-network redundancy and hot-standby claims. The reviewed material does not document ordered customer SIP destinations, failure triggers or customer-side active-call survival. Verify PBX, DNS, power and access-circuit recovery independently, and do not turn provider infrastructure language into an end-to-end availability guarantee.
The reviewed pages also do not establish one current customer TLS/SRTP workflow or an emergency-calling enrollment and approved test procedure. Obtain written account-specific answers before sensitive or emergency traffic. Confirm current number availability, porting, charges, support response and escalation through the account or a dated quote. No account, trunk, number, registration, route, codec, fax, encryption, emergency, messaging, failover, capacity, availability, price or live-call behavior was tested for this guide.
Sources & applicability
Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.
- Voxbeam service overview ↗
- Voxbeam help and getting started ↗
- Voxbeam FAQ ↗
- Voxbeam DID service ↗
- Voxbeam network ↗
- Voxbeam Asterisk configuration guide ↗
- Voxbeam FreeSWITCH configuration guide ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.