We may have found a new bug in Skype for Business Server. It’s located in one of the fields in your Skype Meeting invite.
First, some background:
When we set up our Meeting Invite in Lync Server 2013, it contained three lines under the “Join by phone” section:
- PlanetMagpie Dialin [link]
- Our Local Dial-in Access Number
- “Find a local number” link
The thing is, the “PlanetMagpie Dialin” link didn’t always work. We logged it as an issue, but didn’t fully investigate before moving to Skype for Business.
The other day, we decided to update the Skype Meeting invite. In order to do this you must make changes in the Skype for Business Control Panel:
- In Conferencing, under “Meeting Configuration”
- In Conferencing, under “Dial-In Access Number”
Meeting Configuration lets you add personalization through a logo & custom text. Dial-In Access Numbers lets you set the phone number with which users can call into the meeting. You also set the number’s display name.
“When you deploy dial-in conferencing, you need to set up phone numbers that users can dial from the public switched telephone network (PSTN) to join the audio portion of conferences. These dial-in access numbers appear in meeting invitations and on the Dial-in Conferencing Settings webpage.”
Manage dial-in conferencing access numbers in Skype for Business Server 2015 – TechNet
That’s where we noticed something different. We could not change the Display Name.
The ‘Display Name’ field itself had stopped cooperating.
(Likely) Cause: Bug in ‘Display Name’ from Lync Server Days
In Lync Server 2013, under Dial-In Access Numbers, the Display Name field was recommended but not mandatory. This is where we put the “PlanetMagpie Dialin” name referenced above.
When we upgraded, “PlanetMagpie Dialin” remained in the Display Name field. Skype for Business did its job, and preserved our dial plan information during In-Place Upgrade.
We edited the Display Name, as well as the logo & footer text under Meeting Configuration. But the changes didn’t populate to the Outlook meeting invites. Even trying the recommended cmdlet – Set-CsDialInConferencingAccessNumber – didn’t work.
Likely reason? A bug involving the ‘Display Name’ field. When Microsoft built Skype for Business, the upgrade carried dial plan information through. It appears that our upgrade also carried the bug over!
So we had an un-updated meeting invite, despite the server showing all the changes we wanted. How do we fix it?
Solution: Delete & Recreate the Dial-In Access Number
As with many troubleshooting episodes, the old “rip & replace” worked. Here’s what we did.
- Confirmed the Meeting Configuration has the values you want.
- Switch to the Dial-In Access Numbers window.
- Open the dial plan you have in place now. Take a screenshot of it. Click Cancel.
- Click Edit. Click Delete to delete the dial plan.
- Now the server needs to refresh. The fastest way to do this is to open Management Shell and enter the following cmdlet:
- Wait a moment for the changes to replicate. You can check the status with this cmdlet:
- When it displays “True” the changes have replicated. Return to the Control Panel.
- Still in Dial-In Access Numbers, click New.
- Using the screenshot you took, re-enter the same dial plan values.
- Click Commit.
- Once again, open Management Shell and enter the following cmdlet:
- As before, you can check the status with:
- Wait for it to display “True.” Then you’ll know the new dial plan is published.
- If you want to double-check, open Users in Skype for Business Control Panel. Open one or more User accounts and confirm that your dial plan name appears for them.
- It may take a little longer for the meeting invite to update on all client computers. This took a while for us – long enough to grab lunch, in fact.
Once the updates populated, I checked our meeting invites.
See? “PlanetMagpie Dialin” vanished, but the call-in number remained. All other changes appeared too. Meeting invites up-to-date!
Uncommon Bug, But Deserving of a Skype4B Insider Post!
We aren’t sure this is an official bug. I didn’t locate specific mentions of it in TechNet. We’ll report it, of course, just in case. Even the rarest bug deserves reporting.
In any event, since it IS a Skype for Business issue, we must document it on the blog! Hope it helps you, if you’ve reached this post and have a similar issue messing up your meeting invites.
Have you encountered issues with Meeting Configuration or Dial-In Access Numbers? If so, please comment or email what happened. I’d love to hear about it.