In the Transfer Directly to and Consult Then Transfer option it should have the option to pick the user's voicemailbox as well as their numbers.
Lync phone edition has an option to Consult then transfer to. The Attendant has a button for this as well, as well as the ability to hit CTRL+L to achieve the same thing. Microsoft decided to leave this button out of the Lync PC client. It was in the OCS client but not in Lync. I know callers can merge calls using "Current conversation", but a Consult then transfer to button would be so much easier.
Now it takes a hover and 2 clicks before you can key the party you want to transfer the call to.
If the user mistakenly clicks instead of hovering on the "handset/mike" icon, they end up accidentally muting themself - presumably at a time that they're still talking to the caller whilst trying to make this complicated transfer process appear seamless.... more »
Lync2010/(UserA) --calls--> Lync2010Attendant/ --blind, safe-transfered to--> Lync 2010/(UserC: Lync2010)
-UserC Ignore Call Attendant Will See: Transfer not completed: UserA-Username. UseerC-Username is unavailable.
-UserC Reject Call Attendant Will See: Transfer not completed: UserA-Username. Call was not transferred because UserC-Username... more »
A feature is required that enables established calls to be "moved" from one device to another while in mid-call. This would enable users to take a call on their mobile device (VoIP or Cellular), walk into their office and continue the call on their PC Client.
Of course the reverse should be possible as well. with the call moving to the moble device over VoIP or Cellular.... more »
Right now, file transfers are either enabled or disabled. But some org security groups have heartburn over files leaving the corp network, or going to federated contacts due to data leakage. A policy option to limit file transfers to just internal endpoints, or just org users, would be nice
Would like to see a Lync Report for File Transfers which includes information on the file that was transfer, including name, date, size. Currently all I can see in L2013 reports is who sent a file to whom, with no additional info.
If you block file Transfer for users, the user will still receive an Icon file or a Picture thumbnail before it gets the error.
Lync should be able to block this before, because:
- it measleads the user thinking that is not restricted to send/receive files;
- in some cases a thumbnail Picture can be enough to see the Content.
Right now, if you drag and drop an Excel file into a conversation window, the recipient just sees an Excel icon. No file. File transfer should support all file types that are not blocked.
This doesn't make sense. If it's one of... more »