bcm tandem dialing 1

[mando1]

Have two bcms connected with ip trunks
one has a pri and uses did
I want to route incoming did calls from the incoming pri to the remote bcm. I can make internal calls from the private network to each other and can dial out from the remote bcm through the pri. How do I route the icoming did over the trunks to the remote bcm ?

 

[SupportDude]

You have to use Destination Codes and routes.
This is where the word Plan is very important in the term Dialing Plan.
Be sure the BCM connected to the PSTN doesn't have any target lines programmed that match the recvd numbers for the remote side.
Buid a Des code that matches the DID range for the remote side and send the Des code to the route using the Voip Trunks.
Make sure the Dialed Digits in the remote gateway match up with the Des Code.

Example: (We'll assume BCM A is connected to telco, using 3 digit DN's and Recvd numbers.)
BCM A:
DN's = 2xx
Lines 001 - 010 = pool I (for IP)
Route 002 = use pool I, DN type Private
Des code = 3A, Absorb 0, use route 002
Destination/dialed digits for remote = 3

BCM B:
DN's = 3xx
Each set needs a target line with Private Recvd number matching the Des code to route calls over from BCM A

Fairly simple if the proper planning was imployed.

 

[mando1]

Ok here is the rub, dn lenght = 4
Recieved digits from the phone compnay is 7

 

[SupportDude]

Not a big problem.
You'll just have to do some conversion at BCM A.
You can absorb digits at the Des Code level and add digits at the route.

Give me exact details for one DID and Set and I can provide and example.

 

[mando1]

Thanks you so much for the help
bcm a with pri is 4 digit dn from 7100 to 7179
bcm b is 7711 to 7790
bcm a pri did number range is 487-7100 487 7119
483-3140 to 483 3179

we want to route the 483 numbers to the bcm b

 

[mando1]

excuse me the dn on bcmb is 7712

 

[SupportDude]

Easy enough.
But, you will have to build the route with a DN type of public to tandem the calls from A to B. The Private Received number length is based on the DN length, so we don't have the required room.

BCM A:
Route 002 use Pool x(IP Trunks) DN type Public
Des code 483A, absorb 0, use route 002
Remote Gateway use 483 as dialed/destination digits

BCM B:
You can use the Target Lines you've already built for your private calls and populate with the 7 digit Public Recvd Number or build new target lines.

 

[mando1]

Thanks again, I assume that the A from 483A is a wildcard ?

Howver, the call did not route to the remote, I am not sure what I am doing wrong. I followed the instructions exactly as you spelled out, it never tries to route. I know the did number works beacuse I teporarily assigned it to BCM A to check. Removed it then assigned it to the remote target line. No dice out of service mesaage from teh teloc.

Thanks for your help!!!

 

[SupportDude]

Damn!
Sorry ... I forgot one key element.
You need to setup a remote access package and assign it to the PRI lines and the VoIP lines.

Try this...
Go to Configuration, Call Security, Remote Access.
Choose Package 1.
In the bottom panel add the PRI Bloc and the VoIP Bloc.

Now assign the remote access package to the lines.
Go to Telephony, Lines, all lines.
Choose a line.
In the bottom panel choose the "Restrictions" tab.
In the field titled "Use Remote Package" assign package 01.

That should do it!

 

[mando1]

Thanks again for your help, I was on teh right track, and will try agin tommorow. I had a remote access package, but both the pri and the voip pools were not in it. Perhaps that was why the remote BCM could access the pri ? but not the did's routing correctly ?

I assume the remote package has to be on the bcm A. Do Ineed remote access package on BCM B also ? I created one using the voip pool.
Thanks agin, I am a compute guy and this routing is a bit greek to me. Somone else suggested building targte lines on the main pri bcm and redirectign them to the remote dns, that works, but is there a downside ?

 

[SupportDude]

(I assume the remote package has to be on the bcm A.)
Yes.

(Do Ineed remote access package on BCM B also?)

(Thanks agin, I am a compute guy and this routing is a bit greek to me.) Not a problem ... we were all new once!

(Somone else suggested building targte lines on the main pri bcm and redirectign them to the remote dns, that works, but is there a downside ?)
Yes ... you only have a finite number of Target Lines. If you don't forsee using more than the system can allocate, go ahead and use them. The procedure I provided is how we typically do it so we don't use up the Target Line resources.

 

[mando1]

A little puzzled yet, If I create dest code with the entire number in it 4833145 it will route correctly (with as dest digits 4833145 on the voip trunK) If I use the wildcard it will not route correctly, I tried a couple of things also, I used the 4833145 as a dest code absored 3 and tne had the pub recvd target line on the remote bcm 4 digit at 3145 and it worked, but whenevr I try the 483a, 4833A, 48314A with the correct route to trunks it fails. HMMM

 

[mando1]

Ahh Found it, an errant target line had been assigned locally in the range that prevented the wildcard from working. Thanks so much for your help!!!!!!!

 

[SupportDude]

Not a problem!
It's the tough ones that are the most fun.

Glad you're up and running!

-SD-