VOIP GATEWAY INVENTORY AND ACCEPTANCE WORKSHEET
Guide: https://yenra.com/voip-gateway/
Updated September 7, 2026

Purpose: turn existing telephone equipment into a supported interface plan
and a record of the tests that establish acceptance. Complete this with the
equipment maintainer and calling provider. Use their installation procedures;
this worksheet is not a wiring guide. Do not connect an FXS output to a live
telephone-company line. Keep account passwords out of this file.

SITE AND RESPONSIBILITY
Site: __________________ Owner: ______________ Test window: _____________
Provider/support reference: _______________ Installer: __________________
Gateway model/firmware: ____________________ Manual URL/version: _________
Provisioning owner: ________________________ Backup/recovery owner: _____

INVENTORY (repeat for each independent device or line)
Device purpose: __________ Manufacturer/model: _________ Port label: _____
Verified analog/digital interface: _________ Manual evidence: ___________
Needed gateway role: FXS / FXO / exact digital interface / IP connection
Extension/number: __________ Required concurrent calls: _________________
Country, tones, caller ID, impedance and disconnect method: ______________
Ringing load and candidate limit, with units/manual reference: ___________
Special device? fax / alarm / door / elevator / modem / other: ____________
Maintainer/provider support confirmation and approved test: ______________
Power/network/alternate calling dependencies: ___________________________

FICTIONAL EXAMPLE
Two independent analog desk phones and one fax must operate at the same
time; there is no analog carrier line to retain. Initial requirement:
three FXS ports and three supported simultaneous sessions, including the
agreed fax method. An FXO port adds no required role here. If the fax moves
to an approved service workflow, revise the physical inventory to two FXS
ports and test document receipt/retrieval in that new workflow.

SERVICE EVIDENCE
Exact supported model/firmware and dated source: _________________________
Registration or preconfigured route: _______ Codec/DTMF requirements: _____
Fax method and support across all boundaries: ___________________________
Management access, firmware and provisioning responsibilities: ___________
Emergency location/alternate calling plan reference: _____________________

ACCEPTANCE (record expected, actual, timestamp and evidence for each)
1. Inbound call rings intended extension and displays expected caller ID.
2. Outbound call reaches agreed destination with expected identity.
3. Both parties hear clearly; authorized menu digits are recognized.
4. Required hold/transfer works; hang-up releases the line.
5. Required simultaneous calls work; idle-device ringing remains usable.
6. Special-device tests pass the maintainer/provider's agreed criteria.
7. Scheduled outage/restoration test follows the approved plan; registration,
   routes and alerts recover. Use provider-coordinated emergency verification,
   not casual calls to emergency services.

Expected/actual results and call references: _____________________________
Fax page count/legibility results, if applicable: ________________________
Failed requirement: __________ Owner: __________ Resolution/retest: ______
Acceptance decision and date: ___________________________________________

Use the exact device's limits. Example manuals demonstrate port roles and
regional settings, not universal compatibility or end-to-end fax success.
https://documentation.grandstream.com/knowledge-base/ht813-administration-guide/
https://learn.microsoft.com/en-us/microsoftteams/devices/sip-gateway-plan