Freeze one direction, number and transaction
Record local and UTC time, direction, account, redacted trunk, DID, inbound destination mode, outbound permission, caller identity, channel symptom, SIP Call-ID, first response or timeout, SDP and media result. Redact credentials and personal numbers before sharing evidence.
Classify the first divergence: wrong trunk, outbound disabled, identity rejected, DID routed elsewhere, forwarding selected, channel limit reached, provider attempt absent, PBX rejected, call answered without media or adjacent feature not provisioned.
Separate the trunk object from the DID channel label
Confirm the trunk selected by the PBX and the DID product attached to the account. Compare the ordered channel model with observed simultaneous calls and the exact response on the next attempt. Preserve start and release timestamps.
Do not convert the public unlimited-trunk-object label into unlimited calls or call starts. Change capacity only after the current account order and observed rejection identify the responsible limit.
Trace the DID destination before changing the PBX
Confirm whether the DID points to the phone system or forwards to another telephone destination. Record the saved redacted value, effective time, provider attempt, customer-edge receipt and PBX route match for the same Call-ID.
A saved destination or real-time activation label proves portal state only. It does not prove the expected edge received an INVITE, the PBX matched the intended route or a forwarding rule is failure-triggered.
Follow outbound permission, identity and the first response
Verify that outbound calling is enabled for the selected trunk and preserve the exact destination plus From and asserted identity values. Correlate the first LES.NET response with the PBX-selected object and any later upstream result.
Do not invent credentials, registration or source-IP rules from a brand-level example. The reviewed public pages do not establish one universal authentication or binding model; use the current redacted handoff for the account.
Prove answer and media beyond signaling
Preserve the request, provisional and final responses, SDP offer and answer, negotiated codec, DTMF method, firewall decision and packets in both directions. A provider SIP response or fraud-detection statement is not proof of final answer, decoded audio, security or a completed downstream call.
Do not open unrestricted signaling or media ranges to hide an unknown handoff. Use the observed transaction and provider-approved account instructions to narrow the correction.
Correct one owner and retest the original symptom
Change only the demonstrated trunk permission, caller identity, DID destination, forwarding state, channel entitlement, PBX route or media boundary. Record prior and new values, approval, effective time and rollback, then repeat the same authorized call.
Test 911, SMS, porting, fax-to-email and outage behavior only with the exact provisioned feature and approved procedure. One successful call does not establish pricing, failover, availability, compatibility or support performance.
Sources & applicability
Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.
- LES.NET voice and SIP trunking ↗
- LES.NET customer portal and public service details ↗
- LES.NET service catalogue ↗
- LES.NET local DID service ↗
- LES.NET outbound SIP termination ↗
- LES.NET outbound rate directory ↗
- LES.NET company and currency information ↗
- LES.NET contact and support ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.