Call Forward (CFWD) to a long distance number 1

[sienz]

I need to forward one of the ext in a phone to a long distance number. I have changed the CLS: to CFXA and changed the Redirection DN Length to 16. but I got a busy signal when i call this forwarded phone from an external line. the call went through fine when i call it from internal phone (4-digit)

I also created ACD DN to pointed to the LD number. It has the same issue. I can call it from internal phone but when i call it full number (external phone) i got a busy signal

It seems that there is something that prevent me to forward to LD number.

 

[bigindian65]

how is your RDR and NET data set? cff? trnx yes? extt yes?

Mato' Was'aka

 

[Tman45]

Yes, I agree with bigindian ... this is a call security issue as you normally wouldn't want external calls to your PBX to forward out to a long distance number ... if you open it up too much and someone figures it out you can have major toll fraud on your hands.

 

[roy5188]

I agree with the security precautions everyone has mentioned.
Have you considered having the revert DN in Voice Mail be the LD number and prompting callers to dial "0"during or after the greeting?
RoyS

 

[srtelengine]

Instead of using and 8 or 9 before your number for example 9+1+555-5555 replace it with the route ACOD that you want it to go out on. So it would look like this 1111+1+Number.

Dwayne

 

[lewisp007]

I think by now you have had the solution to your problem but if you didn't, you may want to look at the NCOS and see how the calls are being routed from your system. I am pretty sure that the Ncos of the phone need to be higher.
I had similar problem with a customer about three weeks ago and a higher Ncos was the solution.

"The unexamine life is not worth living, or the life that is living should be examine.

 

[sienz]

Adding ACOD should work but i have a problem with my ACOD. it is not working in general. Anyway, thank you all for your input. I did not make a change in the system since it can open a hole for fraud.

 

[Fleisch]

There are several things to look at here
Trunk in NCOS. Do you have CFF or CFO in CDB Net_data
Ncos of the set plus CFXA in CLS and CFW 12 on key

Also-
FRL on the RLI for the number going out. If the call in starts on a trunk with a ncos of 0 and then is being call forwarded using CFO, when it hits the RLI going out it will get blocked if the FRL is higher and the outbound trung or channel has a higher NCOS.

With CFF, I believe the call takes on the NCOS of the set to pass to the RLI going out, so you need to make sure the NCOS of the set is higher than the outgoing trunk

first you need to determine what route (ld 90)
and find out which RLI it is using
Then go to LD 86 print the RLB for that RLI and see what the FRL is
Most guys made FRL = NCOS but you can further check that in LD 87 with the NCTL at ther NRNG prompt put in the ncos and it will tell you the associated FRL.
If you determine that the incoming trunk has an NCOS of 1 anf the route the

If your using the ACDN to NCFW the number, try using the AC2 access number (if defined)You can find that in LD 86 -ESN data block
You can then go to LD 90 using AC2 to define the number as an SPN if available.

REQ new
CUST 0
FEAT net
TRAN ac2
TYPE spn

SPN 1879 555 4002
FLEN
RLI (make a new RLI with FRL of "0" just for this outbound
SDRR in LD 86)
ITEI (return all the way through)

Keep the RLI just for this kind of forwarding and then nobady else should be able to hit it.

Hope this made soem sense