Voice FAQs: General Information

The SIP setting depends on the origin and termination of the call you wish to place. Please note, there are country wise rules and regulations, and PSTN/IP in India is not authorized.

There is no such limit on the number of concurrent calls, it depends on the need of the customer.

Users can upload .wav files to be used as pre-recorded audio.

EnableX supports recording of only bridged calls. All initial steps which occur in the voice applications before the calls are bridged are not recorded.

Yes! You can use EnableX platform to make Voice Message Broadcast. EnableX provides API to make bulk outbound calls. You can also create a scenarios either for all the calls or on individual call in a bulk calls. EnableX provides full flexibility to create a complete scenario up to per call basis.

Yes. EnableX API to play prompt accepts the text as a parameter. Internally EnableX converts the Text to speech in desired accent and gender for the text to speech to be played on the call.

Yes. EnableX provides a way to make and receive calls without the EnableX room, these services are called Voice services.

EnableX provides webhooks for conveying any event that is observed in the system.

DTMFs are handed over to the application as Events. For example, for the incoming call, DTMFs are handed over to the program through the configured WebHook while assigning the incoming call.

Webhooks are the public URLs that are exposed by the developer on the application server. The voice server calls these URLs on the event completion.

Since Webhook URLs are accessible from the public network, it is important that these services are encrypted and secured. In order to secure the data, EnableX adopts different ways to secure the Webhook both for inbound or outbound calls.

• While sending the Webhook event, the server always encrypts the payload using the AppID and also sends other headers to support encoding/format types in the webhook event.
• The server sends x-algorithm, x-encoding and x-format headers in all webhook requests, so that the client decrypts the message with the same values as the server has encrypted the message.
• The client decrypts the payload using the AppID, and the mentioned headers. This way, only the client can access the webhook message.

Check out the Handle Webhook section for more details.

EnableX provides a way to configure the webhook that is called when the incoming call lands on the system. When the incoming call lands, the system automatically accepts the call.

If the greetings are configured, EnableX accepts the call and plays the greetings, and then invokes the webhook. If the greetings are not configured, the system calls the webhook assigned for the incoming call.

EnableX keeps the pool of numbers for various counties and can be readily used by the partner. In case, if the user needs a dedicated number, the user can order the number manually via the form. The types of number are:

• Dedicated number: Dedicated numbers are purchased numbers by the user. These numbers can have DID (Direct Inward Dialling) enabled for the application, i.e. applications can accept the call with a customized greeting or with no greeting or PIN.
• Shared number: These numbers are shared among EnableX users. It is purchased by EnableX and put it on a public pool to be used by multiple consumers as pay per use model on the same platform.

Enablex numbers also have directional attributes:

• Incoming Only: Calls are inbound towards the EnableX platform from the remote users. In this selection, API to make outgoing calls will fail.
• Outgoing Only: Calls are outbound from the EnableX platform to the remote users. In this selection, API to make incoming calls will fail.

EnableX platform provides “voice service” and “video services” as separate services. These services can interoperate or coexist in the same user application but the purpose of these services differ in the use case scenario. Following are the key differences between these two services:

Video Service

• Video service creates WebRTC based “EnableX Room”.
• The PSTN/SIP call can connect to EnableX room via EnableX WebRTC-SIP gateway.
• Incoming call over PSTN can be directed into the EnableX room via a PIN-based IVR. Every room has a unique pin allocated for it.
• The incoming call number can be provisioned from a shared number or a dedicated number.
• Outbound number can be a shared number or a dedicated number.

Video Service is always associated with a EnableX Room, and is enabled as SIP room to allow legacy calls to join the room.

See server REST API to Create Room

• Voice only service use cases are usually based on PSTN/SIP calls used for the voice messaging, IVRs, number masking
• Voice only service calls are not connected to EnableX Room
• Voice only service is associated with a dedicated number, it is not possible to use a shared number. So to use incoming calls on a Voice only server number must use a dedicated number purchased by the user
• Outbound number can be shared number

Voice Service

• Voice only service use cases are usually based on PSTN/SIP calls used for the voice messaging, IVRs, number masking
• Voice only service calls are not connected to EnableX Room
• Voice only service is associated with a dedicated number, it is not possible to use a shared number. So to use incoming calls on a Voice only server number must use a dedicated number purchased by the user
• Outbound number can be shared number