RAINBOW_ONWEBRTCCALLSTATECHANGED does not always emit

Folgen

Marc EGOLF

• 20. Juni 2019 11:20

Hello

I'm experimenting with WebRTC calls in the Rainbow Web SDK (latest releaserainbow-web-sdk 1.57.1 is installed).

I've noticed that the RAINBOW_ONWEBRTCCALLSTATECHANGED event of the WebRTC part in the Web SDK is not emitting every time.

Here’s the workflow which causes the problem:

1. CPaaS User: Calling Rainbow User
2. Rainbow User: Pick up call
3. CPaaS User: Talks to Rainbow User
4. Rainbow User: Hangs up the call
5. CPaaS User: Is still in the call (presence status: busy)

In the case where the Rainbow User hangs up the call, the ONWEBRTCCALLSTATECHANGED event is never emitted.

I think it is an issue in the SDK but maybe someone can help me with this? 

3

• 

  Konrad Hyzy

  • 21. Juni 2019 09:29

  Hi, 

  the RAINBOW_ONWEBRTCCALLSTATECHANGED event passes only Call object with all the updates. In order to retrieve the current state of the call, try looking at 'status' property of Call object. 

  I couldn't reproduce the same behavior with the newest SDK version. Call status comes back to {key: 0, value: "Unknown"} as soon as I hang up with one of the users.

  Would you be able to share your code with us? 

   

  Best regards,

  Konrad 

  0

  Aktionen für Kommentare Permalink
• 

  Marc EGOLF

  • 21. Juni 2019 10:13

  Hi Konrad,

  Thanks for your answer.

  Did you reproduce it exactly how I described above? Only when you follow this exact scenario you should be able to recreate my issue.

  As you see in my code below I retrieve the call status and create a console log. This works perfectly in every scenario except in the one I described in my first post.

  

   

  Best Regards,
  Marc

  0

  Aktionen für Kommentare Permalink
• 

  Konrad Hyzy

  • 21. Juni 2019 13:29

  Hi Marc,

  so just to make sure, you have two users: one (let's call him user A) is using CPaaS app (a third party app using Rainbow Web SDK), the other is using our UCaaS web client (user B)

  The scenario is as follows:

  1. A calls B

  2. B answers the call

  3. B hangs up

  4. A stays busy despite being effectively disconnected from the call

  Please confirm whether or not I am right so I can proceed with the tests. 

   

  Thanks in advance,

  Konrad

  0

  Aktionen für Kommentare Permalink
• 

  Marc EGOLF

  • 24. Juni 2019 07:56

  Hi Konrad

  Yes this is exactly the case.

   

  Best Regards,
  Marc

  0

  Aktionen für Kommentare Permalink

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.