Perhaps you could change the "minimum call duration" setting on the BCM. The default is 2 sec. All my systems are set to 8 sec.
This setting determines which calls are included in the CDR report. Calls shorter than the "minimum call duration" are not included in CDR.
Rebooting the system will restore access but it's much quicker to just restart the Voice Management Subsystem service under Diagnostics/Service Manager. It only takes a few seconds.
The scenario:
Customer has all incomming calls forwarded to ext 205 and after 10 rings are meant to forward to the voicemail inbox on that extension (205), however they are being forwarded to the voicemail inbox attached to extension 200 instead.
Both 200 & 205 have voicemail configured. 201...
I have also started receiving this error. Have 20 odd BCM50 1.0 & two BCM50 2.0. Alarm is only on 2.0.
CPU usage on both machines were at times reaching 100% which matched up when these alarms were generated. Any ideas?
I don't know the exact cause of this error but instead of rebooting the system all you need do is goto Dianostics/Services Manager. Find VoiceManagerSubsystem & restart the service. Takes 30 sec versus approx 8 minutes for a reboot.
I have seen this problem over the last 3 years on systems 3.6 &...
You can copy a file called "summary.xml" located in BCMElementManager/bin/access to your desktop PC. It contains connection info for your network elemants.
Set DND on Busy to Yes if you do not want your calls
interrupted with a ring tone when a second call comes in. Instead,the button flashes, indicating an incoming call.
I suspect DND may be set to No.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.