Start with the ordered voice service, not the portfolio headline
Pure IP presents SIP trunking, PSTN replacement, platform integrations, managed SBC services and optional resilience capabilities across one portfolio. Record the exact ordered service, countries, numbers, customer and provider demarcations, access path, SBC owner and support model before selecting a PBX template.
A global account or portal login is not the SIP handoff. The reviewed public pages do not establish one universal registrar, digest realm, peer list, transport, codec or protection profile, so the implementation worksheet and loaded configuration remain the deployment evidence.
Documented service facts
Reviewed 2026-10-10. Compare SIP trunk services →
SIP authentication
Not verifiedPure IP publicly describes Internet-based SIP trunking, cloud SIP infrastructure and managed or dedicated SBC options, but the reviewed public pages do not define one universal source-IP, digest, certificate or registration identity for every service. Treat the order, implementation handoff and loaded peer configuration as authoritative; keep a portal login separate from a SIP credential.
SIP registration
Not verifiedThe reviewed public material does not establish that every Pure IP trunk uses REGISTER, a common registrar, a shared expiry or one health indicator. Do not invent those values. Record whether the selected service is static peering, registration-based or platform-connected, then prove the configured peer, current transaction and authorized call independently.
Inbound delivery
DocumentedPure IP describes PSTN replacement over SIP and number porting as part of migration. That establishes a service category, not the selected DID, ingress peer, called-number format, route or destination. Preserve one trace from carrier port state through the received INVITE and PBX match to final answer before retiring the former path.
Routing and failover
DocumentedPure IP publishes geo-redundancy, intelligent routing and failover options, while Hypernetwork is a separate optional US inbound-DID resilience service. Those statements do not establish the ordered alternate targets, triggers, timers, coverage, established-call result or restoration procedure. Map and test only the contracted path.
Number and regional availability
DocumentedPure IP currently advertises full PSTN replacement in more than 50 countries and flexible voice coverage in 137. This is portfolio-level evidence, not number inventory, portability, regulatory eligibility or serviceability for an address. Use a dated country, number and emergency-service qualification for every site.
Audio codecs and DTMF
Not verifiedThe reviewed current public pages do not publish one codec, packetization, DTMF, early-media or transcoding profile for every Pure IP trunk. Obtain the interface specification for the selected service, then retain both SDP directions, decoded digit events and media evidence. A completed SIP dialog does not prove intelligible audio.
T.38 fax
Not verifiedThe reviewed generic SIP-trunk pages do not establish a universal T.38 profile, G.711 fallback, switchover sequence, redundancy method or device compatibility. Fax, alarms, lifts, paging and other specialist lines need their own inventory, supported gateway path and completed acceptance result before legacy service is removed.
Signaling and media encryption
Not verifiedCurrent pages describe secure infrastructure and managed SBC choices, but they do not define a universal TLS hostname, mutual-authentication rule, certificate chain, SRTP profile, cipher set or downgrade behavior for every trunk. Private or managed delivery is not by itself proof of protected signaling and media; verify each leg.
Concurrent calls and call starts
Not verifiedPure IP describes scalable channels, but the reviewed public pages do not establish one account entitlement, burst policy or calls-per-second limit. Keep purchased concurrent paths, call starts, SBC sessions, transcodes, access bandwidth, emergency reserve and alternate-path headroom as separate sizing inputs.
Emergency calling
DocumentedPure IP says emergency calling differs by country and is a major multi-country migration dependency. Portfolio availability does not establish the selected site address, caller identity, location update, callback, notification, outage behavior or approved test method. Bind every site and number to the applicable country process before cutover.
Pricing model
Not verifiedThe public material discusses cost and flexible scaling but does not establish the selected deployment total. Obtain a dated quote covering channels or usage, numbers, porting, access, SBC services, emergency calling, support, implementation, taxes, minimums, renewal, cancellation and parallel-running charges.
Administration and support
DocumentedPure IP exposes separate customer portals for account, SIP-trunking, support and monitoring functions, and its current service pages describe managed support. Record which portal and team owns orders, ports, numbers, routes, tickets, monitoring, emergency records and changes. A portal row or observability record does not replace PBX and packet evidence.
SMS and MMS
Not verifiedThe reviewed generic voice and SIP-trunk pages do not establish SMS or MMS eligibility, sender registration, throughput, retention or price for a Pure IP number. Qualify messaging as a separate country, number, platform and commercial service rather than inferring it from working voice.
Convert global coverage into site-and-number qualification
Pure IP currently advertises full PSTN replacement in more than 50 countries and flexible voice coverage in 137. Those figures describe the portfolio, not serviceability, number inventory, portability, regulatory eligibility or emergency support at a specific address.
Maintain a dated row for every site and number: country, number type, current range holder, port state, service address, emergency record, ingress target, outbound identity, owner and evidence date. Do not transfer availability from one country or platform integration to another.
Keep porting, cutover and final routing as separate states
Pure IP’s June 2026 enterprise migration guide separates estate audit, number-port planning, capacity sizing, parallel cutover and later retirement of legacy lines. A confirmed order, accepted port request, scheduled date, carrier-complete notice, new-provider inventory row and successful inbound call are different observations.
Use the paired ported-number diagnostic when traffic still reaches the former path or splits by originating network. Keep the old service available until the agreed validation set is complete; do not use decommissioning as a test.
Scope resilience to the purchased path
Pure IP publishes geo-redundancy, intelligent routing and failover options. Hypernetwork is separately described as an optional US inbound-DID resilience layer. Do not merge those statements into a universal dual-carrier or instant-failover promise.
Record primary and alternate targets, health signals, retryable outcomes, trigger and restoration logic, country and number eligibility, capacity and responsibility. Provider-core diversity, customer-access diversity, PBX survival and an established call are separate acceptance results.
Make emergency calling a country and location record
Pure IP identifies porting and emergency calling as country-specific dependencies in multi-country replacement. Preserve the applicable regulatory process, dispatchable or service address, callback identity, caller-ID mapping, internal notification, power and network dependency, and provider-approved validation method for each site.
A ported number, successful ordinary outbound call or portfolio emergency capability does not establish correct emergency routing. Maintain an independent alternative calling path during migration and outages.
Leave unresolved interface and commercial facts unresolved
The reviewed current pages do not define one generic Pure IP codec, DTMF, fax, TLS, SRTP, authentication, registration, channel, call-start, messaging or price profile. Obtain those values from the selected service documents and retain observed offer-answer, packet and application evidence.
Bind portals, support, monitoring, numbers, channels or usage, ports, access, SBC services, emergency calling, implementation, taxes, renewal, cancellation and parallel running to current account records. Provider-published scale, resilience and support language is not a VoIP.info availability, compatibility or performance result.
Sources & applicability
Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.
- Pure IP SIP Trunking guide ↗
- Pure IP PSTN Replacement ↗
- Pure IP global voice coverage ↗
- Pure IP enterprise SIP migration guide ↗
- Pure IP customer and partner portals ↗
- Pure IP Observability ↗
- Pure IP Hypernetwork ↗
- Pure IP multi-country PSTN replacement guide ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.