Harald Welte | 75c0e08 | 2016-02-20 10:56:10 +0100 | [diff] [blame] | 1 | == Running OsmoBSC |
| 2 | |
| 3 | The OsmoBSC executable (`osmo-bsc`) offers the following command-line |
| 4 | arguments: |
| 5 | |
Neels Hofmeyr | 4c297e7 | 2016-10-17 06:12:13 +0200 | [diff] [blame] | 6 | === SYNOPSIS |
Harald Welte | 75c0e08 | 2016-02-20 10:56:10 +0100 | [diff] [blame] | 7 | |
| 8 | *osmo-bsc* [-h|-V] [-d 'DBGMASK'] [-D] [-c 'CONFIGFILE'] [-s] [-T] [-e 'LOGLEVEL'] [-l 'IP'] [-r 'RFCTL'] |
| 9 | |
Neels Hofmeyr | 4c297e7 | 2016-10-17 06:12:13 +0200 | [diff] [blame] | 10 | === OPTIONS |
Harald Welte | 75c0e08 | 2016-02-20 10:56:10 +0100 | [diff] [blame] | 11 | |
| 12 | *-h, --help*:: |
| 13 | Print a short help message about the supported options |
| 14 | *-V, --version*:: |
Harald Welte | 16c8910 | 2019-12-01 14:23:34 +0100 | [diff] [blame] | 15 | Print the compile-time version number of the program |
Harald Welte | 75c0e08 | 2016-02-20 10:56:10 +0100 | [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 | 5397326 | 2018-10-23 18:17:28 +0200 | [diff] [blame] | 24 | used. If none is specified, use `osmo-bsc.cfg` in the current |
Harald Welte | 75c0e08 | 2016-02-20 10:56:10 +0100 | [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 configu- ration, 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. |
| 38 | *-l, --local='IP'*:: |
| 39 | Specify the local IP address of the OsmoBSC-MGCP |
| 40 | *-r, --rf-ctl 'RFCTL'*:: |
| 41 | Offer a Unix domain socket for RF control at the path/filename |
| 42 | 'RFCTL' in the file system. |
Neels Hofmeyr | 21a2c81 | 2020-03-18 01:01:39 +0100 | [diff] [blame] | 43 | |
| 44 | |
| 45 | === Multiple instances |
| 46 | |
| 47 | Running multiple instances of `osmo-bsc` on the same host is possible if all |
| 48 | interfaces (VTY, CTRL) are separated using the appropriate configuration |
| 49 | options. The IP based interfaces are binding to local host by default. In order |
| 50 | to separate the processes, the user has to bind those services to specific but |
| 51 | different IP addresses and/or ports. |
| 52 | |
| 53 | The VTY and the Control interface can be bound to IP addresses from the loopback |
| 54 | address range, for example: |
| 55 | |
| 56 | ---- |
| 57 | line vty |
| 58 | bind 127.0.0.2 |
| 59 | ctrl |
| 60 | bind 127.0.0.2 |
| 61 | ---- |
| 62 | |
| 63 | For the following links, OsmoBSC acts as a client and does not listen/bind to a |
| 64 | specific interface, and will hence not encounter conflicts for multiple instances |
| 65 | running on the same interface: |
| 66 | |
| 67 | - The SCCP/M3UA links are established by OsmoBSC contacting an STP. |
| 68 | - The MGCP link is established by OsmoMSC contacting an MGW. |
| 69 | |
| 70 | To run multiple OsmoBSC instances on the same A-interface (SCCP/M3UA), each BSC |
Neels Hofmeyr | b5a25b0 | 2020-03-18 01:01:52 +0100 | [diff] [blame^] | 71 | has to configure a distinct point-code. See <<cs7_config>>. |
Neels Hofmeyr | 21a2c81 | 2020-03-18 01:01:39 +0100 | [diff] [blame] | 72 | |
| 73 | |
| 74 | === Configure primary links |
| 75 | |
| 76 | ==== Configure SCCP/M3UA to connect to an MSC's _A_ interface |
| 77 | |
| 78 | OsmoBSC acts as client to contact an STP instance and establish an SCCP/M3UA |
| 79 | link. |
| 80 | |
| 81 | An example configuration of OsmoBSC's AoIP SCCP link, assuming the BSC at |
| 82 | point-code 1.23.3 and the MSC reachable at point-code 0.23.1 via an SG |
| 83 | listening for M3UA at 127.0.0.1:2905: |
| 84 | |
| 85 | ---- |
| 86 | cs7 instance 0 |
| 87 | point-code 1.23.3 |
| 88 | asp asp-clnt-msc-0 2905 0 m3ua |
| 89 | remote-ip 127.0.0.1 |
| 90 | sctp-role client |
| 91 | sccp-address msc |
| 92 | point-code 0.23.1 |
| 93 | msc 0 |
| 94 | msc-address msc |
| 95 | ---- |
| 96 | |
Neels Hofmeyr | b5a25b0 | 2020-03-18 01:01:52 +0100 | [diff] [blame^] | 97 | This configuration is explained in detail in <<cs7_config>>. |
| 98 | |
Neels Hofmeyr | 21a2c81 | 2020-03-18 01:01:39 +0100 | [diff] [blame] | 99 | ==== Configure MGCP to connect to an MGW |
| 100 | |
| 101 | OsmoBSC uses a media gateway (typically OsmoMGW) to direct RTP streams. By |
| 102 | default, an MGW is expected to receive MGCP requests on the IANA-registered |
| 103 | default port for MGCP (2427) on local host (127.0.0.1). |
| 104 | |
| 105 | Here is an example configuration for a remote MGW: |
| 106 | |
| 107 | ---- |
| 108 | msc 0 |
| 109 | mgw remote-ip 10.9.8.7 |
| 110 | mgw remote-port 2427 |
| 111 | ---- |