States to monitor for retry publishing - critical

[Nagendra Kumar1648581702]

Hello Ant Media Team,

  I am trying to handle the poor network condition in publishing.  Sometimes we connection is lost and publishing stopped then I tried myself with timer and state of ice_connection_state and info but looks like not able to cover all scenarios.

Then  I saw the sample code here

https://github.com/ant-media/StreamApp/blob/2248e7b54ef83fbb20237caa4ea8289f0c4b4647/src/main/webapp/index.html

refresheConnection.  Looks like this is doing in the right way.

Q. I tried this with chrome by disabling wifi and enabling wifi and it works but on mozila it is not working. I am getting state as stable and that is why it is not reconnecting?

Q. Can you advise me how should I handle this on the player side? Is the same logic we should try after play started?

Thanks

Nagendra

[Tahir]

Hi Nagendra,

 

After this I tried it on firefox in ubuntu 18.04, it is working fine like in the screenshot, what is your ant media version or firefox version? Maybe it is related with something like that. Can you explain your steps when creating that situation.

All streams are closed in the server side when the websocket connection is closed, so we need to initialize a new instance of webrtc adaptor. On the player side, I think using the same adaptor will be ok, but you will get error callback as no stream with this name when there is no connection if you keep calling play when the connection is lost so you need to handle that.

Thanks,

Tahir

 

 

[Nagendra Kumar1648581702]

Hi Tahir,

   Thanks for taking care of this issue. I can repro this issue in 100% of the cases.

Steps are easy...just start publishing and switch off wifi. Switch wifi and publishing should itself.

Steps to repro

Open this link https://www.instahelo.com/registration/test  in mozila

  This is going to immediately start publishing to our server. I have added logs to print the state of webRTCAdaptor.signallingState

Once publishing is in progress. Switch off the wifi and make it on after 10 seconds. Then check the status of signalling State 

SignallingState is always stable and as a result, there is no reconnection retry. In fact, we are getting error callback that the connection is closed but in that case Signalling is still stable

In Chrome signalling state comes as null

My ant-media-version -   Enterprise Edition 2.0.0 20200504_1748

Firefox version: 81

Screenshot from Mozilla

EmbeddedImages-68/0.jpg

Thanks

Nagendra

[Tahir]

Yes, your link is creating the same situation in my firefox. It seems like there is an instability since I recreated the same situation in chrome (in firefox it works) with my version. I am creating an issue about this to investigate https://github.com/ant-media/Ant-Media-Server/issues/2559