Hey, all.
I'm working on the installation and setup of two Polycom HDX 6000 systems, located in different counties to connect two court systems. Setup was great, both systems are able to call a variety of test sites, and I can call into each from the local LAN from my Fedora machine with Ekiga, both on SIP and H.323.
One system (call it "System R") is on a resource-restricted network: Difficult to get router and public IP configured, no time/money to allocate additional resources, etc. So we decided that System R will call out to the other system whenever the video conferencing needs to happen.
"System J" is on a network where the network admin has given me full access to everything I need to set up the public face of the video conferencing system. I followed all the various and sundry guides (both Polycom and others) on how to set up the router, firewall, and System J to accept incoming calls.
So here's the wrinkle: Calls to System J are failing, and after some work with Wireshark, I have found out why. When the call is initiated to the public IP address for System J, it's being properly routed. However, System J is responding with its internal IP address (128.222.2.188), rather than its public IP address.
The calling system then uses that wrong address to finish the call setup, and it fails (of course). The Wireshark trace shows that the two talk past each other for about 30 seconds, then the client gives up.
I've tried many and several combinations of the firewall and IP config, and the best I can get is the above. The system displays the public IP address on the "Home" screen, so it's well aware of the public address and all indiciations are that it _should_ work. Complete power-downs/reboots ("hard" and "soft") have not shaken this behavior. It's still broadcasting the wrong address on the SIP setup (H.323 is not working either, but not getting a definitve trace on that one)
So here are my questions:
1. I do software development, and it's my suspicion that having a non-routable address is part of the requirement for this to work (10.0.0.0, 172.0.0.0, or 192.0.0.0), and the fact that System J is on a network that doesn't use those address ranges is the source of the problem. Is this true (the non-routable requirement)? I need to confirm this before having the network guy go through the work of reconfiguring a chunk of his network.
2. If #1 is not the case, is there a good blog entry/documentation/guide that others who have been in a similar situation and have overcome this problem?
3. Any pointers on how to track this down or sift through the sites and documentation? I've tried as many different search terms as I can, but my Google-fu is being defeated by this particular problem. Maybe I'm not using the proper search terminology.
I would be happy to post configs (redacted), capture files, etc. if someone thinks it would help.