RDVasil

About

Username
RDVasil
Joined
Visits
10
Last Active
Roles
Member
Points
5
Badges
0
Which product type of newsletter you want to receive?
Business and consumer products
Posts
5

Comments

  • That's why it's confusing to me. In the absence of any other policies, I thought all IPSEC traffic is by default allowed. I've tried adding a policy (on both routers) just for UDP 10020-10531, added policies Any to Any with the Source or Destination the PBX, turned off Policy Control completely on both routers, and tried…
  • Yes, DHCP server used by phones is at branch and VOIPBX is at main. There is handshaking between phones and PBX on TCP ports 5060/5080 that does take place - we can see it on traffic monitor and logs on both routers. We can see phones at branch send UDP 3462 to PBX, and logs at main show it forwarded. But PBX should reply…
  • Main office has static IP at 66.xxx.xxx.xxx, USG40 at 192.168.0.2, an NEC phone system at 192.168.0.241; Branch office has static IP at 66.xxx.xxx.xxx, USG40 at 192.168.2.254, domain controllers with DNS at 192.168.0.254 (main) and 192.168.2.252 (branch), both functioning correctly and accessible from either side, VOIP…
  • We're got IPSEC VPN configured, not SSL VPN. I see no additional users created, nothing created under SSL VPN, and nothing but the default VPN policies. Our VOIP problems began last weekend, just after the firmware upgrade
Avatar