I've seen similar problems, but could not find a solution that fits this one: I have a IP406 phone system and was adding a new IP500 Phone 16. While performing the upgrade to 5.0 (69) from 4.2 (?), the upgrade failed and now all I get is a red light on the expansion module. The IP406 will not detect the module anymore. Is it possible to restore the expansion module to its original state?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
IP 500 Expansion Module
- Thread starter Protokyll
- Start date
this might be useful
Never argue with an idiot. bystanders won't be able to tell the difference.
Never argue with an idiot. bystanders won't be able to tell the difference.
- Thread starter
- #3
intrigrant
Systems Engineer
Open Manager
Go to File > Off line > create config.
Follow thge wizerd and don't forget to add the module
Send the just created config to a IP Office
Wait till it has fully rebooted
read out the config
power down
add module
turn on both the IPO and the module
The unit should get the firmware through manager ( if your working dir is ok )
If not then follow the path to the last resort:
connect a serial cable to the back of the expansion module
open hyperterminal 38400,8,N,1 and type AT-X
Pray and hope it works, sometimes is does and many times it does not and then you have a bricked module ready to ship to Avaya repair centre
then
Go to File > Off line > create config.
Follow thge wizerd and don't forget to add the module
Send the just created config to a IP Office
Wait till it has fully rebooted
read out the config
power down
add module
turn on both the IPO and the module
The unit should get the firmware through manager ( if your working dir is ok )
If not then follow the path to the last resort:
connect a serial cable to the back of the expansion module
open hyperterminal 38400,8,N,1 and type AT-X
Pray and hope it works, sometimes is does and many times it does not and then you have a bricked module ready to ship to Avaya repair centre
then
- Thread starter
- #5
I ended up going through the hyperterminal with the AT-X and it works perfectly! It even had the proper version so I didn't have to perform the upgrade. That way seemed so much easier. Is it not recommended to go that route instead of the upgrade route?
You should use the normal upgrade path
Using the serial cable is not the normal way !
ACS - Implement IP Office
ACA - Implement IP Telephony -- ACA - Design IP Telephony
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!
Using the serial cable is not the normal way !
ACS - Implement IP Office
ACA - Implement IP Telephony -- ACA - Design IP Telephony
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!
- Thread starter
- #7
Maybe the file did not pass correctly ?
I never had this problem myself to be honest
ACS - Implement IP Office
ACA - Implement IP Telephony -- ACA - Design IP Telephony
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!
I never had this problem myself to be honest
ACS - Implement IP Office
ACA - Implement IP Telephony -- ACA - Design IP Telephony
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!
Same thing happened to me yesterday, but the expansion got bricked. I don't have a better answer other than "sometimes it just happens." There's no rhyme or reason to why it happened, for me anyways.. had to get a replacement, as I got no response from the module from DTE port.
- Status
Similar threads
- Question
