Search results for query: *

thanks for the reply. Do it matter that the replacement MSC came off a 3.6 system?

I have a BCM200 V4.0 that keeps shutting down and generating critical errors. The indication is that I need to replace the MSC card. I have a spare MSC card that was recovered from another BCM200 system that was upgraded to a 400. Question, can I replace the defective MSC with my spare MSC...

Pardon the stupid question, but if a customer migrates from Option 11 to a CS1000, do they have to replace their Call Pilot VM system or can that be made to work with the CS1000. Also if they did want to replace the CallPilot can the Call Pilot licenses be migrated or do they have to be purchased?

With the Nortel to Avaya KRS transition, the process has changed a little. The good news is, you no longer have to purchase an upgrade keycode if you transition keycodes from a broken machine at 1 Rev to a replacement machine at a higher one. The bad news is, that migration process through...

Should have mentioned this in my original post. The loop start trunks are being delivered over a T1 with a Cisco IAD, so I'm thinking it's highly unlikely the trunks are the source of the problem. Although I guess it couldn't hurt to add a protector anyway and totally eliminate it as a possibility.

I have a customer site where I've had to replace/repair the BCM50 4 times in the last year (2 system failures and 2 HD failures). The original install was a year ago. The customer has had uneven power issues in the past but insists those issues have been cleared up with their power...

looks like I don't have access to the Nortel keycode retrieval system anymore. They've migrated it to an Avaya platform as 12/6/10 What are my options?

I have a BCM50 R3 that's died. It's getting harder and harder to find R3 systems. I want to retain my R3 keycodes. What would be the upgrade process if I wanted to take my R3 keycodes and transfer them to a new R5 system? TIA

yes it works for the other lines and the target line I used was already part of that ring group. I did need to change the control set on the target line but it didn't help in the immediate forwarding of the line to the ring group. I'm thinking when I made the change to the control set on the...

quick follow up question I have the target line for the HG configured in a ring group to immediately forward to the AA if the control set puts the system into night mode but for whatever reason it doesn't want to work. What could I be missing? TIA

That seems to work well. Thank you so much for your time and advise.

I had actually tried doing that before I posted last time (I should have mentioned it). The target line parameters won't allow the HG DN to be the prime set or the Priv. Rec'd number or change the line type parameter to DN:397

THankyou very much for the idea. So I can build the route on Site A that sends the hunt group DN (397) across the SIP trunks to Site B but how does Site B route the call to the hunt group without a target line.

I have 2 BCM50s linked together with SIP trunks with MCDN on each machine. I want to take calls from Target Line XXX on Site A and after three rings and forward to a broadcast huntgroup on Site B. I can't change the DN of the huntgroup on Site B to match the extensions and there are no free...

No SIP trunk software needed. As long as you have the BCM IP client license and the PC has IP connectivity to the BCM, you should be good to go.

Yes both sides are IP phones. Thanks for the ideas. I'll try them and let you know the results.

I have 2 BCM50s 1 R3 the other R5. I have all the MCDN and SIP gateway keycodes installed and enabled. All patches are up to date. I have all my call routing, destination codes, target lines, line pools, etc etc configured correctly ( I believe). The WAN is a VPN. I can make make phones ring...

Thanks for the response, but I was just wondering if I can force a change to the minimum password length from 4 to 6 digits?

Can the user voicemail box minimum password length be changed from 4 to 6 digits on a BCM 4.0 system? TIA

so the latest theory from the customer's IT vendor is that the LAN CTE client is messing with the DirectX drivers and removing the LAN CTE client doesn't help. Any ideas?