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.
thanks!
VCS is on X7.1, C20 is on TC6.1.1, HDX is on 3.0.3 firmware.
