Jump to content
  • 0

WebRTC taking 4+ seconds to do handshake after publish call


Divyanshu Kalra
 Share

Question

  • Answers 4
  • Created
  • Last Reply

Top Posters For This Question

Top Posters For This Question

Posted Images

4 answers to this question

Recommended Posts

  • 0

Hey,

 

I have attached the report of webrtc test. I dont think it is due to network params. I did some digging, and it seems takeCandidate is being exchanged multiple time, as mentioned here: https://ant-media-docs.readthedocs.io/en/latest/WebRTC-Developers.html#publishing-webrtc-stream . Is there a way to reduce this? It can help cut down the time. 

Version: ant-media-server-enterprise-2.1.1-20200902_1011

 

 

screencapture-test-webrtc-org-2020-10-02-08_02_30.thumb.png.6d856d7ec6ec1da6b91c60a60d937abd.png

Link to comment
Share on other sites

  • 0
Hi Divyanshu,
   I think you are right. I have similar observations. We are publishing from us west and server is in india. Aws latency is 600-700 ms so total setup time is around 3 seconds. When we tried with aws west servers (aws latency 50ms) then  total  setup time is 0.7 seconds. So call setup time depends on no of exchanges (in setup) and how far is server located 

Thanks
Nagendra

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.

Guest
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.

 Share


×
×
  • Create New...