Cisco Cisco 3365 Mobility Services Engine Release Notes
33
Release Notes for Cisco Mobility Services Engine, Release 8.0.110.0
OL-32458-01
Operational Notes for Mobility Services Engine
Non-Cisco Compatible Extensions Tags Not Supported
The Mobility Services Engine does not support non-Cisco CX Wi-Fi tags. Additionally, these
non-compliant tags are not used in location calculations or shown on the Prime Infrastructure maps.
non-compliant tags are not used in location calculations or shown on the Prime Infrastructure maps.
Cisco Compatible Extensions Version 1 Tags Required at a Minimum
Only Cisco CX Version 1 (or later) tags are used in location calculations and mapped in the Prime
Infrastructure.
Infrastructure.
Monitoring Information Varies for Clients and Tags
In the Monitor > Clients page (when Location Debug is enabled), you can view information on the last
heard access point and its corresponding Received Signal Strength Indicator (RSSI) reading.
heard access point and its corresponding Received Signal Strength Indicator (RSSI) reading.
Calibration Models and Data
Calibration models always applies to Wireless clients, Interferers, Rogue APs, and Rogue Clients.
See Chapter 7, “Context-Aware Planning and Verification” in the Cisco Connected Mobile Experiences
Configuration Guide, Release 8.0 for more details on client calibration.
Configuration Guide, Release 8.0 for more details on client calibration.
Advanced Location Parameters
Settings for advanced location parameters related to RSSI, chokepoint usage, location smoothing, and
assignment of outside walls on floors, are not applicable to tags.
assignment of outside walls on floors, are not applicable to tags.
See the “Editing Advanced Location Parameters” section in Chapter 7 of the Cisco Connected Mobile
Experiences Configuration Guide, Release 8.0.
Experiences Configuration Guide, Release 8.0.
See Services > Mobility Services > Device Name > Context Aware Service > Advanced > Location
Parameters.
Parameters.
Location History Time stamps Match Browser Location
The Prime Infrastructure time stamp is based on the browser location and not on the Mobility Services
Engine settings. Changing the time zone on the Prime Infrastructure or on the Mobility Services Engine
does not change the time stamp for the location history.
Engine settings. Changing the time zone on the Prime Infrastructure or on the Mobility Services Engine
does not change the time stamp for the location history.
Tablets and Smartphone with Limited Probe Requests Might Affect Location
Many tablets, smartphones, and other Wi-Fi devices with power save mode do not continuously send out
probe requests after an initial association to the CUWN. Therefore, calculating the location accuracy of
such devices using RSSI readings is not always optimal.
probe requests after an initial association to the CUWN. Therefore, calculating the location accuracy of
such devices using RSSI readings is not always optimal.
Repeat Use of FloorID returns +1 After Every Hour
In the relevant CAS API, the use of the parameter FLOORID is not guaranteed to return the same value
on consecutive calls. It may get changed by such activities as resynchronizing the MSE. Instead, the
parameter FLOORAESUID should be used. The API call getStationHistoryListByArgs now can use
both parameters in MSE Release 8.0.
on consecutive calls. It may get changed by such activities as resynchronizing the MSE. Instead, the
parameter FLOORAESUID should be used. The API call getStationHistoryListByArgs now can use
both parameters in MSE Release 8.0.