Avaya Site Administration 5.2 Windows 7

Posted on by

Build great experiences for your brand, and gain peace of mind with Avaya's suite of contact center and unified communication solutions designed to your needs. Effective June 3rd, 2013, Avaya Aura Application Enablement Services, Release 5.2.4 and earlier releases – including all corresponding dot releases of 5.2.x are End of Sale. The other important dates of these releases are, End of Software Support August 24th, 2014 and End of Services Support June 3rd 2019.

This is not an official guide! Past performance is no guarantee of future results!

Site Administration Release 5.2 SP6 Table 2: Avaya Site Administration (ASA) 5.2 (SP6) Operating System Third Party Applications & Packages Virtual Machine Support Additional Notes Windows XP Professional with SP 3 Windows Vista (32-bit and 64-bit) Windows 2003 Server with SP2 (Standard and Enterprise) Microsoft Windows 2000 Server with. Since Windows 7 has been widely available to the business community for a few months now. Has anyone used Windows 7 in a production environment for ASA, CMS, IP Agent, IP Softphone, VAL Manager or any other apps? Can you enlighten us on successes or failures? Thanks, gblucas CM 5.2 CMS R14 Intuity Audix 5.1.

Avaya Site Administration 5.2 Windows 7

I've been lucky enough to be testing Windows 10 for some time, and have spoken to lots of Avaya engineers who were worried about using Windows 10 because of compatability with Avaya products. I thought I'd compile an unofficial list of what works and doesn't. Engineers like to tinker with new toys, so wanted to pass on my experience in case you brick your laptop just before walking on site...

Tool

Please bear in mind, this list is based on the Preview build (10162 and earlier), and may not be representative of the final version when it's released on July 29th. My testing comprises of using Windows 10 on three machines, two of which are installed on the primary partition, the third is on VirtualBox on Mac OS X Yosemite (10.10.3). The results are from all three instances unless noted.

  • Provision (2014.3) - no issues found connecting to CM, MM and AAM.
  • ASA (6.0.07 SP11) - no issues including Announcement backup/restore (SP12 is coming soon to support CM7, but this has not been seen/tested)
  • One-X Communicator 6.2.4.07 - worked fine in H.323 and SIP mode, have not tried any presence or video, just voice
  • One-X Agent 2.5.5 (not tested through VirtualBox) - registered to a CM with no issues - recommend more thorough testing
  • CMS Supervisor R17 (not tested through VirtualBox) - limited testing here but worked fine

Other third party apps that have been used and found to be working:

  • PuTTY 0.63
  • WinSCP 5.7.3/5.7.4
  • SecureCRT 7.3.4
  • VMWare vSphere client 5.5 and 6.0

Avaya Site Administration 5.2 Windows 7 32-bit

Firefox remains the browser of choice connecting to Avaya products. Microsoft Edge (the IE replacement) did not fare well, but truthfully I gave it 5 minutes before I realized it sucked and moved back to something tried and tested. Edge doesn't seem to have a decent PDF viewer built in...so no wonder I changed back. Will get better over time I am sure.

So far so good...now for the bad stuff:

Avaya site administration downloadAvaya Site Administration 5.2 Windows 7

Avaya Site Administration Guide

On a number of these builds, I found the upgrade process from build to build bricked my network adapters and/or prevented VPN clients (Cisco & SonicWall) from functioning at all. At this current time, 10162 has bricked both my VPN clients and even a fresh ISO install of 10162 doesn't solve the problem. This will probably go away when Windows 10 goes live, but it's been a nagging problem for a few months. Worth testing first if you rely on VPN clients for day-day or customer connectivity.

Hope this helps :) and please add your experiences in the comments.

Avaya Site Administration 5.2 Windows 7 64-bit

Product names and trademarks used in this post are owned by their respective corporations.