问题描述
当我设置状态存在时，聚合状态改变为我想要的状态，但UserPresenceState仍然是前一个
When I set state presence, the Aggregated state is change to what I want, but the UserPresenceState is still the previous
我用这个用户登录我的Lync客户端，我还在同一个用户的应用程序中创建了一个UserEndpoint，并设置了LocalOwnerPresence的回调函数。 PresenceNotificationReceived
现在，我按以下方式进行测试：
1. ;
我将Lync Client中的可用状态更改为DND，
2.      
在我的应用程序中，我获得了本地状态更改通知，并且在
的数据结构中 LocalPresentityNotificationEventArgs，
AggregatedPresenceState的属性显示DND，UserPresenceState的属性也显示DND。
2. In my application, I got the local presence change notification, and in the data structure ofLocalPresentityNotificationEventArgs,the property of AggregatedPresenceState show DND, and the property of UserPresenceState show DND too.
3.  
现在，我使用LocalOwnerPresence.BeginPublishPresence（new PresenceCategory [] {PresenceState.UserAvailable}，callBack，null）更新状态
3. Now, I use LocalOwnerPresence.BeginPublishPresence(new PresenceCategory[]{PresenceState.UserAvailable}, callBack, null) to update the presence
4.    
现在，我收到了另一个本地状态更改通知，
以及 LocalPresentityNotificationEventArgs，
the AggregatedPresenceState的属性显示空闲，但UserPresenceState的属性仍显示DND。并且Lync客户端也显示空闲。
4. Now, I got another local presence change notification, and in the data structure of LocalPresentityNotificationEventArgs,the property of AggregatedPresenceState show Idle, but the property of UserPresenceState still show DND. And the Lync Client show Idle as well.
实际上，即使我尝试UCMA SDK样本，结果相同。
Actactually, even I try UCMA SDK sample, same result.
leslie
推荐答案
我们修复的问题与Lync发布DND或Busy时有关;当UCMA发布另一个州时，UCMA没有正确清除Lync发布的DND / Busy出版物。
The problem we fixed was related to when Lync published DND or Busy; when UCMA published another state, UCMA didn't properly clear the DND/Busy publication made by Lync.
听起来你可能还有另一个问题。 除了用户状态（即PresenceState.EndpointOnline）之外，还要确保您还发布端点状态。 聚合状态是两种不同类型状态的组合：用户状态
（可用，忙，DND等）和机器/端点状态（在线/可用，空闲/非活动，离开，离线）。 您的UCMA端点需要在UCMA端点的状态发布可能处于用户的聚合状态之前发布两种类型的状态。
请查看
更多信息。
It sounds like you may have another issue too. Make sure you are also publishing an Endpoint state in addition to the User state (i.e. PresenceState.EndpointOnline). Aggregate state is the combination of two different types of state: User state (Available, Busy, DND, etc) and Machine/Endpoint state (Online/Available, Idle/Inactive, Away, Offline). Your UCMA endpoint needs to publish both types of state before the UCMA endpoint's state publications are potentially in the user's aggregate state. Look at http://msdn.microsoft.com/en-us/library/microsoft.rtc.collaboration.presence.presencestate_di_2_ucma3coremref.aspx for more information.
-Matt
这篇关于状态存在集不起作用的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！