Asked by:
Subscriber access - can't log into mailbox

Question
-
Hello
I have set up integration between OCS and Exchange UM and having a problem with the subscriber access.
-
For this scenario the OCS SIP Dial Plan is SIPPlan.
-
The OCS users UM box is associated with SIPPlan.
-
OCS user extension is 12345.
When a user calls the subscriber access number associated with the SIPPlan they are connected to Exchange UM and receive the "Your connected to Microsoft exchange" message. When an OCS user enters in 12345, the user hears "not a valid extension" message. However, when a user presses # and searches for a contact by name, the contact that is associated with 12345, is found and the user can leave a voicemail message for that contact.
Current set up:
UM Dial Plan subscriber access number is listed as 13121112222 in Exchange Console.
In OCSUMUtil interface the subscriber access number for the SIP dial plan is set to +13121112222 (I have also tried it without the + and got the same results)
The OCS user that is created for the subscriber access number is
-
enabled for enterprise voice
-
Line uri is tel:+13121112222
-
Enabled for Federation
-
Appears as type "AutoAttendant" in OCS snap in Users
-
Does not have a mailbox listed in Exchange
Am I overlooking something in the configuration?
Any help will be appreciated.
Thanks,
Jo
Friday, March 14, 2008 4:36 PM -
All replies
-
Have you installed Exchange 2007 SP1 on your Exchange UM Server?
Johan
Saturday, March 15, 2008 12:10 AM -
Yes I SP1 is installed.
Want to make it clear the only thing that isn't working is access to the UM box using the subscriber number. The users can connect to voicemail by selecting "voicemail" in communicator.
Thanks,
Jo
Monday, March 17, 2008 4:08 PM -
Please configure your UM-Dial Plan also in E.164 format
(This works in our environment)
Why would you call exchange on the Access Number and not from the menu?
When you dial the access number you have to type your pin code, from the menu you don't.
Johan
Monday, March 17, 2008 5:31 PM -
Thank you for the suggestion. Just to clarify, you are suggesting I create another Dial Plan using E.164 and add this to the UM IP Gateway that connects to OCS?
The reason why we need an access number is so users can access their UM box when away from their machine. Majority of the users of the application in the environment are highly mobile.
Thank you,
Jo
Monday, March 17, 2008 8:33 PM -
jocellus222 wrote: When a user calls the subscriber access number associated with the SIPPlan they are connected to Exchange UM and receive the "Your connected to Microsoft exchange" message. When an OCS user enters in 12345, the user hears "not a valid extension" message. However, when a user presses # and searches for a contact by name, the contact that is associated with 12345, is found and the user can leave a voicemail message for that contact.
I am trying to understand what you are doing.
1. This is the subscriber access number?
2. Why does the user enter 12345, are they prompted to enter 'something' or do they just think that is what they are supposed to do? I know 12345 is the mailbox of the user.
3. Are you sure that extension 12345 is associated with a user?
4. How many digits are associated with your UM Dial Plan?
Tuesday, March 18, 2008 4:31 AM -
Are you saying that you have another phone system that connects to Exchange UM?
Tuesday, March 18, 2008 11:02 AM -
rsi3 wrote: jocellus222 wrote: When a user calls the subscriber access number associated with the SIPPlan they are connected to Exchange UM and receive the "Your connected to Microsoft exchange" message. When an OCS user enters in 12345, the user hears "not a valid extension" message. However, when a user presses # and searches for a contact by name, the contact that is associated with 12345, is found and the user can leave a voicemail message for that contact.
I am trying to understand what you are doing.
1. This is the subscriber access number?
2. Why does the user enter 12345, are they prompted to enter 'something' or do they just think that is what they are supposed to do? I know 12345 is the mailbox of the user.
3. Are you sure that extension 12345 is associated with a user?
4. How many digits are associated with your UM Dial Plan?
1. Yes, this is the subscriber access number.
2. When calling the subscriber number the user is prompted "please enter your extension or press # to contact a subscriber." The interesting thing here is if I search for the contact using their name the contact is found and am able to leave a voicemail for the contact.
3. Yes I verified using
Get-Mailbox <user>
Get-UMMailbox <user>
4. 5 digits
Thank you,
Jo
Tuesday, March 18, 2008 6:16 PM -
" Are you saying that you have another phone system that connects to Exchange UM?"
Nope, not for this situation. I have successfully had an OCS user mailbox dual homed on a dialplan for the OCS integration and on a dialplan for a connection directly to call manager. The OCS user was able to utilize the subscriber access number for the dialplan connected directly to the call manager to access their UM box. I'm trying to avoid the need to have multiple dialplans on one box (more maintenance, etc).
I'm trying to go through the Mediation server using the subscriber access. When I ran the OCSUMUtil.exe and created a subscriber access a OCS user was also created. I also checked to make sure the subscriber access number matches the subscriber access number for the dial plan in Exchange.
I'm going to perform some traces on the mediation server to help troubleshoot.
Thank you,
Jo
Tuesday, March 18, 2008 6:46 PM -
I solved the issue.
After reviewing the traces on the mediation server, I noticed the call was not reaching the mediation server.
The routing in thecall manager was sending the call directly to UM! I removed that route for the subscriber access number and created a route for the number to connect to the mediation server.
Thank you everyone,
Jo
Tuesday, March 18, 2008 7:31 PM -
Would you mind letting me know how you did this? I have the exact same issue with a small difference. We have multiple UM Dial Plans and only 1 works, the rest never accept the extension.
Thanks.Monday, August 17, 2009 2:38 PM