こちらのページは旧SkyWayの情報です。新しいSkyWayに関する情報はこちら

End call immediately

コメント

3件のコメント

  • Avatar
    岩瀬 義昌

    This is due to trying reconnection which sometimes occurs along with network condition. Currently you need to wait for some secs.

    Alternatively you can use "Room" model even though you're going to make a P2P call, as done in https://example.webrtc.ecl.ntt.com/fullmesh-videochat/index.html# . In this example, after PeerB left, PeerA can notice its event immediately.

    0
    コメントアクション パーマリンク
  • Avatar
    Douglas

    Sorry for replying to an old thread.

    It seems to me like there are two separate scenarios that the SDK has merged into one. These scenarios are:

    1. One of the peers explicitly chooses to disconnect using `call.close`.
    2. One of the peers experiences a network disconnection.

    I think that in scenario 1, the SDK should immediately notify the remote peer that the call will close now, and then close the connection. The SDK should not handle scenario 1 like scenario 2.

    Rewriting to use the room model to work around this issue is undesirable, because from a UX and backend perspective now the app needs to differentiate between "1 on 1 rooms" and "multi party rooms" and then recreate the correct call experience. Eg. when someone hangs up on a 1 on 1 telephone call, both sides will immediately stop broadcasting.

    What do you think?

    0
    コメントアクション パーマリンク
  • Avatar
    Yoshimasa Iwase

    Douglas,

    Thanks for your comments.

    Personally I really understand and agree on what you wrote. Especially, the scenario [1] should reflect on the status immediately and SDK should notice developers.

    SkyWay team has been already understood this background and start to work on the improvement along with the priority.

    0
    コメントアクション パーマリンク

サインインしてコメントを残してください。