BCM Remote Trunk Access

[DoubleCross]

I have a BCM 50 networked with voip trunks to another BCM 50 and that works fine.(no mcdn).At a whole different customer I have a BCM 400 networked with voip trunks to a BCM 50 and that works fine.(with mcdn).Now they both want to be able to use remote trunk access.I have never set this up.Can someone give me a brief how to on this?

Thanks.

 

[endlesswinter]

you set it up the same way as you set up the intercoms between the sights.

Your VOIP lines are assinged to a pool. You must build routes and destination codes that use that pool. You must also build a remote access package,and configure your dialing plan accordingly.

 

[cook1082]

Remote package you add the pool that dials out local on the lines.

 

[DoubleCross]

I built a destination code of 39 in local machine,which uses route 2 (voip trunks).In the remote system I programmed a remote access package to use pool a (4 analog trunks).When I dial 39xxxx I get a fast busy,It won't let me dial any more numbers.I have BCM monitor up for both machines.When i dial 39 it grabs voip trunk 4 on the local machine but never goes any further.I'm missing something.

 

[cook1082]

You need to add a dest code to dial out that the other side uses to dial out. Say dest code of 9 Absorb ZERO in public/ in the public dn's add 9 with 11 digits.If using remote gateway add 9 as a dest digit.

 

[DoubleCross]

The local machine has a pri, there is a destination code of 9 to access the pri.The remote system has 4 analog trunks,the pool access code is 9.

 

[cook1082]

In the route use a 9 as the dial out to send to the other system to use for the access for the analog trunks. But also you need to program the remote gateway dest code of 9 since it is adding the 9 when you dial 39. If 39 is just a dest code and the actual number is dialed after it absorb 2 to take out the 39 then the 9 and the number is sent and using the routing on the other side it dials out.

 

[DoubleCross]

It still won't access the analog trunks on the remote side.

 

[endlesswinter]

in the bcm monitor you should see what digits are being sent out. These digits should look like a regular phone call. It shouldn't show dest code just a regular number that can be dialed from remote system.

 

[DoubleCross]

Well,I got it to work,kind of.When I dial 39-xxx-xxxx normally without waiting in between digits it won't go thru.In BCM monitor I can see my local machine grab an ip trunk,then in the remote machine I can see the ip trunk and an analog line active.If I dial 39-xx and pause you can here a little dial tone then enter the rest of my digits it works.Looks like I'm almost there.Going back to tweek on it.Any ideas? Thanks for the help so far.

 

[DoubleCross]

Still making me dial 4 digits then pause before dialing the rest.

 

[vappl]

On the remote site where you have 4 analog trunks, try removing 9 as pool access code and make it a destination code and build a route for it.Just like your PRI.Try 39 again from your local site and the remote local number.Let me know what happen since I'll be building one also next week.

 

[DoubleCross]

I did that, but i have to dial 39xx wait till i here a short dial tone then enter the rest of my digits or it won't go thru.

 

[vappl]

Cook 1082 is on the right direction.
The way I will do it.Gateway destination code=9
Route Destination code=3 ,External number=9,Absorb=all,Public,
and on the dialing plan for digit 9=11 digits in length
if they are 10 digit dialing on local calls.In this case,the way you will call remote number is 3 +local number.