I have a customer that is currently migrating an old environment of codecs just thrown out on the network and then had NATed a public IP to the device's private IP for connectivity to the internet. this is not an uncommon deployment, but we are now migrating them to a VCS and they want the codec to be able to still be reached via it's public IP address but leverage the VCS as well for CAC. during our testing we noticed that even though the codec has the NAT setting configured, while the H.323 call setup mode is set to "gatekeeper" calls to the codec's IP address get routed to the VCS. this is true for both the polycom HDX and Cisco C series codecs they have. when we set the call setup mode to direct, calls to the IP address work fine.
for the C series codecs the workaround i guess would be to set H323 to direct and then route VCS calls as SIP, and set the default call protocol to be SIP so all outbound calls go through the VCS. the polycoms i have an issue though as i can only deploy them as H323 devices since there is a compatibility issue with Polycom and interworked H323<>SIP messages from the VCS. can anyone explain why the codec would route the IP address call to the VCS as opposed to just sending a reply to the originating IP address? any thoughts on workarounds in the VCS to make this all work? when looking at the packet capture the codec sends the H323 call setup request to the VCS and then the VCS immediately rejects it.
VCS is on X7.1, C20 is on TC6.1.1, HDX is on 3.0.3 firmware.
If the endpoints are registered on VCS, then by default when you make a call, the call is supposed to go through VCS (otherwise you would have problem ). so, so-far so good. if you want to IP call directly out bypassing VCS, then there is an option on endpoint as "direct call" that needs to be selected before making call.
That is not the issue. The issue is inbound calls to the codecs ip address from a 3rd party device. The 3rd party calls a public ip that is then nated to the ip of my codec. My codec gets the setup.messaging then forwards to the vcs instead of responding directly.
Then this would be network question. since you said your endpoint/codec is NAT'ed, hence the ip address is not externally visible to any thing. you can do port forward at firewall to route the call directly to your endpoint/codec, but I have never tried this for video and have serious that whether it's going to work.
Certificates are the first step to deploy Cisco Meeting Server, preparing certificate are very important to enable different services. As a VOIP administrator, mastering the concept of certificates is unavoidable
Using multiple CA servers, instead of a si...
I just finished to write a comprehensive certificates preparation for Cisco Meeting Server Clustering. Through 60 pages I explained in detail, how to create certificates for database cluster, callbridge cluster, certificate chain for webbridge3, certifica...
Translation Pattern is the most important tool in the Call Routing Process for Cisco Unified Communication manager. Largely used in the Globalized Dial Plan, inter-site and intra-site dialing, and a powerful tool to solve the problem of overlapping direct...
Customer relationship management (CRM) tools are essential for managing relationships, collaborating with your team, and closing deals. The most forward-thinking CRM companies now integrate artificial intelligence (AI) into their software. The combination...