All,
we actually have the issue that a 180 ringing status (RONA) is not handled by the Webgateway.
Is this a supported feature in the JavaScript SDK?

Thanks Dirk

Yes, it is supported.

Hello Tsarev,
Thanks for your feedback.

The problem is when a call is coming in thru a VDN and is not answered by an agent within that skill group within a certain time the call goes into queue and is then assigned to the next available agent. This continues until an agent upon receiving such a call answers within the given time (RONA settings). At the customer side this time is at the moment 5 seconds - around 2 times a ringing tone.

When we trace the call we can see as follows:
- When answering the call with sip agent for desktop we can see the call set-up as expected: 100 Trying, 180 Ringing, 200 OK.
- When trying to answer the call with our JavaScript SDK based Soft Client we do not see this 180 Ringing Status. Therefore after 5 seconds the RONA is getting in place (see above).

Is there a way that we can set this 180 Ringing Status of the call via the JavaScript SDK?

Thanks Dirk

Hello, Dirk,

Yes, executing call.startRinging() should resolve the issue for you. Please share JSCSDK logs in case that doesn't help so that we can help you troubleshoot it further.

Thanks,
Artem.

Hello Artem,
thanks for the hint, we have implemented as follows:

if (call && !call.getUserToUserInfo()) {
????????call.startRinging();
?}

This is now working fine on our environment.
Client stays ringing till Rona time gets activated.

For some reason this is still not working on the customer environment.
Call is still within the call list of the client, but call is not longer active.
So perhaps an issue between the AAWG call list and the CM?

Customer is on AAWG 3.4 our is 3.1
Rona is deactivated on customer side.

Could this be an issue?
Dirk

Hello, Dirk,

I think we will need logs to understand the root cause.

Thanks,
Artem.