Mike Jerris
b2447967c6
FS-11287: [verto] update verto-min.js
2018-09-05 20:23:01 +00:00
Brian West
5fa0a04b9b
update adapter.js
2018-07-24 07:21:47 +00:00
Anthony Minessale
1a2d406e86
FS-10862: [freeswitch-core] Updates on webrtc to keep up with browsers #resolve
2018-07-24 07:21:38 +00:00
Anthony Minessale
dacca35a18
FS-10688: [verto.js] Add hack for IOS11 #resolve
2017-09-20 18:00:39 -05:00
Brian West
fbd07d810d
FS-10688
2017-09-20 09:29:17 -05:00
Anthony Minessale
0ef7be6327
FS-10688: [verto.js] Add hack for IOS11 #resolve
2017-09-20 09:15:56 -05:00
Mike Jerris
9127c41316
Merge pull request #1031 in FS/freeswitch from ~THEHUNMONKGROUP/freeswitch:feature/FS-9683-pass-call-recovery-status-to-verto to master
...
* commit '34e491ffa1dca32846d1e0fb97e71f5ac7c34d22':
FS-9683: Pass call recovery status to Verto
2017-08-10 18:41:39 +00:00
Anthony Minessale
4d32ca9826
FS-10420: [verto.js] Verto on Safari -- some more tweaks
2017-08-05 13:17:54 -05:00
Anthony Minessale
89e3a7bb4a
FS-9979: [verto.js] When verto client rejects a call returns hangup cause NORMAL_CLEARING #comment passing neither cause or causeCode will result in normal clearing, passing either one of cause or causeCode will result in that value being passed and parsed on the server side, if the cause is valid it will be accepted otherwise it will try to validate causeCode instead, if neither are true it defaults to normal clearing #resolve
2017-07-13 12:52:04 -05:00
Chad Phillips
34e491ffa1
FS-9683: Pass call recovery status to Verto
...
Previously, users implementing a Verto workflow where both user login and
placing a new call are automated (eg., visiting a URL, and the videoconference
loads automatically) faced the challenge of not having a reliable way to know
that a page load will result in Verto's call recovery mechanism reconnecting
an existing detached call or not.
This adds a verto.clientReady JSON-RPC message, emitted after all calls are
re-attached, which contains a 'reattached_sessions' array, containing the
sess_id of any reattached session.
Client side, this can be caught in the onMessage handler, under the
$.verto.enum.message.clientReady key.
2017-07-06 13:54:08 -07:00
Anthony Minessale
cda7343841
FS-10420: [verto.js] Verto on Safari #resolve
2017-06-22 16:43:11 -05:00
Anthony Minessale
b4156f0984
FS-10360: [freeswitch-core,verto.js] FireFox Screen Sharing
2017-06-02 12:46:39 -05:00
Anthony Minessale
6b3cef9df2
FS-10360: [freeswitch-core,verto.js] FireFox Screen Sharing
2017-06-01 18:40:50 -05:00
Anthony Minessale
58b163e08d
FS-10360: [freeswitch-core,verto.js] FireFox Screen Sharing #resolve
2017-06-01 18:36:38 -05:00
Anthony Minessale
c07ad8c263
FS-10285: [verto.js] Device enumeration in Edge -- remove debug
2017-05-02 17:27:43 -05:00
Anthony Minessale
eafdc9d75b
FS-10285: [verto.js] Device enumeration in Edge #resolve
2017-05-02 17:12:24 -05:00
Anthony Minessale
04fe009a15
FS-9742: [mod_conference,mod_cv] Refactor canvas zoom code
2017-03-21 10:31:02 -05:00
