cs7-config: Explain that A/Iu/Lb interfaces are reouted via STP
Change-Id: Iabba390b41b9d2ad9c3975a6e6cc504a56e59d0b
This commit is contained in:
parent
46f610b3b4
commit
6da11244b0
|
@ -59,6 +59,17 @@ At the time of writing, SCCP/M3UA links involving Osmocom program are:
|
||||||
- IuPS-interface: OsmoHNBGW to OsmoSGSN
|
- IuPS-interface: OsmoHNBGW to OsmoSGSN
|
||||||
- Lb-interface: OsmoSMLC to OsmoBSC
|
- Lb-interface: OsmoSMLC to OsmoBSC
|
||||||
|
|
||||||
|
On the SCTP/IP level, those connections are actually all established from
|
||||||
|
the respective program (BSC, MSC, HNBGW, SGSN, SMLC) to OsmoSTP. Hence,
|
||||||
|
if you look at the traffic in a protocol analyzer like wireshark, at IP
|
||||||
|
level, you will see each of those programs establishing an SCTP
|
||||||
|
association from a random local IP to the well-known SCTP port for M3UA
|
||||||
|
(2905) at the OsmoSTP.
|
||||||
|
|
||||||
|
Those star-connections for M3UA/SCTP then are the transport network for
|
||||||
|
higher level protocols like SCCP. OsmoSTP then acts as central router
|
||||||
|
for SCCP-level message exchange between all the connected programs.
|
||||||
|
|
||||||
=== Connect to STP Instance
|
=== Connect to STP Instance
|
||||||
|
|
||||||
By default, an STP instance is assumed to listen on the default M3UA port
|
By default, an STP instance is assumed to listen on the default M3UA port
|
||||||
|
|
Loading…
Reference in New Issue