- How to forward calls using Voice API
- How to forward calls to VoiceXML
- How to forward calls to a SIP endpoint
- How to forward calls to my mobile/cell/land line number
You have four options for handling inbound calls to a Nexmo voice-enabled virtual number (DID). You may forward the call to:
1) an Voice API Application
2) another voice-enabled number directly
3) a SIP address
4) a VoiceXML script
Forward to Application (Voice API)
1) You can configure the application ID in Dashboard, by setting "Voice Setting" to "Forward to APP", once you have created your application using the Application API, referencing your NCCO and Event endpoints.
When we receive the call, we connect your call and run the parameters specified in your NCCO. You can play text-to-speech, play audio, create voicemails, start conferences, IVR menus and much more.
Example use cases can be found on our Tutorials.
Forward to Phone
2) You can configure the forwarding number in Dashboard, by setting the "Voice Setting" to "Forward to Phone" and entering a number in international format.
Forward to SIP
3) You can configure the forwarding address in Dashboard, by setting the "Voice Setting" to "Forward to SIP" and entering the SIP URI in the format of IP email@example.com or a SIP address firstname.lastname@example.org
There is no authentication for inbound calls, however you can limit the requests to only our subnets.
Best practice is to set: 12345@your.IP.address or email@example.com
Forward to VoiceXML (Deprecated Call API)
4) You can configure the VoiceXML URL in Dashboard, by setting the "Voice Setting" to "Forward to VXML". Once you have created a VoiceXML script and are hosting it on a web server you can configure the VoiceXML URL against each voice number.
When we receive the call, we connect your call and run the script. You can play text-to-speech, play audio files, create voicemails, create IVR menus with call transfer or transfer the call to a phone number.
If you are using a firewall, you should whitelist the following IPs:
We discourage anybody from using HTTPS for VoiceXML URLs, as we are only able to support SHA-1 certifications which are vulnerable. We advise all of our customers to use HTTP for the VoiceXML URLs.