Hey guys maybe somebody can give me a hand on this issue I am having with our SVMI Email notifications for voicemail not sending the notification email. I checked in the mclass menu and all options are set correct as well as in the system wide parameters menu. This is the error I am getting and I can't figure out why it keeps timing out.

=>NOTICE - MIME Message 0000690C, Time: 2.15s, Voice Size: 32400, Fax Size: 0
=>NET 15:50.36.77 SmtpMain Got Packet MClassSN:668 MsgFile(C:\TEMP\000005C4.EML)
Flags:x1 RetryCount:2
=>NET 15:50.36.77 SmtpBeginSession> Host(174.123.161.xxx) Cur(174.123.161.xxx) I
nSess?0
=>NET 15:50.36.77 SmtpBeginSession Connecting to Server 174.123.161.xxx:25
=>NET 15:50.36.77 SmtpOpen Remote Host End Point: 174.123.161.xxx:25
=>ERROR - SMTP Connect to Server 174.123.161.xxx:25 Timed out
=>NET 15:51.37.30 SmtpClose Connection aborted
=>NET 15:51.37.30 SmtpBeginSession SmtpOpen failed

> SMTP Connect to Server 174.123.161.xxx:25 Timed out

It doesn't look like there is a mail server listening at the destination, or the connection is being blocked my a firewall.

What I thought to I called and made sure port 25 is unblocked it is.. Port 26 same thing.. No matter what it still times out. I can ping the address.. Its very weird.

Does the mail server accept non-authenticated inbound messages ?

Can you ping the SVMi-20E from the local and remote networks ?

I can ping it local. I don't have remote set up as I only access it internally.

It all worked fine till we switched to ATT Uverse. I called ATT and they unblocked port 25 yet that still doesn't work. It does not accept non authenticated messages but I have the username and password in the one menu and it also has been setup that way.

Maybe I am missing something. I am new to setting this up.

Is there a way I can test a connection on the SMVI-20E internally? Like pinging something or ?

So it was working fine until your ISP changed ?

If so, which end (Officeserv or mail server), or both ?

Switched from a T1 to a PRI so had ot get separate data. So went to Uverse cause all that was available in this area.

Try typing the following into a command prompt

telnet 174.123.161.xxx:25

see if you get a connection

yep I got a connection just fine. I also tried port 26

Check the gateway and subnet on the svmi20e matches the pc you tested from

I don't have the cable and are kind of new to this.

Is there a way I can do that via login over hyperterminal?

Type "display c:\sockets\socket.cfg" without the quote marks from the port activity screen and post the results.

The SIO cable is the same as a cisco console cable (light blue) so if you know any it guys that work with cisco they are bound to have some floating around.

# Packet driver settings
ip address 10.0.1.128/24
interface pdr if0 dix 1500 10 0x60 10
route add default if0 10.0.1.1
domain server 64.238.96.12
domain server 66.180.96.12

# The following will cause SOCKETS to display IP status
ip address

# The following lines set TCP parameters
ip ttl 64
tcp mss 1460
tcp window 2920


I see the guys who previously set it up have the DNS Servers wrong and maybe the port to..

I found a cable actually serial w/rj45 on the other end. How do I edit the Socket.cfg file?

seem to remember sconfig

As the remote end is specified by IP the DNS entries may not be used.

Check the netmask and gateway are correct, this is much more likely to be the cause of local connectivity working but remote not.

PM sent re. editing config.

Subnet mask is correct for ip and gateway.
Is that gateway correct?
You will need to run sconfig from a dos prompt to edit the socket.cfg file.

Don't worry about dns the SVMi20e doesn't support DNS lookup for smtp server, so it will always be IP address

Thanks for all help. I am going to try it fix it up this weekend. Since i've read I have to bring the system down. Unless I am wrong on that?

I double checked the gateway and when he configured it, he configured the wrong address. So I'll change that out and see if it works.

You only have to take the voicemail down, not the whole system

Thanks for all the help. I got some time to figure it out this weekend. Was a lot easier then I anticipated. All is working now.. Had to change some ip addresses around and reconfigure our company gateway but all is working.