Open ivelin opened 7 years ago
I built the app with RVD and exported as zip. Works like charm on my restcomm cloud account. Attached. Voice Echo.zip
@otsakir reassigning it to you. I know we discussed it already I think on slack
The tricky part here is how shall we apply custom handling for only some of all created IncomingPhoneNumbers so that they are assigned the VoiceEcho application. Doing this for all numbers is wrong. It also seems wrong to have such kind of automation hardcoded inside rcomm core.
This looks like a good fit for a retscomm extension. Create "OnAccountCreate" and "OnDIDCreate" hooks and let the extension .jar apply the customized bahavior.
It is also important which accounts/numbers these demo applications should be activated for. @ivelin , @deruelle any ideas on that ?
For example:
Crystalizing these rules will help have a cleaner implementation path when the time comes to write the extension.
I've also discussed the extension idea with @gvagenas and agrees it's in the right direction.
It was more to include those default apps out of the box like the test apps we bundle right now and in dashboard drop down list when you need to choose an application when you provision a new number to have that app as default.
Update here? Logging into a new RaaS account this morning, I noticed that there are no default apps still.
The SMS default app #1804 is also waiting.
Users often try to call a new number they just registered. They expect something rewarding to happen. Currently the call hangs up and they think something is wrong.
We should offer a more rewarding default behavior. For examples a simple voice echo app similar to the Skype Echo app. Play a prompt, explain to user that their voice will be recorded and played back, record, play back, explain where the user can go to find out more about Restcomm voice apps.
https://support.skype.com/en/faq/FA265/how-do-i-test-my-sound-is-working-in-skype-make-an-echo-test-call