Hello,
second try to add support to bs11_config for bport0/1 configuration. This
time with enum abis_bs11_line_cfg.
It seems sometimes creating bport1 fails, even LMT shows create obj
greyed out. Don't know why yet.
Regards,
Daniel Willmann
Daniel Willmann (1):
Add {create,delete}-bport1 and bport0-{star,multidrop} to bs11-config
openbsc/include/openbsc/abis_nm.h | 10 +++++++++-
openbsc/src/abis_nm.c | 31 +++++++++++++++++++++++++++++--
openbsc/src/bs11_config.c | 26 ++++++++++++++++++++++++++
3 files changed, 64 insertions(+), 3 deletions(-)
Hi,
I'm currently implementing Early Assignment in the On Waves branch and as part
of this I will have to take care of RSL channel releases as well.
Someone else was pointing this out as well but I could not find the email. Our
channel release is a bit sloppy and I will fix it and start using T3111 and
T3109 in the rsl code for doing so.
In the "normal" case (bsc on the left, bts on the right):
RSL Channel Release -->
<- RSL Channel Release Ack
<- Release Indication SAPI=0
RSL Channel Release ->
<- RSL Channel Release Ack
In the "abnormal" case:
<- Error Indication
RSL Channel Release ->
<- RSL Channel Release Ack
<- Release Indication SAPI=0
RSL Channel Release ->
<- RSL Channel Release Ack
I'm going to change that into the following way.
"normal" case:
1.) Release the established SAPIs
2.) After their ACKs release the Channel
Have all this guarded by T3109 (or whatever is more appropriate)
"abnormal" case:
1.) Start T3109
2.) Then do the normal case.
During the shutdown sequence I need to make sure that we are not allocating
the channel again. I'm thinking of either using the chan mode Harald was
introducing while doing the hand over work, or just a "locked" flag to not
assign the channel.
I hope to be done with this by tomorrow or the day after, anyone has comments
or ideas on how to approach this?
z.
Hi all,
I'm cross-posting this to both OpenBTS and OpenBSC mailing lists
in a hope to get wider audience. Sorry if you get this message twice.
Ivan and I are working on USSD support for OpenBTS now. We've got
all our test phones working except old Siemens A52 (newer A65 is ok).
When we request more information from the phone in order to create
menu-like experience, this phone deny processing any further USSD
with "NOT EXECUTED" error, while still keeping L3 channel open.
This looks quite much like a bug in the phone, but also seems we have
a problem in our code too - I tested it with my working SIM card and
my normal operator USSD menu and it works.
So I kindly ask everyone who have Nokia 3310 with MBUS cable or
any other GSM sniffer and have access to live network with working
USSD to help us with gathering some real-network data. Please:
1) Call some simple USSD request, which just return a single piece
of data. Like "Show my balance"
2) Call some menu-like USSD request and go through several levels
of it. On our network we have a kind of "Self-care service" through
USSD which works that way.
3) If you know how to summon network-originated USSD request or
notification - we will appreciate if you include this too. I have never
seen this on my home network, though.
4) Send me your trace.
Thanks!
--
Regards,
Alexander Chemeris.
Hi there,
Has anyone been working on using OpenBSC with a Sangoma E1 card connected to
the BTS ? I guess they would be some patches to add to the generic driver to
have it fully working and recognized within the OpenBSC framework ?
The last thread I saw related to Sangoma was from Oystein :
http://lists.gnumonks.org/pipermail/openbsc/2009-August/000821.html
Cheers,
Xavier.
Hi
What needs to be changed in openbsc in order to add a new input ?
I'm currently developing a GAN protocol stack, and would like to add it to
openbsc so it could deal with the DTAP msg coming from GAN
regards,
--
k2
hi,
while porting the select.c to LCR, i found the problem:
the unix select function returns a set of file descriptors to be
handled. the result-loop (the loop after the select()) is called again,
if more than one descriptor is removed by the callback funtion. this may
lead to a another call to the callback function, because the bits of the
FD_SETs do not change and still set.
i think we must clear these bits, if they are handled, so the handler
will not be called twice in case of a "restart" of that loop.
regards,
andreas
Hello Andreas,
On Wed, 20 Jan 2010 09:30:17 +0100, "Andreas.Eversberg" <Andreas.Eversberg(a)versatel.de> wrote:
>
> some stupid question: if a phone does not support any encryption, is it
> possible to use it on an official GSM network? (authentication works, of
> course) if so, what phone might it be?
I did a quick check, at least Vodafone and T-Mobile here in Germany
reject the Location Update Request with "Network Failure" (0x11) if
they get a classmark without any encryption available. The registration
works with the same phone if the classmark indicates that encryption
support is available. The test was done with a phone where I can
modify the classmark data.
Best regards,
Dieter
--
Dieter Spaar, Germany spaar(a)mirider.augusta.de
hi,
some stupid question: if a phone does not support any encryption, is it possible to use it on an official GSM network? (authentication works, of course) if so, what phone might it be?
regards
andreas
Mit freundlichen Grüßen,
.-.
/'v'\
(/ \)
------------------------------------------------------------------"-"-
|_|
i.A. Andreas Eversberg
Network Operations / 2nd Level Data - KC Internet
Versatel Nord GmbH
Nordstr. 2
D-24937 Flensburg
Fon: +49-461-9099749 | Fax: +49-461-909960749
andreas.eversberg@versatel.de@versatel.de | www.versatel.de
Sitz der Gesellschaft: Flensburg, Registergericht: Flensburg, HRB 3395 FL
Geschäftsführer: Dr. Hai Cheng, Dr. Max Padberg, Joachim Bellinghoven
Hello list,
I have a nanobts1800 and installed openbsc on Debian yesterday (from git).
After building the project and configured the bts on the network, I executed
bsc_hack with -c openbsc.cfg.nanobts.
But it failed to execute with the following error:
<0005> bsc_init.c:860 Failed to parse the config file: 'openbsc.cfg.nanobts'
I haven't modified the config file, I haven't modified anything at all in
openbsc.
Any idea?
Thanks.
Hello,
the commit "[OML] parse attributes depending on BTS type" seems to break
bsc_hack completely since it's no longer possible to add a new BTS.
This happens because the VTY config sytem first tries to allocate a BTS
of type UNKNOWN and later changes that type when the type statement is
encountered. I have commited a patch in daniel/fixes that registers a
BTS of type unknown so the code should work as before (tested with a BS11).
Maybe it is smarter to change the way the gsm_bts_alloc function works
instead (so you don't need to provide a type there), I'm not sure about
that.
Regards,
Daniel Willmann