One-X Attendant V402 010 ReleaseNotes CM

Avaya GmbHCus-tomer:

Project: One-X Attendant 4.00Sub-ject:

One-X Attendant 4.02.010

Release Notes

Created by Date Last changes by at Rev.:Mathias Schuch 4.12.2012 Mathias Schuch 4.12.2012File name: document.doc Page 1 of 12



Introduction

The Version 4.02.010(SP1) of one-X Attendant is based on Version 4.01.000 from 02.07.2012.

Extensions

- New option for Calendar function “Without password request”. This means that one-X Atten-dant isn’t asking for the Lotus Notes password after login to the client. If this option is chosen and Lotus Notes started with the setting “File/Security/User Security/Don’t prompt for a pass-word from other Notes-based programs”, no password is necessary to get the calendar infor-mation. Without the Lotus Notes setting, Notes will prompt for the password (PEM 190904).

- User Password can now also be changed in ConfigTool. If it is the default password, it must be changed during the login. (Security PEM 190969).

- Support of Avaya AURA Feature Pack 1

Limitations/Important information’s

Common- Update of Client and Server is obligatory, AIS is recommended.- Up to 25 clients on the same one-X Attendant server- AddressParser configuration:

o In the case of problems, there is a chapter with the description of the address parser algorithms and some examples in one-X Attd service manual.

o In countries w/o national code, the area code field has to be left empty and the area code has to be in-serted at the beginning of the PABX number in the corresponding field.

- If the import from external databases via UpdateService is used, it is recommended to set in Config Tool / JOnAS / Server the Transaction timeout to 240. Maybe otherwise the connection to phonebook server (JOnAS) does not work; this problem can only be resolved by a restart of the phonebook server.

- Tomcat 6.0.29 is the supported Tomcat version for WebLM versions 4.7 and later.- one-X Attendant has no approbation for “Avaya Unified Communication as a Service" (UCaaS)- In case of an update from a beta trial R4 version (4.00.004 or lower), it is necessary to delete the files/sub-

directories absenceinfopusher.conf, updateservice.conf, JONAS\deploy and JONAS\ repositories in the C:\Avaya\Servers and C:\Avaya\Servers\backup directories before installing the update.

- If the client shows a window with the message “java.lang.OutOfMemoryError: Java heap space” then the heap space for the JVM has to increased. This has to be done in the file deployment.properties which you can find the folder C:\Documents and Settings\<username>\Local Settings\Application Data\Sun\Java\De-ployment (Windows XP/2003) or C:\Users\<username>\AppData\LocalLow\Sun\Java\Deployment (Win-dows 7/2008). Add the following line: deployment.javaws.jre.0.args=-Xms64m –Xmx256m. The '0' corre-sponds to the JRE you want to set these parameters for. It may be different, i.e. 1,2 etc., do this for the JRE with version “1.6.0_23”.

CM- If the CM installation is distributed over several countries, a separate one-X Attendant Server is needed for

each country to support the different national numbering plans.- CM failover is supported in all scenarios (e.g. CM Interchange) where the IP-Address of CM does not

change.




- MasterDirectory: reading the CM Directory over IP doesn't work- The SCAPI Interface for CM connection does not allow correct external call number detection in all cases. Limi-

tations, configurations and examples are described in the document ‘ExternalCallDetection.pdf’ which can be found on one-X Attd DVD in the directory \doc\Service.

- There are known issues in the call state handling due to lack of some SCAPI events. These SCAPI events and the correspondant call states are described in the document ‘CallStateHandlingOne-XAttendantCM.pdf’ which can be found also on DVD in directory \doc\Service.

Network- See General Real Time Communication Requirements.Operating system- With Windows 7/2008 R2 (32/64 Bit) there could be problems with audio connection in RoadWarrior mode,

like application hang up and one-way speak connection (PEMs: 188351, 188252). This is solved with SP1 of Windows 7/2008 R2.

- If the Korean language is used for the one-X Attendant on Windows XP; the Windows setting for the non-Unicode programs has to be set to Korean, otherwise some text aren’t correctly displayed.

Busy/Presence Information- SVAManager and Avaya AURA Presence Server can’t used together with one-X Attendant

- Maximum values of numbers in net wide busy view:SVAManager: 10000Avaya AURA Presence Server: 1000 (will be increased step-by-step during Controlled Introduction)

- Maximum values of supported SVAManager Configurations:With cluster functionalityTserver Links: 20Other switches: 50Tserver Links + Other switches: 50Monitor Points: 20000

Without cluster functionalityTserver Links: 20Other switches: 100Tserver Links + Other switches: 100Monitor Points: 20000

- If more than 1500 monitor points are configured in extended busy lamp field, the environment variables MAXMESSAGESIZE and MAXBUFFERSIZE have to be set to a value “50 * <number of monitor points>”

- PEM 189759: After upgrading from R3 SP3 or lower on first start of SVAManager Config Tool (qconfig_sva.exe), the SVAManager config tool asks to convert the configured monitor points to new clus-ter configuration. If you click “yes”, some monitor points could disappear and then have to be re-entered. To avoid this, click “no”. For more information on new Cluster functionality. please read the correspondant chapter in Installation and Administration Manual: Additional components->Network-wide busy display (SVA Manager)->QTapi Cluster)

- one-X Attendant will register as ‘trusted application” at AES, this means the TSAPI-Link of the AES has to be configured as encrypted.

- There are some known problems with AIS and Outlook 2007 SP2, it is recommended to update Outlook 2007 to SP3.




- One-X Attendant uses the Exchange Web Service to get busy/free information from the exchange server and only single exchange domain is supported.For further information please look at the service manual, in the chapter “Calendar information”.

- If neither Microsoft Outlook nor Lotus Notes integration is used, it is strongly recommended to deactivate the “calendar usage” option in the Config Tool (item one-X Attendant).




System requirements

Windows 8, Windows Server 2012 and Internet Explorer 10 are not supported (Client and Server).

Server

The PC running the one-X attd server components must meet the following minimum requirements:

one-X Attendant server w/o other server components:- Quad Core CPU with 3 GHz on a Server-Hardware or comparable powerful

Virtual Machine.- 3 GB RAM (recommended 6 GB)- 1 GB available disk space (depending on data)- 100 Mbit/s Ethernet IP connection- Operating systems 32 Bit:

Windows Server 2008 SP2 Standard/Enterprise (recommended), Windows 7 Professional/Ultimate

- Operating systems 64 Bit: Windows Server 2008 R2 Standard/Enterprise (recommended), Windows Server 2008 SP2 Standard/Enterprise, Win 7 Professional/Ultimate 2008 R2 (Enterprise/Standard), Windows 7 (Professional/Ultimate).

- The latest service pack has to be installed in all cases.

One-X Attendant Server with other server components (e.g. MS Exchange, Lotus Domino):- Quad Core CPU with 3 GHz on a Server-Hardware or comparable powerful

Virtual Machine.- 4 GB RAM (recommended 6 GBytes)- 2 GB available disk space (depending on data)- 100 Mbit/s Ethernet IP connection- Operating systems 64 Bit: Windows Server 2008 R2 Standard/Enterprise

(recommended)- Operating systems 32 Bit: Windows Server 2008 SP2 Standard/Enterprise

(recommended)- The latest service pack has to be installed in all cases.

Client

The PC running the one-X Attendant application must meet the following minimum requirements:- PC with 2 GHz- 1 GBytes RAM, depending on the configuration and installation of other com-

ponents (for example MS-Outlook, MS-Word)- Operating systems 32 Bit: Windows XP, Windows 2008 Server, Windows 7

(Professional/Ultimate).Operating systems 64 Bit: Windows Server 2008 (Enterprise/Standard), Win-dows Server 2008 R2 (Enterprise/Standard), Windows 7 (Professional/Ulti-




mate).The latest service packs must always be installed.

- 350 MBytes available disk space (depending on data)- 100 Mbit/s Ethernet IP connection- 19”-monitor with 1280x1024 pixels. (or a 21” monitor for visually impaired

users)- 1 free COM interface if a Braille module is connected.- Printer with graphics capability for printing charges and statistical data.- In Road Warrior mode: USB Headsets with DSP or USB phone.- In Telecommuter mode: Any telephone that can be reached from the ACM.

Single-user

A PC with a single--user solution must meet the following hardware and software requirements:- PC with 2 GHz- 3 GB RAM (recommended 5 GBytes), depending on the configuration and in-

stallation of other components (for example MS-Outlook, MS-Word)- 800 MB available disk space (depending on data)- 100 Mbit/s Ethernet IP connection- 19”-TFT-monitor with 1280x1024 pixels (for visually impaired users a 21”-TFT-

monitor)- 1 free COM interface if a Braille module is connected.- In Road Warrior mode: USB Headsets with DSP or USB phone.- In Telecommuter mode: Any telephone that can be reached from the ACM.- You will need a printer with graphics capability to output charges data and sta-

tistical data.- Operating system 32 Bit: Windows 7 Professional/Ultimate (recommended),

Windows XP Professional, Windows Server 2008 SP2 Enterprise/Standard- Operating system 64 Bit: Windows 7 Professional/Ultimate (recommended),

Windows Server 2008 R2 Enterprise/StandardThe latest service packs must always be installed.

Real-time Communication requirements

The following are the general real time communication requirements for one-X Attendant servers and clients.

Delay: for signalling, a delay can cause a lag in getting events or a malfunction in making feature requests on one-X Attendant servers and clients. For audio, the quality of voice service can become affected – es-pecially in Road Warrior mode – by a delay due to the one-X Attendant usage in a Virtual Desktop Environ-ment It is important to understand, that the delay is not only limited to the network connection between one-X Attd server and clients, but also extends to the one-X Attd client’s audio device.




Avaya recommends an overall delay of less than 150ms.

Packet Loss: a high level of packet loss for signalling can cause missed heart-beats which in turn can cause un-registration of one-X Attendant applications or components. A high packet loss can also cause delay in getting events or making feature requests due to re-transmission delays.

Avaya recommends a packet loss of less than 1%.

Avaya offers to its customers to make a real time communication assessment from an Avaya Certified Implement-ation Specialist (ACIS).

Supported (Tested) 3rd Party Components

-Exchange 2007 and 2010

-Outlook 2007(SP3) and 2010

-Domino Server 8 and 8.5

-Lotus Notes 8 and 8.5

-Virtualization of the one-X Attendant server components with VMWare ESXI 4.0 and Hyper-V:Tests are done with the following operating systems running under VMWare: Windows 7 (32/64 Bit), Windows Server 2008 (32/64 Bit)Tests are done with the following operating systems running under HyperVManager: Windows 7 (32/64 Bit), Windows Server 2008 (32 Bit)VMWare ESXI 5.0 is also supported.

-Citrix XenDesktop 5.5 and higher (not in RoadWarrior mode)

-AES for connection of SVAManager(network wide busy lamp) to the CM:CM 6.0.1 or lower requires AES 4.2.2 Super Patch 4 (AES 6.2 is recommended)CM 6.2 requires AES 6.2 - latest Service Pack

-A list of tested and approved headsets is described in the documents “Avaya one-X Attendant GN USB Head-set”, “Plantronics Headsets-Unified Communications Brochure” and “Plantronics Headset Finder Tool”, which can be found on https://support.avaya.com and https://enterpriseportal.avaya.com/ptlWeb/gs/products/P0639/AllCollateral

-TTrace 3.0.5

-Codes G.711 and G.729 are supported for CM Road Warrior Mode

Supported Languages

- Languages: English, German, Spanish (LAT), French, Italian, Japanese, Korean, Simplified Chinese, Por-tuguese (Brazilian), Russian


https://enterpriseportal.avaya.com/ptlWeb/gs/products/P0639/AllCollateral



Corrected Issues

RC2 (4.02.010)PEM QQ/SR Description Solution

190543Number of entries in call journal cannot be configured.

Extended User Config Dialog Page Other allows to configure the number of call history entries and the number of IM history entries. Min. 1, Max. 500, Default 100.

RC1 (4.02.000)PEM QQ/SR Description Solution

190115

No possibility to reduce the num-ber of proposed fields in the op-erator window.

Configuration possibility added

190371

Issues with status display of presence server in system con-figuration

Now connection beetween JONAS and AIP is observed

190578 Can't changing a container

In v4.00 the system menu does no longer exist for containers. Therefore the user manual has to be corrected. The necessary changes to the user manual have been provided.The changes have been done

190709Display is not updated in case of transfer to digital phone

Reset Contrahent Number after transfer if name changed but number is empty

190727 Accessibility: Operator Window

When the user has logged in every 500ms it is tried to make the oneX-Atte-nandent window the foreground window until this has succeeded.

190761 Documentation WebAccess Service and User manual changed

190764Phonebook service locked if timeout in Updateservice occures

Solved

190770Release 4 IAM not clear with ex-change 2010 see page 36

Service manual changed

190804Doc. Jonas.conf file is now in wrapper_ext.conf


190806Release 4 installation wizard: SMGR password visible

System Manager not needed->no more asked during installation

190940Multifunction button: tooltips and user manual description.

Tooltip and User manual changed

190962 IM History - Only three IM lines in IM History Details

Extend detailed IM History view from 250 to about 8185 characters (for each chat). This should be sufficient for a chat. A single message is limited to 255 characters, so even with max message length 31 messages can be displayed.




Normal shorter messages results in showing much more messages.

190997

Different primary call numbers at the phone book after SMGR-User import

Use E164 Number always as primary number no matter of the order in the ex-port file

191003 Window button is light grayAdded timer to divers Window classes. Method OnTimer updates buttons.

191025Timestamp in operator windows should be in the format hh:mm:ss

Durations in the call card of the operator window are now displayed with hours.

191093SMGR Password is registered false in LPS.properties

It is no longer necessary to enter the SMGR password for LPS.properties, so this is no more a PEM.

191119 IAM Service manual changed

191124IAM. Wrong information about the tsapi licenses


191150

eBLF: tsapi licences are counted. (in AES' WebLM) for each moni-tored user

Named License activated again

191268User guide. Only manually en-tered datasets can be edited

User manual changed

191271IAM Stating one-X Attendant without ACM


190524 point 5 of Alpha test reportNow connection beetween JONAS and AIP is observed

Adopted from Relases 3 Service Pack 6 (3.07.001)PEM QQ/SR Description Solution

187063 161812

'old Mapping' remains when changing an existing ext. database connection

Remove mapping for (external) columns which doesn't exists anymore

187586

No names displayed in BLF when apply Address Parser with local prefix

If Adressparser is changed, enable notifi-cation(which causes an config reload) of all components (Client/Server) again.

188258

ODBC configuration window pops up by associating an image to a phonebooken-try,

Corrected

189700

Documentation. jstels driver can only im-port local files

Description in Configuring the software/Tools: Phone book added

188816 SQL exceptions during AIS activity

SQL stored procedures corrected

189846

'one-X Attendant Info' compiles logfiles in wrong order

Show last 10 logs for jonas, absenceinfo-pusher,client-java,configtool,updateservice in correkt order

190103

AIS display doesn't work for some entries in the net wide busy display EBL (NBA)

Use shadow number delivered with "On-AbsenceChanged" Event instead of read-ing again from server.

190153

Phonebook import can lead to data loss and inconsistency in 1XAttd database

- If option "attach new datasets" is chosen PhonebookID is ignored, this means only if name or phone number is equal the exist-




ing entry is overwritten. All other entries will be added- next_key in "tlb_TableKeys" is allways readjusted (since 3.01.002)

190203

Empty fields in the DB tab of system con-figuration on client side

Use read only access to ODBC settings under HKLM and writing only to HKCU

190363

An accent on the first character causes a bad presentation of the search result

See PEM 189833

190586 Some monitor points wouldn't be set

Trigger SVAManager also for Monitor Type QMT_Normal

190621 Nessus scan detect problems with Sybase

Parameter "-sb 0" to databse service con-figuration added

190887

Wrong sort 'per page' in Network-wide Busy Display

Save SortPerPage in Database and use it on Login / adapt manual

190904 1-3501803338

1XAttd's Notes password query shall be suppressed

New option "Without password request" in Config-Tool/one-X Attendant/Calendar Us-age

190906

1xATTD couldn't start after Java 7 update 4 updated

Checking java plugin registry settings dur-ing startup and reparing it if necessary

190941

Client crash when use 'secondary ringing device'

use main thread for playing wav files if secondary ringing device is configured

190976 Trunk name not displayed

Problem is that "Name" is an entry in data-base with no/invalid call numbe... so if searchnumberhead is 1, "Name" is shown for every unknown number ==> Change default value of searchnumberhead to 0




Changed Components

File Version Comment

Changed Files

File Date Comment

Ospc.exe 30.11.2012

Os_tapi.dll (SC_TAPI) 30.11.2012

Os_tapi.dll (QTAPI) 30.11.2012

Os_tapi.dll (TAPI) 30.11.2012

scapi32.dll 11.01.2012

SVAManager.exe 30.11.2012

qcie11.dll 11.01.2012

qconfig_sva.exe 11.01.2012

one-XAttendant.ear 30.11.2012

pom2.jar 30.11.2012

OSPCConfigTool2.jar 30.11.2012

Ldap.jar 11.01.2012

OSPCLDAP_JDBC_Driver.jar 07.02.2012

AbsenceInfoServer.exe 12.11.2012




DBUpdate.jar 07.02.2012

UPDATE_one-X Attendant_000016_000017.sql

12.11.2012


12.11.2012


30.11.2012


30.11.2012


Date post:	11-Nov-2014
Category:	Documents
Upload:	heart-fragile
View:	115 times
Download:	0 times