Help! Need to out Group Hunt GHT asap 1

[captnamo]

I'm moving to Cisco UCM in stages from Nortel/Avaya CS1000E 6.0. Need to out the TNs as we convert because the CUCM and CS1000 are bridged, so I need to out the old phones once the CUCM is cut over to make external calls ring on the new phones.

However, I've run into error SCH8825 trying to out TN 104 0 4 5 (DN 8315).

SCH8825 x
The DN must first be removed from the GHT list.
Where: x = the corresponding DN key number. This number is only printed
for digital sets.

Reviewing old threads, I've learned I must have a group hunt set up that I never knew I had. So here's what I find in LD 20 and LD 57:
REQ: prt
TYPE: ght
LSNO

GHLN 0010
GHT

PLDN 8027
DNSZ 16
STOR 0 8277
STOR 1
STOR 2 8108
STOR 3 8022
STOR 4 8314
STOR 5 4170

and

REQ prt
TYPE ffc
CUST 0
CODE pldn

CUST 00
FFCT YES
PLDN 8027
USE GPHT
LSNO 10
HTYP LIN
CFWI NO
MQUE ALL

DN 8315 isn't even on the list?!?!?!?

I can really get rid of this GHT completely. Is it enough to out it in LD 18, or do I have to do something in LD 57 also. And, if so, any idea which I should do first and how?

Knowing just enough to be dangerous,

--Steve

 

[captnamo]

PS -- Here's the TN I'm trying to OUT in case there's some clue here I don't know about.

REQ: prt
TYPE: tnb
TN 104 0 4 5
SPWD
DATE
PAGE
DES

DES CLERK
TN 104 0 04 05 VIRTUAL
TYPE 3904
CDEN 8D
CTYP XDLC
CUST 0
ERL 2
FDN 8328
TGAR 2
LDN NO
NCOS 6
SGRP 0
RNPG 4
SCI 0
SSU
LNRS 16
XLST
SCPW
CLS CTD FBD WTA LPR PUA MTD FND HTA ADD HFA GRLA CRPD STSD
MWA LMPN RMMD SMWD AAD IMD XHD IRA NID OLA VCE DRG1
POD DSX VMD SLKD CCSD 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 MCDD T87D PKCH
CPND_LANG ENG
RCO 0
HUNT 8328
LHK 2
LPK 0
PLEV 02
PUID
DANI NO
AST
IAPG 0
AACS NO
ITNA NO
DGRP
MLWU_LANG 0
MLNG ENG
DNDR 0
KEY 00 SCR 8315 11 MARP
CPND
NAME RECORDS
XPLN 13
DISPLAY_FMT FIRST,LAST
01 SCR 7315 D MARP
CPND
NAME RECORDS
XPLN 13
DISPLAY_FMT FIRST,LAST
02 SCR 7316 D MARP
03 SCN 8136 0
CPND
NAME Jane Doe
XPLN 13
DISPLAY_FMT FIRST,LAST
04 SCN 8108 0
CPND
NAME John Doe
XPLN 13
DISPLAY_FMT FIRST,LAST
05 SCN 8309 0
CPND
NAME DOE DOE
XPLN 19
DISPLAY_FMT FIRST,LAST
06
07
08
09
10
11
12
13
14
15
16 MWK 4170
17 TRN
18 AO6
19 CFW 4 8038
20
21 PRK
22 RNP
23 SCC 2313
24
25
26
27 CLT
28 RLT
29
30
31
DATE 30 NOV 2017

 

[tbonz25]

The issue is corruption that pointer would have to be removed from pdt.

 

[captnamo]

Tek-Tips to the rescue again! Went back and reviewed a prior thread on the topic. I outed the PLDN in LD 57 first, then outed the LSNO in LD 18, and then successfully outed x8315's TN. Here's the part that helped:

To OUT the PLDN do the following below.

LD 57

MEM AVAIL: (U/P): 2724040 USED U P: 237342 86041 TOT: 3047423
REQ out
TYPE ffc
CUST 0
ALL no
CODE PLDN
PLDN 4330
PLDN
CODE

To out the Group Hunt List.

>ld 18
SCL000
MEM AVAIL: (U/P): 2724082 USED U P: 237342 85999 TOT: 3047423
DISK RECS AVAIL: 1152
REQ out
TYPE ght
LSNO 45

MEM AVAIL: (U/P): 2724115 USED U P: 237324 85984 TOT: 3047423
DISK RECS AVAIL: 1152
REQ

 

[captnamo]

tbons25, you're probably right. I'll bet x8315 used to be in STOR 1.

 

[tbonz25]

Do you have pdt access?

 

[captnamo]

TTY actually has gone into PDT on its own from time to time, having to wait for it to time out to get back to my normal Loads, but I've never used it. Since I'm going to decommission the CS1000E, I'll not pursue it unless I run into more trouble.

 

[tbonz25]

Ok as that's the only way to remove the corrupt pointer without reloading the software that is.

 

[KCFLHRC]

How did we get to a corrupt pointer by outing a GHT ??

 

[captnamo]

KCFLHRC, I think I ended up outing the GHT BECAUSE of a corrupt pointer.

 

[tbonz25]

CS1000 Any Release: Unconfigured hunt calls to and from PLDN (Pilot Directory Number) caused by Group Hunt (GHT GPHT) corruption


Rate Content Rate this Page




Doc ID: SOLN193957
Version: 6.0
Status: Published
Published date: 15 Jul 2010
Updated: 18 Dec 2014


Author:
Content Migrator





Details


Corruption in Hunt Group


Problem Clarification


Unconfigured hunt calls to and from PLDNs (Pilot Directory Number) is caused by Group Hunt Corruption.



Scenario:

1. Call rings on one DN (Directory Number) of the PLDN. If the call is not answered, the call hunts to a DN which is not configured on the GHT (Group Hunt) list.



or



2. Call rings in one DN without any Hunt, FDN (Forward DN), EHT (External Hunt), or EFD (External Forward) configured to PLDN.If the call is not answered, the call hunts to a PLDN.



Both scenarios indicate that the DN has a Group Hunt Corruption. Even though the DN is not listed on the GHT list, it has an incorrect pointer to GHT list so it behaves as a Group Hunt member.



If any change is made to this DN, error SCH8825 is produced indicating that this DN must be removed from the group hunt list, even though the DN does not appear on any GHT list. This confirms Group Hunt corruption.