Monday, April 30, 2012 2:37 AM
We are experiencing the failure in performing consult and transfer a call on Lync Client or through Lync Client API with the scenario below:
1->Lync Client A got an incoming (audio) call and answered it, then put it on hold;
2->Lync Client A made a new direct (audio) call to Lync Client B, and then got answered by B;
3->On Lync Client A, the options under "Current Conversations" were greyed out, i.e. the call could not be 'complete transfer';
If we ran our application with using Lync API, we would get a 'false' from the api call 'avModality.CanInvoke(ModalityAction.ConsultAndTransfer)', i.e. it was not allowed to perform 'complete transfer'.
We have some other Lync Clients to be able to perform the transfer, and only two machines never work on the transfer. All the Lync Clients are of the same latest version, and also the machines they are running have the same system (Windows 7 SP1). We also have tried to swap the users to log in. The tests have showed that it is not to do with the lync users. That two 'transfer failure' Lync Clients never work no matter what lync user log in, and the other 'good transfer' Lync Clients always work with no mather what user log in. Reinstalling Lync Client didn't help either.
Can anyone provide some helps or guidelines for us to detect or resolve the issue?
Monday, April 30, 2012 11:50 PMOwner
Any information in the client or server logs?
-- How To Ask a Question: http://support.microsoft.com/kb/555375 -- This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm
Monday, May 07, 2012 10:38 PMWe've found out the issue. That seems to do with the windows login user. We haven't yet dug out the real cause but it works if log in to the 'issue' machine with a windows user who can perform 'transfer' on the other machine.
- Marked As Answer by Kai Strandskov [Msft]Owner Tuesday, May 08, 2012 8:15 PM