Start with the accepted order and controlling documents
Identify the customer, service location, accepted service order, service schedule, service term, service commencement date, completion notice, ordered voice service, numbers, channels, access-loop design and support owner. The current product page lists fiber business lines, SIP trunks and PRI, while the Standard Terms make the accepted Service Order and applicable Service Schedule the governing records.
A product page or downloadable sheet does not establish that a particular SIP trunk, channel quantity, access design, feature, number or support term was ordered or activated.
Documented service facts
Reviewed 2026-10-30. Compare SIP trunk services →
SIP authentication
Not verifiedPublic records do not publish one universal registration, source-address, digest, certificate or managed-edge identity model. The accepted order and implementation record govern.
SIP registration
Not verifiedReviewed public records do not establish whether one order registers, peers by address, uses provider equipment or combines controls.
Telephone numbers and inbound calling
DocumentedDID numbers and existing-number retention are described. Order, port, storage, provider attempt, delivered value, PBX route and answer remain unverified.
Access redundancy and continuity
DocumentedRedundant and non-redundant access-loop scopes are distinguished. Ordered design, alternate path, call delivery, established-call survival, media and restoration remain account- and observation-specific.
Service form and handoff
DocumentedSIP trunks, PRI, Ethernet and optional PRI handoff language are published. The accepted order, site, serviceability, access, demarcation and loaded handoff govern.
Codecs and media
DocumentedThe SIP sheet names G.711 for SIP channels. Exact negotiation, packetization, DTMF, encryption, transcoding, media range, packet delivery, decoding and audibility remain unverified.
Fax and modem behavior
Not verifiedThe Voice Service Schedule describes voice service as carrying speech, facsimile or modem traffic, but reviewed SIP records do not establish T.38, passthrough, fallback or completed-page results.
PBX security and fraud controls
DocumentedThe schedule assigns customer terminal-equipment security and fraud controls to the customer; separate provider guidance lists defensive questions. Exact controls, events, findings and liability remain account-specific.
Channels and call admission
Not verifiedScalable line additions are described, but ordered channels, active dialogs, attempts, PBX resources, access demand, provider responses and completed calls remain separate.
E911 activation and location
DocumentedThe current schedule requires affirmative activation and location maintenance and lists power, broadband and number-type limits. Accepted record, callback, route and approved validation remain order-specific.
Price and availability
Not verifiedNo current account quote was reviewed. Access design, handoff, channels, numbers, equipment, support, taxes, term, serviceability and activation remain order-specific.
Completion, SLA and support
DocumentedCurrent terms, the Voice Service Schedule and a 24x7x365 NOC path are published. Completion notices, loop scope, tickets, findings, actions, credits and verified restoration remain separate evidence.
SMS and MMS
Not verifiedReviewed SIP trunk records do not establish SMS or MMS eligibility, sender registration, consent, throughput, retention or pricing for trunk numbers.
Separate access, handoff and loaded PBX state
Record whether the ordered service is on-net or off-net, the access circuit and redundancy design, demarcation, Ethernet or PRI handoff, customer PBX or SBC, signaling target, identity or authentication method, number ranges and support boundary. Compare the implementation record with the objects actually loaded and the network path actually selected.
The reviewed public sources do not publish one universal registrar, realm, credential, source-address rule, port set, certificate profile or media range. Fiber-network and installed-service language does not prove the intended trunk, route, SDP or media path is functioning.
Bound codec, capacity and compatibility statements
The SIP info sheet states that FirstLight SIP channels use G.711 and describes scalable line additions, existing-number retention, an Ethernet interface and an optional PRI handoff. Preserve ordered channel quantity, active dialogs, offered attempts, PBX resources, access demand, negotiated SDP, observed payloads, destination responses and completed calls separately.
The sheet says the service works with most modern phones, but it does not approve a specific PBX, SBC, firmware, topology or feature. G.711 wording does not establish packetization, DTMF, fax, encryption, transcoding or successful two-way media for one account.
Reconcile redundancy language with the current SLA
The current product page and SIP sheet use redundancy and availability language. The August 21, 2026 Voice Service Schedule defines separate access-circuit availability levels for geo-diverse redundant and non-redundant access loops, credit schedules and excused-outage boundaries. Preserve the ordered loop design, affected service, outage start and end, provider fault finding, exclusions and credit request.
The SIP sheet also mentions 99.999% for Cloud Communications and redundant VoIP-related services. Do not transfer that marketing statement to a SIP-trunk order where the controlling current schedule states different access-loop levels. Neither figure proves measured availability, call completion, established-call continuity or restoration.
Keep telephone-number and E911 evidence distinct
Preserve number order or port authority, carrier state, assignment, provider attempt, delivered called value, PBX route and answer. The Voice Service Schedule says disconnected or unused numbers may return to the native carrier after a stated non-use period unless stored through a new order; that contractual rule is not evidence of one number’s current state.
For E911, retain activation, valid registered street address for each number, rate-center alignment, callback identity, effective update, PBX emergency route, power and broadband dependencies and provider-approved non-live validation. The current schedule says activation is not automatic and excludes soft phones, local inbound numbers and virtual numbers; the older acknowledgement remains separately date-scoped. Do not place an uncoordinated live emergency call as a test.
Preserve customer PBX security responsibility
The current Voice Service Schedule assigns customer terminal-equipment security and toll-fraud controls to the customer. FirstLight’s PBX-hacking page recommends controlled management access, disabling unnecessary remote call-out or maintenance access, unique voicemail passwords, secured maintenance ports and coordination with the PBX vendor and FirstLight when unexplained activity appears.
Those responsibilities do not prove that fraud occurred, identify an attacker or establish which control failed. Preserve authorized configuration, audit evidence, call records, account restrictions, provider findings and remedial actions separately without publishing reusable credentials.
Treat support, completion and restoration as separate evidence
The Standard Terms distinguish installation, testing, completion notice, a review window and service commencement. The support page lists customer service and a 24x7x365 NOC path. Preserve the exact service object, completion record, ticket-open time, severity, provider response, finding, action, credit request, ordinary-call retest and monitoring interval.
A completion notice, ticket, response, service credit or closed case does not prove root cause, call restoration, recurring stability or what callers heard. Use one bounded proof plan and change only the first demonstrated owner.
Sources & applicability
Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.
- FirstLight — Voice and SIP Trunking ↗
- FirstLight — SIP Trunk info sheet ↗
- FirstLight — Service Schedule A, Voice Services, version 4 (August 21, 2026) ↗
- FirstLight — Standard Terms and Conditions, version 5 (June 16, 2025) ↗
- FirstLight — E911 Acknowledgement, version January 14, 2019 ↗
- FirstLight — Legal, Regulatory, Terms and Conditions ↗
- FirstLight — Customer Support ↗
- FirstLight — Prevent Long Distance Fraud and PBX Hacking ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.