The LynxGuide Server application is available as a SaaS or On-Premises solution
The SaaS Solution does not require any ingress connections to the customer’s network. Lynx software and hardware achieve bidirectional communication through a client-initiated persistent socket session.
StratusLynx (SaaS) requires an annual connection license for every device connecting to the server. Connections can be initiated by the LynxClient software, LynxNet hardware, LynxApp for mobile devices, or connections from third party integrations.
The On-Premises Solutions can either utilize a customer provided server that meets the Lynx server specifications, or a turnkey solution with the LynxGuide software pre-loaded on a Dell OEM server. The LynxGuide System is typically operated by the security department, but IT’s role is critical for deployment of the system.
The LynxGuide server requires ingress ports 80 or 443 and 10114-10120.
Outbound Communication for the LynxSMS and LynxVoice Plans the LynxGuide server must be able to connect to http://sms1.mitsi.com and http://sms2.mitsi.com on port 443.
E-mail LynxGuide has the ability to send email through a customer’s mail server.
Users can login to the Lynx Server web interface using their Active Directory credentials.
LynxClient Software and LynxNet Hardware
LynxClient and LynxNet Devices check-in with the LynxGuide Server by default every 5 minutes. Supervision packets are less than 1Kb.
LynxClient PC Software is deployed using a MSI and can be manually installed or distributed using your software distribution tools. LynxClient can be deployed in a dormant mode and can be enabled through the LynxGuide web interface. The MAC client is a DMG file that can be installed manually or distributed using your software distribution tools.
When an alarm is received from the LynxClient software, the LynxGuide server uses a lookup table to translate a unique identifier into useful location information. This information can be uploaded to the Lynx system in a .CSV file. Computer name, IP address range, or AD user name can be used to identify the location of an alarm.
The LynxClient test feature allows users to provide location information or verify the stored location as part of the monthly test. The users input is presented in a report to the Lynx owner so it can be verified before updating the lookup table. This location data is exportable so it can be shared with IT.