diff options
| author | Philipp Maier <pmaier@sysmocom.de> | 2020-11-09 16:47:27 +0100 |
|---|---|---|
| committer | Philipp Maier <pmaier@sysmocom.de> | 2020-11-10 21:25:40 +0100 |
| commit | 70d78f21f289e5fa2ce0073889a59df8e0e2f5b9 (patch) | |
| tree | a148e8d8f1e6e6183301142d74d54600995d4aeb /doc | |
| parent | 5e92f628ab7089f3d8efcb04b6674733eee0ccd3 (diff) | |
rsl.adoc: add info about RSL_IE_OSMO_REP_ACCH_CAP
The RSL documentation should reflect some explanatory info about the
recently added RSL_IE_OSMO_REP_ACCH_CAP IE.
Depends: libosmocore I61ea6bf54ea90bd69b73ea0f0f3dc19a4214207b
Change-Id: I1d70846c2c184f7a189074c51137bc1f38fb3859
Related: OS#4796 SYS#5114
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/manuals/abis/rsl.adoc | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/manuals/abis/rsl.adoc b/doc/manuals/abis/rsl.adoc index 20ee8362..8843a74e 100644 --- a/doc/manuals/abis/rsl.adoc +++ b/doc/manuals/abis/rsl.adoc @@ -842,6 +842,7 @@ addition to those indicated in 3GPP TS 08.58 Section 9.3: |=== | IEI | Name | This document ยง | 0x01 | RSL_IE_CHAN_NR | <<RSL_IE_CHAN_NR>> +| 0x60 | RSL_IE_OSMO_REP_ACCH_CAP | <<RSL_IE_OSMO_REP_ACCH_CAP>> | 0xf0 | RSL_IE_IPAC_REMOTE_IP | <<RSL_IE_IPAC_REMOTE_IP>> | 0xf1 | RSL_IE_IPAC_REMOTE_PORT | <<RSL_IE_IPAC_REMOTE_PORT>> | 0xf3 | RSL_IE_IPAC_LOCAL_PORT | <<RSL_IE_IPAC_LOCAL_PORT>> @@ -953,6 +954,15 @@ This information element contains the RTP payload identifier, which is used in the PT (Payload Type) field of the RTP header in subsequent transmissions of the RTP flow. +[[RSL_IE_OSMO_REP_ACCH_CAP]] +==== RSL_IE_OSMO_REP_ACCH_CAP + +This is a one byte length TLV IE that is used to enable or disable repeated ACCH +capabilities on the BTS side during Channel Activation and Mode Modify. If the +IE is present and its value byte is set to 0x01, then the BTS will enable +repeated ACCH capabilities, otherwise the channel is activated without repeated +ACCH capabilities present. + === A-bis RSL Initialization / BTS bring-up Upon receiving the 'IPA RSL CONNECT' OML message by the respective |