Ericsson RBS » History » Version 3
laforge, 02/19/2016 10:47 PM
link to rbs_links
| 1 | 1 | laforge | [[PageOutline]] |
|---|---|---|---|
| 2 | = Ericsson RBS 2000 = |
||
| 3 | |||
| 4 | There is some initial/experimental code in OpenBSC to support the Ericsson RBS 2000 family of BTS. |
||
| 5 | |||
| 6 | As opposed to Siemens/ip.access, Ericsson A-bis is much farther away from the specs, particularly |
||
| 7 | since their Organization and Maintenance Layer (OML) is a proprietary protocol called OM2000. |
||
| 8 | |||
| 9 | Nonetheless, we have been making quite a bit of progress in getting the RBS 2000 series supported. |
||
| 10 | Right now it is still not complete. Don't expect anything to work at this stage. |
||
| 11 | |||
| 12 | 3 | laforge | We are collecting links to documents describing the Ericsson RBS architecture at [wiki:RBS_Links] |
| 13 | 1 | laforge | == Requirements == |
| 14 | |||
| 15 | 2 | laforge | * Ericsson RBS 2000 series BTS |
| 16 | * E1 or T1 interface card, supported by the [wiki:DAHDI] driver. WE DO NOT SUPPORT RBS with mISDN drivers! |
||
| 17 | * RBS with software + IDB in default configuration, especially OML TEI set to 62 |
||
| 18 | * /etc/dahdi/system.conf with "dslot=1,4" in it |
||
| 19 | 1 | laforge | |
| 20 | == Setup == |
||
| 21 | |||
| 22 | 2 | laforge | * Check that dahdi_tool is showing the link as OK, otherwise you have some wiring/polarity issues |
| 23 | * Create an openbsc.cfg that lists your BTS as 'rbs2000' type (see attached example) |
||
| 24 | * do not try to be clever and use non-standard E1 timeslot assignments, the code is hard-coded and assumes certain values |
||
| 25 | * start [wiki:bsc_hack] as usual |
||
| 26 | 1 | laforge | |
| 27 | == Status == |
||
| 28 | |||
| 29 | So far, you should get |
||
| 30 | * A-bis link initialization, i.e. BSC telling the BTS to use TS1 as signalling for IXU/DXU OML |
||
| 31 | * OpenBSC configuring and starting the CF (central function) |
||
| 32 | * You can manually connect, configure and enable the IS via the VTY |
||
| 33 | * With some luck, the OML SAPI to the RRU/TRU's can then be established |
||
| 34 | * Using the '-p foo.pcap' option, you can write a PCAP protocol trace to be used with wireshark and our OM2000 wireshark dissector |
||
| 35 | |||
| 36 | What is NOT supported yet: |
||
| 37 | * Actually initializing the transceivers and Um timeslots |
||
| 38 | * Any actual communication with phones |
