This is because of the fix for bug 1110
(https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1110). Since the
exact type of the data in the short_message field is not fixed (it can
be text in different character sets or binary), its field type is
FT_NULL. You can see the details and progress of the mentioned bug for
more details.
HTH
Abhik.
On Tue, Oct 7, 2008 at 10:05 AM, siri m <svu004@xxxxxxxxx> wrote:
> Sure Abhik, I will wait for your response,
>
> Thanks,
>
> siri
>
>>Abhik wrote:
>
>>I have checked this with the latest code and the behaviour is the
>
>>same. I'll have a look at it and see why it doesn't populate the
>>values.
>
>>Regards,
>>Abhik.
>
> On Tue, Oct 7, 2008 at 5:22 AM, Bill Meier <wmeier@xxxxxxxxxxx> wrote:
>> siri m wrote:
>>> Hi,
>>>
>>> Currently, we are using tshark 0.99.6 to convert a SMPP capture file to
>>> pdml format using the following:
>>>
>>
>>
>>>
>>> Is it a known issue with tshark/pdml producing null values for show and
>>> value? Has anyone come across this issue? Any pointers would be quite
>>> helpful to me,
>>>
>>
>> I don't know the answer to your question but I would note that 0.99.6 is
>> quite old .... :)
>>
>> I suggest downloading a current wireshark/tshark (v1.0.3) and trying
>> that to see if you see the same as for 0.99.6.
>>
>>
>> _______________________________________________
>> Wireshark-users mailing list
>> Wireshark-users@xxxxxxxxxxxxx
>> https://wireshark.org/mailman/listinfo/wireshark-users
>>
>
>
> _______________________________________________
> Wireshark-users mailing list
> Wireshark-users@xxxxxxxxxxxxx
> https://wireshark.org/mailman/listinfo/wireshark-users
>
>
