Unified Messaging Application with Exchange

[MattJenkins]

We have installed UMA on a Windows 2003 DC server running Exchange 2003. In the MERLIN Messaging Release 3.0 Administration program I have setup the exchange server and it sees it. However, when I try to unify an extension with an e-mail address I get an error in the administration program. Looking in the umslog.csv file in the UMA application on the server, I see:

INFO ,3,[7808],02/23/2004,17:27:50, Request to get info. for mailbox 26.
INFO ,2,[7808],02/23/2004,17:28:02, Request to create emailbox: mjenkins
ERROR,2,[7808],02/23/2004,17:28:02, Could not log on to mailbox mjenkins

I am running the UMA service with a user having domain admins privs. Any ideas on this one? Thanks.

Matt

 

[Mongo5150]

I am assuming that you have the box checked for mailbox 26 that says "unify with email"?

If you go into administrative tool and click on services does the mailbox say "started"??



MFurrer@charter.net

 

[MattJenkins]

Yeah the service is started and running. I am wondering if it has to do with permissions on the exchange user. Domain admins cannot normally (by default) access an exchange user's mailbox for security reasons. However, the service has to run as a server admin. So I wonder if I will have to circumvent our Exchange security to fix this? I hate to do that.

Any other ideas?

Thanks for the quick response.

Matt

 

[Mongo5150]

The user account on the PC where you have UM on? That must have admin privileges. It enables the UM to access the files/registryof the pc.

MFurrer@charter.net

 

[MattJenkins]

Yeah the UM is installed on a Win2003 DC. The user is in the domain admins group. So it has full access to the server.

Matt

 

[Mongo5150]

This link doesnt do squat. But maybe you missed something. Email me and let me know if you get it working, I will tinker and see what I can find.

http://support.avaya.com/elmodocs2/mmsg3/100202_1.pdf

MFurrer@charter.net

 

[itpphoneguy]

Hi Matt,
You know, iP Office is having trouble with WIN2003, is it possible to try running the app. on a 2000 server? Just to try.
-Chris

 

[MattJenkins]

Chris,

I was worried about that. I suppose it depends on how the UM service connects to the exchange service.

Matt

 

[itpphoneguy]

Hi Matt,
Yup, too bad. I hear 2003 has a smaller (faster) kernal and other fixes. Let me know what you find.

 

[MattJenkins]

What a pain. I've given up for tonight. Will fight it again tomorrow. I created an account specifically for the merlin UMA service (was using the exchange administrator account I had setup before). Gave it full rights to the exchange server by going into the exchange system manager, right-clicking the server, and giving the UMA user full privs. Added the UMA user to the Administrators group.

Now I'll be darned if I can't even add the exchange server in the merlin admin program. I gave the following in the logs:

INFO ,2,[22344],02/23/2004,21:31:08, [MainMailboxThread.cpp:668], Request to create email server: forrest
INFO ,3,[22344],02/23/2004,21:31:08, [ExchangeInterface.cpp:201], Creating profile forrest
ERROR,1,[22344],02/23/2004,21:31:23, [ExchangeInterface.cpp:123], Could not open default message store hr=0x80004005
ERROR,2,[22344],02/23/2004,21:31:23, [MainMailboxThread.cpp:701], Could not open a session to forrest
INFO ,3,[22344],02/23/2004,21:31:23, [ExchangeEmailServer.cpp:94], Closing session to server forrest

2K isn't an option at this point b/c our licensing is for 2003. Eventually we'll get it figured out. Thanks for the help so far! If I make any progress I'll let you know.

Matt

 

[Mongo5150]

Matt,
Go to the Legend/Magix forum and look at their FAG's. someone put a nice troubleshooting guide on there. Maybe that will help.

Matt

MFurrer@charter.net

 

[MattJenkins]

I must say that I just tried this using a Windows 2000 DC and Exchange 2000 and it worked flawless. The DC was on a network by itself with only the Messaging system attached to the hub. Now to figure out if it is a Windows 2003 or Exchange 2003, or both, problem.

Matt

 

[MattJenkins]

I installed UMA on a Windows 2000 server (not a DC). Tried to connect to the Exchange 2003 server. No luck. I presume there must be a difference on connecting to Exchange 2000 and 2003, at least in the way UMA does it.

I am giving up for now as I have spent too much time on this. I will have our phone support people call Avaya and ask the status of compability with Exchange 2003.

It doesn't look like at this point UMA is compatible with Exchange 2003. I'll post back if I hear anything from Avaya concerning this.

Thanks for everyone's help.

Matt

 

[itpphoneguy]

Hi Matt,
Sorry to hear 'bout that, but that is where I figured the problem was. As I mentioned, iP Office 2.0 is not compatible with 2003 server / exchange either.
-Chris

 

[MattJenkins]

Our phone rep contacted Avaya. Avaya says they are working on a release that will fix this problem, that they know it exists. No expected release date was given to us :-(

Matt

 

[itpphoneguy]

Hi Matt,
Actually, it may not be that long in coming. Migration to the 2003 platform is ongoing. They (Avaya) have more than one system with this problem. Let us say that Avaya is motivated to fix this.
-Chris