Unnessecery IP address setting causing problems

[Oliver Broad]

I've been running smoothly using the trunk (Gamma) that was originally set up for another system. After identifying the trunk I configured 3CX to use it.

Our site is supposed to have Static IP, but events have shown it isn't quite as static as I thought. After a weekend down our ISP decided to assign us a new IP...

So I reconfigured 3CX, got in touch with the provider to get the trunk configured, and it didn't immediately spring back to life.

Turns out that in "Options" theres a configuration "Put Public IP in SIP VIA Header" and a field with the old IP address in.

After manually updating this everything worked.

Now I realise that there may be edge cases where the admin needs to set an IP manually, but surely by default it should just use its public IP as configured in network settings.

 

[YiannisH_3CX]

Turns out that in "Options" theres a configuration "Put Public IP in SIP VIA Header" and a field with the old IP address in.

After manually updating this everything worked.

Now I realise that there may be edge cases where the admin needs to set an IP manually, but surely by default it should just use its public IP as configured in network settings.

The default IP in VIA leaving the PBX is the local IP of the server. If you have a public IP then it will be public but the default VIA of the machine is its local IP.
The VIA header is designed to work that way as each server the call goes through adds it's IP address so it can be reached on the way back.
Most providers do not have issues with this but Gamma needs it for identification purposes.

 

[Oliver Broad]

Well what I'm asking for is an option that says use the box's public IP as set in the network settings rather than using an additional configuration field that isn't immediately obvious.

I'm reluctant to tamper with something that seems to work, but for all I know maybe if "Put Public IP in SIP VIA Header" was enabled and the IP fileld was empty it would default to the public IP?

I can see there might be niche cases where the value might be something other than the private IP or public IP, maybe in some double-NAT or corporate firewall scenario the trunk might go to a different gateway to user traffic.

 

[N_G]

Well if you use a supported provider that doesnt require these settings you would not be having these issues.