When implementing a Cisco IOS MCM with proxy functionality in a co-edge model (i.e. in parallel with an existing firewall, so the firewall does not have to inspect the H.323 traffic), what would be a suitable ACL to apply to the external-facing interface, to ensure that only H.323 entered the network? Would it be necessary to permit traffic from other gatekeepers. Can the ACL be restricted to certain ports, or does the dynamic nature of H.323 make this problematic?
Not sure what application or functional use you require, but for IP/VC I would suggest:
configuring the proxy on the inside of your firewall , enabling H.323 fixup on the firewall (assuming PIX) and then creating an ACL on the firewall opening port 1719 to the IP address of the Proxy.
In some University environments that required internet users to access conferences inside the University firewall we have used a guest gatekeeper model. Install a guest gatekeeper outside the firewall that Internet users will use to access conferences and then use the proxy model described above to get the video traffic through the firewall.
There are cases/situations where we have to configure custome CPTONE to resolve FXO disconnect issue. Following are situations which can arise due to FXO disconnect issue:
Phone A calls Phone B, Phone B does not answer. Phone A then goes on-hook but Phon...
Cisco announced major enhancements today to Webex Contact Center. Learn more about the highlights including
better support for the needs of large contact centers worldwide
improvements in the agent and cust...
SymptomsI’m doing a factory reset on the mobile board and it’s giving me the same issues that I wasn’t able to also send over last time. It says that it can’t connect to the server because of a firewall (we don’t have one) and then sometimes it...