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

Monitor Voicemail Pro 1

Status
Not open for further replies.

fortage

MIS
Jun 15, 2000
329
US
3.1(15)
Is there a program that will monitor voicemail pro? Something similar to running it in application mode.

 
Yes, its called debug2 or somthing like that. You can also go to services where the vmail runs and go to properties and allow desktop interaction. This will show constant raw data running in the vmail service (same as debug2). I think you have to stop the service first to enable it.
 
Hey Super - where can I find the debug app. My search of the HD came back empty?
 
This was provided by avaya tech support. Its not on the avaya site. I cant send it to ya today cause I will be out the rest of the day. Leave your email and I will try to send it to ya tommorrow morning.
 
I tried using the Dbgview.exe program from the link and there is no output on the screen or in the log file. Does it work for VMPro 3.1.15?

I followed the directions and added the registry key for the debugfile as * under HKLM\Software\Network Alchemy\Directories and then decided to just reboot the VMPro server. I'm running VMPro on a Windows 2003 Server with SP1.
 
Well, then there is i useless peice of software then.
I have a good version but i cant give it to you.
The following instructions do the same as the software but is a bit less userfriendly, nevertheless you will se the same info in the log file.
Hope it helps.....

The Debug Trace output from the IP Office VoiceMail application running on a PC.
- The IP Office Voicemail application (Voicemail Lite, Voicemail Pro and Voicemail Pro Service) all produce Debug tracing. The level of the tracing provided, the name and size of the Debug file are all configured via settings in the PC’s registry.

- The debug file that is produced is given the name “DbgOut.txt” by default and is located in the root (c:\) directory. The default size of the DbgOut.txt file is set to 4Mb. Both these settings can be changed and are held in the registry and are located at - HKEY_LOCAL_MACHINE\SOFTWARE\AVAYA\Common\Utilities\Debug Message Logger\Settings.

The Debug setting is set to level 5 by default when Voicemail is installed. Under certain circumstances this setting may need to be increase to level 9.


- VoiceMail Pro – The Registry location for this setting on Voicemail Pro is: -HKEY_LOCAL_MACHINE\SOFTWARE\AVAYA\vmprov5\Debug\ Filter Level

- The Registry location for this setting on Voicemail Pro Server is: - HKEY_LOCAL_MACHINE\SOFTWARE\AVAYA\vmprov5svc\Debug\ Filter Level

- If VoiceMail Lite - The Registry location for this setting on Voicemail Lite is: -HKEY_LOCAL_MACHINE\SOFTWARE\AVAYA\vmlite\Debug\ Filter Level

- If Embedded VoiceMail - You will need to use the SysMon application and enable the following option: CALL > Embedded VoiceMail
 
Thanks for the info. I tried it out and it works.
 
Addendum:

trace level 0 = lowest ( = no messages )
....
tracelevel 9 = highest ( = all messages )

Other applications ( KeyServer etc. )also write in the same file and have corresponding registry settings ( default level = 5 ) change to 0 if you only want VM logged
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top