Using Google Dialogflow with AEP 8

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • cruz554
    Aspiring Member
    • Sep 2024
    • 2

    Using Google Dialogflow with AEP 8

    Hi,

    We are integrating for 1st time our AEP server with google dialogflow. I have created the ASR server and uploaded the json file from Avaya. And using the default application in mpp. But we are unable to make a successful call to google. I'm getting below error in EPM
    Google Server shutdown stream from remote. Endpoint ID: 0, Error Code: 16, Error Msg: Request had invalid authentication credentials. Expected OAuth 2 access token, login cookie or other valid authentication credential. See https://developers.google.com/identi...onsole-project.
    FileName=media/google/DialogFlowEEProvider.h LineNumber=969
  • avc925018484510
    • Jun 2025
    • 1

    #2
    Ensure you have created a service account in the Google Cloud Console with the necessary Dialogflow API permissions.
    Download the JSON key file for the service account.
    Make sure your AEP server is configured to use this JSON key to generate OAuth 2 tokens during API requests.

    Confirm that your AEP and the Dialogflow EE Provider are correctly configured to include the OAuth 2 access token in the API request headers.
    Check if your integration code is correctly reading and using the JSON credentials to obtain an access token.
    geometry dash

    Comment

    • avc953069690058
      Aspiring Member
      • Dec 2025
      • 1

      #3
      Avaya AEP requires the service account key (JSON) from Google Cloud. COC MOD APK
      If the JSON was created for the wrong project or wrong Dialogflow agent, Google will reject it.
      Last edited by avc953069690058; 12-10-2025, 05:39 AM.

      Comment

      • avc924546680786
        Member
        • Jun 2025
        • 5

        #4

        The error indicates that Google Dialogflow is rejecting the request due to invalid authentication credentials. Please ensure that the JSON key you uploaded from Avaya corresponds to a service account with the correct permissions in your Google Cloud project. Also, verify that the OAuth 2 token is properly configured and accessible by your AEP server.

        Double Check the following:

        1. The service account has Dialogflow API enabled.
        2. The JSON key is correctly referenced in your ASR configuration.
        3. The system time on your AEP server is synchronized, as OAuth tokens are time-sensitive.
        4. You are using the correct endpoint for your Dialogflow environment (ES vs. CX if applicable).

        Once these are confirmed, restart the ASR server and try the call again. If the issue persists, consider generating a new JSON key and updating the configuration.

        Reference: [Google OAuth 2.0 Guide](https://developers.google.com/identi...ervice-account)
        Last edited by thiel2; Today, 08:09 AM. Reason: Removed malicious link disguised as text in reply

        Comment

        Loading