Monitor causes 406v2 reboot

[jtierney]

We have a customer with a 406v2 running 3.2 v54 and 3.2 v28 vmpro. Calls come in to a 'group' ring hunt with apprx. 23 members.

When calls are made to the group extension or are routed there by Incoming Call Route, the system is alright UNLESS Monitor is running. If Monitor is running, we see btwn 150 -250 packet loss then the base unit reboots spontaneously. The DTE trace shows nothing nor does Monitor prior to losing the network connection.

We have tested on and off the customer LAN, and running individual applications (Call Status/Manager/etc) w/o the reboot. We have run Monitor and VM Pro off a tech laptop as well w/o the reboot.

Any info would be helpful.

JT

 

[RotoOrb]

Monitor does use system resources from the switch, possible resource overload, then crash and burn, i wopuld upgrade to v4.0 then run the system status app, less hungry on the switch