Ericsson RBS » History » Version 12
laforge, 11/04/2020 08:27 AM
1 | 6 | laforge | {{>toc}} |
---|---|---|---|
2 | 1 | laforge | |
3 | 12 | laforge | *NOTE: Please use [[OsmoBSC:]] which has much superior support for RBS2xxx and even RBS6xxx by now* |
4 | |||
5 | 6 | laforge | h1. Ericsson RBS 2000 |
6 | 1 | laforge | |
7 | 6 | laforge | |
8 | There is some initial/experimental code in [[OpenBSC]] to support the Ericsson RBS 2000 family of BTS. |
||
9 | |||
10 | 1 | laforge | As opposed to Siemens/ip.access, Ericsson A-bis is much farther away from the specs, particularly |
11 | since their Organization and Maintenance Layer (OML) is a proprietary protocol called OM2000. |
||
12 | |||
13 | Nonetheless, we have been making quite a bit of progress in getting the RBS 2000 series supported. |
||
14 | Right now it is still not complete. Don't expect anything to work at this stage. |
||
15 | |||
16 | 6 | laforge | We are collecting links to documents describing the Ericsson RBS architecture at [[RBS_Links]] |
17 | 1 | laforge | |
18 | 6 | laforge | h2. Requirements |
19 | 1 | laforge | |
20 | |||
21 | 6 | laforge | * Ericsson RBS 2000 series BTS |
22 | * E1 or T1 interface card, supported by the [[DAHDI]] driver. WE DO NOT SUPPORT RBS with mISDN drivers! |
||
23 | * RBS with software + IDB in default configuration, especially OML TEI set to 62 |
||
24 | * /etc/dahdi/system.conf with "dslot=1,4" in it |
||
25 | 1 | laforge | |
26 | |||
27 | 6 | laforge | h2. Setup |
28 | |||
29 | |||
30 | * Check that dahdi_tool is showing the link as OK, otherwise you have some wiring/polarity issues |
||
31 | * Create an openbsc.cfg that lists your BTS as 'rbs2000' type (see attached example) |
||
32 | ** do not try to be clever and use non-standard E1 timeslot assignments, the code is hard-coded and assumes certain values |
||
33 | * start [[osmo-nitb]] as usual |
||
34 | 9 | dexter | * OM2000 messages can be decoded with Wireshark, set the following options: |
35 | 11 | dexter | ** Right-Click on Link Access Procedure, Channel D (LAPD) --> Protocol Preferences --> Use GSM SAPI values |
36 | ** Right-Click on GSM A-bis OML --> Protocol Preferences --> A-bis dialect to be used --> Ericsson OM2000 |
||
37 | 6 | laforge | |
38 | h2. Status |
||
39 | |||
40 | |||
41 | 1 | laforge | So far, you should get |
42 | 6 | laforge | * A-bis link initialization, i.e. BSC telling the BTS to use TS1 as signalling for IXU/DXU OML |
43 | * [[OpenBSC]] configuring and starting the CF (central function) |
||
44 | * You can manually connect, configure and enable the IS via the VTY |
||
45 | * With some luck, the OML SAPI to the RRU/TRU's can then be established |
||
46 | * Using the '-p foo.pcap' option, you can write a PCAP protocol trace to be used with wireshark and our OM2000 wireshark dissector |
||
47 | 1 | laforge | |
48 | What is NOT supported yet: |
||
49 | 6 | laforge | * Actually initializing the transceivers and Um timeslots |
50 | * Any actual communication with phones |
||
51 | 7 | laforge | * Any form of GPRS. This requires us to implement a PCU compatible with the Ericsson PCU-CCU A-bis protocol. See [[Ericsson_RBS2000_GPRS]] for some collected information on this topic. |