Embedded Voicemail stops sending Email 1

[sroderick]

Anyone else have a problem where embedded voicemail just stops sending voicemail to email messages or even alerts? The system in question is an IPO 500v2 running 8.1(43). Here is all that monitor shows:

573103394mS SMTP: SMTPServer New Email...
573103395mS SMTP: SMTPServer woken up... Session f514c058 Client 00000000 State 2 Q Size 75 current_message 00000000
573103395mS SMTP: SMTPServer snoozing...

This was from a Test Alarm. The SMTPServer just wakes up and goes back to sleep. If the system is rebooted it works for a day or so. There is no attempt to contact the SMTP server at all once it stops working.

Any thoughts appreciated.

Steve

 

[superikey]

Anyone on this.
We have been having this issue for a few years now and it doesn't seem like its been fixed.
We keep having to reboot client systems, but not frequently enough if the issue arises at random and client doesn't get alerts and doesn't know they have voice-mails waiting.

Isaac Braca
Avaya ACA - IP Office
CTO / ICCS & Co., LLC.


ICCS, Your Premier IT & Telecom Partner, is a New York City Based Avaya SMB Expert Business Partner and IT Consulting Firm.

Visit and Post on my Blog:

http://ipofficeexpert.blogspot.com/

 

[CarGoSki]

I would imagine that the destination is stuffing the entire process.
IPO will try to queue those until it gags.
Not really gag but since the buffer is only so big you can see when it stops trying to send.

You can turn on smtp traces on in sysmon and here is the trick... save them.
The next trick is to parse through them till you find the exact spot where the first email is rejected.
You should see a rejection code and reason.

 

[RingTHIS]

Had the same issue just over a year ago on a 7.0.xx, I think. VM to EMail would randomly stop. We were finally able to trace to Exchange. Exchange had a small limit on the size of the file being sent and once it was eclipsed, it would not allow any more traffic.

 

[fshaw]

The embedded voicemail has an issue on its mail relay program. Once it has an issue, it does not recover. Much like a whiny kid, it will pick up its ball and go home.

If the mail program is unable to connect to the destination mail server, it will simply queue the message. It will queue the next message without trying to send and the next message and so on. It does not appear to ever try to resend its queue. Or at least I am not aware of how to kick start it without rebooting the system and losing the queued messages.

The resolution is to reboot the IPO.

Good luck.
Frank

 

[Telecomboy]

I had a client that had this as well and I think what ultimately solved it was deleting all new messages before rebooting. They had forward on for emails and it got stuck one day. A reboot fixed it and it worked for another day or so. This continued for a couple of weeks and a reboot always fixed it temporarily. After troubleshooting for a while I noticed the reception phone had 100 messages on it. I think what was happening was a reboot fixed it until reception was left another message. At that point the system tried to send all 100 messages through at once and it would get blocked and stop it for the whole system. A reboot fixed it again until reception received another message. I had them delete all messages at reception and it has been working for over a year now with no issue.

 

[Westi]

Telecomboy that is good stuff. Thanks for sharing have some pink stuff

Joe W.

FHandw, ACSS (SME), ACIS (SME)

http://convergednetworks.ca

Give a tech a solution and he will be back tomorrow to ask you the next question, teach a tech how to read the manual and he will be able to solve the problems for a life time.