Neels Hofmeyr | 8c8ebb1 | 2017-09-18 16:19:30 +0200 | [diff] [blame] | 1 | == Running OsmoMSC |
| 2 | |
| 3 | The OsmoMSC executable (`osmo-msc`) offers the following command-line |
| 4 | arguments: |
| 5 | |
| 6 | === SYNOPSIS |
| 7 | |
Vadim Yanitskiy | aefbf7a | 2021-11-12 20:28:08 +0300 | [diff] [blame] | 8 | *osmo-msc* [-h|-V] [-d 'DBGMASK'] [-D] [-c 'CONFIGFILE'] [-s] [-T] [-e 'LOGLEVEL'] |
Neels Hofmeyr | 8c8ebb1 | 2017-09-18 16:19:30 +0200 | [diff] [blame] | 9 | |
| 10 | === OPTIONS |
| 11 | |
| 12 | *-h, --help*:: |
| 13 | Print a short help message about the supported options |
| 14 | *-V, --version*:: |
Harald Welte | 22d0ba8 | 2019-12-01 14:25:39 +0100 | [diff] [blame] | 15 | Print the compile-time version number of the program |
Neels Hofmeyr | 8c8ebb1 | 2017-09-18 16:19:30 +0200 | [diff] [blame] | 16 | *-d, --debug 'DBGMASK','DBGLEVELS'*:: |
| 17 | Set the log subsystems and levels for logging to stderr. This |
| 18 | has mostly been superseded by VTY-based logging configuration, |
| 19 | see <<logging>> for further information. |
| 20 | *-D, --daemonize*:: |
| 21 | Fork the process as a daemon into background. |
| 22 | *-c, --config-file 'CONFIGFILE'*:: |
| 23 | Specify the file and path name of the configuration file to be |
Daniel Willmann | 020a485 | 2018-10-23 18:17:28 +0200 | [diff] [blame] | 24 | used. If none is specified, use `osmo-msc.cfg` in the current |
Neels Hofmeyr | 8c8ebb1 | 2017-09-18 16:19:30 +0200 | [diff] [blame] | 25 | working directory. |
| 26 | *-s, --disable-color*:: |
| 27 | Disable colors for logging to stderr. This has mostly been |
| 28 | deprecated by VTY based logging configuration, see <<logging>> |
| 29 | for more information. |
| 30 | *-T, --timestamp*:: |
| 31 | Enable time-stamping of log messages to stderr. This has mostly |
| 32 | been deprecated by VTY based logging configuration, see |
| 33 | <<logging>> for more information. |
| 34 | *-e, --log-level 'LOGLEVEL'*:: |
| 35 | Set the global log level for logging to stderr. This has mostly |
| 36 | been deprecated by VTY based logging configuration, see |
| 37 | <<logging>> for more information. |
Neels Hofmeyr | 8c8ebb1 | 2017-09-18 16:19:30 +0200 | [diff] [blame] | 38 | |
| 39 | |
| 40 | === Multiple instances |
| 41 | |
Neels Hofmeyr | fee9dd7 | 2017-09-25 16:37:34 +0200 | [diff] [blame] | 42 | Running multiple instances of `osmo-msc` on the same computer is possible if all |
| 43 | interfaces (VTY, CTRL) are separated using the appropriate configuration |
| 44 | options. The IP based interfaces are binding to local host by default. In order |
| 45 | to separate the processes, the user has to bind those services to specific but |
| 46 | different IP addresses and/or ports. |
Neels Hofmeyr | 8c8ebb1 | 2017-09-18 16:19:30 +0200 | [diff] [blame] | 47 | |
| 48 | The VTY and the Control interface can be bound to IP addresses from the loopback |
| 49 | address range, for example: |
| 50 | |
| 51 | ---- |
| 52 | line vty |
| 53 | bind 127.0.0.2 |
| 54 | ctrl |
| 55 | bind 127.0.0.2 |
| 56 | ---- |
| 57 | |
| 58 | If external SMPP is enabled, you may bind it to a different interface using: |
| 59 | |
| 60 | ---- |
| 61 | smpp |
| 62 | local-tcp-ip 10.23.42.1 2775 |
| 63 | ---- |
| 64 | |
| 65 | More on SMPP configuration in <<smpp-config-global>>. |
| 66 | |
Neels Hofmeyr | 92b0246 | 2020-05-26 23:13:53 +0200 | [diff] [blame] | 67 | The external MNCC handler is a UNIX domain socket that is created when external MNCC handling is configured. A separate |
| 68 | path must be used per osmo-msc instance: |
| 69 | |
| 70 | ---- |
| 71 | msc |
| 72 | mncc external /tmp/mncc_socket |
| 73 | ---- |
| 74 | |
| 75 | More on MNCC in <<mncc-external>>. |
| 76 | |
| 77 | The SGs interface by default listens on 0.0.0.0:29118. Configure a different IP and/or port for each osmo-msc instance. |
| 78 | You may also want to configure different VLR names: |
| 79 | |
| 80 | ---- |
| 81 | sgs |
| 82 | local-ip 127.0.0.1 |
| 83 | local-port 29118 |
| 84 | vlr-name vlr.example.net |
| 85 | ---- |
Neels Hofmeyr | 8c8ebb1 | 2017-09-18 16:19:30 +0200 | [diff] [blame] | 86 | |
| 87 | For the following links, OsmoMSC acts as a client and does not listen/bind to a |
| 88 | specific interface, and will hence not encounter conflicts for multiple instances |
| 89 | running on the same interface: |
| 90 | |
| 91 | - The SCCP/M3UA links are established by OsmoMSC contacting an STP. |
| 92 | - The GSUP link is established by OsmoMSC contacting an HLR. |
Neels Hofmeyr | d233104 | 2020-03-18 01:08:46 +0100 | [diff] [blame] | 93 | - The MGCP link is established by OsmoMSC contacting an MGW. |
Neels Hofmeyr | 8c8ebb1 | 2017-09-18 16:19:30 +0200 | [diff] [blame] | 94 | |
| 95 | |
| 96 | === Configure primary links |
| 97 | |
| 98 | ==== Configure SCCP/M3UA to accept _A_ and _IuCS_ links |
| 99 | |
Neels Hofmeyr | 346a3b9 | 2020-03-18 01:10:42 +0100 | [diff] [blame] | 100 | OsmoMSC acts as client to contact an STP instance and establish an SCCP/M3UA |
| 101 | link. |
Neels Hofmeyr | 8c8ebb1 | 2017-09-18 16:19:30 +0200 | [diff] [blame] | 102 | |
Neels Hofmeyr | 346a3b9 | 2020-03-18 01:10:42 +0100 | [diff] [blame] | 103 | An example configuration of OsmoMSC's SCCP link: |
Neels Hofmeyr | 8c8ebb1 | 2017-09-18 16:19:30 +0200 | [diff] [blame] | 104 | |
| 105 | ---- |
| 106 | cs7 instance 0 |
Neels Hofmeyr | 346a3b9 | 2020-03-18 01:10:42 +0100 | [diff] [blame] | 107 | point-code 0.23.1 |
| 108 | asp asp-clnt-OsmoMSC-A-Iu 2905 0 m3ua |
| 109 | remote-ip 127.0.0.1 |
Pau Espin Pedrol | 11c420a | 2023-06-08 19:39:13 +0200 | [diff] [blame] | 110 | role asp |
Neels Hofmeyr | 346a3b9 | 2020-03-18 01:10:42 +0100 | [diff] [blame] | 111 | sctp-role client |
Neels Hofmeyr | 8c8ebb1 | 2017-09-18 16:19:30 +0200 | [diff] [blame] | 112 | ---- |
| 113 | |
Neels Hofmeyr | 346a3b9 | 2020-03-18 01:10:42 +0100 | [diff] [blame] | 114 | This configuration is explained in detail in <<cs7_config>>. |
| 115 | |
Neels Hofmeyr | 8c8ebb1 | 2017-09-18 16:19:30 +0200 | [diff] [blame] | 116 | Note that _A_ and _IuCS_ may use different SCCP instances, if so desired: |
| 117 | |
| 118 | ---- |
| 119 | cs7 instance 0 |
| 120 | asp my-OsmoMSC-A 2905 0 m3ua |
| 121 | remote-ip 10.23.42.1 |
Pau Espin Pedrol | 11c420a | 2023-06-08 19:39:13 +0200 | [diff] [blame] | 122 | role asp |
| 123 | sctp-role client |
Neels Hofmeyr | 8c8ebb1 | 2017-09-18 16:19:30 +0200 | [diff] [blame] | 124 | cs7 instance 1 |
| 125 | asp my-OsmoMSC-Iu 2905 0 m3ua |
| 126 | remote-ip 10.23.42.2 |
Pau Espin Pedrol | 11c420a | 2023-06-08 19:39:13 +0200 | [diff] [blame] | 127 | role asp |
| 128 | sctp-role client |
Neels Hofmeyr | 8c8ebb1 | 2017-09-18 16:19:30 +0200 | [diff] [blame] | 129 | msc |
| 130 | cs7-instance-a 0 |
| 131 | cs7-instance-iu 1 |
| 132 | ---- |
| 133 | |
Neels Hofmeyr | 8c8ebb1 | 2017-09-18 16:19:30 +0200 | [diff] [blame] | 134 | ==== Configure GSUP to reach the HLR |
| 135 | |
| 136 | OsmoMSC will assume a GSUP server (OsmoHLR) to run on the local host and the |
| 137 | default GSUP port (4222). Contacting an HLR at a different IP address can be |
| 138 | configured as follows: |
| 139 | |
| 140 | ---- |
| 141 | hlr |
| 142 | ! IP address of the remote HLR: |
| 143 | remote-ip 10.23.42.1 |
| 144 | ! default port is 4222, optionally configurable by: |
| 145 | remote-port 1234 |
| 146 | ---- |
Philipp Maier | 945b060 | 2021-08-03 11:33:20 +0200 | [diff] [blame] | 147 | |
| 148 | ==== Configure MGCP to connect to an MGW |
| 149 | |
| 150 | OsmoMSC uses a media gateway (typically OsmoMGW) to direct RTP streams. By |
| 151 | default, an MGW is expected to receive MGCP requests on the IANA-registered |
| 152 | default port for MGCP (2427) on local host (127.0.0.1). |
| 153 | |
| 154 | Here is an example configuration for a remote MGW: |
| 155 | |
| 156 | ---- |
Pau Espin Pedrol | b44cf2d | 2022-10-17 18:09:15 +0200 | [diff] [blame] | 157 | network |
| 158 | mgw 0 |
Pau Espin Pedrol | ef70bb2 | 2022-10-19 13:25:55 +0200 | [diff] [blame] | 159 | remote-ip 10.9.8.7 |
| 160 | remote-port 2427 |
| 161 | reset-endpoint rtpbridge/* <1> |
Philipp Maier | 945b060 | 2021-08-03 11:33:20 +0200 | [diff] [blame] | 162 | ---- |
| 163 | <1> The 'reset-endpoint' setting instructs the OsmoMGW to send a wildcarded |
| 164 | DLCX to the media gateway. This helps to clear lingering calls from the |
| 165 | media gateway when the OsmoMSC is restarted. |
Pau Espin Pedrol | b44cf2d | 2022-10-17 18:09:15 +0200 | [diff] [blame] | 166 | |
Pau Espin Pedrol | 68d2a67 | 2022-10-20 16:24:06 +0200 | [diff] [blame] | 167 | OsmoMSC is also able to handle a pool of media gateways for load |
| 168 | distribution. See also <<mgw_pooling>>. |
| 169 | |
Pau Espin Pedrol | b44cf2d | 2022-10-17 18:09:15 +0200 | [diff] [blame] | 170 | [NOTE] |
| 171 | ==== |
| 172 | Previous versions of OsmoMSC (1.9.0 and below) didn't have the 'mgw' VTY node and |
| 173 | hence didn't support the MGW pooling feature. Therefore, historically the MGW |
| 174 | related commands where placed under the `msc` VTY node. The MGW related commands |
| 175 | under the `msc` VTY are still parsed and used but its use is deprecated and |
| 176 | hence discouraged in favour of the new `mgw` node. Writing the config to a file |
| 177 | from within OsmoMSC will automatically convert the config to use the new `mgw` |
| 178 | node. |
| 179 | ==== |