Inventory trunks, DIDs and channels as different objects
LES.NET's public pages say an account can define multiple SIP trunks and describe an unlimited count of IP trunk objects. The same portal lists channel limits on DID products. Do not combine those statements into an unlimited-call claim: a configured trunk, an assigned number, an active-call allowance and a calls-per-second control are different records.
For each pilot, capture the redacted trunk identity, assigned DID, selected inbound destination, ordered channel model and any account-wide or directional limits shown in the current portal. The reviewed pages do not publish an account-wide active-call ceiling or calls-per-second limit.
Documented service facts
Reviewed 2026-09-27. Compare SIP trunk services →
Authentication
Not verifiedLES.NET's public voice page says an account can define multiple SIP trunks and control outbound calling and caller ID, but the reviewed pages do not identify the trunk's digest, source-IP or other authentication requirement. Confirm the exact account identity and authorization model before building a PBX object.
SIP registration
Not verifiedThe reviewed public pages do not establish whether a trunk uses SIP REGISTER, static delivery, a fixed contact or another binding model. Do not interpret a missing registration indicator as a fault until the actual portal record and provider instructions identify the connection method.
Inbound delivery
DocumentedLES.NET says local DIDs can route to a phone system or call forward to another number. Record the selected destination for each DID and keep direct SIP delivery separate from telephone-number forwarding; the page does not establish the SIP URI format or PBX configuration.
Inbound failover
Not verifiedPublic pages describe call forwarding as a routing choice, not a failure-triggered priority list. They do not establish which timeout or SIP response advances, whether an active call survives, or how a destination is restored. Treat resilience as an account-specific design and controlled test.
Number and regional availability
Not verifiedLES.NET publicly describes local numbers in thousands of Canadian and US cities and says porting is available. Exact inventory, locality, portability, documents, activation time and account eligibility still require a current search or dated order for each number.
Audio codecs
Not verifiedThe reviewed public service and product pages do not publish a current codec, packetization or transcoding matrix. Preserve the PBX allow list, inspect negotiated SDP and obtain route-specific confirmation before requiring narrowband, wideband or transcoding behavior.
T.38 fax
Not verifiedThe portal lists fax-to-email as a separate service, but the reviewed pages do not establish T.38 or fax-over-audio support on a SIP trunk. Do not turn the separate fax product into a trunk compatibility claim; qualify the exact number, direction, endpoint and page profile.
Signaling and media encryption
Not verifiedThe reviewed public pages do not establish a TLS or SRTP service workflow. A portal claim about toll-fraud detection does not prove encrypted signaling, protected media or a secure PBX. Confirm each carrier and PBX leg and retain independent call-permission and spend controls.
Concurrent calls and call starts
DocumentedThe public portal distinguishes an unlimited count of IP trunk objects from DID channel limits: it lists four channels for metered Canadian and US DIDs, with more by inquiry, and two channels for unmetered DIDs. Those figures are not a published account-wide active-call or calls-per-second limit; confirm the current order and every traffic direction.
Emergency calling
Not verifiedThe public portal labels 911 as included, but the reviewed pages do not establish eligible locations, civic-address validation, caller identity, routing, callback behavior, activation, fees or an approved test procedure. Obtain the exact emergency workflow for every service address before deployment.
Pricing model
DocumentedLES.NET publishes dated CAD account, DID, usage and setup figures, with metered and flat-fee number options plus separate outbound, conferencing and fax-to-email charges. These public figures are a planning snapshot, not a quote; confirm the current rate deck, destination mix, taxes, porting and optional services in a dated order.
Administration and support
DocumentedLES.NET describes real-time DID ordering and activation, number routing and a support-ticket channel; its contact page publishes weekday office hours. Those controls do not establish an SLA or incident response. Record portal state and PBX evidence together for each change.
SMS and MMS
Not verifiedLES.NET's DID page says its DIDs are SMS enabled and the portal lists SMS/text messaging, but the reviewed pages do not establish number eligibility, SMS or MMS direction, registration, throughput, retention, API or client behavior, or charges. Validate messaging as a separate number-specific workflow.
Route one DID without assuming failure-triggered failover
The local-DID page says a number can route to a phone system or call forward to another number. That supports an inbound-routing choice, not a documented failover sequence. Record whether the number points to SIP service or telephone forwarding and preserve the exact destination before changing it.
The reviewed pages do not identify priority order, timeout, advancing SIP responses, active-call behavior or restoration. Test only an approved new-call outage after the provider confirms the intended resilience feature; a selectable forwarding destination alone is not evidence that failure triggers it.
Resolve authentication and registration before choosing a template
The voice page describes account controls for trunks, outbound calling and caller ID, but the reviewed public sources do not establish digest versus source-IP authentication, SIP REGISTER versus static delivery, the registrar or destination format, Contact handling or expiry. Start with the actual portal record and provider instructions rather than a PBX template selected by brand name.
Record the loaded PBX endpoint, registration and identify objects, resolved next hop, transport and redacted identity. A successful outbound request does not prove inbound routing, and a missing registration indicator is not a fault when the service is not confirmed to use REGISTER.
Read public Canadian pricing as a dated snapshot
LES.NET publishes Canadian-dollar account, DID, setup and usage figures, with metered and flat-fee number choices plus separate outbound, conference and fax-to-email charges. Those pages are useful for identifying bill components, but they are not a quote and can change.
Price the actual destination and number mix using a current dated order. Include account subscription, number setup and rental, inbound and outbound usage, channel model, porting, optional services, taxes and any support or regulatory charges. Do not treat the public label of unlimited trunks as an unlimited-minute or unlimited-channel plan.
Qualify 911, SMS and fax as separate workflows
The public portal labels 911 and SMS/text messaging as included, and the DID page says DIDs are SMS enabled. Those statements do not establish eligible numbers or locations, civic-address validation, caller identity, callback behavior, SMS or MMS direction, registration, throughput, retention, application access or fees. Obtain a current workflow for each service address and number, and use only the provider-approved emergency test procedure.
Fax-to-email appears as a separate portal product. It does not prove T.38 or reliable fax-over-audio behavior on the SIP trunk. Qualify the selected number, direction, endpoint, page profile and fallback independently.
Pilot media, security and operations with bounded evidence
The reviewed pages do not publish a current codec matrix or establish TLS and SRTP. The outbound-termination page's toll-fraud-detection claim is not proof of encrypted media or a secure PBX. Preserve negotiated SDP and transport evidence, restrict destinations and caller identity, set independent spend controls and confirm any required encryption before launch.
The provider describes real-time DID ordering and activation, routing controls, support tickets and weekday office hours, but those are not an SLA. Record the portal state, PBX logs and provider case together for each change or incident. Protect credentials, phone numbers and customer data in captures.
Run a bounded acceptance record
For one pilot DID, verify the intended inbound destination, outbound authorization, caller identity, two-way audio, DTMF, release behavior, channel signal, long-call behavior and reboot recovery. Test forwarding, messaging, emergency calling, fax and outage behavior only when the exact account feature and approved procedure are known.
Confirm number inventory, porting, authentication, registration, codecs, encryption, capacity, pricing, emergency obligations, messaging and support in the current account or dated order. No LES.NET account, PBX, trunk, number, route, port, call, media, fax, emergency, messaging, price or support response was validated 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 services ↗
- LES.NET customer portal and public service details ↗
- LES.NET local DID service ↗
- LES.NET outbound SIP termination ↗
- 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.