Ok guys,
I'm giving up for now, definitely have to take care of more important work
right now :(
The status is as follows:
* You need 'dchan=1,4' in your /etc/dahdi/system.conf
* laforge/rbs2000 has been merged master as it doesn't touch common code
* OpenBSC happily 'initializes' the A-bis link now (IXU OML LAPD+TEI 62)
* The IS MO can (must) be configured manually via the VTY (see last mail)
* SABM on TEI=0/SAPI=62 (TS0) as well as TSI=1/SAPI=62 (TS4) for TRX0
and TRX1 fail. OpenBSC now tries to establish those SAPIs according
to the TRX you configure in openbsc.cfg
* If I configure the IS to route (524,16,4), i.e. connect ICP 524..527 to
ICP 16..19, I get a valid HDLC idle pattern (0x7e) on TS 4, which confirms
the assumption that the ICP assignments are as follows:
ICP 0..3 : E1 Port A TS 1
ICP 4..7 : E1 Port A TS 2
ICP 8..11 : E1 Port A TS 3
ICP 12..15 : E1 Port A TS 4
...
ICP 512..515 : TRX 0 Signalling
ICP 516..519 : TRX 0 Um TS 0..3
ICP 520..523 : TRX 0 Um TS 4..7
ICP 524..527 : TRX 1 Signalling
ICP 528..531 : TRX 1 Um TS 0..3
ICP 532..535 : TRX 1 Um TS 4..7
...
* The DCP numbers referenced in some documents are DCP = ICP / 4
* Further observations:
* Unused traffic slots seem to generate raw bit pattern 0x5555
* Unallocated slots (no assignment in IS) generate raw bit pattern 0x5454
If anyone wants to play with it, feel free to do so. I would definitely
want to know if anyone else gets the SAPI 62 to TRX0 or TRX1 up. As in my
setup not even the Racal 6113 can get that SAPI up, I think I may be facing
soem malfunction/misconfiguration in my RBS.
Regards,
Harald
--
- Harald Welte <laforge(a)gnumonks.org>
http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)