https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6248
--- Comment #6 from Jaap Keuter <jaap.keuter@xxxxxxxxx> 2011-08-25 23:11:06 CEST ---
(In reply to comment #5)
> Hi again,
>
> SIP messages are decoded thanks Wireshark software. When there are
> two parts on the body, both of them are decoded as media parts.
>
> In my example, first part is displayed like this :
>
> First boundary: --P25 ISSI body boundary\r\n
> Encapsulated multipart part: (application/x-tia-p25-issi)
> Content-type: application/x-tia-p25-issi\r\n
> \r\n
> Media Type: application/x-tia-p25-issi (7 bytes)
> Boundary: \r\n--P25 ISSI body boundary\r\n
>
> whereas it should be at least displayed as following :
>
> First boundary: --P25 ISSI body boundary\r\n
> Encapsulated multipart part: (application/x-tia-p25-issi)
> Content-type: application/x-tia-p25-issi\r\n
> \r\n
> c-i:1\r\n
> \r\n
> Boundary: \r\n--P25 ISSI body boundary\r\n
>
> In fact, the first part is today not displayed.
Here you are mistaken. There is no way to tell what media type
application/x-tia-p25-issi is or how to present that data. You now claim it to
be text/plain, but the content type doesn't say so, and that's all Wireshark
can depend on.
... or you add a dissector, registering to dissect media type
application/x-tia-p25-issi, as shown before, and show the data as text.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.