Freeze one call and the effective account contract
Record UTC and local time, direction, called and calling numbers, 8x8 or PBX Call-ID, expected trunk, current Statement of Work revision, Professional Services handover, recent support case, expected public source address, peer, transport, certificate name, media profile and number assignment. Capture the first response and elapsed time without editing the provider, firewall and PBX at once.
Classify the symptom narrowly: PBX waits for REGISTER; INVITE leaves from the wrong address; no digest challenge; repeated challenge; TLS or certificate failure; number is claimed but not assigned; 8x8 attempt never reaches the edge; PBX rejects the request; call reaches 200 but media or identity is wrong; or the issue began after a support-owned change.
Resolve SOW, interface reference and loaded PBX state
Compare the current SOW and support case with the linked interface specification and the PBX's effective configuration. Record differences in source identity, peer, authentication, registration, signaling transport, certificate trust, codec or media protection. Do not copy a generic 8x8 Work endpoint port or an older trunk example over a newer account assignment.
If the SOW is unavailable or ambiguous, stop before broad firewall changes and obtain the current values from 8x8. The public network page expressly scopes SIP-trunk signaling and media to the customized SOW; it is not evidence that every historical X Series trunk was migrated to one common profile.
Test source address, challenge response and REGISTER independently
Confirm the actual public egress address after NAT and compare it with the provider-applied address. Then inspect one outbound INVITE and any authentication challenge, preserving realm, username reference, nonce lifecycle and result without retaining a password or reusable response in shared evidence.
If the trunk follows the fixed no-REGISTER interface, remove the assumption that registration state must become available; do not blindly add a registration object. If the current SOW explicitly assigns another mechanism, follow that account record. Address authorization, digest success, accepted identity and call routing are still separate outcomes.
Prove number claim, trunk assignment and inbound delivery
In Admin Console, distinguish a claimed available number from the support-owned assignment to the X Series trunk. Retain the case identifier and effective time for assignment or removal. For an inbound failure, prove the number state and 8x8 trunk attempt before altering the PBX inbound route.
At the customer edge, match source, destination, Request-URI, To and asserted identity to the same Call-ID, then inspect endpoint identification and the first dialplan match. A number visible in inventory, a support case marked complete and a packet from 8x8 are three different observations.
Follow the assigned signaling and media profile
For SIPS, record DNS or assigned peer selection, TCP connection, TLS version, certificate chain, name validation and SIP exchange separately. For protected media, preserve SDP offer and answer, negotiated profile, keys only within authorized secure tooling, observed packet endpoints and decoded audio result. Never downgrade transport or open broad media ranges merely to make a test pass.
Keep endpoint and application port tables outside the trunk diagnosis unless the SOW explicitly adopts them. If standby Internet is involved, verify that the approved public identity and stateful policy survive the active-standby transition; do not assume active-active load balancing or provider failover.
Correct the first divergence and close the support loop
Change only the first demonstrated mismatch: provider-applied address, peer, SOW version, PBX registration assumption, digest identity, transport, certificate trust, number assignment, firewall scope, inbound match, caller identity or media policy. Provider-owned changes need an 8x8 case with before-and-after evidence and rollback; local changes need their own approval and validation.
Repeat controlled inbound and outbound calls, then verify expected signaling, answer, two-way media, DTMF when required, number presentation, billing record boundary, standby path and restoration separately. No 8x8 account, order, SOW, PBX, trunk, number, certificate, packet, media stream, bill, emergency workflow or live call was inspected or tested for this diagnostic.
Sources & applicability
Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.
- 8x8 SIP trunking interface specification ↗
- 8x8 X Series SIP Trunk FAQ ↗
- 8x8 Network Best Practices ↗
- 8x8 X Series upgrade impact ↗
- 8x8 Admin Console phone-number claiming ↗
- 8x8 Admin Console service and emergency addresses ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.