T-Metics attendant console drops TN or bad TN

[bltodd]

Hi all, (Sorry about the original post having the wrong error) I struck it out so you can see the change.
We have a T-Metrics attendant console set up on our Nortel/Avaya CS1000 ver. 7.5. It seems to work well for the most part but we have occasional issues where the T-Metrics console cannot connect and we get an "InvalidDUPLICATE TN" message on the switch TTY. The only way to get it back is to change or move the console programming to another TN and then program the new TN on the T-Metrics console. Or move it to a new TN and Back to the original. (a bit easier because we don't have to go to the switchboard to configure) It has no regularity to it. We could go 3 or 4 months with no problems and then have the issue one time and maybe a couple weeks later 2 or 3 days in a row. One thing we have tried recently to rule out corruption on the telephone programming is to build and use a new TN from a different card. We also have a backup console the switchboard operator moves to when this happens. And it too has had the same issue at times. We have been working with T-Metrics support to resolve and it seems that updates or trouble shooting on their part has not resolved it. Also, we have had our Network specialist test and check connections and port configurations. I can't seem to find anyone else with this issue by searching the net. I'm pondering on QOS just because it’s basically a softphone but the programming is still on the CS1000. Other than that it could be a T-Metrics programming or insufficiency problem not detected by support yet. This has been ongoing for a couple years.
If anyone has any experience with this issue or a good idea to troubleshoot this, I would appreciate the help.
Thanks, Bret

 

[yyrkroon]

What type of set is the T-Metric trying to emulate on the CS1000

The only time I've ever seen Invalid TN is when I'm attempting to register a device different than what the TN is define as...ie, attempting to register a 2050PC where the TN was built for a 1165.

When you get this invalid message, did you stat the TN to see what state it was in...idle and register or unreg?

 

[bltodd]

See below for Console programming with type**
THANKS FOR THE QUICK RESPONSE!

I HAD TO EDIT(I had the wrong error was listed) The proper answer to your question about the status:
The switch TTY shows REGISTERED before, during, and, after the issue. We get this error: "DUPLICATE TN." So the T-Metrics possibly gets a network delay? Then tries to establish back on the Telephone Switch and that's when we get duplicate TN error. Again as stated in original post. We have to move the console to another TN and/or move it back and reboot the console PC or re-log it into the network before it works again. Also, we have checked the network connections for packet loss, status and port configuration.


**
DES TMETRC
TN 152 0 15 31 VIRTUAL
TYPE 2004P2 (WE REPLACED A NORTEL 2250 Console with T-Metrics)
CDEN 8D
CTYP XDLC
CUST 0
NUID
NHTN
KEM 2
CFG_ZONE 00001
CUR_ZONE 00001
MRT
ERL 0
ECL 0
FDN
TGAR 1
LDN NO
NCOS 0
SGRP 0
RNPG 0
SCI 0
SSU
XLST
SCPW 395
CLS UNR FBD WTA LPR MTD FND HTD TDD HFD CRPD
MWD LMPN RMMD AAD IMD XHD IRD NID OLD VCE DRG1
POD SLKD CCSD SWD LND CNDA
CFTD SFD MRD DDV CNID CDCA MSID DAPA BFED RCBD
ICDD CDMD LLCN MCTD CLBD AUTU
GPUD DPUD DNDA CFXD ARHD FITD CNTD CLTD ASCD
CPFA CPTA ABDD CFHD FICD NAID BUZZ AGRD MOAD
AHD DDGD NAMA
DRDD EXR0
USMD USRD ULAD RTDD RBDD RBHD PGND OCBD FLXD FTTC DNDY DNO3 MCBN
VOLD VOUD CDMR PRED RECD MCDD T87D SBMD
KEM2 MSNV FRA PKCH MUTA MWTD DVLD CROD ELCD
CPND_LANG ENG
HUNT
PLEV 02
PUID
UPWD
DANI NO
SPID 393X
AST
IAPG 0
AACS NO
ITNA NO
DGRP
PRI 01
MLWU_LANG 0
MLNG ENG
DNDR 0
KEY 00 ACD 397X 0 39XX
SUPY ACID 393X KEY 42
01 NRD
02 MSB
03 SCR 395X 0 MARP
CPND
NAME Marshall PBX
XPLN 27
DISPLAY_FMT FIRST,LAST
04 MCR 395X 0 MARP
CPND
NAME Operator
XPLN 27
DISPLAY_FMT FIRST,LAST
05 MCR 395X 0 MARP
CPND
NAME Elevator
XPLN 27
DISPLAY_FMT FIRST,LAST
06
07
08
09
10
11
12
13
14
15
16
17 TRN
18 AO6
19 CFW 16
20 RGA
21 PRK
22 RNP
23
24
25
26
27
28
29
30
31
KEM 1 PAGE 0
32 DWC 1234
33 HOT D 4 1235
34 HOT D 4 1238
35 HOT D 4 1238
36 MCR 3999 0
CPND
NAME Operator
XPLN 27
DISPLAY_FMT FIRST,LAST
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
KEM 2 PAGE 0 : NO KEYS CONFIGURED
DATE 19 JAN 2016

 

[yyrkroon]

Duplicate TN - T-Metric lost registration with the Call Server, but the CS still has it registered (think it's still reg). When T-Metric attempts to re-register to that TN, the CS send the duplicate TN message letting you know the TN is already registered. You should be able to manual un-reg the TN then T-Metric should be able to reg without having to go through all that mess.

Use to see this a lot with the 2050PC, but what causes it - don't know, never found out...sorry.

 

[bltodd]

Thanks for brainstorming with me. We went back to the vender on this assuming it had to be programming. I don't understand why they never found it before as this has been happening for around 2 years. But they found a default secondary IP in their programming. (S1 and S2) Just like the Avaya 1230 IP Phone. The primary one was set up to our 10.x.x.1 and he secondary one was left as a default (placeholder) address of 192.168.1.1. So if there was a network issue it would go for the second address which would take it off line, then in a few seconds with a failure to connect (S2), it would try the primary IP (S1) but since the phone was still registered, it would reject as a duplicate TN. This issue stemmed from the programmer that installed our system over two years ago. They should have known about S1 and S2.

Thanks, Bret