|
Hi,
I am still testing an ata186 behind a H.323 enabled Cisco router
Using netmeeting I can make calls both ways through the router – everything is fine
*Mar 1 02:59:43.187: %IPNAT-6-NAT_CREATED: Created udp 101.0.0.3:1270 100.0.1.3:1270 100.0.0.24:1719 100.0.0.24:1719 *Mar 1 02:59:43.187: NAT: RAS : [0] processing a RRQ message *Mar 1 02:59:43.187: NAT: RAS : using an existing full entry to translate 101.0.0.3:1270->100.0.1.3:1270 *Mar 1 02:59:43.187: NAT: RAS : [0] TransportAddress addr changed 101.0.0.3->100.0.1.3 *Mar 1 02:59:43.187: NAT: RAS : [0] TransportAddress addr changed 101.0.0.3->100.0.1.3 *Mar 1 02:59:43.187: NAT: RAS: message changed, encoding back *Mar 1 02:59:43.471: NAT: RAS : [1] processing a RCF message
With the ata186:
If I enable Supportnattedendpoints I can make “out” calls through the router but not “in”
If I disable Supportnattedendpoints which for a properly working router should work – I get invalidcallsignaladdress on the RRQ packet
Further investigation shows the GRQ is being natted correctly but the RRQ is not
Below is the output from the Cisco for “debug IP nat h323”
*Mar 1 02:35:11.055: NAT: RAS : [0] processing a RRQ message *Mar 1 02:35:11.055: NAT: RAS : using an existing full entry to translate 101.0.0.2:1739->100.0.1.2:1739 *Mar 1 02:35:11.055: NAT: RAS : [0] TransportAddress addr changed 101.0.0.2->100.0.1.2 *Mar 1 02:35:11.055: NAT: RAS : [0] TransportAddress addr changed 101.0.0.2->100.0.1.2 *Mar 1 02:35:11.055: NAT: RAS: message changed, encoding back *Mar 1 02:35:11.055: NAT: RAS: [0] NAT newly encoded message length (119) doesn't match original length (121) *Mar 1 02:35:11.071: NAT: RAS : [1] processing a RRJ message
help!
Stuart Marsden
|
