| Pau Espin Pedrol | 3fb2359 | 2019-07-19 17:20:57 +0200 | [diff] [blame] | 1 | include::{commondir}/chapters/osmux/osmux.adoc[] |
| 2 | |
| 3 | === Osmux Support in {program-name} |
| 4 | |
| 5 | ==== {program-name} in a A/IP with IPA/SCCPlite network setup |
| 6 | |
| 7 | In this kind of setup, Osmux is transparent to {program-name} and no specific |
| 8 | configuration is required here, since the CN-side of the BSC-attached MGW is |
| 9 | managed directly by the MSC. |
| 10 | |
| 11 | So, in this case, only MSC and MGW (both for MSC-attached one and BSC-attached |
| 12 | one) need to be configured explicitly. |
| 13 | |
| 14 | ==== {program-name} in a 3GPP AoIP network setup |
| 15 | |
| 16 | Osmux usage in {program-name} in managed through the VTY command `osmux |
| 17 | (on|off|only)`. Once enabled (`on` or `only`), {program-name} will start |
| 18 | appending the vendor specific _Osmux Support_ IE in _BSSMAP RESET_ and _BSSMAP |
| 19 | RESET-ACK_ message towards the MSC in order to announce it supports Osmux. This |
| 20 | way, the MSC can decide whether to use Osmux or not based on this information |
| 21 | when setting up a call (this time using _Osmux CID_ IE). It should be noted that |
| 22 | this option should not be enabled unless MSC managing {program-name} supports |
| 23 | handling this extension IE (like OsmoMSC), a 3rd-party MSC might otherwise |
| 24 | refuse the related _RESET_/_RESET-ACK_ messages. |
| 25 | |
| 26 | {program-name} will behave differently during call set up based on the VTY |
| 27 | command presented above: |
| 28 | |
| 29 | * `off`: If _BSSMAP Assign Request_ from MSC contains _Osmux CID_ IE, meaning |
| 30 | MSC wants to use Osmux for this call, then {program-name} will reject the |
| 31 | assignment and the call set up will fail. |
| 32 | * `on`: BSC will support and accept both Osmux and non-Osmux (RTP) upon call set |
| 33 | up. If _BSSMAP Assign Request_ from MSC contains _Osmux CID_ IE, |
| 34 | {program-name} will instruct its MGW to set up an Osmux connection on the |
| 35 | CN-side of the MGCP endpoint, and will provide the MSC with its _recvCID_ |
| Martin Hauke | a29affd | 2019-11-13 22:10:41 +0100 | [diff] [blame] | 36 | through the extension IE _Osmux CID_ appended to the _BSSMAP Assign Complete_ |
| Pau Espin Pedrol | 3fb2359 | 2019-07-19 17:20:57 +0200 | [diff] [blame] | 37 | message. On the other hand, if _BSSMAP Assign Request_ doesn't contain an |
| 38 | _Osmux CID_ IE, {program-name} will instruct its MGW to set up a regular RTP |
| 39 | connection on the CN-side of the MGCP endpoint. |
| 40 | * `only`: Same as per `on`, except that {program-name} will accept only Osmux |
| 41 | calls on the CN-side, this is, if _BSSMAP Assign Request_ from MSC doesn't |
| 42 | contain an _Osmux CID_ IE, it will reject the assignment and the call set up |
| 43 | will fail. |