![]() ![]() The second however does NOT, instead, calling CloseExtensibilityWindow closes the extensibility window of the first conversation!!! What i found was: The first conversation raises an error when calling CloseExtensibilityWindow before BeginOpenExtensibilityWindow. ![]() Calling CloseExtensibilityWindow before BeginOpenExtensibilityWindow Delayed call to BeginOpenExtensibilityWindow: Starting a background thread, wait for 5 sec after connected and then call it. No caching of the retrieved ConversationWindow: Everytime i need it, i call Automation.GetConversationWindow(conversation) To find out what the problem could be i tried the following: EndOpenExtensibilityWindow does NOT raises any error, it just passes. If one of them is outbound, there's no problem, but when both are inbound, the call to BeginOpenExtensibilityWindow passes without doing anything. ![]() Then the function BeginOpenExtensibilityWindow does nothing at all) (So caller A calls me, i accept and while on the call, caller B calls me. However, for as i can tell now, there's one specific scenario when this does NOT work: When a new incoming AV call presents, while having an active (onHold or not doesn't matter) incoming call. On application startup i register the application etc and on an accepted call, the program calls BeginOpenExtensibilityWindow on the ConversationWindow. I'm creating an application which displays some data of the caller, using the ExtensibilityWindow. It is a minor thing, but in my mind it should just work. I'm having some troubles using the Lync2013 Client SDK. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |