I was at a customer’s site the other day when we he received the following request.
User A (the Boss) forwards his phone to User B (the Assistant). As someone calls the Boss, obviously the Assistants phone rings and she picks it up, it turns out the caller is important and needs to talk to the Boss. The Assistant transfers the call to the Boss… and that’s it. Since the Bosses phone is forwarded, nobody will be able to reach him.
Interestingly, in the ancient PBX world there was a “feature” (I’d call it bug) where the Assistant could “break through” the forwarding setting and therefore transfer calls to the Boss.
After bouncing some ideas we came up with a pretty simple solution. As the title implies, it makes use of Private Line feature in Lync 2013.
After some testing we configured a Private Line on the Bosses account and again, set up call forwarding to the Assistant in his Lync client.
Now, if someone calls the Boss, the Assistants phone would ring. If the caller wants to talk to the Boss, the Assistant can now simply forward the call to the Bosses private line. Call forwarding settings are not applied to this line, so his client would ring and he would be able to take the call.
Sure enough, there is no “one” solution, other possibilities would be the use of the Delegate or even Team Call features. In this particular case, though, we decided to use the Private Line.
Update: Another solution for this particular problem would be to have the Boss configure the Assistant as his delegate, and the configure “Forward to Delegate” in her Lync Client. This enables User B to put calls through to User A, even though User A’s client is configured to forward calls.
You can use my wrapper script for SEFAUtil to configure this, too.
Thanks to @jpborth for pointing this out!
The Private Line feature requires Lync Server 2013, and is not exposed in the Lync Control Panel. The Set-CsUser cmdlet is used to configure a private line for a user:
Set-CsUser –Identity [email protected] –PrivateLine “tel:+39123123”
Note: TechNet says, private line is new in Lync 2013, next time I’m in a pure 2010 environment, I’ll check if this feature can be configured on Lync 2010, too.
This post has been migrated from our earlier blog based on BlogEngine.NET.