For partners that build or integrate commercially available applications and service solutions with the Oracle Cloud Platform
For partners that provide implementation or managed services around Oracle Cloud Applications
Hi All,
I was able to import, along with support, the accelerator since I had 2 files with errors.
Now, this accelerator, unlike the accelerator of the AgentDesktop, does not have a utility to simulate an incoming call.
I'm diving the code but it's getting harder than expected.
thanks, Regards.
Hey there Matias, cant work out from what you wrote where you are having a problem? I have a fair bit of experience with Twilio so will try to help you once I know more about your issue.
From my experiences with Twilio, you dont need a "simulator". With the configuration of Twilio you will end up with a Twillio account with some free credit and a real phone number you can call with your mobile. From what I have skim read of the accelerator you have everything you need. What exactly is the problem?
Hi Richard,
Thanks for your comment!
The problem is not with Twilio, the problem is with the Distributed Accelerator.
Currently I do not have a Twilio account and it is a long journey related to definitions and bureaucracy of my company.
The design and logic of the accelerator (BUI Extension) causes the controls to be hidden or displayed dynamically. This means that I can not simulate an incoming call without having the integration ready.
Agentdesktop the accelerator is a utility to simulate this without having to wait hiring the PBX.
On the other hand, I read the page Twimlets (Twilio Labs) but that information is not the same as the accelerator asks me to integrate.
Regards.
Hi All,
I have developed a button inside the accelerator to simulate an incoming call and to be able to advance with the graphic layer development without needing to have Twilio configured.
Attach file ctiTelephonyAddin.html, ctiViewHelper.js and ctiTelephonyAddin.js
Inventory to modifications to Button Test call incoming:
- ADD id="test_make_call" class="button button-blue" in ctiTelephonyAddin.html
- ADD CtiViewHelper.simulateIncomingCallDialPadControls = function (simulate) in ctiViewHelper.js
- $("#test_make_call").off().on("click", simulate);
- ADD ctiViewHelper_1.CtiViewHelper.simulateIncomingCallDialPadControls(this.simulateIncomingCall) in ctiTelephonyAddin.js
- ADD this.simulateIncomingCall in ctiTelephonyAddin.js
- CREATE https://es.gravatar.com/userimage/134063002/89c3ce965680613d067fa048b13a099b.png?d=mm
- ADD var sampleMessage = {"success":false,"contact":{"name":"SimulateIncomingCall","firstName":"Matias","lastName":"Buonavolonta","phone":"437512785","email":"mbuonavodt@gmail.com","dp":"https:\/\/es.gravatar.com\/userimage\/134063002\/89c3ce965680613d067fa048b13a099b.png?d=mm"}}
That is awesome Matias!!
Thanks for the contribution.
Hi All,
I have developed a button inside the accelerator to simulate an incoming call and to be able to advance with the graphic layer development without needing to have Twilio configured.
Attach file ctiTelephonyAddin.html, ctiViewHelper.js and ctiTelephonyAddin.js
Inventory to modifications to Button Test call incoming:
- ADD id="test_make_call" class="button button-blue" in ctiTelephonyAddin.html
- ADD CtiViewHelper.simulateIncomingCallDialPadControls = function (simulate) in ctiViewHelper.js
- $("#test_make_call").off().on("click", simulate);
- ADD ctiViewHelper_1.CtiViewHelper.simulateIncomingCallDialPadControls(this.simulateIncomingCall) in ctiTelephonyAddin.js
- ADD this.simulateIncomingCall in ctiTelephonyAddin.js
- CREATE https://es.gravatar.com/userimage/134063002/89c3ce965680613d067fa048b13a099b.png?d=mm
- ADD var sampleMessage = {"success":false,"contact":{"name":"SimulateIncomingCall","firstName":"Matias","lastName":"Buonavolonta","phone":"437512785","email":"mbuonavodt@gmail.com","dp":"https:\/\/es.gravatar.com\/userimage\/134063002\/89c3ce965680613d067fa048b13a099b.png?d=mm"}}