neels has uploaded this change for review. (
https://gerrit.osmocom.org/c/osmo-gsm-manuals/+/32273 )
Change subject: add static SS7 routing example to cs7-config.adoc
......................................................................
add static SS7 routing example to cs7-config.adoc
Related: SYS#6422
Change-Id: I44afddf7004f5bf37eec706ca3da12c04f83f8fa
---
M common/chapters/cs7-config.adoc
1 file changed, 161 insertions(+), 0 deletions(-)
git pull ssh://gerrit.osmocom.org:29418/osmo-gsm-manuals
refs/changes/73/32273/1
diff --git a/common/chapters/cs7-config.adoc b/common/chapters/cs7-config.adoc
index 5ac9bae..203df07 100644
--- a/common/chapters/cs7-config.adoc
+++ b/common/chapters/cs7-config.adoc
@@ -343,3 +343,154 @@
So you only have the following options:
* Using M3UA with routing context (1..N)
* Using M3UA without routing context (0)
+
+==== Example: Static Routing
+
+Osmocom SS7 supports dynamic routing, allowing minimal SS7 configuration. If
all of your components support dynamic
+routing, you should probably use that: see `accept-asp-connections
dynamic-permitted` in osmo-stp.cfg.
+This chapter explains how to configure osmo-stp if dynamic routing is not an
option.
+
+In this example, let's connect osmo-bsc via osmo-stp to osmo-msc using only
static SS7 routing.
+
+----
+ BSC <--RK-1--> STP <--RK-3--> MSC
+ IP 1.1.1.1 IP 2.2.2.2 IP 3.3.3.3
+ M3UA 12905 M3UA 2905 M3UA 32905
+ PC 1.1.1 PC 3.3.3
+----
+
+Every one static route fanning out from STP gets assigned a distinct Routing
Key -- a simple integer number. Above, the
+BSC's link has RK 1, the MSC's link has RK 3.
+
+Every component has a distinct M3UA port. For static routing, the M3UA port
numbers must be fixed, i.e. there must be no
+`0` for a client's local port as in `asp foo 2905 0 m3ua`.
+
+Above example has distinct IP addresses 1.1.1.1, 2.2.2.2, 3.3.3.3 *and*
distinct M3UA port numbers 12905, 2905, 32905,
+just to show which ends up where in the configuration.
+
+The BSC needs to configure:
+
+- its own point-code -- has to match the PC in osmo-stp.cfg
+- the routing key -- has to match the RK assigned to BSC's PC in osmo-stp.cfg
+- the MSC's point-code -- has to match the PC in osmo-stp.cfg and osmo-msc.cfg
+- local+remote IP:port for M3UA -- have to match the IP:ports in osmo-stp.cfg
+
+The MSC needs to configure:
+
+- its own point-code -- has to match the PC in osmo-stp.cfg
+- the routing key -- has to match the RK assigned to MSC's PC in osmo-stp.cfg
+- local+remote IP:port for M3UA -- have to match the IP:ports in osmo-stp.cfg
+
+The STP needs to configure:
+
+- all routing keys -- they have to match the RKs used in osmo-bsc.cfg and
osmo-msc.cfg
+- all point-codes -- they have to match the PC in osmo-bsc.cfg and osmo-msc.cfg
+- local+remote IP:port for M3UA -- have to match the IP:ports in osmo-bsc.cfg
and osmo-msc.cfg
+
+.osmo-bsc.cfg
+----
+cs7 instance 0
+ point-code 1.1.1
+
+ asp mybsc-0 2905 12905 m3ua
+ remote-ip 2.2.2.2
+ local-ip 1.1.1.1
+ sctp-role client
+ as mybsc0 m3ua
+ asp mybsc0-0
+ routing-key 1 1.1.1
+
+ sccp-address mymsc
+ routing-indicator PC
+ point-code 3.3.3
+
+msc 0
+ msc-addr mymsc
+----
+
+.osmo-stp.cfg
+----
+cs7 instance 0
+ xua rkm routing-key-allocation static-only
+ listen m3ua 2905
+ accept-asp-connections pre-configured
+ local-ip 2.2.2.2
+
+ # asp <name> <remote-port> <local-port|0> m3ua
+ asp mybsc-0 12905 2905 m3ua
+ remote-ip 1.1.1.1
+ local-ip 2.2.2.2
+ as mybsc m3ua
+ asp bsc-0
+ routing-key 1 1.1.1
+
+ asp mymsc-0 32905 2905 m3ua
+ remote-ip 3.3.3.3
+ local-ip 2.2.2.2
+ as mymsc m3ua
+ asp mymsc-0
+ routing-key 3 3.3.3
+
+ route-table system
+ update route 1.1.1 7.255.7 linkset mybsc
+ update route 3.3.3 7.255.7 linkset mymsc
+----
+
+.osmo-msc.cfg
+----
+cs7 instance 0
+ point-code 3.3.3
+
+ asp mymsc-0 2905 32905 m3ua
+ remote-ip 2.2.2.2
+ local-ip 3.3.3.3
+ sctp-role client
+ as mymsc0 m3ua
+ asp mymsc0-0
+ routing-key 3 3.3.3
+----
+
+For comparison, the same setup with dynamic routing is a lot shorter,
especially at osmo-stp.cfg, and there is no need
+ty synchronize point-codes and routing keys between STP and \{BSC,MSC}:
+
+.osmo-bsc.cfg
+----
+cs7 instance 0
+ point-code 1.1.1
+
+ asp mybsc-0 2905 0 m3ua
+ remote-ip 2.2.2.2
+ local-ip 1.1.1.1
+ sctp-role client
+ as mybsc0 m3ua
+ asp mybsc0-0
+
+ sccp-address mymsc
+ routing-indicator PC
+ point-code 3.3.3
+
+msc 0
+ msc-addr mymsc
+----
+
+.osmo-stp.cfg
+----
+cs7 instance 0
+ xua rkm routing-key-allocation dynamic-permitted
+ listen m3ua 2905
+ accept-asp-connections dynamic-permitted
+ local-ip 2.2.2.2
+----
+
+.osmo-msc.cfg
+----
+cs7 instance 0
+ point-code 3.3.3
+
+ asp mymsc-0 2905 0 m3ua
+ remote-ip 2.2.2.2
+ local-ip 3.3.3.3
+ sctp-role client
+ as mymsc0 m3ua
+ asp mymsc0-0
+----
--
To view, visit https://gerrit.osmocom.org/c/osmo-gsm-manuals/+/32273
To unsubscribe, or for help writing mail filters, visit
https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-gsm-manuals
Gerrit-Branch: master
Gerrit-Change-Id: I44afddf7004f5bf37eec706ca3da12c04f83f8fa
Gerrit-Change-Number: 32273
Gerrit-PatchSet: 1
Gerrit-Owner: neels <nhofm...@sysmocom.de>
Gerrit-MessageType: newchange
