UCMA 3.0 联络中心示例应用程序中的应用程序共享限制
首先我要说的是，我知道 ContactCenter 示例只是一个示例，它公开的应用程序共享扩展类并未得到官方支持。
尽管如此，我发现 ContactCenter 示例的应用程序共享功能存在一些限制。
即：
1）呼叫者与座席共享屏幕后，座席无法控制呼叫者的屏幕。没有错误，但控制请求只是发生而没有结果，即使客户已将会话设置为接受所有控制请求
2) 在呼叫者共享其屏幕之前，他们可以是会议中唯一的参与者看到的是联络中心服务员。一旦代理接受共享会话，代理的身份就会显示在呼叫者的参与者列表中。
3）如果呼叫者共享他们的屏幕，关闭共享会话，然后启动一个新的会话，这个新的共享会话将作为单独的对话进入代理，在它自己的窗口中带有自己的 toast 消息，等等。
我有很多理论至于为什么存在这些限制和可能的解决方法，但在过于积极地追求它们之前，想看看其他人是否有解决方法，或者 UCMA 团队是否确信这些只是 UCMA 的固有限制。
任何信息将不胜感激。
Let me preface this by saying that I know the ContactCenter sample is just a sample and that the application sharing extension classes it exposes are not officially supported.
With that said, I've found several limitations to the ContactCenter sample's application sharing functionality.
Namely:
1) After the caller shares their screen with the agent, the agent cannot take control of the caller's screen. There is no error, but the request for control just kind of happens with no result, even if the customer has set the session to accept all requests for control
2) Prior to the caller sharing their screen, the only participant in the conference they can see is the contact center attendant. As soon as the agent accepts the sharing session, the agent's identity is revealed in the caller's participant list.
3) If the caller shares their screen, closes the sharing session, then starts a new one, this new sharing session comes into the agent as a seperate conversation, in its own window with its own toast message, etc.
I have plenty of theories as to why these limitations exist and possible workarounds, but before pursuing them too aggressively, wanted to see if anybody else had workarounds OR just as usefully, if the UCMA team is confident that these are just inherent limitations to UCMA.
Any info would be appreciated.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我和我的同事找到了一些答案，他将其发布在：http://blog.greenl.ee/2012/02/06/handling-application-sharing-calls-ucma/
简而言之，如果您将应用程序共享呼叫分离到另一个对话中并返回到支持它，您可以获得一些良好的基本功能。
My colleague and I found some answers, which he posted about at: http://blog.greenl.ee/2012/02/06/handling-application-sharing-calls-ucma/
The short version is that if you separate the application sharing call into another conversation and back to back it, you can get some good, basic functionality going.