Call Routing Tandberg vs. Radvision

[videojunkie1208]

I run a VTC network, and have been trying to sort out some connectivity issues with another department that manages their own VTC network. Their gatekeepers are Radvision (do not know the model number) I have a top to bottom Tandberg Solution.

When I implement call routing (with or without call transfer) on my GK, I can no longer connect to their endpoints, even though when it is disabled (set to direct), I can call no problem.

I would like to implement call routing and call transfer (as I have some applications on our network for these features), is there a setting that the other group needs to implement in the Radvision to make it play nice nice with the Tandberg GK, and call routed mode?

The only other issue that I can think of is that the firewall rules are VERY restrictive, is there something I should look for in the firewall rules that might prevent this from working?

Thanks!

[jo3baltes]

I would expect to find that that the TCP ports needed for H.225 or H.245 is being blocked between the GKs, or the firewalls are mangling the H.225 packets.

The best way to test is to collect a sniff of traffic to the RADVISION GK side of the connection and attempt to route a call from your TBG GK to them.

If there are firewalls in the path between locations and GK direct routing works, this is almost certainly the problem. What are the firewalls (Pix/ASA by chance?)?

~joe