#3466 - Twilio deprecated js 1.1 end of life
Hi, I would like to know whether you are aware that twilio javascript version 1.1. is deprecated and will reach its end of life in February 14th 2018. If you are aware, should we expect a new version coming up soon?
As Twilio mentions here: https://www.twilio.com/docs/api/client/twilio-client-javascript-sdk-11-12-migration-guide
" - The JavaScript library will no longer be served from our CDN. - Connections made with the deprecated library will be refused. - Twilio Support will no longer address questions on deprecated libraries. "
All connections will stop being served and making call functionality will stop working.
Please advice on how we should proceed with this.
Thank you in advance.
- Using: SugarCRM Enterprise version 7.9.0.0
6 years ago
Hi,
Thank you for reporting this issue. We will inform you when there is an update coming.
Kind Regards, Rolustech Support support@rolustech.com
6 years ago
Hi,
We have updated RT Telephony to cater the changes that are planned by Twilio regarding javascript version 1.1. being deprecated. The new version is **RT_Telephony_Sugar7_V3.3.1.zip **. You can use that version of RT Telephony.
Please let us know if you face any difficulties or have any questions.
Kind Regards, Rolustech Support support@rolustech.com
6 years ago
Hi, we have finally found the time to integrate the new version of RT_Telephony_Sugar7_V3.3.1.zip. However, calls hang to "RUNNING DEVICE SETUP".
As far as I understand the only change done was this line from twilio.min.js: $.getScript('//static.twilio.com/libs/twiliojs/1.1/twilio.min.js', function (response, status) { to $.getScript('//media.twiliocdn.com/sdk/js/client/v1.4/twilio.min.js', function(response,status) {
Correct? Cause when i change the v1.4 string to 1.1, the plugin works like a charm.
Any ideas what may cause this issue?
6 years ago
Hi,
The plugin seems to be working fine on our end.
Can you please share a screenshot of running a Twilio test from the link below,
https://networktest.twilio.com/
Thanks, Rolustech support@rolustech.com
6 years ago
Screenshot above.
We have noticed that when using the 1.1 version, the Twilio.Device.Offline is called when we open the drawer, then Twilio.Device.Ready is re-called and thus deviceReady is set to True and buttons become enabled, while in v. 1.4, Twilio.Device.Ready is never re-called when the drawer opens and it never falls into the
if-block. This leaves deviceReady to false and buttons remain disabled.
Any ideas why?
6 years ago
Hi,
Our team will look into it and we will get back to you shortly.
Thanks, Rolustech support@rolustech.com
6 years ago
Hi,
We can not seem to reproduce the error on our side.
Can you please share the access to your instance with us on support@rolustech.com?
6 years ago
Unfortunately, I am not allowed to share access to our instance due to security protocols. However, we could arrange a call-meeting of sorts, to see the instance live through screen sharing etc.
Please let me know how you would like us to proceed.
Thank you.
6 years ago
Hi,
Sure we can schedule a call and have a look in to your system like that.
Since we do not have an email ID of yours, can you please mail us at support@rolustech.com and we can schedule a time for the meeting from there.
Regards, Rolustech Support support@rolustech.com