DISA issue with VOIP trunks

[DigitelD]

Customer has an MPLS network with 1 BCM400 4.0(site A)and 2 BCM50's Rls 1(site's B & C). They can call from site to site with no problem over VOIP trunks. What they want to do is call from site's A & B locally to site C's area. They want toll bypass. I understand that the BCM does not support Auto/DISA DN over VOIP trunks. You can, however, use remote packages with VOIP trunks. At site C they are using routing to make their calls. Has anyone set this up before? If so I would appreciate any help on this.

Thanks

SHK Certified (School of Hard Knocks)

 

[bluemr2]

If you are at site A and want to call a local number using site b's local trunks. On site A you need destination codes for all the numbers local to b (I typically use just the area code, but you can use area code and exchange) Create a new route on site A that uses the IP trunks and service type public. Set these destination codes to use this new route, but don't absorb the 9. (assuming you use 9 to dial out). In site A's IP trunk programming put the leading digits (9 plus area code) in site b's gateway. Repeat for all other sites. You will need to set up a remote access package (typically 01) and assign the IP trunks and PRI to the remote package. Assign remote package 01 to the lines. Do this at all sites. Its actually not that difficult, its just a lot of programming. Good luck

 

[hawks]

digitel Remote Packages will work try this for a quick set up:
Site C is really all you need to worry about.
1) Build filter
2) Assign Filter to Remote Package
3) Give the Remote Package access to the Line Pools you are using.
4) Assign the Remote Package to the inbound VoIP trunks and the trunks that are going to be used for outbound.

At the remote sites you might have to change the Public Dialing Plan to add an extra digit for those calls. Hope this helps some.

Just a side note on the DISA try it like a PRI circuit. Just build a DISA DN in site C then dial that DN from the remote side and see what happens.

 

[bluemr2]

What you are doing is sending the whole number (9 included) to the other bcm, then it will follow its own routing to make that call. Pretty slick. One other thing. You will need to increase the length of the default public dn length to 11, so it can send the 9 as well.

 

[hawks]

One thing when you send the 9 across is to make sure that you set up some provision at the remote site for 911 dialing. Because if they dial 9-911 you don't want that going out from some other switch in another city..

 

[MagnaRGP]

Use appropriate dest codes at each site for 911 to keep 911 at the local trunks.

Set up a routing service so that if a call fails over the VoIP, it will fail back to the local PSTN and the call will go through.

Also, if you set up your dest codes properly, users can dial 9-1-npa-nxx-yyyy and have it try the voip first, and then fail to local pstn if voip isn't available.

This makes it transparent to the endusers. I have a 6 BCM and 1 PBX network set up this way, but I use NRS.