BCM Capabilities Question

[gs4910]

I have been battling issues with a Norstar system and I am thinking that going to a BCM is the way to go.

I have a quick question on configuration. We have 5 sites, and 2 are very small. I am trying to get a handle on our hardware and key code needs.

My thought was this:
-two sites with BCM 200 v3.6
-main site with BCM 400 v3.7
-two branch offices with IP phones connecting back to the BCM 400.
-capability to display caller ID between offices and call between offices over IP is a requirement.

Do I need to purchase more key codes or different systems? In the existing offices I was going to get the digital station modules for the BCMs to connect existing extensions.

Thanks in advance.

 

[cook1082]

If they are networked you need Voip trunks and MCDN keys.

 

[mad006]

From my understanding of MCDN; you do not need this keycode if it's BCM <---IP Trunk--->BCM. You will only need MCDN if you are going BCM <---IP Trunk---> M1.

Please let me know if I'm wrong.

 

[cook1082]

Dosen't matter you neet it either way.

 

[MagnaRGP]

MCDN is not necessary, but definately helps. For that many sites networked together, you might want to consider adding an NRS to simply the call routing and make it easier to program off-net calling site to site.

Intranet topology and number of users would dictate your final requirements, but I would definately go with all BCM's as 4.0 and skip the 3.X.

 

[mad006]

Cook1082:

Can you please explain further?

 

[madwok]

I'd rather choose BCM50 v2 over BCM200 and BCM400 v4 . I had about 6 BCM400 v4 and 20 BCM50 v2 , all stable with IP trunk and remote IP sets . MCDN is not truely needed . If you got money, spend on SIP trunking instead as it is being recommended by Nortel engineer who designed our system.

 

[cook1082]

We have BCM's tied together for a couple differant customers and they have MCDN.I think it is mainly for centralized VM. So the forwarding to VM will see the OLI of the remote set and send it to it's VM box. For Point to point with their own VM I don;t think you should need MCDN cause the PRI should pick up on the CLID.

 

[frenche]

MCDN is needed for centralized voice mail as well as other features such as CLID and CPND between sites and anti-tromboning. This is the case for both BCM to BCM or BCM to CS1000.

 

[mad006]

I have setup BCM to BCM via IP trunks (non-centralized VM) without MCDN and it still display CLID and CPND. I believe that centralized VM will also work without MCDN. (Have not tried this nor can I verify anti-tromboning)

As a stated earlier, I believe the only time you will need MCDN is when you are connecting to another BCM via PRI or connecting BCM to M1/SL1 via IP trunks.

Maybe things have changed since I touched a BCM. (early '06)

 

[biv343]

MCDN is needed when using centralized voicemail for MWI. It's also needed for CLID/CPND when going to a CS1000. BCM to BCM without centralized VM, over IP trunks, you can get away without the MCDN keycode as you will get the business name of the system and name of the set.

MCDN is required when connecting a BCM to another BCM or a CS1000 over PRI.

TAT/TRO functionality requires MCDN as well.