Question regarding SIP trunks and Self-Hosted 3CX on Azure

Status
Not open for further replies.

Liam1982

New User
Joined
May 3, 2023
Messages
3
Reaction score
1
Hi all,

Bit of a newbie question, so bear with me.
Is it possible with 3CX to install the call manager itself on our Azure cloud infrastructure, but have the SIP trunk presented/terminated in our local data centre via our main Internet link? (The SIP trunk would be with one of 3CX's preferred providers, possibly Gamma or BT)
My assumption is that the SIP trunk would be 'pointed' towards the IP address of the Azure 3CX installation (Via CLI commands on our router?) and as long as our Firewall and other networking infrastructure is configured correctly then traffic can pass between them.
Or am I way off and it's an absolute pain to get working?
We could go for an on-premise install too, but management are keen to use Cloud where possible.

Thanks for any info
 
In your case, you will have to use a VPN between Azure and on-premise, and have the router do all the tricky routing, so that 3CX can register to the SIP trunk remotely through that.

However, this might cause latency and delays in the calls so be aware of that.

It's always easier to have a SIP trunk that isn't provided via a second WAN or fiber or anything like that. Specially if you want it cloud.
 
  • Like
Reactions: Liam1982
Thanks for that, sorry can you explain the last part there? Is there another more ideal way we could have SIP services delivered, one that isn't attached to our main Internet link?
Can we purchase a SIP that gets terminated within the Azure Cloud Infrastructure, as opposed to in our local DC?
I'm thinking it would be easier to configure, and less likely to have latency, if we install in on prem.
Thanks
 
Thanks for that, sorry can you explain the last part there? Is there another more ideal way we could have SIP services delivered, one that isn't attached to our main Internet link?
Can we purchase a SIP that gets terminated within the Azure Cloud Infrastructure, as opposed to in our local DC?
I'm thinking it would be easier to configure, and less likely to have latency, if we install in on prem.
Thanks
You cannot get SIP that "terminates" in Azure.

You need to understand that the SIP trunk delivery on Internet link is only for providers who do that.

When you're Cloud, it doesn't matter where the trunk "terminates" as long as it's reachable by the PBX (and within some latency limits) For example, Twilio is available worldwide, doesn't matter where the PBX is.

Also, remember that the PBX registers to the trunk, not the opposite.
 
  • Like
Reactions: Liam1982
Brill, thanks for that, appreciated!
 
  • Like
Reactions: Evolute IT
Status
Not open for further replies.

Members Online Now

No members online now.

Forum statistics

Threads
111,831
Messages
589,277
Members
164,660
Latest member
RJenkinsROCK