What is the actual point of the "public IP" portion of the network topology?
If I have IP based SIP Trunks, and the customer has "failover" internet. Meaning that when the backup internet kicks in, all internet traffic will be natting out with a new public IP. If the "new" public IP is different from the IP set in the network topology, will the sip trunks not work. Keep in mind that the SIP provider will accept traffic from both IPs and all firewall rules are correct.
My worry is that no matter the "NAT" created by the firewall, the IP office will setup its sip messages with the IP that is SET in the "network topology".
And yes I have confirmed that this will work with registration based sip trunks, however the carrier they are using does not do registration based.
Just looking more or less as to what the "network topology" setting of PUBLI IP really does if anything in terms of SIP messages or any sort of signalling or security.
If I have IP based SIP Trunks, and the customer has "failover" internet. Meaning that when the backup internet kicks in, all internet traffic will be natting out with a new public IP. If the "new" public IP is different from the IP set in the network topology, will the sip trunks not work. Keep in mind that the SIP provider will accept traffic from both IPs and all firewall rules are correct.
My worry is that no matter the "NAT" created by the firewall, the IP office will setup its sip messages with the IP that is SET in the "network topology".
And yes I have confirmed that this will work with registration based sip trunks, however the carrier they are using does not do registration based.
Just looking more or less as to what the "network topology" setting of PUBLI IP really does if anything in terms of SIP messages or any sort of signalling or security.