tag:blogger.com,1999:blog-1636331107856379895.post2692115385335366454..comments2024-02-13T13:51:17.421+01:00Comments on Daniyar's Tech blog: Lync 485 Ambiguous errorUnknownnoreply@blogger.comBlogger2125tag:blogger.com,1999:blog-1636331107856379895.post-72796933981676105912015-03-04T20:40:06.620+01:002015-03-04T20:40:06.620+01:00yes, absolutely, Lync will treat xxx and xxx;ext=y...yes, absolutely, Lync will treat xxx and xxx;ext=yyy as duplicate...Daniyarhttps://www.blogger.com/profile/14100906602007622552noreply@blogger.comtag:blogger.com,1999:blog-1636331107856379895.post-77739046769569159252015-03-04T00:13:04.487+01:002015-03-04T00:13:04.487+01:00I found a similar problem with 485 and 4199 Ambigu...I found a similar problem with 485 and 4199 Ambiguous errors, where scripts weren't finding the duplicate until I realized the users private line was also set to the LineURI, but not including the ;ext=xxxx. So, similar behaviour of having a single number for extension dialing, but forgetting to set ALL objects with that main number with an ext.<br /><br />Another script that seems to spit out every possible item that has a phone number, including PrivateLine, is Get-AssignedLineURI.ps1:<br /><br />https://gallery.technet.microsoft.com/office/Lync-numbers-in-use-6c890b9aKorbynhttps://www.blogger.com/profile/06023515396762843537noreply@blogger.com