Jump to content
  • 0

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
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?

Link to comment
Share on other sites

  • Answers 3
  • Created
  • Last Reply

Top Posters For This Question

Popular Days

Top Posters For This Question

Posted Images

3 answers to this question

Recommended Posts

  • 0

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.





Link to comment
Share on other sites

  • 0
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
  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



Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Create New...