tomorgan / lync-uisuppression-videoautoanswer Goto Github PK

I've recompiled the project to work with Lync 2013 SDK however cannot overcome this issue

A first chance exception of type 'Microsoft.Lync.Model.LyncClientException' occurred in Microsoft.Lync.Model.dll
Microsoft.Lync.Model.LyncClientException: Generic COM Exception. Code is 0x800706F7.
at Microsoft.Lync.Model.Conversation.AudioVideo.VideoWindow.set_Owner()

when calling LyncObject.Owner = value; in class class LyncVideoWindow

There's an issue when using this within a conference. It works fine whilst you're in a conference, but when the conference ends, a COM exception is thrown on the kiosk. You can power through it by clicking Continue and everything will keep working, but we need to look at it. It'll be something to do with the way the conversation terminates (or doesn't) at the end of the conference.

If an outgoing call is declined by the remote participant, there's no feedback and the screen doesn't revert back to the Waiting screen.

Hello, when I open this project in visual studio 2015, I get the error: The type or namespace name 'Lync' does not exist in the namespace 'Microsoft' (are you missing an assembly reference?). I cannot find the 'Microsoft.Lync.Model.dll' and I do not find the file to download on the Internet. So where could I get the file or how can I fix the error? Thanks!

Possibly outgoing video not always displayed in corner of screen. Seems to be resolved if you retry. We think this may be a hardware device timing issue, or possibly something environmental.

Tom, not sure if you still monitor this project or not, but I'm having a issue when I try to use this with a response group. The call works well if it is being answered with a video call however call if the call is missed and forwarded to a phone number the call fails and a InvalidOperationException occurs in Lync.cs, any ideas to get around this?

Lync's GetContactInformation() call returns syncronously, but isn't always ready immediatly, leading to us either getting data in a state where it's not yet ready, or getting a NotReadyException.

I'm mitigating this with some nast while loops and thread sleeps, but I don't like it. Raising it as an issue to sort out later - there must be a better way of doing this.