R9.1 SP10 Release 2

[edlee321]

Anyone tested the R9.1 SP10, below are the release notes, seams like a smaller revision than previous SP

The following field issues have been addressed in IP Office Core and Manager:
JIRA Number Description of Issue
IPOFFICE-116577 Missed Call Log is not working in 9.1.9
IPOFFICE-116227 SMDR field position unexpectedly changed for calls routed to VM Module
IPOFFICE-115841 Avaya Communicator for Windows does not show call log entries
IPOFFICE-115110 Mobile Twinning feature on locked deskphone doesn't work
IPOFFICE-114967 Softconsole shows busy on a call to a logged off user
IPOFFICE-114947 Two popup call alerts for incoming calls to Avaya Communicator for Windows
IPOFFICE-114009 ACW client utilizes multiple sessions with one-X Portal during registration, which results unable to
login to all the ACW users simultaneously
IPOFFICE-113969 System Restart 500v2: 9.1.6 - buffer leak
IPOFFICE-113682 System Restart - IP500V2 9.1.6.0 reboot probably caused by memory leak
IPOFFICE-113387 Using SoftConsole (9.1.8) search is slow to find a record with matching name
IPOFFICE113366 Intermittent one way speech between one-X Mobile and Avaya Communicator
IPOFFICE-112216 Voicemail to Email changes not persistent for Longest Waiting Group in 9.1.300.120 configuration
file
IPOFFICE-111994 VMPro Alarms are intermittently not alerting
IPOFFICE-51741 Ringback Issues when using Account Codes
IPOFFICE-114833 SSA intermittently fails to login – User has insufficient access rights error message
IPOFFICE-113045 Remote hunt group information not displayed in SoftConsole directory panel

3.2 Voicemail Pro (Preferred Edition) 9.1.10.0.9 – Resolved field issues

The following field issues have been addressed in this release of Preferred
Edition (VoiceMail Pro):
JIRA Number Description of Issue
IPOFFICE-117663 VMPro 9.1.800.9 Outcalling : Escalation list is completed only once
IPOFFICE-116610 VMPro outcalling does not work if you are using a VMPro Time Profile
IPOFFICE-114457 Clock Widget is NOT giving time w.r.t. to the timezone set in the IPO BUT is reporting based on the
location of the centralised VMPro
IPOFFICE-113064 Visual Voice will intermittently play the same hunt group voicemail message when the Primary VM
is failed over to the Secondary VM
IPOFFICE-113020 Server Edition 9.1.8 : VMPro resets daily with segmentation violation
IPOFFICE-111751 Dual VMPro 9.1.7 sends out duplicate emails
IPOFFICE-115610 VMPro outcalling does not work if you are using a VMPro Time profile
IPOFFICE-110491 Intermittently VMPro menu not recognizing DTMF on PRI calls
4
Global IP Office Technical Bulletin Number 203

3.3 one-X Portal 9.1.10.0.5 – Resolved field issues

The following field issues have been addressed in this release of one-X Portal:
JIRA Number Description of Issue
IPOFFICE-114832 HG Queue Monitor in one-X Portal Agent-desktop continues to show a call in-waiting state when that
was already answered
IPOFFICE-113389 One-X Portal is not sending emails for Conferences to users under Personal tab
IPOFFICE-115270 External call retrieved from park slot using 1XP co ntrolling a DECT phone shows as ringing on 1XP
whilst actually connected to the handset.

3.4 Server Edition 9.1.10.0.192 – Resolved field issues

The following field issues have been addressed in this release of Server Edition:
JIRA Number Description of Issue
IPOFFICE-118083 System restart – Server Edition 9.1.9
IPOFFICE-115202 Licences renewing only after reboot–PoweredByIPOffice OSS WebLM
IPOFFICE-113984 System Restart SE: 9.1.6.19 Segmentation violation
IPOFFICE-113773 Web Manager: User rights modifications cannot be updated
IPOFFICE-113197 Primary Server restarting VMPro service with Segmentation violation when EWS is enabled
IPOFFICE-112687 LDAP User Synch job still runs daily after deletion
IPOFFICE-112414 System Restart SE – 9.1.600 Build 153. Restart
IPOFFICE-112315 Resilience : Secondary IPO fails to connect to Voicemail on failover
IPOFFICE-112310 Web Manager changes in Log Missed Hunt Group Calls for User does not work
IPOFFICE-110031 New service user experiences HTTP request failed: 401 Unauthorized
IPOFFICE-115726 SSA Alarm continues to show additional hard drive removed even though CR functioning normally
IPOFFICE-114251 Sysatem Restart following a TAPI call from ACW to a group containing an unavailable DECT
handset
IPOFFICE-113970 Server Edition SMDR outpout incorrect for call forwarded externally via Expansion system
IPOFFICE-112683 Server Edition – incorrect call direction shown in expansion system SMDR record in conference
scenario
IPOFFICE-112423 DECT_REVERSEW NoUser source code not working correctly in 9.1
This release of IP Office Server Edition consists of IP Office core software
9.1.10.0.192, Preferred Edition (VoiceMail Pro) 9.1.10.0.9, one-X Portal 9.1.10.0.
Any field related fixes in these releases will also be incorporated into this release
of Server Edition.

3.6 Branch 9.1.10.0.192 – Resolved field issues
JIRA Number Description of Issue
IPOFFICE-114335 System Manager will not synchronize with IP Office

 

[IPGuru]

Seems this release will not install on windows XP - aagghh


Do things on the cheap & it will cost you dear

 

[tlpeter]

and it shouldn't as it is not supported for a long time now.


BAZINGA!

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

 

[Okkie26]

To bad for one description on an issue I raised.

IPOFFICE-114967 Softconsole shows busy on a call to a logged off user

This is not the correct desription.

Issue was that when the receptionist is using the sofconsole in combunation with the ACW, the softconsole freezes when a call is made to a logged off user.

But this is solved in this release. Just tested this.

 

[Pepp77]

IPOFFICE-116577 Missed Call Log is not working in 9.1.9

Description for that is also wrong - it should be missed calls answered at coverage not showing in missed calls list.

| ACSS SME |

 

[edlee321]

as long as these gets fixed, i am not so concerned about their descriptions, but it is funny how they cant detail things correctly.

 

[Westi]

The problem is that you are looking for a solution to an issue you may have and can't see the resolution in an upgrade so you won't spend the time upgrading and rather create a new ticket.

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

 

[edlee321]

you are correct, didnt think about that

 

[derfloh]

In my opinion worst is that there is no list with known issues (along with workarounds and solution target) and the list of solved issues within the release notes is only part of all solved issues. So you never know what is solved, what is known and when can we expect an issue to be solved.

More transparency would be a win-win situation. We wouldn't have to waste time opening tickets for known issues and support wouldn't waste time to answer those tickets.

 

[piercej2010]

Just took the plunge with this version. I have issues with the Save Configuration As feature.

The Manager software will perform the save with the filename specified to the destination specified but then this error appears:

"C:\Program Files (x86)\Avaya\IP Office\Manager\[name].cfg" is a version
9.2 configuration
which is not supported by this version of Manager

A file will be created with the file name specified in my desired destination, however when I try to open that .cfg file with the Offline menu I get the same error as above.

I've tried saving to different destinations, with the same result. I've tried saving as the suggested filename, and also changing the file name, with the same result. I've tried with and without a password with the same result. I've tried from a Windows 7 PC and a Windows 8.1 laptop with the same result.

Also, when Manager preferences are configured to "Save Configuration File After Load" and "Backup Files on Send" it does create .cfg files in the Manger folder. When I try to open those files I get the same error as above.

I just noticed this today and haven't had a chance to do some proper trouble shooting, so I have no ideas to add as to why or how or if I'm doing something wrong.

Good luck out there.

 

[Ivan917]

I get the same error. Upgraded our system on Monday. Nice work Avaya! I see a downgrade to SP 9 happening tomorrow.

 

[piercej2010]

Off the wall guess: some part of the Manager application falls down when it sees two digits in the minor release field.
For example: 9.1.9 had a single digit in the minor release field. 9.1.10 has two digits in the minor release field.
I can open configurations and make changes just fine, so it would be something to do with the file save and offline file open process.
I don't have the technical wherewithall to even know how prove this. Just a guess.

 

[Pepp77]

Tried an R10 manager?

| ACSS SME |

 

[piercej2010]

@Pepp77
I have not. Only 9.1.10

 

[edlee321]

I confirm same error with 9.1 SP10 installed on Windows 10 x64

How many people test these builds before release you think?

 

[critchey]

I created an offline config with 9.1.10 and saved it same issue as reported(it errors second you save it and fails to re-open it as usual). Opened with 10.0.3 which does work. Control unit is reported as version 9.2.0.0 build 192 but a combo card I added was 9.1.10.0 build 192.

 

[Ivan917]

Used 10.0 sp3 to open a 9.1 sp10 saved file, no problem. Shows control unit, combo card, PRI, and DS 8 as 9.1.10.0 build 192. Used 9.1 sp 10 to pull config from control unit, shows control unit and all cards as 9.1.1000.192. Used 10.0 sp3 to "save config as" and tried to open saved config with 9.1 sp 10, same error. 9.1 sp10 can open saved configs from 4.0 - 9.1 sp 9. So it appears the only config files it can't open are 9.1 sp10. Windows 10 64 bit.

 

[derfloh]

Did they replace the full help file with a basic edition help file in the latest R9.1 Manager too? In R10 I only have basic edition help...

 

[Greybeard191]

just want to add that I see the same issue WRT 9.1.10 SP10 Manager.

Config created or saved from an IP office running this release cannot be properly saved. Nor can it ever be reopened using 9.1.10 manager. If opened with R10 Manager, the IP500V2 under control unit reports as 9.2.0.0 Build 192, while all the cards report as 9.1.10.0 Build 192. Given that evident corruption, I wouldn't trust it.

If you are in the habit of working on offline configs, this build is unusable, particularly given some of the issues that have shown up around using R10 manager to manipulate earlier releases... reports of config corruption etc.

GB

 

[IPid10t]

I have found a workaround to get a backup config of a 9.1.10 system. go to File>Import/Export then just export the configuration then uninstall manager 9.1.10 and install release 9.1.9 (I haven't tried in another release but I'm sure it would work)then go to File>Offline>Create new configuration after the offline config is created do File>Import/Export and import the configuration.csv file and save. Once you do this you will have a working offline configuration that still shows as 9.1.10 release.