Manitou - MediaGateway - Climax Telecare Devices - Installation

12/27/2023 4:13 pm EST

Climax Telecare Devices are small pendant/jewelry devices with a button that sends a TCP signal and places a call in the event of a medical emergency is occurring.

Pre-Install

The install steps are for after Instant Connect has been installed and tested. This is considered an addition to that. If Instant Connect has not been setup previously, please see the documentation for setting up and testing instant connect before proceeding.

Install Notepad++

Update Customer's License

  • License for Universal Connector
    • TCP Connector
  • License for Instant Connect - Two Way Lines.

Download Install Package

The install package for Climax Devices includes a data map and a menu. The datamap is necessary for the TCP connector and the menu is necessary for handling the climax instant connect calls.

Installation

Manitou Event Configuration

For the installation, a custom event code of 'CX' will be created. It will need to be a lower priority of an MA otherwise the signal priority flow will not be correct. Please follow the instructions below to add the CX event.

  1. Open the SWS and navigate to event codes (Maintenance ? Events ? Event Codes)
  2. Select MA and note the following.

    • Do not change the customer's setting if the MA configured differs from the MA screenshot below.

    • Make note of the Medical Alarm's Priority (default of 2)
    • Make note of the Default Action Pattern.
      • Verify with the customer that the default action pattern specified is used. If not, ask the customer what action pattern is used and make note of that.  
  3. Verify that CX is not already added for a different integration, if it is please contact level 3 support for assistance on making changes necessary. (*CX is not the same as CX and can be ignored)
  4. Enter Edit Mode and Select Add
  5. Enter an Event Code of CX and a description of Climax Activation and select OK.
  6. Enter in the following information:
    • Event Category - System Alarms
    • Alarm - Yes
    • Priority - 2 more than the integer set for the priority of MA (This makes it a lower priority)
    • Default Action Pattern - Same as MA (this will be changed later)
    • Customer Attributes - E
    • Viewed Alarm Changes Warning Level - 90
    • Viewed Alarm Changes Danger Level - 180
    • Actioned Alarm Changes Warning Level - 60
    • Actioned Alarm Changes Danger Level - 90
    • Alarm Color Foreground - White
    • Alarm Color Background - Red
    • See the screenshot below for the full configuration  
  7. Select Save to apply the new Event Code
  8. Open Event Maps to add CX to the SIA Event Map. (Maintenance? Events? Event Maps)
  9. Change the selected Protocol Format to SIA.
  10. Enter Edit mode by selecting Edit.
  11. Scroll to the bottom of the Event Codes configured under SIA.
  12. Add a new Events Code by entering in the following:
    • Message - CX
    • Decode Qualifier - 0
    • Event Code - CX (from dropdown)
    • No Description
    • No Attributes
    • Comment - Climax Device
    • See the screenshot below for details  
  13. Select Save to apply changes.

Add the Transmitter Type

A Transmitter Type will be added that is Audio Capable. It is important to note that the Transmitter Type will be used for both the TCP signal received as well as the Medical Alert created that is audio capable.

  1. Open the Operator Workstation (OWS)
  2. Navigate to Transmitter Types (Maintenance ? Transmitter Types)
  3. Enter Edit Mode
  4. Select Add
  5. Within the popup window, specify the following:
    • Type - CLIMAX
    • Description - Climax Device
    • System Type - Event Monitoring
    • See screenshot for details

  6. Select OK and the Climax Transmitter Type will be added.
  7. Under attributes, check Audio Capable.
  8. Set the Audio Type to whatever is configured for Instant Connect. (If there is no Audio Type configured, please see documentation on setting up Instant Connect)

  9. Select the Programming Tab located at the bottom.

  10. Add two Input Transmitter Programming Lines, one for CX and another for MA.
  11. Set the Output Event of CX to CX and the output event of MA to MA
  12. Add a Command on MA to be Audio Capable.
    1. Select the Commands Cell directly to the right of MA.
    2. Select the Ellipses that appears.
    3. Select Audio(Type, Delay) and then select the Greater Than symbol to add.
    4. Leave Options as default (Type - Yes, Delay - 0) and select OK

  13. Verify the Transmitter Programming lines look similar to the screenshot and select save to apply all changes.

MediaGateway Configuration

Setting up the Mediagateway will review both the install for a TCP Connector and Instant Connect. Those will not be reviewed in this document in detail, but the configurations will be briefly discussed as the installation process is already detailed in other documents.

TCP Connector Configuration

The TCP Connector must be through the MediaGateway and not through the BoldXML receiver driver as it will have multiple devices that connect to it. It is a listen port and has now a special configuration aside from the check box "Map File Name to Fieldset". It is recommended to label the TCP Connector as "IP Connect Climax" for consistency with the installation documented. Please see the screenshot below for any additional details of configuring the TCP Connector.

TCP Datamap and Menu Configuration

The Datamap for the TCP Connector is provided as part of the ClimaxTelecareInstallPackage.zip file. The Menu, however, is the same UCSend datamap that is detailed within the TCP Connector documentation. Once the Datamap and Menu are both added, the line driver can be configured. The FEP, Receiver and a specific Line are all recommended for easy review within the Raw Data Log in the OWS or SWS. This will then be mapped to a line within the receiver configuration in Manitou (documented further down). Please refer to the following screenshot as an example.

Instant Connect Configuration

The amount of lines to be used is determined generally by the customer. At minimum 2 should be added, however, it is recommended to have 4 configured per phone line. For example, In the screenshot below assume the customer has two numbers configured (719) 358-4700 and (719) 358-4710. (719) 358-4700 corresponds to 4 lines (8 through 11) and (719 358-4710 corresponds to an additional 4 lines (12 through 15). If a call was then placed to the 4700 number it would reach line 8 first, and if another call was placed at the same time it would then roll past 8 which is being used to 9.

The lines configured should be uniquely identified for each Line Driver. This is to allow easy identification within the raw-data log in Manitou of which line the signals came from.

Important: Do not specify lines already in use by other drivers!

The Menu configured for the lines is included in the ClimaxTelecareInstallPackage.zip file. It is the same as the TwoWay Instant Connect menu, aside from sending a Medical Alarm instead of an Activation. It has been included and labeled this way to provide separation from possible custom menus created for Elevator or other Instant Connect setups. See the screenshots below for the Menu structure and component properties of the Send Signal MFC.

Creating Receiver Lines

Creating Receiver Lines should be detailed already in the InstantConnect documentation, however, it is reviewed here as well in regards specifically to the Climax Telecare Integration. It is assumed that each line driver configured has a line specified to it already. It is important to be sure that the lines configured are not already in use by other MediaGateway connectors/drivers.

  1. Open the SWS if not already open.
  2. Navigate to Receivers.
  3. Select Edit to enter Edit Mode.
  4. Select Rec Line Prefixes and then select Add
  5. Add the following information to the Add Receiver Line Prefix pop-up window.
    • Receiver Line Prefix - CX
    • Description - Climax Device
  6. Select OK and then Select Save.
  7. Select Edit again.
  8. Select the MediaGateway Receiver (already created as part of the MediaGateway install instructions)
  9. Select Add
  10. Add the following information to the Add Receiver Line Map pop-up window.
    • Receiver Line Prefix - CX | Climax Device
    • Description - Climax Device
    • Starting Number - This should match the line configured on the Line Driver
    • Number to Add - This can be left as default to add a single Receiver Lines Map, or if you are looking to add additional incrementing lines, you can set it to add the number of lines to add.
      For example - if there are 4 lines to add starting from 8 that will end with 11, set the Number to Add to 4 to add all 4 lines in one go.
    • Please note: In addition to adding the lines for the Instant Connect Line Drivers, this is also where the TCP Connector Line is added. For the examples below, Lines 8 through 15 are all Instant Connect Line Drivers, whereas Line 80 is the TCP Connector.

Create a default action pattern

For the instructions below, we will be adding a global default action pattern. This means we will be setting it at the monitoring company level. It is recommended you talk to the customer first before proceeding to make sure they are okay with adding it at the Monitoring Company level. If necessary, the action pattern can be added at the customer level instead, however the default action pattern specified will remain as whatever was first specified in the instructions above.

  1. Open the OWS if not already open.
  2. Navigate to the Monitoring Company (Maintenance ? Monitoring Company)
  3. From the Jump To Menu select Action Patterns
  4. Enter Edit Mode and Select Add
  5. Specify the Following information within the Add Action Pattern pop-up window.
    • Copy From - This can be used if the customer wants a similar action pattern as what is used for the Medical Alarms.
    • Action ID - CLIMAX
    • Description - Climax Device Activation
    • Category - <Default>
    • Ignore all other fields (leave blank)
  6. Select OK
  7. Select Attention from the Command selection dropdown.

  8. Within the Attention text box, specify attention to the operators that a Medical Alarm is supposed to follow. Use the following unless the customer specifies otherwise.
    • "A Medical Alarm is to follow this alarm within 30 seconds containing a call. If a call/Medical Alarm is not received, please contact the customer!"
  9. Select Add Item to add it to the action pattern.
  10. If an action pattern was copied, move the attention action to the top of the action pattern using the arrow keys located on the right.

  11. If an action pattern was not copied, add a contact customer action.
    1. Select Contact from the Command selection dropdown
    2. from the Contact List, select Customer

    3. Select Add
    4. Leave all options as default/blank and Select OK in the Contact Action pop-up window.
  12. Verify with the customer if other items need/want be added. Please see the screenshot of a recommended action pattern used on other integrations.  
  13. Select Save to apply all changes.
  14. Open the SWS if not already open.
  15. Navigate to Event Codes (Maintenance ? Events ? Event Codes)
  16. Select Edit
  17. Select the CX event code
  18. Specify the Default Action Pattern to CLIMAX
    • If the Action Pattern does not display, close the Event Codes window (Ctrl +F4) and reopen.
    • This is caused due to the Event Codes window being left open before the Global Action Pattern on the Monitoring Company was added.
  19. Select Save to apply all changes.

Creating Transmitters

The instructions below detail adding transmitter to an already existing account/test account.

  1. Open the OWS and open a test account.
  2. Navigate to Systems within the Jump To menu.
  3. Select Edit
  4. Select Event Monitoring within the inner left Menu list
  5. Select Add
  6. Enter in the Following information in the Add System pop-up window.
    • System Number - Leave as defaulted Value
    • Description - Climax Device Monitoring
    • System Type - Event Monitoring
    • Monitoring Type - Alarms Only
    • See screenshot for details

  7. Select OK
  8. Select Transmitters Under the Event Monitoring System just added and select Add.
  9. Specify in the description the phone number of the device that will be calling in.
  10. Select OK
  11. Enter the following information into the Transmitter
    • Transmitter Type - CLIMAX
    • Receiver Line Prefix - CX
    • Transmitter ID - The phone number of the device calling in.
    • Audio Capable should already be checked, if not, verify the audio type is set correctly on the Transmitter Type configured.
    • See screenshot for details  
  12. Select Save to apply all changes
  13. Enter Edit Mode again
  14. Select Transmitters Under the Event Monitoring System just added and select Add.
  15. Specify MG#### where #### is filled with the TXID the device will be sending in via the TCP Connection.
  16. Select OK
  17. Enter in the following information to the Transmitter
    • Transmitter Type - CLIMAX
    • Receiver Line Prefix - CX
    • Transmitter ID - The TXID the device will be sent in via the TCP Connection.
    • Audio Capable should already be checked, if not, verify the audio type is set correctly on the Transmitter Type configured.
    • See screenshot for details   
  18. Select Save

Testing the Integration

At this moment everything is setup and ready for testing. To test, have the customer press the button on the Climax Telecare Device to place a call. The call will be made and you will see 3 signals come into Manitou.

  1. The first signal received is the device's TCP signal.
    • This signal will have the event code CX and will soon be replaced by the Medical Alarm.
  2. The second signal received is a listen-in and will likely be logged.
  3. The third signal received is a higher priority MA.
    • If an operator has already picked up the CX, they will be notified a higher priority alarm has been received and will be requested to handle it. Be sure the operator selects 'Yes' to handle the new higher priority signal.
    • If an operator has not already picked up the CX, only the MA will be shown in the alarm queue.

These signals can be verified in the Raw Data log, and should appear similar to the following screenshot.

Once a signal has been processed and handled, the customer activity log can be verified that the action pattern and escalation occurred properly. See the following screenshot as an example.

A customer's configuration can vary depending on their Central Station's need and pre-existing configuration. This document serves only as a guide toward setting up the Climax Telecare Devices and their intended functionality.

Was this article helpful?
Thank you for your feedback!
User Icon

Thank you! Your comment has been submitted for approval.

Copyright © 2024-26 Bold Group All rights reserved.