Choose the static or dynamic service identity first
BCM One's September 2024 implementation guide separates PBXs with a static public IP from PBXs with a dynamic public IP. The dynamic model registers with an assigned username and password; the static model does not need to register for inbound delivery. Preserve the selected service model, public address ownership, source authorization, registration identity, expiry, assigned proxy and redacted credentials independently.
The guide uses legacy nexVortex hostnames alongside BCM One branding. Confirm the current account worksheet, DNS answers and support direction instead of replacing or retaining a hostname from memory. A successful REGISTER, an Active portal indicator, an authenticated outbound request and a completed inbound call are different evidence states.
Documented service facts
Reviewed 2026-09-28. Compare SIP trunk services →
Authentication
DocumentedThe September 2024 implementation guide separates static-public-IP service from credentialed registration. It says dynamic-public-IP PBXs require registration using the assigned username and password, while a static-public-IP PBX does not need to register. Preserve public-address ownership, source authorization, credentials and the selected service model separately.
SIP registration
DocumentedThe guide requires registration for dynamic public addresses and gives bounded expiry guidance, but says a static public address should not register for inbound delivery. A successful REGISTER, portal Active status and completed inbound or outbound call remain different evidence states. Confirm the current account worksheet and registrar before using the historical nexVortex hostnames in the guide.
Inbound delivery
DocumentedThe portal's Number Routing area assigns each DID or toll-free number to static-address or dynamic-registration delivery and controls the user part presented in the inbound Request-URI. Preserve the number, term type, IP or contact, translation value, delivered URI and PBX route independently; a portal entry does not prove PBX acceptance.
Inbound failover
DocumentedDisaster-Recovery Routing can forward an individually configured number to as many as three alternate locations, using telephone numbers or IP endpoints, after delivery to the intended location fails. The guide does not publish every detection interval, SIP response trigger or established-call behavior. Treat it as new-call routing and validate approved failure cases separately.
Number and regional availability
Not verifiedThe guide describes continental US and Canada outbound calling, DID and toll-free inbound service, international capability and number porting. It does not establish current inventory, portability, service eligibility or regulatory support for any requested address or number. Obtain a dated order and portability result for the exact account and location.
Audio codecs and DTMF
DocumentedThe guide lists G.711u and G.729a and specifies RFC 2833 telephone-event DTMF with payload 101 toward BCM One gateways. Its bandwidth figures are planning inputs, not measured call quality or account acceptance. Capture the actual SDP, packetization, RTP endpoints and digit events on authorized representative calls.
T.38 fax
DocumentedBCM One documents G.711u pass-through and T.38, recommends T.38, and explicitly calls fax over IP best effort. This is not a delivery guarantee. Qualify the exact number, direction, gateway, document set, initial audio path, T.38 switchover, redundancy, page count and fallback behavior.
Signaling and media encryption
Not verifiedThe reviewed BCM One guide documents UDP 5060, a TCP exception path, source-address and RTP firewall requirements, passwords and PBX hardening, but does not establish customer-facing TLS, certificate validation, SRTP or a downgrade policy for this service. Flowroute support articles describe a different BCM One-owned service and are not transferred to this record.
Concurrent calls and burst
Not verifiedThe guide advertises unlimited SIP trunk call paths but separately notes restrictions for broadcast and auto-dialer applications and recommends PBX-side maximums. It does not publish one account's call-start rate, fraud controls, fair-use terms, queueing or rejection behavior. Do not convert marketing language into infinite technical capacity; obtain dated contractual and operational limits before load testing.
Emergency calling
DocumentedThe guide links addresses to transmitted numbers, proxy identities or fixed public addresses and warns that incorrect mapping can reach the wrong emergency answering point. It documents 933 address readback from each location and separate support review for multi-site E911. Confirm the exact number, address, callback and provider-approved test process; 933 does not test a live 911 call or notifications.
Pricing model
Not verifiedThe reviewed guide and public legal index do not publish a complete current SIP Trunking quote. Obtain dated terms for call paths, usage, numbers, toll-free service, international calling, off-net disaster-recovery forwarding, E911, porting, taxes, support, restrictions, renewal and termination. A real-time billing portal is operational evidence, not a general rate card.
Administration and support
DocumentedThe portal manages service status, number routing, disaster-recovery destinations, port orders, E911 mappings and billing. The guide uses BCM One branding with legacy nexVortex service hostnames; preserve the current account worksheet, portal state, DNS answers, support confirmation and change timestamps rather than replacing hostnames from memory.
SMS and MMS
Not verifiedThe reviewed BCM One SIP Trunking implementation guide does not establish SMS or MMS on trunk numbers. Voice and toll-free service do not prove messaging eligibility, sender registration, consent management, API delivery, throughput, retention or fees. Verify the exact number and a separately identified messaging product before representing support.
Follow each number through inbound routing
BCM One's Number Routing area assigns each DID or toll-free number to static-address or dynamic-registration delivery. It can also translate the user part placed in the inbound Request-URI. Preserve the number, term type, selected public IP or registered contact, translated user, delivered Request-URI, PBX endpoint or context and final destination.
A portal route proves configured intent, not receipt or PBX acceptance. Use an authorized inbound call to correlate the provider call identifier, source and destination addresses, Request-URI, To and Diversion or History-Info fields where present, PBX match and user-visible result. Do not repair a route by broadly accepting arbitrary source addresses or called identities.
Separate provider redundancy from disaster-recovery routing
The guide documents DNS SRV and primary or backup proxy behavior for service-side redundancy. It separately documents Disaster-Recovery Routing for an individual number, with as many as three alternate telephone-number or IP destinations after delivery to the intended location fails. Record which layer selected the next target, the triggering response or timeout, order, timestamp and resulting destination.
Neither feature establishes every detection interval, SIP response trigger or the survival of an established call. Treat recovery routing as a new-call control unless dated account documentation and an authorized failure test prove more. Preserve a rollback and an independent calling path before testing.
Qualify media, DTMF, fax and the network edge
BCM One lists G.711u and G.729a and specifies RFC 2833 telephone-event DTMF with payload 101 toward its gateways. It primarily documents UDP signaling on port 5060, with a custom TCP path, and expects public addresses in SIP and SDP. Allow only the current first-party signaling and RTP scope, then capture negotiated SDP, RTP endpoints, packetization and digit events on representative authorized calls. Published bandwidth figures are planning inputs, not measured quality.
The guide documents G.711u pass-through and T.38 fax, recommends T.38 and labels fax over IP best effort. Qualify the exact number, direction, gateway, document set, initial audio, switchover, redundancy and fallback. The reviewed BCM One guide does not establish customer-facing TLS, certificate validation, SRTP or downgrade policy for this service. Flowroute documentation belongs to a different BCM One-owned service and is not evidence for this record.
Bind emergency service to the actual identity and location
The guide links emergency location to the transmitted number, proxy identity or fixed public address and warns that a wrong mapping can route a call to the wrong emergency answering point. It documents 933 address readback from each location and says multi-site deployments should review their design with BCM One. Preserve the eligible number, approved civic address, service model, outbound identity, callback path and current provider procedure for each site.
Use 933 only under the current account procedure and record the date, time, calling number and returned information. A correct readback does not test a live 911 call, dispatch, callback or notifications. Do not place a live emergency test without provider and local authorization, and keep an independently tested fallback.
Keep marketing, account limits and lifecycle evidence separate
BCM One describes unlimited SIP trunk call paths but also restricts broadcast and autodialer use and recommends PBX-side maximums. That phrase does not establish infinite active calls, call starts, fraud controls or acceptance under load. Obtain dated contractual and operational limits before a bounded load test. Likewise, continental US and Canada calling, DIDs, toll-free service, international capability and porting descriptions do not prove current inventory or eligibility for a specific number or address.
The reviewed implementation guide and public legal index do not provide a complete current quote or establish SMS and MMS on trunk numbers. Obtain dated terms for numbers, usage, toll-free service, disaster-recovery forwarding, E911, porting, taxes, support, restrictions, renewal and termination, plus separately identified messaging eligibility if required. No account, PBX, trunk, number, registration, route, call, media path, failure case, emergency call, message, price, availability or support response was tested for this guide.
Sources & applicability
Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.
- BCM One SIP Trunking and Implementation Guide, September 2024 ↗
- BCM One legal and service documents ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.