Wireless Discovery

Overview

The Enhanced Location Tracking - Location Awareness feature described in this section requires CUCM 12.5 SU2 or later and applies to supported wireless Cisco IP Phones and the Jabber Client. For wireless discovery information with HELD, please refer to Webex HELD Discovery.

Once infrastructure devices are added to CUCM, the 9Line agent will import BSSID information from CUCM via AXL. After 9Line finishes importing infrastructure devices, you will assign Locations to each entry. This can be accomplished individually using the portal or in bulk using the bulk import feature of the 9Line portal. Refer to the Bulk Import Operations document for further guidance on managing Infrastructure Devices and Locations.

Any manufacturer’s wireless access point can be used with this feature.

Non-Cisco devices, such as Aruba, will require importing the BSSID of each frequency and band to CUCM via the Bulk Administration Tool.

If the access point is Cisco or Meraki, only the Base BSSID must be imported into CUCM via the BAT tool or the Cisco Wireless LAN Controller synchronization feature.

Example Bulk Administration Tool CSV of an Aruba Access Point

To create the import file, you will need to obtain the BSSIDs of each radio. Fetching the BSSID of each radio and SSID can easily be achieved using APIs or CLI, such as the Aruba output available in “show ap bss-table”.

ACCESS POINT

IPV4 ADDRESS

IPV6 ADDRESS

BSSID

DESCRIPTION

Conf Room 1

00:FF:01:CD:CD:EF

Conf Room 1 - 2.4GHz

Conf Room 1

00:FF:01:CD:CD:00

Conf Room 1 - 5GHz

Additional Considerations

Once added, you cannot delete access points from the CUCM database; only deactivate it. For guidance on manually removing entries from the CUCM DB via CLI, raise a support ticket with the 9Line team.

Jabber clients have specific requirements:

  • You must configure the parameter <EnableE911OnPremLocationPolicy>true</EnableE911OnPremLocationPolicy> in the jabber-config.xml or the same setting on the Jabber Config UC Service for later versions of CUCM.
  • Please consult the Cisco document Wireless Location Monitoring Service for detailed guidance.
  • Jabber for Mac requires version 14.1.3, or later, due to bug CSCwc68937.
  • Jabber for Mac users must allow location by clicking "OK" to the message "Cisco Jabber would like to use your current location" when presented.

Recommended Reading