FAQ - AML: Location

Valid for N670 / N870 / N870E but not supported by N610. Software 2.52 or higher is needed.

Via the MQTT interface an application server is able to request the Location from the handset.

The location information can be based on:

DECT
- Supported by: SL800H / S700H / R700H / S650H / SL750H / OpenStage M3
- Provides raw DECT RSSI values
Bluetooth
- Supported by: SL800H / S700H / R700H
- Provides Bluetooth RSSI values transmitted by BLE beacons
DECT and Bluetooth

1. Example set-up using an Ubuntu server

Scroll to top

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

Scroll to top

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

Example response

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"}}
local/1013/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

Scroll to top

With the following command you can ask for the location information from the handset using the SIP ID

sudo mosquitto_pub -u as1 --psk-identity as1 --psk 123456789012345678901234567890ab -t 'as1/pos/sip_id/1023/req/position' -m '{"msgId":"pos_2","params":{"sip_id":"1023","mode":"dps"}}' -p 8884 -h 192.168.178.190

"as1" proper external_client id
"123456789012345678901234567890abEEEE" proper external client password
"{}" inside You can specify the message
"8884" messages can be only sent on port 8884

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.

Location request using IPUI
as1/pos/ipui/029e74a599/req/position {
											"msgId":"pos_2",
											"params":
											{
												"ipui":"029e74a599",
												"mode":"dps"
											}
										}

Positive response
dm2/029e74a599/as1/pos/res/position
											{
												"msgId":"pos_2",
												"payload":{"ble":{},
												"dm_id":"dm2",
												"dps":
											{"bases":
												[{"fpn":"215","rpn":"66","rssi":"60"},
											 	 {"fpn":"215","rpn":"67","rssi":"59"}],
											"bs_fpn":"215",
											"bs_mac":"7c2f80e0d6d7",
											"bs_name":"BSDM2",
											"bs_rpn":"66",
											"time":"1593602403"},
											"ipui":"029e74a599",
											"sip_id":"1023"}}

dm2/1023/as1/pos/res/position 
										{
											"msgId":"pos_2",
											"payload":{"ble":{},
											"dm_id":"dm2","dps":
											{"bases":
												[{"fpn":"215","rpn":"66","rssi":"60"},
												 {"fpn":"215","rpn":"67","rssi":"59"}],
											"bs_fpn":"215",
											"bs_mac":"7c2f80e0d6d7",
											"bs_name":"BSDM2",
											"bs_rpn":"66",
											"time":"1593602403"},
											"ipui":"029e74a599",
											"sip_id":"1023"}}

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.

Location request using IPUI
as1/pos/ipui/029e74a599/req/position {
											"msgId":"pos_2",
											"params":
											{
												"ipui":"029e74a599",
												"mode":"dps"
											}
										}
Positive response
dm1/029e74a599/as1/pos/res/position 
											{
												"msgId":"pos_2",
												"payload":{"ble":{},
												"dm_id":"dm1",
												"dps":
												{"bases":
													[{"fpn":"215","rpn":"2","rssi":"58"},
													 {"fpn":"215","rpn":"67","rssi":"60"},
													 {"fpn":"215","rpn":"66","rssi":"60"}],
												"bs_fpn":"215",
												"bs_mac":"589ec60d8c73",
												"bs_name":"BSDM1",
												"bs_rpn":"2",
												"time":"1593602685"},
												"ipui":"029e74a599",
												"sip_id":"1023"}}
dm1/1023/as1/pos/res/position 
											{
												"msgId":"pos_2",
												"payload":{"ble":{},
												"dm_id":"dm1",
												"dps":
												{"bases":
													[{"fpn":"215","rpn":"2","rssi":"58"},
													 {"fpn":"215","rpn":"67","rssi":"60"},
													 {"fpn":"215","rpn":"66","rssi":"60"}],
												"bs_fpn":"215",
												"bs_mac":"589ec60d8c73",
												"bs_name":"BSDM1",
												"bs_rpn":"2",
												"time":"1593602685"},
												"ipui":"029e74a599",
												"sip_id":"1023"}}

4. Bluetooth (BLE) location request

Scroll to top

Page tree

FAQ - AML: Location