I have been trying to setup an ATA 186 behind a NAT box to connect to a
Gatekeeper but it never worked fully.
I have also been working with a cirilium gatekeeper and I get the same
problem. The ATA working behind a NAT box in the H323 configuration fails in
the RAS process.
The RAS meassages that are coming back from the GK to the ATA are lost and
never get to the destination. This happens once the IP inside the RAS
payload is an internal IP of the ATA (a local LAN IP) and not the public IP
provided by the NAT box.
Does anybody knows if it is possible to change the configuration of the ATAs
to send the correct IP in the Payload ?
This is a serious limitation of the ATA.
Thanks
_________________________________________________________________
Winterize your home with tips from MSN House & Home.
http://special.msn.com/home/warmhome.armx
Gatekeeper but it never worked fully.
I have also been working with a cirilium gatekeeper and I get the same
problem. The ATA working behind a NAT box in the H323 configuration fails in
the RAS process.
The RAS meassages that are coming back from the GK to the ATA are lost and
never get to the destination. This happens once the IP inside the RAS
payload is an internal IP of the ATA (a local LAN IP) and not the public IP
provided by the NAT box.
Does anybody knows if it is possible to change the configuration of the ATAs
to send the correct IP in the Payload ?
This is a serious limitation of the ATA.
Thanks
_________________________________________________________________
Winterize your home with tips from MSN House & Home.
http://special.msn.com/home/warmhome.armx