["Frederic Heem" <frederic.heem@xxxxxxxxx>]

Hi, 
In some situations, ethereal (0.10.0a and 0.10.7, linux and windows) fails to find the protocol h225, it says it's a h245 whereras it's a h225.
In the trace attached, there are four endpoints based on the telsey h323 stack, each of them have 2 phone numbers:
 
I.p            Phone numbers
192.168.0.15   98600020
               98600021

192.168.0.16   98600022
               98600023

192.168.0.34   341
               342

192.168.0.36   361
               362
192.168.0.32   gnugk 2.08 on windows

There are 2 types of setup where decodifications fails:
 
packet 237, 668 and 1102:  98600022 -> 361
packet 265, 691 and  1117: 98600020 -> 341

all other setups don't present the problem
98600021 -> 342
98600023 -> 362
341      -> 98600020
342      -> 98600021
361      -> 98600022
362      -> 98600023

When the setup decodification fails, all successive messages failed to be decoded (call proceeding, alerting, connect and release complete).
If "Decode As" is performed on a wrong packet, it doesn't allow to choose h225  
Let me know if one needs more informations.
Regards,
Frederic Heem

Attachment: abacus-major2-20041108-1.eth
Description: abacus-major2-20041108-1.eth