F.A.Q.

VoxImplant Web SDK lets you build apps that can make and receive calls right in web browser. VoxImplant Web SDK establishes connection with VoxImplant Cloud and work together with VoxEngine apps running in the cloud. VoxEngine apps describe call control logic. Please check Web SDK Reference for more details.

Web SDK supports all modern desktop browsers, depending on the browser and its version Web SDK can use either WebRTC or Flash technology. Some new mobile browsers are supported as well.

Related articles

Does Web SDK support mobile browsers?

Web SDK should support any WebRTC-enabled browser, we know only one mobile WebRTC-enabled browser so far - Google Chrome for Android ver. 29 or higher. We are sure that the list will grow fast in the near future and we will update this article accordingly.

Related articles

What browsers does Web SDK support?

Yes, Web SDK supports video calls, but you can make video calls between two peers only when the Web SDK operates in the same mode on both of them (WebRTC or Flash). Peer-to-peer calls are supported only for WebRTC mode. Learn more in our Peer-to-peer video chat tutorial.

We don't recommend to do that, because we constantly improve both client and backend it's important to use the latest version of VoxImplant JS lib to avoid interoperability issues.

While there are sure to be VoxImplant uses beyond our current thinking, some examples off the top of our heads include softphones, click-to-call, automated surveys, cloud contact center or PBX, cloud IVR and call tracking. We don't want to limit your imagination, please let us know what you built, we are happy to add more examples to the list!

There are few options available: get phone number from VoxImplant or connect your existing number using SIP. Learn more in our Phone number connected to IVR tutorial.

VoxImplant Application is a set of call-processing rules and users that can use it. When you create an application, you need to specify, which users will have access to it. This list, of course, can be modified later.

Related articles

What is VoxImplant Scenario? What is VoxImplant User? What is VoxImplant Application Rule? How VoxImplant Applications, Scenarios, Users, and Rules are related?

Call control scenarios are written in Javascript and executed directly in the VoxImplant Cloud, they give you full control over any calls.

Related articles

What is VoxImplant Application? What is VoxImplant User? What is VoxImplant Application Rule? How VoxImplant Applications, Scenarios, Users, and Rules are related?

To make or receive calls using VoxImplant, users have to introduce themselves. You can define any number of users in your account, so some people will be able to authenticate into the application using a specified username and password. Please note, a user alone can't make a call. You will need to assign it to an application so that the corresponding call processing scenario will take place. Each user can be assigned to any number of applications, and they can log into them separately.

Related articles

What is VoxImplant Scenario? What is VoxImplant Application? What is VoxImplant Application Rule? How VoxImplant Applications, Scenarios, Users, and Rules are related?

VoxImplant Application Rule is a criteria to be tested on dialed number that specifies which call scenarios will be executed for specific call. Each rule has 3 parameters:

• Pattern - a regular expression that a dialed number will be checked against. Please note that this expression is applied to a whole number, so if one dials the number 123456, it will not match the pattern 123, but it will match pattern 123.+
• Exclude pattern - an optional regular expression that a dialed number will be tested against. If they match, the rule will be marked as not matching the number.
• Scenarios - a list of the scenarios that will be executed in the specified order when a rule will match.

Related articles

What is VoxImplant Scenario? What is VoxImplant Application? What is VoxImplant User? How VoxImplant Applications, Scenarios, Users, and Rules are related?

When a call arrives to VoxImplant, and it decides that it belongs to the current application, the rules of the current application are being checked in order. When the first rule, that has the Pattern that matches the dialed number and Exclude Pattern that doesn't match dialed number, is encountered, all scenarios assigned to that rule are executed in order. After that no more rules are checked for the current call.

Related articles

What is VoxImplant Scenario? What is VoxImplant Application? What is VoxImplant Application Rule? What is VoxImplant User?

We accept Visa and Master Card or we can create an invoice for wire transfer.

When your account balance reaches zero you will no longer be able to make and receive phone calls or send SMS messages.

Calls rated on a per minute basis; partial minutes rounded up for billing. For example, if call duration is 4 minutes and 19 seconds it will be rounded up to 5 minutes for billing.

Total call cost depends on various parameters, we have created cost call visual calculator, it's available in Pricing

Yes, you can enable in VoxImplant Manager if you have specified credit card information. It will automatically recharge your balance when it falls below a chosen threshold. You can specify the threshold amount and the amount that will be withdrawn from the card and added to your VoxImplant account balance.

Yes, we do. For more information on bulk discounts and volume pricing, please send an email to our sales team at sales@voximplant.com.

VoxEngine is heart of VoxImplant Cloud, it's application engine that runs your apps inside the cloud. Each call is processed according to call control logic written in Javascript. In addition to standard ECMA5 JS functions there is a number of VoxImplant JS functions available. Please check VoxEngine Reference for more details.

First of all, you can specify Caller ID if it was previously verified or if it's a number you got from VoxImplant. There are two ways to verify custom Caller ID: using Control Panel -> Settings -> CallerIDs or using VerifyCallerID method of HTTP API. Caller ID can be specified in VoxEngine scenario in callPSTN function as 2nd parameter.

he source code of the method is available on GitHub

HTTP API lets you control your VoxImplant account remotely via HTTP. It allows integration of VoxImplant with other services - you can create, edit or delete users, applications, scenarios, get call history, etc. Please check HTTP API Reference for more details.

Most of the apps built using VoxImplant have some client application that uses our Web or Mobile SDK , or other type of the endpoint communicating with VoxImplant (like SIP client), but there are couple of scenarios when there is no client application involved. The most common one is callback scenario, when platform makes calls to different destination and join these calls while required. Or another one – automated notifications or surveys, when you want call to your customer and playback some important message or get the feedback. Special part of HTTP API available for VoxImplant developers that makes this scenarios possible and easy to implement is called Control API (since it’s created for controlling sessions, unlike Provisioning API created to let you add/edit/delete different VoxImplant entities, like app Users, Rules, etc.). Description of the API is available here , “How To” is available at http://voximplant.com/docs/quickstart/19/making-calls-using-http-api/. Learn more in our blog post about Control API

Depending on your application you may want to launch a usual session or a conference session, there are two HTTP API methods for that StartScenarios and StartConference.

Every VoxImplant account creates its unique 3rd level domain name and every application creates its unique 4th level domain name, this names are formed in the following way - appname.accname.voximplant.com. If you have created VoxImplant application and called it, for example, testapp and your VoxImplant account name is testacc, then the domain name will be testapp.testacc.voximplant.com If you created user with username testuser and password testpwd and assigned it to the application then your credentials for SIP phone for registration or making calls will look as follows: Username: testuser@testapp.testacc.voximplant.com (or just testuser) Password: testpwd Domain: testapp.testacc.voximplant.com

VoxEngine scenarios describe how each call should be processed, so if you want to send a call from VoxImplant via your SIP server you need to write appropriate scenario where callSIP function should be used. It will send the call via server specified in the function parameters.

First of all, you need to specify list of IP addresses (or networks) that are allowed to make calls through your VoxImplant account without SIP authorization at https://manage.voximplant.com/#sip. Then calls can be forwarded to your application by specifying application rule accordingly and handled in VoxEngine scenario using CallAlerting event.

We have special web service that returns IP addresses of the servers used for different purposes: http://api.voximplant.com/getMediaResources To get the list of addresses where SIP comes from (SBCS): http://api.voximplant.com/getMediaResources?with_sbcs To get the list of addresses where RTP (media) comes from (Media Servers): http://api.voximplant.com/getMediaResources?with_mediaservers To get the list of addresses used by SDKs (Web/Mobile): http://api.voximplant.com/getMediaResources?with_webgateways You can also combine params to get more all info in one request.