How do you de-acquire a TN (SCH1509)? 3

[AFWireDawg]

I have a TN that was programmed in LD 11 as type: OOSMLT. When I try to out the TN to restore it I get an SCH1509. How do I de-acquire a TN? See below:
REQ: out

TYPE: oosmlt

TN 36 0 0 2

SCH1509

REQ: !err sch1509

>
>

SCH1509
Cannot MOV/OUT acquired TN. First De-acquire the TN and then proceed
with MOV/OUT request
Action: De-acquire the TN and then proceed with MOV/OUT operation.
Severity: Minor

 

[GHTROUT]

The command line method is:

LD48
.DACR AGT 36 0 0 2

However, in most cases, it's done from Symposium.

Since your TN is an OOS TN, you might have more of a problem. In your case, I would do the LD48 method - for this particular TN.

[©] GHTROUT.com [⇔] A Variety of Free Resources for Nortel Meridian/CS1000 System Administrators

 

[AFWireDawg]

GHTROUT,
Thanks for your input,but it didn't work. Here is a little back ground on the OOS TN. Whenever a unit is bad I program the TN as OOSMLT so it won't be counted as an unused voice unit. I was finally able to get a new replacement card for the card that had 4 bad units. Now I am trying to put the 4 OOSMLT units back in service but I keep getting the SCH1509 error. I think you may be right: "might be more of a problem".

 

[bigindian65]

The problem might be putting them in OOSMLT without de-acquiring them in the first place.

Mato' Was'aka

 

[GHTROUT]

Some release systems could not deal with OOS TNs. I've seen many systems require a reload in order to get them back.

It's odd. It lets you "make them" OOSMLT, but it won't let you OUT them once they are fixed.

[©] GHTROUT.com [⇔] A Variety of Free Resources for Nortel Meridian/CS1000 System Administrators

 

[AFWireDawg]

Thanks GHTROUT and bigindian65,
I won't use OOSMLT anymore. Bigindian65, I sure do wish the manual would have mentioned de-acquire before doing OOSMLT, it might have saved me a lot of grief. All you can do is 8^) and move on...

 

[bigindian65]

yes sir, sucks. but, wo't happen to you again right. Use to get beat down on MAX because a ACD queue wouldn't report but somewhere a agent was still coded on key 0 keeping me from outting anything. Couple of those trips and yeah, lesson learned. I don't know anyone who can't say we've all been there in one form or another. Good luck

Mato' Was'aka

 

[telebub]

This is a known problem. You need patch MPLR19479. Below is the Knowledge Base solution for this issue:

Problem Description

Fact:
Succession 3.0
CPP
Unit types are not acquired as they are not telephones but are used as Out of Service Multi Line Telephone or Out of Service Single Line Telephone.


Symptom:
Unable to remove Out of Service Multi Line Telephone (OOSMLT)
Cannot free up the TNs to be re-programmed as digital sets such as M2616.
Cannot remove OOSMLT or OOSSLT units in LD 11 or LD 10
SCH1509: Cannot MOV/OUT acquired TN. First De-acquire the TN and then proceed with MOV/OUT request
Action: De-acquire the TN and then proceed with MOV/OUT operation.
Severity: Minor. Critical to Monitor: No. SNMP trap: No


Problem Resolution

Fix:
Install Mplr19479.
Remove OOSMLT or OOSSLT units in LD 11 or LD 10.


War Eagle!
Lions Baseball '09!

 

[AFWireDawg]

Thanks telebub, I will get with management and see if we can get the patch.

 

[AFWireDawg]

Hey telebub, we got the patch update and the TNs work like a champ. Thanks for the assist!