Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Voicemail to Email Problem 1

Status
Not open for further replies.

steveycarr

Technical User
Apr 23, 2003
132
GB
Hi Guys,
Standard Mitel 3300 CXi in its own small Network, WAN Port to 2 wire BB Router, 10 Phones, 6 PC's + 1 Server in 3300's LAN, all able to access Internet etc.
I can't seem to get my 3300 MCD 4 to send voicemails to the email server. The system has advanced voicemail enabled in Licence Options, the IP Address of the Email Server is in the same network of the 3300, ICP 192.168.10.2, Email Server 192.168.10.9 which is configured in the System Options Form with a senders email and I've 'Forward to Email' always enabled on the Mailbox with a valid email address.
I know the email server is ok because I've tried it with another 3300, (spare). There's no Software Error Logs, its as if the 3300 just dosent attempt to send the email. I've had all the PC's disconnected from the the LAN leaving only the 3300 and the Server, Have I missed something simple. Any ideas would be much appreciated.

!ExtraDunce
 
I can't recall the details (I don't have them in front of me), but there should be a few threads on this, try a search. VM Network Servers form rings a bell...
 
Setup the Networked VM form (even if the system is standalone)

The DNS suffix can be the issue. without is the VM will send the email as VM-Name@192.168.10.2 instead of VM-NAme@company.com

The Timezone should be set regardless.

Success or Failure, there should be software logs on the 3300 for SMTP attempts.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.
 
So first of all what version are you running? one of the 10.0 versions had vm to email broken in it. Next, are you sure the mitel system is trying to send the email out? you can check this by using a hub and wireshark and sniffing the LAN port of the 3300 to see if you see anything headed towards your mail server. If you do see traffic headed to the mail server its possible that the security on the mail server will not allow you to relay from that. to test this follow this instuctions below and make sure you can recieve one of these messages.











Some peoples mail servers will be locked down and wont allow the 3300 to send emails to people. you can verify that the mail server is setup correctly by going through this.


1.
If you dont know the mail server youre sending to or to check and make sure the mail server is setup correctly with DNS
* Open a CMD prompt
* Type NSLOOKUP
> set q=mx
> theirdomain.com
Response:
Non-authoritative answer:
theirdomain.com MX preference = 50, mail exchanger = mail.theirdomain.com

2.
SMTP communicates over port 25. We will now try to use TELNET to connect to their mail server "mail.theirdomain.com"
* Open a CMD prompt
* TELNET MAIL.THEIRDOMAIN.COM 25
You should see something like this as a response:
220 mx.google.com ESMTP 6si6253627yxg.6
Be aware that different servers will come up with different greetings but you should get SOMETHING. If nothing comes up
at this point there are 2 possible problems. Port 25 is being blocked at your firewall, or their server is not responding. Try a
different domain, if that works then it's not you.

3.
Now, use simple SMTP commands to send a test email. This is very important, you CANNOT use the backspace key, it will
work onscreen but not be interpreted correctly. You have to type these commands perfectly.
ehlo mydomain.com
mail from:<martin9700@mydomain.com>
rcpt to:<recipient@theirdomain.com>
data
This is a test, please do not respond
.
quit
So, what does that all mean?
EHLO - introduce yourself to the mail server HELO can also be used but EHLO tells the server to use the extended
command set (not that we're using that).
MAIL FROM - who's sending the email. Make sure to place this is the greater than/less than brackets as many email servers
will require this (Postini).
RCPT TO - who you're sending it to. Again you need to use the brackets. See Step #4 on how to test relaying mail!
DATA - tells the SMTP server that what follows is the body of your email. Make sure to hit "Enter" at the end.
. - the period alone on the line tells the SMTP server you're all done with the data portion and it's clear to send the email.
quit - exits the TELNET session.

4.
Testing SMTP relay is very easy, and simply requires a small change to the above commands. See below:
ehlo mydomain.com
mail from:<martin9700@mydomain.com>
rcpt to:<recipient@someotherdomain.com>
data
This is a test, please do not respond
.
quit
See the difference? On the RCPT TO line, we're sending to a domain that is not controlled by the SMTP server we're
sending to. You will get an immediate error is SMTP relay is turned off. If you're able to continue and send an email, then
relay is allowed by that server.
 
Hi,
Just a quick update, I tried this customers config on my Lab 3300 and it worked ok. My Lab Software is the latest version and the Customers is an earlier release, I dont have the exact version to hand, so I will upgrade this Customer to the latest release which I'm sure will fix it. I'll update the forum. Thanks for all your help guys



!ExtraDunce
 
Your internal SMTP server may also be configured to allow requests from IP addresses, not domains, so it still may not work. Agreed though, upgrade and see.
 
Fixed,
Updated from 10.0.0.13_1 to 10.0.2.8 cured problem.

Thanks for your input

!ExtraDunce
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top