![]() Note: The list of standard commands can be found in section 5.1.2.1 of the SMPP specification (SMPP Command set). Here is an example of PDUs passing through the network when sending an MT, then receiving an SR: Wireshark will reassemble PDUs correctly, so it is mostly transparent for the Wireshark user. The stream is made up of independent PDUs: each PDU is a message containing a command, a status, a sequence number, and other information based on the command.ĭue to the nature of TCP as a stream protocol, a TCP packet may contain more than one PDU, and PDUs may span over 2 or more TCP packets. The protocol works over TCP and is fully binary, meaning that special tools like Wireshark (or a hexadecimal editor) are required to decrypt the content of the stream. Use the Follow TCP stream tool to isolate the stream you are working on.Ĭlose the red/blue text window that pops up because it is only useful for text protocols which are not relevant to SMPP. To isolate packets by phone number or by text content, use the search feature with the following settings: ![]() Use a display filter on the port of the SMS-C.įor example, if the SMS-C uses port 10000, use the following filter: To filter out SMPP traffic in Wireshark, there are three important features: A brief introduction is available on howtogeek - How to Use Wireshark to Capture, Filter, and Inspect Packets. ![]() ![]() This topic assumes that you’re familiar with the basics of Wireshark: capturing packets, defining simple filters, reading packet details. The file outfile.pcap can then be opened in Wireshark for further analysis. Here is a sample tcpdump command-line to capture port 12345 to outfile.pcap: tcpdump -i any -w outfile.pcap tcp port 12345 If you already know the TCP port of the connection, put the correct filter to avoid capturing all traffic. If you don’t have direct access to the machine, it may be necessary to capture using command-line tools like tcpdump. ResolutionĬapturing network traffic without Wireshark If you are using an SMPP simulator instead of connecting to a real SMS-C, you should use the source code (or a debugger) to understand what is happening. If the SMS-C replies with an error, your SMS-C partner will be the best person to tell you why it replied with the error. When troubleshooting problems, always contact the SMS-C partner to obtain information or to help you double-check what you get. Since the SMPP protocol contains many parts left to the interpretation of the implementation team, there are differences between different SMS-C. This article is not a substitute for this specification: it gives practical tips on how to interpret the protocol specification and match it with the Wireshark display to help troubleshoot problems between Adobe Campaign and the SMS-C partner. The SMPP protocol is documented in the SMPP Protocol Specification v3.4 available on the internet as a PDF document. This protocol allows sending SMS and receiving information about the delivery of these SMS. Most high-throughput Short Message Service Centers (SMS-C) are compatible with the SMPP protocol version 3.4. Learn to analyze SMPP traffic using Wireshark. SMPP Protocol Analysis Using Wireshark Description
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |