General IAUG Discussion Forum

 View Only
  • 1.  Workplace deployment using AADS

    Posted 10-05-2020 04:15 PM
    Hi all,

    We are preparing to deploy Avaya Workplace to existing One-X Communicator users.  We plan on doing a minimal UC type of deployment at first utilizing CM, SMGR and AADS.  We're running into a couple of challenges:
    • We are unable to use DNS for automatic configuration, so we are going to include the web URL for automatic configuration in the install to make it as simple as possible for our customers and minimize mistakes and support calls.  However, in our testing we are still prompted for a username and password after entering the URL.  Is there a setting in the config that I'm missing to bypass/disable this?  In the planning doc, it also mentions needing to create an Avaya Cloud account with a mapping for our domain to get past this.
    • Related to the above, documentation (attached) says to start at Avaya Cloud Account but I can't even browse there, let alone create the account/mapping.
    • Most of our current users are H.323, but Workplace is SIP-only.  I understand we can set up dual-registration, at least until we go full SIP internally.  Is there an easy method for bulk creating SIP accounts to map to all the existing stations, or will we have to perform this manually?
    I've attached the documents I've used as reference, if it helps.  If any of you have already done a similar deployment and experienced any gotchas that I should also watch out for, please let me know.  Thank you very much!

    ------------------------------
    Shane Comer
    Network Engineer
    Washington State Department of Health
    Tumwater
    ------------------------------


  • 2.  RE: Workplace deployment using AADS

    Posted 10-06-2020 08:25 AM
    Good morning Shane,

    After the user enters the web URL for configuration, IX workplace prompts for the SIP username and password or in other words the SIP extension and the communication profile password set for the user in their System Manager user profile. As for the Avaya Cloud account, there are two configuration settings you can add to the settings file; ENABLE_AVAYA_CLOUD_ACCOUNTS and AVAYA_CLOUD_SPACES_URI. These settings trigger the Avaya Spaces login step in the account setup when logging in for the first time. Setting the ENABLE_AVAYA_CLOUD_ACCOUNTS to "0" should allow the client to skip the Avaya spaces login. 

    -Manny

    ------------------------------
    Edmanuel Ferrer-Lebron
    Enterprise System Analyst I
    Texas Tech University System
    Lubbock TX
    ------------------------------



  • 3.  RE: Workplace deployment using AADS

    Posted 10-06-2020 11:42 AM
    ​Thank you all!  The insight I received was all very helpful.  Some points to clarify:

    • to Kellye RE: DNS - Even if it's the easier method normally, we have to rely on an outside agency to make changes to the required fields because of how our state forest is structured.  Because that's always an uphill battle, we usually try to exhaust every internal-only option first.
    • to Edmanuel RE: username/password - I figured it might be the SIP username in SMGR, but I was changing the wrong password in the Identity tab instead of the Communication Profile!  Thank you for clearing that up, I'll try that one again.
    • to Kellye RE: cloud account - Thanks for clarifying that.  We are not using Apple push notification (yet), but we'll see where the future takes us with the mobile realm.  Also, thank you for your input on the SIP accounts.  We're not using AAWG, so that shouldn't be an issue.  If a bulk import turns out to be too challenging we do normally partner with Cerium, so I can ask them about provisioning.
    I think this puts us on a good path forward.  Again, thank you all for the help!  This type of knowledge sharing is exactly why I love this community.

    ------------------------------
    Shane Comer
    Network Engineer
    Washington State Department of Health
    Tumwater
    ------------------------------