Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

bcm not cfw'ding out to external numbers

Status
Not open for further replies.

phonetech2012

Vendor
May 18, 2012
284
US
We are trying to cfw'd our sets out to external numbers. We enabled redirect in each user profile so we can now use the feature 4 and feature 84 now. Prior to enable redirect we were getting a denied in admin error on the sets.
When we try the feature 4 or 84 and test it out, only the first 9 digits are being passed down to the carrier, from what they see on the trace. The carrier mentioned turning on IE74, but I am not familiar with that on the BCM. Any ideas? We already tried putting in an extra 9, so we tried 99,1917xxxxxxx, and also 91917xxxxxxx.
Thanks!
 
Check the Remote Packages Filters and make sure the respective Line Pools are included in the package and then assign that Remote Package to the trunk\pool. CFWD to an internal set doesn't apply, but when using external trunks, you will need to check this.

I hope this helps and have a blessed day,

Stocking Distributor for E-Metrotel
 
Also, if you are using POTS Lines, you need to see the Remote Package settings under the Active Physical Lines\Restrictions tab....

Stocking Distributor for E-Metrotel
 
They are using pri lines. I see the remote package settings, but it is not making sense to me. I chose remote access package 01 and put BlocB in it, which is my public lines out, but I am not sure what to do after that. Is there steps from start to finish with this? The install guide seems a little vague. Plus I'm a Meridian guy, so this is all Greek to me :) Thanks for your help!
 
Is 9 the usual dial out method or new route you built?
If new then check these settings:

Routing
Route 00X to use PRI-B
Dest code of 9 to use Route 00X , Absorb All

Dialing Plan Public Network
9 = 12






________________________________________
We take the time to try to answer your questions for free, please return the favor and take the time to answer back and include any resolution you found elsewhere, thanks.

=----(((((((((()----=

small-logo-sig.png

Toronto Canada
 
Yes 9 is the usual way to dial out. "Dialing Plan Public Network
9 = 12"? 9 was not in the DN prefix but I added it and put 12 in the DN length field next to it, still not working. When I call I get a message saying the number you have reached is not in service.
What am I supposed to do with the remote access package? I think that's what I am missing.
 
OK....Here you go...

1. Select a Remote Package (located under Call Security tab). I normally pick one that isn't used as default because if you select the default package, (4), ANY changes you make will apply to ALL lines assigned with that default setting! So, for the sake of this example, lets pick Remote Package 15.

2. Use the "Add" button to add the Line Pool your PRI is in to allow this Remote Package to apply the settings to the Line Pool.

3. Under the Lines\Active Physical Lines tab, select the PRI trunks.

4. Under the Details box, you will see a tab "Restrictions" and default Remote Package will be in the box. Change the Remote Package to be "15" (per our example).

This will allow ALL the trunks\channels of the active PRI to be able to dial out from an external source, such as DISA, or allow the External Call Forwarding.

Try this an let us know if this resolves your issue....
Have a blessed day,

Stocking Distributor for E-Metrotel
 
Thanks for the detailed reply. I have it set up just like you said but it is still not working. I am getting the carrier message saying the number is not in service. The DID works fine when I remove the forwarding, so I know that part is working.

Dialing out straight from the sets works fine and has been for a few years now. This is the first time they are trying to cfw externally though.

9= destination code, route 001, absorb all, access package 15 with BlocB in it, pri's all have 15 in the restriction tab, allow redirect is on all sets, redirect ring as well. I am putting 91917xxxxxxx under the forward all calls field on my set that I am testing with. What else am I missing? I'm ready to blame the carrier and call it a day..lol
 
The carrier may be blocking it. Although Answer supervision doesn't normally play into PRI, D Channel signaling does. Try doing a CFNA for a couple of rings and set the destination to be the external number and see if that works.....Also, If you have a POTS line you can use to try the outgoing re-directed call, try that as well...

Stocking Distributor for E-Metrotel
 
I just got off with the carrier. They are seeing our destination code of "9" being outpulsed, along with the next 6 digits, so they are getting 7 out of 12 digits that we are inputting. The carrier is seeing 9191760 instead of 1917607xxxx

I put my cell number in the CFNA field already with 4 rings, and then with 3 rings and still get the same crap. I am doing this under the ALL DN's, Line access of the set, and inputting the external number under the forward no answer field and also under the forward all field. I am pretty sure this is the right place to input this data..?
 
drum roll....of course it was the carrier as usual. CLID problem, they were seeing numbers that are not in the DID range and rejecting them. The carrier now controls the outbuond clid and it's working.
Thanks for the help guys! Happy 4th!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top