Manual Part 2

Wireless Array
184 Configuring the Wireless Array
2. Wi-Fi Tag UDP Port: If Wi-Fi tagging is enabled, enter the UDP port that
the Wi-Fi tagging server will use to query the Array for data. When
queried, the Array will send back information on tags it has observed. For
each, the Array sends information such as the MAC address of the tag
transmitting device, and the RSSI and noise floor observed.
3. Wi-Fi Tag Channel BG: If you enabled Wi-Fi tagging, enter the 802.11
channel on which the Array will listen for tags. The tag devices must be
set up to transmit on this channel. Only one channel may be configured,
and it must be an 802.11b/g channel in the range of Channel 1 to 11.
4. Ekahau Server: If you enabled Wi-Fi tagging and you are using an
Ekahau server, enter its IP address or hostname. Ekahau Wi-Fi Tag
packets received by the Array will be encapsulated as expected by
Ekahau, and forwarded to the server.
Location
The Array offers an integrated capability for capturing and uploading visitor
analytics data, eliminating the need to install a standalone sensor network. This
data can be used to characterize information such as guest or customer traffic and
location, visit duration, and frequency. Use this Location window to configure the
Array to send collected data to an analytics server, such as Euclid.
When Location Support is enabled, the Array collects information about stations,
including the station ID and manufacturer, time and length of the visit and related
time interval statistics, and signal strength and its related statistics. Data collected
from stations comprises only basic device information that is broadcast by Wi-Fi
enabled devices. Devices that are only detected are included, as well as those that
actually connect to the Array. The Array sending the data also sends its own ID so
that the server knows where the visitors were detected. Data messages are
uploaded via HTTPS, and they are encrypted if a Location Customer Key has
been entered. Data is sent as JSON (JavaScript Object Notation) objects, as
described in “Location Service Data Formats” on page 504.