OpenBSC

openbsc@lists.osmocom.org

6 participants
4274 discussions

patch 37: assigning traffic channel
by Andreas.Eversberg 09 Jun '09

09 Jun '09

hi, i have a phone that requests a SDCCH channel after it is paged. (even if paging request required a TCH Full channel.) in this case, i assign a GSM_LCHAN_TCF_F channel except for location update. (see patch) in the second part of this patch, i check if the current channel is a traffic channel. if not, we can't use it on calls BSS->MS. this happens if a call is received after location update, but before the channel is released. this second part depends on the application patch (36). andreas

2 1

patch: 30
by Andreas.Eversberg 09 Jun '09

09 Jun '09

my subsequent patches are dependant on the patches by holger from may 5th. for personal testing and for information, i packed them together. i tested them and they work well. Mit freundlichen Grüßen, .-. /'v'\ (/ \) ------------------------------------------------------------------"-"- |_| i.A. Andreas Eversberg Administrator Betrieb und Entstörung 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: Soeren Wendler, Dr. Hai Cheng, Dr. Max Padberg, Peter Schindler, Joachim Bellinghoven

2 1

patch 32: subscr_update() missing.
by Andreas.Eversberg 09 Jun '09

09 Jun '09

If location update is requested, but subscriber is not yet authorised within mm_rx_loc_upd_req() function, the subscr_update() is not called, because subscriber information is not complete. During mm_rx_id_resp() the subscriber informations is may be complete, so authorize subscriber succeeds and database must be updated.

2 1

Re: Some notes about BS-11 clock calibration
by Dieter Spaar 08 Jun '09

08 Jun '09

Hello Harald, On Mon, 8 Jun 2009 16:28:54 +0800, "Harald Welte" <laforge(a)gnumonks.org> wrote: > > The various clock related issues that people have been describing already gave > me a lot of headache. With the method you described in your mail we now have a > documented way how to make sure the BS-11 runs on the 'right' frequency. Thank you, I hope that together with the description and tool from Andreas it will help to solve any issues related to the BS-11 clock. Best regards, Dieter -- Dieter Spaar, Germany spaar(a)mirider.augusta.de

1 0

AW: isdnsync
by Andreas.Eversberg 08 Jun '09

08 Jun '09

the "g" is missing. maybe i lost the "g" while copying. i prefer OpenBSC svn because the tool is currently usefull for OpenBSC only. -----Ursprüngliche Nachricht----- Von: openbsc-bounces(a)lists.gnumonks.org [mailto:openbsc-bounces@lists.gnumonks.org] Im Auftrag von Holger Freyther Gesendet: Montag, 8. Juni 2009 11:56 An: openbsc(a)lists.gnumonks.org Betreff: Re: isdnsync Cool, two small questions. Do you mind if I add a "g" to your name in the isdnsync.c, or did I always misspell your name? The second one is if the OpenBSC svn is to be preferred over misdn-utils? z.

2 1

Re: Trying to understanding the source
by Nordin 08 Jun '09

08 Jun '09

Hi guys, I'm a bit ashamed to ask, but I'll ask anyway, could someone help me explaining the OpenBSC source? make_sock(): I didn't know it's possible to call select() on a read signal to finally call the accept() for the socket_fd. Logically seen, socket_fd receives something (in this case a new connection), so it works. I just thought select() is only used for reading/writing data (or an except) on file descriptors. Why is OpenBSC written to work synchronously and not multihtreaded? If somewhere in the chain hangs (by a bug), telnet for example won't respond, right? What is the idea behind this concept? Is it a popular concept in the Linux world (so I can be familiar with)? Which other functions does timer.c has besides returning a timevalue for the select() call (nearest_timer) time-out. I mean what more other purposes has timer.c Cause I don't really understand why timer_values also be put in a doubly linked list... That's all for now, I might ask some more questions, but after some studying :s Thank you. P.S: I do have experience in C/C++ programming....in Bill Gates environment. I know.....I'm sorry.

3 3

(no subject)
by Andreas.Eversberg 08 Jun '09

08 Jun '09

hi, this small tool is used to enable layer 1 and 2 on a given isdn card. the card can be used to retrieve clock signal from a network. layer 2 (PTP) is required to keep layer 1 without interruption. this tool works on e1 and s0 cards. to use the clock signal with other cards, interconnection with a clock-slave-card is required. this tool is GPL v2. the import to the subversion server on bs11-abis.gnumonks.org is welcome. a documentation with card interconnection howto does not exist, but if someone really successfully connects two cards (HFC-S PCI and HFC-E1), we can write one from these experiences. regards, andreas

2 1

Some notes about BS-11 clock calibration
by Dieter Spaar 08 Jun '09

08 Jun '09

Hello, I did a few tests with the BS-11 clock. I wanted to find out how accurate the clock of the BS-11 is and how the calibration value influences the clock. This is only about one BS-11, but I guess the others are similar. To control the BS-11 clock I used a slightly modified HFC-E1 card, instead of the 32.768 MHz oscillator of the card an external signal from an accurate and stable clock source is used. The BS-11 "PLL Mode" is set to "Locked" so that it locks to the E1 clock. I am observing the PLL "Work Value" which is the actual value used by the PLL. I also measured the RF frequency of the BS-11. HFC-E1 clock is 32.768 MHz: PLL Work Value is 1024 HFC-E1 clock is 32.768 MHz + 0.1 ppm: PLL Work Value is 941 HFC-E1 clock is 32.768 MHz - 0.1 ppm: PLL Work Value is 1116 So a lower PLL calibration value means a higher frequency. Another observation is that the actual RF frequency is following the E1 clock slowly. For example if the E1 clock is changed by 0.1 ppm, the RF frequency is slowly changing until after several minutes it has also changed by 0.1 ppm. The PLL "Working Value" is following even slower, it takes nearly an hour until is has settled to a stable value. The clock of the BS-11 is very stable, if set to "Stand Alone" the RF frequency is not changing very much, its much less than the required 0.05 ppm from the GSM specification for a BTS. Another interesting thing is that the factory PLL calibration of this BS-11 is 1016, very close to 1024 of the measured value. What does that all mean ? If you want to calibrate the clock of your BS-11 by using a HFC-E1 card which is synchronized from a stable and accurate clock (Andreas explained how this can be done with a second ISDN card) I would recommend to do the following: - let the BS-11 warm up for at least one hour - set the "PLL Mode" to "Locked" with bs11_config - start bsc_hack and let it run for an hour so that the PLL can adjust to the E1 clock and the PLL "Work Value" settles (you can use bs11_config to watch the value). - set the "PLL Mode" to "Stand Alone" with bs11_config, this makes sure that the PLL "Work Value" will no longer change and is used next time, even if the HFC-E1 clock is no longer synchronized. The BS-11 oscillator should be stable enough so that there is no need for continuous synchronisation with an external reference. Best regards, Dieter -- Dieter Spaar, Germany spaar(a)mirider.augusta.de

2 1

[PATCH 0/3] Updated Channel Allocation Code
by Holger Freyther 06 Jun '09

06 Jun '09

Hey, I posted some of these patches some time ago and started to rebase them now. The main idea is to make the "paging" layer more internal and only request to open a channel (of a specific type) to a certain subscriber. The internal handling would find the right bts in the lac ("new" requirement and not yet implemented), will make sure that we assign as many as possible channels to the subscriber but will not lose any request (act as a queue). I would like to merge the first two patches as I think they are moving in the right direction and are unlikely to break anything and plan to test the third patch later this week (if I get access to a BTS). So if you will see a regression in call handling, shout at me.. z. include/openbsc/gsm_data.h | 2 include/openbsc/gsm_subscriber.h | 9 ++ src/bsc_hack.c | 1 src/gsm_04_08.c | 6 - src/gsm_subscriber.c | 139 ++++++++++++++++++++++++++++++++++++++- 5 files changed, 153 insertions(+), 4 deletions(-)

1 3

Re: WG: patch 12 14, 15, 16
by Dieter Spaar 06 Jun '09

06 Jun '09

Hello Harald, On Sat, 6 Jun 2009 10:03:38 +0200, "Harald Welte" <laforge(a)gnumonks.org> wrote: > > In other words: IMSI ATTACH/DETACH is only used in addition to regular Location > Update, and it is used in situations where a MS on a network with ATT=0 would > not perform any signalling with the network at all. I have read at some places that the idea of IMSI ATTACH/DETACH is to save resources of the network, if its is know that an MS is off (IMSI DETACH was sent) there is no need to allocate resources for paging the MS. IMSI ATTACH is the reverse, it tells the network that the phone is back again. Its up to the operator to use this feature. I am not sure if this is the real motivation, but it makes sense for me. Best regards, Dieter -- Dieter Spaar, Germany spaar(a)mirider.augusta.de

2 1

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC