VCS control and VCS expressway peer address failed
We have implementation of VCS control with VCS expressway within an internal leg of the Fortigate firewall with no dual NIC. We have NAT-ed virtual public IP for both inside the firewall. both VCS are in the same subnet (private IP and NAT-ed virtual public IP). Peer addressing for both NAT-ed virtual public IP is failing but both can definitely recognized their private IP.
Someone might have a similar experience in this kind of implementation. Please advise. Thank you.
I am not sure I understand the topology completely but I would start with a ping test. Log into the root of the VCSC and ping the VCSE IP address you are trying to peer with. Also, Static NAT is not supported on the VCSC, only the VCSE if that is what you are trying to do.
ping test and traceroute were successful after enabling NAT feature of the virtual public ip (vip) in the firewall for both VCS. also vip peer address of VCSe went active in VCSc but h323. attached also is the network orientation for illustration. thank you.
I have looked at the topology diagram and still am a little confused. What is the device outside of the firewall before the cloud? This is were the VCS-E would usually sit - possibly further protected by another Firewall thus creating a DMZ, but this is not absolutely necessary.
The VCS-C and VCS-E pair make up a firewall traversal solution - i.e. allowing video traffic to travel across the firewall meaning without the need to open up a whole bunch of ports. It seem from the diagram that the VCS-C and VCS-E are logically connected to the same internal network.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...