Ask Your Question
0

Dissector bug protocol sip

asked 2024-07-27 23:57:39 +0000

updated 2024-07-28 03:28:45 +0000

Chuckc gravatar image

Wireshark is throwing dissector bug, protocol SIP: error as shown below. This happens for a sip message from Ericsson containerized P-CSCF towards IMS core. Looks like Ericsson container P-CSCF has added some tags after Branch Tag in Via header. Wireshark is unable to handle that. I already checked sip protocol options but there is nothing that can be done from user interface to ignore the additional tags. Can someone help on a workaround for the dissector bug.

 Session Initiation Protocol
    Request-Line: REGISTER sip:msg.lab.t-mobile.com SIP/2.0
    Message Header
        Via: SIP/2.0/UDP 10.xxx.xxx.xxx:5060;branch=z9hG4bKg3Zqkv7iiuu5d9cb2gyyeore6tohdm87j;eric_th_id=1;be-route=MTkyLjE2OC43Ny42MDo4MDgw
            Transport: UDP
            Sent-by Address: 10.xxx.xxx.xxx
            Sent-by port: 5060
            Branch: z9hG4bKg3Zqkv7iiuu5d9cb2gyyeore6tohdm87j
            **eric_th_id=1
            be-route: MTkyLjE2OC43Ny42MDo4MDgw**
[Dissector bug, protocol SIP: C:\gitlab-builds\builds\MsQ3pox2\0\wireshark\wireshark\epan\packet.c:3456: failed assertion "handle != ((void *)0)"]
    [Expert Info (Error/Malformed): C:\gitlab-builds\builds\MsQ3pox2\0\wireshark\wireshark\epan\packet.c:3456: failed assertion "handle != ((void *)0)"]
        [C:\gitlab-builds\builds\MsQ3pox2\0\wireshark\wireshark\epan\packet.c:3456: failed assertion "handle != ((void *)0)"]
        [Severity level: Error]
        [Group: Malformed]
edit retag flag offensive close merge delete

Comments

Please update the question with the output of wireshark -v or Help->About Wireshark:Wireshark.
It helps to have a sample capture file. Can you put one on a public file share then update the question with a link to it.

Chuckc gravatar imageChuckc ( 2024-07-28 04:23:43 +0000 )edit

1 Answer

Sort by ยป oldest newest most voted
0

answered 2024-07-28 05:33:20 +0000

Jaap gravatar image

The proper channel to report this to be fixed is in our GitLab project. Filling out all fields of the issue template and attaching a sample capture file to it allows to address this, perhaps before the next stable release comes out.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower

Stats

Asked: 2024-07-27 23:57:39 +0000

Seen: 108 times

Last updated: Jul 28