Identify the ordered product, region and operating relationship
NUSO lists SIP Trunking separately from UCaaS, Teams and Zoom integrations, messaging, fax, toll-free and other platform services. The current SIP Trunking page describes premise phone-system connectivity and access through public Internet, private networks or NUSO partner carriers. Preserve legal customer, partner or reseller, region, order, product, site, access, PBX or SBC boundary, portal tenant and enabled date.
A portfolio page, accepted order, portal row, loaded trunk object and completed call are separate evidence. Do not transfer Cloud PBX, messaging, fax, Teams, Zoom or carrier-platform behavior into a premise SIP-trunk order.
Documented service facts
Reviewed 2026-10-29. Compare SIP trunk services →
SIP authentication
Not verifiedPublic records do not establish one universal registrar, credential, source-IP model, peer set, port or certificate contract. The accepted implementation record and provider confirmation govern.
SIP registration
Not verifiedThe product connects premise systems but does not establish whether one order registers, trusts source addresses or uses another handoff. Loaded state and an accepted transaction remain unverified.
Numbers and inbound delivery
DocumentedNUSO documents local, toll-free, number inventory, activation and port tracking. Assignment, activation, delivered called value, route match and completed call remain unverified.
Failover and NUSOflex
DocumentedNUSO documents built-in failover and NUSOflex for inbound PSTN and local-service impairment. One order’s enrollment, trigger, alternate destination, action, established-call behavior and restoration remain unverified.
Access and serviceability
DocumentedNUSO describes public Internet, private-network and partner-carrier connectivity. Exact region, access, demarcation, serviceability, activation and routing require current order confirmation.
Codecs and media
Not verifiedReviewed public records do not publish one universal codec, packetization, DTMF or transcoding profile. Offer, answer, protected packets, decoding and audible media remain unverified.
Fax
Not verifiedNUSO lists IPFax separately. The reviewed SIP Trunking records do not establish T.38, passthrough, fallback or completed-page behavior for one trunk.
TLS, SRTP and customer boundary
DocumentedThe HIPAA page says SIP Trunking uses TLS and SRTP and places premise-system security with the customer. Peer validation, selected profile, fallback, custody and observed protection remain unverified.
Channels and fraud monitoring
DocumentedNUSO describes scalable channel allocation and monitoring of concurrency, calls per minute, daily totals and duration. One order’s allocation, thresholds, enforcement and observed capacity remain unverified.
E911 and location
DocumentedNUSO lists E911, but reviewed public records do not establish one number’s eligibility, registered location, identity, callback route or test method. Provider-approved non-live verification is required.
Price, order and availability
Not verifiedMarketing describes per-minute and bundled options without a complete account quote. Price, fees, taxes, availability, serviceability, commitment and activation are order-specific.
Portal, status and support
DocumentedNUSO documents management portals, provisioning, turn-up, support contacts and a network-status path. Portal rows, notices, tickets, findings and verified restoration remain separate evidence.
SMS and MMS
Not verifiedMessaging is listed as a separate platform service and subscription. A voice trunk or number does not prove messaging eligibility, registration, consent controls, API behavior, retention or price.
Keep access, channel allocation and call evidence separate
NUSO describes scalable channel allocation, flexible calling plans and local, long-distance and toll-free calling through one connection. Those statements do not publish one account’s channel count, calls-per-second limit, directional scope, peer set, bandwidth, codecs or overload response. Preserve purchased channels, active dialogs, new attempts, first responses, PBX resources and media load separately.
A visible portal allocation or successful registration does not prove provider admission, destination acceptance, answer or audio. Public, private and partner-carrier access also remain distinct handoffs with different demarcation and failure evidence.
Bound failover and NUSOflex to the affected call path
The SIP Trunking page lists built-in failover, while Platform Services describes NUSOflex for inbound voice calls traversing the PSTN and local inbound service impairment. Voice Services separately describes geo-redundant facilities and multiple paths. Record the ordered feature, eligible numbers, monitored boundary, trigger, alternate route, destination, event time, provider action and restoration.
A network-redundancy or AI-powered routing statement does not prove one account is enrolled, that an established call survives, that outbound calls reroute, or that the customer Internet and PBX remain reachable. Internal office calling during an Internet outage is a PBX capability question, not proof of provider failover.
Treat fraud monitoring as a signal, not a verdict
NUSO describes monitoring concurrent calls, calls per minute, daily totals and duration, with Cloud Attendant producing a per-call risk score and captured details for investigation. Preserve metric window, threshold, score, alert, affected call, reviewer, account action and final finding separately.
A high score, alert or temporary restriction does not by itself establish fraud, compromise or root cause. The public page does not publish one account’s thresholds, enforcement action, retention or appeal workflow; obtain those through authorized account and support records.
Verify TLS, SRTP, customer security and media independently
NUSO’s HIPAA page says SIP Trunking is delivered using TLS and SRTP and places the premise system and stored information under customer responsibility. Confirm the ordered peer names, certificate chain, trust policy, TLS version, SRTP profile, keying, fallback and customer-edge custody.
A TLS connection does not prove SRTP, and an SRTP offer does not prove selected protection, two-way packets, decoding or audibility. Public records reviewed here do not provide one universal registrar, authentication credential, source-address allowlist, firewall range, codec list or PBX template.
Keep numbers, emergency calling, portal and support bounded
NUSO lists E911, CNAM, CID, directory listing, number inventory, activation and port tracking, while its management portals support provisioning and turn-up. Preserve number order, port state, activation, caller identity authorization, emergency eligibility and registered location separately. Support contacts, a status page and a ticket are operational evidence paths rather than proof of outage scope or restoration.
Messaging is a separately subscribed service on Platform Services. Call metadata retained for troubleshooting or billing is not call content, and neither establishes messaging retention. Obtain dated commercial and availability terms rather than reproducing marketing language as a quote.
Sources & applicability
Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.
- NUSO — SIP Trunking product page ↗
- NUSO — Platform Services ↗
- NUSO — Voice Services and SIP Trunking ↗
- NUSO — HIPAA compliance and SIP Trunking security responsibilities ↗
- NUSO — customer support contacts ↗
- NUSO — technical support and network-status path ↗
- NUSO — policies, programme documents and customer-service contact ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.