Client Type Characteristics And Deployment Scenarios
Avaya Messaging can be purchased in several varieties. Options and Add-Ons can be included to extend its capabilities.
Licensing Levels |
---|
Basic |
Advanced |
All Avaya Messaging versions (Advanced and Basic) are available per user on an annual subscription or a perpetual basis. Annual subscription licensing includes software assurance for the duration of the license. Per user perpetual licensing includes 1 year of software assurance. Annual software assurance renewal is required for license updates and support entitlement.
Note: A minimum of 50 users, in any combination, must be purchased with the initial license. |
Caution: One site cannot combine both an Avaya Messaging Subscription license and an Avaya Messaging Perpetual license. |
Avaya Messaging Advanced
Avaya Messaging Advanced is a comprehensive unified communications and collaboration platform. Avaya Messaging offers next generation cloud-enabled communication features that improve collaboration and boost productivity, including Unified Messaging with voicemail, Real-time communication applications like voice and instant messaging and voice conferencing.
Avaya Messaging Basic
AdvancedBasic provides Voicemail integration.
Options can be applied to any version of Avaya Messaging, and must be purchased annually for each user.
Transcription
Voicemail is transcribed into text and delivered to the client’s email inbox.
ASR (Automatic Speech Recognition) & Text-to-Speech
Provides voice access and navigation of email, contacts and the calendar. Initiate calls, hear and respond to email and send messages using voice commands instead of the keyboard. Call in and have the system read your emails to you.
Fax Option
eFax services require UM or Collaboration for Google Apps licenses (included with Collaboration Pro).
Add-Ons are one time costs and are not subject to annual subscription fees or renewal costs.
•Per Port License for G.729 (quantity must be equal to voice ports and SIP must be enabled).
•SR140 Fax board support.
•JITC (Joint Interoperability Test Command) compliance for high security environments.
•Integration with Avaya Symposium.
The following table demonstrates the different types of license and the features available to each:
Features | User Type |
ADVANCED |
BASIC |
---|---|---|
Web config. Access (Mailbox Administration) |
● |
● |
Mobility |
● |
|
All clients - Phone, email, PC Mobile, Web |
||
Access to Contacts |
● |
|
Web client specific |
|
|
Access to Availability filters |
● |
|
Access to Find Me |
● |
|
Access to Assign calls |
● |
|
Access to Locations Calendars |
● |
● |
Phone specific |
||
Enhanced Call Control |
● |
|
Find Me (Sequential) |
● |
|
Find Me (Broadcast) |
● |
|
Follow Me (One number per location) |
● |
● |
Speech Commands |
Optional |
|
Speech access to public contacts |
Optional |
Optional |
Speech access to private contacts |
Optional |
Optional |
SMS |
● |
|
Remote Notification |
● |
|
Message Forwarding |
● |
● |
Distribution Lists |
● |
● |
iLink Pro Desktop options |
● |
|
Screen POPS |
● |
|
PIM integration |
● |
|
Instant messaging |
● |
|
Presence management |
● |
|
Access to visual directory & buddy list |
● |
|
Desktop Dialing with IP dialer |
● |
|
Call Log window |
● |
|
Desktop SMS (ability to send to SMS) |
● |
|
Synchronized contacts |
● |
|
Synchronized calendar |
● |
|
Inbox Access |
||
Web client |
||
Administration |
● |
● |
Access to Inbox |
● |
● |
Access to internal messages |
● |
● |
Access to e-mail messages |
● |
● |
Access to voice & Fax messages |
● |
● |
Phone Access |
||
Access to VM from Phone |
● |
● |
Access to fax messages from phone |
● |
● |
Access to email messages from phone |
● |
|
Synchronization mode |
||
Groupware Forms |
● |
|
Sync voice messages to users’ email inbox |
● |
|
Contacts |
● |
|
Outbound Desktop Faxing Capabilities (ODFC) |
● |
|
Use eMail to send Fax |
● |
|
Other Features |
||
Transcription1 |
● |
● |
Send URL (WebLink) |
● |
|
Collaboration |
||
Presence |
● |
|
Instant messaging |
● |
|
Click-to-call |
● |
|
Voice communication |
● |
|
Geo-location sharing |
● |
|
Screen pops and call logging |
● |
|
Call control |
● |
|
Unified Messaging with Voicemail |
||
Voicemail |
● |
|
Auto-attendant |
● |
● |
IVR Trees |
● |
|
Unified Messaging |
● |
|
Message Synchronization (MWI) |
● |
|
Call History |
● |
|
Voicemail to contact resolution |
● |
|
Integration with contacts for dialing and replies |
● |
|
Fax |
||
Fax message access from the inbox |
● |
● |
Fax messaging (Inbound) |
● |
● |
Fax on demand |
● |
|
Application Integration |
||
Google Apps |
● |
|
Salesforce CRM |
● |
|
Office 365 |
● |
|
Avaya Aura Contact Center integration (Meridian IVR and ACCESS caller applications) with M1/CS1000 |
● |
|
Clients |
||
iLink Mobile |
● |
|
iLink Desktop |
● |
|
Desktop UM client for Outlook, Groupwise |
Outlook only |
|
Web Access - message, manage greetings, user settings |
● |
|
Add-on Applications |
||
eFax |
Optional |
|
IVR connector |
Optional |
|
Speech-to-text transcription |
Optional |
|
Text-to-speech |
Optional |
|
Automatic speech recognition |
Optional |
|
1 Transcription requires separate licenses be activated, which is distinct from the user type requirements.
Product Support recommends the following to ensure successful and responsive assistance with regard to any field issues. All systems must be configured for Remotely Accessed support.
The Avaya Messaging Server is accessible via an Internet connection. This will enable Avaya’s Product Support team to initiate a WebEx session with the administrator of the Avaya Messaging Voice Server. This is a low-impact and very powerful tool for remote trouble-shooting.
Prior to loading third-party applications on the system, open an Service Request on the Avaya support page with the appropriate sold to account number. A member of the GSS team will reach out to help identify any potential conflicts. Examples of third- party applications include antivirus and backup software applications.
Note: To avoid unnecessary technical support charges, refer first to the product documentation. The Avaya Messaging documentation suite can be found through the documentation website at support.avaya.com. |
Note: To access technical support you must be a certified technician with a valid PIN number and the site must have an active warranty maintenance contract. |
Note: It is not possible to validate every Anti-virus program. If the proper exclusions are granted for the appropriate user, then there usually are no issues. However, every site is unique and we cannot guarantee untested AV utilities will not affect Avaya Messaging. |
Minimum Client Hardware Specifications
A client workstation should at least meet the following minimum hardware specifications:
• Multimedia PC (sound card + speakers for multimedia playback)
Note: These specifications should be adjusted accordingly depending on other applications that may be running alongside end user Avaya Messaging applications. |
Note: For all Windows 2012, 2016 and 2019 installations, disable the User Access Control (UAC) feature of Windows to ensure proper operation of the software. Refer to the Server Install Guide for more details. |
When utilizing the plug-ins for iLink Pro Desktop (e.g. Outlook Plug-in) please keep in mind that the client machine will have to simultaneously run both the iLink Pro Desktop and the software that the plug-in is integrating with. When looking at the Outlook Plug-in as an example, Microsoft requires minimum of 256MB of ram for the Microsoft Office Suite 2008 and the requirement increases depending on the features that the user employs from the suite. This means that Microsoft's requirements must be added to the iLink Pro Desktop's requirements in order for them to function properly. Please consider exactly how the user will utilize iLink Pro Desktop when deploying the software to client machines.
Like most applications iLink Pro Desktop only uses resources when necessary. When the user has the iLink Pro Desktop window minimized, it will require less resources. When the iLink Pro Desktop is opened, and the user has numerous windows opened (e.g. Chat window, Call Control window, Directory window, etc.), the application will use more resources. So when you are deploying the application to a client machine, please consider the user's habits and general usage estimates as well. When you consider the responsiveness and speed of the application, users that require heavy usage will need additional hardware resources to experience the same level of performance as light users.
Since iLink Pro Desktop requires an Internet and/or network connection to communicate with the Avaya Messaging server, having no or very low network resources available on the client machine may prevent proper operation. While iLink Pro Desktop does not require significant amount of network resources, if another application is using up all or most of the resources, iLink Pro Desktop may fail to communicate with the Avaya Messaging server when called upon.
Note: All users who wish to utilize Web Client along with iLink Pro Desktop must also have a compatible web browser installed. Please refer to the Web Client requirements section for detailed information. |
Deployment Scenario 1 - Basic iLink Pro Desktop Usage
If the user only requires core functionality of iLink Pro Desktop (e.g. Chat, Call Control) and no additional plug-ins, the following setup will prove to be sufficient.
Note: Deployment Scenarios assume that the user's computer does not run any other resource intensive software while utilizing iLink Pro Desktop unless mentioned specifically within the scenario. |
The user should not experience any significant delays while using their computer. All notification, messages and windows should appear almost instantly under these conditions. Basic applications such as web browsers may be used without significant effect on performance, which means that Web Client can be loaded without any difficulties.
Scenario 2 - Integrated iLink Pro Desktop with Outlook
If the user requires core functionality of iLink Pro Desktop (e.g. Chat, Call Control) along with Microsoft Outlook plug-ins, the following setup will prove to be sufficient.
Note: The RAM requirement for Microsoft Office Suite varies greatly depending on the user’s needs. If the user is only using Outlook from the entire suite, only 256MB of extra RAM is required in addition to it's own requirements. |
Note: Deployment Scenarios assume that the user's computer does not run any other resource intensive software while utilizing iLink Pro Desktop, unless mentioned specifically within the scenario. |
The user should not experience any significant delays while using their computer. All notification, messages and windows should appear almost instantly under these conditions. Basic applications such as web browsers may be used without significant effect on performance, which means that Web Client can be loaded without any difficulties.
Since the Outlook tool bar contains all the major features of , the user may have the iLink Pro Desktop window minimized for better desktop management. However, minimizing will not reduce the resources that iLink Pro Desktop uses since the Outlook plug-in will always be active in its place. This ensures proper response time of the software at all times by eliminating the need for the application to reallocate the resources that it requires every time it becomes active.