Nortel Trunk to Trunk Transfer

[kprintz]

I searched through the threads for this and found a few but none of the threads indicated that any of the suggestions resulted in correcting the issue, so here I go. I am trying to allow trunk to trunk transfers so that our call center agents can call back customers, then transfer them to a third (outside) party. When the transfer key is pressed, the agent can dial the toll free number for the third party and conference in both the customer and the third party but cannot transfer the call or drop out without disconnecting the two calls. I tried implementing the Trunk to Trunk feature per the Nortel NTP's but instead of it working, it causes transfers (that normally work) to stop working. (ie inbound call from being transferred across TIE lines to another Nortel in our network). The trunks have supervision set to yes, and here is my NET_DATA

TYPE NET_DATA
CUST 00
OPT RTA
AC1 LOC
AC2 INTL NPA SPN NXX
FNP YES
ISDN YES
VPNI 0
PNI 2
PINX_DN
MBG 0
BSGC 65535
PFX1
PFX2
HLOC 500
LSC
RCNT 5
PSTN NO
TNDM 15
PCMC 15
SATD 1
OCLI NO
DITI NO
TRNX YES
EXTT YES
FTOP FRES
VNR NO
NIT 8
NAS_ATCL NO
NAS_ACTV NO
FOPT 14
CNTC
NATC
INTC

 

[dlesap]

Try DITI YES

 

[GHTROUT]

I am guessing the Trunk Routes could hold the key. Curious if the trunk route used to call the customer is usually the same one used to call the toll free number. And if true is it set up as COT...

If I am not mistaken, coneecting to outgoing COT trunks will always always drop when you drop. No matter what you do, they will still drop.

If by chance this is your setup, I think the workaround might be classsifying the route and members as as DID.

Looks line you have the intl supp package, which changes things - such as even having the DITI prompt, which may be the fix.


but program the route to operate like the COTs

with you in the call - and releasing yourself will either not complete or will drop the connection - regarless of all the or conference bring you and two outgoing COTs in a three way call will two outgoing calls over COT


is that trunk route classified at "COT"

If it is COT, than I I would create a new route to move a few of the members to, if possible. Make the route a WAT

If that isn't feasable in the scheme of things: Is the toll free number but the trunk route for each call is the same

~

http://www.DeadPhone.com/

http://www.GHTROUT.com/

 

[Firebird Scrambler]

First of all, check that you are not using "RART" in LD 56. You may be trying to dial out on a route that is barred. Another way is to check the routes in LD 21 for "ART" near to the end of the data string.
Whilst you are there, check that "TRMB" is set to "YES" to allow calls to be routed back onto the same incoming route.

All the best

Firebird Scrambler
Meridian Programmer in the UK

http://mysite.wanadoo-members.co.uk/firebird_scrambler

Useful Nortel forum at

http://www.tspforum.com

If it's working, then leave it alone!.

 

[kprintz]

Thanks to all for the responses. We are not using Route Barring.

When the agents call the customer, they could go out tie lines to another PBX location to get to the public network but then when they attempt to transfer to the toll free number, they would use one of these two routes. Also, keep in mind, the agents are not restricted from calling, they just cannot complete the transfer. (pressing the transfer key to complete the transfer doesn't work)

ROUT 0

TYPE RDB
CUST 00
ROUT 0
DES VERIZON ISDN
TKTP DID
M911_ANI NO
M911_TONE NO
NPID_TBL_NUM 0
SAT NO
RCLS EXT
VTRK NO
DTRK YES
BRIP NO
DGTP PRI
ISDN YES
MODE PRA
IFC NI2
CBCR NO
NCOS 0
SBN NO
PNI 00002
NCNA YES
NCRD YES
CHTY BCH
CPFXS YES
CPUB OFF
DAPC NO
BCOT 0
INTC NO
DSEL VOD
PTYP PRI
AUTO NO
DNIS NO
DCDR NO
ICOG IAO
RANX NO
SRCH LIN
TRMB YES
STEP
ACOD 8900
TCPP NO
PII NO
TARG 02 03
CLEN 1
BILN NO
OABS
INST
IDC YES
DCNO 1
NDNO 1 *
DEXT NO
DNAM NO
ICIS YES
TIMR ICF 512
OGF 512
EOD 13952
NRD 10112
DDL 70
ODT 4096
RGV 640
FLH 510
GRD 896
SFB 3


PAGE 002

NBS 2048
NBL 4096

IENB 5
VSS 0
VGD 6
DRNG NO
CDR YES
INC YES
LAST NO
QREC NO
OAL YES
AIA YES
OAN NO
OPD NO
CDRX NO
NATL YES
VRAT NO
MUS NO
RACD NO
EQAR NO
FRL 0 0
FRL 1 0
FRL 2 0
FRL 3 0
FRL 4 0
FRL 5 0
FRL 6 0
FRL 7 0
OHQ NO
OHQT 00
TDET NO
TTBL 0
ATAN NO
PLEV 2
MCTS NO
ALRM NO
ART 0
SGRP 0
AACR NO

REQ: PRT
TYPE: RDB
CUST 0
ROUT 1

TYPE RDB
CUST 00
ROUT 1
DES BELL DOD
TKTP COT
NPID_TBL_NUM 0
PRIV NO
SAT NO
RCLS EXT
VTRK NO
DTRK NO
ISDN NO
PTYP ACO
AUTO NO
ICOG OGT
RANX NO
SRCH LIN
STEP
ACOD 8901
CPP NO
TARG 02 03
CLEN 1
OABS
TIMR ICF 512
OGF 512
EOD 4096
DSI 34944
NRD 10112
DDL 70
OOD 1
ODT 4096
RGV 640
FLH 510
GRD 896
SFB 3
CRD 0

IENB 5
TFD 0
LEXT 100
VGD 6
SST 3 0
NEDC ETH
FEDC ETH
CPDC NO
SPCT IMM
HOLD 02 02 40
SEIZ 02 02
RGFL 02 02
RVSD 08 31
ILLR 02 02
CDR YES
INC YES
LAST YES
QREC NO
OAL YES
AIA YES
OAN NO
OPD NO
CDRX NO
NATL YES
MUS NO
MR NO


PAGE 002

RACD NO
MANO NO
EQAR NO
FRL 0 0
FRL 1 0
FRL 2 0
FRL 3 0
FRL 4 0
FRL 5 0
FRL 6 0
FRL 7 0
OHQ NO
OHQT 00
TDET NO
TTBL 0
ATAN NO
OHTD NO
PLEV 2
MCTS NO
ALRM NO
ART 0
SGRP 0
AACR NO

 

[kprintz]

also....I tried DITI=YES and that prevents inbound calls from being transferred back out to the public network.

 

[aramirez148]

are you r sets programmed with CLS= FTTU instead of FTTC?

Andy Ramirez
NNCSS BCM 3.0

What thaaa????

 

[kprintz]

yes....for the one set I am using to test this feature.

 

[GHTROUT]

Ref: kprintz (Programmer)
10 Jul 06 9:53

Are you saying the two outgoing routes posted are in anothetr PBX? Do you think it could be related to the route datablock programming in the Agent's own PBX? I may have misunderstood, but in any event I think the first step to solving a problem that holds a feature from completing is going to be in the PBX where the feature is being attempted.



~

http://www.GHTROUT.com/

 

[kprintz]

the 2 routes I posted are in the same PBX, and this is also the PBX that houses the agents.

 

[aramirez148]

can you post your set data?

Andy Ramirez
NNCSS BCM 3.0

What thaaa????

 

[kprintz]

DES 017261
TN 068 0 07 09
TYPE 2616
CDEN 8D
CTYP XDLC
CUST 0
AOM 0
FDN 6880
TGAR 0
LDN NO
NCOS 19
SGRP 0
RNPG 71
SCI 0
SSU 0000
LNRS 16
XLST
SCPW 2
CLS CTD FBD WTA LPR PUA MTD FND HTA TDD HFA
MWA LMPN RMMD SMWD AAD IMD XHD IRD NID OLD VCE DRG1
POD DSX VMD CMSD SLKD CCSD SWD LNA CNDA
CFTD SFD MRD DDV CNID CDCA MSID DAPA BFED RCBD
ICDD CDMD LLCN MCTD CLBD AUTU
GPUA DPUA DNDD CFXA ARHA FITD CLTD ASCD
CPFA CPTA ABDD CFHD FICD NAID BUZZ AGRD MOAD AHD
DDGA NAMA
DRDD EXR0
USMD USRD ULAD RTDD RBDD RBHD PGND OCBD FLXD FTTU DNDY DNO3 MCBN

CPND_LANG ENG
RCO 0
HUNT 6880
LHK 1
PLEV 02
AST 00
IAPG 1
AACS NO
ITNA NO
DGRP
MLWU_LANG 0
DNDR 0
KEY 00 SCR 8648 0 MARP
CPND
NAME IVR TEAM HOTEL 8
XPLN 16
DISPLAY_FMT FIRST,LAST
01
02 TRN
03 AO6
04 CFW 8 5759
05 RNP
06 ADL 16
07
08 ADL 16
09 ADL 16
10 ADL 16
11 ADL 16
12 ADL 16
13 ADL 16
14 MWK 6880
15
DATE 7 JUL 2006

 

[aramirez148]

try changing your FTOP to FTLY in your NET_DATA.

Andy Ramirez
NNCSS BCM 3.0

What thaaa????

 

[kprintz]

ok....thanks for the suggestion.....I tried that....still doesn't work.


TYPE NET_DATA
CUST 00
OPT RTA
AC1 LOC
AC2 INTL NPA SPN NXX
FNP YES
ISDN YES
VPNI 0
PNI 2
PINX_DN
MBG 0
BSGC 65535
PFX1 610
PFX2 921
HLOC 500
LSC
RCNT 5
PSTN NO
TNDM 15
PCMC 15
SATD 1
OCLI NO
DITI NO
TRNX YES
EXTT YES
FTOP FTLY
VNR NO
NIT 8
NAS_ATCL NO
NAS_ACTV NO
FOPT 14
CNTC
NATC
INTC

 

[GHTROUT]

Is there a TIE route to the other PBX that is still part of the picture?, or is that simply one of the alternatives you had tried in testing.

-----------------------------------------
kprintz (Programmer) 10 Jul 06 9:53
When the agents call the customer, they could go out tie lines to another PBX location to get to the public network but then when they attempt to transfer to the toll free number, they would use one of these two routes. Also, keep in mind, the agents are not restricted from calling, they just cannot complete the transfer. (pressing the transfer key to complete the transfer doesn't work)

kprintz (Programmer) 11 Jul 06 9:08
the 2 routes I posted are in the same PBX, and this is also the PBX that houses the agents.






~

http://www.GHTROUT.com/

 

[kprintz]

Yes....in fact....there are several (5) tie routes that the call could be routed over to get to the public network....just depends on the area the customer lives in. I included the two local DID/COT routes because these are the 2 routes that would be used when the agent attempts to transfer the call (customer) to the 3rd party (toll free number). Of course, if the customer happens to be local to this PBX, then the call out to the customer and the call to the third party could be placed on the same route.