The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This document describes how to troubleshoot an issue where an endpoint tries to register to the Video Communication Server (VCS) via the H.323 signaling protocol and the VCS shows registered, but the endpoint shows unregistered.
Contributed by Ishan Sambhi, Cisco TAC Engineer.
The endpoint shows registered on the VCS control, but unregistered on the endpoint. This packet capture from the endpoint shows that the endpoint sends the Registration_Request (RRQ) out, but does not receive the Registration_Confirm (RCF).
This VCS packet capture shows that the VCS sends the RCF to the endpoint, however the RCF never reaches the endpoint.
On the VCS, the endpoint shows registered as from the VCS's perspective it has sent the RCF. However, since the endpoint does not receive a RCF it shows unregistered on the endpoint.
This is usually a firewall issue, where UDP port 1719 might not be open from the VCS to the endpoint or because the RCF is dropped on the network between the VCS and the endpoint.