cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
528
Views
0
Helpful
4
Replies
Highlighted

Different response content?

Hi,

after having said "Good Bye" to the notifications I'm now polling my MSE, providing the MAC of the clients.

curl -k -u username:password https://ip_of_mse/api/contextaware/v1/location/clients/xx:xx:xx:xx:xx -H "Accept: application/json"

Normally I'm getting reponses like this one (anonymized):

{

    "WirelessClientLocation": {

        "GeoCoordinate": {

            "lattitude": xx.xxxxxxxx,

            "longitude": xx.xxxxxxxx,

            "unit": "DEGREES"

        },

        "MapCoordinate": {

            "unit": "FEET",

            "x": 124.14,

            "y": 170.27

        },

        "MapInfo": {

            "Dimension": {

                "height": 9.84,

                "length": 229.66,

                "offsetX": 259.19,

                "offsetY": 0.0,

                "unit": "FEET",

                "width": 147.64

            },

            "Image": {

                "imageName": "domain_0_1386169087303.jpg"

            },

            "floorRefId": -6048156075595661243,

            "mapHierarchyString": "xx>xx>xx"

        },

        "Statistics": {

            "currentServerTime": "2014-02-17T12:34:07.630+0000",

            "firstLocatedTime": "2014-02-17T12:34:03.180+0000",

            "lastLocatedTime": "2014-02-17T12:34:03.180+0000"

        },

        "band": "UNKNOWN",

        "confidenceFactor": 24.0,

        "currentlyTracked": true,

        "dot11Status": "PROBING",

        "isGuestUser": false,

        "macAddress": "xx:xx:xx:xx:xx:xx"

    }

}

But there is (at least) one device, for which - although it is in the same room and is associated to the same SSID (not necessarily the same physical access point) or probing it - the MSE returns much less information. Most missed: LocationHierarchy and GeoCoordinates

{

    "WirelessClientLocation": {

        "MapCoordinate": {

            "unit": "FEET",

            "x": 40.73,

            "y": 113.72

        },

        "MapInfo": {

            "floorRefId": 0

        },

        "Statistics": {

            "currentServerTime": "2014-02-17T12:39:49.141+0000",

            "firstLocatedTime": "2014-02-17T12:38:30.765+0000",

            "lastLocatedTime": "2014-02-17T12:38:30.766+0000"

        },

        "apMacAddress": "xx:xx:xx:xx:xx:xx",

        "band": "UNKNOWN",

        "confidenceFactor": 104.0,

        "currentlyTracked": true,

        "dot11Status": "ASSOCIATED",

        "ipAddress": [

            "10.227.109.182"

        ],

        "isGuestUser": false,

        "macAddress": "xx:xx:xx:xx:xx:xx",

        "ssId": "xxxxxxxx"

    }

}

How is that possible? All access points are connected to one and the same WLC.

Regards

4 REPLIES 4
Highlighted
Cisco Employee

Re: Different response content?

I think what is happening is that the X,Y coordinates of the device that is detected is in a location that does not have a ZONE associated with it.

Does this every occur when the devices are in the same spot ?

Does the room that these device happen to be in have a ZONE that goes down the middle of the room ?

This is my initial idea.

Regards,

Darryl Sladden

Highlighted

Re: Different response content?

No I think that is not the case. A couple of other devices got the full response, in the same room, on the same table.

One hour later I got that full response for the device in question too.

A pull of incomplete information is extremely useless...

Regards

Highlighted
Cisco Employee

Re: Different response content?

Neil,

We are working on this internally and it appears this may be a bug.  It seems to be due to a timing issue with fields in DB not being correctly joined.

Regards,

Darryl Sladden

Highlighted

Re: Different response content?

Thanks for the update.

Let me know, how it goes.

Regards

CreatePlease to create content
Content for Community-Ad
Cisco Community May 2020 Spotlight Award Winners
This widget could not be displayed.