Currently set to Index
Currently set to Follow

Twilio Voice Hardcoding

If your Twilio library is working and you don’t want to add any additional programming or libraries to your project, use our hardcoding option to take advantage of thinQ’s inbound and outbound calling technology.

Twilio Voice Hardcoding

If your Twilio library is working and you don’t want to add any additional programming or libraries to your project, then you can use our hardcoding option to take advantage of thinQ’s inbound and outbound calling technology.

Let thinQ handle the routing of your Twilio calls, while Twilio manages and manipulates your calls. Hardcoding thinQ into Twilio Voice is a great option for developers who are already using Twilio and do not want to make any major changes to their existing code, but are interested in saving up to 50% on calls and having more control of their routing and higher reliability. No additional libraries and software are required to be installed with this option, just a simple text change needs to be made.

How Does thinQ Hardcoding Work?

By changing a simple parameter that is sent to Twilio in your Twilio Library code, Twilio will re-route your outbound calls as a SIP call to thinQ. Our cloud communications platform will route your your calls for you, unlock higher quality voice, give you full control – and save you money in the process.

The parameter to change is the TO phone number. Change this parameter from the format or just the phone number, “19191231234”, to the new format of: 

 

sip:12155551212@wap.thinq.com?X-account-id=01234&X-account-token=567890

How Do I Get Started?

To get started just sign up for a test account with Twilio enabled, then go into your existing code that is already working with the Twilio Library.

Change the existing TO phone number to the above format to replace what is in the TO field with this information to have your calls sent to thinQ. 

Before:
Twilio Code Before thinQ

After:
Twilio Code After thinQ Hardcoding

The thinQid and thinQ token parameters need to be sent with the call for authentication purposes. You can get the values of these parameters by logging into your thinQ account.