From 1a62f1299dcf986cd70573b77ed2c7f05afa28f9 Mon Sep 17 00:00:00 2001 From: David Baker Date: Thu, 6 Nov 2014 16:55:15 +0000 Subject: Detect call type by examining the SDP always rather than just in Firefox as it seems Chrome's behaviour is the odd one out here. --- syweb/webclient/components/matrix/matrix-call.js | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) (limited to 'syweb/webclient') diff --git a/syweb/webclient/components/matrix/matrix-call.js b/syweb/webclient/components/matrix/matrix-call.js index c13083298e..0631649946 100644 --- a/syweb/webclient/components/matrix/matrix-call.js +++ b/syweb/webclient/components/matrix/matrix-call.js @@ -175,7 +175,8 @@ angular.module('MatrixCall', []) this.state = 'ringing'; this.direction = 'inbound'; - if (window.mozRTCPeerConnection) { + // This also applied to the Safari OpenWebRTC extension so let's just do this all the time at least for now + //if (window.mozRTCPeerConnection) { // firefox's RTCPeerConnection doesn't add streams until it starts getting media on them // so we need to figure out whether a video channel has been offered by ourselves. if (this.msg.offer.sdp.indexOf('m=video') > -1) { @@ -183,7 +184,7 @@ angular.module('MatrixCall', []) } else { this.type = 'voice'; } - } + //} var self = this; $timeout(function() { -- cgit 1.4.1