Start with the service order and exact routing target
Broadvoice says its SIP trunking service connects an existing PBX or cloud platform to the public telephone network and exposes centralized provisioning, DID management and routing controls. Record the legal customer, current order, numbers, selected PBX or cloud target, trunk identifier, support owner and rollback contact before applying a template.
A portal login, visible DID or routing control does not prove that inbound delivery, outbound authorization, identity, media or emergency service is active. Preserve dated order and portal evidence without exposing credentials.
Documented service facts
Reviewed 2026-10-13. Compare SIP trunk services →
SIP authentication
Not verifiedBroadvoice publishes a distinct SIP-trunking portal and says the service connects an existing PBX or cloud platform, but the reviewed public material does not define one digest-credential, source-IP or certificate authentication model for every order. Obtain the assigned connection record and preserve source addresses, SIP and authorization identities, challenges and responses without treating a portal login as trunk authentication.
SIP registration
Not verifiedThe reviewed public pages do not establish whether REGISTER is required, optional or unsupported, or publish a universal registrar, realm, Contact policy, expiry, refresh or transport. Select a PBX template only after reconciling the current order and provider-issued configuration, then retain the actual registration exchange if registration applies.
Inbound delivery and number format
Not verifiedBroadvoice documents DID management, local and international numbers, routing controls and use with an existing PBX. The reviewed pages do not publish one inbound target, Request-URI format, identity-header policy, source range or destination port for every deployment. Retain the assigned number, route object, delivered identifiers, source and first PBX match for each accepted inbound test.
Routing and failover
Not verifiedThe product page advertises built-in redundancy and failover across an existing PBX or b-hive platform. It does not define alternate targets, health checks, retry responses, detection and restoration timers, route priority or established-call behavior. Attach every continuity claim to the ordered topology and an approved new-call failure and recovery exercise.
Number and regional availability
DocumentedBroadvoice documents centralized DID management plus local and international numbers, and says SIP trunking can support locations and regions. Those statements do not establish current inventory, portability, local-presence rules, activation time or caller-identity rights for one account. Preserve a dated order or port result for the exact number, country and legal entity.
Audio codecs and DTMF
Not verifiedThe reviewed public pages do not publish one codec list, packetization interval, DTMF method, RTP range, transcoding policy or media-anchoring model for every trunk. Obtain the service-specific technical record and preserve both SDP bodies, telephone-event mapping, RTP endpoints and decoded authorized-call evidence.
Fax and T.38
Not verifiedBroadvoice lists Virtual Fax as a separate component on its public status page. The reviewed SIP-trunking materials do not establish T.38, G.711 pass-through, switchover behavior, gateway support or document limits on the voice trunk. Treat hosted fax and trunk fax as separate services and acceptance paths.
Signaling and media encryption
Not verifiedThe product page describes secure IP connectivity, but the reviewed public material does not establish SIP TLS, certificate validation, SRTP, keying, approved source ranges or end-to-end protection for the ordered trunk. Map every signaling and media leg and verify authorization, transport and negotiated protection separately.
Concurrent calls and call-start rate
DocumentedBroadvoice documents adding channels or capacity on demand, bursting and scaling for peak demand. The agreement surface links a service-specific addendum, but public wording does not establish the selected concurrent-call entitlement, calls-per-second rate, burst ceiling, bandwidth requirement or PBX limit. Preserve the signed order and run only a separately approved bounded load exercise.
Emergency calling
Not verifiedThe reviewed public SIP-trunking pages do not establish automatic emergency-calling entitlement, registered-location workflow, caller-ID mapping, nomadic behavior, callback handling, outage behavior or an approved validation method for every trunk. Confirm each site and number against the current order, keep an independent calling path and never place an uncoordinated emergency call.
Pricing model
Not verifiedBroadvoice describes flexible pricing and the agreement page links a current Elastic SIP Trunking Addendum. The reviewed public product page does not provide a complete selectable quote for one deployment. Preserve the signed order, channels, burst treatment, minutes, destinations, DIDs, toll-free service, taxes, fees, term, renewal, cancellation and support rather than reusing an old public rate card.
Administration and support
DocumentedBroadvoice documents centralized provisioning, DID and routing changes, usage visibility and real-time reporting. It also publishes a SIP portal, ticket and telephone support, service-delivery and contract-change paths, and a status component for SIP Trunking. These surfaces do not establish account roles, maintenance notice, response target, escalation, retention or restoration terms for one order.
SMS and MMS
Not verifiedBroadvoice publishes SMS elsewhere in its communications portfolio and exposes an SMS status component, but the reviewed SIP-trunking page does not establish messaging eligibility on every trunk number, sender registration, API or webhook security, throughput, retention or commercial terms. Qualify messaging as a separate number, compliance, application and order workflow.
Obtain the connection record before choosing a template
The reviewed public pages do not define a universal authentication or registration method. Obtain the current provider-issued connection record before configuring digest credentials, source-IP trust, registrar, proxy, transport, Contact, expiry or firewall policy.
For one authorized call in each direction, preserve resolver output, source and destination addresses, SIP and authorization identities, challenges, Request-URI, identity headers, responses and the first PBX route. A successful portal login, REGISTER or OPTIONS response is not equivalent to completed bidirectional calling.
Separate DID controls from accepted number routing
The product page documents local and international DIDs plus direct DID and routing changes. These are control-plane capabilities rather than proof of current inventory, portability, route activation or the format delivered to the PBX. Retain the exact number, country, legal entity, order or port record, activation event and observed Request-URI and identity headers.
After cutover, test inbound calls from independent networks and outbound identity under an approved plan. Do not retire a previous path solely because the number appears in the new portal.
Turn redundancy and burst language into testable limits
Broadvoice advertises built-in redundancy, failover, on-demand channels and bursting. Preserve the ordered route targets, priorities, health method, failure responses, detection and restoration timers, established-call treatment, subscribed capacity, burst terms and any call-start-rate limit.
Exercise new-call failure and recovery separately from established-call behavior. Run only an approved bounded load test; a low-volume call, a status-page component or marketing language does not establish the production ceiling or resilience result.
Keep media, fax and protection unresolved until specified
The reviewed pages do not publish a universal codec, DTMF, RTP, T.38, TLS or SRTP contract for the selected trunk. Obtain the current technical specification and configure only overlapping PBX and service methods.
Preserve offer and answer SDP, telephone-event mapping, RTP endpoints, decoded result, transport, certificate validation and negotiated media protection where applicable. Secure-connectivity wording does not prove protected signaling or media, and a separate Virtual Fax component does not prove T.38 on the trunk.
Qualify emergency, messaging, operations and price separately
Confirm emergency-calling entitlement, number-to-location mapping, callback identity, outage alternative and a provider-approved validation workflow for every site; never place an uncoordinated emergency call. Treat SMS or MMS as a separate number, sender-registration, compliance, application and commercial workflow.
Reconcile the current addendum and signed order with channels, burst treatment, minutes, destinations, numbers, toll-free service, taxes, fees, term, renewal, cancellation, portal roles, monitoring, maintenance, escalation and retention. Public support, status and pricing surfaces are discovery evidence, not proof of one account or an observed response.
Sources & applicability
Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.
- Broadvoice SIP Trunking ↗
- Broadvoice master service agreements ↗
- Broadvoice Elastic SIP Trunking Addendum ↗
- Broadvoice SIP trunking portal ↗
- Broadvoice contact and support ↗
- Broadvoice platform status ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.