Open GoogleCodeExporter opened 9 years ago
GoogleCodeExporter
commented
9 years ago Hi Florin,
have you managed to solve this issue? we're experiencing it as well, and it's
driving us crazy.
LorenzoOriginal comment by lmini...@gmail.com on 8 Jul 2013 at 9:39
GoogleCodeExporter
commented
9 years ago Just to add a few more details about what we found out about the issue, it
looks like a state machine issue. In our scenario, both the caller and the
callee are handled by the webrtc2sip gateway, which is a frontend to an SBC.
When the callee hangs up, webrtc2sip logs an "invite dialog terminated" event,
and forwards the BYE to the SBC. When the BYE gets back to webrtc2sip to notify
the caller, though, the gateway doesn't seem to be able to find the dialog
associated to the Call-ID anymore ("No matching state machine found"), and so
forwards the BYE as is to sipml5, which of course doesn't know how to handle it
(wrong Call-ID) and ignores it. This makes me think that something in the
application logic related to the first BYE (cleaning the session there) steps
on the other session as well while it shouldn't, messing the state machine.
Anyone else met the same issue? It's been a while since this problem was first
reported.
LorenzoOriginal comment by lmini...@gmail.com on 8 Jul 2013 at 9:54
GoogleCodeExporter
commented
9 years ago Original comment by boss...@yahoo.fr on 4 Aug 2013 at 1:16
GoogleCodeExporter
commented
9 years ago Fixed: https://code.google.com/p/doubango/issues/detail?id=292
Will be closed when fully tested and confirmed.Original comment by boss...@yahoo.fr on 5 Aug 2013 at 5:03
GoogleCodeExporter
commented
9 years ago I also have the same problem, but when I use Websocket Secure. If I change the
mode of transport to WS, it works correctly: Invoked event 'Call terminated' in
the caller when the callee hangs.Original comment by alvaro.r...@gmail.com on 13 Sep 2013 at 8:11
GoogleCodeExporter
commented
9 years ago Facing the same issue. Call won't terminate on the browser (caller) end when
the callee terminates the call and I am using WSS. I am using WebRTC2SIP and
have enabled RTC Web Breaker. The problem seems to disappear if I use WS
instead of WSS. However, Firefox does not allow a call if WSS is used and the
protocol of the site is not HTTPS. Can someone please share more details on
this. Is this a known bug?Original comment by johnsaj...@gmail.com on 19 Sep 2013 at 11:21
GoogleCodeExporter
commented
9 years ago I am also facing this issue.But only when I use Websocket Secure.Unfortunately
Firefox wont allow ws for https connections.Original comment by arununnikrishnan11@gmail.com on 20 Sep 2013 at 3:49
GoogleCodeExporter
commented
9 years ago hi.....
for Issue of WS in HTTPS ..In firefox type about:config...then search for
websocket .Then make websocket for HTTPS true..It works for me.. Original comment by soni8...@gmail.com on 1 Oct 2013 at 10:03
GoogleCodeExporter
commented
9 years ago [deleted comment][deleted comment][deleted comment]I have the same issue with ending call from callee when on wss and works ok
with ws. (using chrome 39, asterisk 13). does anyone have solution? Original comment by matja...@gmail.com on 16 Jan 2015 at 1:39
Original issue reported on code.google.com by
florin.p...@gmail.comon 20 Feb 2013 at 7:58