Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here


Avaya: Legacy SMB Systems (Partner/Merlin/Spirit) FAQ

Unified Messaging

Setting up AVAYA Legend/Magix Unified Messaging in non-exchange mode by jukeman1
Posted: 6 Mar 10

I am running unified messaging using an ISP mail provider as the carrier of the messages (non-exchange mode)  There were a TON of road blocks, but I got through them.  

1st: If you were previously using a local exchange server, you must uninstall unified messaging, and re-install it, in the non-exchange mode.  

2nd: I use AT&T U-Verse for my ISP, so I had to create a mail user with U-Verse and use it as the sender (U-Verse would not allow a non-U Verse sender to send mail over their service).  SO, I have every mailbox that is set up for unified messaging use the same e-mail address as the sender.

3rd: U-Verse had port 25 blocked by default (this is the SMTP sendmail port), and port 25 is the ONLY port that the unified messaging software can send on.  So I called U-Verse to open port 25 transmission. This took about 1 minute, as the first tech that ansered the phone knew exactly what I was asking for.  

Finally, I had to adjust my McAfee virus protection software to ALLOW port 25 transmission (the default is blocked, to prevent mass mailing worms from sending mail).  

Of course, your meriln mail and the PC running Unified Messaging must be on the same network, same dafault gateway.

Prior to U-Verse installation, I was using Bellsouth.net DSL; they were not so tight on the originating e-mail address, matching their service.

I've been using Unified messaging in this mode for a very long time, and it is VERY reliable.  It will take much trial and error on your part to get it set up, but it is worth the effort.  I receive my notifications in my mailbox, and on my Blackberry SECONDS after a message is left on the voicemail.  Overall, AT&T's unified messaging is a great, low cost, reliable solution.  

In the logfile, there is a status field.  The status codes are as follows:

STATUS  Description


1       Error connecting to host
2       Bad user name
3       Unable to connect to server (I think)
4       Bad user name or password
8       Connection lost
16      Not connected
18      Invalid session
21      Message deleted
32      Windows sockets error
64      Unexpected error
128     Error creating thread
256     I/O error

Back to Avaya: Legacy SMB Systems (Partner/Merlin/Spirit) FAQ Index
Back to Avaya: Legacy SMB Systems (Partner/Merlin/Spirit) Forum

My Archive

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close