http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1385
luis.ontanon@xxxxxxxxx changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution| |FIXED
------- Comment #2 from luis.ontanon@xxxxxxxxx 2007-02-21 00:27 GMT -------
the minor part of PkgdName was added to the tree using the parameter id whic
caused confussion.
The value 2 is there, and it was labeled correctly.
I Committed revision 20885 to fix the bug.
you can download an automated build of that release from:
http://www.wireshark.org/download/automated/
As per the Q.1950 annex A params, signals and events some are there some aren't
(same thing for Annex C Annex E and 3gpp packagess). I'll be adding them "on
demand" (my own demand). I spend my time troubleshooting MGws so sometimes I
add things I need to do my job.
BTW you do not need to be a C programmer to add a package or parts of it, take
a look to
http://anonsvn.wireshark.org/viewvc/viewvc.py/trunk/epan/dissectors/packet-h248_q1950.c?view=markup
http://anonsvn.wireshark.org/viewvc/viewvc.py/trunk/epan/dissectors/packet-h248_annex_e.c?view=markup
http://anonsvn.wireshark.org/viewvc/viewvc.py/trunk/epan/dissectors/packet-h248_annex_c.c?view=markup
and
http://anonsvn.wireshark.org/viewvc/viewvc.py/trunk/epan/dissectors/packet-h248_3gpp.c?view=markup
And you'll see that adding more parameters it's an easy Job...
Just fill the blanks send in the modified files and you'll earn your name
written in the AUTHORS list (you won't get anymore than that!)
--
Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
