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!

V7 &V8 bug confirmed with over 254 ip extensions 1

Status
Not open for further replies.

Fuzziedunlop

Programmer
Jul 3, 2012
8
GB
Thought it let you guys know yesterday I had confirmation from Avaya that if you have more than 254 ip extensions connected to the ip500 they will randomly reset and reconnect. And the bug has been found in V7 as well. Ive been told I will have a bug fix by next week.
 
There is a tech bulletin about it somewhere, I read it a couple of days ago, but they specified over 255 in that doc :)

 
Or are you on R8 :)

 
I think he is because he says it is in R7 too :)

BAZINGA!

I'm not insane, my mother had me tested!

 
I'm on 8.0(44) already and require a patch which I should get next week. When your on or over 255 ip extension and you move or reregister extension you find either around 60 extensions or all of them reset on urq and log back on. But it doesn't happen every time. It does it when it feels like it. I've unplugged a few to 249 and it's stable. So much 300+ extensions at the moment!
 
The 384 limit is based on the physical port limit of the system, you can actually put over 500 IP users on one system (at least you could in earlier releases) :)

 
Is unsupported of course :)

 
I'd just settle for 270 extensions working right now! This could of damaged 4 new other sites and scn'ing them all up with this one.
 
It's a silly issue, obviously something to with internal addressing of some sort as the figure 255 is too much of a coincidence :)

 
Did anyone obtain a fix for this problem? One of my customers just manage to go over 254 (when they shouldn't have according to my calculations) and now all hell broke loose :)
 
Just received 8.0(443102) from Avaya :)
 
I wonder if it also is a issue on 6.1 since this very thing happens.

 
Hi the fault is on 6.1 as well, i was told that as i was looking to find a stable version of software and thats when i was advised how far back the fault went, i was on version 8 and had to downgrade to Version 7.0(36) and its been stable. i've gone up to 277, 1600 series handsets with no problems. I do have a version 8 fix but i didn't try it(customer just wanted it fixed and had had enough by this point) and i havn't checked if thats an issue in 8.1?
Hope this helps.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top