Live Call Routing using Vonage
Live Call Routing empowers your organization to route incoming calls directly to on-call responders, ensuring the timely and efficient handling of incidents.
In Vonage:
- Create a Vonage account
- Go to the Vonage website. (Sign up for an account if you don't have one already)
- Purchase a phone number.
- Once logged in, navigate to the Buy Numbers under the Phone Numbers section.
- Purchase a phone number that you will be using to route the calls.

- Obtain an API Key and Signature secret:
- In your Vonage dashboard, locate your API Key and Signature secret
. These are typically found in your API settings under Control or on the dashboard homepage.
- Copy the API Key and Signature secret

In Zenduty:
- Log in to your Zenduty account as an Admin/Owner.
- Navigate to the 'Accounts' section.
- Go to 'Call Routing' under the 'Connections' tab.

- To configure call routing, paste the copied data into the respective fields in your Zenduty call routing configuration (API Key and Signature secret for Vonage)
- Enter the purchased phone number without brackets.
- Select the services you wish to include (maximum of 10 services).
- Set the timeout duration in seconds (e.g., 30 seconds).
- Choose the condition under which an incident is created (e.g., "no answer", "always", "never").


- Save your Settings.

Note: After saving your configuration, a webhook URL will be displayed. Please keep it safe for future use.
In Vonage:
- In your Vonage dashboard, navigate to the voice settings from the sidebar menu.
- In the sidebar panel, select Applications and Add a new application.
- Fill in all the required details.
- Set the answer URL to the webhook URL you saved in the previous step.
- Select the method as 'GET' and save the application.
- Add the Region if you want the calls to be redirected to the selected region
- Click on 'Generate new Application' to save the setting
- Next, review the numbers listed below and link the one you'd like to use for routing.



Once these steps are completed, calls will be routed to the on-call users based on the service configuration, and incidents will be created based on your chosen conditions if no one answers the call.