3CX SINGTEL CLOUD SIP in AWS

[eds.pare]

Hi, Just wondering if anyone have use Singtel-Singapore for the 3CX Cloud SIP under AWS or any cloud provider.

They ask to setup or have the server to have a different IP subnet, which is not on the current IP of the 3CX in AWS.

When i add another NIC into the server the Secondary IP will drop the connection of my other SIP connection via open internet. yet they have the same outgoing and incoming policy, the secondary though doesn't have any public facing IP address.

Some DNS errors. but when remoting into the server i can resolve the SIP.

Any idea on how to resolve it?

 

[YiannisH_3CX]

Hi @eds.pare

Have you tried the recommendations in the Singtel configuration guide?

 

[eds.pare]

Everytime i add the secondary NIC, our other SIP Server connection will drop and shows

In AWS, do i need a public IP for the secondary link for 3CX? as i only added a local NIC.

And the Singtel documentation seems to be focus via LOCAL LAN or onprem.

 

[YiannisH_3CX]

And the Singtel documentation seems to be focus via LOCAL LAN or onprem.

This is something you will need to discuss with Singtel to see if its possible to add them with a second NIC in the cloud.

 

[jc155]

For AWS VPC, both NICs use the same Internet gateway to reach Singtel and the 1st sip provider..

If using Linux server, your need a route-table for the 2nd NIC and a rule for Singtel gateway in the table.

A possible way is to add NIC profiles in /etc/network/interfaces and disable "#source-directory /run/network/interfaces.d", otherwise reconnect to 3CX may fail.

More info in AWS reference:
.
How can I make my secondary network interface work in my Ubuntu EC2 instance?