Hello,
we have some trouble with the presence module of JS SDK 4.15.0.0.
We used the samples from
https://www.devconnectprogram.com/site/global/products_resources/avaya_client_sdk/programming_docs/current/javascript/communication/guide/publishing_presence.gsp
After login, we publish automatic presence like following:
selfPresence.setPhoneState(AvayaClientServices.Services.Presence.PhonePresenceState.PRESENCE_STATE_AVAILABLE);
selfPresence.setVideoState(AvayaClientServices.Services.Presence.VideoPresenceState.PRESENCE_STATE_AVAILABLE);
selfPresence.setEnterpriseIMState(AvayaClientServices.Services.Presence.IMPresenceState.PRESENCE_STATE_AVAILABLE);
presenceService.publishAutomaticPresence();
Then, the user publishes manual presence state:
presenceService.publishManualState(AvayaClientServices.Services.Presence.PresenceManualState.PRESENCE_STATE_BUSY);
The manual state will be published and distributed to other clients.
But how should we clear the manual state correctly? We are resetting the manual state with unspecified:
presenceService.publishManualState(AvayaClientServices.Services.Presence.ManualPresenceState.PRESENCE_STATE_UNSPECIFIED);
With this, there is a strange behavior:
We receive 2 presenceupdate events, one with overall-availability "offline" and a following one with "available".
But many times we are receiving the events in reversed order. At first the "available" and then the "offline" event. So, the last user presence received from the JS SDK is "offline".
IX Workplace for Windows also receives the offline presence.
Please see the attached log file which contains the chrome console log output from JS SDK.
Are we anything missing here? Is the publishManualState with unspecified the incorrect way to reset a manual state?
Any other ideas where to investigate?
Thanks
Daniel