Hi Dermot,
[apologies for responding this late to this mail -- my ISP is to blame as I
am cut off from the Internet since Dec 17th, 2005]
That code was written "some time ago" for being able to dissect an incoming
WAP Push over SMPP. Did you manage to get any progress on this issue?
Best regards,
Olivier
----- Original Message -----
From: "Dermot Bradley" <dermot.bradley@xxxxxxxxxxxx>
To: "Ethereal development" <ethereal-dev@xxxxxxxxxxxx>
Sent: Wednesday, December 14, 2005 3:22 PM
Subject: [Ethereal-dev] GSM decoding of WAP Pushes?
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
_______________________________________________
Ethereal-dev mailing list
Ethereal-dev@xxxxxxxxxxxx
http://www.ethereal.com/mailman/listinfo/ethereal-dev
