Neels Hofmeyr has submitted this change and it was merged. Change subject: move smpp.adoc to common chapters, generalize ......................................................................
move smpp.adoc to common chapters, generalize OsmoMSC will need the same SMPP chapter as OsmoNITB. In smpp.adoc, replace program name with parameter, add parameter to OsmoNITB's main adoc and move smpp.adoc to common/chapters. Change-Id: I15febdea6569316dad3eed5f9dc7158adb5b078c --- M OsmoNITB/osmonitb-usermanual.adoc R common/chapters/smpp.adoc 2 files changed, 8 insertions(+), 5 deletions(-) Approvals: Neels Hofmeyr: Looks good to me, approved Jenkins Builder: Verified diff --git a/OsmoNITB/osmonitb-usermanual.adoc b/OsmoNITB/osmonitb-usermanual.adoc index 85b4c7d..63d430a 100644 --- a/OsmoNITB/osmonitb-usermanual.adoc +++ b/OsmoNITB/osmonitb-usermanual.adoc @@ -28,7 +28,7 @@ include::chapters/hlr.adoc[] -include::chapters/smpp.adoc[] +include::../common/chapters/smpp.adoc[] include::../common/chapters/mncc.adoc[] diff --git a/OsmoNITB/chapters/smpp.adoc b/common/chapters/smpp.adoc similarity index 92% rename from OsmoNITB/chapters/smpp.adoc rename to common/chapters/smpp.adoc index 23951ba..e62a844 100644 --- a/OsmoNITB/chapters/smpp.adoc +++ b/common/chapters/smpp.adoc @@ -2,16 +2,19 @@ == Short Message Peer to Peer (SMPP) The _Short Message Peer to Peer (SMPP) Protocol_ <<smpp-34>> has been -used for the communication with SMSCs. OsmoNITB implements version 3.4 +used for the communication with SMSCs. Osmocom implements version 3.4 of the protocol. Using this interface one can send MT-SMS to an attached subscriber or receive unrouted MO-SMS. + +SMPP is served by the Osmocom MSC layer (both in the old OsmoNITB as well as +the new OsmoMSC. SMPP describes a situation where multiple ESMEs (External SMS Entities) interact with a SMSC (SMS Service Center) via the SMPP protocol. Each entity is identified by its System Id. The System ID is a character string which is configured by the system administrator. -OsmoNITB implements the SMSC side of SMPP and subsequently acts as a TCP +{program-name} implements the SMSC side of SMPP and subsequently acts as a TCP server accepting incoming connections from ESME client programs. Each ESME identifies itself to the SMSC with its system-id and an @@ -21,13 +24,13 @@ === Global SMPP configuration -There is a `smpp` vty node at the top level of the OsmoNITB +There is a `smpp` vty node at the top level of the {program-name} configuration. Under this node, the global SMPP configuration is performed. Use the `local-tcp-ip` command to define the TCP IP and port at which the -OsmoNITB internal SMSC should listen for incoming SMPP connections. The +{program-name} internal SMSC should listen for incoming SMPP connections. The default behaviour is to listen on all IPs (0.0.0.0), and the default port assigned to SMPP is 2775. -- To view, visit https://gerrit.osmocom.org/4104 To unsubscribe, visit https://gerrit.osmocom.org/settings Gerrit-MessageType: merged Gerrit-Change-Id: I15febdea6569316dad3eed5f9dc7158adb5b078c Gerrit-PatchSet: 2 Gerrit-Project: osmo-gsm-manuals Gerrit-Branch: master Gerrit-Owner: Neels Hofmeyr <nhofm...@sysmocom.de> Gerrit-Reviewer: Harald Welte <lafo...@gnumonks.org> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: Neels Hofmeyr <nhofm...@sysmocom.de>