Tech

Creating a Transport Layer Security (TLS) Connection between Vodia and Telnyx

Published on:

June 30, 2023

This comprehensive guide outlines the setup of a secure Transport Layer Security (TLS) connection between Vodia and Telnyx, emphasizing the crucial aspects of data confidentiality and integrity. By following the steps provided, users can establish a secure SIP trunk connection. This TLS connection guarantees encrypted and secure communication, enhancing data protection and privacy for your business.

In this blog we guide you through the process of setting up a TLS connection between Vodia and Telnyx. TLS provides secure communication over the Internet, ensuring the confidentiality and integrity of data exchanged between the two systems; by following the stops below, you can establish a secure connection for your SIP trunk.

Connecting with Telnyx 

Create a SIP registration connection in Telnyx. 

Step 1: Connecting with Telnyx

Create a SIP registration connection in Telnyx.

  • Choose "Registration" as the type, then copy your SIP password.
  • The SIP password will be required when setting up the SIP trunk on the Vodia phone system.
  • Save and finish the registration.
Create a SIP Connection with Telnyx
Register a SIP Connection with Telnyx
  • Edit the connection and enable Secure Real-Time Transport Protocol (SRTP) under "Encrypted Media".
  • Save the configuration.

Note: Outbound settings already utilize SRTP settings from the inbound settings. 

Edit SIP Connection to enable SRTP

Step 2: Configuring the Vodia Phone System

  1. Navigate to the SIP trunk to create your Telnyx connection in the Vodia phone system.
  2. Click on "Add" and select "Telnyx."
  3. Enter your Telnyx SIP account details:
    • Name: Provide a name for your trunk.
    • Password: Enter your Telnyx SIP credentials.
    • User: Enter your Telnyx user account.
    • DID: If applicable, enter your Direct Inward Dialing (DID) number.
    • Save the configuration.
  4. Configure TLS under "Proxy Address" by using the following example:
    Proxy Address: sip:sip.telnyx.com;transport=tls

Navigate to the SIP trunk to create your Telnyx connection: Click on “Add” and select "Telnyx." 

Choose Telnyx from the service provider trunk list
Add password to create a SIP Connection with a service provider trunk

Configure the TLS under "Proxy Address" by using the following example:

  • Proxy Address: sip:sip.telnyx.com;transport=tls
Proxy Address to configure TLS

Step 3: Caller ID and Phone Numbers 

To define the Caller ID used when making calls from the Vodia system, follow these steps:

  1. Define the FROM headers and Remote Party ID under the SIP caller-ID presentation:
    • Choose "custom headers" from your Telnyx SIP trunk.
    • You can set up the Domain ANI in the Tenant general settings under "dom_settings.htm".
    • Alternatively, you can set up an ANI on the extension and instruct the header to use "Extension ANI".
  2. Save the settings.

Note: Read more information about Vodia tenant level.

SIP caller-ID Presentation

By following the above steps, you can establish a TLS connection between Vodia and Telnyx, ensuring secure and encrypted communication for your SIP trunk; this added layer of security helps protect your data and ensures the privacy of your calls. Implementing TLS is a crucial step in maintaining a secure communication infrastructure for your business.

Sample inbound show TLS 

INVITE sip:9787368016@54.146.189.63:43296;transport=tls;line=02522a2b SIP/2.0 Record-Route: <sip:192.76.120.10:5061;transport=tls;r2=on;lr;ftag=jBpNrQtFDFegp> Record-Route: <sip:10.255.0.1:5061;transport=tls;r2=on;lr;ftag=jBpNrQtFDFegp> Record-Route: <sip:10.13.247.8:6051;transport=tls;r2=on;lr;tnx=461.748> Record-Route: <sip:10.13.247.8:6050;r2=on;lr;tnx=461.748>

Sample outbound show 

INVITE sip:4001@96.237.116.94:65069;transport=tls;line=shb07dy9;wrtc=true SIP/2.0 Via: SIP/2.0/TLS 54.146.189.34:443;branch=z9hG4bK-0fda88b9200ab8e60062fc693972f2e8;rport

Latest Articles

View All

Vodia Visits IT Expo 2025

Vodia was excited to attend IT Expo 2025 in Ft. Lauderdale, where Sales Engineer Eric Altman connected with industry leaders such as Tommy Lee from Fanvil, Gary Harbeck from Dinstar, Spencer Lee from Telin, Sebastian Balan from Fidelity, Todd Weikle from Soar Communications, Steve Scott from Borderless.com, and Mitch Kahl from BCM One. The discussions highlighted the role of AI in business communications, Vodia’s Microsoft Teams-certified PBX, and our integration with Realtime AI via APIs. This event followed a strategic planning session with key partners to outline Vodia’s goals for 2025. We look forward to connecting with you at future events!

February 19, 2025

AI-Powered Hotel Phone System: OpenAI for Guest Services

Vodia has integrated OpenAI’s Realtime API with its PBX, enabling real-time AI-powered hotel phone systems that enhance guest services. By leveraging natural speech processing, guests can make reservations, request services, and access hotel amenities in multiple languages - all through voice commands. This integration streamlines hotel operations, reduces staff workload, and improves guest satisfaction. Whether booking a room, ordering room service, or arranging transportation, AI-powered phone systems provide seamless communication and efficiency. Hotels can now offer personalized, automated experiences while maintaining reliable, high-quality service.

February 18, 2025

Vodia and Microsoft Teams: Your Call Center Solution

ConnectPlus, a fictional call center with 150 agents and 20 support team members, faced several challenges in managing its phone systems and customer interactions. The company struggled with inefficient call routing, long wait times, and inadequate reporting, especially as it relied on Microsoft Teams for internal communication. To improve operational efficiency and enhance the customer experience, ConnectPlus sought a solution that could streamline its processes across multiple devices and platforms. Integrating Vodia’s PBX with Teams provided the ideal solution, optimizing their call handling and overall communication capabilities.

February 12, 2025