Hello Dirk Engelbart,

We are aware of your problem and I am working to find a solution, this issue will continue being addressed in the technical ticket that was created.

Regards,
Leandro.

Hello Dirk Engelbart,

We are aware of your problem and I am working to find a solution, this issue will continue being addressed in the technical ticket that was created.

Regards,
Leandro.

Hi MajGab8852,

Javascript Client SDK don’t have the ability to set the uuid on outgoing calls, you can only pass it through from the far end to the local client.

Regards,
Leandro.

Hello MajGab8852,

I will try to find documentation about implementing a one time token generator from AAWG service and will get back to you.

Leandro.

Hello DmitrySenashenko3,

The Javascript Client SDK doesn't support WebRTC implementation available in mobile browsers. I suggest you use the available SDK to develop Android applications instead.

Note: that doesn't mean it shouldn't work at all, in fact I just did some tests and as far as I can see, I have problems receiving video from a JSCSDK web client, but I can send and receive audio as well as send video, the test was done with a mobile Chrome version joining an Avaya Spaces conference (application was opened in a desktop version).

Leandro.

Hello Sbogdanov,

Could you please elaborate on the issue? If you are defining a username as credentials for Javascript Client SDK user config then you're probably seeing basic auth being used, right?

Leandro.

Hi Bruno,

Our apologies for the delay in response.

In order to understand your needs, I would like to ask you: do you want to implement a quality of service indicator for the call? or optimize the call configuration to improve the quality of service for those calls that present problems such as packet loss, slow connections?

If you want to implement a QoS indicator for the call, please refer to Call.ServiceQuality API.

Regards,
Leandro.

Hello DanielStingl,

We are analyzing the described problem, please specify which versions are you using of Javascript SDK, Native SDK, AAWG, PMM.

Leandro,
Avaya DevConnect support team.

Hi okahane,

Yes, Javascript SDK has the capability to make calls to a traditional landline phone.

Leandro,
Avaya DevConnect support team.

Hi okahane,

There shouldn't be any differences in Chrome and Firefox behaviour on MacOS.

Please note that Javascript SDK collaboration capabilities are not available in Safari.

Leandro,
Avaya DevConnect support team.

Hello AlokKulkarni,

Audio packet loss stats:

Audio packetLossTotalReceived loss https://www.devconnectprogram.com/site/global/products_resources/avaya_client_sdk/programming_docs/current/javascript/communication/api_refs/AvayaClientServices/AvayaClientServices.Services.Call.AudioDetails.html#toc11

Audio packetLossTotalTransmitted loss https://www.devconnectprogram.com/site/global/products_resources/avaya_client_sdk/programming_docs/current/javascript/communication/api_refs/AvayaClientServices/AvayaClientServices.Services.Call.AudioDetails.html#toc12

Regarding the rest of the statistics you mention, they are not available from the JSCSDK at the moment.
Since some of them cannot be found in webRTC's definitions, in case you want to make a request for those statistics to be considered for future releases, we ask you to please attach references to webRTC's official documentation of the statistics you are looking for.

Leandro,
Avaya DevConnect support team.

Hello AlokKulkarni,

Please check if you are replacing the broken reference in any instance, because the jscsdk itself should not change, it should be like that:

AvayaClientServices.Base.Library.Service.jQuery.addOnVersionChangedCallback

Leandro,
Avaya DevConnect support team.

Hello Dirk_Engelbart,

Correcting my previous response, we are aware that there is an issue regarding Chrome's new same-site cookie policy, this is currently being addressed from the server side and will take effect in an upcoming update.

To clarify the situation, according to https://www.chromium.org/updates/same-site this policy will be introduced in the stable Chrome channels in a future release, not yet defined.

Leandro,
Avaya DevConnect support team.

Dirk_Engelbart wrote:
When trying to re-login we got the Message "A Cooki associated with cross-site resource.." within the Chrome Logs

Did you also get any unexpected behavior along with that error, please try with current Chrome version (80) that already implemented that policy? There shouldn't be cookies that do not comply with the policies of sameSite, but it seems that Chrome is showing that error even in cases that comply with policy.

Leandro,
Avaya DevConnect support team.

Hello Dirk_Engelbart,

We're taking a look at your issue, we'll be back with an reply as soon as possible.

Leandro,
Avaya DevConnect support team.