calls that FNA from 2nd line of 2616 to Unity connection end up at main Unity connection greeting

[kenthoma]

Calls that FNA from 2nd line of 2616 to Unity connection end up at main Unity connection greeting instead of called number voicemail. Programming in CS-1000 is standard hunt 000 and
LHK 1 to Unity system Number. A trace shows the key 0 number as the calling number when connecting to Unity?

 

[kenthoma]

Adding TNB
NACT
REQ: prt
TYPE: tnb
TN 20 0 5 111

SCH0000

TN 20 0 5 11
DATE
PAGE
DES

DES 000
TN 020 0 05 11
TYPE 2616
CDEN 8D
CTYP XDLC
CUST 0
AOM 0
MRT
ERL 0
FDN 6599
TGAR 1
LDN NO
NCOS 6
SGRP 0
RNPG 0
SCI 0
SSU
LNRS 16
XLST
CLS CTD FBD WTA LPR MTD FNA HTA ADD HFA
MWA LMPN RMMD AAD IMD XHD IRD NID OLD VCE DRG1
POD SLKD CCSD TENA SWD LNA CNDA
CFTD SFD MRD DDV CNID CDCA MSID DAPA BFED RCBD
ICDD CDMD LLCN MCTD CLBD AUTU
GPUD DPUD DNDA CFXA ARHD 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 FTTC DNDY DNO3 MCBN
CDMR PRED RECD MCDD T87D SBMD
PKCH CROD ELCD
CPND_LANG ENG
RCO 0
HUNT 6599
LHK 1
TEN 1
PLEV 02
PUID
UPWD
DANI NO
AST
IAPG 0
AACS NO
ITNA NO
DGRP
MLWU_LANG 0
DNDR 0
KEY 00 SCR 2616 0 MARP
CPND
NAME
XPLN 13
DISPLAY_FMT FIRST,LAST
01 SCR 0 MARP
CPND
NAME KRISTEN JAHN
XPLN 13
DISPLAY_FMT FIRST,LAST
02 TRN
03 AO6
04 CFW 4 6599
05 MWK 6599
06
07
08 ADL 16
09 ADL 16
10 ADL 16
11 ADL 16
12 ADL 16
13 ADL 16 *
14
15
DATE 20 JUL 2017

 

[Firebird Scrambler]

Have you tried changing CLS = CFTA SFA?.

Firebird Scrambler

Nortel & Avaya Meridian 1 / Succession & BCM / Norstar Programmer

Website =

http://somertel.com

linkedin

 

[StanleySteamer]

How are the integration TNs programmed?

 

[kenthoma]

The integration 2616's have CLS: HFD, ADD, CNDA, HTA, MWA
KEY 0 SCR XXXX
KEY 13 MIK
KEY 14 MCK
KEY 15 TRN

I have no access to the CS-1000 and rely on the vendor that manages it for TNB or programming changes. I do have access to the PIMG (used only for MWI) and the Unity connection Rls. 11.5

For Firebird Scrambler I did have SFA added to CLS of the TNB included in this post. I will need to find out what the ACDN(?) 6599 is NCFWed too.

 

[StanleySteamer]

DNDA or DNDD on the integration TNs?

 

[kenthoma]

DES CISCO
TN 060 0 11 12
TYPE 2616
CDEN 8D
CTYP XDLC
CUST 0
AOM 0
MRT
ERL 0
FDN
TGAR 1
LDN NO
NCOS 6
SGRP 0
RNPG 0
SCI 0
SSU
XLST
CLS CTD FBD WTA LPR MTD FND HTA ADD HFD
MWA LMPN RMMD AAD IMD XHD IRD NID OLD VCE DRG1
POD SLKD CCSD TENA SWD LND CNDA
CFTD SFD MRD DDV CNID CDCA MSID DAPA BFED RCBD
ICDD CDMD LLCN MCTD CLBD AUTU
GPUD DPUD DNDD CFXD ARHD 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 FTTC DNDY DNO3 MCBN
CDMR PRED RECD MCDD T87D SBMD
PKCH CROD ELCD
CPND_LANG ENG
RCO 0
HUNT 4021
LHK 0
TEN 1
PLEV 02
PUID
UPWD
DANI NO
AST
IAPG 0
AACS NO
ITNA NO
DGRP
MLWU_LANG 0
DNDR 0
KEY 00 SCR 4020 0 MARP
CPND
NAME CISCO
XPLN 13
DISPLAY_FMT FIRST,LAST
01
02
03
04
05
06
07
08
09
10
11
12
13 MIK
14 MCK
15 TRN
DATE 7 MAR 2008



DNDD The integration TN is only for MWI it doesn't take calls

 

[kenthoma]

6599 is CDP to T-1 (Router) I need to identify what device the T-1 is connected too.

 

[kenthoma]

One other note to add is that the CSK1 tech said that this used to work prior to Unity connection upgrade to Rls.11.5 from 10.5

 

[kenthoma]

Issue resolved by changing Key 0 MCR 2616 0 and Key 1 MCR 2616. Also added IRA OLA & NIA hoping it would make answering/making calls more efficient. The not working after upgrading CUCM & CUC told to me by onsite tech seemed to be a lazy response. I noticed in the TNB above that key features need to be addressed.