Information Regarding Future Change in Modem Support in Doors.NET

Information Regarding Future Change in Modem Support in Doors.NET

End-of-Life for PXL and Entraguard Modem Communication

Keri has decided to delay removing support for modem communication for PXL and Entraguard units to the next software release.

Doors.NET v4.8.0 will be the last software revision that will support modem communication for PXL and Entraguard products.

Modem communication for PXL and Entraguard units will end beginning with Doors.NET v4.9.0.

This change will be made to accommodate the rapid conversion by telecommunication providers from POTS lines, which are completely modem compatible, to VOIP lines, which do not transfer data packets reliably and have differences that vary from vendor to vendor, making it impossible for us to ensure modem compatibility with all VOIP vendors and the VOIP hardware they use.

Keri strongly recommends preparing for this change by the following methods:

For Data Communication with Either PXL or Entraguard Units

  • Keri recommends replacing your modems with a LAN-520 Ethernet module.
  • Alternatively, if your computer has a serial communication port, you can use a direct-connection cable.

For Voice Communication with Entraguard Units

  • You will use a VOIP converter for voice calling between Entraguard units and tenants. This requires the use of a VOIP adapter.
  • Keri recommends the Cisco SPA 112 VOIP Adapter, however your ISP likely has their preferred unit.

    • Related Articles

    • PXL-500 Setup in Doors.NET

      1.0 Introduction This section covers the basic configuration of PXL controllers in Doors.NET software. It assumes Doors.NET has already been successfully installed on your host PC, the software license has been activated, and the PXL gateway has been ...
    • PXL-500 Setup in Doors.NET with a LAN-520

      1.0 Introduction This guide explains how to setup a PXL-500 in the Doors.NET software using a LAN-520 module. It assumes you have worked through the steps to install and license the Doors.NET software and that you have also setup the PXL gateway. In ...
    • PXL-500 Controller Address Change

      PXL - Change Controller Address Viewing the Controller's Address To view the controller address, click S1. The controller address will appear on the display for a few seconds.   Setting the Controller's Address To set the desired operating address ...
    • Doors32 to Doors.NET Networking Setup Procedure

      1.0 Introduction The NC-485 module was designed to provide RS-485 connectivity across an Ethernet network and to simplify the management of a Doors32 system - as it allowed multiple PXL networks to be combined and then administered and monitored as a ...
    • PXL-500 Setup in Doors.NET With a USB-Serial Adapter

      1.0 Introduction This guide explains how to setup a connection to a PXL-500 Primary controller using a USB-serial adapter. The adapter used in this example is the Keyspan 19-HS by TRIPP-LITE which is one that Keri highly recommends. It is robust, ...