BenjaminRamsay | 2017-03-15 20:35:17 UTC | #1
When using the API to update user presence, the presence Notification service gets out of sync and stops sending new notifications in certain cases. Steps to replicate:
- Fire up Developer Tools Notification Tester and subscribe to your own presence notifications
- In the PureCloud client change your status back and forth between Available and Busy several times.
- You will see a presence Notification event received for each change. That's good.
- Leave yourself in Available status when you're done observing this.
- Now use Developer Tools API Explorer to call
/api/v2/users/{userId}/presences/{sourceId} using the presence ID for "Busy" status. - userId = Your user ID
- sourceId = PURECLOUD
- BODY =
{ "presenceDefinition": { "id": "31fe3bac-dea6-44b7-bed7-47f91660a1a0" } }
- Your status will change to Busy in PureCloud, and you'll receive a Busy presence notifcation. So far so good.
- Now use PureCloud client to change back to Available.... you will receive no notification.
- Use the API call to change to Busy status again. No notification, and your presence indicator does not update in PureCloud.
This only occurs when using the API to change presence status. Furthermore, it only occurs when switching back to the presence status you were on previously. If you cycle between three distinct presences statuses, you will not observe this behavior.
(*this is obviously a contrived example. But the issue comes up a lot in practice when using a custom app to manage presence via the API)
tim.smith | 2017-03-14 16:13:34 UTC | #2
Reproduced. I've logged SHIA-1492 for this issue.
system | 2017-08-28 19:32:54 UTC | #3
This post was migrated from the old Developer Forum.
ref: 1033