comparison doc/Network-MT-SMS-testing @ 20:1a923a97228e

doc/Network-MT-SMS-testing: document written
author Mychaela Falconia <falcon@freecalypso.org>
date Sun, 27 Aug 2023 21:14:10 +0000
parents
children b23b9f69c02a
comparison
equal deleted inserted replaced
19:6a1a436747e9 20:1a923a97228e
1 Testing MT direction of SMS-PP from the network side
2 ====================================================
3
4 The envisioned way to generate SMS-DELIVER TPDUs for MT SMS testing from the
5 network side is to run a shell pipeline of this form:
6
7 sms-encode-text [opt] [msg-text] | gen-sms-deliver-pdu from-number [opt]
8
9 Breaking it down:
10
11 * The message text to be turned into an SMS-DELIVER TPDU (or multiple such TPDUs
12 with concatenated SMS) can given on the command line as an argument to the
13 sms-encode-text step in the pipeline, or can be fed as stdin to the pipeline.
14
15 * Options for concatenated SMS or UCS-2 encoding need to be given at the
16 sms-encode-text pipeline stage.
17
18 * The "From" number to be encoded into the SMS-DELIVER TPDU is given as a
19 mandatory argument at the gen-sms-deliver-pdu pipeline stage.
20
21 * Additional options may be given at the gen-sms-deliver-pdu pipeline stage.
22 Possible options are lp, mms, rp, sr, pid and sc-ts, described in the
23 Tool-workflow article under sms-gen-tpdu description.
24
25 The output from this pipeline will be a single hex-encoded SMS-DELIVER TPDU,
26 emitted as one long hex line, or multiple such hex lines (each carrying a TPDU)
27 in the case of concatenated SMS. Test programs written in the course of SMSC
28 development will be designed to take this hex TPDU format as their input, on
29 stdin, so that the final SMSC-specific step will be simply added to the
30 just-described pipeline.