Tech

Setting up Thinq.io SMS with the Vodia phone system

Published on:

July 12, 2022

Setting up thinq.io SMS on the Vodia phone system involves several key configurations within the thinq.io user portal. First, you must configure your thinq.io number to support SMS. Next, set up the IP allow list by adding your Vodia phone system's IP address under Messaging. For messaging URLs, specify your DNS for both inbound and outbound messages, being sure to select the appropriate formats. After creating your API tokens in thinq, record your Account ID for Vodia integration. Finally, navigate to the Vodia system settings to input thinq.io details and enable SMS for user extensions, ensuring unique SMS numbers for each user.

Setting thinq.io SMS on the Vodia phone system isn't that difficult, but e will need to set up a few configurations in the thinq.io user portal.

Configure your thingq.io number to use SMS

thinq number

Setting up IP Allow List

In this section, you will need to add your Vodia phone system IP address under Messaging

Ip watch

Setting up inbound and outbound messaging URL

  • Outbound Messages settings: Enter your DNS - for example https://YourDNS/recvsms
  • Chose "JSON"
  • Inbound Messages Messages settings: Enter your DNS - for example https://YourDNS/recvsms
  • Choose "URL"
configureing sms

API

Thinq API is found below - it's called "Tokens." Please take a look at this example. Once you have created your API tokens, you should see the Token user and Token key itself. You will need this information for the Vodia phone system.

api

User profile

Thinq user profile information is necessary, as the "Account id" Isn't shown with the API.

Write your "Account ID" number, as we will use this on the Vodia phone system.

user

Phone System SMS Settings

Navigate to your Vodia phone system "System Level," then go to "Messaging" -- Notifications  

  • Provider : Thinq
  • Username or account: Thinq user account found in a user profile which consists of 5 numbers
  • Application ID:  User Token user from API list
  • Text messaging-enabled for domains by default is "optional"
  • URL Prefix: recvsms
  • Address for pulling MMS content: https://YourDNS
  • Default ANI for sending SMS messages:  Thinq phone number configured for SMS

Save the configuration.

Please check below for visual aid.

thinq

Under the extension "ANI for SMS" you must use the SMS number programmed on thinq. This has to be done for all the users in the tenant. but the SMS number cannot be the same - SMS work individually, just like smartphones ;)

s

Testing it all out

Navigate to your Vodia user portal, dial a number in your home page and press the MSG icon to send an SMS to a cellular user.

1

Latest Articles

View All

Podcast | Why Hotel Room Phones Still Matter in the Age of AI

Hospitality is undergoing a major shift as AI and cloud telephony reshape guest interactions. In this podcast, Christian Stredicke discusses which changes genuinely improve hotel operations and guest experience, why room phones still matter, and how modern PBXs can balance automation with the human touch that defines real hospitality. He also examines on-prem versus cloud deployments, renovation timing, emergency calling, and the ways the right system can reduce costs while raising service quality.

December 10, 2025

Seamless Compatibility: Htek and Vodia Announce Joint Webinar

Vodia and Htek are hosting a joint webinar to showcase the seamless compatibility between the Vodia PBX and Htek’s full IP phone lineup, including the UCV(Pro) smart video series and UC900 business phones. Eric Altman and Hector Hao will present key insights on product capabilities, cost-effective deployment, industry use cases, and provisioning workflows, with Stephen Yu joining for live Q&A. Attendees will learn how the combined Vodia Htek solution delivers a powerful, scalable communications experience for education, hospitality, and other sectors.

December 9, 2025

FCC Revises Cybersecurity Requirements for Telecommunications Companies

The FCC has reversed its January 2025 cybersecurity ruling for telecom providers, eliminating the proposed national standards and annual certification requirements under CALEA. The change reduces formal compliance obligations, but it does not lessen the risks facing carriers as cyberattacks grow more frequent and more sophisticated. The reversal underscores how essential it is for service providers to rely on platforms built with strong inherent protections.

November 27, 2025