After SYSLOADing

[PBXT3CH]

our 61c (we got our vendor to convert 8 digital to 8 ip) i noticed that one of our ACD supervisors was suddenly deleted! when trying to rebuild the set through OTM, it says that the number has a conflict with the PBX. here is what I see:


REQ: PRT
TYPE: DNB
CUST 0
DN 7336
DATE
PAGE
DES
NO ACT SINCE NO DATE

here is the ACD group and TN's:


DN 7585
CPND
NAME ADMISSIONS ACD
XPLN 20
DISPLAY_FMT FIRST,LAST
TYPE MCDN
MCID 87235 TN 004 0 04 02
MCID 87221 TN 004 0 03 06
MCID 87224 TN 004 0 03 08
MCID 87584 TN 004 0 03 11
MCID 87215 TN 004 0 07 09
MCID 87232 TN 004 0 03 15
MCID 87499 TN 004 0 10 13
MCID
MCID 87429 TN 004 1 07 08
MCID 87305 TN 020 0 08 06

notice that there is a tn missing where the SUPERVISOR used to be.

and when EDD the switch after performing a change in the PBX, it had given me an EDD NO GO BAD DATA.

I suspect corruption, what are the steps to resolve?

thanks,
-pt

 

[thattekguy]

When you do a conversion like that you need to delete the digital tn's first, not doing that, the PBX will automaticaly delete the 8 that it needs to to replace with the 8 IP tn's.Try an EDD CLR, and then do and INI.What are you using the dn 7336 for, the pos id or the scn key?You might also need new Patches if you are first introducing IP to the PBX.

 

[PBXT3CH]

7336, used to be the SCR of the SUPERVISOR's phone; 87336 was the SUP's agent ID all of the agents are assigned to.

IP was already a part of the PBX, they just needed addtional user licences.

thanks,
-pt.

 

[sporty2]

Can you prt your SLT in LD 22.

sporty2

 

[TAnselm]

They didnt use 8733 as a DN did they???
That would be a conflict with the agent ID as opposed to the private dn. Either way the switch would balk.