I'm trying to set up an auto attendant in Teams through Skype for Business, and I've run into an error. I completed the integration without issues. I created a resource object with a phone number and UPN, synced it online, and assigned the appropriate license. However, when I try to call the number, I see an error in the Skype for Business logs: Event ID 32126, stating that the contact object is not homed properly. It seems like this could be due to misconfiguration with the contact object's routing. I haven't linked the MACP to Office 365 yet since the script I had is outdated and needs a rewrite for MS Graph. Any advice would be greatly appreciated!
3 Answers
It's important to note that issues like this can sometimes happen when there are delays in Active Directory replication. Just to be safe, ensure that any changes made on the AD side have fully propagated to the Skype for Business servers. This could account for why your contact object might be behaving unexpectedly.
Just a heads up, Skype for Business is nearing its end of support. While you might still get security updates for a little while, it's good to keep future plans in mind as it is expected to stop functioning completely later on. For now, though, make sure to check your contact object’s settings and try rehoming it if it’s not correct.
It sounds like you've hit a common snag with the contact object not being properly homed. Usually, you can resolve this by using the Get-CsAdContact command to verify which registrar pool your contact is linked to. If it’s still pointing to the wrong pool, consider rehoming it. Also, ensure that your resource account and contact object share the same SIP address and that the LineURI is set up correctly. These details are critical, especially in hybrid setups where small errors can lead to routing issues.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures