Toggle sidebar Toggle sidebar

Connect an on premise SIP trunk with 3cx on cloud (Azure)

Status
Not open for further replies.

ga_sync

Customer
Joined
Oct 6, 2020
Messages
8
Reaction score
0
Hi,

We have a 3cx deployed on Azure for a customer located in Swiss.
The customer has purchased a SIP trunk from a supported provider (Sunrise).
The SIP provider has installed an SBC on-site (they told us it's not possible to do direct connection to their SBCs with public IPs ).
What would be the best option to connect the 3cx to Sunrise SBC with private IPs onsite?

If a VPN is required, has anyone done this setup? Can you please share the steps to establish this?
My concern is that the 3cx has already a public IP address that is used to connect internet clients (i.e. 3cx softphones, direct SIP external b2b calls...), can we set another private IP address on the server to be used to connect the SIP trunk over the VPN tunnel?

Thank you for your help,

Regards,
George
 
Are you sure it is a trunk offer coming from provider? not a voip solution fully coming from SIP provider ?
if it's 3CX supported provider did you see something particular about way to use their trunks ?
Did you follow this doc?
https://www.3cx.com/docs/swiss-sip-trunk-sunrise/
 
I have checked, the link, most probably it's for 3cx on premise not on cloud.
I have checked with Sunrise, they provide an SBC on premise to connect to 3cx.

I'm attaching the diagram provided by Sunrise, you can see that the 3cx is on site and it is connected to their SBC using private addresses.

In my case 3cx is on Azure, how can we establish the connectivity?

Thanks,
George
 

Attachments

  • surise-3cx.jpg
    surise-3cx.jpg
    28.7 KB · Views: 47
Perhaps I'm wrong but IMO it's impossible to be connected partially to on premise ressources and same time using PBX on cloud.
Is it possible to host your PBX on premise instead of Azure?
 
Hi,

In this case your deployment type is simply not compatible with the trunk solution you are using.

You will have to bring your PBX locally on the same network as the provider's on-premises SBC so they two can communicate.

VPN can be a possible solution, but this is something you have to do by yourself and will not be without its problems.

If local deployment is not an acceptable solution, you can consider using a provider that allows connections over the internet.
 
I understand that you have no hasel free working setups, where the 3cx is on the cloud and the sip trunk of a provider is terminated on-prem.

What about a voice gateway (FXS) like Yeastar TA3200 installed on prem with a 3cx on cloud?

VPNs are not recommended in these 2 cases? Shall we stick to the 3cx on-prem deployment?

Regards,
George
 
Hi George,

The easiest solution would be to go on-prem with a small server or a VM on an existing server that has ample resources.


1.) VPNs can work, but it's all up to you to figure out and maintain. If you don't have previous experience with this I would not recommend doing it on a client and risking causing them downtime.

2.) the FXS would not be a good solution, you want the PBX and its features to work with SIP phones and soft clients, an FXS would convert extensions to analog lines which is not what you are looking for in this case


If the client wants to use their provider, the best solution would be to go on prem and just open the necessary firewall ports to allow the 3CX system to work exactly like before.

In case you need assistance or have questions regarding the migration we will be glad to help!
 
Do you have enough bandwith with your local ISP or Is it a reason why you choose Cloud hosted?
 
Thank you John for your reply.
We will approach again the customer and ask if deploying 3CX on-prem is possible.

Can you please send server specs to support 200 extensions.
In addition do you recommend 3cx on windows or Linux, which one is more stable?
Shall we deploy it directly on the server or we need to deploy in on a VM?

The customer has already analog phones and doesn't want to invest in IPphones at this stage, he rather chose FXS gateways. Do you have any recomendations also for the FXS gateways. We chose Yeastar TA3200 but aparently they are out of stock so we need to find other brand.

Thanks,
George
 
aws2p said:
Do you have enough bandwith with your local ISP or Is it a reason why you choose Cloud hosted?
Click to expand...
the BW isn't a problem , the customer prefers to deploy his servers on Azure.
 
ga_sync said:
the BW isn't a problem , the customer prefers to deploy his servers on Azure.
Click to expand...
easier to manage especial that we don't have unattended remote connection to the site.
 
ga_sync said:
The customer has already analog phones and doesn't want to invest in IPphones at this stage, he rather chose FXS gateways. Do you have any recomendations also for the FXS gateways. We chose Yeastar TA3200 but aparently they are out of stock so we need to find other brand.
Click to expand...
How many Analog phones do you have to connect ?
this one from Grandstream is 48 ports
1601997973403.png
 
JohnS_3CX said:
Hi George,

The easiest solution would be to go on-prem with a small server or a VM on an existing server that has ample resources.


1.) VPNs can work, but it's all up to you to figure out and maintain. If you don't have previous experience with this I would not recommend doing it on a client and risking causing them downtime.

2.) the FXS would not be a good solution, you want the PBX and its features to work with SIP phones and soft clients, an FXS would convert extensions to analog lines which is not what you are looking for in this case


If the client wants to use their provider, the best solution would be to go on prem and just open the necessary firewall ports to allow the 3CX system to work exactly like before.

In case you need assistance or have questions regarding the migration we will be glad to help!
Click to expand...
Thank you John for your reply.
We will approach again the customer and ask if deploying 3CX on-prem is possible.

Can you please send server specs to support 200 extensions.
In addition do you recommend 3cx on windows or Linux, which one is more stable?
Shall we deploy it directly on the server or we need to deploy in on a VM?

The customer has already analog phones and doesn't want to invest in IPphones at this stage, he rather chose FXS gateways. Do you have any recomendations also for the FXS gateways. We chose Yeastar TA3200 but aparently they are out of stock so we need to find other brand.

Thanks,
George
 
Last edited:
So for this project you must

1. Absolutely use an on premise PBX or change to a supported cloud SIP provider

2. If in the cloud, use an SBC and IP Phones. If on premise you can use analog gateways if you must but dont think you are going to save money. Its only for hotels for example that dont have ethernet wiring to the rooms.

3. There is also the webclient, windows client and mobile apps

If customer insists on an unsupported scenario please do not propose 3CX to them.
 
Last edited by a moderator:
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
111,964
Messages
590,004
Members
164,869
Latest member
hpgitsupport
3CX Logo Footer Copyright © Sitemap Privacy
Top Bottom