atcomsystems.ca/forum
Device Manager- Unable to access items in VMAA programming: Open Block Table, Activity Log, Subscriber List, System Parameters,...
I have had this happen on several OS systems lately and am wondering if anyone else is running into this issue.

I am able to access system programming for all areas of the database in Device Manager. But if I try to access any part of the VMAA area that needs to gather real-time information (Extensions, Mailboxes, Activity Log, Status Screen,...) I sit and watch the "Wait a moment...Downloading data" pop-up only to ultimately be given a "Check the link between DM and System" error message. I am typically not disconnected from the system and can access other portions of the database but not the VMAA list.

I initially thought this was a remote access/firewall issue but when I am onsite and connect to the system locally I get the same response. The Management IP Whitelist has my IP address range for local and remote access.

When I reboot the system, I am able to access all portions of VMAA programming both locally and remotely.
This has become a more prevalent issue with several sites.

Has anyone else ran into this issue? If so, any steps that were taken to keep access to VMAA programming available? Any common traits to systems that do not allow this access periodically?
I have tried to track the time frame after a reboot that the VMAA database is accessible but I have not been able to determine if after X number of days the programming is unavailable due to fluctuations in the access availability window, and I am not in these systems but once in a while depending on the customer.
Have you checked to see if there are any ip conflicts? What system is this? Is it an embedded VM or VM card?
What is the software version?
Did you add anything in your Management IP White List in mmc875? Did you add a local range like 192.168.x.255 for example? If you did, please take that out.
I have noticed this on embedded VM of 7100 and 7200s.
Software version ranges from 4.8X through 4.98/99 and 5.01- have had the issue with several software versions. Have tried different versions of DM to see if using a newer version of DM than the system software was causing an issue.

No IP conflicts- able to access system programming.

I did have an IP range in the Management IP White List for the system I am trying to access today, but have had other systems that do not have a range but still not able to access voicemail.


It is odd that the entire VMAA database is available for a "period of time" after a system is rebooted, but then the portions of the VMAA that use database information become inaccessible.
If you are having trouble with just the VM DB being downloaded, I would check for an ip conflict if it is a separate VM card. Sometimes they do not always show up in alarm history. Also, are you having port 21 forwarded to the VM by chance for ftp traffic?
I've had the same isssue on a 7100, V4.99.
Reboot and then I can access.
Had something similar when a VLAN was in place. The main system programming could be accessed, but not the VMAA. Ended up putting the PC port on the back of an IP phone into the same VLAN as the phone and it plugged my laptop in to the phone and it started working.
I was incorrect about this system having an embedded VM- this system has an SVMi-20 card. Other systems that I am having this similar issue are 7100's with embedded VM.

There are no IP conflicts on the network- looking at the router, .1= network gateway, .5= MP20 processor, .6= OAS, .7= SVMi-20

Port 21 is forwarded to .7 (SVMi-20 IP address).
The VMAA tables are available after a SVMi card restart which leads me to believe IP addressing is not an issue at this site.


I shouldn't have to reboot hardware to access the VMAA tables. But I am at a loss of where to look to resolve.
Remove the ftp 21 forwarding to the router and just make sure 6001 is pointed to the svmi.

FTP ports are constantly getting slammed with floods. So if the SVMi is receiving all of them then it will cause it to not work correctly. I have seen this at sites that I have had the same issue. I close port 21 to svmi and everything works as normal.
Thank you for the reply. I am updating a couple of sites that I have had this issue with. After a week or so I will check remote access to the Open Block Table database and respond with my findings.
I believe with newer software you can setup a port redirection or change the ftp port.

Without ftp you can't upload new voice prompts or look at logs.
Since you are unable to log onto voicemail. You must reboot it at least once.

Only allow the ip address of your computer which you use OSDM on in the management whitelist.
If you have the whole range in the whitelist. Which means you allow any device in that ip range to bump onto the ftp port. SVMI will block any suspicious connection.
Biztel, If you close port 21 won't you lose access to activity reports etc?
© Sundance Phone System Forums - VOIP & Cloud Phone Help