Search results for query: *

BCM50 will support two DITs, but you need keycodes to have the expansion modules that they are installed in.

BCM will migrate to Linux in the October timeframe. The main reason is that Microsoft will no longer support Windows Embeded NT after 2006. The release will be BCM 4.0 Any BCM with a 20MB hard drive can be upgraded to release 4.0, but the BCM will have to be at release 3.6, or 3.7 first.

They will only hear it ring on a set if the same lines that the Auto Attendant answers ring, or appear and ring on that set. I warn you, that for standard lines, you need two rings to get Caller ID information into the system. As far as I know, the menu repeat key only works from the AA, or...

You could set up your AA to send the incomming caller id number to a mailbox node on your CCR tree. The mailbox you choose would be the target info box.

DND issues aside...if I understand what you want to know, you cannot have multiple appearances of target lines have different ringing attributes.

To my knowledge the APC smart ups is the only system supported, and it uses a DB9.

BCM 4.0 will also use element manager and be Linux based. I had heard that it was to be released 4th quarter, but someone recently told me it would be 2nd quarter of 06. Not sure which is true. BCM 4.0 will also allow telset programming.

Re: BCM at rls. 3.7 I have noticed that since we upgraded our BCMs to 3.7 we get "Internal Server Error" on many BCMs (200, 400, 1000) when we access greetings for AA or Call Center. The problem appears especially after F982. Anyone else?

As I understand it, if the CO does not provide caller ID with name, it has a problem with the BCM if we send system name. I personally have not experienced this, but have heard the information from many of my students.

Blotnik Thanks, but the systems don't recognize that a MBM is even installed on the bus, with or without a phone installed. Thanks, Jim

Thanks all... I have tried all of these things and more. The machines are at 3.6, and all other MBM's work just fine. I am about to conclude that it is an MSC issue. Thanks, Jim

acewarlock, I assume that you used F*0 and pushed the button in question to verify that it is a pool key. If so I have a question: What kind of lines are in pool B? Is it possible that they are manual tie lines to the hospital? Jim

I have had a few BCM400 - 3.6 systems that fail to recognize any DSM (16, 16+,32, 32+ or 4X16). Other MBM's work fine. Has anyone else had this issue? Jim

I assume if your system is at 5.1, your system is a MICS 0X32 not a 8X24? If so, disconnect supervision is available on DS or CI trunk cards only. The older cards (without DS or CI printed on the card) will work but will not provide supervision. It sounds like you have turned the feature on...

Does the problem exist on both internal and external calls? Might be a trunk problem. I have never heard of the port that an IP set is plugged into on the ethernet switch making a difference unless it is a line powered LAN. Perhaps the power supply for the phone is the problem. I also wonder...

Bcpaul, The amphenol punchdown for the GATM 4 or 8 is actually: 26-1 27-2 Skip 28-3 and 29-4 30-5 31-6 Skip 32-7 and 33-8 etc.

I assume that you meant ASM8 for bus 2? The only thing I would do differently would be to put the DSM32+ cards on 2 and 3, and the ASM8 on 4. This would give you a digital set on port 201 for the operator/alarm set, etc.

Is there any reason why a NAM with DVCs cannot support centralized voicemail? Unless it will not support the latest NAM software, I am not aware of anything. Any help?

Can you select next?

Rapetou, You may be right, but the documentation says that the purpose of the DND on busy is to allow calls to work up the keys if DND is set to busy. Otherwise, how or why would you program a Target Line to go to the ICM key, and work its way up?