remote filter

[RYLSFAN]

i have 2 bcm's networked together and we can dial between them via our VoIP gateways. My question today is... can someone please explain to me how i set up remote access so that users on system A can call out local through system b?

TIA.

Thats not my fastball, thats my hurry up and get by you pitch... Satchel Paige

 

[gecko202002]

Setup destination codes for local calling to go through your VOIP trunks on site A, set absorb digits to none. At site B setup same destination code, absorb dest code only, to go out local trunks. Make sure you setup a remote access package at site B that allows VOIP trunks to access local trunks and apply to all trunks that will be used.

 

[RYLSFAN]

after following these instructions the best i could, i don't seem to get and outside. any ideas?

route 001
dest 8

accessing line pool a

Thats not my fastball, thats my hurry up and get by you pitch... Satchel Paige

 

[biv343]

I'll assume you dial 9+number to access the PSTN.

Site A (no PSTN trunks). Build a route pointing to the IP trunks - DN type is public. Build destination code (not line pool code) for 9. Absorb none. Point to the route mentioned above. Add 9 to your destination digits table under the site config for the IP trunks. Also, don't forget to change your prefix default from 7 (or 10) to 8 (or 11). The system will attempt to send the call after 7 (or 10) digits are dialed otherwise. You will also need to build a new prefix of 91 with a length of 12 for the LD calls. May need to build a 90 if international dialing is required.

Give the IP trunks access to the PSTN trunks by building a remote access package on the "far end". For example, add pool A and pool N to package 1, and assign package 1 to all CO trunks and IP trunks. When a user at the "remote" site makes a call, the digits will come across as 9XXXXXXX, and will follow the destination codes on the system with the PSTN trunks.

Don't forget about 911 on the other system - might want to put a COT or two in there for outbound 911 - adjust your destination codes appropriately.

 

[hawks]

The Remote package at site "A" is the key. That package has to match on the inbound line and also on the outbound line of site A. If the package matches and the call is allowed then it will go out site A.

 

[RYLSFAN]

so does the caller have to hit, 2(site a VoIP destination code) and then 9(site b line pool destination code)? I'm alittle turned around.


Thats not my fastball, thats my hurry up and get by you pitch... Satchel Paige

 

[hawks]

You can do it that way or you can use the Digit table and if you dial a 2 from site B it will insert the 9 at A. Tha way the people just dial 2+number. If 2 is for extensions in site B then I would use 9 just like I was at site B when making the call.

 

[RYLSFAN]

so i have changed directions. I now have

dest 8 using
route 003 pointed to pool B (VoIP lines)

9 is the line pool access code at site B.

So i have asked the user to dial 8.9.555-1212 and they are given a fast busy... all numbers outpulsed by the system as I watch the bcm monitor.

am I even close?

Thats not my fastball, thats my hurry up and get by you pitch... Satchel Paige

 

[hawks]

When you dial 8 from site A what line does that come in on site B?

 

[RYLSFAN]

when 8 is dialed, line 001 is called at site b(site b is a bcm 50)

Thats not my fastball, thats my hurry up and get by you pitch... Satchel Paige

 

[hawks]

OK does Line 1 at site B have the same Remote Package assigned to it as the line being used to go out of site B?