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 derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Debugging embedded networked voicemail

Status
Not open for further replies.

slapin

MIS
Sep 26, 2006
898
US
Is there any way to increase debug level for networked voicemail? I have a number of complains from trusted sources that some of the messages forwarded from inside of the voice mailbox will come back as undeliverable. I could not repeat the problem and don't see any errors in existing logs. There were no network issues during observed period of time.
Any original ideas are appreciated.
 
By 'logs' do you mean the diag.dat file? If not, then that is the best place to look (on both systems).
 
yes, this file as well. It does not reflect message forwarding activity which is not stable. I hear these complains once in a while from people who were able to do so before and after they reported the problem.
 
Any chance you are running out of space in the vm partition? Or are they by chance large voicemail files? EMEM copies the files locally before sending in case of an error, check to see if you have any files here:

/vmail/vpim/sent/

It may not send if it can't save a local copy?
 
What I also found from users and logs are confirming that the message is coming back in about 10 minutes. Space is good.
 
Are there any logs around the time that this occurs (in diag.dat)? How accurate is the '10 minute' report? It seems like a long time. There are timers in EMEM along the 1 minute scale, so I could see 3-4 minutes given that it has to go back to back between systems.

If you send a message to another user on another system, it should NACK back only if the far end's mailbox is full. I don't think that that shows up in the logs however, you could try and check. In that event, a NACK is sent back to the originating system and the message is restored back.
 
Actually I'm looking for these logs which will reflect SMTP communications. Returning message appeares in logs as a new one. Remote system is not even reporting incoming message. Malbox was not full according to existing records. I was able to track successful session, so I can compare now. The complication is that both systems are pretty heavy loaded and someone is always touching voicemail.
 
In that case, use:

bvpimcltdebug=1

and

bvpimdebug=1

They should put more info out at the shell.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top