-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hey there,
I have come across a nanoBTS 165AU but since is used and not tested from the previous owner, I guess it has set a static IP.
After turned on is booting (RED light) and then remains (ORANGE not flashing) even if the eth is connected to the router.
At the moment I am trying with ipaccess-find and BtsInstaller to find in on my LAN .
Unfortunately it is not answering and is not even getting an IP from the router by the DHCP daemon.
Two possibilities, I have thought:
- - an hw/sw issue;
- - a Static IP is set.
Supposing that is the 2nd possibility, I was thinking:
- - to change private class of my LAN, to see if it changes something;
- - to make an hard reset of the bts.
Do you know if it possible to reset in someway?
Ever happened this issue to you guys?
Suggestions or insults are welcome.
Thanks in advance.
Cheers,
Luca
P.S.: I don't recall exactly, but one time I heard that is possible to reset by short-circuiting some pins of the LAN/48VDC eth connector. Is it right?!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org
iQIcBAEBAgAGBQJSE682AAoJEPLE1Qsi6ZiTuKkQAJaYGFTgMF5XlWuZuCI1eSvU
lVCvpdB+fDRY7o6iut3y0fGlS1ZOIS8X93c7/T0XKUvSJaZ2ARIGjqi81A4XlkAK
pdFvBNPKixYATYZYhP3nIggC1QGK9fuWQSUKVEGgnswsXt0VaJKdEwgn0CX7ttku
uoh6FM3vtp30drB4t9oe0bW9M9qzGz6yyw+8asaqQBs8bafOHm4+S4kJsN6lYmPU
wY/s8ctzqZerNI0MwBVASZCFldsyWe0NuduquYZlwg4god996srFNkVQL+o9nrmF
vmPb896DTsCdivwqs+UyaZOgp1mKxjtfco275pVATG4qSAgz/JYQBxWK6fWQr+Zv
PIzQvFLME1kh/29nUihxw93mzju5Rz1naTosx5+Fs7jPjCFocqD5Var3hkU4iu78
kNALJNx6UGOdfbqcInO30ltSm21HH1QBJnIoZf6MblELvHcvHbBNyPB8zM13suoS
y3/oD/wcXefQaMaSa5HFc30ydJHBWS+adNlVp3fdYYArZaVkFxaVjJx8fW1juPVx
54aco5j7/tZD5tfg9FCOTHqmAiOVDqjs7nZrOpsRdkdPJHq2uHbGmHGqyhZlVWNv
B+9/eiOdQyKZ5R+3vvRrmhBe9g2a28xtRI7N8KxwCov0wbA6R0h8l2UtGza6NTcn
EUdW3ptIWP216tSFdVTs
=9Ctc
-----END PGP SIGNATURE-----
Hi Harald (sorry for the typo).
I think that line 10 is a log of the USSD call I made.
My configuration is:
- Followed the tutorial. (
http://openbsc.osmocom.org/trac/wiki/network_from_scratch (using all
configurations shown in the tutoria, except the network name, that I
changed to DCG).
- Using a Ettus USRP N210
- All libraries installed in my notebook, with Ubuntu 13.04
kernel 3.8.0-29-generic.
- Starting osmo-nitb with the following command: osmo-nitb -c
~/.osmocom/open-bsc.cfg -l ~/.osmocom/hlr.sqlite3 -P -m -C
--debug=DRLL:DCC:DMM:DRR:DRSL:DNM
- I manually select the network in the Network Preferences. The phone is an
old Motorola Z6.
Hope it helps. If you need more information, just ask. If you need, I can
use other configurations or command options.
Best Regard,
On Sat, Aug 24, 2013 at 5:37 PM, Alexander Chemeris <
alexander.chemeris(a)gmail.com> wrote:
> Of-list: His name is "Harald", not "Herald" :)
>
> On Sun, Aug 25, 2013 at 12:36 AM, Alexander Chemeris
> <alexander.chemeris(a)gmail.com> wrote:
> > Maicon,
> >
> > Your log doesn't show any user activity, so you either (1) haven't
> > enabled enough logging or (2) your phone is not attached to the
> > OsmoNITB network.
> >
> > If you followed instructions from
> > http://openbsc.osmocom.org/trac/wiki/network_from_scratch, then you
> > should have enough logging enabled. In this case we have only option
> > (2) left and it would be great if you specify your software and
> > hardware setup and describe the procedure you're using to select the
> > network in your phone.
> >
> > On Sat, Aug 24, 2013 at 11:46 PM, Maicon Kist <maicon.kist(a)inf.ufrgs.br>
> wrote:
> >> Hi Herald,
> >>
> >> I'm trying to check the log messages. I'm trying to understand whats
> >> happening, but so far nothing came to my mind.
> >> I'm attaching the osmo-nitb log messages right before I call the *#100#
> >> number.
> >>
> >> Do you have any suggestion?
> >>
> >> PS: SMS and calls are working perfectly.
> >>
> >> Best Regards,
> >>
> >>
> >> On Sat, Aug 24, 2013 at 11:59 AM, Alexander Chemeris
> >> <alexander.chemeris(a)gmail.com> wrote:
> >>>
> >>> On Thu, Aug 22, 2013 at 9:40 PM, Maicon Kist <maicon.kist(a)inf.ufrgs.br
> >
> >>> wrote:
> >>> > Is there a tutorial in how to make a USSD application work in a
> OpenBSC
> >>> > network?
> >>> > Firstly I'm want to implement a simple "Hello World" application. eg.
> >>> > the
> >>> > client enter with a valid USSD number (*something) and the "Hello
> World"
> >>> > application executes.
> >>>
> >>> Look at the openbsc/src/libmsc/ussd.c file - it's very easy to extend
> >>> it to respond to various USSD requests. It would be great if we have a
> >>> kind of external API for implementing external USSD applications
> >>> without touching the OsmoNITB code. Patches for this are welcome.
> >>>
> >>> --
> >>> Regards,
> >>> Alexander Chemeris.
> >>> CEO, Fairwaves LLC / ООО УмРадио
> >>> http://fairwaves.ru
> >>
> >>
> >
> >
> >
> > --
> > Regards,
> > Alexander Chemeris.
> > CEO, Fairwaves LLC / ООО УмРадио
> > http://fairwaves.ru
>
>
>
> --
> Regards,
> Alexander Chemeris.
> CEO, Fairwaves LLC / ООО УмРадио
> http://fairwaves.ru
>
Hi list,
Peter, thank you for your reply.
I still have questions about media control:
1) when parsing MGCP CRCX, sdp is not expected. May I change it?
2) I still can't run media in BSC mode. Seems I'm missing something.
osmo-bsc and osmo-bsc_mgcp are running
BSSAP works perfectly
But it seems two interfaces are working completely independent:
-- MGCP between MSC and BSC
-- interface between BSC and BTS (ip.access):
at MGCP, connection is acknowledged, endpoint is allocated (at BSC
ip=192.168.1.11)
at ip.access interface between BSC and BTS, BTS replies to ip.accessCRCX
with proper acknowledgement with proper ip:port at BTS (192.168.1.9) , then
BSC issues ip.accessMDCX with endpoint ip zero:
7e:73:01:09:f8:00:2d:*f0:00:00:00:00*:f1:0f:be:f4:00:f2:03
My attempts to modify connection at MGCP interface has no impact on
ip.access interface
The key question, I'm not getting how osmo-bsc and osmo0bsc_mgcp are
interacting.
Thank you,
Dmitri
PS my configs are
mgcp
local ip 192.168.1.11
bts ip 192.168.1.9
bind ip 192.168.1.11
bind port 2427
rtp base 6000
sdp audio payload number 3
sdp audio payload name GSM/8000
number endpoints 31
and
e1_input
e1_line 0 driver ipa
network
network country code 250
mobile network code 07
short name OsmoBSC
long name OsmoBSC
auth policy closed
location updating reject cause 13
! encryption a5 1
neci 1
paging any use tch 0
rrlp mode none
mm info 1
handover 0
handover window rxlev averaging 10
handover window rxqual averaging 1
handover window rxlev neighbor averaging 10
handover power budget interval 6
handover power budget hysteresis 3
handover maximum distance 9999
timer t3101 10
timer t3103 0
timer t3105 0
timer t3107 0
timer t3109 0
timer t3111 0
timer t3113 60
timer t3115 0
timer t3117 0
timer t3119 0
timer t3122 0
timer t3141 0
dtx-used 0
subscriber-keep-in-ram 0
bts 0
type nanobts
band PCS1900
cell_identity 2611
location_area_code 51601
training_sequence_code 7
base_station_id_code 63
ms max power 15
cell reselection hysteresis 4
rxlev access min 0
channel allocator ascending
rach tx integer 9
rach max transmission 7
ip.access unit_id 1801 0
oml ip.access stream_id 255 line 0
neighbor-list mode manual-si5
gprs mode none
trx 0
rf_locked 0
arfcn 810
nominal power 0
max_power_red 20
rsl e1 tei 0
timeslot 0
phys_chan_config CCCH+SDCCH4
hopping enabled 0
timeslot 1
phys_chan_config TCH/F
hopping enabled 0
timeslot 2
phys_chan_config TCH/F
hopping enabled 0
timeslot 3
phys_chan_config TCH/F
hopping enabled 0
timeslot 4
phys_chan_config TCH/F
hopping enabled 0
timeslot 5
phys_chan_config TCH/F
hopping enabled 0
timeslot 6
phys_chan_config TCH/F
hopping enabled 0
timeslot 7
phys_chan_config TCH/F
hopping enabled 0
msc
! ip.access rtp-base 6000
timeout-ping 20
timeout-pong 5
dest 192.168.50.10 5000 0
in fact, BSSAP goes from a card over VPN, while MGCP comes from
self-written TRAU running locally, the same host as BSC
Change '%s(bsc)#' to '%s(config-bsc)# '. The missing trailing blank
brakes osmopy's VTYInteract.command() because the blank is contained
in the end patterns which are checked to decide whether to leave the
select loop. Thus trying to execute the 'bsc' command there blocks
the test script forever.
---
openbsc/src/osmo-bsc/osmo_bsc_vty.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/openbsc/src/osmo-bsc/osmo_bsc_vty.c b/openbsc/src/osmo-bsc/osmo_bsc_vty.c
index 8eaa55b..f6cf1a0 100644
--- a/openbsc/src/osmo-bsc/osmo_bsc_vty.c
+++ b/openbsc/src/osmo-bsc/osmo_bsc_vty.c
@@ -43,7 +43,7 @@ static struct osmo_msc_data *osmo_msc_data(struct vty *vty)
static struct cmd_node bsc_node = {
BSC_NODE,
- "%s(bsc)#",
+ "%s(config-bsc)# ",
1,
};
--
1.7.9.5
Hello,
Where can download/find the *.SWL file for flash the BS11 ?
Thanks
bye
On 12/06/2013 00:48, choukoumoun wrote:
> Hello,
>
> Thanks you very much for your help (Love the open-source/hacker community)
> I'll try that tomorrow and soon I will return.
>
> Bye!
>
> Le 12/06/2013 00:06, Sergey V. Efimov a écrit :
>> Hello,
>>
>> Yep, it seems you need to reflash your BS11. You can start with
>> "bs11_config -S" to download the safety file into the station if you
>> have one.
>> The next step is to download the real working firmware into the
>> station. It can take up to 1,5 hours depending on the various conditions.
>> You need to get several files, listed at
>> http://openbsc.osmocom.org/trac/wiki/bs11_config, try to ask your seller.
>>
>> At the end of the flashing process (after reboot) you should see
>> MBCCU0/MBCCU1 No Load / Load messages.
>>
>> Sergey.
>>
>> On Jun 12, 2013, at 1:48 AM, choukoumoun wrote:
>>
>>> Hello,
>>>
>>> it is the boot-up log for my Bs11
>>>
>>>
>>>
>>> LMT LOGON: ACK
>>>
>>> PHASE: 1 load SMU Intended Abis-link: down
>>> PHASE: 1 load SMU Intended Abis-link: down
>>> PHASE: 1 load SMU Intended Abis-link: down
>>> PHASE: 1 load SMU Intended Abis-link: down
>>> PHASE: 1 load SMU Intended Abis-link: down
>>> PHASE: 1 load SMU Intended Abis-link: down
>>> PHASE: 1 load SMU Intended Abis-link: down
>>> PHASE: 1 load SMU Intended Abis-link: down
>>> PHASE: 1 load SMU Intended Abis-link: down
>>> PHASE: 1 load SMU Intended Abis-link: down
>>> PHASE: 1 load SMU Intended Abis-link: down
>>> PHASE: 1 load SMU Intended Abis-link: down
>>> PHASE: 1 load SMU Intended Abis-link: down
>>> PHASE: 1 load SMU Intended Abis-link: down
>>> PHASE: 1 load SMU Intended Abis-link: down
>>> PHASE: 1 load SMU Intended Abis-link: down
>>> PHASE: 1 load SMU Intended Abis-link: down
>>> PHASE: 1 load SMU Intended Abis-link: down
>>> PHASE: 1 load SMU Intended Abis-link: down
>>> PHASE: 1 load SMU Intended Abis-link: down
>>> PHASE: 1 Unknow Abis-link: down
>>> PHASE: 1 Unknow Abis-link: down
>>> PHASE: 1 Unknow Abis-link: down
>>> PHASE: 1 Unknow Abis-link: down
>>> PHASE: 1 Unknow Abis-link: down
>>> PHASE: 1 Unknow Abis-link: down
>>> PHASE: 1 Unknow Abis-link: down
>>> PHASE: 1 Unknow Abis-link: down
>>> PHASE: 1 Unknow Abis-link: down
>>> PHASE: 1 Unknow Abis-link: down
>>> PHASE: 1 Unknow Abis-link: down
>>> PHASE: 1 Unknow Abis-link: down
>>> PHASE: 1 Unknow Abis-link: down
>>> PHASE: 1 Unknow Abis-link: down
>>> PHASE: 1 Unknow Abis-link: down
>>> PHASE: 1 Unknow Abis-link: down
>>> PHASE: 1 Unknow Abis-link: down
>>> PHASE: 1 Unknow Abis-link: down
>>>
>>>
>>> Iawait yourreplywith great pleasure
>>>
>>> best,
>>> Choukoumoun
>>>
>>> Le 10/06/2013 11:58, Sergey V. Efimov a écrit :
>>>> Hello,
>>>>
>>>> I recall that something similar happened when I tried to monitor freshly received
>>>> BS-11 without operating firmware. Could you please provide full boot-up log.
>>>>
>>>> Sergey.
>>>>
>>>> On Jun 10, 2013, at 1:36 AM, choukoumoun wrote:
>>>>
>>>>> Hello list,
>>>>>
>>>>> I have a problem with BS11 at startup:
>>>>>
>>>>>
>>>>> When I put the BS11 voltage and that I connect in serial and I run:
>>>>>
>>>>> ./bs11_config-p / dev/ttyUSB0 query
>>>>>
>>>>> I like the result:
>>>>>
>>>>>
>>>>> PHASE 1: unknown Abis-link: Down
>>>>>
>>>>> PHASE 1: unknown Abis-link: Down
>>>>>
>>>>> PHASE 1: unknown Abis-link: Down
>>>>>
>>>>> PHASE 1: unknown Abis-link: Down
>>>>>
>>>>> PHASE 1: unknown Abis-link: Down
>>>>>
>>>>> PHASE 1: unknown Abis-link: Down
>>>>>
>>>>> PHASE 1: unknown Abis-link: Down
>>>>>
>>>>>
>>>>> constantly and eternally ......
>>>>>
>>>>> Any idea??
>>>>>
>>>>>
>>>>> thank you
>>>>>
>>>>>
>>>
>>>
>>
>
Hi,
As the caption states, it removes duplicated library linkage. in
tests/db/Makefile.am.
--
Regards,
Alexander Chemeris.
CEO, Fairwaves LLC / ООО УмРадио
http://fairwaves.ru
Hi Harald,
We're trying out SMPP interconnection and found that for Submit_SM
(aka MT-SMS) sender is always set to an extension of subscriber ID 1.
Looking into the code, this happens because we set "sms->sender" to
point to subscriber ID 1 in submit_to_sms() function in SMPP code:
/* fill in the source address */
sms->sender = subscr_get_by_id(net, 1);
sms->src.ton = submit->source_addr_ton;
sms->src.npi = submit->source_addr_npi;
strncpy(sms->src.addr, (char *)submit->source_addr, sizeof(sms->src.addr)-1);
And then src.addr/ton/npi are ignored when we store to the SMS DB and
only subscriber ID is stored:
/* FIXME: correct validity period */
result = dbi_conn_queryf(conn,
"INSERT INTO SMS "
"(created, sender_id, receiver_id, valid_until, "
"reply_path_req, status_rep_req, protocol_id, "
"data_coding_scheme, ud_hdr_ind, dest_addr, "
"user_data, text) VALUES "
"(datetime('now'), %llu, %llu, %u, "
"%u, %u, %u, %u, %u, %s, %s, %s)",
sms->sender->id,
sms->receiver ? sms->receiver->id : 0, validity_timestamp,
sms->reply_path_req, sms->status_rep_req, sms->protocol_id,
sms->data_coding_scheme, sms->ud_hdr_ind,
q_daddr, q_udata, q_text);
So when we read SMS back from the DB, sender address is taken from
that subscriber.
It seems that a solution is to store actual ton/npi/addr in the SMS DB
instead of storing ID. Then we could set sms->sender to NULL and just
ignore it.
Is there anything wrong with this approach? Otherwise we'll work on a
patch to implement that.
PS What is the current policy about changing DB layouts - just
increase SCHEMA_REVISION?
--
Regards,
Alexander Chemeris.
CEO, Fairwaves LLC / ООО УмРадио
http://fairwaves.ru
Good day list
We acquired a BS-11 microBTS a while ago and in the preliminary stages
of setting up the equipment came upon the following:
background -
1. we installed OpenBSC as per the OpenBSC wiki.
2. we manufactured a serial cable to interact with the BS-11.
3. using bs11_config as per the bs11_config wiki page we started the
BS-11 and got the following:
$ ./bs11_config -p /dev/ttyUSB0
bs11_config (C) 2009 by Harald Welte and Dieter Spaar
This is FREE SOFTWARE with ABSOLUTELY NO WARRANTY
LMT LOGON: ACK
PHASE: 1 Warm Up Abis-link: Down
PHASE: 1 Warm Up Abis-link: Down
PHASE: 1 Warm Up Abis-link: Down
.
.
PHASE: 1 Warm Up Abis-link: Down
PHASE: 1 Software required Abis-link: Down
No valid safety Load file "BTSBMC76.SWI"
After this nothing further happens.
From the wiki page I conclude that the file in question is the SMU safety load that is needed to create the minimal configuration to get the BS-11 to boot.
There seem to be another firmware image needed for the BS-11 namely the HS011106.SWL
Am I correct in my assumption that the BS-11 was not preloaded with this software?
Where do I get these firmware images as the wiki page states that the project can't provide any of the firmware due to copyright constraints.
Regards
--
Paul van Wyk
_____________________________________________________
TruTeq Wireless (Pty) Ltd. Tel +27 12 667 1530
http://www.truteq.com Fax +27 12 667 1531
Copyright & Legal: http://truteq.com/legal_notice.pdf