error message when deleting a station

[speechguy]

Has anyone seen the error message " Must have normal button for display module" when deleting a station?

This is on a G3si v2.0 and the stations is an 8434D.

History log shows,
HISTORY
Date of Loaded Translation: 5:54pm Fri Nov 12, 2004

Date Time Port Login Actn Object Qualifier

6/13 16:50 IP avaya cha station 4500 NOROOM: -10035



thanks

 

[donbott]

The history report shows change station, not delete station. I've seen messages like "must have normal button for display..." often when changing from one type of phone to another. Could there be software corruption? I have a station I can't remove that has a button for attendent q-calls, and we never have had a attendent console programmed.

DonBott

 

[speechguy]

It is strange but it is when I try to delete the stations..

remove station 4500 Page 1 of 5
STATION

Extension: 4500 Lock Messages? n BCC: 0
Type: 8434D Security Code: TN: 1
Port: 01A0714 Coverage Path 1: COR: 1
Name: One-Ugly Coverage Path 2: COS: 1
Hunt-to Station:

STATION OPTIONS
Loss Group: 2 Personalized Ringing Pattern: 1
Data Module? n Message Lamp Ext: 4500
Speakerphone: 2-way Mute Button Enabled? y
Display Language: english Expansion Module? n

Media Complex Ext:
IP SoftPhone? n
Remote Office Phone? n




Must have normal button for display module- is the response


If I try to change the type an error message sya there is "not enough space".

Should I assume the translation card is faulty?

 

[noisecode]

Have you tried adding a normal button before deleting the station?

 

[mikeydidit]

It sounds like you do have some sort of software corruption going on. This station may have been a 7400 series phone at one time (which needs a normal button) and something in the software has you hosed up. I would try to change the set type to a 7444 add the normal button and see if it will let you remove it. If that doesn't work you may have to do a "reset system 1" and then see if it will let you remove it. I had something like this years a ago that liked to have drove me nuts just trying to remove some abridged appearances. I did the reset system 1 and the software was so hosed up that the system escalated the reset to a reset system 2. Then it finally let me remove the appearances. Oh and one more thing. Please give my deepest sympathies to the user of this phone if the name field is any reflection on them…….



Mike Jones
Louisiana State University Health Sciences center

 

[speechguy]

Hoseage!

Mike, I rebooted, than changed One-Ugly to a 7444 and gave it a normal button. Then deleted it. And now it is gone.

Now that was Ugly! This is the first time I have had to reboot this system to solve a problem.

I'm curious, how often do you find strange problems that requires the Avaya to be reset?

p.s. One-Ugly is only a test machine in my R&D lab. It's an inside joke.

I have a few Cisco Call Managers (4.0.1) here too and I haven't found a need to reboot them contrary to popular belief.

thanks

 

[DAVIDPAYNE]

We just upgraded to S8700, but on the old G3si. I had to reboot it once in 4 years do to the modem getting hung up.
But of 12 years working with AT&T/Lucent/Avaya PBX's i can not think of many times that I had to reboot.

 

[mikeydidit]

I have only had to reboot on two occasions in 12 years speechguy. Once that I mentioned to you in an earlier post and once when our CO cut over to some new equipment for our PRI service. Our PRI's were down for 3 days until one old field engineer came out from Avaya. He hooked up a protocol analyzer, you name it and then said, " Ok reset system 4". It sounded pretty bad but when it got through rebooting, they came back up just fine.

Glad that got your problems fixed.

Mike Jones
Louisiana State University Health Sciences center

 

[speechguy]

Mike, that reminds me of another problem I had years ago when I was in Tier 4 at Lucent/Octel.

I was managing betas for the roll out of QSIG for the Octel Serenade. One of out customers in Ohio on a G3R was having problems with some PRI's for the main 800 number.

We sent a few field engineers to site with a protocol analyzer. Signals were fine to the G3r but the switch was not handling any messages. My tier 4 bud in the green room did reset 4 and Bada-boom-Bada-bing service was restored.

So.."stuff happens" ;-)

thanks