Merlin Unified Messaging 4.0 Problems

[bolsonttu]

Hello all-

I am having some serious problems getting UM up and running. We currently run Exchnage 2003 through a hosting provider, so using Exchange integration is obviously a no-go. However, I tried getting the SMTP option working, still a no-go. It seems that our Exchange host performs a Sender-ID check to verify that the sender of any message is verified against the list of valid email servers in the MX records of DNS prior to message delivery. In other words, if the email originates from a server other than our "real" email server, the message will not be delivered. I have even tried getting another domain registered to have emails sent through its SMTP server, however, the SMTP server requires authentication before it will allow sending an email message. I have not been able to find a setting for a username and password for the SMTP server in the UM interface. Does anyone know of a workaround for this, or a way to get the suthentication information into UM?

Why does this have to be so complicated??

Any assistance would be greatly appreciated!

Thanks,

Brandon Olson

 

[tdaugirdas]

If you are running Exchange 2003 after the last May/June (2006) Microsoft automatic update - it will not work correctly with UM. You need to roll back the update to prior to May 2006. Unfortunately, Avaya never updated the software to be compatible with newer versions of Exchange.

Tom Daugirdas,
President
STCG, Inc.
stcg.com

 

[kwing112000]

Tom i think he knows that and that was why he was trying to use SMTP instead.

 

[bolsonttu]

Thanks for your responses!

I think I need to do less whining and make my questions a little more clear. I guess the bottom line question is this:

Is it possible to set up the SMTP component to send mail to an SMTP server that requires a username and password to be verified before sending any mail?

I hope this helps.

Thanks Again,

Brandon Olson