Name the ordered service before choosing a PBX template
AireSpring publishes Local SIP Trunking terms and a separate Long-Distance SIP Trunking product. The Master Service Agreement defines Local SIP Trunking as routing between the customer's IP connection and the public telephone network and delivering the service to a gateway or IP-PBX using SIP. Preserve the quote, service schedule, account worksheet, service address, circuit relationship and exact product name before importing a configuration example.
The reviewed public sources do not establish one universal PBX authentication or REGISTER workflow. Obtain the assigned signaling hosts, ports, transport, source-address scope, credentials if any and inbound delivery model from the account documentation. A configured trunk object, reachable host, authorized request and completed call are different evidence states; do not infer one from another.
Documented service facts
Reviewed 2026-09-29. Compare SIP trunk services →
Authentication
Not verifiedThe reviewed public SIP Trunking page and data sheet do not establish a universal customer authentication model, credential format, source-IP policy or SBC trust boundary. The Local SIP Trunk terms describe routing between the customer's IP address and AireSpring, but that is not enough to infer IP-only authorization for every ordered product. Obtain the implementation worksheet and exact permitted sources before choosing a PBX template.
SIP registration
Not verifiedThe reviewed public material does not say that the ordered SIP trunk registers, nor does it document a registrar, username, expiry or Contact behavior. Do not wait for a registration indicator or create credentials unless the current implementation record requires them. Preserve the ordered service, handoff, assigned hosts, SBCs and provider confirmation.
Inbound delivery
DocumentedThe Local SIP Trunk terms describe inbound and outbound service through AireSpring-assigned or ported telephone numbers, with traffic delivered to the customer's gateway or IP-PBX over SIP. This does not establish the Request-URI format, asserted identity, accepted source set or routing object for an account. Trace one authorized number through the provider route, exact SIP identity and PBX destination.
Inbound failover
Not verifiedThe general data sheet advertises geo-redundant network failover, while the separately named Long-Distance SIP Trunking service documents Direct Termination Overflow and flexible routing. The reviewed material does not establish that those portal controls, triggers or destination types apply to every Local SIP Trunk order. Obtain the exact service design and test new-call failover with approved destinations, timing and rollback.
Number and regional availability
DocumentedAireSpring's current product page lists DIDs, toll-free service, number porting and international calling, while the Local service terms limit use to numbers supplied by or ported to AireSpring. These statements do not prove inventory, portability, address eligibility or installation interval for a requested number. Obtain a dated orderability and port result for every location.
Audio codecs and DTMF
Not verifiedThe current product page advertises HD audio where available, but the reviewed public materials do not define the exact codec list, DTMF mode, packetization, transcoding or downstream PSTN behavior for an account. Confirm the ordered media profile and inspect the actual SDP offer, answer and telephone-event payload on authorized calls; an HD-audio headline is not a negotiated result.
T.38 fax
Not verifiedThe reviewed SIP Trunking product, data-sheet and Local service terms do not establish T.38, G.711 fax pass-through or an acceptance workflow. AireSpring publishes separate POTS-replacement and device material, but those capabilities are not transferred to this trunk. Qualify fax independently for the exact number, gateway, direction, document set, switchover and fallback.
Signaling and media encryption
DocumentedThe current product page and data sheet list TLS and SRTP as available encryption options. The separately named Long-Distance service also advertises TLS and SRTP. Verify the exact ordered service, transport, hostname, certificate chain and peer validation, SRTP profile, keying method and downgrade behavior. Published availability does not prove that a completed call used protected signaling and media.
Concurrent calls and burst
DocumentedAireSpring's current Local SIP Trunk terms say each trunk enables one concurrent call and may have multiple DIDs, while the current product page advertises scalable capacity. The reviewed pages do not establish the ordered trunk count, calls-per-second limit, burst behavior, rejection response or Long-Distance capacity. Preserve active-call channels and call-start rate as separate contractual and operational limits.
Emergency calling
DocumentedThe product page lists E911, and the current service terms require the telephone number associated with the registered address in the SIP From URI user part for SIP Trunking 911. The terms also describe power, broadband, address and routing limitations. Confirm eligibility, exact number, authorized outbound identity, validated civic address, callback route and provider-approved test method; never place an uncoordinated live emergency test.
Pricing model
Not verifiedThe current product page describes flexible pricing but does not publish a complete account quote. Older state tariffs and unrelated Long-Distance rate descriptions are not a current universal price. Obtain dated terms for trunks, channels, directions, destinations, numbers, porting, E911, failover, encryption, taxes, support, commitment, renewal and termination.
Administration and support
DocumentedAireSpring identifies managed service and support paths, while the Long-Distance page separately advertises routing controls and Direct Termination Overflow. Preserve the quote, order, product name, implementation worksheet, assigned endpoints, redacted trust inputs, change timestamps, ticket and call identifiers. Do not infer portal access or a routing control from a different product page.
SMS and MMS
Not verifiedThe reviewed SIP Trunking product, data sheet and Local service terms do not establish SMS or MMS entitlement on trunk numbers. Voice-number service does not prove messaging eligibility, registration, consent controls, API delivery, throughput, retention or fees. Verify a separately identified messaging product and each exact number before representing support.
Prove DID ownership and the inbound route
The agreement says Local SIP Trunking may have multiple direct-inward-dial numbers and that only telephone numbers provided or ported by AireSpring can be used with the service. Record the ordered trunk, assigned DID, service address, expected Request-URI or called identity, provider source scope and intended PBX destination before testing.
Follow one authorized inbound call across the provider identifier, Request-URI, To and any Diversion or History-Info values, PBX match and final destination. Keep number assignment, number port completion, trunk reachability and route selection separate. A successful outbound call does not prove inbound delivery, and a DID visible in an account record does not prove the PBX accepted the expected identity.
Treat media and protection as negotiated evidence
AireSpring's current product page and dated data sheet advertise high-definition audio where available plus TLS and SRTP options. Those statements are capability and ordering inputs, not proof that a particular call negotiated a wideband codec, TLS signaling or protected media. Confirm the ordered option, assigned hostname, certificate name and trust chain, transport, peer validation, SRTP profile, keying and fallback behavior on the actual carrier leg.
Capture a bounded SIP and RTP trace for an authorized call and retain the offer, answer, selected codec, packetization, RTP endpoints and telephone-event payload. The reviewed sources do not establish a universal codec list, DTMF mode, transcoding policy or T.38 workflow. Do not transfer analog fax or another AireSpring product's capability into this SIP trunk record.
Separate concurrency, call starts and failover
The Local SIP Trunking terms say each trunk enables one concurrent call and can have multiple DIDs. Treat that as an active-call unit for the ordered Local service, not as a calls-per-second allowance or a promise about an account's total purchased trunks. Obtain the trunk count, shared or directional behavior, call-start limit, burst response and rejection code before a bounded authorized capacity test.
The August 2023 data sheet markets geo-redundancy and failover, while the separate Long-Distance page describes DTO and routing choices. Neither establishes one universal customer-destination order, health probe, failure trigger, recovery time or established-call survival for every Local order. Obtain the exact topology and test procedure; record only whether a new call used the expected alternate path, not that an established call survived.
Bind emergency identity and commercial claims to the account
The Master Service Agreement ties emergency routing to the address registered for the service and says the user part of the outbound From URI must identify the callback number. It also documents limitations involving address accuracy, relocation, power, broadband and network outages. Preserve every eligible number, validated civic address, outbound identity, callback route, change owner and provider-approved non-live test method. Do not place a live emergency call without provider and local authorization; maintain an independently tested fallback.
The product page markets flexible and scalable pricing, number porting, toll-free service and international calling, but it does not establish a quote, number availability, destination permission, fraud control, support commitment or contract for a particular account. Obtain dated terms for channels, usage, numbers, porting, emergency service, international access, taxes, commitments, renewal and termination. The reviewed sources do not establish trunk-number messaging or fax entitlement. No account, trunk, call, failure case, emergency procedure, commercial term or availability result was tested for this guide.
Sources & applicability
Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.
- AireSpring SIP Trunking ↗
- AireSpring SIP Trunking data sheet, August 2023 ↗
- AireSpring Master Service Agreement ↗
- AireSpring Long-Distance SIP Trunking ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.