SfB user can’t add Delegates or Team Call members

In the process of deploying an SfB installation or maybe in the early days of go-live it’s not uncommon for users to report a problem where they’re unable to add people to their Delegates or Team-Call Group list. It’s less common to see this in established installations, but there are genuine reasons why this might happen.

When this problem occurs you’ll typically be able to see the user when you search, but the OK button won’t light up:

ChooseADelegate-NoOK

Interestingly, my Office 2016-based client’s giving me some extra text – but only intermittently:

If OK isn't enabled, you've picked one or more contacts who can't participate in this activity.

ChooseADelegate-NoOK text

The usual fixes

If you don’t even see the other user’s name appear below the search box, it might just be the address book hasn’t updated. Try entering their SIP address (as “blah@contoso.com”) and they should materialise.

Once you have them visible but not “OK-able”, confirm that the other user’s enabled for Enterprise Voice, as Team Calling and Delegation are EV features.

Next – and more commonly-seen in a brand new deployment – is that the other user has never signed into their new account and it’s not been ‘initialised’. Have them sign in and then repeat this test.

If having the above confirmed you still can’t get OK to light up, try restarting your client and repeat – there might just be a replication lag delaying your success. If all else fails, read on…

Enter “Privacy Mode”

Privacy Mode exists for those deployments where you might have a desire – or a government mandate – for an “opt in” approach to sharing presence information. In this screen-capture it’s enabled:

Get-CsPrivacyConfiguration

Here’s how the client reports that privacy mode is active:

SfBClientStatus-Privacy

If PrivacyMode is disabled, the text around the radio buttons changes:

SfBClientStatus-PrivacyDisabled

With “EnablePrivacyMode” $true, you won’t be able to see the presence of any other users – or add them as a Team-call Group member or Delegate – until they’ve changed the radio button in the above image, or added *you* as a Contact. In my Lab this change didn’t manifest for my client instantly, and I was forced to restart the client before I could then see the other user’s presence and add them.

When all Else Fails

They haven’t blocked you have they? It wouldn’t be the first time…

ChangePrivacy-Blocked

Reference

Set-CsPrivacyConfiguration

Acknowledgement

Thanks to my colleague Mike for suggesting the Privacy Mode fix.

Revision History

3rd Feb 2018: this is the initial post

 

– G.

3 Comments

  1. “confirm that the other user’s enabled for Enterprise Voice, as Team Calling and Delegation are EV features.”

    Some vague wording here: the devil lies in the fact, whether both ME and my TEAMMATE must be EV-enabled to form a team-call-relationship (initiated by ME and answered by HIM)

    • Hey Soder,

      You’re 100% correct. I didn’t think it necessitated making that distinction above, because if *you’re* not EV-enabled, you won’t even be presented with the Call Forwarding option in order to find yourself in the predicament depicted!

      – G.

Leave a Reply

Your email address will not be published. Required fields are marked *

... and please just confirm for me that you're not a bot first: Time limit is exhausted. Please reload the CAPTCHA.