merlin mess. 3.0 with unified messaging 1

[31LDog]

I am receiving the following error message while trying to connect to exchange server:

Unable to create the email server on the unified messaging application.

Application is loaded on a windows 2000 server w/ service pack 4 domain controller. I have verified IP, Gateway, Subnet, and unified messaging address. We are able to connect locally to the messaging module but unable to get the unified messaging working. Any ideas or suggestions greatly appreciated.

 

[merlinman]

Did you ever get this to work?

 

[jinxs]

did you download the drivers from the avaya website? They have a worksheet on things that need to be done. I'm going to be attempting this as well in the near furture, let me know how things work, how it delivers it's messages, average size of files, ect.

 

[merlinman]

jinxs, do you have some details as to where to go to get this from their website?

I was there earlier and quite frankly, I got lost.

I did not see anything I could use.

I am also trying to implement this.

Please let me know.

This has the potential to be a KickAce thing.....

 

[jinxs]

http://support.avaya.com/japple/css...il&executeTransaction=avaya.css.UsageUpdate()

There you go!!!

 

[merlinman]

Thanx Jinxs

 

[Stengrad]

When, and if, you created the user acount on your Exchange/SMTP server for the UM application, did you give the account access privileges ? Also, the user name for the for the application "must" have local administrator privileges on the PC where the appliction is running. I have this runnning at two sites. The first time I had a problem because I did not give the account access privileges in Exchange. The second, I had problems getting the email server and the UM application talking, because I had the domain name wrong in Merlin Messaging.

Good Luck!

Field Technician
Virginia Integrated Communications

Http://www.vicom-corp.com

 

[merlinman]

OK, here's where I am today.

The Customer's IT guy is the only person allowed to do the changes on their EXCHANGE 2000 Server.

He assures me he followed all the directions to the T, but it doesn't work.

His theory is the Messaging Admin Software also needs to reside on the Exchange Server.

Is he wrong?

I installed the Messaging Admin Software (along with WINSPM) on a "REGULAR END USER" Machine.

Does this make sense?

I will be "CONDENSING" these posts in an email to him, once I think we have this nailed down.

Thanx....

 

[Stengrad]

The UMA application does not have to reside on the the same machine as the exchange server. None of my sites are set up that way. When exactly are you getting the error message? Is it when you try to set the domain name in Merlin Messaging? Or some other place? Remeber the domain name = whatever the letters that are after the @sign.
Ex: whoever@company.com, the "company.com" would be the domain name. I'll post the installation, and trouble- shooting guides in the FAQ area so anyone who needs it can look it over. They helped me out alot.

Field Technician
Virginia Integrated Communications

Http://www.vicom-corp.com

 

[Stengrad]

Well ,I won't post the Quick Ref guide, it doesn't read well the way it posts when I copy and paste. I'll just give you a link to the UMA installation doc on Avaya's site.

UMA Installation Guide:

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

Also, the readme file on the software CD has good tips as well.

Field Technician
Virginia Integrated Communications

Http://www.vicom-corp.com

 

[merlinman]

Thanks a bunch.....

I will let you know how this works out....

 

[MattJenkins]

I got this to work flawless on Win2000 SP4 and Exchange 2000. The UMA service is running on the server with Exchange. The server with Exchange is a DC (don't think that should matter). Follow the directions in Avaya's PDF. Here it is in a nutshell:

Create account on the domain using AD Users & Computers called merlin (or any other name). Give it an e-mail account when creating the account.

On the PC you will install the UMA service on, add user merlin to the Administrators group (not domain admins, enterprise admins, ... just Administrators).

Go into the Exchange System Manager, go under the organization, right-click the server's name and choose Security. Add user merlin and make sure it has full rights. To do this click the Advanced button and make sure ALL allow and NO deny boxes are checked.

Install UMA service.

Restart Exchange Information Store to make sure security settings take affect (instead of waiting up to 15 mins).

Configure Partner system to point to the IP address of the server where you installed the UMA service using the the administration tool. Add server using the administration tool. Make sure server make is correct, and the domain is correct.

If there are still problems you may want to have him check proper DNS setup on the server with the UMA service installed and make sure it can resolve server.domain, otherwise it will most likely fail.

Hope that helps. Now if I can just get this to work with Win2003 and Exchange 2003 I would be happy =)

Matt

 

[merlinman]

Matt,

I am confused about the following:

"Configure Partner system to point to the IP address of the server where you installed the UMA service using the the administration tool."

Do you mean the Merlin Messaging system, instead of the Partner system?

 

[MattJenkins]

You can configure the merlin messaging system by using the RS-232 port or using the modem to configure the IP address of the UMA server. However, that is unnecessary since this setting can be changed using the "Merlin Messaging Release 3.0 Administration" application under the System Properities, Parameters, and set the IP address and choose Save IP. Once that is correct, the "Unified Messaging Application" group will show up on the left hand side, which indicates that the messaging card is aware of the UMA server now.

Matt