Processing voice calls in SDKs

This article will guide you through the process of creating and utilizing call functionality within your web or mobile application.

Before integrating calling functionality into your web or mobile application, you must first create your application, import our SDK, establish a connection with Voximplant, and log in with your user. For more information on how to accomplish this, refer to this guide.

In your application, prepare the call settings before you make a call. Then use the call method to make a call from the application to the scenario.

Specify the destination you want to call in the first parameter of the call method. This parameter can be a user, phone number, or SIP address.

After you start a call in your mobile or web application, you receive this call in the platform. Create a proper routing rule to match the destination in the first parameter of the call method in your SDK.

In the scenario, depending on your destination (a user/phone number/sip), call one of the methods described in this article to create a proper call. You can retrieve your call destination value from the e.destination property. Then unite the application call and the scenario call via the easyProcess method.

Use the hangup method in your application to end the call.

All the incoming calls in Voximplant are processed by routing rules. Before you process an incoming call, create a routing rule and set it up for your specific scenario. Follow this guide to learn how to do this.

To make calls into an application, you need to call a user that is currently logged into the application.

Then, in the application, subscribe to the IncomingCall event, and use the call.answer event to answer a call or the call.decline event to decline a call.

Refer to the API Reference of your platform to find information about the methods. Here is a code example of how to answer and decline a call in a Web/iOS/Android application:

Q: What happens if I close the app on iOS/Android during an active call?
A: On iOS, if you want a call to continue while the app is in the background mode, you need to specify the background modes while creating the app. When you close the app by swiping it from the app manager, the app closes and the access to camera and microphone terminates. The call will end by the timeout (30 sec) on the Voximplant Cloud side. You can specify to hang up the call at app closing in the AppDelegate, then closing the app leads to immediate call termination.
On Android, if you want a call to continue while the app is in the background mode, you need to specify the foreground mode as it is shown in this demo. With the foreground mode, when the call starts, a notification about an active call appears. Then, even if you close the app by swiping it from the app manager, the call remains active because the foreground service still executes the part of the application.

Q: I want to make a button for my website that accepts some data, like phone number and customer name, and makes a call. How can I implement this?
A: You can implement it manually from scratch using our Web SDK or use our ready-to-use Click-to-call widget for websites.

Q: Can I call stationary or mobile numbers without a caller ID?
A: No, you cannot. You need a caller ID to make calls to phone numbers. You can use your own phone number, but this feature has limitations, for example, you cannot use Russian mobile numbers. If you rent a phone number from Voximplant, there are no limitations.

Q: I want to integrate VoIP calls into my existing application to make user-to-user calls. I have thousands of users. Do they need to be registered as Voximplant users? How do I authorize the users?
A: The VoIP calls are available only between registered users. If you have large numbers of users, you can use the Management API's AddUser method to register users on our platform. You can use the one-time key for your user authorization and then use the callUser or callUserDirect to make calls.

Here you can download our voice calls demos for multiple platforms for your instance: