Contact header not using IP specified in trunk

[Grégory Brusick]

Hello,

I have a trunk to interconnect a 3CX PBX to a non 3CX PBX in another remote office through VPN.

I've set the internal IP to be used in the contact field in the Trunk options tab, but it still sends the public IP in the contact of all the messages it sends.
With this contact field being wrong, the remote PBX sends ACK messages to the public IP and the communication is dropped after 30s.
I've also made sure the remote PBX is in the LOCALSUBNETS list in the parameters
Am I missing something?

Best regards

Gregory

 

[StefanW]

there is still a check if the IP entered is inside of RFC1918 and the target outside, if so, this would be a non routable setup. As you have an VPN, can you target the "internal IP" or an FQDN which resolves to an internal IP.

 

[Grégory Brusick]

The other PBX, even though it is accessed through a VPN, has a public IP and no private IP.
It could be possible to connect from outside of the VPN by opening ports, but we prefer not to have it in clear on the internet and and we also would like to avoid having NAT in between.

Is there a place to add an address to extend this check to other addresses than only RFC1918 ones?
I thought it was the goal of the LOCALSUBNETS parameter