Thank you for your quick response. I will take your advice and see how it works out.
Claremont Speede
Software Developer
TeleCommunication Systems, Inc.
speedec@xxxxxxxxxxxxxx
410 295 1442 (vox)
410 280 1094 (fax)
>>> Guy Harris <guy@xxxxxxxxxx> 05/22/02 04:46PM >>>
On Wed, May 22, 2002 at 04:31:30PM -0400, Claremont Speede wrote:
> I cannot seem to see my Submit_sm data when I send SMPP messages. I
> can see Enquire_link, Enquire_link - resp, Bind_receiver, and
> Bind_receiver - resp data, but not Submit_sm data. Is there a
> configuration parameter or filter I am missing out?
There are no configurable parameters in the SMPP dissector, and there is
nothing in the libpcap capture filter mechanism that knows anything
about SMPP, so the answer to your last question is "no, there isn't".
The main SMPP dissector is a "heuristic" dissector, which means it tries
to guess whether a packet is an SMPP packet or not based on the contents
of the packet. It might be that the heuristics it uses don't work on
Submit_sm commands or responses.
Is this SMPP-over-TCP or SMPP-over-X.25? If it's SMPP-over-TCP, try
selecting one of the SMPP packets, selecting "Decode As..." from the
"Tools" menu, selecting the appropriate port (or "both") from the item
after "TCP" and before "port(s)" in the dialog it pops up, selecting
SMPP from the list on the right, and clicking "OK". This will cause the
non-heuristic SMPP dissector to be used on the port or ports in
question.
If that fixes the problem, you might want to send mail to the author of
the SMPP dissector about the problem. (Don't send mail only to me, as
I'm not the maintainer of that dissector.)
