["Bilig Oyun" <boyun@xxxxxxxxxxx>]

Mike,

 

Great info, thanks. I'll wait for 0.10.5.

 

Bilig

-----Original Message-----
From: Oliveras, Michael [mailto:mike.oliveras@xxxxxxxxxxxxx]
Sent: Wednesday, July 07, 2004 6:11 PM
To: 'boyun@xxxxxxxxxxx'; 'Ethereal user support'
Subject: RE: [Ethereal-users] Ethereal can't decode H.225 message correctly --- Unknown PER Malformed Packet

Hi Bilig,

 

A patch was included with ethereal 0.10.4 that added some h235 decoding that was ignored in previous releases.  Because it only had limited support, it cause some packets to not get decoded anymore.  I have a version that I compiled from cvs, and your trace is successfully decoded.  When 0.10.5 is released your trace should be decoded properly.

 

- Mike

 

Michael Oliveras
QA Engineer
Teleglobe (formerly ITXC Corp.)
609.750.3454 - office
609.750.3272 - lab

-----Original Message-----
From: Bilig Oyun [mailto:boyun@xxxxxxxxxxx]
Sent: Wednesday, July 07, 2004 4:35 PM
To: ethereal-users@xxxxxxxxxxxx
Subject: [Ethereal-users] Ethereal can't decode H.225 message correctly --- Unknown PER Malformed Packet

Hi,

 

I have a case where Ethereal is unable to decode properly the h.225 packets from a Siemens IP Phone.

 

Please look at the packet 6 --- I know this is a faststart setup with G.711 aLaw and uLaw (other codes possible), but Ethereal doesn't decode the faststart element.

Also packet 16 is a RRQ (registration request) and packet 160 is a DRQ (disengage request), where the Ethereal failed to decode.

 

I'm using Ethereal 0.10.4 on a Windows 2000 machine.

 

Thank you,

 

Bilig