Hi folks
For some time the SMPP dissector has correctly called the WSP & WBXML
decoders whenever it sees an SMS submission with a destination port of
2948 (so packets of structure eth:ip:tcp:smpp:gsm-sms-ud:wsp:wbxml).
I'm now looking at some SS7 captures that contain SMS-DELIVER (which go
as far as mtp3:sccp:tcap:gsm_map:gsm_sms). The destination port is
clearly 2948 but the WSP/WBXML decoder is not called.
Looking at this the SMPP dissector calls gsm-sms-ud (which is in
packet-gsm_sms_ud.c) whereas the GSM MAP dissector (packet-gsm_sms.c)
doesn't seem to check the significance of the destination port (in
functions dis_iei_apa_8bit and dis_iei_apa_16bit).
Is there any reason why these functions can't simply call the gsm-sms-ud
decoder? (why decode the UDH stuff anyway in packet-gsm_sms.c when the
gsm-sms-ud can do all that?)
Is anyone hacking around in this area of Ethereal at the moment?
--
Dermot Bradley dermot.bradley@xxxxxxxxxxxx
Senior TPS Engineer, Mobile Systems
Openwave Systems Direct: +44 28 90416218
Belfast, Northern Ireland Fax: +44 28 90416201