Integrating Avaya's Intuity LX to User Email Applications for Unified Messaging

As an Avaya Certified Expert working with Avaya products (but non-Avaya Employee) I'm asked questions all the time pertaining to solving issues with Avaya products. In the interest of promoting Avaya products and services and thus improving the stance of the company that makes, what I feel is the most feature rich and stabil, IP enabled, PBX on the market; I am providing my answers to such questions to users of Avaya products...

A user asked:

"

I have a problem that is driving me crazy. I have a customer that had an initial VM requirement was based around the Intuity LX R2.0 . This client has grown exponentially and as such, now has a global reach that has put the LX into multiple time zones. Granted the LX can support the location offsets on discreet PBXes (with certain RTU enabled), This does not work with the PBX operating in a centralized model (one logical location as far as the Audix is concerned).

As Avaya are not going to resolve this on the LX (development stopped) I can see only one solution and that is to provide them with email delivery in the remote locations. Now all the documentation that I have been able to lay my hands on (and all the other forums) seem to point to a POP3 /IMAP4 solution. This is not acceptable to the client for security reasons.

What I need is some direction or documentation that will allow this environment to function in an SMTP world as this is the only other option other than going to MM.

This is the screen scrape of the SMTP TEST

ipcopen `mx!mis001.business.com!25`

mx_connect: no MX hosts, trying tcp! mis001.business.com!25

Trying address 192.168.5.22

Trying mis001.business.com ...

Opening connection to mx!mis001.business.com!25

---> 220 mis001.business.com Microsoft ESMTP MAIL Service, Version: 6.0.3790.3959 ready at Wed, 19 Nov 2008 12:05:48 +1100

---> 250-mis001.business.com Hello [10.1.3.14]

---> 250-TURN

---> 250-SIZE 12800000

---> 250-ETRN

---> 250-PIPELINING

---> 250-DSN

---> 250-ENHANCEDSTATUSCODES

---> 250-8bitmime

---> 250-BINARYMIME

---> 250-CHUNKING

---> 250-VRFY

---> 250-X-EXPS GSSAPI NTLM

---> 250-AUTH GSSAPI NTLM

---> 250-X-LINK2STATE

---> 250-XEXCH50

---> 250 OK

---> 221 2.0.0 mis001.business.com Service closing transmission channel

All looks good...

Hope someone can assist on this

"

My suggestion:

"

SMTP is a "Receive Email" protocol on the Intuity LX. i.e., you can "receive" a text email in your inbox and it will be part of the user's voicemail space (but the LX may not do text to speech to 'read' the email to the user though). SMTP won't work to transfer messages off or 'from' the LX to another email box.

You are correct, POP3 and IMAP are your available options. The email client (the Outlook or other email client on the PC of a user) must be configured to check email on the Intuity in addition to the Exchange or other email server.

The customer may also be interested in the offering from Mutare known as "EVM" which can pull using POP3 from the LX and push to any other email service via SMTP (it also converts the file from an "*.lvp" file to a "*.wav" file which allows you to play the message without the special Avaya codec - which is a HUGE benefit).

"

This customer ended up selecting Mutare's application - and they love it like every customer I've ever installed one for... it's a very valuable tool for remote workforce.