# HG changeset patch
# User Mychaela Falconia <falcon@freecalypso.org>
# Date 1693170850 0
# Node ID 1a923a97228ed7844266874b18492663626b0831
# Parent  6a1a436747e9b5004c71652735f31562b4913ba6
doc/Network-MT-SMS-testing: document written

diff -r 6a1a436747e9 -r 1a923a97228e doc/Network-MT-SMS-testing
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/doc/Network-MT-SMS-testing	Sun Aug 27 21:14:10 2023 +0000
@@ -0,0 +1,30 @@
+Testing MT direction of SMS-PP from the network side
+====================================================
+
+The envisioned way to generate SMS-DELIVER TPDUs for MT SMS testing from the
+network side is to run a shell pipeline of this form:
+
+sms-encode-text [opt] [msg-text] | gen-sms-deliver-pdu from-number [opt]
+
+Breaking it down:
+
+* The message text to be turned into an SMS-DELIVER TPDU (or multiple such TPDUs
+  with concatenated SMS) can given on the command line as an argument to the
+  sms-encode-text step in the pipeline, or can be fed as stdin to the pipeline.
+
+* Options for concatenated SMS or UCS-2 encoding need to be given at the
+  sms-encode-text pipeline stage.
+
+* The "From" number to be encoded into the SMS-DELIVER TPDU is given as a
+  mandatory argument at the gen-sms-deliver-pdu pipeline stage.
+
+* Additional options may be given at the gen-sms-deliver-pdu pipeline stage.
+  Possible options are lp, mms, rp, sr, pid and sc-ts, described in the
+  Tool-workflow article under sms-gen-tpdu description.
+
+The output from this pipeline will be a single hex-encoded SMS-DELIVER TPDU,
+emitted as one long hex line, or multiple such hex lines (each carrying a TPDU)
+in the case of concatenated SMS.  Test programs written in the course of SMSC
+development will be designed to take this hex TPDU format as their input, on
+stdin, so that the final SMSC-specific step will be simply added to the
+just-described pipeline.