Possible Corrupt Extn 2

[JaeP2R]

Avaya
Using ASA 6.0
-
Did a batch change on a series of extensions, just updating the coverage path and voicemail number.
All but 2 extensions were changed successfully - when we went to update the two 'failed' extensions - by changing the coverage path, we are seeing the following error:

"Button type is not allowed on this station type of module"

It is not possible to remove or alter this extension at all.
I am able to call the number and talk with the user.
We can unplug the device and 'see' that it is disconnected from the network
Plugged back in - but still unable to make those changes.

How can we resolve this problem?
Is there a way to change the phone login password via the TUI? Just wondering ...
-----
Jae

 

[JaeP2R]

@AvayaTier3
-
Using terminal - I left all things as they were - then on page 1 under the Button Module I attempted to change that to 3
I submitted and received the same error as previously.

I then, using another extension added the additional modules
in the 1st space I added as a bridged appearance

Here is the list usage image

I was not able to alter the extension 33853

 

[AvayaTier3]

Command: change extension 33853

This will allow changing to another extension. (change information on the form to a different unassigned number)
Then you could do add station 33853

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

bsh

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

 

[AvayaTier3]

change extension-station 33853                                  Page   1 of   1

                              CHANGE STATION EXTENSION

          Station Name: Test Change Extension          Port: 02A0304

                     FROM EXTENSION               TO EXTENSION
                     --------------               ------------
                       Station: 33853             12345
                  Message Lamp: 33853             12345
        Emergency Location Ext: 33853             12345

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

bsh

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

 

[JaeP2R]

Thank you - I will do this, as I was not able to understand exactly what you were saying ..
I will provide screenshots
------
Jae

 

[JaeP2R]

@AvayaTier3
-
Thank you again for so much of your help.
Unfortunately that 'change extension-station" command did work - but the problem moved with it ...
-
We have asked to escalate the issue ... but the process is slow ...
-
I can't thank you all enough for what I was able to test to this point.
-----
Jae

 

[AvayaTier3]

This sounds like a bug or software corruption in CM related to the station.
This can be resolved by an Avaya software corruption engineer.

The work-around was meant to allow you to change a station so you could use it
without administration blockage. Moving it to a different software record was
how I chose to help you. The change extension number used, if not in your blocks of
used stations is a minimal issue which really does not need resolution.

I have done Avaya Software corruption work for years. This is easy to resolve
and would take under an hour. If you are escalating to someone besides Avaya, or to
Avaya group that is not trained, it will never be fixed. Click my signature link if
you need help.

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

bsh

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

 

[JaeP2R]

@AvayaTier3
-
Yes sir! Exactly ...
I have reached out to the Avaya Corruption team - and am hoping to get some assistance, hopefully today.
Just stepping through the processes - just means it takes a bit to 'get on the list'
-
I, and the customer appreciate the work around - that worked perfectly - and she is up and running, as are the others.
Again, I am very, VERY appreciative of all you have done.
-----
Jae