RBS6000 OM2000 Extensions » History » Version 2
laforge, 07/30/2020 06:32 AM
| 1 | 1 | laforge | h1. RBS6000 OM2000 Extensions |
|---|---|---|---|
| 2 | |||
| 3 | 2 | laforge | When looking at a [[DUG 20]] with OM2000 > G12R10, we are seeing a few new OM2000 message types, all of them on the SAPI=62/TEI=62, i.e. BTS-central OML link: |
| 4 | 1 | laforge | |
| 5 | * 0x012c (MCTR Configuration Request) |
||
| 6 | * 0x012e (MCTR Configuration Request Accept) |
||
| 7 | * 0x0132 (MCTR Configuration Result) |
||
| 8 | * 0x0130 (MCTR Configuration Result ACK) |
||
| 9 | * 0x0134 (MCTR suspected Alarm/Status/Error?) |
||
| 10 | 2 | laforge | |
| 11 | 1 | laforge | |
| 12 | We are also seeing a few new information elements: |
||
| 13 | |||
| 14 | * DEI 0xB5 in TX Config Req, 2 bytes fixed length (06fe) |
||
| 15 | * DEI 0xA8 in 0x012c, 2 bytes fixed length (0300, c001, 0f00) |
||
| 16 | * DEI 0xA9 in 0x012c, 1 byte fixed length (32) |
||
| 17 | * DEI 0xAA in 0x012c, 1 byte fixed length (06) |
||
| 18 | * DEI 0xAB in 0x012c, 2 bytes fixed length (0100) |
||
| 19 | * DEI 0xAC in 0x0134, no structure? |
