Avaya Aura enterprise distribution

Does anyone have experience with distributing Avaya Aura Call Center Elite Multichannel via SCCM? I can't seem to figure out how to apply the Link setting, such as "AVAYA#SWLINK1#CSTA-S#XXX.XXX.XXX.XXX", on the Telephony tab. Also, according to the Avaya guide, there are parameters such as XMLSIPADDRESS, but there is also a secondary parameter with the same name XMLSIPADDRESS. Can these settings be applied at distribution via PowerShell? Also, has anyone used the configuration data commands (p.178) in the deployment scripts? Any help will be greatly appreciated.

3 Comments   [ + ] Show comments
  • Vigneshwaran4264 and rileyz, thank you for your responses!

    Our organization is quite large, and in this case I have to relay my questions to Avaya support through the department which is buying the software, but the testing starts Monday.

    I made a really obvious mistake that I am embarrassed to admit. I was first scripting the base install of Aura 6.4.0 with parameters in the arguments and then applying service pack 6.4.1, which was wiping the parameters out.

    So now almost everything works. The correct code is below. The parameters in question can be used in the arguments string of the last component of the installation. They do not require forward slashes, or quotation marks around the values.

    #Installing base MSI 6.4.0
    $BaseArguments = "/i `"$BaseMSIDir\Avaya Aura Call Center Elite Multichannel Desktop.msi`" /qn"
    Start-Process -FilePath "$Program" -ArgumentList "$BaseArguments" -Wait -PassThru | Out-Null
    #End installing base MSI 6.4.0
    #Install Service Pack 6.4.1
    Start-Process -FilePath "$Program" -ArgumentList "$SPArguments" -Wait -PassThru | Out-Null
    #End installing Service Pack 6.4.1

    Then I was happy to learn that once an Aura registered user logs into the client software, the AD user syncs and the Link string in question ("AVAYA#SWLINK1#CSTA-S#XXX.XXX.XXX.XXX") gets called from the Avaya Configuration Server and fills automatically on the Telephony tab.

    Now I just have to see if I can figure out how to apply the secondary XML server, and that will probably require doing a transform. I will share my findings. - powerserge 5 years ago
  • Happy to hear it finally worked with the property itself. - apptopack 5 years ago
  • Glad to hear its working.
    Powershell tip. I only learnt this recently but it apparently better to do this:

    $null = Start-Process -FilePath "$Program" -ArgumentList "$BaseArguments" -Wait -PassThru

    Than this

    Start-Process -FilePath "$Program" -ArgumentList "$BaseArguments" -Wait -PassThru | Out-Null

    I dont know the technical details, but it's more efficient to assign it to a null variable than to pipe it to a Out-null.

    lol, not that you would notice in 4 lines of PowerShell, but you might write bigger things, you never know :P

    (search for out-nill) - rileyz 5 years ago

Answers (2)

Posted by: apptopack 5 years ago
Red Belt

I haven't installed but can help you. What happens when you try installing
msiexec /I "Avaya Aura Call Center Elite Multichannel Desktop.msi" XMLSIPADDRESS="AVAYA#SWLINK1#CSTA-S#XXX.XXX.XXX.XXX" /qb

If it gets successfully installed, then open the shortcut and go to Tools-option-telephony and see whether the link you provided has refelected.

If not then you can use installrite or picturetaker to capture the changes by manually adding the link. Add the changes to a Transforms file and install it.

Posted by: rileyz 5 years ago
Red Belt
Contact Avaya, you should have a support contract, well you better do for the amount of money your company is coughing up for the VIOP solution!

Vigneshwaran4264 is on the button, you are as well. 
  • Start with the documentation, there should be a MSI Property that you can set to apply you desired setting.
  • If you can't find the property, then do this from command prompt after switching to your directory with the installer.
    msiexec /i NameOfUr.msi /l*vx .\Install.log

    The above will launch the installer in GUI mode, presuming you enter the parameters as part of the setup, it will get logged to the file. After the install, look in the log file for a line called PROPERTY, one of these should have your setting. Its normally at the end of the file.
  • If it not part of the install, then you need to figure out where it stored, hopefully in the registry.
    Use this tool
    to discover the registry change, I recommend reg_file_from_application as it watchs only the exe you select (less noise). 

One you know what the setting is the registry or file, come back to us and we'll let you know how you can create a TRANFORMS to apply the setting to the MSI.

  • @rileyz
    Thanks for your feedback.I have went through the document provided by Avaya and see no clear input. I have provided an outline solution below to capture the changes (file or registry) when manually adding the link and add it in transforms file. Hope it's clear now. - apptopack 5 years ago
    • Ah cool, I've down tick my answer and up ticked your answer. Hopefully it should sit at the top. - rileyz 5 years ago
      • @rileyz
        The user has found that the given property is working by default. So both our answers should sit at the top :) - apptopack 5 years ago
      • :D - rileyz 5 years ago
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ