09-20-2011 12:37 PM - edited 03-17-2019 10:30 PM
I'm a VTC tech that has just taken ownership of an existing Tandberg network that has some strange quarks. From HQ we can dial certain sites by IP address and not by E.164 alias. Those outstations can dial us by E.164 alias but not by IP address. It's not limited to one type of unit. They are all desktop Tandbergs, either 1000s or 1700s. They all have different firmware and upgrading isn't fiscally viable right now. It's not limited to geography or time of day. It's also not limited to a certain zone on our VCS Expressway. The firewall has all the ports open that are referenced in the Tandberg Security white paper. Any ideas, including exorcisms, will be entertained. Thanks!
09-20-2011 02:30 PM
I would check if the systems are properly registered and how the search rules and call logs look like.
Open ports are often not enough, check that there are no ALG/Layer3 features for sip/h323 are enabled.
Please remember to rate helpful responses and identify
09-21-2011 06:41 AM
Thanks for the lead on the ALG. I've got the network guys checking that out. As for the search rules and the call logs, what would cause the issues between h323 and e164, or what should I be looking for in there?
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide