Hello,
Now I can configure the bs11 using the bs11_config. Everything worked fine and I obtained this on bs11_config query :
LMT LOGON: ACK
PHASE: 3 Normal MBCCU0: Load MBCCU1: No Load Abis-link: Restoring
BS11 ATTRIBUTES: BS-11 ESN PCB Serial Number: 001073 BS-11 ESN Hardware Code Number: 135-2044/03.03 BS-11 ESN Firmware Code Number: 135-2044/03.03 PLL Set Value=1053, Work Value=1053
SITE MANAGER ATTRIBUTES: E1 Channel: Port=0 Timeslot=1 (Full Slot) TEI: 25
BS11 Line Interface ATTRIBUTES: PLL Mode: Standalone
BS11 Power Amplifier 0 ATTRIBUTES: TRX Power: 30mW (GSM) Mon May 25 16:01:12 2009 <0020> abis_nm.c:811 GET ATTRIBUTE NACK LMT LOGOFF: ACK
I didn't doanwload: -the SAFETY LOAD software -the BTS software Is it necessary since I can reach Phase 3 and since I can see the Firmware Code Number?
I continued to follow the "getting started" tutorial untill the E1 Link and I have the following problem when launching bsc_hack :
./bsc_hack -f 123 --debug=DRLL:DCC:DMM:DRR:DRSL:DNM:DMI:DMUX:DPAG:DRLL:DSMS DB: Database initialized. DB: Database prepared. 1 device found id: 0 Dprotocols: 00000018 Bprotocols: 0000006e protocol: 4 nrbchan: 30 name: hfc-e1.1 activate bchan activate bchan Mon May 25 16:07:39 2009 <1000> input/misdn.c:125 alen =6, dev(0) channel(0) sapi(63) tei(127) Mon May 25 16:07:39 2009 <1000> input/misdn.c:128 <= len = 12, prim(0x8) id(0x7f3f): DL_INFORMATION_IND Mon May 25 16:07:39 2009 <1000> input/misdn.c:135 DL_INFORMATION_IND: use channel(0) sapi(63) tei(127) for now mISDN message for unknown sign_link
May be it's coming from my BN1E1 card from Beronet. I only changed the Dip switches for 120 ohms. I can see 2 steady red led (which means i am in NT mode, TE mode deactivate). Both green leds are off (is it normal?).
/* HFC-E1 OEM */ + /* 2 red blinking: NT mode deactivate + * 2 red steady: TE mode deactivate + * left green: L1 active + * left red: frame sync, but no L1 + * right green: L2 active + */
Anyone? Thanks in advance!
Best regards Eric Cathelinaud
On Mon, May 25, 2009 at 03:08:10PM +0200, Eric Cathelinaud wrote:
I didn't doanwload: -the SAFETY LOAD software -the BTS software Is it necessary since I can reach Phase 3 and since I can see the Firmware Code Number?
no, it is not. the firmware is completely installed on your system, otherwise the TRX0 would never get into 'Load"
Mon May 25 16:07:39 2009 <1000> input/misdn.c:125 alen =6, dev(0) channel(0) sapi(63) tei(127) Mon May 25 16:07:39 2009 <1000> input/misdn.c:128 <= len = 12, prim(0x8) id(0x7f3f): DL_INFORMATION_IND Mon May 25 16:07:39 2009 <1000> input/misdn.c:135 DL_INFORMATION_IND: use channel(0) sapi(63) tei(127) for now mISDN message for unknown sign_link
this basically means that the TEI manager was instantiated on the E1 link, but no TEIs were established, most likely a layer 1 problem...
Regards,
I think I still have a problem with mISDN cause I checked the RJ45 cable connections and it's ok. If I try a lsmod I can't see any mISDN_*** modules. But the line in /boot/grub/menu.lst "hfcmulti.dslot=1" is recognized at the boot (no more ignored). In my menuconfig I put an * for : <*> Modular ISDN driver ---> <*>Digital Audio Processing of transparent data <*>ISDN over IP tunnel <*>Support for HFC PCI cards <*>Support for HFC multiport cards (HFC-4S/8S/E1)
Is there something more to do for mISDN? I saw on mISDN.org that mISDNv2 is already in the kernel >= 2.6.27 so I were thinking it should work directly.
I can't even do "modprobe mISDN_core" for exemple. mISDN_core is not found. So I checked the /lib/modules/2.6.27.4/ directories. I didn't find any mISDN directory in /lib/modules/ 2.6.27.4/kernel/drivers/isdn but I found it in /lib/modules/2.6.27.4/build/drivers/isdn with about 60 files inside (.o, .c, .h and .ko) and I found it also in /lib/modules/2.6.27.4/source/drivers/isdn (exactly the same content in mISDN directory)
Is this normal?
Thanks Eric Cathelinaud
2009/5/26, Harald Welte laforge@gnumonks.org:
On Mon, May 25, 2009 at 03:08:10PM +0200, Eric Cathelinaud wrote:
I didn't doanwload: -the SAFETY LOAD software -the BTS software Is it necessary since I can reach Phase 3 and since I can see the
Firmware
Code Number?
no, it is not. the firmware is completely installed on your system, otherwise the TRX0 would never get into 'Load"
Mon May 25 16:07:39 2009 <1000> input/misdn.c:125 alen =6, dev(0)
channel(0)
sapi(63) tei(127) Mon May 25 16:07:39 2009 <1000> input/misdn.c:128 <= len = 12, prim(0x8) id(0x7f3f): DL_INFORMATION_IND Mon May 25 16:07:39 2009 <1000> input/misdn.c:135 DL_INFORMATION_IND: use channel(0) sapi(63) tei(127) for now mISDN message for unknown sign_link
this basically means that the TEI manager was instantiated on the E1 link, but no TEIs were established, most likely a layer 1 problem...
Regards,
- Harald Welte laforge@gnumonks.org
============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)
On Wed, 27 May 2009 18:00:19 +0200 Eric Cathelinaud e.cathelinaud@googlemail.com wrote:
Is this normal?
Yes, it is, as you compiled it into the kernel and not as a module. (<*> = Builtin, <M> = Module in menuconfig).
cheers,