When we dial from the browser using WebRTC the ring back never stops, even though the far end answers the call. The far end hears silence and disconnect works as expected if either side hangs up.
At the CLI, asterisk shows that the is being answered. See screenshot attached.
Anyone else have this issue? I can create a video of the issue if it would help.
-Matt
Dialing from the Android
Dialing from the Android application does not have the same issue, ring back stops when the far end answers.
Hi Matt, you are experiencing
Hi Matt, you are experiencing this issue as your configuration lacks ICE servers configured and assigned to an extension, there will be new blog post soon regarding Connect, ICE servers, and new methods of NAT traversal, which Connect is using.
yes if you use pfSense or
yes if you use pfSense or some other BSD firewall you are shit out of luck because BSD has the worst possible implementation of NAT there is. Your only work-around is a TURN server and it will push so much bandwidth onto your server that your costs will go up A LOT. WebRTC is probably going to be the final nail in the coffin for BSD firewalls. They never were worth a damn putting Xbox or PlayStations behind them without a bunch of hoops to jump through, and even then you couldnt have two gaming consoles. Business didnt install gaming consoles so they didnt care, but realtime media applications in HTML5 are only going to increase, and no DMZ hack is going to work because no business wants to be told that only 1 single PC will be able to use it.
Screenshot