Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

BCM 450 VOIP Trunking/MCDN

Status
Not open for further replies.

ljclives

Vendor
May 22, 2004
276
US
Hello All - have an application question and need to know if something works. Same customer with two locations - BCM 450 at each. I want to do three digit dialing between the two. How do I make this happen if some of the extension numbers are the same? Site A is existing with Voice Messaging. Site B will be a new install. If I have Voice Messaging at Site B do I need MCDN? Can I just use VOIP trunks? Any insight would be appreciatted - thanks!
 
I would use four digit dialing and make each location dns different. ie. site a 2000 series and site b 3000 series. Yes you can use ip trunks to accomplish this. You need the proper keycodes, routes, dest codes and target lines set up to achieve this.

Jeremy J. Carter
Charm City Communications
Norstar. BCM. CS1000 Programmer
 
If you are going to use the mail in side B also, then you do not really need the MCDN code. You can set up Routs and Desti codes at each location to accomplish what you want.
 
Thanks guys. Here is my problem; site A is currently a BCM with three digit extensions; 200 and some in the 300's. Site B is going to be replaced with a BCM and they have ext #'s in the 300's. Four digit extensions will be a serious headache and they will not go for it. Any other options with keeping three digits? With VOIP trunking can you do an access code of say 7 or 8 from one system and then dial the three digit # of an extension in the other system?
 
I mean you can do it and I've been to jobs that had 3 digit dns but it's something that I wouldn't do. It just seems to be a cleaner way to go with 4 digit. You will have to set up dest. codes, ie site A will need a dest of 3 and set the absorb length for 1. So when a user will dial say 300 the 1st 3 will be stripped by the BCM. Have you ever done any routing etc. with a Norstar/BCM or is this the first time?

Jeremy J. Carter
Charm City Communications
Norstar. BCM. CS1000 Programmer
 
Only with PRI's, target lines, Dest codes, etc... Have done remote IP phones but never VOIP tunking. Nortel tech since 1994 so I'm good at what I've done but some things have never attempted - this is one of them. Site A has some 300 series extension and site B is all 300 series. How will your scenario work?
 
Are any of the extensions duplicated between the two sites? For example, is there an extension 325 (just picked that one out of a hat)at both locations? If not then the routing can be done although it will be a little tricky. Example: You have extension 325 at Site B, in order to put the destination code for 325 in Site A you may have to renumber a conflicting DN 325 and/or target line receive digits before it will let you add the destination code.
 
maybe you can use UDP dialing rules, but i am not very familiar with that.

I am trying to do the same at our 6 sites, but dont have the information.
 
tj, you can set it up the same way you've done with a PRI but instead of putting the PRI lines in the route you just tell the system to use the VOIP lines.
 
So is the short answer I can have three digit dialing between sites even though some of the extensions are duplicated? Or if no then I just make sure some none are duplicated and I can do it?
 
& yes they can be duplicate, just build a rout & desti to the site.
 
Just change the dialing like others have said,Explane that its all new and this will work for the best,, or you will be there for a while .. Keep it simple as poss..
 
I agree 110% with Justatec!
Trying to maintain your current dialing plan across multiple sites with centralized voicemail is just begging for constant problems.
Multi-site voice networks, just like data networks, require planing out the address schemes carefully.
In a voice network your dialing plan is basically your address scheme, and you have to emphasize the word plan!

-SD-
 
OK guys thanks but conflicting answers. NO Centralized Vmail, each site will have its own. Definitely keeping three digit extensions - it sounds it will be better to have none of the extensions conflict.
 
Not sure why you coudn't do an access code or destination code over the VoIP trunks between the sites and have it strip the first digit/code.
 
Just adding my two cents worth. I have installed countless multisite BCM's.

4 digit dialing is a must if you have duplicate exts or else you will regret it and so will the customer.

You must have MCDN if you want TAT and TRO to work. Site to Site CLID works much better with it as well.

NCSS, NCDS, for CS1000 and BCM
 
OK - four digit dialing no problem but can each site have three digit extensions still?
 
I would stongly recommend no. All exts and mailboxes should be 4 digits at all sites. If there is a hint of a thrid site then you absolutely have no choice. As an earlier person stated in this thread make one site 2xxx and the other 3xxx. I know it requires some reprogramming of the VM at the existing site. I know MCDN is expensive but I strongly reccommend it.

You have to ask yourself and the customer. Do we want to do this the right way or the cheap way? I have been in your situation and it is not fun trying to piece meal things only to end up doing what you should have in the beginning. Sometimes if customers don't want to do it the right way you are better off walking away to avoid a bad situation. Keeps your good name intact.

The bitterness of poor quality remains long after the sweetness of cheap price is forgotten.

NCSS, NCDS, for CS1000 and BCM
 
OK - I'm following your logic. Site A has 100+ phones with three digit extensions that havent changed since 1995. Huge headache for customer to change. Much worse for me - I have to reprogram entire system! Correct?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top