Voice API Handle Incoming Calls

How to Handle Inbound Phone Calls with Node.js

Published January 26, 2017 by Tomomi Imura

This is the second of a two-part Voice API tutorial on making and receiving phone calls with Node.js. It continues the “Getting Started with Nexmo and Node.js” series, which followed our Getting Started series on SMS APIs. See links to prior tutorials in these series at the bottom of the post.

In Part 1 of this tutorial, I showed how to create and secure an application and learned how to make an outbound text-to-voice call using the Voice API with the Node.js client library. In this tutorial, you will learn how to receive inbound calls by implementing a webhook.

GitHub icon View the source code on GitHub.

Using Nexmo Application

In this tutorial, you will use the same application that was created in the previous tutorial to receive a voice call. You also will update the application with webhook endpoint URLs. If you haven’t reviewed the first tutorial, “How to Make an Outbound Text-to-Speech Call with Node.js”, refer to the section, Creating a Nexmo Application and Generating a Private Key to create an application.

When a user calls the Nexmo virtual phone number associated with your voice application, Nexmo retrieves the Nexmo Call Control Objects (NCCO) from your answer_url webhook endpoint, and answers the call with a synthesized voice that reads the text you have specified in the NCCO.

Accepting incoming calls
Diagram 1: Using The Voice API to receive a call to your Nexmo virtual number

Nexmo also sends status information to another webhook endpoint defined by event_url. The event is triggered when the user’s handset is ringing (ringing), when the call is answered (answered), etc. You can find all the events in the API Reference documentation.

Defining Webhook Endpoints

In order to accept an incoming call to your Nexmo virtual phone number, you need to associate your voice application with webhook endpoint URLs.

Just as a previous tutorial showed how to use ngrok to receive SMS messages, let’s use ngrok to expose your webhook endpoint on your local machine as a public URL.

Run ngrok with a port number of your choice (let’s make it 4001 for now):

Your local server (localhost:4001) now has a forwarding URL, something like https://97855482.ngrok.io that can be used as your webhook endpoint during development.

Writing WebHook Endpoints with Express

Let’s handle the POST requests with Express. You will also need to install body-parser.

Create a .js file, instantiate express, and listen to the server to port 4001. Because you have set your ngrok to expose localhost:4001, you must stick with the same port.

Let’s define the endpoint for the Answer URL as /answer and the Event URL as /event.

Create an HTTP GET route to handle the requests for /answer to retrieve your NCCO:

Define your text to be read by a synthesized voice in JSON (or JavaScript object, in this case). You can customize the audio with optional params, such as voiceName, which you can choose from varieties of voices for a language, gender, and accent.

The endpoint for the event_url needs to be POST, so let’s define /event:

You don’t need to actually return anything if you just want to monitor the status in a terminal.

Updating Nexmo Application with WebHook URLs

Nexmo applications contain configuration information you need to connect to the Voice API endpoints. Previously, we used placeholders for both the Answer URL and the Event URL. Now you are going to use the Nexmo CLI to update the application information with the webhook endpoints you just defined.

You need the Application ID to update the information. You can get it from the make-call.js in the previous tutorial, or use the app:list command:

The CLI should return a list of each app ID and an app name. Now, use the correct app ID to update the application with the webhook URLs:

Associating the Info with Your Virtual Number

Finally, you need to associate your application with the virtual number you rent from Nexmo. Let’s use the Nexmo CLI again. Use the command nexmo link:app followed by the phone number, which must start with a country code and then the app ID. So, the command should look like this:

When the linking is successful, the CLI returns with the message, “Number updated”.

Testing Your Voice Application

Let’s make a phone call to see if your application works! Call your virtual number from your physical phone. If everything works, you should hear the message you have defined in your NCCO.

Also, see your terminal to check the status of your call.

In the next tutorial, you will learn how to record calls as audio files, so stay tuned!

Learn More

Here are some resources you can use to dive deeper into Nexmo APIs and Node.js.

API References and Tools

Nexmo Getting Started Guide for Node.js

Nexmo Logo

Leave a Reply

Your email address will not be published.

Get the latest posts from Nexmo’s next-generation communications blog delivered to your inbox.

By signing up to our communications blog, you accept our privacy policy , which sets out how we use your data and the rights you have in respect of your data. You can opt out of receiving our updates by clicking the unsubscribe link in the email or by emailing us at privacy@nexmo.com.