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

Call forward to external number not working accross TIE

Status
Not open for further replies.

M1north

IS-IT--Management
Sep 28, 2007
357
CA
Hello,

We are trying to figure out why CFXA works when you call the DID externally, however if you call it from a PBX that is connected via a TIE line (PRI) you get a busy.

Works: Incoming DID>PBX3>TIE>>PBX3>
Doesnt work: PBX1>TIE>PBX2>CFXA>PBX3>OUT to PSTN

See the DCH errors below:

DCH 5 IMSG SETUP REF 00008001 CH 5 1 TOD 14:12:10
CALLING #:9030 NUM PLAN: NUM UNKNOWN
CALLED #:4618 NUM PLAN: NUM UNKNOWN

DCH 5 OMSG STP ACK REF 00008001 CH 5 1 TOD 14:12:10

DCH 5 OMSG FACILITY REF 00008001 CH 5 1 TOD 14:12:10
FEAT :TRO

DCH 5 OMSG CALLPROC REF 00008001 CH 5 1 TOD 14:12:10

DCH 5 IMSG DISC REF 00008001 CH 5 1 TOD 14:12:10
CAUSE :NORMAL CALL CLEARING

DCH 5 OMSG RELEASE REF 00008001 CH 5 1 TOD 14:12:10
 
In LD 56, are you using RART's / TBAR's etc?.

Can you call the extension without the call forward being applied?.



All the best

Firebird Scrambler
Meridian 1 / Succession and BCM / Norstar Programmer in the UK

If it's working, then leave it alone!.
 
couple of things to look at.. is the tie another nortel.. in the primary switch.. cff (cdb) will look at the ncos of the forwarding station.. cfo (cdb) will look at the ncos of the originating station..

be sure the ncos of the trunks between the two has an ncos high enough to make the call and that the targ of the tie route does not match the targ of the did route and that the stations do not have a tgar that match either route..



john poole
bellsouth business
columbia,sc
 
I had a similar situation - only the Call Pilot was snagging the number and of course didn't recognize the incomming fowarded DN and dumped it. Thay had to add that incoming DN to thier tables.....
 
CFF is set in RDR_DATA. Trunks are ncos 4 on incoming route. External route access is NCOS 1. We have tenanting and they are all permitted to all routes.

Here is what happens:

CALLED #:7324 NUM PLAN: PRIVATE

PRI254 DCH: 6 DATA: 0 5

PRI254 DCH: 6 DATA: 0 5

PRI254 DCH: 6 DATA: 0 5

PRI254 DCH: 6 DATA: 0 5

PRI254 DCH: 6 DATA: 0 5

PRI254 DCH: 6 DATA: 0 5

DCH 6 IMSG RELEASE REF 00008017 CH 8 23 TOD 16:29:54

 
Here is what the TIE is spitting out:

DCH 117 OMSG SETUP REF 00000015 CH 117 21 TOD 8:33:44
FEAT :NCID
CALLING #:4168888888 NUM PLAN: E164
CALLED #:7324 NUM PLAN: PRIVATE

DCH 117 IMSG FACILITY REF 00000015 CH 117 21 TOD 8:33:44

DCH 117 IMSG FACILITY REF 00000015 CH 117 21 TOD 8:33:48

DCH 117 IMSG CALLPROC REF 00000015 CH 117 21 TOD 8:33:48

DCH 117 IMSG ALERT REF 00000015 CH 117 21 TOD 8:33:48

DCH 117 IMSG DISC REF 00000015 CH 117 21 TOD 8:33:48
CAUSE :CALL REJECTED

DCH 117 OMSG RELEASE REF 00000015 CH 117 21 TOD 8:33:48

DCH 117 IMSG REL COMP REF 00000015 CH 117 21 TOD 8:33:48
 
do you have trmb yes on both ends?

your switch says it will not send a call out the same route it came in. how many stations do you need this on? try cfxa to the acod then then the number..

you cam TRY changing call type on your rlb.. you could attempt maxp 1 acd work arounds..

this is not uncommon with on only one route

john poole
bellsouth business
columbia,sc
 
This has been fixed by changing the OCLI prompt in NET_Data to EXT. I found this deep within another post.

Thanks everyone for trying.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top