Teleco4321
Programmer
Just to let everyone know there is a new service pack for Avaya IP Office 11.0 Feature Pack 4 on Avaya's support site.
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 Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Avaya IP Office 11.0 Feature Pack 4 Service Pack 1 2
- Thread starter Teleco4321
- Start date
- Status
Nortel4Ever
Vendor
That's nice but where in the hell is the 11.0.5 they've been promising for July delivery?
11.0 FP4 SP1 = 11.0.5
They just finally started naming them how they are supposed to.
They release a description about versioning a while back which I can't seem to find now, basically it's supposed to be
a.b.c.d.e
a = major release
b = minor release
c = feature pack
d = service pack
e = patch
Although, they might as well go change it in the next release.
"Trying is the first step to failure..." - Homer
They just finally started naming them how they are supposed to.
They release a description about versioning a while back which I can't seem to find now, basically it's supposed to be
a.b.c.d.e
a = major release
b = minor release
c = feature pack
d = service pack
e = patch
Although, they might as well go change it in the next release.
"Trying is the first step to failure..." - Homer
Nortel4Ever
Vendor
I looking for a fix for PSN005408u - the B169 licensing issue where this Avaya SIP device requires a third party license and won't work with a regular Avaya IP Client license.
I've read through the release notes for 11.0 FP4 and don't see a reference to a fix for this issue as was promised in PSN005408u.
I've read through the release notes for 11.0 FP4 and don't see a reference to a fix for this issue as was promised in PSN005408u.
Hopefully it is better than the 11.0.4 and looking at the tech bulletin they fixed a lot.
Still won't install it anywhere for at least 2 months
Don't feel like being the Avaya guinea pig
Joe W.
FHandw, ACSS (SME)
"This is the end of the world, make sure to buy your T-shirt before it is too late"
Original expression of my daughter
Still won't install it anywhere for at least 2 months
Don't feel like being the Avaya guinea pig
Joe W.
FHandw, ACSS (SME)
"This is the end of the world, make sure to buy your T-shirt before it is too late"
Original expression of my daughter
We run R11 SP4 on all customers since they finally fixed their SIP stack one year after I reported it, and it required me to bring in several partners and our dist before they even listened.
If service providers used letters in an custom field in the VIA header the IPO just ignored it.
"Trying is the first step to failure..." - Homer
If service providers used letters in an custom field in the VIA header the IPO just ignored it.
"Trying is the first step to failure..." - Homer
They are on the download page
[URL unfurl="true"]https://support.avaya.com/css/P8/documents/101060218[/url]
"Trying is the first step to failure..." - Homer
[URL unfurl="true"]https://support.avaya.com/css/P8/documents/101060218[/url]
"Trying is the first step to failure..." - Homer
Looking at the release notes, there are again some false informations in it regarding the version numbers which should be part of this release.
DECT Gateway is listed as 10.0.7, but included is 10.2.9. Well, this is not real problem.
WinPDM is listed as 3.12.0, but it is completely missing. However 3.13.2 is the one we need since long time (2 years?)
J100 SIP are listed as 4.0.0.0.21. And that's really what they deliver! There are several versions released since then. Last Wednesday 4.0.2.1 came out!
96x1 H.323 are listed as 6.8.0.02. And that's really what they deliver. Latest Release was 6.8.2.02
UC Module should also get an update, but there is no c110-*.iso.
It's not mentioned in the TB221, but I would expect the get updated package for Hyper-V as well, but there is no IpolCPEHyperV. Sounds like we are supposed to install the latest available and then upgrade it with the ISO?
I did not check every position, there could be more...
DECT Gateway is listed as 10.0.7, but included is 10.2.9. Well, this is not real problem.
WinPDM is listed as 3.12.0, but it is completely missing. However 3.13.2 is the one we need since long time (2 years?)
J100 SIP are listed as 4.0.0.0.21. And that's really what they deliver! There are several versions released since then. Last Wednesday 4.0.2.1 came out!
96x1 H.323 are listed as 6.8.0.02. And that's really what they deliver. Latest Release was 6.8.2.02
UC Module should also get an update, but there is no c110-*.iso.
It's not mentioned in the TB221, but I would expect the get updated package for Hyper-V as well, but there is no IpolCPEHyperV. Sounds like we are supposed to install the latest available and then upgrade it with the ISO?
I did not check every position, there could be more...
It is still early but has anyone successfully upgraded a server edition solution with expansion cabinets to this version yet? There are supposed to be some fixes so the expansions don't get stuck mid upgrade (which hasn't happened to me but I really don't want it to)
twitchy087
Vendor
We had a system with a random reboot issue on 11.0.4. This service pack fixed 6-8 DIFFERENT random reboot issues (really?!?!?). We successfully upgraded the system last night. It took 3 hours to do a primary SE, secondary SE and a 500v2 expansion. The expansion took the longest, as usual. We will see if they actually fixed our issue however I am not feeling good.
-
2
- #13
Nutritional_Info
Vendor
After upgrading to 11.0.4.1, we have noticed an intermittent issue so far when pressing the hold key then picking up a call appearance where SIP & IP Phones (no digital phones tested yet) will display acquiring service and terminate active calls on the extension. Hopping between the call appearances, skipping the hold key, has proved effective in avoiding this issue. Has anyone experienced something similar?
Nutritional_Info
Vendor
Nevermind... Appears to have been related to phone firmware 4.0.0.1.2. Manually uploaded firmware 4.0.2.1.3 and the issue hasn't been able to be recreated.
Did the upgrade on a server solution with expansion cabinets from 10.1.2 to 11 fp4 sp1
Could have been worse but there were some issues. All expansions gave message "upgrade failed--unknown cause"--however everything appears fine (the upgrade did complete as far as I can tell). One expansion oversees "failed to pull files"--that one I had to have someone recreate the SD card.
Tech bulletin 221 is wrong about what firmware comes with 11 FP4 SP1 : "9608, 9611, 9621, 9641 Phone Firmware – Application
6.6.6.04 (6.6) [change?:] No"
I was counting on this, however 9611 phones went to 6.8002 And the black label phones now have the "low volume on headset" issue even though this firmware was supposed to fix that.
Everything basically running ok other than those things.
Could have been worse but there were some issues. All expansions gave message "upgrade failed--unknown cause"--however everything appears fine (the upgrade did complete as far as I can tell). One expansion oversees "failed to pull files"--that one I had to have someone recreate the SD card.
Tech bulletin 221 is wrong about what firmware comes with 11 FP4 SP1 : "9608, 9611, 9621, 9641 Phone Firmware – Application
6.6.6.04 (6.6) [change?:] No"
I was counting on this, however 9611 phones went to 6.8002 And the black label phones now have the "low volume on headset" issue even though this firmware was supposed to fix that.
Everything basically running ok other than those things.
Sorry I should have said expansion systems, maybe using wrong terminology. The 500V2s that are part of the server solution.
Looks like the wrong firmware did load for the phones. Still trying to figure out why it is going to the older firmware 6.8002 when I have the 96x1Hupgrade.txt file and the new firmware files on there... Looking through the files I don't see where it says to update but still checking. did Avaya really send this release out with 6.8002 that has the headset problem or is something else going on (I mean it sure looks like it since no one put the files on manually--they were at 6.6604 previously...)
Looks like the wrong firmware did load for the phones. Still trying to figure out why it is going to the older firmware 6.8002 when I have the 96x1Hupgrade.txt file and the new firmware files on there... Looking through the files I don't see where it says to update but still checking. did Avaya really send this release out with 6.8002 that has the headset problem or is something else going on (I mean it sure looks like it since no one put the files on manually--they were at 6.6604 previously...)
On a server edition system with hundreds of 9611 phones on 6.6604, rebooting all phones (by powering them off at the switch) about 1/8 of phones load the 6.8202 firmware fine, 1/4 needed to be rebooted manually/individually to load it, about 1/4 won't load the firmware (but I haven't manually rebooted them yet by pulling the plug), and 3/8 get the firmware (as best we can tell) and also come up looking for a vpn address. Once vpn turned off manually they are fine. I haven't been able to duplicate this vpn behavior on a test system yet. Anyone else seen that? 46xxsettings.txt is autogenerated and the specials file doesn't have any vpn settings. Also got GRQ --- RAS reaches the max capacity of 60 error when I tried resetting the ip office service to reset phones ( sounds a bit like ) but I don't have any legacy adi licenses on the system (one PLDS license is now obsolete). So could be two issues here, one is phones not updating from the server edition (I haven't tried with separate http server yet) and the other is some phones coming up with vpn turned on (which disables the phone until it is turned off in the admin menu). Let me know if anyone else experiences these. Has been ok on our cloud server upgrades (but those aren't using 9611G).
- Status
Similar threads
- Locked
- Helpful tip
- Locked
- News