|
Via the MQTT interface an application server is able to request the Location from the handset. The location information can be based on:
|
1. Example set-up using an Ubuntu server |
The following test environment is used for the documentation.
- Ubuntu server
- Gigaset N870 with the latest firmware
- Application server / MQTT interface enabled
- DECT handset that supports DECT location request like SL800H
- DECT handset has location license enabled
Ubuntu preparation
First we installed the mosquitto client: sudo apt install mosquitto-clients
Host file:
Add the N870 to your host file in case you want to use a DNS name. (/etc/hosts)
127.0.0.1 localhost 127.0.1.1 Int-VirtualBox 192.168.178.192 int-589ec60e71c0 # The following lines are desirable for IPv6 capable hosts ::1 ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters |
2. How to see the MQTT response |
Before you start sending the first location request, you would also like to see the response of the Cordless system.
You can do this by opening a new command line window on the Linux PC and enter the command.
mosquitto_sub -u as1 --psk-identity as1 --psk 123456789012345678901234567890ab -t +/+/as1/pos/# -p 8884 -h 192.168.178.190 -v |
local/035edb3a92/as1/pos/res/position {"msgId":"pos_2","payload":{"ble":{},"dm_handover":"no","dm_id":"local","dps":{"bases":[{"fpn":"f1","rpn":"03","rssi":"54"},{"fpn":"f1","rpn":"02","rssi":"34"}],"bs_fpn":"f1","bs_mac":"7c2f80c7326d","bs_name":"Backside","bs_rpn":"03","timestamp":"1623405168"},"ipui":"035edb3a92","sip_id":"1013"}} |
3. DECT location request |
With the following command you can ask for the location information from the handset using the SIP ID
In the answer below the handset was connected to DM2 and there was no synchronization between DM2 and DM1. The DECT handset is only able to see BSs from all synchronized cluster it is in sync with. Cluster may be synced within DM range and/or inter DM. As it is not synchronized with DM1, you do not see the bases from DM1.
In the answer below the handset was connected to DM1 and there was synchronization between DM2 and DM1. The DECT handset is able to see BSs from all synchronized cluster it is in sync with. Therefore you can see now 3 base stations in the respond.
|
4. Bluetooth (BLE) location request |
With the following command you can ask for the BLE location information from the handset using the SIP ID
In the answer below the handset belonging to sip_id 1013 (S700H) found one SL800H acting as BLE Beacon SL800H handset, 589ec626c098, Type: Beacon, UUID: 75E072C3AAAB4E97AF357BB7FA1A0BE8, MAYOR: C098, MINOR: C626, INTERVAL: 250
|
5. DECT and BLE location request |
With the following command you can ask for the DECT and BLE location information from the handset using the SIP ID
|
6. Location request timing (Caching) |
If the system receives an location request (DECT + Bluetooth) via MQTT:
- DECT location request will take around 5 seconds
- Then Bluetooth search is done, duration: "search time-out in MQTT command"
- Results are cached for 10 seconds (To protect system against location request flooding)
- DECT and Bluetooth have an own cache
Example DECT + Bluetooth location request:
Send an DECT + Bluetooth Location request (MQTT) with the search time-out = 5 seconds "A".
If we would send an new Location request "B" 17 seconds later, we would receive new DECT location values and cached Bluetooth values.
Sending a new location request after 20 seconds "C" results in new DECT and Bluetooth location values.
Example Bluetooth location request:
Send an Bluetooth Location request (MQTT) with the search time-out = 5 seconds "A".
If we would send an new Location request "B" 13 seconds later, we would receive cached Bluetooth values. (Syslog message: send cached ble result)
Sending a new location request after 17 seconds "C" results in new Bluetooth location values.