AAAD registry key

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • cpreskar
    Aspiring Member
    • Apr 2012
    • 1

    AAAD registry key

    We are trying to use KASE to push the install of the prerequisites required by the AAAD. The push is being done with admin permissions. The agent launches the desktop from their non-admin profile and receives a softphone error. The application is trying to write to the registry but can't. Does anyone know what the application is putting in the registry and where? We can add this to the KASE push if we can find it.

    Particulars:
    MBT
    AACC Voice and MultiMedia 6.2.whatever is current.

    Any help would be appreciated!
  • gupta5
    Aspiring Member
    .
    • May 2012
    • 2

    #2
    Reply

    Hi

    I would advice to involve Avaya Backbone to resolve the issue. They will be able to help you in resolving the issue after collecting the required details from Site

    Nikhil

    Comment

    • alexhp
      Brainiac
      • Nov 2010
      • 61

      #3
      Are you using the embedded H323 softphone?

      Comment

      • stphnwd
        Brainiac
        .
        • Jan 2011
        • 52

        #4
        The SignalProtocol Registry key setting is well documented and required for using the embedded softphone of AAAD. There is also a Group Policy Object included on the AACC server for this. Search the AACC documentation for SignalProtocol.
        Stephen Wood

        Comment

        • tluucong
          Member
          • Aug 2012
          • 3

          #5
          I see this topic is so long time but may be not closed so that I give comment as well.

          As I understand that there is no silent install package for AAAD. When you want to run AAAD on a new machine, you need to install prerequisites required packages and AAAD software. You can push install prerequistites required from your domain but AAAD package is cannot.

          There are thousands keys writing to registry during AAAD run the installation. You need to use admin permissions to install this and take a first Agent login then this machine can use for all other Agents.

          That is my idea. Please advice if you have matter.

          Comment

          Loading