# Call is freezing on demo.mediasoup.org

**URL:** <https://mediasoup.discourse.group/t/call-is-freezing-on-demo-mediasoup-org/2807>\
**Category:** mediasoup-demo\
**Created:** [May 20, 2021, 10:31am UTC](https://mediasoup.discourse.group/t/call-is-freezing-on-demo-mediasoup-org/2807 "2021-05-20T10:31:06Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![subham](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/subham/32/1760_2.png) [@subham](https://mediasoup.discourse.group/u/subham)\
**Post date:** [June 22, 2021, 11:43am UTC](https://mediasoup.discourse.group/t/call-is-freezing-on-demo-mediasoup-org/2807/8 "2021-06-22T11:43:06Z")

</div>

> [@transport connection state never gets 'failed' as of Chrome 76](https://mediasoup.discourse.group/t/transport-connection-state-never-gets-failed-as-of-chrome-76/267):
>
> Here’s the scenario of change in webrtc connection state before Chrome 76: connecting \> connected \> block transport \> disconnected \> failed Tested on both Chrome 76 and 77, the ‘failed’ state never is met.

I guess as per the chromium bug in the link above, failed state is never achieved.  
please check.  
Even I am trying to figure out what is the best case scenario to decide when to fire an ICE restart (definitely if the network changes example from 4g to wifi or vice versa) or clean up everything and restart based on ice connection state to reconnect ice properly

Cheers.

---

_[View the full topic](https://mediasoup.discourse.group/t/call-is-freezing-on-demo-mediasoup-org/2807)._