While I have a collaboration started, every few seconds I get an error in the console:

POST http://amms<PROJECT NAME>.aps.gl.avaya.com/viewer/rest/live_viewer/ net::ERR_CONNECTION_REFUSED

The wcsConfiguration looks like this:

wcsConfiguration: {

        enabled: true,

        credentialProvider: new AvayaClientServices.Config.CredentialProvider(username, password),

      },

I have tried both with and without a credentialProvider and the error is the same.

Whast is amms used for ?
How can we fix the CONNECTION_REFUSED error ? Is anything wrong with the wcsConfiguration?

You only need to set wcsConfiguration to enabled. The credentials and connection info come from the conference server. It looks like the URL being given out is not routable for some reason. Also, I see that it is http. It should be https. There may be some misconfiguration on the conference server.

The ams is a type of media server that the WCS is co-resident with.

JMiddleton wrote:You only need to set wcsConfiguration to enabled. The credentials and connection info come from the conference server. It looks like the URL being given out is not routable for some reason. Also, I see that it is http. It should be https. There may be some misconfiguration on the conference server.

The ams is a type of media server that the WCS is co-resident with.

Who can take care of the misconfiguration on the conference server ? Is it something we have to fix on our part ?

please provide some details on your environment, who supplied it, who configured it? I am looking for company, not individual there. There are a lot of possibities for the environment you are utilizing. In general a business partner or Avaya Professional Services would have deployed and have responsibilities related to initial configuration of the environment, and you would be under a maintenance contract with someone for different levels of 'day 2' support. It could be their responsibility assuming you are using a production environment, or it might be yours - especially if you are in some form of lab environment your company put together and your team did the configuration for the environment. I suggest finding out who did the initial configuration of meetings server and asking them if there is a support contract in place.

ibogdan,

Avaya support has contacted me and is indicating that collaboration connection is working fine (with https) for the default portal client that comes with Avaya Meetings. That indicates it is likely a problem with the custom application. Can you please collect debug logs and attach them? https://www.devconnectprogram.com/site/global/products_resources/avaya_client_sdk/programming_docs/current/javascript/communication/tech/troubleshooting_and_debugging.gsp

Be sure to enable verbose logging in Chrome Dev Tools prior to capturing the logs. Thanks.

For debugging purposes, I have set the following wcsConfiguration inside UserConfiguration that is used to create the user.

wcsConfiguration: {

        enabled: true,

        networkProviderConfiguration: new AvayaClientServices.Config.NetworkProviderConfiguration(

          new AvayaClientServices.Config.ServerInfo('amms1<project_name>.aps.gl.avaya.com', port, true),

        ),

      },

I have noticed that the user's wcsConfiguration is getting overwritten at one point and the isSecure changes from true to false.
I have created 2 log files:
Part 1 - The first log file has all the logs beginning from the starting and joining of a Meetme conference up to the point where the wcsConfiguration is overwritten and isSecure is changed from true to false. This happens then the call's state changes to 'established'.
Part 2 - The second log file contains all the logs AFTER the call was established until Avaya does requests (that fail) to the wcs URL.

One thing that has caught my attentions are the MESSAGE RECEIVED logs inside the part 1 log file.
The first MESSAGE_RECEIVED log has "messageType": "callEstablished". The "messageData" has "webCollaboration":"true", but "webCollaborationUrl\":\"REMOVED\"
The second MESSAGE_RECEIVED log has "messageType": "updateCallData". The "messageData" has "webCollaboration":"null" and "webCollaborationUrl\":\"REMOVED\"
I tried to access one of these resource URLs separately from the application, for example https://aawg1<project_name>.aps.gl.avaya.com/csa/bsid/65635933-ece4-420f-8fa8-b88341c6abf0/resources/tenants/default/users/self/clients/65635933-ece4-420f-8fa8-b88341c6abf0/calls
and I got a different response:
"webCollaboration":"true" and "webCollaborationUrl":"https://amms1<project_name>.aps.gl.avaya.com/viewer.php?token=7B612175D70711EEAD69856C5D5B3BED&participantId=7B5317B4D70711EEAD69856C5D5B3BED&meeting_id=2142&mode=JOIN&login=2001001@sip.<project_name>.com" instead of "REMOVED".

Please check the log files.
Thank you!

Thanks for the logs. They confirmed that the URL is coming correct from the server.

I went back and looked at the parsing for the URL and see that it is ignoring the protocol and using http or https based on the protocol of the page being rendered. This was an old workaround to avoid attempting http for an https site because the browser would not like it. I'm guessing you are serving your application from an http url. If you change it to https it should solve the issue. You need to use https anyways in order for webrtc to work.

Please only set the enabled field in the wcsConfiguration. As you noticed, the rest of the fields are purposely overridden when the url is parsed from the server.

By changing to https, the problem was indeed solved. Thank you!
There are no more failed requests and the connection to the live_viwer is succesful. "WCSCollabProvider: Socket open. wsConnId: 2_511"

But I am still facing a major issue. I have started the Collaboration but all the capabilities are still not allowed with reason: CAPABILITY_INVALID_STATE.
How could I have screen sharing or whiteboard capabilities allowed?

I can't think of a reason off the top of my head. Please capture a new set of logs. Maybe that would help.

JMiddleton,

I have managed to start a screen sharing locally, thank you for the responses.
I am now facing another problem, please see https://www.devconnectprogram.com/forums/posts/list/0/26754.page#p168118