Upgrade OpenSIPs / Freeswitch to enable TLS, SRTP and TCP for our client base.
Budget: $25 – $50 USD
Our current Operating environment is a clustered OpenSIPs server using UDP only. OpenSIPs uses Freeswitch PBX gateways for inbound and outbound calls.
Current Project requirement is to enable TLS, SRTP and TCP for our client base.
We have a test environment setup using OpenSIPs 3.3.3. TLS is working (only with the default certificates generated with the install of OpenSIPs 3.3.3) using a 3CX test platform.
This is where we need assistance including following steps;
We have tried using rootCA and userCA certificates generated by opensips-cli without success. Only the default certificate generated at the install works.
We have tried using letsencrypt certificates without success. We are concerned about having to generate these types of certificates every few months and how to automate. We require guidance on best practice to issue certificates preferably with an expiry greater than a few months (i.e 1 to 2 years).
Errors include “New TLS connection from 180.94.236.34:49799 failed to accept”
We require knowledge on how to generate these certificates so they work properly including which certificates go where.
Determine best way to manage for future?
Goals
#1 SIP communications to be able to use TCP and TLS. We need to be able to create and easily manage certificates for our customers and the server. We would prefer these managed from the database (which is working).
#2 RTP media to be encrypted from the client to our Freeswitch PBX gateways.
#3 TCP implementation has caused issues in the past with a number of customers. How can we tune the current configuration to make this robust?
We will provide ssh access to OpenSIPs via public IP address as well as a backup Freeswitch box. We can also provide 3CX access via web console and any other assistance as required.
Current Project requirement is to enable TLS, SRTP and TCP for our client base.
We have a test environment setup using OpenSIPs 3.3.3. TLS is working (only with the default certificates generated with the install of OpenSIPs 3.3.3) using a 3CX test platform.
This is where we need assistance including following steps;
We have tried using rootCA and userCA certificates generated by opensips-cli without success. Only the default certificate generated at the install works.
We have tried using letsencrypt certificates without success. We are concerned about having to generate these types of certificates every few months and how to automate. We require guidance on best practice to issue certificates preferably with an expiry greater than a few months (i.e 1 to 2 years).
Errors include “New TLS connection from 180.94.236.34:49799 failed to accept”
We require knowledge on how to generate these certificates so they work properly including which certificates go where.
Determine best way to manage for future?
Goals
#1 SIP communications to be able to use TCP and TLS. We need to be able to create and easily manage certificates for our customers and the server. We would prefer these managed from the database (which is working).
#2 RTP media to be encrypted from the client to our Freeswitch PBX gateways.
#3 TCP implementation has caused issues in the past with a number of customers. How can we tune the current configuration to make this robust?
We will provide ssh access to OpenSIPs via public IP address as well as a backup Freeswitch box. We can also provide 3CX access via web console and any other assistance as required.