cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
398
Views
1
Helpful
5
Replies
Highlighted

I don't understand, what the MSE is doing here....

OK,

finally I made it this morning to schedule Presence and Absence for just ONE device (my own) by applying entityFilter. So far so good. Presences was rather accurate, whereas Absence is crap... Scheduled for AbsenceDuration of 2 minutes, AbsenceNotifications just come in after the phone's wifi is off for > 30 minutes or so...

Now I wanted to give ContainmentEvent a try.. What a mess...

What is wrong with this? (private things anonymized)

1) Check for scheduled notifications:

curl -i -k -u <user:pass> -H "Accept: application/json" https:<ip_of_mse>/api/contextaware/v1/notifications -X GET

Result:

{

"List":[

   {

       "name":"all-event-trigger",

       "notificationType":"EVENT_DRIVEN",

       "dataFormat":"JSON",

       "lastModifiedTime":"2014-01-29T09:31:37.277+0000",

       "subscribedEvents":[

           {

               "type":"ContainmentEventTrigger",

               "eventEntity":"WIRELESS_CLIENTS",

               "boundary":"INSIDE",

               "zoneHierarchy":"xxx",

               "zoneTimeout":0

           }

       ],

       "NotificationReceiverInfo":{

           "transport":{

           "type":"TransportHttp",

           "hostAddress":"xxx",

           "port":5000,

           "macScramblingEnabled":false,

           "urlPath":"/",

           "https":false

       }

       }

   }

]

}

Hey, is this just one containment trigger or not?? IMHO, it is...

But what I get is still the same old Presence/Absence notification as scheduled (and deleted) 2 hours ago... Gees, that is so stupid...

{

"PresenceEvent": {

   "subscriptionName": "all-event-trigger",

   "entity": "WIRELESS_CLIENTS",

   "deviceId": "xx:xx:xx:xx:xx:xx",

   "locationMapHierarchy": "xx",

   "locationCoordinate": {

     "x": 122.52,

     "y": 168.58,

     "unit": "FEET"

   },

   "mseUdi": "xx",

   "geoCoordinate": {

     "lattitude": xx,

     "longitude": xx,

     "unit": "DEGREES"

   },

   "floorRefId": -6048156075595661243,

   "timestamp": "2014-01-29T10:38:34.809+01:00"

}

}

Not a trace of a single Containment Notification, as I would expect.

I would suggest to go back to the labs with all that stuff...

Regards

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Cisco Employee

Re: I don't understand, what the MSE is doing here....

Looks like there is some loading issue in the MSE.

Notification registration looks ok.

But the notifications were not dispatched from the queue in a regular pace.

They were stuck into the queue for a long time.

Will request our test team to reproduce this problem to check whether there is some bug.

View solution in original post

5 REPLIES 5
Highlighted

Re: I don't understand, what the MSE is doing here....

I deleted all notifications, made a GET to ensure, that there are not notifications again and scheduled a generic presence event w/o a filter applied. Went to a meeting. Came back after an hour. No change in behavior. Same as described above. Came back 2 hours later and finally the MSE did spit like a machine gun, following my advice given 2 hours earlier...

Is this by design?

Highlighted
Cisco Employee

Re: I don't understand, what the MSE is doing here....

Looks like there is some loading issue in the MSE.

Notification registration looks ok.

But the notifications were not dispatched from the queue in a regular pace.

They were stuck into the queue for a long time.

Will request our test team to reproduce this problem to check whether there is some bug.

View solution in original post

Highlighted

Re: I don't understand, what the MSE is doing here....

Right, this is also something I would suspect. The question is, why isn't the notification queue completely flushed if there is NO notification at all?

Highlighted
Cisco Employee

Re: I don't understand, what the MSE is doing here....

Current implementation does not flush out the notification queue when you remove all notifications (de-registration).

The reason is that the notifications in the queue were placed when the notifications got triggered and they are before

removing the notifications registrations.

Highlighted

Re: I don't understand, what the MSE is doing here....

Yepp, and if I think twice, this is exactly the behavior I'm experiencing with my local electricity provider. Whenever I switch the light off, it remains on for at least one additional hour. The company says, that it is my fault, because I haven't foreseen to switch the light off one hour earlier.

I hope you see, how strange your argumentation is: Either you offer to control the MSE and let me control the MSE, or you don't. "Eat or die" cannot be the parole.

Regards

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