Replacing a traditional POTS line with a modern cellular or IP solution may seem simple: install the gateway, connect the analog device, configure the account, and test the line.
But in real deployments, a successful installation involves much more than checking that the device powers on and produces a dialing tone.
For elevator emergency phones, fire alarm panels, security systems, fax machines and other critical analog applications, the communication path must be verified end-to-end.
Before leaving the site, installers should take a few extra minutes to confirm that the entire system is operational, properly configured, and ready for long‑term service.
Here are 10 points that every installer must check.

1. Confirm that the analog device is properly connected
Start with the physical connection.
Verify that the elevator emergency phone, alarm panel, fax machine, or any other analog endpoint is connected to the correct FXS port and that the wiring is secure.
For multi‑line deployments, confirm that each analog device is connected to the intended port. Incorrect port mapping can create confusion during troubleshooting or provisioning of individual lines.
A simple physical check during installation can prevent unnecessary service calls later.
2. Check the power supply and backup power
A POTS Replacement device is only useful if it remains operational when the main power source is interrupted.
Before leaving the site, verify that the gateway receives a stable power supply and that its backup battery is properly installed and recognized.
For life‑safety applications, backup power should not be considered an option. Elevator emergency phones and other critical communication systems must remain available during building power outages.
Devices such as the PR12 incorporate a backup battery into a compact platform designed for applications where energy resilience is important.
For larger deployments, the PR18 provides an integrated backup power supply as part of a high‑density communication platform.
3. Verify cellular or network connectivity
A device can be powered and yet not be able to provide reliable communication.
Installers must verify the actual network connection, including:
· Cellular registration
· Signal power
· SIM Status
· IP Connectivity
· WAN status if applicable
For cellular deployments, signal strength should be verified at the actual installation site rather than relying solely on coverage maps.
A few minutes spent evaluating the network during installation can prevent future connectivity issues.
4. Check the SIM card and operator service
If the deployment uses cellular connectivity, confirm that the SIM card has been activated and assigned correctly.
For dual SIM devices, verify which SIM is currently active and confirm that the backup configuration is correct.
Operator certification can also be an important criterion during deployment. For example, the LM150 has obtained AT&T, Verizon, and T‑Mobile certifications, offering a validated option for single‑line cellular POTS replacement applications.
L'objectif n'est pas simplement d'insérer une carte SIM, mais de vérifier que l'appareil est réellement enregistré et capable de maintenir le service.

5. Test outbound calls
This seems obvious, but it should never be ignored.
Make a real outbound call from the connected analog device and confirm :
· Dial tone
· Call Setup
· Two-way Audio
· Correct identification of the caller if applicable
· Stable call duration
For an elevator emergency phone, this means verifying that the emergency phone can successfully reach the designated destination.
For other analog devices, confirm that the call behavior meets the client's requirements.
A successful outbound call provides the first indication that the full communication path is working.
6. Test incoming communication
Depending on the application, incoming communication can be as important as outgoing calls.
Verify that the assigned number can receive an incoming call and that the connected analog endpoint responds correctly.
This is particularly important for applications where the monitoring center, service provider, or authorized staff may need to call the device.
Do not assume that because outbound calls work, inbound communication will automatically behave as expected.
Both directions must be tested when the application requires it.
7. Verify alarm, fax, or modem communication
Not all analog devices are simply phones.
Fire alarm panels, fax machines, and legacy modem applications can have markedly different communication requirements.
For alarm applications, installers must verify that the appropriate signal reaches the intended monitoring destination.
Selon le déploiement, cela peut impliquer des protocoles tels que Contact ID ou SIA.
For fax and modem applications, successful voice communication does not necessarily guarantee successful data transmission.
This is where solutions such as the Vola POTS Media SBC can play an important role by providing optimized media management for legacy analog data applications.
The key lesson is simple :
Test the application, not just the phone line.
8. Confirm account provisioning and configuration
Before leaving the site, verify that the correct account or service configuration has been applied.
This may include:
· SIP credentials
Provisioning URL
· Phone number
· Account assignment
· Device MAC address
· Line configuration
For managed deployments, installers must also verify that the device is correctly associated with the client's organization and assigned to the appropriate configuration profile.
A device that works locally but is incorrectly provisioned can become a support issue later.
9. Verify VolaCloud connectivity and remote access
The installation should not stop when the local test is finished.
If the device is managed via VolaCloud, verify that it appears online and that the correct device information is visible on the platform.
Engineers must verify that they can access the device remotely and view important operational information.
This provides a critical advantage for future support.
If a client reports a problem several months later, the technical team may be able to investigate the device remotely instead of immediately sending a technician on site.
For MSPs and integrators managing large deployments, this capability can significantly reduce unnecessary on‑site travel.
10. Documenter l'installation avant de partir
The final step is documentation.
Record the information that may be needed six months or two years later :
· Numéro de série de l’appareil
· Adresse MAC
· Phone number
· SIM information
· Installed location
· Analog device connected
· Configuration profile
· Network information
· Installation date
This information becomes particularly valuable when hundreds or thousands of devices are deployed across multiple sites.
VolaCloud can provide centralized visibility on managed devices, helping organizations maintain an accurate operational view after deployment.
A successful installation is more than "It works"
The most important lesson learned from POTS replacement projects is that installation should not be considered finished simply because the device is powered on and has a tone.
A properly executed deployment must answer ten questions:
Is it connected ?
Is it powered ?
Is the network available ?
Does the SIM card work?
Can it make calls?
Can it receive calls ?
Can it transmit the required application data?
Is it properly provisioned ?
Can it be managed remotely ?
Is everything documented ?
When the answer to the ten questions is yes, the installer can leave the site with much more confidence.
The POTS Replacement is primarily about replacing a communication path that customers have relied on for decades. The new solution therefore must be tested and deployed with the same level of rigor.
For installers, a few extra minutes before leaving the site can save hours of later troubleshooting.
And for MSPs, integrators, and building owners, a standardized installation checklist can transform thousands of individual deployments into a predictable and manageable infrastructure.
Install once. Verify fully. Manage remotely.
