New answers tagged

0

The configuration and the call setup looks OK. The 200 OK response would be very important to see. Also you should enable webrtc logs in the browser and check that also (or submit here) so we can see where it is actually sending the (DTLS encoded) SRTP. Here is a detailed description about WebRTC setup in Asterisk 13. Also it might worth to try to run ...


0

Indeed, try direct DNS route via hosts file, and also try using Google public DNS instead of relying on your ISP finding the correct site swiftly. And did you run a bunch of tests on webpagetest.org ? It may indicate whether it's DNS or just Time To First Byte issues.


0

When the server is not responding, you can try to browse it using its ip address. If you can browse with ip so the problem is the dns otherwise you have other issue.



Top 50 recent answers are included