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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

POTS30 v2 does not communicate with IPO 500v2 all of the sudden

Status
Not open for further replies.

tpit

MIS
Aug 5, 2011
53
NL
We have a brand new IP Office 500v2 installation running 7.0.27. We also have a Phone 30 module running 9.0.27 firmware. During testphase the Phone 30 was working perfectly normal. After racking it in our customers rack, it does not comminicate with the IPO any longer.

What have we done? We have tried multiple interconnect expansion cables, created our own, we have first booted the Phone 30 module prior to booting the IPO 500v2.

We have also tested the unit on another IPO 500v2 running the SAME software. 7.0.27. This time, the phone30 module emmediately worked. Thus we thought that it might be the control unit of the IPO 500v2. Thus we switched our IPO 500v2 control unit with the clients one. However, now the Phone 30 module also does not communicate with the IPO. What could have happened? Is our SD Card defective in such a way it only affects the Phone 30 module? This riddles me...

Any help is greatly appreciated. A case with Avaya has already been logged, but this forum has been proven to be just as effective as Avaya support.

______________________________________________
VoiceByte - Networking & Telephony
watchguard | cisco | avaya | aastra | nortel
w: voicebyte.nl | e: tpit [at] voicebyte.nl
 
Have you rechecked your cable? also try a software reload or upload. I am might sound inconsistent but that might help, surely from your steps, there is nothing wrong with equipment, maybe use same cables as from your lab.
 
Hey 7deedtz,

I tried different cables and also made a new one. Did not help. It might be a license problem however. Also reloading software is an option, however, since it has worked before I best do this as a last resort. Since it will be a lot of downtime! ;)

Regards,
Tommie

______________________________________________
VoiceByte - Networking & Telephony
watchguard | cisco | avaya | aastra | nortel
w: voicebyte.nl | e: tpit [at] voicebyte.nl
 
Th interconnect cable MUST be a CAT5 shielded cable with a max length of 1 meter.
Any other type of cable gives the problem you encounter, if the cable is OK then check the power supply, if that is OK replace the box.

If it ain't dutch it ain't much
 
While this is a brand new install, is it brand new equipment? Did you load it with the small site upgrade licence? :)

 
Hey all,

This box works on another IPO 500v2 with same software load. It also worked before on the same IPO during test phase. This almost 100% concludes it must be something else to look for! ;) The cables that we used are from Avaya itself. And the powersupply functions properly with the same box on another IPO.

Equipements is also brand new and has been working before on this IPO.

:)

Regards,
TOmmie

______________________________________________
VoiceByte - Networking & Telephony
watchguard | cisco | avaya | aastra | nortel
w: voicebyte.nl | e: tpit [at] voicebyte.nl
 
we have seen this a few times where the module will just drop off and then all of a sudden come back. I have also seen them try to keep upgrading the modules. sometimes leaving it plugged in for a while will bring it back. I have also had some guys plug them in while the IPO was already running and then reboot to see if they connect. Not sure i would do that but i know it has worked in the past.

Kevin Wing
ACSS Small and Medium Enterprise (SME) Communications
ACS- Implement IP Office
ACA- Implement IP Office
Carousel Industries
 
True, hey but have you also tried a different config file? Maybe try the equipment back at your office again. seems you have hardware and or software issues. what CAT5 shielded length are you using?
 
I would first look at licenece errors as amriddle suggested , if indeed you have the small upgrade licence or the licence has somehow corrupted you are waisting your time(confirm by running monitor and tick licencing on the system tab), if you are happy licences are not the issue try putting the expansion unit into a different expansion port and reboot.

Recreating the sd card is not as much down time as you think , the IPO will run without the SD card present so if the above fails format/recreate the sd put it back in the unit and try the steps you did originally as that is the correct procedure to follow.

APSS (SME)
ACSS (SME)
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top