Map LES.NET service objects before interpreting a call
LES.NET publishes SIP trunks, local DIDs, toll-free numbers, outbound termination, conferencing, fax-to-email and messaging as separate service concepts. Record the account, redacted trunk identity, outbound permission, caller-ID setting, DID, selected destination and ordered channel model before testing one transaction.
An unlimited count of trunk objects is not unlimited active calls, minutes or call starts. A paid account, saved trunk, assigned DID and successful call remain separate checkpoints.
Documented service facts
Reviewed 2026-10-23. Compare SIP trunk services →
Authentication
Not verifiedThe public pages expose outbound permission and caller-ID controls but do not establish digest, source-IP or another universal trunk-authentication method. Use the current account handoff.
SIP registration
Not verifiedThe reviewed sources do not establish REGISTER, a registrar, Contact expiry or static delivery as universal. A missing registration indicator is not a fault until the account model is known.
Inbound delivery
DocumentedA local DID can route to a phone system or call forward to another destination. Preserve the selected mode, exact redacted destination and observed provider attempt.
Inbound failover
Not verifiedCall forwarding is a selectable route, not documented failure-triggered advancement. Timeout, response handling, restoration and active-call survival require account instructions and controlled tests.
Number and regional availability
Not verifiedLES.NET states that local DIDs cover thousands of Canadian and US cities and that porting is available. Current inventory, locality, portability and order eligibility remain number-specific.
Audio codecs
Not verifiedThe reviewed public pages do not publish a current codec, packetization or transcoding matrix. Preserve SDP and packets for the selected route.
T.38 fax
Not verifiedFax-to-email is listed as a separate service; the sources do not establish T.38 or fax-over-audio behavior on a trunk.
Signaling and media encryption
Not verifiedFraud-detection language does not establish TLS, SRTP, PBX hardening or acceptance of one call. Confirm each signaling and media leg.
Concurrent calls and call starts
DocumentedThe portal distinguishes unlimited IP trunk objects from four-channel metered and two-channel unmetered DID labels. Confirm the current order, direction and rejection behavior.
Emergency calling
Not verifiedThe portal labels 911 as included but does not establish activation, eligible locations, civic-address validation, identity, callback or an approved test procedure.
Pricing model
DocumentedLES.NET publishes Canadian-dollar account, DID, usage, conferencing and fax components. Treat them as dated public snapshots and obtain a current order including taxes and optional services.
Administration and support
DocumentedPublic materials describe real-time DID ordering and activation, routing choices, support tickets and weekday office hours. These are not an SLA or incident result.
SMS and MMS
Not verifiedThe DID page says DIDs are SMS enabled, while the public pages do not establish exact number eligibility, SMS or MMS direction, registration, throughput, retention, access method or charges.
Trace each DID to its selected destination
The local-DID page says a number can route directly to a phone system or call forward to another destination. Preserve which mode is selected, the exact redacted destination, effective time, provider attempt, customer-edge receipt and PBX route match.
A selectable call-forward destination is not evidence of failure-triggered failover. The reviewed public sources do not define destination priority, timeout, advancing SIP responses, restoration or active-call survival.
Keep trunk objects and DID channels separate
The public portal describes unlimited IP trunk objects while labeling metered DIDs with four channels and unmetered DIDs with two. Treat those as product-page statements for distinct objects, not an account-wide capacity promise. Confirm the current order, number, direction, concurrent-call entitlement and rejection behavior.
A portal channel label is not measured capacity or calls per second. Preserve the first rejection, provider record, PBX channel inventory and release timing for the same call.
Verify outbound permission, identity and response independently
The voice page says an account can enable or disable outbound calling and manage caller ID. The termination page says outbound SIP traffic passes through LES.NET routing to upstream carriers. Preserve the PBX-selected trunk, destination, From and asserted identity, first provider response and final call result.
The public pages do not establish digest, source-IP authorization, REGISTER, registrar, Contact expiry or one mandatory PBX object model. Obtain the current account handoff rather than inferring it from a generic template.
Qualify media, security and adjacent features separately
The reviewed public pages do not publish a current codec matrix or establish TLS, SRTP or T.38 on the trunk. Preserve signaling transport, SDP offer and answer, selected codec, DTMF method and packets in both media directions. Fraud-detection language does not prove encryption, PBX hardening or that one attempted call was accepted.
Portal labels for 911, SMS/text messaging and fax-to-email belong to separate workflows. Confirm number and location eligibility, activation, callback, messaging direction, application access, fax delivery and approved tests independently.
Version pricing, support and acceptance evidence
LES.NET states that its published prices are Canadian dollars and lists account, DID, usage, conferencing and fax components. Treat each value as a dated public snapshot; obtain a current order for number inventory, setup, rental, usage, porting, optional services, taxes and regulatory charges.
A support-ticket path and weekday office hours are not an SLA. Record the portal state, PBX evidence, provider case, response time and correction separately. No account, call, media, emergency, message, fax or support result was tested for this guide.
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.