unable to delete Avaya extension from ASA/CM

[Avaya Naresh]

Dear All,

We are facing the issue with to remove the extension from CM. we are getting the error object in use . we busy out and release the station but no good luck. we checked also though list usage station and list usage digit-string, off set pbx station mapping but there is no benefits.. any one can suggest here

 

[ZeroZeroOne]

There should be an error message at the bottom of the screen when you try to delete a station in the terminal (ASA). Some of the more common errors are:

Bridged appearances must be removed before removal

Run List Usage ext xxxx to find any bridged-appearances of this station and remove them from all other stations.​

Run Change station xxxx and remove any bridged appearances.​

Cannot change/remove extension; remove from Intra-Switch CDR form first

run change intra-switch-cdr xxxx and remove the station from the form​

Extension must be removed from Off-pbx-telephone station-mapping first

run change off-pbx-telephone station-mapping xxxx and remove any entries for the station​

Message(s) waiting; please delete message(s) first

run clear amw all xxxx to remove the message indicator​

Object in use.

Someone is actually using the phone. This is a good indicator that maybe you should NOT remove the station. ​

I suggest looking at bridged appearances. It could be that there's a button somewhere that is showing activity.

 

[AvayaTier3]

This is a pbx extension line status hung issue.

Without a reset on CM, this would only be correctable by calling Avaya and
having a software corruption engineer write out extension line status in CM software tables.

Command: save translation
Command: reset system 2 or higher will reset system status and most likely allow removal of your station.
This is service affecting so notify users of service interruption to occur.

A great teacher does not provide answers, but methods to teach others "How and where to find the answers"

bsh

49 years Bell, AT&T, Lucent, Avaya
Tier 3 for 39 years and counting
[URL unfurl="true"]http://bshtele.com[/url]

 

[Avaya Naresh]

@Avaya Tier3... I am understand reset system 2 here. Could you please elaborate

 

[AvayaTier3]

reset system 2 or higher will stop and start call processing and this will drop calls. Within a minute, users can go off-hook and get dialtone again.


A great teacher does not provide answers, but methods to teach others "How and where to find the answers"

bsh

49 years Bell, AT&T, Lucent, Avaya
Tier 3 for 39 years and counting
[URL unfurl="true"]http://bshtele.com[/url]

 

[techdgrubbs]

I had this problem when I first started working with this phone system blindly. Avaya kept saying the object was corrupted. ZeroZeroOne is right, first make sure it's not bridged or appearing, or forwarded etc. Once all that, then look up your number in System Mgr, then turn off the two sliders for Session Manager Profile and CM endpoint profile, then delete the entry. Then you have to delete the " soft deleted" entry and you're done. It's a pain, but this prevents corruption. At least, that's my experience. Hope it helps.