-
Notifications
You must be signed in to change notification settings - Fork 11
/
Copy pathTODO_bad_clients.txt
53 lines (53 loc) · 2.35 KB
/
TODO_bad_clients.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
Bad clients:
SMPP Connection and flow:
* Do not send elink
* Send elink too fast
* Send elink too slow
* Do not response with elink_resp
* Unexpectedly drop connection (close socket without unbind)
* Do not response to deliver_sm
* Trying to connect with many sessions (semibad)
* Do not wait for unbind (semibad)
* Do not wait on throttling error
* Too much connections / binds without delay
* Drop connection on error in resp
* Drop connection after request packet send
* Sending submit_sm with expired absolute validity_period
* Sending submit_sm with expired absolute scheduled_delivery_time
* Drop connection after bind (not waiting for bind_resp)
* Do not limit speed from client / not using windowing
* Bind session for a single message
* Send esm_class = 1 (datagram mode) with submit_sm and registered_delivery flag
* Try to send messages in bind_receive session
* Do not analyze deliver_sm
** For servers:
*** Send submit_sm_resp after (semi)unlimited timeout. Answer with submit_sm_resp after 40 minutes.
Encoding:
* Using ASCII in short_message (semibad)
* Using utf-8 in short_message (semibad)
* Using utf-16 in short_message (semibad)
* Using windows-1251
* Using BOM in message
* Using ASCII with gsm-7bit encoding (mostly bad)
* Using 160-byte-lengthed messages for encoding to 7bit on SMSc side (mostly bad)
* Using UCS-2 with little endian
* Send HTML in sms such as <b></b>
PDU encoding:
* Using numbers started with 8 (semibad, bad for Russia)
* Using numbers without prefix (7 for russia) ex. 9261234567
* Using numbers with special characters 7(913)123-45-67
* Using DEF-numbers with incorrect TON/NPI
* Using Alpha-numbers with incorrect TON/NPI
* Using + or 00 in International numbers (TON/NPI 1/1)
* Using shortnumbers with incorrect TON/NPI
UDH / SAR concatination:
* Incorrect length for SAR-concatination (short_message longer than 134 octets)
* Incorrect length for UDH-concatination (short_message longer than 134 octets without UDH)
* Incorrect UDH-concatination (8 bit/16 bit/custom)
* Incorrect esm_class with UDH
* Incorrect number of messages and message number (semibad)
* Incorrect order of parts (semibad)
* Sending not all parts with current connection (semibad)
* Sending all parts only after receiving deliver_sm for first part
* Sending single SMS with UDH/SAR for 1 part
* Sending single SMS with message_payload