Identify the ordered product, site and exact handoff
Start with the accepted TPx order, legal customer, site, service address, trunk or group, enabled features, project record and activation. UCx SmartVoice SIP Trunking is not the same evidence object as a fully hosted UCx with Webex seat, a Webex add-on, PRI, CAS, ordinary Internet access or managed SD-WAN.
TPx documents a native SIP handoff to the customer LAN as one connectivity choice, alongside PRI and CAS for traditional PBXs. Preserve the exact demarcation and customer-edge ownership instead of selecting a configuration from the public brochure.
Documented service facts
Reviewed 2026-10-29. Compare SIP trunk services →
SIP authentication
Not verifiedReviewed public records do not publish one universal registration, IP-authentication, username, password, source-address or identification model. The account implementation record and loaded edge govern.
SIP registration
Not verifiedA native SIP handoff is documented, but the public sources do not establish whether one order registers, peers by address or uses a provider-managed gateway.
DIDs and inbound delivery
DocumentedNationwide numbers, DID features and several forwarding controls are documented. Assignment, activation, provider attempt, delivered called value, PBX route and answer remain unverified.
Forwarding and continuity
DocumentedCFNR, Trunk Group Call Forwarding, Standard DTO, Enhanced DTO and managed-SD-WAN active/active continuity are distinct. Entitlement, trigger, alternate answer, established-call survival and restoration remain unverified.
Access and handoff
DocumentedTPx describes private IP, existing bandwidth, managed SD-WAN and native SIP, PRI or CAS handoffs. The ordered site, demarcation, transport, activation and observed route govern.
Codecs and media
Not verifiedReviewed records do not publish one universal codec, packetization, DTMF, encryption or transcoding profile. Offer, answer, packet directions, decoding and audibility remain unverified.
Fax
Not verifiedThe reviewed UCx SmartVoice records do not establish T.38, passthrough, fallback, gateway requirements or completed-page behavior for one order.
Security and credential custody
Not verifiedProvider materials use secure-service language, but do not establish one edge-hardening, certificate, TLS, SRTP, credential or firewall policy. Observed protection remains deployment-specific.
Channels and call paths
DocumentedThe product page describes one channel as one call path. Ordered paths, active dialogs, attempts, call starts, bandwidth and PBX limits remain separate; no universal burst or call-start ceiling was verified.
911 location and identity
DocumentedTPx requires accurate phone-number, location and caller-ID records and documents power and access dependencies. Eligibility, effective update, route, callback and approved validation remain unverified.
Price and availability
Not verifiedReviewed public sources do not establish one complete quote. Access, channels, features, DTO, SD-WAN, numbers, usage, support, taxes, term, serviceability and activation remain order-specific.
Portal, status and support
DocumentedTPx publishes case, portal, phone, escalation and status paths. Portal rows, notices, cases, provider findings and verified restoration remain separate evidence.
SMS and MMS
Not verifiedThe Webex add-on brochure mentions messaging, but that does not establish SMS or MMS eligibility, consent controls, sender registration, throughput, retention or pricing for trunk DIDs.
Keep access, transport and application layers separate
The current product material describes delivery over TPx private IP access or existing bandwidth, and the brochure describes managed SD-WAN with mixed transports. Record the ordered access, each circuit owner, IP or routing evidence, SD-WAN policy, gateway, LAN and PBX separately.
Dynamic bandwidth allocation, secure transport and 100% uptime SLA language are provider claims. They do not prove available bandwidth, packet treatment, failover convergence, call continuity, the applicable service schedule or an achieved SLA for one site.
Bound channels, call paths and observed capacity
The product page explains a SIP line or channel as one call path within a larger trunk. Retain ordered channels or call paths, active dialogs, offered attempts, call starts, PBX resources, bandwidth, provider response and completed calls as different quantities.
The brochure uses high-capacity and scalability language, but does not publish one universal call-start rate, burst ceiling, codec plan or PBX limit. Do not generate production load or infer capacity without an ordered ceiling from marketing language.
Separate DID forwarding, trunk forwarding and DTO
The DID feature guide documents Call Forwarding Not Reachable for an outage or All Call Paths Busy condition, with features purchased and assigned before use. The current brochure separately describes per-DID forwarding and Trunk Group Call Forwarding, while TPx support distinguishes Standard Direct Trunk Overflow from Enhanced DTO with per-DID routing.
Record feature entitlement, scope, destination, trigger, portal, notification, provider action, alternate alert and answer separately. A saved destination or alert is not proof that the affected call used it.
Limit continuity claims to the ordered design
TPx describes active/active continuity when managed SD-WAN and more than one transport are part of the design. That is distinct from network-level path selection, Call Forward Not Reachable, Trunk Group Call Forwarding, Standard DTO and Enhanced DTO.
Preserve which service detected which condition, the observed path change, each SIP attempt and the final route. Do not infer that an established call survived, every DID shared the same fallback, the customer PBX remained reachable or restoration was complete.
Bind 911 to number, location, identity and dependencies
The TPx 911 addendum requires accurate location, address and caller-ID information for each telephony device and warns that moves, power loss and service disruption can affect emergency calling. Keep eligibility, assigned number, registered dispatchable location, callback identity, PBX route, power, access and effective update separately observable.
The document describes a broadband failover connection as reducing disruption likelihood, not as a guarantee. Use only the provider-approved non-live validation process; never place an uncoordinated live emergency call.
Preserve support, status, finding and restoration evidence
TPx publishes customer-portal case management, phone support, outage escalation and a systems-status page. Retain the public notice, affected account and site, case number, sanitized artifact, provider finding, action and verified ordinary-call restoration as different records.
A public status item does not prove one customer is affected. A case, escalation response target or cleared notice does not prove that signaling, routing, media, forwarding and emergency records all recovered.
Sources & applicability
Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.
- TPx — UCx SmartVoice SIP Trunking product page ↗
- TPx — UCx SmartVoice SIP Trunking brochure ↗
- TPx — SmartVoice user guides ↗
- TPx — SmartVoice PRI, CAS and SIP DID Features Guide ↗
- TPx — Introduction to Direct Trunk Overflow ↗
- TPx — 911 for SmartVoice and iPBX SIP Trunking Addendum ↗
- TPx — customer support and escalation paths ↗
- TPx — systems performance status ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.