Windows 2019 Static Routes for Route Calls and Terminate SIP trunks

[mlawgeorge]

Hello Team,

I need your advice about having multiple network static routes within a windows 2019 datacenter edition 3CX server version 16 to terminates SIP service provider trunks/connection that are directly connected to the network cards of the 3CX server, would this arrangement be fine since occasionally we experience silent calls and at some point conflicting reports I have added two diagram illustrating the current setup or arrangement and the planned setup.

Or we should not be bothered adding multiple static routes if it will not impact the calls and functionality of 3CX check diagram below;-

 

[Evolute IT]

I'd rather use the firewall or a switch to do the static routing instead of relying on WS2019 to act correctly.

Remember that in a static route, you also need a route from the other side to yours in order for packets to travel back&forth.

 

[Saqqara]

Why not add a router that can handle both of the isp links, and have this route traffic correctly.

 

[ChrisC_3CX]

...would this arrangement be fine since occasionally we experience silent calls and at some point conflicting reports...

Just to clarify in case I have misunderstood. Are you saying that you are planning on implementing this network configuration in an attempt to resolve this issue? If yes, I highly recommend you first investigate further in order to identify the cause of the problem as it may very well not be related to this specific setup meaning you might end up doing it all for nothing.

 

[mlawgeorge]

Not entirely because of the silent calls and conflicting reports as we still need support from the SIP service provider the main point in question would recommend someone to have static routes in the box with over 3 network cards connected in the server two for service provider and the other for LAN, currently we having this setup and we use static routes to make sure we have calls in and out.

The plan is to have routers to terminate the SIP connections and then have one network in the 3CX server box

Thanks @ChrisC_3CX

 

[Marconi]

I have seen arrangements where the 3CX server has only one network card but one of the SIP providers uses IP authentication. In this case you will (should have) been given the IP range and gateway settings for use with the SIP service. You assign one of the IPs as a secondary address on the NIC and then define a static router using the command prompt (with admin privileges).

Take a look at this post on Whirlpool for the arrangement used with 3CX and a TPG IP SIP Trunk.

I hope this helps.

 

[NickD_3CX]

We generally don't recommend adding 2 IPs to the same physical NIC.
If you can't do what you want with Static Routes and a single IP, then best add a second NIC without a Gateway.

Don't ask me for specifics as there is not something specific, but over the years we have seen very weird problems stemming from multiple IPs on the same NIC.
There have been others of course that worked fine...

Just my 2 cents....

 

[Marconi]

Don't ask me for specifics as there is not something specific, but over the years we have seen very weird problems stemming from multiple IPs on the same NIC.
There have been others of course that worked fine...

I have, personally, seen some very strange behaviour when having more than 1 NIC in a 3CX server so you're caught between a rock and a hard place either way.

If it's possible to have a firewall/router/switch do the routing then that might be a better way to handle it but I haven't had an opportunity to test that type of arrangement so can't say for sure.