Network BCM50 and BCM400 4

[jimmers]

Im trying to network a BCM50 with BCM400. I'm using VoIP trunks with H.323 between the two. No matter what extension I dial, it goes to the prime set on the destination BCM. Here are my specs.

Private and received numbers set to 3 on both BCM's
Private network type is CDP
Private DN length is set to 3 on both BCM's
Virtual private network ID is set to 1 on both BCM's
VoIP lines are added to the same pool
My route is using the VoIP pool
I created a route in my VoIP trunks using the other BCM's IP
GW type is BCM
GW protocol is CSE
VoIP protocol is H.323

Any help would be much appreciated!

 

[pronei]

You forgot to define target lines.

And the Private Network ID's need to be unique.

 

[jimmers]

Thanks for the help. I changed the network ID's so their unique. Can you elaborate more on the target lines.

 

[pronei]

BCM50 Element Manager

1. Telephony, Lines, Target Lines
2. Select the first target line listed (generally Line 125)
3. The control set column should already be populated
4. Prime set column should already be populated
5. In the Priv. Received Column, enter the DN of the Set assigned to that target line.
6. On the bottom half of the page, in the ASSIGNED DNs tab, make sure the DN listed is the same DN you just entered inthe Priv. Received Column above. Make appearance type Ring Only (that will send the call to Intercom Key).

Repeat process for each set DN you have advancing the target line each time.

So basically:

Target Line 125 programmed with priv. recvd number of 221 and Ring only on set DN 221

Target Line 126 programmed with priv. recvd number of 222 and Ring only on set DN 222
etc
etc

 

[jimmers]

Sorry I guess I didn't make myself clear with the target lines. I understand how to use them and set them up. I just wasn't clear on why they are needed in order for me to communicate across two BCM's.

 

[Deweyhumbolt]

Because the BCM sees the incoming DTMF as on TRUNKS not internal dialtone. Hence, you need to build Private Digits under Target Lines.

Adversity is Opportunity

 

[jimmers]

Thanks for the response. So every DN needs a target line assigned to it in order to be called from a different BCM?

 

[hawks]

You got it

 

[jimmers]

Thanks, I wasn't aware of that. It makes sense though.

 

[jimmers]

I set up my target lines but it still doesnt work. I get sent to the operator after I enter 2 digits. Any ideas?

 

[hawks]

Let's say site B has extension 300
So if you call from site A and dial 300 all you can dial is 30 and it goes to the prime set of site B?

 

[telcodog]

Are you using a different set of DN numbers at the remote location? Are you trying to use 3 digit dialing or are you using location codes plus the 3 digit DN.

I just set this very same system up with a 400 and 3 other 50's accross the country. Setup is simple in terms of the voip stuff but you do have to set up normal type routing to get the calls to go out in addition to the target line programming listed above.

If you still can't get it to work, give me a way to contact you and I can through the setup I used. Works great but is a bit different from what's listed above.

 

[jimmers]

Hawks, that is exactly what is happening.

 

[jimmers]

emillysdad,
I am using a different set of DN's for each location. The way it's set up at the moment is you dial your routing code, then the extension. That is how I was told to set it up. If there is an easier way I'm all ears. Is it possible to pick up the phone, dial a 3 digit extension, and ring the phone? I appreciate your help. If I can't get it to work I might have to take you up on your offer!

 

[SupportDude]

What are the DN's on the 400?
What are the DN's on the 50?

Are both sites using a DN length of 3 internally?


This is actually pretty simple once you have the concept.



-SD-

http://www.mysupportguy.net

 

[telcodog]

Yes you can do it by just dialing the 3 digit extension number BUT you will have to make sure that NONE of the DNs are the same on both sites. As you know, doing DN changes on a 4.0 can be painfully slow.

Using location codes is much easier and works well also, especially if you can get away with using a single digit code.

In terms of setting up the voip part, set it up with your destination IP as you normally would, your destination digits as your location code you set up in the Private Networking, set the GW type to BCM, the Gateway Protocol to None and the voip protocol to SIP (as long as your 50 is not a 3.0).

In the Private Networking, set your DN length as required (3 in this case I guess), your private network id to 1 (doesn't really matter as it's only applicable to an M1 anyway), your location code to whatever you decide to make it (like 71, 72, 73 etc.) In the MCDN section check off all 3 boxes (not really required but I always check them off just in case), and that's it for the voip stuff.

In the Routing section, create Destination codes for each of your Location codes. Choose a unique route number and set the Absorbed Length to 0. In you route, just make sure you select your voip trunk pool, choose Private as your DN type and don't put anything in the External Number,

Make sure to set up your target lines the way pronei detailed above as well.

The BCM50 is set up exactly the same way. As you know, the information is presented slightly differently but all the parameters are there. Just make sure they're the same for both ends.

Whew, I think that's it. I don't think I missed anything but hey, you never know.

If that setup doesn't work on the first call, contact me here and we'll go through it again, one step at a time.

Good Luck with it.

 

[telcodog]

Sorry, forgot to mention, if you want to just dial the 3 digit extension number, the setup will be slightly different. Let me know if that's what you want.

 

[SupportDude]

If you want to use Location Codes, you have to use UDP, not CDP, under private networking.

The symptom described isn't matching up with what we're being told here.
If you can only dial 2 digits, the BCM is considering the dialing sequence as complete and sending the call. When the call gets to the destination, there are not enough digits coming in with the call to determine which Target Line the call should be handed to, so the call goes to the Prime Set for the trunk it arrived on, which appears to be the receptionist.

Emilysdad makes a very good point ... ensure the DN Type on the route is set to private. One of the things this setting controls is how many digits the BCM looks for before sending the call.

It really isn't this complicated.
You just need to review your information.
It all has to fit into the dialing plan.



-SD-

http://www.mysupportguy.net

 

[jimmers]

Thanks for the help emillysdad and SupportDude. I will give what you posted a try. I'll report later with the results.

Emillysdad, the BCM50 is 3.0. Is the setup alot different to dial directly?

 

[hawks]

On your routing code, are you absorbing all? If not that could be part of your problem.
Example:
DN for site B = 300
Desti Code site A = 4
Absorb = 0

When you dial 4 + 300 to get to site B the system at site A is actually sending 430. Then if site B does not see a Target Line for 430 then it will go to the Prime set.