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(-)
Hey,
I think in the next days I will go around the sourcecode and change a couple
of logging messages. My two primary goals are increase the usefulness to figure
out what was going wrong and the second to be able to put some of these into
the syslog. Should we use DEBUG* to also log to syslog or introduce a new set
of macros?
Log Levels:
I think Harald has expressed the wish to introduce log levels. Should we
follow the log levels of syslog(3)?
Messages:
I would like to collect formats for various actions. Currently I'm thinking of
the following but would like to have more input.
subscriber:
When talking about a subscriber use TMSI, IMSI and Extension.
lchan:
Include refcount, channel type, link_id, subscriber
sccp:
Talk about SCCP source local reference and pointer
transaction:
Print the transaction?
gsm0408:
Print the lchan which prints the subscriber?
comments?
holger
From: Steffen Neubauer <stefreak(a)stefreak.de>
- Added function "gsm340_scts" to decode the service center time stamp
into a UTC/GMT timestamp
- in function gsm340_validity_period: can now decode validity period
format absolute.
I hope it's good ;)
Greetings,
Steffen
Hi all!
I've pushed the current state of GPRS support into the 'gprs' branch. All the
'core' changes related to GPRS are already in master, so it mainly really adds
the GPRS protocols (gprs_{ns,bssgp,llc}.[ch]) as well as the handling of the
most importnat 04.08 GMM messages (gsm_04_08_gprs.[ch]) as well as the state
management for the SGSN MM context (gprs_sgsn.[ch]).
The status of the code is as follows:
* NS link and BSSGP link are established between OpenBSC and the nanoBTS
* LLC frames from the MS get delivered to the OpenBSC LLC code
* GMM messages sent over LLC are delivered to the GMM code
* The GMM code tries to respond with useful answers, permitting
GPRS attach as well as routing area update
What's missing:
* any kind of GGSN functionality, i.e. gatewaying to PPP daemon for actual
user payloads
* persistant storage of SGSN MM context information, especially the
attach/detach status, routing area and P-TMSI of a subscriber
* PDP context activation/deactivation
* flow control for the BTS as well as for each MS (BSSGP level)
* retransmissions and things like acknowledged mode of LLC
* support for multiple BTS
There's really only one extremely ugly hack in the code right now,
and that is that the IP address of the BTS is hard-coded in the
ipac_gprs_send() function. You will have to enter the IP address
of your BTS there to make packets in the SGSN->BTS direction delivered.
Apart from that, I think the code is at a state where other interested
developers can start playing with it. I am leaving to Korea on a customer
assingment tomorrow and will unlikely have time to work on any GPRS code
throughout the next two weeks.
To get the code going, you should do the following things:
* chceck out the gprs branch
* hard-code your ip address into ipac_gprs_send() as indicated above
* change your openbsc.cfg to use the last timeslot (TS 7) as "TCH/F_PDCH"
instead of just "TCH/F"
Patches / Bug reports / ... welcome
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)
hi harald,
> sorry for not getting back earlier. I honestly did not realize that
there
> was a second attachment to your mail. We typically use inline
patches, and one
> patch per mail on this list. Once again, sorry for the delay.
next time i will send the patches inline...
> I'm now looking at the code in detail, I shall be getting back to you
at some
> point during the next days.
in order to remove md5 code, you can use a simple XOR to mix the input
data.
i think it is good enough to not select the same random number as the
base station.
regards,
andreas
hi there,
i found the problem with the delayed audio between application and the
nanoBTS. the reason was the timestamp. a delay in openbsc causes packets
to be delayed 1/2 seconds, so many packet of 1/2 seconds arrived at
nanoBTS after the delay at once, nanoBTS buffers them.
the reason for the delay was the "usleep(100000)" hack inside
input/ipaccess.c. the patch will use the tx_timer instead, so openbsc
and application will not stall. this timer was already used with BS11
messages. (there it uses 50 miliseconds instead of 100 miliseconds.)
sending 10 messages to nanoBTS will take almost one second. can we
decrease the tx_timer value for nanoBTS? how many packets can handle
nanoBTS per second?
also i fixed some bugs in the rtp patch. use rtp_2.patch for
commission/discussion instead.
regards,
andreas
> Currently the branch is doing:
> - Stops borrowing the gsm_subscriber to the lchan
> - Fixes leaks in the vty_interface_layer3.c code for subscriber
action
> - Fixes a subscriber leak (actually two) in mncc_send.
>
> if wanted I can attach the patches to this mail to ease reviewing.
what branch is it? do i need additional patches? i use the master with
the RTP patch applied.