Avaya ip500 help 2

[steveo242]

I recently.took a job for an avaya ip500 that the office reported 25 lines down. They shipped a new control unit and expansion module. I replaced both, and transfered the sd card. I know the expansion module must be booted first to be recognized, after booting, the control module flashes healthy led's. The expansion module flashes red on the Middle led. From what I read that means it is trying to load firmware but never gets it. I can connect to the system with a static IP but when I try the default password it says. No response on that TCP port. The port seems correct 5xx08. I used putty for a serial connection and reset the admin password with the AT-SECURITYRESETALL command then entered the mac address and got the OK. Still a
Can't logon with the GUI. It keeps on saying no response. As it sits, some phones work but you cannot dial in, but on the phones that work you can dial out. Any guidance would be appreciated to diagnose the system. If I. An get the GUI working im sure it would.be much easier to diagnose and fix. Again, any help would be appreciated...

 

[Swiney52]

I think the first step would be to install Manager and try accessing using that instead of Web manager.
What version is the IPO?

 

[steveo242]

Yeah that's good advice. I have been reading the documentation all day and have a list of things to.check.on when I get back over there. Turns out I had the wrong kind of cable connected for my terminal session, i was using a cisco blue with a db9 to usbA.So thats probably the issue with getting a no response. I am going to connect via the web manager off the office network and test the reset passwords first. Hopefully get a system status done to identify the problem(s). Then Install office manager on my pc like you suggested. I will then check.the compatibility of all hardware with each other and make sure the software versions are the same, then make plans to correct the errors. I will definitely be asking for more help when I get the system status done on Tuesday.

Thanks for your reply

 

[derfloh]

Did you ever work with IP Office? Doesn’t sound so. You should contact a business partner.

 

[john3voltas]

There's no need to start the expansion module first and the IP500 later.
They can both be started at the same time. Since the IP500 will take longer to boot up, the expansion module will be up and running when the IP500 goes trying to find it.
So, booting at the same time is ok. But you did good to double-check booting the IP500 later than the expansion module.
I'd look at SysMonitor and/or System Status Application.
And if all that would fail, I'd hookup a Serial cable from the PC to the Expansion Module and have it boot up while monitoring it via PuTTY. Do that with both the serial cable hooked up to the EM and later do the same with the serial connected to the IP500.
Maybe you can see something coming up on the console that can explain why the EM stays offline.
Cheers

 

[john3voltas]

Also, if you type AT and press enter, the console respond with OK.
That's how you would prove that the serial connection is ok.
Make sure you set the flow control to None. PuTTY defaults that to XON/XOFF. You need it to be None.

 

[snowman50]

Since you have already plugged in a wrong cable for management.
Have you connected the expansion unit with the correct cable supplied and into port 1 at the rear of the ipo control unit..for the expansion units.

 

[skylerdodson]

It sounds like you're dealing with a tricky setup.

• Verify the firmware version on the SD card matches what the system expects. If there's a mismatch, the control unit might not be able to properly communicate with the expansion module. Use Avaya Manager to update/reload the firmware.
• Ensure the expansion module powers up before the control unit. If it's already doing that, try re-seating the connections and rebooting the devices in the proper sequence again.
• Double-check the static IP settings, including the subnet mask and gateway. Ensure the control unit and your PC are on the same network.
• Even after resetting the admin password, confirm that you're connecting using the correct credentials and port (default is 50705 for IP Office Manager, not 5xx08).
• The fact that some phones work but you can't dial in could suggest an issue with the line configurations. Check the trunks' status and configuration once you regain GUI access.

If the GUI still won’t connect, you might need to reformat and recreate the SD card using Avaya’s utility.

 

[teletechman]

I have found you can't use the GUI until you have logged in via the Manager program and it will ask you to change the passwords then you can use the GUI.
Mike