Connecting BCM 400 and BCM 200 together through VoIP trunk

I'm looking for some information on what can and cannot be done with the BCM200/400 system.

We have two offices. One has a BCM 400 system and the other has a BCM

200. The two offices are connected thogether with 10 Mbps Verizon TLS connection that we want to use for Voice traffic as well. What we would liek to be able to do is:

  1. Have standard 3 digit extensions for everyone in the organization regardless of which office they are in. And be able to dial that 3 digit extension without having to add a prefix if the person you are trying to call is in the other location.

  2. Be able to receive all calls from the outside (connected to the phone company with a PRI) and be able to get to the person that you are trying to get to by punching their extension number when the greeting message comes on. This should work even if the person is at a location other than the one that has the PRI connection.

  1. Be able to forward messages from one mailbox to another even if that mailbox to be forwarded to is on the other BCM.

Initially our vendor led us to believe that all these could be done and had us buy the VoIP licenses. Now they are saying that none of the above can be accomplished.

Is that really true? How can I get the two BCMs to act as a single autonomous phone system?

Thanks,

Shahid

Reply to
shahidsheikh10
Loading thread data ...

It can all be accomplished if you have VoIP trunk Key Codes and Vpim call pilot key codes

The Key is coordination of your Dial plans and 4 digit extensions. Each BCM comes with 600 extension numbers, so you need 4 digits to keep them from overlapping one another.

You will have to take charge of your installation an dictate your Dial Plan to your installer.

If BCM 400 DN range starts at 2221 thru 2820, then BCM 200 DN range should be 3221 thru 3820

Also it would be nice if you could coordinate your PRI DID range to match

For example you have a PRI with (NPA)NXX-2200 thru 2299 delivering 4 digit DNIS

Initialize BCM 400 with DNs starting at 3221 thru 3820 then pull down the first 50 DNs down into the first 50 DID range 2200 thru 2249 this is done with DN renumbering

Then initialize BCM 200 with DNs starting at 4221 thru 4820 and pull down the first 50 DNs down into the last 50 DID range 2250 thru 2299, using DN renumbering.

This will allow you to coordinate extension DN and DID number without conflicting Private Dial Plans between systems and have both systems use the same PRI for outbound and Inbound dialing.

The 10 Mbps circuit should be more than adequate to handle this level of traffic, especially if Verizon is controlling QOS at both ends

Reply to
XBarNone

I think you will also need MCDN code if you want to dial remote site from main auto attendant.

b
Reply to
bjsvec

Only if one side is Meridian One / CS1000 / SL100

Reply to
XBarNone

Cabling-Design.com Forums website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.