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 Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Call Forward External problem

Status
Not open for further replies.

Harley01

IS-IT--Management
Aug 10, 2006
66
US
I am trying to forward a DN X1234 to an outside location. I have set the CLS to CFXA and put in a long distance number in the fdn field of the station. When someone from within the building dials X1234 the call forwards to the LD number but when trying to call X1234 from an outside location you get a busy after 2 rings. I know that when someone places the call to X1234 they come in on the same trunk group that the forwarded number on X1234 goes out. Any suggestions would be helpful.

Thanks, Steve
 
FDN is used for Internal calls so it is working the way it should. Try putting the number either at the Hunt or the EFD prombt.
 
You will be opening your system to potential Toll fraud. Usualy you have to sign a waiver with your CPE (customer prem equiment) maintenance vendor before you do this.... if you have one.

If you can CFNA to an ACD queue then It's safer to setup an ACD queue that has the NCFW as the LD number.
 
Check CDB for CFF instaed of CFO.

And I wouls use the ACD CNFW and use the ACOD of the Route the call would go out on.




This is a Signature and not part of the answer, it appears on every reply.

This is an Analogy so don't take it personally as some have.

Why change the engine if all you need is to change the spark plugs.


 
I've not seen a vendor require a waiver in many years. As a vendor I always insist that we require them of our customers, but I am usually overruled by upper management.

We recently had an experience where a customer got hit by Toll Fraud and is wanting to blame us for the configuration of the system that they authorized. What a pickle... if only they had demanded the waiver as I'd suggested.
 
i always just chgd cls to cfxa and then chg the cfw to say 12 on the key then let the user press cfw 9#...
 
PS, Pardon me if you know all of this already...

I would agree with acewarlock. LD 15 CDB OPT CFF will permit phones to forward offnet if the phone can call the number directly. CFF stands for "Call Forward, Forwarder" which means that the FRL associated with the outbound call is taken from the forwarding TN (the TN where you program the FDN) instead of from the originating TN (which would be the trunk the call came in on.)

Using LD 23 ACD-DNs with NCFW (small typo on acewarlock's part but still essentially accurate) would bypass FRL restrictions in your ESN (electronic switched networking) datablock by using the ACOD on the out-bound route.

And, yes, changing Customer Data Block (CDB) Options (OPT) from CFO (Call Forward, Originator) to CFF does open your PBX to toll fraud if any sets in your building are configured with CFXA, CFW keys and an NCOS sufficient to reach off site (or the ability to dial the ACOD directly).

You can find all sets with CFXA using the LD 81 LST FEAT CFXA routine.

Code:
OVL000
> LD 81

REQ: LST
.
.
.
FEAT CFXA
FEAT

.
.
. output




Good news for us today, the customer was made to realize that the toll fraud issue preceded the replacement of the voicemail system which died in the beginning of December 2007. We're no longer on the hook for the system being changed during the rebuild work, the issue precedes our company's involvement with the customer.

Bad news for them, their national long distance provider is trying to hit them for the full cost of every fraudulent call. Semi-hopeful news for them, we also happen to be an agent for that long distance provider so we're going to see if we can help get a waiver on some or all of the fraud. (Some of it is so very clearly fraud...)


Specifically the problem with this site was the voicemail ports were configured with NCOS 5 (FRL 5) and the ESN (specifically SPN 011) was configured with an RLI that had an FRL of 0... which meant that any phone was permitted to dial internationally. Since the issue arose, the customer has agreed that there is no need for voicemail to call off site for any reason.

(The DATE output on when the TN was last changed is invaluable in showing when the data was last changed. Looks like someone many years ago left the back door open and the problem only recently started, or perhaps only recently became excessive.)
 
Thanks to everyone. I changed the CDB to CFF and it is working now.

Thanks, Steve
 
Keep in mind Steve, that this opens up possibility of phone abuse. If I were you I would throttle it down to cfw 8. That will allow for forwarding only to a local number.

With it wide open someone let's say on the east coast has family on the west coast so he forwards his phone to his relatives number (long distance) and then goes home and calls his desk. Now he is on a local call and talking long distance on your dime.
 
Thats why I use an ACD to forward to a cell phone.

Also if you only put cfw8, you can still manually add the rest of the digits when you call in, I have done that many times.




This is a Signature and not part of the answer, it appears on every reply.

This is an Analogy so don't take it personally as some have.

Why change the engine if all you need is to change the spark plugs.


 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top