2.0 (18)

[SPIPOffice]

Does anybody have a list of what was fixed is 2.0.(18)?

 

[IPOJedi]

Most of what Avaya £#*ked up in 2.0(16).....this can be found from Tech bulliten no 22 avaialable from

http://www.avaya.com

website...here is a brief look..However having spokern to Avaya they only list about a 1/3 of the fix's



Avaya is pleased to announce the availability of IP Office 2.0(18) Software. This is a
scheduled maintenance release including additional functionality and addressing a
number of identified field issues found in the IP Office 2.0 release.
This maintenance release incorporates new software and CDs for Voicemail Pro 2.0(17),
User applications 2.0(14), and CCC 4.0(25).
IP Office 2.0(18) should be used for all new installations and upgrades. The IP Office
2.0(18) software and associated applications can be downloaded from the Avaya Support
Website:

http://support.avaya.com

This software is for use with the IP Office IP401, IP403, IP406, IP412 and the IP Office
Small Office Edition.
The Support Centre web site can be navigated in several ways. If you are unfamiliar with
the site, try the following:
•
•
•
•
•
•
Click on the link in the main screen labelled “Select Your Product”
Scroll the screen to find the heading labelled “IP Office”
IP Office 2.0(18) Resolved Field Issues
The following field issues have been addressed in the IP Office 2.0(18) software:
Core Software:
The volume on DT Handsets has been increased for New Zealand.
SNMP agent now no longer sends additional random traps when an ATM16 or
DCP16 module is disconnected or reconnected.
SNMP now generates a change event for a replaced module instead of a failure trap
followed by an operational trap.
Ad-hoc conference from SoftConsole now sets a valid failure route.
Page 1 of 12
IP Office Technical Bulletin 22
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
TDMLink errors are no longer encountered when performing 2 consecutive page calls
to a group of 180 users.
The IP Office 412 could reset if a merge config was performed from another subnet,
for example, across a WAN link. This has been resolved.
Merge request could in rare circumstances initiate a reset. This has been resolved.
The IP Office 412 could reset when a config request was made at the same time as a
merge was being performed. This has been resolved.
Monitoring the routing table on an IP Office Small Office Edition no longer eventually
results in the IP stack not responding.
When making consecutive page calls to a HuntGroup from the SoftConsole
application the second page call is not longer incorrectly displayed as a held call.
VoIP Quality degradation issues that could gradually occur over a 2-4 week period
have been resolved.
When calling another Extn via a configured DSS key, it is now possible to use the
message function.
The BLF updates in SoftConsole no longer occasionally freeze due to the application
receiving an incomplete BLF status message from a remote IP Office linked via SCN.
The System Monitor tool no longer incorrectly displays SNMP “Set Request”
messages as “Trap PDU” messages.
When SNMP “Set Request” messages were sent to the IP Office, instead of the
message being silently ignored (as it is unsupported), authentication failure traps
could be generated. This has been resolved.
When pressing a DSS key configured for a user to check the status of a user, if the
user was busy and VoiceMail was selected, the mailbox being routed to was always
the user configured for DSS key 1, regardless of the user being checking. This has
been resolved.
If IPHC was not set, PPP over Frame Relay would not fragment packets. This has
been resolved.
SNMP trap for trunk ports no longer report incorrect values.
Incorrect spelling of “Disconnected” in Dutch on the display of 44xx series phones
has been corrected.
If an incoming call was answered by a user who then manually invoked the call
record feature through a shortcode, and the supervisor then attempted to perform a
“call listen” on that call, the speech path could be permanently cut off from the
external caller.
If an incoming call was answered by a user with Auto-Record configured, and the
supervisor then attempted to perform a “call listen” on that call, the speech path could
be cut off from the external caller for 5-6 seconds during the listen action and then reestablished.
The conference feature now works correctly on the IP Office 401.
A +2db Gain has now been set on E1R2 lines for Korea.
If using an IP Office with a German locale set and 64xx series handsets, the Small
Office no longer resets when the “Dial by Name” feature on the handsets is used.
The date and time fields that are obtained from the CLI of an incoming call on an
Analogue Trunk are now correctly decoded.
When using RIP, the RIP1 & RIP2 request messages are now responded to correctly.
Page 2 of 12
IP Office Technical Bulletin 22
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
If an Incoming call Queuing for a HuntGroup timed out, the IP Office could reset
because there was no ACD record after the call had timed out. This has been
resolved.
The IP Office could reset if a call steal was performed on a call in a HuntGroup
Queue being played a Queued or Still Queued Message. This has been resolved.
If a Call Steal was performed on an Internal call in a HuntGroup Queue being played
a Queued or Still Queued Message, the user performing the call steal could be
incorrectly connected to the wrong end of the call, i.e. they were connected to the
Voicemail Server instead of the calling party. This has been resolved.
If an IP Hard phone User performed a Call Steal on an External call in a HuntGroup
Queue being played a Queued or Still Queued Message, the user performing the call
steal could be incorrectly connected to the wrong end of the call, i.e. they were
connected to the Voicemail Server instead of the calling party. This has been
resolved.
If using a “NAPots” module on an IP Office running in Swedish Local (SVE), English
tones could still be used for users connected to the “NAPots” Module.
Internally calling a user who has DND set now results in NU being displayed on the
calling terminal.
Paging a user with DND set now results in a busy tone being returned.
Auto recording to a different mailbox on a 412 no longer causes modules to lose
connectivity to the switch.
Japanese ISDN Number plan identification is now set to 80 for calls made from IP
endpoints, to prevent call rejection with certain service providers.
Large volumes of invalid DTMF digits received on T1 lines could cause a system
reset when T1 DSP option was selected on monitor. This has been resolved.
System could reset on RAS Dial in from a remote user. This has been resolved.
Installation Wizard:
When setting a VoIP line, on specifically selecting an Audio Codec, G.711 ALAW for
example, when the wizard saved the config to the unit this setting was not saved and
Automatic selection was being used.
If using a Dutch Operating System, pressing F1 for Help would not display the help
file. This has been resolved.
When creating a new configuration, on the Dial Plan screen, if there are no virtual
users and the user had cleared out the starting Virtual Extension number, default
short codes were not created. This has been resolved.
Delta Server:
If an Agent answers an incoming call using Phone Manager Pro and the call is put on
hold (again using PhoneManager), then the agent dials an external number which is
answered, when the agent transfers these two calls together and then hangs up, the
Agent is now in a Ready state. The next incoming call that agent answers could be
incorrectly shown in CCV as an Outgoing Call.
Real-Time Agent Status display showed incorrect information, with some Agents
appearing to be in a “ready” state when they were in fact “Busy”.
Page 3 of 12
IP Office Technical Bulletin 22
DECT:
•
•
•
•
•
When calling a busy user and setting “Call-Back”, when the user became free the
User who requested the Call-Back was not alerted.
Voicemail ring-back displayed misleading CLI. When Voicemail called the user to
alert them of a new message the CLI presented was not “Voicemail” but instead
incorrectly displayed either the CLI of the caller who left the message or just
“incoming call”.
If answering an incoming call on a twinned DECT and the calling party hangs up the
call, the next incoming call would only ring on the desk phone even if the DECT was
"off-hook".
If a DECT phone was a member of a HuntGroup where one or more users were
disabled, then when an incoming call to the group was presented to the DECT phone
no CLI was displayed.
External calls transferred to a terminal with a twinned DECT now divert to voicemail
correctly.

 

[SPIPOffice]

Hello

Thanks - I cannot fine IP Office Technical Bulletin 22 anywhere, can you post the link please.

 

[IPOJedi]

Ooops sorry its on this website, but you will need to register to access it...

https://emea-businesspartner.avaya.com/

then go to this page

https://emea-businesspartner.avaya.com/Support/TechnicalDatabase/main.asp?lng=enuk&cat=tch