My real interest in Signalwire is to do some digging into their integration capabilities/solutions with freeswitch, so from that venue the bonus starter was great. But 3/4 of a penny per minute rounded to 1 mn is still in the same league as callwithus which charges 0.9 cent/mn with 1mn rounding. As I said in my post they charge you for everything even for calls that didn't go through and they are not particularly competitive. You will use both pieces in your registration string and peer settings with chan_sip.Īs for the pennies for the verification calls, you're right.
When you create the SIP endpoint on Signalwire make sure that in addition to the user name you create a password (right below the username box). I did not white list any of their numbers. Once the CodeSandBox is open, upload your google-key.json file to the root directory of the project.: I used a chan_sip trunk per ward's post further up in this thread, with a small change I did not use a /DID at the end of the registration string as there will be no incoming calls. You can follow the instructions in the GitHub repository on how to run this locally or you can use a CodeSandBox we’ve created that is ready to run. Upon completion you will have downloaded a JSON file with your google key.
To access the Google Speech to text and language translation API, you need to create an account and some credentials.īe sure to include permissions for the translation API as well. That audio file is downloaded and then passed to the Google Speech and Translation API. Their response is recorded by SignalWire and a URL where the wav file containing the audio is stored is fetched from the RELAY API. When the RELAY consumer receives a call it will prompt the user to leave a message and press the # key. Set the Relay context that your phone number forwards to as translator Google Speech and Translate
0 kommentar(er)
