So this pretty much I had transit VoIP trafic from site Z with dynamic IP and get around Cloud PBX IP restriction I enforce VoIP over PepVPN link on egress side
on Ingress side I enforced to WAN1 with Static IP white-listed on PBX.
After update this setting is broken but strangely I was able to make it to work with using priority instead of enforce and in prioritys I select again WAN1 and Pep VPN connection to SF hub on Pep380.
Here in my test scenario again all relevant to original issue on ananaspep1 site I have WAN1 Static IP whitelisted on pbx.pangeaequity.com and any WAN IPs on ccVPN site is also whitelisted on PBX.Pangeaequity.com but WAN2 is NOT whitelisted as it’s dynamic IP
and what’s why my SIP endpoints or even in the browser on PC I can’t go to PBX.pangeaequity.com
but If it would route as it should I didn’t had any issues with my SIP endpoint or PC accessing PBX.pangeaequity.com
Also As I mentioned earlier why outbound routes have redundant rules to same destinations by IP and
domain name that looks like routing by domain name doesn’t work and its broken since 6.1.1 at least.
haven’t tried it on 6.1.0
Sorry I am not Voip expert. Can you elaborate more RTP via port range 10000 - 20000? Basically the communication is from where to 172.16.82.35? In short what is the possible source IP to communicate with 172.16.82.35?
in this case source UDP from IP 213.155.221.14 and it uses port 5060 for registration, and then if there is a phone call after establishing session it uses UDP RTP in this case select random port in the range 10000-20000 to send UDP traffic which carries Voice packets.
Andrey, Would you please start the network capture on the unit http://<Unit IP address>/cgi-bin/MANGA/support.cgi and make a call in order to reproduce the issue. Then, get the captured file and send to us?