Lynx Systems
Your Link to Duress & Mass Notification
The LynxGuide Hosted Software Only packages contain a set number of connections to LynxGuide Stratus. A Lynx technical support specialist will gather your requirements and coordinate the deployment of your Lynx system. A seat is defined as a network connection to the LynxGuide Stratus server.
A LynxNet hardware device uses a seat, or LynxClient installed on a computer or the Lynx Alerts app. This is a managed system – if the customer needs changes, simply call the Lynx support team.
The LynxNet hardware and LynxClient software achieves bidirectional communication through a client-initiated, persistent socket session to the LynxGuide Stratus server on ports 443 and 10117-10121. No network ingress connections are required. All server communications are TLS encrypted. In addition to providing security, this method is ideal if the hardware is behind a gateway, as no NAT rules are required to achieve connectivity.
| Number of Seats | 5, 10, 25, 50, 100, 500 |
|---|
Micro Technology Services Inc. (MTSI) has been in business since 1990. The Security Products Division of MTSI has been developing Lynx Systems since 2004.
As a member of several security organizations, MTSI responded to many customers’ requests for an easier, more cost-effective way to install and operate duress and notification alarm systems.
OWASP ZAP vulnerability scanning is included in our Continuous Integration development process. Security considerations are paramount in our development and software lifecycle.
Lynx software and hardware achieve bidirectional communication through a client-initiated persistent socket session to the server. No network ingress connections are required. All traffic is TLS encrypted.
Learn how Lynx can provide a duress and mass notification solution that is tailored to your needs. Contact us to schedule your webinar today!
Schedule a Free Demo
