Tandberg NAT behind firewall works without NAT

[Augusto Garcia]

Hello

I have a tandber endpoint that has access to internet througt an ASA firewall, the thing is we had some trouble stablishing calls recently and testing the device with another endpoint outside the network, the call got established when we set the NAT configuration of our tandberg in nothing.

And Im trying to understand why is it working in that configuration? doesnt it have to work with the NAT option set? because its behind a firewall...

Appreaciate the comments.

Thank you.

[Martin Koch]

If you would tell us a bit about the deployment, like stand alone/registered to a VCS or BC

which protocol you use (h323/sip), which system type and software version it is, what you try

to dial (uri, ip, ...), how the asa is configured and so on.

Just that something might not be properly deployed does not mean that parts could not work. :-)

[Augusto Garcia]

Thank you for the quick answer,

The endpoint is registered to a VCS, we are using h323 and we are trying to dial an ip address, the ASA is configured to let everything from the public IP of the other office to have full access to our endpoint

Why could it be working without NAT? thats the question Im trying to answer, could the ASA be blocking something with the IPS when the endpoint sets the h323 headers with the public ip?

Best regards

[Martin Koch]

Is it a VCS-C or -E? The VCS-E is designed to do the firewall traversal.

It depends a bit on what you expect whats possible to dial.

If you have the system registered to the expressway all other protocol based

NAT handling should be turned off as the VCS-E is doing the magic and just

gets confused if something else is trying to know it better.

This would be on the endpoint but also on the firewall. So no NAT setting on your endpoint

and on the ASA.

This enables you to use inbound and outbound uri and e164 dialing for h323 and uri for sip.