Routing Question for BCM's

[TLBRINSON]

This system has been dumped on me. Basically, we have 4 branches, 1 has a BCM400, and 3 have BCM 50's. 2 are in one area code and 2 in another. 1 of the branches in each area code have a PRI line coming in. The 2 branches that don't have PRI's dial out on analog lines. All branches have a data network with VOIP to call extensions. So any extension can call any other extension at any branch.

Ok, having explained all that, my task is to set up "toll bypass". Right now, one branch can call another thru VOIP with no long distance, but if we want to call the building next to the remote branch, then it's long distance. How do I set up, in the routes and the destination codes, to dial out of the PRI at another location? I have tried all different kinds of destination codes and always get a fast busy. The extensions at Br1 all start with 291? (DID's) and 30??, Br2 extensions are 400?, Br 3 are 50??, and Br4 are 600?.

Branches 1 and 3 have the PRI's. Here are the destination codes for those branches:
Br1: 4, 50, 60A all using Route 2 which is VOIP, DN type private, and 9 which uses route 1 which is the PRI.
Br3: 29A, 30A, 3333, 40A, 60A, route 1, which is VOIP, DN type private. and 9a which uses route 1 which is PRI.

Hopefully I've given enough information. If not, please let me know. Any suggestions at all on how to set this up to avoid paying long distance is greatly appreciated.

 

[senk1s]

each location has unique first digit dialing

A B C
2 3 4

Destcode 3 ->rte to B Tgt line recd 3xx
Destcode 4 ->rte to B Destcode 4 ->rte to C
Destcode 2 ->rte to A

Without formatting hopefully this makes sense

 

[senk1s]

first column - config for A
second column - config for B

 

[TLBRINSON]

No, I'm sorry, I'm new at this. It doesn't make sense to me. The extensions are working, so the destinations beginning with 2, 3, 4, 5, 6 are working correctly.

Answer this questions for me. This might help me understand better. When a destination is using a certain route, and that route is assigned to a certain pool, and the VOIP lines are assigned to that pool. If every destination just points to the VOIP pool, how does the VOIP pool know which branch to route that call to?

 

[acewarlock]

By the IP address programmed under
Services
IP Telephony
IP Trunks
H.323 Trunks
Remote Gateway

 

[TLBRINSON]

I don't seem to have those options. Maybe we're using different software? I'm using Nortel BCM Element Manager to connect to BCM50's and a BCM400, using software 4.0.2.03a.

 

[gberger]

On your Bcm 4.0, it is under Configuration-Resources-Telephony Resources-Bus 0(ip trunks)-Routing table-
Your destination digits will match a destination Ip. If you
want to have multiple destination digits pointing to the
same ip adress, you need to separate them with a space.

 

[MagnaRGP]

If you are going to do toll bypass, then it would be wise with that many branches to purchase an NRS. That way all configuration is done once in the NRS and addition of branches is made simple.

I set up toll bypass on 5 BCMs and a CS1000M across Canada and all users dial normally (4 digit CDP ext dialing, 9+NPA-NXX-XXXX for local calls and 9+1-NPA-NXX-XXXX). The systems will handle the digit manipulation necessary (takes some programming) and will fail to their own local PSTN if teh VoIP network is unavailable. Next phase sees more units being placed within overlapping NPA's where several units will cover the same areas, but some calls within a single NPA are LD from one site and local from another. There are first choice and second choice units for a single call.

It's time consuming to set up, but well worth it as future adds don't require duplicating the whole database into each new machine.

Speak with your vendor. It will be worth the initial investment.

 

[TLBRINSON]

I will look into the NRS thing. Thanks for the advice.

I would like to try and make this work in the meantime. I now understand how VOIP calls get routed to different BCM's. I would like to set it up to be switched out at of a different BCM if we dial an 8 instead of a 9. I have it set up in the route that anything with a destination code of 8 gets routed to the VOIP lines, and under telephony resources, I have an 8 in the destination digits to route to the BCM that is local to the call I am trying to make. Also, in the other BCM that the call is being routed to, I have an 8 in the destination code to route to the PRI, but when I call the #, (for example 82815555555) I get a fast busy. Any ideas of what I am missing?

 

[TLBRINSON]

Ok, the reason I was getting a fast busy was because I had an absorbed length of 1 which was cutting off the 8 as I sent it over VOIP. Now, I am getting a public network message saying to check the number and dial again. When I check the BCM monitor from where I am, it shows the whole string of numbers being sent across the VOIP line, but when I run the monitor at the far end, I can see it going out the PRI, but it's cutting off the last 2 digits of the number. Any ideas are greatly appreciated.

 

[biv343]

Could be a few things going on. If you dial 8+number at the far end, with the PRI, does the call complete? My guess is that either the destination code of 8 whatever at the far end is removing too many digits, or something in your public DN lengths needs to be adjusted.

Is your route type marked as public for the 8+ calls that go over the IP trunks? If its private, you could be sending the wrong call type to the far end, or the system is truncating digits. Try making a new route on the "non PRI" end using the same pool the IP trunks are in with a call type of public, point the destination code of 8 to that route and see what happens.

 

[TLBRINSON]

Thanks so much for the response.

I did not have them try dialing out with an 8. Good suggestions, I will have them try it tomorrow.

The route is marked as public. If I dial 81411, then the call is properly switched out of the PRI to 1411, and goes to information. If I dial 82815551480, then it tries to dial out 28155514 on the PRI. It is truncating the LAST 2 digits of the number, so I get a "check the number and try your call again" message. What the heck is truncating these digits? The default DN length on the calling end is 10, and the PRI end is 11. I tried changing the default to 11 on the calling end and it didn't do anything.

Thanks for your help.

 

[biv343]

If you use 10 digit dialing to get to the PSTN, define a public DN prefix of 8 with length of 11 on the 'non pri' BCM, and build a public DN prefix of 81 with a length of 12. You may be truncating the digits on the non PSTN side of the device.

 

[TLBRINSON]

That was it! On the calling end, I had to add an 8 to the DN prefix with a length of 11.

Thank you so much for your suggestions.