Freeze one call and the current order before changing a route
Record local and UTC time, exact product, service address, trunk and DID inventory, port state, expected normal and DTO destinations, portal route, active-call count, calling identity, provider source, customer destination, first response or timeout, PBX match and media result. Preserve the current order and implementation handoff with the snapshot.
Classify the first divergence: number not assigned or ported, wrong account route, unsupported control, unexpected capacity response, DTO invoked or skipped, no edge receipt, wrong PBX destination, or signaling success with missing media.
Resolve product and handoff mismatches first
Do not transfer the current Long-Distance page's routing and DTO language to every Local order, or treat dated marketing material as the current account interface. Confirm the exact service, assigned peers, customer addresses, transport, trust method, registration requirement, portal entitlement and change owner.
If the PBX expects registration but the implementation uses a fixed IP handoff, or permits the wrong source while the provider sends from another assigned peer, correct the implementation boundary before changing digits or media.
Prove number state, provider route and edge receipt in order
The Local terms require an AireSpring-supplied or ported number. Compare the current number record, completed port, active route, saved destination and change timestamp with the provider attempt. Then retain source and destination addresses, transport, Request-URI, To, asserted identity, Diversion or History-Info where present, Call-ID and response.
A number in inventory does not prove the port is active, a saved portal route does not prove it was effective for this attempt, and an accepted packet at the firewall does not prove that the intended PBX object matched.
Separate capacity, DTO and manual or scheduled rerouting
Compare the purchased Local trunk count with the active calls and the exact new attempt. Preserve the first SIP response or timeout before attributing the result to capacity. Then identify whether the account order documents DTO, manual routing, percentage allocation or time-of-day routing and whether the observed destination belongs to that control.
The public material does not establish one universal failure-code matrix, trigger, delay, retry order or restoration sequence. Do not manufacture a circuit outage or place emergency calls merely to test overflow.
Follow edge receipt through PBX routing and negotiated media
Once the INVITE reaches the customer edge, follow source authorization or registration, endpoint identification, context, normalized DID, first matching Asterisk or FreePBX route and final destination. Keep provider route selection and PBX route selection separate.
If signaling completes, compare the offer, answer, codec, DTMF payload, RTP endpoints, NAT translation, packet direction and decoded audio. TLS, SRTP and HD-audio availability are not proof of this call's negotiation or user experience.
Correct the earliest divergence and retest bounded scenarios
Correct only the demonstrated number, product, handoff, portal route, capacity, DTO, firewall, PBX or media mismatch. Retest an authorized normal call, the provider-approved alternate condition and restoration, recording the number, provider attempt, edge receipt, PBX destination, answer and media in both directions.
One exercise does not establish every failure trigger, active-call survival, capacity, availability, compatibility, emergency behavior or support outcome. No AireSpring account, route, call, DTO event, packet or media stream was inspected or tested.
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, revision May 12, 2023 ↗
- AireSpring Master Service Agreement ↗
- AireSpring Long-Distance SIP Trunking ↗
- AireSpring data-sheet index ↗
- AireSpring Top 10 Reasons for SIP Trunking infographic, revision July 5, 2022 ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.