Thanks Andreas, I didn't know that ethereal is that stateful. Indeed, I am behind a NAT device. Providing my public address to the gateway is the only way to get the H.323 VoIP service behind the NAT. So I seem to have to live with this until a next ethereal might be less stateful and just interpret the message as it is. Or is this theoretically impossible?
Regards Dirk Los -----Original Message----- From: Andreas Sikkema [SMTP:[EMAIL PROTECTED] Sent: Monday, October 27, 2003 9:31 AM To: [EMAIL PROTECTED] Subject: RE: [Ethereal-users]TKTP protocol not recognized On zondag 26 oktober 2003 20:48, [EMAIL PROTECTED] wrote: > Spontaneously I experienced that the H.245 messages were not > expanded anymore, even TPKT wasn't shown, only TCP data. > Also the RTP and RTPC traffic wasn't expanded anymore, just > showed as UDP > traffic The problem is that in frame 34 the client sending the setup message reports its H.245 IP address as 145.53.64.143 and the port as 18010, while the traffic to that port is going to IP address 10.0.0.230. Are you using NAT? The solution is either to not cause the destination IP address to change or sent incorrectly, OR, use Decode As... Which will not help very much because also the RT(C)P traffic has the same issue. -- Andreas Sikkema _______________________________________________ Ethereal-users mailing list [EMAIL PROTECTED] http://www.ethereal.com/mailman/listinfo/ethereal-users
