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

Weirdest prob ever: change one DN name (CPND), it changes another too 2

Status
Not open for further replies.

chippowell9

Technical User
Aug 18, 2005
176
US
This has happened on a couple different occasions now. CPND database corruption? I change the CPND name on one DN and it changes it automatically on another DN. No relationship between the two phones EXCEPT: They were both worked on recently (maybe the last two built/renamed), and they both use MCR keys instead of SCR keys. I can fix by OUT'ing one's name in LD 95 and then rebuilding it, so it's an easy workaround once the problem is discovered, but I'd rather solve it for good.

Any thoughts?

Here's a demonstration in LD 95, followed by one phone's TNB.

REQ [highlight #8AE234]prt[/highlight]
TYPE name
CUST 0
PAGE
DIG
DN 8687

DN 8687
TYPE SL1/MIX
NAME Jane, Ferguson
XPLN 27
DISPLAY_FMT FIRST,LAST

DN 8434

DN 8434
TYPE SL1/MIX
NAME Jane, Ferguson
XPLN 27
DISPLAY_FMT FIRST,LAST

DN **

MEM AVAIL: (U/P): 94306985 USED U P: 8906773 421183 TOT: 103634941
DISK SPACE NEEDED: 547 KBYTES
REQ [highlight #FCE94F]chg[/highlight]
TYPE name
CUST 0
DIG
DN 8434
NAME TestPhone,8434
DISPLAY_FMT
DN
ENTR
DCNO

MEM AVAIL: (U/P): 94306985 USED U P: 8906773 421183 TOT: 103634941
DISK SPACE NEEDED: 547 KBYTES
REQ [highlight #8AE234]prt[/highlight]
TYPE name
CUST 0
PAGE
DIG
DN 8434

DN 8434
TYPE SL1/MIX
NAME TestPhone, 8434
XPLN 27
DISPLAY_FMT FIRST,LAST

DN 8687

DN 8687
TYPE SL1/MIX
NAME TestPhone, 8434
XPLN 27
DISPLAY_FMT FIRST,LAST

DN ***

If you follow along, you can see that both phones were named "Jane, Ferguson". Then I changed 8434 to "TestPhone,8434". Then when I printed both, they were both named "TestPhone,8434". Whatever I change one to, it changes the other. Doesn't matter if I change the name in LD 95 or right in the TN itself. Here's the TN for 8434:

DES J6009
TN 004 1 09 15 VIRTUAL
TYPE 3904
CDEN 8D
CTYP XDLC
CUST 0
MRT
ERL 0
FDN 8988
TGAR 1
LDN NO
NCOS 4
SGRP 0
RNPG 0
SCI 0
SSU
LNRS 16
XLST
SCPW
CLS CTD FBD WTA LPR MTD FNA HTA TDD HFA GRLA CRPA STSA
MWA LMPN RMMD AAD IMD XHD IRA NID OLA VCE DRG1
POD SLKD CCSD SWD LNA CNDA
CFTD SFA MRD DDV CNID CDCA MSID DAPA BFED RCBD
ICDD CDMD LLCN MCTD CLBD AUTU
GPUD DPUA DNDD 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 VMSA
CPND_LANG ENG
RCO 2
HUNT 8988
LHK 1
LPK 1
PLEV 02
PUID
UPWD
DANI NO
AST
IAPG 0
AACS NO
ITNA NO
DGRP
MLWU_LANG 0
MLNG ENG
DNDR 0
KEY 00 MCR 8434 0 MARP
CPND
NAME Jane, Ferguson
XPLN 27
DISPLAY_FMT FIRST,LAST
01 MCR 8434 0
CPND
NAME Jane, Ferguson
XPLN 27
DISPLAY_FMT FIRST,LAST
02 ADL 16
03 ADL 16
04 MIK
05 MCK
06 ADL 16
07 ADL 16
08 ADL 16
09 ADL 16
10 ADL 16
11 ADL 16
12
13
14
15
16 MWK 8988
17 TRN
18 AO6
19 CFW 8 8898
20 RGA
21 PRK
22 RNP
23
24 PRS
25 CHG
26 CPN
27 CLT
28 RLT
29
30
31
DATE 9 JAN 2017
 
What version you running? There is an issue with the CPND in 7.6 that could go back. We saw the same thing and Avaya provided a patch. They did also cringe when I informed them some people were changing names instead of removing the name and adding back in. Personally I out the name and then add back new, but this comment may spark a string of comments about what is the correct way to do it.

Remove Patch MPLR33704 and replace with MPLR33622. When you install 33622, it doesn't remove 33704. It just installs and you have to manually remove 33704.

Hope this helps.

John Anaya
Amdocs Inc.
ACSS/ACIS - CS1000 Rls 7.5/Call Pilot 5
ACSS/ACIS - SME - IP Office 8.0
APSS/APDS - Avaya UC Services

Public Profile
 
Yes, we are on release 7.6. Thank you for the info on the patch!

No, I was never taught to out and readd names, rather than changing them. When a user leaves, we change a few things: NCOS, HUNT/FDN, and name becomes "Vacant,[DN]" When a new user comes and takes over the phone, we change it to the new user's name. Never had an issue on SCR keys, just these last couple times with MCR keys.

Great, I have a plan now re: outing the names, plus the patch. Thanks!!!
 
I have actually done a name change and the system adds the old name with the new name. That's when I got in the habit of just outing and adding.
 
Yeah, I've had similar issues, and for us it was when messing with the name format. For example, our CS1K's name format is First, Last. So if we changed "Jane, Ferguson" to simply "Vacant" the phone would then read "Vacant, Ferguson." We've also had Personal Directory issues, BFS label issues...you name it!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top