E zcall all_spec_sheets

Specifications subject to change without notice. Copyright 2010 – QBsoft Solutions

EZcall Enterprise DCS – Display Control Server Description The Display Control Server is the core component of an EZcall system. The Display Control Server receives and processes all alarms, events and schedule activity on an EZcall system. A DCS may be operated as a stand-alone application directly connected to a single input system and a single output system, or complemented with various input, display and output client applications. The DCS may be expanded to accept numerous output client applications by adding an MDS (Message Dispatch Server) which allows several different output connections to reside on a single system as well as adds group, naming alias, Email and message centre networking capabilities.

All display, RTLS, and alarm input clients network with the DCS over a standard Ethernet LAN or WAN network using the TCP/IP protocol. A single EZcall DCS will support up to 10,000 supervised client connections of each type, and a single MDS connection over a network allowing over 10,000 alarm systems more than 10,000 messaging/output systems and over 10,000 display clients to be networked into a single-node EZcall installation. Multiple DCS servers may be networked into a central DCS server for multi-site applications. Watchdog signals are used between the DCS and all client applications to ensure reliable communications.

The Display Control server is a hardware agnostic platform that can interface and integrate various types and brands of alarm systems into a single system to share alarms, reporting and dispatching. The DCS also provides added functionality to basic alarm systems, by adding user features such as dementia monitoring, door control and other similar features to simple alarm or i/o systems.

Features • TCP/IP, UDP/IP, RS232, RS485 communications support • Secure encrypted server communications • Rapid setup and deployment for small or large systems • HL7 (Health Level 7) integration support • Multi-site support, or multi-node server support • Fail-Over/Standby high availability options • May be run as an application or a supervised Windows service • Virtual COM port support • Support for standard and proprietary protocols including XML, SOAP, SNMP, HTML • Integrated simulator for testing & troubleshooting • Direct output or networked output support • Wireless coverage test tool built-in supports coverage testing using any system • 3-click device swap provides user-friendly device replacement for repairing hardware • Direct input, networked input, or combined/mixed input • Remote client control with built-in remote-access engine • Integrated error logging and reporting • Integrated database maintenance utility, with support for SQL, MSDE • Configurable login schemes; per user, per access level, or per function • Large button touch-screen support • Skin’ able desktop allows the operator interface to be customized • Multiple language support, c/w English, Dutch, French, Chinese (simplified) • Integrated history reporting utility • Provides primary output, secondary and backup • Support for static, dynamic, or scheduled assignments

1939 144th Street

Surrey, BC V4A 7M7 T. 604.812.SOFT (7638)

E. [email protected] W. www.qbsoft.ca

All trademarks, and trade names shown here are the property of their relative owners.

Data Sheet No. DCS_Display_Control_Server_Spec_Sheet


• Configurable assignment options; by area, by room, by ward, global • Easy-to-use schedules; day, evening and night shifts may be individually configured • Smart SAM (Sensor Activity Monitor) ensures device sensors are always operational • PC Watchdog card support & integrated software watchdog • Configurable icons • Global priority standardization, up to 9999 system priorities • Packaged with; Paging Encoder Emulator, Virtual Null Modem Application, EZtext server, Time Sync Client, EZstart

application launcher and Ascom OAP emulator utilities • Extensive log reports simplify system troubleshooting

Supported Applications EDC – Event Display Client TDC – Target Display Client TPH – Touch-Panel Host AIC – Alarm Input Client NWC – Network Watchdog Client BBC – Button Bar Client PDC – Popup Display Client MDS – Message Dispatch Server EGW – EZcall GuardRFID Wrapper VKC – Virtual Keypad Client TTC – Text Talker Client EEW - EZcall Ekahau Wrapper WAC – Web Access Client iServer – Inovonics Wireless Server EWC – EZcall Wireless Client SAS – Spider Alert Server FCC – Facility Control Client TMC – Text Messaging Client VAC – Virtual Alarm Client EZtext/LoginOut Server Supported Direct Output Protocols Visiplex paging output Globestar ConnexAll TMDP (Text Message Dispatch Protocol) COMP2 paging output TAP (Telocator Alphanumeric Protocol) 1.8 paging direct serial output Ascom enhanced TAP output TAP 1.8 dial-up paging output Supported Direct Input Protocols Hill-Rom LightCom nurse call system network Maxivox Maxicomm I nurse call system network Maxivox Maxicomm II nurse call system network GE/Dukane StaffCall Pro nurse call system network Raw Data input Added Applications/Functions Staff location/presence Dementia monitoring w/Artificial Intelligence auto-configuration Staff rounds monitoring Guard tour monitoring Patient/Resident check-in Service requirements Door monitoring and alarm w/access control support CCTV popup and control support RTLS equipment location monitoring and alarm support System Requirements CPU: Intel Xeon Quad Core or Equivalent, >200MHz OS: Windows XP, 7, Server 2003, Vista Ultimate Memory: 2GB minimum (4GB recommended) LAN/WAN: 10/100 (Gigabit recommended) Hard Disk: 160Gb Interface: RS232 db9/Ethernet (alarm and paging system dependent)

1939 144th Street





EZcall Enterprise MDS – Message Dispatch Server Description The Message Dispatch Server is an expansion module to an EZcall DCS (Display Control Server) that allows multiple output clients to be used and provides additional features. In addition to adding the ability for multiple output client connections, the MDS has a built-in Email and LED message board interface. By adding an MDS to an existing DCS, additional EZcall features are enabled, including output device group creation and output device aliasing. The Message Dispatch Server networks directly with an EZcall DCS over a standard Ethernet LAN or WAN network using the TCP/IP protocol. The Message Dispatch Server supports up to 10,000 of any type of output client connection, allowing the system to be very expandable. Every DCS may only be linked to one MDS and typically reside on the same server computer. Watchdog signals are used between the DCS and the MDS applications to ensure reliable communications.

Features • SMTP, POP3, TCP/IP, UDP/IP, RS232, RS485 communications support • Secure encrypted server communications • Rapid setup and deployment • Standard or secure Email server support, with MIME, HTML, and UUencoding support • May be run as an application or a supervised Windows service • Virtual COM port support • Supports direct connection to LED message centres • Output device group creation and alias naming adds versatility to a DCS server • Instant Email SMS message output capability supported by mobile devices • Prioritized Email output capability • Integrated simulator for testing & troubleshooting • Extensive log reports simplify system troubleshooting

Supported Systems/Products Application Connections LED Message Centers Email Output TPC – Telephone Paging Client (up to 9999) Edwards Message Centre SMTP SPC – Serial Paging Client (up to 9999) Alpha PrintPak POP3 CAC – Command Argument Client (up to 9999) Alpha EZkey II MIME OCC – Output Control Client (up to 9999) Alpha EZ95 UUencoding DCS – Display Control Server (1 connection) Pro-Lite ver. 5.25 Pro-Lite ver.6 System Requirements CPU: Intel Xeon Quad Core or Equivalent, >200MHz OS: Windows XP, 7, Server 2003, Vista Ultimate Memory: 2GB minimum (4GB recommended) LAN/WAN: 10/100 (Gigabit recommended) Hard Disk: 120Gb Interface: RS232 db9/Ethernet (output system dependent)

1939 144th Street




Data Sheet No. MDS_Message_Dispatch_Server_Spec_Sheet


Data sheet No. WAC_Web_Access_Client_Spec_Sheet

EZcall Enterprise WAC – Web Access Client Description The Web Access Client is a powerful EZcall server application that allows EZcall DCS functions to be accessed using any standard web browser. The Web Access Client prevents the need of installing and supporting numerous client program installations on user computers. By allowing browser access to most EZcall functions, a large facility deployment may be completed in a fraction of the time needed by using dedicated client programs. The browser interface also allows an EZcall deployment to be operating system independent. No matter what O.S. or web browser is being used in the facility (Linux, Unix, MAC, Windows), all will function in the same manner using their standard web browsers as the user interface. The Web Access Client is also supported by all popular standard and mobile browsers including; Firefox, Windows Internet Explorer, Apple Safari, Opera, Google Chrome.

Features • Standard HTTP 1.0 and 2.0 support ensures reverse compatibility • Secure password protection login • Secure encrypted server communications • Built-in FGA Web Server does not rely or use IIS • Reliable FGA Web Server not susceptible to HTTP virus attacks, spoofing or malware • Rapid setup and deployment; no HTML language required • May be run as an application or a supervised Windows service • Alarm text and graphical map display • Manual text messaging to any EZcall output device • Alarm history display • Call Routing Assignments • On-Screen Virtual Call Buttons • Staff Presence location display • Reconfigurable skins allows graphics to be customized to the site/customer • Mobile browser support (iPhone, BlackBerry, Android, Windows Mobile) • Extensive log reports simplify system troubleshooting

System Requirements Clients: Web browsers that support HTTP 1.0 CPU: Intel Xeon Quad Core or Equivalent, >180MHz OS: Windows XP, 7, Server 2003, Vista Ultimate Memory: 2GB minimum (4GB recommended) LAN/WAN: 10/100 (Gigabit recommended) Hard Disk: >120GB @ 7200RPM (> 10,000RPM recommended)

1939 144th Street





EZcall Enterprise IWS – iServer Inovonics Wireless Server Description The EZcall iServer is a fully functional integrated RTLS system that can network with an EZcall system. The iServer uses the Inovonics EchoStream hardware to function as a wireless duress, locating and nurse call solution. The iServer communicates directly to the Inovonics EchoStream hardware to allow all EchoStream alarms to be received and processed by EZcall, as well as allowing the iServer to function as a stand-alone alarm system. Every IWS can network (optional) to an EZcall DCS (Display Control Server) over a standard Ethernet LAN or WAN network using the TCP/IP protocol. A single EZcall DCS will support up to 10,000 supervised EGW client connections over a network allowing that many systems to be networked into an enterprise EZcall installation. Watchdog signals are used between the DCS and all EGW applications to ensure reliable communications.

Features • TCP/IP, UDP/IP, RS232, RS485 communications support • Secure encrypted server communications • Fully functional stand-alone wired/wireless duress/alarm system • Rapid setup and deployment • Real-time location and alarm information monitoring using proprietary RTLE algorithms • Integrated web-server for alarm and history display, as well as transmitter management • May be run as an application or a supervised Windows service • User configurable priorities and messages • Supports direct connection to numerous pocket paging systems • Supports WWC wireless wizard client connections for system maintenance • Integrated transmitter simulator for testing & troubleshooting • Extensive log reports simplify system troubleshooting

Supported Systems/Products Inovonics EchoStream serial receiver, repeaters and transmitters EZcall DCS server (optional) WWC wireless wizard client Standard HTTP 1.0 capable web browsers System Requirements CPU: Intel Core2 Duo or Equivalent, >180MHz OS: Windows XP, 7, Server 2003, Vista Ultimate Memory: 2GB minimum (4GB recommended) LAN/WAN: 10/100 (Gigabit recommended) Hard Disk: 160Gb Interface: Inovonics proprietary protocol

1939 144th Street



EchoStream and Inovonics are registered trademarks of Inovonics Inc..

Data Sheet No. IWS_iServer_Inovonics_Wireless_Server_Spec_Sheet


EZcall Enterprise EEW – EZcall Ekahau Wrapper Description The EZcall Ekahau Wrapper is a bi-directional interface between an EZcall system and an Ekahau RTLS system. The EEW integrates directly with an Ekahau RTLS server using the proprietary Ekahau XML-based protocol to allow all Ekahau alarms to be received and processed by EZcall, as well as allowing an EZcall system to dispatch alarm messages to Ekahau WiFi badge tags. Every EEW networks to an EZcall DCS (Display Control Server) over a standard Ethernet LAN or WAN network using the TCP/IP protocol. A single EZcall DCS will support up to 10,000 supervised EEW client connections over a network allowing that many systems to be networked into an enterprise EZcall installation. Watchdog signals are used between the DCS and all EEW applications to ensure reliable communications.

Features • TCP/IP, UDP/IP, RS232, RS485 communications support • Secure encrypted server communications • Secure encrypted RTLS server communications • Rapid setup and deployment • Real-time location and alarm information monitoring • Message dispatching to badge tags • May be run as an application or a supervised Windows service • User configurable priorities and messages • Integrated badge tag simulator for testing & troubleshooting • Extensive log reports simplify system troubleshooting

Supported Systems/Products Ekahau RTLS server EZcall DCS server System Requirements CPU: Intel Core2 Duo or Equivalent, >180MHz OS: Windows XP, 7, Server 2003, Vista Ultimate Memory: 2GB minimum (4GB recommended) LAN/WAN: 10/100 (Gigabit recommended) Hard Disk: 60Gb Interface: TCP/IP XML-based protocol

1939 144th Street



Ekahau is a trademark of Ekahau Corporation Inc.

Data Sheet No. EEW_EZcall_Ekahau_Wrapper_Spec_Sheet


EZcall Enterprise EGW – EZcall GuardRFID Wrapper Description The EZcall GuardRFID Wrapper is a bi-directional interface between an EZcall system and a GuardRFID RTLS system. The EGW integrates directly with an GuardRFID Argus server using the proprietary GuardRFID XML-based protocol to allow all GuardRFID SafeGuard, TotGuard and AllGuard alarms to be received and processed by EZcall, as well as allowing an EZcall system to dispatch alarm messages to GuardRFID staff tags. Every EGW networks to an EZcall DCS (Display Control Server) over a standard Ethernet LAN or WAN network using the TCP/IP protocol. A single EZcall DCS will support up to 10,000 supervised EGW client connections over a network allowing that many systems to be networked into an enterprise EZcall installation. Watchdog signals are used between the DCS and all EGW applications to ensure reliable communications.

Features • TCP/IP, UDP/IP, RS232, RS485 communications support • Secure encrypted server communications • Secure encrypted Argus server communications • Rapid setup and deployment • Real-time location and alarm information monitoring • Message dispatching to staff tags • May be run as an application or a supervised Windows service • User configurable priorities and messages • Integrated badge tag simulator for testing & troubleshooting • Extensive log reports simplify system troubleshooting

Supported Systems/Products GuardRFID Argus server EZcall DCS server System Requirements CPU: Intel Core2 Duo or Equivalent, >180MHz OS: Windows XP, 7, Server 2003, Vista Ultimate Memory: 2GB minimum (4GB recommended) LAN/WAN: 10/100 (Gigabit recommended) Hard Disk: 60Gb Interface: TCP/IP XML-based protocol

1939 144th Street



TotGuard, Argus, SafeGuard, AllGuard and GuardRFID are trademarks of GuardRFID Inc.

Data Sheet No. EGW_EZcall_GuardRFID_Wrapper_Spec_Sheet


EZcall Enterprise TPH – Touch-Panel Host Description The Touch-Panel Host is an EZcall server application to monitor alarm information from networked or serially-attached EZtouch panels. Various protocols are supported by the TPH client application that may be received by a direct serial, or supervised TCP/IP connection. Every TPH client networks to an EZcall DCS (Display Control Server) over a standard Ethernet LAN or WAN network using the TCP/IP protocol. A single EZcall DCS will support up to 10,000 supervised TPH client connections over a network allowing that many EZtouch panels and systems to be networked into an enterprise EZcall installation. Watchdog signals are used between the DCS and all TPH applications to ensure reliable communications.

The TPH client operates as a server that hosts any number of supervised EZtouch panels. All EZtouch events are logged by the TPH and instantly forwarded to the EZcall DCS server for immediate alarm dispatching and archiving. A single TPH can host any combination or 2.8 inch and 4.3 inch EZtouch panels. A single TPH may be sued to host both serially attached or Ethernet networked EZtouch panels providing flexibility of using home-run or daisy-chained cabling on a single system.

Features • TCP/IP, UDP/IP, RS485 communications support • Secure encrypted server communications • Rapid setup and deployment • May be run as an application or a supervised Windows service • Supervised touch panel connections • On-screen virtual touch-panel emulates the attached devices • Integrated simulator for testing & troubleshooting • Simple integration to an EZcall DCS server • Supports any combination or PoE Ethernet and RS485-looped EZtouch panels • Customizable priorities and alerts

Supported Systems/Products EZ-TP28E - 2.8” Color LCD PoE Ethernet EZtouch panels EZ-TP28S - 2.8” Color LCD RS485 serial EZtouch panels EZ-TP43S – 4.3” Color LCD RS485 serial EZtouch panels EZcall DCS (Display Control Server) System Requirements CPU: Intel Xeon Quad Core or Equivalent, >180MHz OS: Windows XP, 7, Server 2003, Vista Ultimate Memory: 2GB minimum (4GB recommended) LAN/WAN: 10/100 (Gigabit recommended) Hard Disk: >120Gb @ 7200RPM (>10,000RPM recommended) Interface: RS232 db9/Ethernet (alarm system dependent)

1939 144th Street




Data Sheet No. TPH_Touch_Panel_Host_Spec_Sheet


EZcall Enterprise EZtouch – Color Touch-Screen Panels Description The EZtouch panels are a user-friendly wall-mounted touch-screen panel that provide configurable alarm buttons and alarm display capabilities. EZtouch panels are available as PoE powered Ethernet devices and RS485 serial devices to allow multiple cabling configurations to be used. Each EZtouch panel supports from zero to 40 call buttons and may also be configured with an alarm display and/or door control & monitoring. Every EZtouch panel networks to an EZcall TPH (Touch Panel Host) over a standard Ethernet LAN/WAN network using the TCP/IP protocol or through an RS485 serial link. A single EZcall TPH will support up to 100,000 supervised EZtouch panel connections on a single system. Watchdog signals are used between the TPH and all EZtouch panels to ensure reliable supervised communications.

EZtouch panels are available in two sizes; 2.8” display and 4.3” display. EZtouch panels are water-resistant with an IP65 rating and may be cleaned using standard cleaners. All EZtouch panels are designed to mount in industry-standard North American electrical boxes and also have weatherproof surface-mount backboxes available for outdoor mounting. These cost effective touch panels provide an attractive and cost effective alarm initiation or display device that may be used virtually anywhere. EZtouch panels may be used as alarm initiation devices, to display alarms at strategic locations or as workflow control devices. With EZtouch panels, you are free to select which buttons you need at all locations and can add/remove buttons as required.

Features • Intuitive user-friendly call buttons • Timeout digital clock display helps reduce light emission during evenings. • Supervised connection alerts EZcall whenever a panel is disconnected or offline • PoE powered Ethernet and RS485 models available • Ethernet and RS485 models may be intermixed on a single TPH • Fully configurable and customizable buttons with icons • Alarm display (optional) • Door monitoring and control display (optional) • Integrated clean-screen option allows the screen to be cleaned • Quick and easy to setup • ESD Protection to 4kV • Wide operating temperature range from -20°C ~ 70°C • IP65 Waterproof front panel • Built-in alarm sounder (speaker on the EZ-TP43 models) • Very low power consumption (<2.5W) • 5-Year warranty

System Requirements EZcall TPH Touch Panel Host 12VDC power supply (RS485 models) IEEE 802.3af class 1 PoE network switch (Ethernet models)


Data Sheet No. EZtouch_Panels_Spec_Sheet


Physical Characteristics EZ-TP28 panels have a 2.8” TFT LCD color touch-screen display. EZ-TP28E is a PoE powered Ethernet model and the EZ-TP28S is an RS485 serially networked (up to 31 per loop) model. EZ-TP28S dimensions are similar to EZ-TP28E. EZ-TP43S panels hand a 4/3” TFT LCD color touch-screen display and are networked with an RS485 loop (up to 31). Specifications

1939 144th Street




EZcall Enterprise AIC - Alarm Input Client Description The Alarm Input Client is the input gateway for an EZcall system to retrieve alarm information from virtually any alarm system or hardware. Various protocols are supported by the AIC client application that may be received by a direct serial, TCP/IP, or UDP/IP connection. Every AIC client networks to an EZcall DCS (Display Control Server) over a standard Ethernet LAN or WAN network using the TCP/IP protocol. A single EZcall DCS will support up to 10,000 supervised AIC client connections over a network allowing that many systems to be networked into a single-node EZcall installation. Watchdog signals are used between the DCS and all AIC applications to ensure reliable communications.

Features • TCP/IP, UDP/IP, RS232, RS485 communications support • Supports XLM, SOAP, TAP, and Proprietary protocols • Secure encrypted server communications • Rapid setup and deployment • AIC hardware appliance; reduces setup/deployment time • May be run as an application or a supervised Windows service • Virtual COM port support • Integrated simulator for testing & troubleshooting • Built-in web-server provides instant alarm display & activity monitoring • Extensive log reports simplify system troubleshooting

Supported Systems/Products Fire Alarm Systems Nurse Call Systems Intercom Systems Edwards EST-3 serial interface Dukane Procare 6000 VM input Algo VoiceComm 3400 OAI input Edwards Quick serial interface Dukane Procare 2000 network input Dukane Starcare OAI input Simplex 4100U serial input Dukane Procare 6000 ARMS input Edwards AccuSound Network input Simplex 5000 serial input Dukane Procare 6000 OAI input Maxivox MC1 network interface Notifier AM2020 serial Dukane Procare 6000 TAP input Sentex Infinity Mircom serial Dukane StaffCall Pro Network input Honeywell XLS-1000 serial GE Caregard modem input Other Alarm Systems

GE Telligence Telergy TAP input Andover Continuum ascii input GE Telligence SQL database interface Genetec Synergis/Omnicast Hill-Rom ComLite network input GE Facility Commander

Paging System Emulation Maxivox Maxicomm I network interface GE Summit Pro PET input Ascom Wireless paging input Maxivox Maxicomm II network interface Kantech Enterprise/Global Generic TAP server emulation Rauland Responder 3000 net-controller Keyscan Visiplex pocket paging input Rauland Responder 4000 PIP OAI RBH Axiom COMP1 / COMP2 paging input Rauland Responder IV TAP input Senstar Stellar StarNet Globestar Formatted TAP input Tunstall CMS4000 OAI serial interface X-Mark Halo TAP input Home Free AMS ElmoPage input Zettler Sentinel 500 TAP input X-Mark Hugs/MyCall/FintIt Nordicom AL800 server West-Com Endeavour/Novus/Odyssey+ X-Mark RoamAlert TAP input Salcom paging server Tektone NC300 / NC300 II Visonic Eiris OAI input Scope paging server Ascom TeleCARE / TelePROTECT Visonic Eiris 3.0 UDP capture

Simplex EZcare TAP input ADAM-6000 I/O boards Austco APR protocol Ontrak ADR2000 I/O boards

System Requirements CPU: Intel Core2 Duo or Equivalent, >200MHz OS: Windows XP, 7, Server 2003, Vista Ultimate Memory: 2GB minimum (4GB recommended) LAN/WAN: 10/100 (Gigabit recommended) Hard Disk: 120Gb Interface: RS232 db9/Ethernet (alarm system dependent)

1939 144th Street




Data Sheet No. AIC_Alarm_Input_Client_Spec_Sheet


EZcall Enterprise VKC – Virtual Keypad Client Description The Virtual Keypad Client is the input gateway for an EZcall system to retrieve alarm information from various intrusion alarm systems. Various protocols are supported by the VKC client application that may be received by a direct serial, TCP/IP, or UDP/IP connection. Every VKC client networks to an EZcall DCS (Display Control Server) over a standard Ethernet LAN or WAN network using the TCP/IP protocol. A single EZcall DCS will support up to 10,000 supervised VKC client connections over a network allowing that many intrusion alarm systems to be networked into a single-node EZcall installation. Watchdog signals are used between the DCS and all VKC applications to ensure reliable communications.

The VKC client also includes a built-in web-server that allows operators to connect to the VKC and it’s associated intrusion alarm system through any standard web browser. All intrusion alarm keypad functions including arming, disarming, and bypassing zones are supported through the intuitive on-screen virtual keypad that emulates the actual keypads functions.

Features • TCP/IP, UDP/IP, RS232, RS485 communications support • Secure encrypted server communications • Rapid setup and deployment • May be run as an application or a supervised Windows service • Virtual COM port support • On-screen virtual keypad emulates the attached system • Integrated simulator for testing & troubleshooting • Built-in web-server provides instant alarm display & system control • Extensive log reports simplify system troubleshooting

Supported Systems/Products DSC Maxsys DSC Power864 GE NetworX GE Concord GE Advent Honeywell/Ademco Vista Paradox Esprit Paradox Spectra System Requirements CPU: Intel Xeon Quad Core or Equivalent, >180MHz OS: Windows XP, 7, Server 2003, Vista Ultimate Memory: 2GB minimum (4GB recommended) LAN/WAN: 10/100 (Gigabit recommended) Hard Disk: >120Gb @ 7200RPM (>10,000RPM recommended) Interface: RS232 db9/Ethernet (alarm system dependent)

1939 144th Street




Data Sheet No. VKC_Virtual_Keypad_Client_Spec_Sheet


EZcall Enterprise BBC – Button Bar Client Description The Button Bar Client is a unique input client used to generate alarms on an EZcall system from a PC desktop. The Button Bar Client is fully customizable to provide any quantity and type of on-screen button with different functions. The BBC provides a non-intrusive bar on a PC desktop that can be hidden away until needed. Ideal uses include nurse station porter and cleaner requests, and non-conventional workflow requests. Buttons may be added or deleted from the bar and configured individually on each desktop. Every BBC client networks to an EZcall DCS (Display Control Server) over a standard Ethernet LAN or WAN network using the TCP/IP protocol. A single EZcall DCS will support up to 10,000 supervised BBC client connections over a network allowing that many systems to be networked into a single-node EZcall installation. Watchdog signals are used between the DCS and all BBC applications to ensure reliable communications.

Features • Attractive display does not take-up the entire screen • Configurable wards or areas – only display the locations that are needed • May be run as an application or a supervised Windows service • Event list display • Lockable to prevent shutting-down or relocating the window • Extensive log reports simplify system troubleshooting

System Requirements CPU: Intel Core2 Duo or Equivalent, >180MHz OS: Windows XP, 7, Server 2003, Vista Ultimate, Linux Ubuntu 9.0 Memory: 2GB minimum (4GB recommended) LAN/WAN: 10/100 (Gigabit recommended) Hard Disk: 60Gb

1939 144th Street




Data Sheet No. BBC_Button_Bar_Client_Spec_Sheet


EZcall Enterprise CAC – Command Argument Client Description The Command Argument Client is an output gateway for an EZcall system to output standard DOS-like commands to control various specialized systems. The Command Argument Client may be fully customized to generate virtually any command-line argument output needed. Every CAC client networks to an EZcall MDS (Message Dispatch Server) over a standard Ethernet LAN or WAN network using the TCP/IP protocol. A single EZcall MDS will support up to 10,000 supervised CAC client connections over a network allowing that many systems to be networked into a single-node EZcall installation. Watchdog signals are used between the DCS and all CAC applications to ensure reliable communications.

Features • Fully configurable & customizable command-line arguments • Secure encrypted server communications • Rapid setup and deployment • May be run as an application or a supervised Windows service • Virtual COM port support • Integrated testing & troubleshooting utility • Extensive log reports simplify system troubleshooting

System Requirements CPU: Intel Core2 Duo or Equivalent, >180MHz OS: Windows XP, 7, Server 2003, Vista Ultimate Memory: 2GB minimum (4GB recommended) LAN/WAN: 10/100 (Gigabit recommended) Hard Disk: 60Gb

1939 144th Street



Data Sheet No. CAC_Command_Argument_Client_Spec_Sheet

DOS is a registered trademark of Microsoft Corp.


EZcall Enterprise EDC – Event Display Client Description

The Event Display Client is an output client used to display alarm or status messages on a computer output display. The Event Display Client is fully configurable to display events from specific areas and/or specific call types and priorities. Some uses include centralized Code Blue annunciators, local annunciators, maintenance or housekeeper alarm displays. Every EDC client networks to an EZcall DCS (Display Control Server) over a standard Ethernet LAN or WAN network using the TCP/IP protocol. A single EZcall DCS will support up to 10,000 supervised EDC client connections over a network allowing that many systems to be networked into a single-node EZcall installation. Watchdog signals are used between the DCS and all EDC applications to ensure reliable communications.

Features

Skin’able border images allow for a customized appearance of the display Configurable wards or areas – only display the locations that are needed Selectable priorities – only display the events types that are required Configurable time – allows events to only generate popups at certain times-of-day Hidden mouse pointer support May be run as an application or a supervised Windows service Configurable fields and text size, color & font Date/Time display Configurable screen size and location with locking capability to ensure that

the display is always shown at the same location every time it is started Multiple EDC support – run several EDC windows on the same computer to

display various event types or areas on a single display Windows and Linux versions available Support for Microsoft Agent popup characters Extensive log reports simplify system troubleshooting

System Requirements

CPU: Intel Core2 Duo or Equivalent, >180MHz OS: Windows XP, 7, Server 2003, Vista Ultimate, Linux Ubuntu 9.0 Memory: 2GB minimum (4GB recommended) LAN/WAN: 10/100 (Gigabit recommended) Hard Disk: 60Gb

1939 144th Street




EZcall Enterprise PDC – Popup Display Client Description

The Popup Display Client is an output client used to display alarm or status messages on a computer output display. The Event Display Client is fully configurable to display events from specific areas and/or specific call types and priorities. Some uses include centralized Code Blue annunciators, local annunciators, maintenance or housekeeper alarm displays. Every EDC client networks to an EZcall DCS (Display Control Server) over a standard Ethernet LAN or WAN network using the TCP/IP protocol. A single EZcall DCS will support up to 10,000 supervised EDC client connections over a network allowing that many systems to be networked into a single-node EZcall installation. Watchdog signals are used between the DCS and all EDC applications to ensure reliable communications.

Features

Select from over 10 different window types Configurable wards or areas – only display the locations that are needed Selectable priorities – only display the events types that are required Configurable time – allows events to only generate popups at certain times-of-day May be run as an application or a supervised Windows service Configurable fields and text size, color & font Text-to-speech and sound file support allows sounds to be used in conjunction with a visual popup window Lockable to prevent operators from shutting-down the alarm display Extensive log reports simplify system troubleshooting

System Requirements

CPU: Intel Core2 Duo or Equivalent, >180MHz OS: Windows XP, 7, Server 2003, Vista Ultimate, Linux Ubuntu 9.0 Memory: 2GB minimum (4GB recommended) LAN/WAN: 10/100 (Gigabit recommended) Hard Disk: 60Gb

1939 144th Street




EZcall Enterprise TTC – Text Talker Client Description

The Text Talker Client is a Text-to-Speech output client that allows alarm messages to be verbally announced using a PC speaker output. The Text Talker Client is compatible with most industry-standard text-to-speech engines and voices and supports multi-language translation. A TTC client may be configured to output specific wards or areas or all areas to provide multiple output alarm messaging using standard spoken messages rather than pre-recorded alerts. Every TTC client networks to an EZcall MDS (Message Dispatch Server) over a standard Ethernet LAN or WAN network using the TCP/IP protocol. A single EZcall MDS will support up to 10,000 supervised TTC client connections over a network allowing that many systems to be networked into a single-node EZcall installation. Watchdog signals are used between the DCS and all TTC applications to ensure reliable communications.

Features

Fully configurable & customizable using several brands of text-to-speech voice Configurable time – allows events to only output at certain times-of-day Secure encrypted server communications Rapid setup and deployment May be run as an application or a supervised Windows service Supports text-to-speech, pre-recorded .WAV files or a combination of both Support for Microsoft Agent popup characters Built-in abbreviation and phonetic translator to ensure that all messages are understood Integrated testing & troubleshooting utility Extensive log reports simplify system troubleshooting

System Requirements

CPU: Intel Core2 Duo or Equivalent, >180MHz OS: Windows XP, 7, Server 2003, Vista Ultimate Memory: 2GB minimum (4GB recommended) LAN/WAN: 10/100 (Gigabit recommended) Hard Disk: 60Gb

1939 144th Street




EZcall Enterprise TDC – Target Display Client Description The Target Display Client is a unique output client used to display real-time staff response times or call activity. The Target Display Client is fully configurable to display events from specific areas and allows you to set a specific target response time. Only events outside the target time will increment the counter and be displayed. Ideal uses include manager heads-up display for at-a-glance status reporting and worker incentive displays. Every TDC client networks to an EZcall DCS (Display Control Server) over a standard Ethernet LAN or WAN network using the TCP/IP protocol. A single EZcall DCS will support up to 10,000 supervised TDC client connections over a network allowing that many systems to be networked into a single-node EZcall installation. Watchdog signals are used between the DCS and all TDC applications to ensure reliable communications.

Features • Attractive display does not take-up the entire screen • Configurable wards or areas – only display the locations that are needed • May be run as an application or a supervised Windows service • Event list display • Lockable to prevent shutting-down or relocating the window • Extensive log reports simplify system troubleshooting

System Requirements CPU: Intel Core2 Duo or Equivalent, >180MHz OS: Windows XP, 7, Server 2003, Vista Ultimate, Linux Ubuntu 9.0 Memory: 2GB minimum (4GB recommended) LAN/WAN: 10/100 (Gigabit recommended) Hard Disk: 60Gb

1939 144th Street




Data Sheet No. TDC_Target_Display_Client_Spec_Sheet


EZcall Enterprise NWC – Network Watchdog Client Description

The Network Watchdog Client is an input client that allows an EZcall system to supervise network software components and hardware. The Network Watchdog Client monitors other network devices by sending requests for their response. The NWC client will alert the DCS server of any network components that is unresponsive to generate a system alarm or perform other actions. Various protocols are supported by the NWC client application including; PING, SNMP, and MAC ID request. Every NWC client networks to an EZcall DCS (Display Control Server) over a standard Ethernet LAN or WAN network using the TCP/IP protocol. A single EZcall DCS will support up to 10,000 supervised NWC client connections over a network allowing that many intrusion alarm systems to be networked into a single-node EZcall installation. Watchdog signals are used between the DCS and all NWC applications to ensure reliable communications.

Features

TCP/IP, UDP/IP, SNMP, PING communications support Rapid setup and deployment May be run as an application or a supervised Windows service Receive alerts of unresponsive critical network components Integrated testing & troubleshooting utilities Extensive log reports simplify system troubleshooting

System Requirements

CPU: Intel Core2 Duo or Equivalent, >180MHz OS: Windows XP, 7, Server 2003, Vista Ultimate Memory: 2GB minimum (4GB recommended) LAN/WAN: 10/100 (Gigabit recommended) Hard Disk: 60Gb

1939 144th Street




EZcall Enterprise SPC – Serial Paging Client Description The Serial Paging Client is the output gateway for an EZcall system to forward alarm text messages to various SMS and paging systems or serial printers. Various protocols are supported by the SPC client application that may connect by a direct serial, TCP/IP, or UDP/IP connection. Every SPC client networks to an EZcall MDS (Message Dispatch Server) over a standard Ethernet LAN or WAN network using the TCP/IP protocol. A single EZcall MDS will support up to 10,000 supervised SPC client connections over a network allowing that many systems to be networked into a single-node EZcall installation. Watchdog signals are used between the DCS and all SPC applications to ensure reliable communications.

Features • TCP/IP, UDP/IP, RS232, RS485 communications support • Secure encrypted server communications • Rapid setup and deployment • SPC hardware appliance; reduces setup/deployment time • May be run as an application or a supervised Windows service • Virtual COM port support • Built-in abbreviation translator to ensure that all messages fit the mobile device screens • Integrated simulator for testing & troubleshooting • Extensive log reports simplify system troubleshooting

Supported Protocols COMP1 / COMP1 Visonic SL-PTX Poltys DCC output (Eiris emulation) TAP/PET 1.8 (serial & dial-up) Edwards EST-3 printer emulation Pelco P & D ascii output Visiplex basic EZcall serial printer detailed Salcom paging protocol Visiplex VS-40 EZcall serial printer simple Scope paging protocol Ascom Enhanced TAP Waveware protocol SecureTech WAVE 2-way radio output J-Tech Extended Zetron TAP (capcode support) Austco APR Globestar formatted TAP Nordicom AL800 GE Telergy 7.1 TAP (GUID support) System Requirements CPU: Intel Core2 Duo or Equivalent, >180MHz OS: Windows XP, 7, Server 2003, Vista Ultimate Memory: 2GB minimum (4GB recommended) LAN/WAN: 10/100 (Gigabit recommended) Hard Disk: 60Gb Interface: RS232 db9/Ethernet (paging system dependent)

1939 144th Street




Data Sheet No. SPC_Serial_Paging_Client_Spec_Sheet


EZcall Enterprise TPC – Telephone Paging Client Description The Telephone Paging Client is the output gateway for an EZcall system to forward alarm text messages to various wired and wireless telephony systems. Various protocols are supported by the TPC client application that may connect by a direct serial, TCP/IP, or UDP/IP connection. Every TPC client networks to an EZcall MDS (Message Dispatch Server) over a standard Ethernet LAN or WAN network using the TCP/IP protocol. A single EZcall MDS will support up to 10,000 supervised TPC client connections over a network allowing that many systems to be networked into a single-node EZcall installation. Watchdog signals are used between the DCS and all TPC applications to ensure reliable communications.

Features • TCP/IP, UDP/IP, RS232, RS485 communications support • Secure encrypted server communications • Rapid setup and deployment • TPC hardware appliance; reduces setup/deployment time • May be run as an application or a supervised Windows service • Virtual COM port support • Built-in abbreviation translator to ensure that all messages fit the mobile device screens • Integrated simulator for testing & troubleshooting • Extensive log reports simplify system troubleshooting

Supported Systems/Products Nortel Companion Polycom Spectralink Lin150/Link3000 Polycom Spectralink NetLink Polycom Kirk Ascom Analog Ascom VoIP Cisco 7900 series telephones NEC OpenWorX Panasonic KX-TDx Generic TAPI/SAPI Vocera System Requirements CPU: Intel Core2 Duo or Equivalent, >180MHz OS: Windows XP, 7, Server 2003, Vista Ultimate Memory: 2GB minimum (4GB recommended) LAN/WAN: 10/100 (Gigabit recommended) Hard Disk: 60Gb Interface: RS232 db9/Ethernet (telephony system dependent)

1939 144th Street




Data Sheet No. TPC_Telephone_Paging_Client_Spec_Sheet

E zcall all_spec_sheets

Technology

Transcript of E zcall all_spec_sheets