Route Call Question

[dennislyon]

I'm having a problem with a very simple command. I have a situation where I don't need to execute a script. In my master script when CDN equals xxxx, I just need to route the call to an outside long distance number. Very straightforward, however, it gives me a fast busy. I can change it to any local number and it works. I can call the long distance number directly from my desk, no problems. But when I plug that long distance number in the route call command, fast busy.

Any ideas?

Thanks in advance.

 

[Milesprower]

There may be restrictions in the switch. Sometimes it is easier to route the call to a "dummy" ACD that night call forwards to the correct number.

 

[dennislyon]

I tried that too, same results. I'm sure it's in the permissions, but I'm concerned about opening up a potential toll fraud scenario.

 

[bizkitchris]

to avoid the toll fraud and fix the issue, create a phantom DN that is dcfw to the long distance number then in the script use route call to the phantom DN

 

[dennislyon]

Tried that too, same results. Also, setup an acd to call forward to an external number. Could it be something in NCOS I'm missing?

 

[bizkitchris]

does the NCOS of the phantom have the ability to call the LD number? It mist for it to work.

 

[captaingadget]

Trunk to trunk barring springs to mind. TGAR TARG settings??