Real-Time UC

A Universal Communications Blog by Office Servers and Services MVP Michael LaMontagne

Fixes Lync Skype for Business

Phantom Conference Bridge

While verifying a new conference bridge for a client, I came across a phantom conference bridge entry listed on the Lync Server Dial-in page but not on the Outlook meeting invites.

Using Get-CsDialInConferencingAccessnumber cmdlet which lists information about all dial-in conferencing numbers configured in an organization and the region parameter to search for the specific entry. A warning was returned saying the contact object for the entry could not be found. Looks like the bridge was leftover from the OCS days. Record the “Line URI” listed in the warning message.

get-csdialinconferencingaccessnumber -region "<RegionName>" -Verbose |FL

First step was to recreate the region that was associated to the phantom bridge. This was done by creating a new User Dial Plan with the “Dial-in conferencing region” exactly matching what was listed on the Dial-in page for the phantom bridge.

Next create a new Dial-in Access Number where the “Line URI” matched what was returned in the warning from the get-csdialinconferencingaccessnumber, and add the “Associated Region” that was created in the last step.

Running the same get-csdialinconferencingaccessnumber as before will now display the contact object.

Now delete the new Dial-In Access Number and the User Dial Plan that was created for the phantom bridge and invoke CMS replication (invoke-csmanagementstorereplication). Running the get-csdialinconferencingaccessnumber command will now show no object and the phantom bridge will be removed from the Dial-in page.

As a side note you may have noticed in the screenshots I’m using csdialinconferencingaccessnumber vs. get-csdialinconferencingaccessnumber, not sure if the cmdlet was just too long to type or it was late. After taking to Twitter about this “Feature”, Ravikanth Chaganti recommended I trace what’s actually happening.

trace-command -ex { csdialinconferencingaccessnumber } CommandDiscovery -PSHost -Verbose

One of the last steps when PowerShell is unable to find a command is to prepend the command with “get-”.

Update: Looks like Andrew Morpeth blogged about a similar stuck conferencing number, see his post: https://ucgeek.co/2015/03/remove-stuck-conferencing-number-lync/

Hugo-Octopress Theme | Powered by Hugo