Networking improvements.

[sssputnik]

Just got asked to complete a survey on our 3CX experience.

Nice to be asked for feedback and good too see 3CX seeking such.

One issue that's always bugged me is multiple NICs on the the 3CX system.
We usually use private SIP trunks, these break out into a private network at our SIP provider and provide external call routing via this. On the internal side we have another NIC with footprint in internal network.

Can be setup, but we normally need to change routing priority via command line, (what NIC to use for internet etc). Some sort of wizard or auto config for this would be great.

 

[datamerge]

Additionally, on Linux version, any form of secondary NIC, or sub interface will crash the managment UI, which means these private SIP trunks need to be dealt with on the router, usually involving NAT.

 

[Sopock]

In that case 3CX will not put "public" IP in SDP without additional outbound proxy!
network_diagram

We usually use private SIP trunks, these break out into a private network at our SIP provider and provide external call routing via this.

I also wonder how will such providers enable this:

• allow inbound and outbound calls to +357 numbers(from 212.50.96.162)