Java_Bob

if you want to do this CLS CFXA,,,,,,,,,but as Jack will say when he sees this it is not a good practice to allow this all kinds of abuse can happen

do a search of this site for external call forward and you wil get alot of info

jshaw

Thanks, but as I said, all sets have CFXA, and it works within the customer to and external COT line. It fails only when a ICT DID line to the FWD set.

gei_spot

Sounds like TRK-to-TRK xfer problem. Do an enhanced TRAC on the trunk and check the TGAR if incoming is lower than outgoing the call will fail.

__________________
Mr. Wiggles "Really. I'll just come in for a minute."

PP

THE NCOS OF THE DID'S IS MOST LIKELY A 0, CHECK THAT IF IT IS YOU HAVE 2 CHOICES YOU CAN CHANGE IT TO A NCOS HIGH ENOUGH TO DIAL OUT OR GO TO CDB UNDER OPT AND CHANGE CFO TO CFF

jshaw

Well, I did the Enhanced trace on the Incoming DID and then on the Outgoing COT. Here is the test scenerio:
Incoming DID (rout 2, TN 8 0 1 1) calls a set (TN 13 0 9 6, DN 6010) that is CFXA to DN 9-905-681-6200 (some recorded announcement phone).
The DID is seized, the set tries to CFW to the highest COT member, and the call fails. The COT is Rt 0, TN 6 0 1 0.
DID NCOS=7, COT NCOS=0, 500 set NCOS=6, TGAR 1.
Internal calls to the set do get forwarded, but not External Incoming DID calls. The trace shows that it is a "DIRECT MW_CALL", not sure why.

Here is the ENTC of the DID tn (8 0 1 1):

.ENTC 8 0 1 1 0005

.GOTR

.22:38:00 19/08/2004
IDLE TN 008 0 01 01

.22:38:08 19/08/2004
ACTIVE TN 008 0 01 01
ORIG 008 0 01 01 DID RMBR 2 2
TERM NONE
DIAL DN NONE
MAIN_PM READY
TALKSLOT NONE
EES_DATA:
NONE
QUEU DIAL
CALL ID 0

.22:38:08 19/08/2004
ACTIVE TN 008 0 01 01
ORIG 008 0 01 01 DID RMBR 2 2
TERM NONE
DIAL DN 6
MAIN_PM DIAL AUX_PM DNTRAN
TALKSLOT NONE
EES_DATA:
NONE
QUEU DIAL
CALL ID 0

.22:38:12 19/08/2004
ACTIVE TN 008 0 01 01
DIRECT MW_CALL
ORIG 008 0 01 01 DID RMBR 2 2
TERM 006 0 01 00 COT RMBR 0 5
TTR 012 0 04 01
DIAL 6 8 TTR 10
RCVR 13 SET 13

DIAL DN 99056816200
MAIN_PM DIAL AUX_PM DDL
TALKSLOT ORIG 10 TERM 10
EES_DATA:
NONE
QUEU 128
CALL ID 0

AUX NARS

.22:38:16 19/08/2004
ACTIVE TN 008 0 01 01
DIRECT MW_CALL
ORIG 008 0 01 01 DID RMBR 2 2
TERM NONE
TTR 012 0 04 01
DIAL 6 0 TTR 0
RCVR 13 SET 13

DIAL DN 99056816200
MAIN_PM DIAL AUX_PM NARS_CALL
TALKSLOT NONE
EES_DATA:
NONE
QUEU 128
CALL ID 0

AUX NARS

.22:38:20 19/08/2004
ACTIVE TN 008 0 01 01
DIRECT MW_CALL
ORIG 008 0 01 01 DID RMBR 2 2
TERM NONE
TDTN 2 SLOT 30 PTY SLOT 30
DIAL DN 99056816200
MAIN_PM REOR
TALKSLOT NONE
EES_DATA:
NONE
QUEU DIAL
CALL ID 0

.22:38:28 19/08/2004
ACTIVE TN 008 0 01 01
DIRECT MW_CALL
ORIG 008 0 01 01 DID RMBR 2 2
TERM NONE
DIAL DN 99056816200
MAIN_PM HALFDISC
TALKSLOT NONE
EES_DATA:
NONE
QUEU DIAL
CALL ID 0

.22:38:28 19/08/2004
IDLE TN 008 0 01 01

Now here is the ENTC of the COT TN (6 0 1 0):

.ENTC 6 0 1 0 0005

.GOTR

.2246 19/08/2004
IDLE TN 006 0 01 00

.22:43:00 19/08/2004
ACTIVE TN 006 0 01 00
DIRECT MW_CALL
ORIG 008 0 01 01 DID RMBR 2 2
TERM 006 0 01 00 COT RMBR 0 5
TTR 010 0 05 01
DIAL 6 19 TTR 19
RCVR 16 SET 14

DIAL DN 99056816200
MAIN_PM DIAL AUX_PM DDL
TALKSLOT ORIG 16 TERM 17
EES_DATA:
NONE
QUEU 128
CALL ID 0

AUX NARS

.22:43:02 19/08/2004
LOCKOUT TN 006 0 01 00

.22:43:06 19/08/2004
IDLE TN 006 0 01 00

SCH0000

Tried CLS FTTU on the forwarding extension?

jshaw

Thanks all for the replies. I found the probem: someone disconnected one of the outgoing COT lines from the bix. I disabled this unit, and forced the incomming DID call to grab the next trunk, and the call worked. It seems that when the wires of a COT are disconnected or cut, the trunk displays IDLE, so it grabs that route member regardless. If I had been on site, I probably would have seen this sooner!