Firefox Nightly 36.0a1 (2014-11-11) - Why, when making a WebRTC call, do I seem to successfully ring the destination but on destination answer there is no audio
I have built a simple website (www.badtothebone.wtf). At the bottom of each page on the site, there is text "Call from your WebRTC enabled browser - " and below that a click2dial link - "http://click2dial.org/u/YWRtaW5AYmFkdG90aGVib25lLnd0Zg==". This works well and as intended on current Developer and Canary versions of Chrome and on Opera Developer. In Firefox Nightly 36.0a1 (2014-11-11) I can hear the destination ring after the "enabling the microphone" step, but there is no further audio in Firefox. Call logs indicate the call did connect to the destination (where a message is played and a message may be left).
Giải pháp được chọn
After doing extensive reading and research regarding this issue, I have found that it is a known problem with how Firefox differs from Chrome and Opera in establishing a DTLS handshake required for click2dial. This apparently can be addressed by creation of a self-signed OpenSSL certificate. I have additional research to do prior to creating my certificate but now realize that the problem is solvable. As initially reported, it works as intended in Chrome and Opera.
Đọc câu trả lời này trong ngữ cảnh 👍 0Tất cả các câu trả lời (2)
On normal wired telephone systems, if you dial a number, and the connection goes thru, the phone at the callers end starts ringing. However, this does not mean that the receiving phone is ringing. I know that if there is a problem with the line, the current phone system gives no kind of error.
Long ago, if you tried calling someone, and there was a problem, you did get tones that would tell you there was a problem. But not today ? ! ? !
Giải pháp được chọn
After doing extensive reading and research regarding this issue, I have found that it is a known problem with how Firefox differs from Chrome and Opera in establishing a DTLS handshake required for click2dial. This apparently can be addressed by creation of a self-signed OpenSSL certificate. I have additional research to do prior to creating my certificate but now realize that the problem is solvable. As initially reported, it works as intended in Chrome and Opera.