Wireshark-bugs: [Wireshark-bugs] [Bug 9068] New: New BSMAP dissector does not decode Signal valu
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Thu, 22 Aug 2013 15:20:42 +0000
Bug ID 9068
Summary New BSMAP dissector does not decode Signal values
Classification Unclassified
Product Wireshark
Version 1.11.x (Experimental)
Hardware x86
OS Windows 7
Status UNCONFIRMED
Severity Normal
Priority Low
Component Dissection engine (libwireshark)
Assignee bugzilla-admin@wireshark.org
Reporter jon.carmicheal@gmail.com 

Created attachment 11437 [details]
One packet containing "Signal: Call waiting tone on"

Build Information:
Wireshark 1.11.0-SVN-51193 (SVN Rev 51193 from /trunk)
--
Related to Bug 8883: https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=8883

A BSMAP/DTAP dissector was added in revision 51040.  However, it does not
dissect the Signal values in SIP INFO messages.  Another custom dissector that
a colleague has dissects these signals in a meaningful way.  E.g. in the
attached packet his dissector presents this in the SIP block:

Signal - Call waiting tone on
Element ID
Signal value:  (7) Call waiting tone on
0000 00.. : Reserved
0000 00.. : Alert pitch: medium pitch (Standard alert)

While the dissector built into Wireshark's 51193 build has this:

Information Record Type [2]: (5) Signal
  Length: 2
  Record Content

So the "Call waiting tone on" is not displayed.  Similarly, the custom
dissector can dissect the "Tones off" signal, and presumably many other
signals.

Signal - Tones off
Element ID
Signal value:  (63) Tones off
0000 00.. : Reserved
0000 00.. : Alert pitch: medium pitch (Standard alert)

Can these signal dissections be added to Wireshark?  There is an example packet
attached that has the signal for "Call waiting tone on."

Thanks,
Jon

You are receiving this mail because:
  • You are watching all bug changes.