Troubleshooting Avaya Mobile Communications

Last Updated : Apr 12, 2021 |

Troubleshooting client communication with AvayaMobileCommunications snap-in service

Avaya Mobile Communications is an Avaya Breeze® platform snap-in service. Avaya Mobile Communications integrates Avaya Aura Web Gateway (AAWG) and Avaya Session Border Controller (ASBC) with the Avaya Oceana® to deliver Avaya WebRTC Connect features.

The following table lists common issues seen in client communication between the Avaya Mobile Communications and the AAWG server, and how to troubleshoot these issues:

Issue Description

Cause

Action

The following error message is displayed in your web browser: “ERR_INSECURE_RESPONSE”.

The browser does not trust the server.

  1. Right-click the URL and open it in a new tab to trust the server. This is a temporary solution.

  2. Install the required trust certificates on the client PC running the browser to solve the issue permanently. For more information, see Deploying Avaya Oceana®.

XMLHttpRequest cannot load the following URL: https://1.2.3.4/services/AvayaMobileCommunications/sessions. The https://1.2.3.4:8443 origin is not allowed to be accessed. The response from the server has HTTP status code 404.

The Access-Control-Allow-Origin header function is absent on the requested resource.

  1. On the System Manager web console, click Elements > Avaya Breeze® > Configuration > HTTP Security > HTTP CORS.

  2. Check if Allow Cross-origin Resource Sharing for all is enabled for Avaya Oceana® Cluster 2.

The following error message is displayed: “Request to AMC failed”.

The configuration of the Avaya Oceana® Cluster 2 IP address is incorrect.

On the System Manager web console, click Elements > Avaya Breeze® > Cluster Administration. Check if the Avaya Oceana® Cluster 2 IP address is configured correctly.

Troubleshooting Media Devices

The following table shows how to allow permission for media devices on different platforms. For more information about deploying sample reference clients on each of these platforms, see Deploying Avaya Oceana®.

Platform

Action

JavaScript

  1. Ensure a microphone is connected to the PC.

  2. Check if permissions are allowed on your web browser.

  3. In the drop-down menu that appears in the search bar of your web browser when you make a call, select Allow.

  4. Click Confirm. This allows the site to use your camera and microphone.

iOS

Allow app permissions for microphone on your device:

  1. Go to Settings > Apps and scroll down the list of apps.

  2. Tap an app you want to see the permissions for.

  3. Enable or disable media device permissions for the app.

Android

At install time, the device prompts you to allow app permissions for microphone at install time. After the app is installed, perform the following steps to allow app permissions for microphone:

  1. Go to Settings > Apps.

  2. Tap an app you want to see the permissions for.

  3. Select Permissions from the drop-down menu.

  4. Enable or disable media device permissions for the app.

Troubleshooting SSL certificate errors

The following table shows common SSL certificate issues on different platforms:

Platform

Issue description

JavaScript

The following error is displayed in the web console:

“ERR_INSECURE_RESPONSE”.

iOS

The following error is displayed in the logs:

“The Certificate for this server is invalid”.

Android

The following error is displayed in the logs:

“SSLHandshakeException”.

To troubleshoot SSL certificate issues, perform the following steps:

  1. Install the SSL certificate for the endpoint you are making the request to.

  2. If the endpoint uses self-signed certificates, trust the Certificate Authority (CA) that created the SSL certificate.