To remove a stuck dial-in conferencing number follow the steps below. These worked for me, I hope they do you you.
- Open the Lync Control Panel and find the dial-in region for the deleted access number.
- In Lync PowerShell run get-CsDialInConferencingAccessNumber -region <your region>. You will see the following warning “Cannot find the contact object associated with the entry for line URI “tel:+xxxxxx”.
- From the Lync Control Panel under under “Voice Routing” -> “Dial Plans”, assign the region found in step 1 to a Dial Plan.
- From the Lync Control Panel under “Conferencing” -> “Dial-in Access Number”, create a new Dial-in Access Number to match the display number LineURI Primary Language. The SIP URI can be any unique string.
- In Lync PowerShell run set-CsDialinConferencingAccessNumber -Identity <identity e.g. “sip:xxxxx”> -scopetoglobal, Use the identity you created in step 4.
- Re-run the PowerShell command from Step 2. This time you should not get a warning, and instead you will see the info for the access number created in step 5.
- Delete the Dial-in Access Number you created in step 4, and re-run the PowerShell command in Step 6 to verify it is deleted.
- Wait for a few minutes, then you should no longer see the dial-in access number in the access number listing.
[…] 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/ […]
This, my friend, is gold. Between a domain migration, an upgrade from Lync to Skype for Business, this was the only artifact to appear. From whence it came we do not know.
“Sometimes to get rid of something that does not exist, you have to create it.” – Old System Admin Proverb
Thanks, glad it helped!