| Html |
|---|
<div class="lang-box-pdf">
<div>
<div class="google-lang">
<div id="google_translate_element">
</div>
<script type="text/javascript">
function googleTranslateElementInit() {
new google.translate.TranslateElement({pageLanguage: 'en', includedLanguages: 'de,es,fr,it,nl', autoDisplay: false}, 'google_translate_element');
}
</script>
<script type="text/javascript" src="//translate.google.com/translate_a/element.js?cb=googleTranslateElementInit"></script>
</div>
<div class="pdf-button">
<a href="https://confluence.wildix.com/spaces/flyingpdf/pdfpageexport.action?pageId=80708434" alt="Convert to .pdf" title="Convert to .pdf"><img src="https://confluence.wildix.com/download/attachments/14549012/pdf-button-download-wildix-documentation.png"></a>
</div>
</div>
</div> |
...
| Info |
|---|
This Guide explains how to get the location of the nearest W-AIR Base Station in W-AIR Network in case of emergency alarm triggered on W-AIR Handset.
Created: December 2020 Permalink: https://confluence.wildix.com/x/UoPPB |
| Table of Contents |
|---|
Description
The operator who receives the alarm triggered by a W-AIR handset can receive the information about the closest Base Station and the type of alarm. This information is passed using Messaging protocol enabled on W-AIR starting from the firmware indicated in this document.
To differentiate the type of alarms and the base stations you can record your own system prompts or use the Text-To-Speech (TTS) service.
The PBX can pass the information about the closest base station based on the RPN of the base station and the RSSI levels passed by the handset. RSSI levels indicate which base station is currently the closest one to the handset.
Requirements
- Hardware/ Virtual PBX
- W-AIR Network set up on the PBX
- W-AIR firmware starting from v. 0501b5
...
- Edit call file template config located in the file /var/lib/callweaver/dialplan/alarm.template.
Follow the prompts in the file to edit it:
| Code Block |
|---|
# Call file template. Supported values (should be in {{}}):
# ID1, ID2 ... - RFPI Addresses, 10 hex digits, in descending signals level order, check it on the web interface of a base, Home/Status page
# SHORTID1, SHORTID2 ... - 2 last digits of IDs
# LEVEL1, LEVEL2 ... - corresponding signal levels, optional
# EXTENSION - extention of alarmed device
# NAME - user name of alarmed device
# TYPE - type of alarm, one decimal digit, check it on the web interface of a base, Alarm page, Idx column
Channel: Local/alarms@alarm-wair
Callerid: "{{NAME}}" <{{EXTENSION}}>
WaitTime: 60
MaxRetries: 3
RetryTime: 30
Context: alarm-wair, specify Dialpan procedure used for managing W-AIR calls here
Extension: {{SHORTID1}}{{TYPE}}
Priority: 1
Setvar: base={{ID1}} |
...
| Note |
|---|
The following IDs correspond to the alarm types:
|
Here is an example of how you can specify called numbers in the alarm-wair Dialplan:
...