3300 conectivity to SMTP server

[SmurfTurf]

I am all of a sudden having problems with my 3300ICP embedded voicemail connecting to my smtp server. I have a network configuration with 50 private networks all connecting through a cisco asa. The SMTP server is provided by my ISP and is outside of my network. It has been working fine for years and all of a sudden it started not emailing voicemail messages. I have a multitech faxfinder on the same private internal network and it connects to the smtp server just fine. Can anyone think of a setting that might be off?

 

[LoopyLou]

What would suddenly have changed? More likely the remote stuff has been changed by the ISP. Can you tell that the messages are being sent but don't reach the server?

I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.

 

[Lundah]

Make sure you can hit your target SMTP server, you can test this through a plain old telnet session. Use a PC on the same subnet as the 3300, then you're checking the entire path. Once you have verified you can reach the SMTP server, then you can start looking at the 3300.

Troubleshooting SMTP:

http://www.port25.com/how-to-check-an-smtp-connection-with-a-manual-telnet-session-2/

 

[Questionary]

Mitel 3300 first tries to ping (ICMP) to the SMTP server address. If ping (ICMP) does not reply, no emails are sent. So check if ICMP is blocked.

 

[danramirez]

check if the email server has been recently updated. It happened to us two days ago and the reason was the ITs upgraded the email server, (no idea what email server was). apparently the new version did not like what the Mitel was sending, something to do with the @ and the Mitel IP address.

http://www.hatkana.com

http://www.wtelecom.com