Keep SIP Trunking distinct from adjacent Momentum services
Momentum positions SIP Trunking as PSTN connectivity for an existing legacy or IP PBX, then separately lists Cloud Voice, Teams Phone, SD-WAN, collaboration and other services. An adapter can also present analog or PRI toward an older PBX. These portfolio relationships do not make their identities, features, security controls, failover or price interchangeable.
Record the exact ordered product, site, access, adapter, PBX or SBC, numbers, call paths, routing and signed options. Do not import cloud-PBX, Teams, messaging, fax or managed-network capabilities into the trunk merely because they can be sold together.
Documented service facts
Reviewed 2026-10-07. Compare SIP trunk services →
SIP authentication
Not verifiedThe reviewed public product, datasheet, feature and legal pages do not publish one universal digest, source-IP, mutual-TLS or certificate-authentication model. Obtain the implementation record for the exact order and preserve realms, credentials, accepted addresses, SBC ownership and secret-handling policy without exposing secrets.
SIP registration
Not verifiedThe public materials establish a service for an existing PBX but do not define one REGISTER, static-peer, refresh, proxy, DNS or failover-registration workflow for every deployment. Use the provider-issued turn-up document and observed signaling for the ordered site rather than importing a recipe from another Momentum service.
Inbound delivery
DocumentedMomentum advertises global number coverage, local and toll-free number portability, inbound and outbound service, DIDs and custom routing. These are portfolio and ordering capabilities, not proof of number availability, port acceptance, one delivered identifier format or one PBX destination rule. Preserve the exact number inventory, port state and delivered headers.
Routing and failover
DocumentedThe current materials advertise geo-redundant infrastructure, multi-site deployments, custom routing and redundant solution options. They do not establish that a particular order includes diverse customer access, automatic alternate destinations, retryable responses, a restoration sequence or established-call survival. Capture signed routing policy and run an approved new-call failure test.
Number and regional availability
DocumentedMomentum advertises global number coverage and domestic calling, but public coverage language does not establish serviceability, customer eligibility, number inventory, portability or regulatory permission at a particular address. Obtain dated serviceability and port responses and keep them separate from calling-plan scope.
Audio codecs
Not verifiedThe reviewed sources do not publish one universal codec, packetization, DTMF, RTP-addressing, transcoding or media-anchoring profile. Obtain the current interface specification and preserve SDP offer, answer, selected codec, DTMF method, RTP endpoints and decoded audio for each relevant leg.
T.38 fax
Not verifiedThe reviewed SIP Trunking sources do not establish T.38 entitlement, G.711 pass-through requirements, redundancy, gateway behavior, page limits or support for one fax path. Do not transfer analog, PRI, cloud-fax or adapter capability into this record; validate the exact design and retain delivery evidence.
Signaling and media encryption
Not verifiedCarrier-grade, managed-network and reliability language does not establish SIP TLS, certificate validation, SRTP, keying, media encryption or end-to-end protection. Map every signaling and media hop, then confirm ordered controls and inspect negotiation on the accepted deployment.
Concurrent calls and call starts
DocumentedMomentum's older feature sheet describes shared concurrent call paths, while current material advertises on-demand scaling and suitability for high call volumes. Purchased paths, active calls, call attempts per second, route limits, burst allowance, PBX and SBC resources, and access bandwidth remain separate quantities. Confirm the current order and test plan; no public claim is treated as measured capacity.
Emergency calling
DocumentedMomentum advertises 911 and E911 functionality. Its emergency terms bind routing to a registered address and warn that VoIP 911 can differ from traditional service. Preserve the assigned number, accepted dispatchable location, update ownership, power and access dependencies, callback path and provider-permitted test result for every site.
Pricing model
DocumentedCurrent material advertises usage-based or unlimited choices and says unlimited service is subject to the Acceptable Use Policy; an older feature sheet shows multiple package patterns and six-second billing. These are not a current account price. Use a dated quote, service order, agreement and AUP for paths, DIDs, ports, usage, international and toll-free traffic, emergency service, access, support, taxes, renewal and cancellation.
Administration and support
DocumentedMomentum advertises 24x7 support, coordinated installation, subscriber-management tools and managed network connections. The public material does not establish one portal, role model, change workflow, demarcation, response target or escalation path for every order. Preserve named owners, current contacts, maintenance windows, acceptance criteria and signed support terms.
SMS and MMS
Not verifiedThe reviewed SIP Trunking sources do not establish SMS or MMS entitlement on trunk numbers, sender registration, API access, throughput, webhook security, retention or price. Keep messaging and adjacent Cloud Voice, Teams Phone and collaboration products outside the trunk record unless the signed order explicitly includes them.
Separate call paths, call starts and network capacity
An older Momentum feature sheet describes shared concurrent call paths, while the current product and datasheet emphasize on-demand scaling and high-volume use. Treat purchased paths, active calls, attempted call starts, burst allowance, route limits, PBX channels, SBC resources, codec bandwidth and access utilization as separate quantities.
Scaling language is not a calls-per-second result or acceptance test. Preserve the current order and implementation limits, model representative busy-hour behavior, and validate only within an approved plan.
Turn number coverage and custom routing into records
Momentum advertises global number coverage, local and toll-free portability, multi-site deployment and custom routing. Those statements do not establish serviceability, inventory, port acceptance, one header format, one retry policy or one alternate destination.
Maintain a dated inventory for every number, port status, authorized identity, inbound route, outbound route and after-hours or failure destination. Record the response codes and timers that actually trigger alternate routing, and keep new-call recovery distinct from survival of established media.
Bind E911 to the accepted location and dependencies
Momentum advertises 911 and E911 support. Its emergency-services terms describe a registered address and warn that VoIP 911 can be affected differently from traditional service. A marketing statement therefore does not establish the correct dispatchable location, number, callback route, power, access or provider acceptance for one endpoint.
For each site, preserve the signed emergency terms, assigned number, submitted and accepted location, update owner, user notice, failure behavior and provider-permitted validation. Never infer emergency readiness from an ordinary completed call.
Treat reliability, support and price as order-specific
Geo-redundant network, 24x7 support and managed-installation claims describe the offer, not the customer's complete service chain or response entitlement. Confirm the demarcation, access diversity, maintenance, escalation, response and credit terms in the current agreement. Customer power, LAN, PBX, SBC and last-mile dependencies remain separate.
Current material advertises usage-based or unlimited choices, with unlimited use subject to an AUP; an older sheet describes several package patterns. Use the dated quote, service order, agreement and AUP rather than copying a generic price model. The reviewed public sources do not establish universal authentication, registration, codecs, DTMF, T.38, TLS, SRTP, SMS or MMS. No live account, trunk, call, media, fax, protected path, failover event, emergency workflow, message, availability, price or support response was inspected or tested for this guide.
Sources & applicability
Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.
- Momentum SIP Trunking ↗
- Momentum SIP Trunking datasheet ↗
- Momentum SIP Trunking packages and feature sheet ↗
- Momentum emergency-services dialing terms ↗
- Momentum legal and service-agreement index ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.