|
|
The features on this page require a GENESIS64 Advanced license and are not available with GENESIS64 Basic SCADA . |
|
|
The features on this page require a GENESIS64 Advanced license and are not available with GENESIS64 Basic SCADA . |
Twilio has a couple of Voice and language options that they support (https://support.twilio.com/hc/en-us/articles/223132827-What-Languages-can-the-Say-TwiML-Verb-Speak-). You can set them up in Workbench under your Twilio configuration under voice customizations.
If translations are available, IcoWebAPIService will pick up the translated strings from your system and use the voice you provide.
But if you need additional control for Twilio module at the IcoWebAPIService, here is what you can do.
You would go to C:\Program Files\ICONICS\GENESIS64\WebSites\IcoWebAPIService and open IcoTwilio.json.
This has a couple of configuration details available for IcoWebAPIService. These are overridden by WB configuration details when available.
1)Voice : Here you can change the voice to Twilio supported options(woman,alice,man etc). The language options available for each voices vary. So we should be careful to choose voices that support the language required.
2)Language: Here we tell the Twilio which language our text will be in so that it can provide the proper voice. For example, if we would be using French strings we would change “en-Us” to ”fr-FR” (Which is French European according to Twilio documentation, there is also French Canadian and you can find the different ones supported for different voices here-: https://support.twilio.com/hc/en-us/articles/223132827-What-Languages-can-the-Say-TwiML-Verb-Speak-).
Then you would create a file similar to IcoTwilio.en-US.json ending with fr-FR (IcoTwilio.fr-FR.json) with the translated strings as the values in the same folder. The keys in the json should remain unchanged.
Add the json file “IcoTwilio.fr-FR.json” with the proper translations to the folder C:\Program Files\ICONICS\GENESIS64\WebSites\IcoWebAPIService
You would then add “fr-Fr” to the “Supported cultures” under the “Localization” in appsettings.json file in the folder C:\Program Files\ICONICS\GENESIS64\WebSites\IcoWebAPIService
"Localization": {
"DefaultCulture": " en-US ",
"DefaultUICulture": " en-US ",
"DefaultCultureFallback": true,
"SupportedCultures": [ "en-US" ,"fr-Fr" ]
},
Re-start IcoWebAPIService. And it should now pick up the instructions in French.
If the translations are available in IcoWebAPIService folder already under the Twilio specified Language extension and you have configured in WB that the language should be “fr-Fr”,(or any other supported by Twilio) it should automatically pick the available translation.
Note: Voice, incoming sms support and Acknowledge of Alarms not supported for Alphanumeric Sender Ids.
We can now add Alphanumeric sender IDs as From in Phone number field in Twilio Configuration. See ref: https://support.twilio.com/hc/en-us/articles/223181348-Alphanumeric-Sender-ID-for-Twilio-Programmable-SMS
This Alphanumeric Sender Ids are supported only in some countries. See details: https://support.twilio.com/hc/en-us/articles/223133767-International-support-for-Alphanumeric-Sender-ID
Details on getting an Alphanumeric Sender ID is here: https://support.twilio.com/hc/en-us/articles/223181348-Alphanumeric-Sender-ID-for-Twilio-Programmable-SMS#h_01F4SK0WYHA75NK1DNXGTCFMP8
There are also Limitations for alphanumeric Sender Ids such as it is only used for outgoing sms and cannot be used for incoming sms, and no voice support etc. See ref: https://support.twilio.com/hc/en-us/articles/223181348-Alphanumeric-Sender-ID-for-Twilio-Programmable-SMS#h_01F4SK0DVD49N6BTMRX78RAZNE
The Format limitations for adding these Sender IDs in the Twilio Config form are as below:
Alphanumeric Sender IDs can contain up to 11 characters from the following categories:
Upper-case letters A - Z
Lower-case letters a - z
Numbers 0 - 9
Spaces
Sender IDs must contain at least one letter. Special characters and punctuation are not allowed.
Note: Some carriers may impose minimum length restrictions on Alpha Sender ID's. This can result in your Alpha Sender ID being modified or replaced by a generic sender ID i.e., "unknown".