Anders Broman wrote:
> Richard van der Hoff wrote:
>
>> Well, if your H.223 is over TCP, it may or may not be bitswapped
>
> Guy wrote:
>> That presumably means that either
>>
>> 1) call setup negotiates the bit order
>>
>> or
>>
>> 2) the bit order is chosen "out of band" (e.g., manual
-Ursprungligt meddelande-
Från: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] För Guy Harris
Skickat: den 19 februari 2007 05:19
Till: Developer support list for Wireshark
Ämne: Re: [Wireshark-dev] H.223 dissector - separate "bitswapping" into
separate dissector
Richard van der
Richard van der Hoff wrote:
> Well, if your H.223 is over TCP, it may or may not be bitswapped
That presumably means that either
1) call setup negotiates the bit order
or
2) the bit order is chosen "out of band" (e.g., manually).
If it's negotiated at call setup time, presumab
Guy Harris wrote:
> Richard van der Hoff wrote:
>
>>The H.223 dissector contains code to deal with "bitswapped" captures -
>>ie, where all of the bytes have their bits backwards. It seems that this
>>is much better handled as a separate dissector entry point, so that the
>>right one can be chos
Richard van der Hoff wrote:
> The H.223 dissector contains code to deal with "bitswapped" captures -
> ie, where all of the bytes have their bits backwards. It seems that this
> is much better handled as a separate dissector entry point, so that the
> right one can be chosen when the dissector i
The H.223 dissector contains code to deal with "bitswapped" captures -
ie, where all of the bytes have their bits backwards. It seems that this
is much better handled as a separate dissector entry point, so that the
right one can be chosen when the dissector is registered, rather than
the curre
