I am having a UM problem. We deployed some people from using avaya phones over to all ocs client. When I disabled UM and reenabled with the OCS UM Policy, I have one user who tries to call our VM extension and they enter their extension and they receive an error stating =
(insert extension here) is not a valid mailbox extension.
However if you call their extension and do not answer the phone, it will roll to the UM Voicemail. Any suggestions on how to fix this?
I'm facing the same problem.
If i dial the extension, and do not answer the call, it will go to VoiceMail and i'm able to leave a voicemail and receive the voicemail in my Exchange Inbox.
But if i dial the UM Pilot it prompts me for my extension but I will get "(insert extension here) is not a valid mailbox extension."
Anyone have any resolution for this?
If you have multiple UM dial plans then you will need to dial into the UM dial plan that is associated with the mailbox in question.
... or add multiple EUM "e-mail addresses" to the user's account. Use the same extension number, but add one for each dial plan.
Here's mine: x639 in 2 dial plans, as well as the SIP one for Lync:
- Proposed as answer by Greiginsydney Tuesday, May 15, 2012 11:09 PM
Ensure the UM account/User account is not 'disabled' in Active Directory.
Find the account, right-click and if 'Enable' is an option on the context menu, then the account is disabled and you will get this error message. Also the icon will show a small down arrow on it in Active Directory.
The suggestion to add multiple EUM addresses to the account can work but would be difficult to maintain. I have found you need to have the Pilot Identifier set properly in your hunt group, especially if you have more than one associated with an IP PBX or gateway. That fixed it for me.