3 of 3 users support this suggestion
MS365-connector: Once a presence is set, allow it to unset to "aviable"
Currently there is an edge case within the M365 presence connector:
It is not possible to reset an external presence (e.g. DND from Teams) to "aviable".
As example:
A User is avaible in Teams and the pbx.
The user sets its teams presence to DND.
The DND presence is synced to the pbx and an attribute with the value microsoft365://dnd is created within the user object.
Now the user clears the presence in Teams and resets is to "aviable".
Now the user clears the presence in Teams and resets is to "aviable".
The "aviable" presence is NOT synced in the pbx. Within the pbx the "microsoft365://dnd" presence remains set.
This is due to a special behaviour of the "aviable" presence in the PBX: In the pbx no presence attribute equals "aviable". The "aviable" presence is created by clearing all attributes previously set within the user object.
Since each app (calendar, M365 Connector) can only read and write within its own namespace (microsoft365://, calendar://), the Teams Connector can not reset a users presence to aviable.
Thus we suggest an enhacement to the internal pbx presence with a dedicated aviable-presence within the PBX firmware.
This would allow any app to set an "aviable"-presence (microsoft365://aviable, calendar://aviable). Since the most recently changed presence is displayed within the phone and myApps, this would also allow multiple apps to set/unset the users presence (e.g. calendar + M365 presence).
Best Regards
Danny
This would allow any app to set an "aviable"-presence (microsoft365://aviable, calendar://aviable). Since the most recently changed presence is displayed within the phone and myApps, this would also allow multiple apps to set/unset the users presence (e.g. calendar + M365 presence).
Best Regards
Danny