| Harald Welte | 9b6a39b | 2011-10-10 12:38:45 +0200 | [diff] [blame] | 1 | = Osmocom Erlang SCCP implementation = |
| 2 | |
| 3 | This is a currently still incomplete Erlang SCCP implementation which |
| 4 | is part of the overall Osmocom project (http://osmocom.org/) |
| 5 | |
| 6 | The aim is to fully implement SCCP for connectionless and connection- |
| 7 | oriented services, including global title translation. It should be |
| 8 | possible to use this as both STP or SCP, or even as an ITP/SGW. |
| 9 | |
| 10 | |
| 11 | == Configuration == |
| 12 | |
| 13 | The SCCP stack is configured via the regular OTP application configuration |
| 14 | file. |
| 15 | |
| 16 | |
| 17 | === Signalling linksets and links === |
| 18 | |
| 19 | The MTP functionality can be provided by either M3UA or a classic MTP3 (over |
| 20 | M2UA or real MTP2). |
| 21 | |
| 22 | A linkset is a group of links, all connected to the same destination (point |
| 23 | code). |
| 24 | |
| 25 | Each signalling linkset has to be configured in the config file, providing |
| 26 | the following parameters: |
| 27 | * linkset name |
| 28 | * local point code |
| 29 | * remote point code |
| 30 | |
| 31 | Each signalling link has to be configured in the config file, providing the |
| 32 | following parameters: |
| 33 | * linkset name |
| 34 | * SLS |
| 35 | * IP address and port information (for M3UA) |
| 36 | |
| 37 | The sccp_links module keeps track of signalling linksets and links by means of |
| 38 | ets tables. It maintains a record of the Erlang process pid responsible for |
| 39 | each respective link. |
| 40 | |
| 41 | == Architecture == |
| 42 | |
| 43 | osmo_sccp_app starts osmo_sccp_sup, which in turn starts the individual signalling |
| 44 | links through the respective signalling link provider modules. |
| 45 | |
| 46 | It also starts sccp_scrc (the SCCP routing) |
| 47 | |
| 48 | One sccp_scoc instance will be started for each SCCP connection. |
| 49 | |
| 50 | == Implementing a SCCP-user == |
| 51 | |
| 52 | == Implementing a MTP provider for SCCP == |
| 53 | |
| 54 | This section outlines how to write a MTP transport for the SCCP stack. |
| 55 | |
| 56 | FIXME |