[mike <mike321@xxxxxxxxxxxxx>]

Ronnie,

Thanks for the reply -- but I don't think that the trunk group is in a clear token.

When I open the file in ethereal 0.9.11 with the h323 plugin, this information appears to just be ignored.  (It as at the end of the packet).  
With 0.9.15 it actually does seem to decode part of it, but the name is displayed wrong, and the packet is reported as a malformed packet.  As a result, the type of h225 message is not displayed in the top ethereal window.  I included a decode of the information below for an ARQ.  For this case, the Calls_Available_group should be "ITXC", and the GroupID should also be "ITXC".  

Could you possible take another look?  If ethereal could decode the information that would be great - if not it would be nice if it was ignored, so that the type of h225 packet is displayed in the top window and the packet is not displayed as a malformed packet.

Thanks,

Mike Oliveras

canMapAlias: 1... .... True
                CallIdentifier
                    guid: 78028935002411D881CCB2F7D3FBAC11
                tokens
                    Item 0
                        something unknown here
                cryptoTokens
                    Item 0
                        something unknown here
                willSupplyUUIEs: 0... .... False
                CallCapacity
                    currentCallCapacity
                        voiceGwCallsAvailable
                            Item 0
                                CallsAvailable
                                    CallsAvailable_calls: 94
                                    CallsAvailable_group: 06495458
                CircuitInfo
                    sourceCircuitID
                        GroupID
[Malformed Packet: H225]


-----Original Message-----
From: Ronnie Sahlberg <ronnie_sahlberg@xxxxxxxxxxxxxx>
Sent: Oct 21, 2003 4:24 AM
To: mike <mike321@xxxxxxxxxxxxx>, ethereal-users@xxxxxxxxxxxx
Subject: Re: [Ethereal-users] ethereal does not decode cisco trunk group correctly in H225 messages

No one has yet written a H.235 dissector for Ethereal.
Ethereal will not be able to dissect the ClearToken and friends in those
packets until someone
writes a dissector for H.235.

You example capture I am sure will be very helpful for whomever starts
implementing H.235.


----- Original Message ----- 
From: "mike"
Sent: Saturday, October 18, 2003 1:46 PM
Subject: [Ethereal-users] ethereal does not decode cisco trunk group
correctly in H225 messages


> When I use ethereal 0.9.15 to decode H225 mesasges using cisco trunk
groups, ethereal reports the packet as a Malformed Packet.
>
> It looks like the group should be decoded as a string, however ethereal is
not displaying it as one.
>
> I included a capture file with an ARQ and an LRQ using trunk groups; the
trunk group also is sent in the ACF/LCF and the H225 setup.  I also attached
a "debug h225 asn1" debug from a cisco gatekeeper which shows the ASN1
decode.
>
> Thanks,
>
> Mike Oliveras