September 2012 - OpenBSC - lists.osmocom.org

Re: Any interest for Osmocom meetings in Bavaria ?

by Dieter Spaar

So far three persons have indicated their interest to join a meeting at my place. Considering the time it takes to drive to my place, it probably makes sense to have the meeting at the weekend (either Saturday or Sunday) so that there is more time for the meeting itself. I can suggest one of the following dates for the first meeting, somewhere between 10:00 to 18:00 on each day: 25.8. (Sa) or 26.8. (Su) 1.9. (Sa) or 2.9. (Su) 8.9. (Sa) or 9.9. (Su) So please let me know when you have time and also make suggestions in which Osmocom topic you are interested in so that we can have some sort of agenda for the meeting to make best use of the time. Best regards, Dieter -- Dieter Spaar, Germany spaar(a)mirider.augusta.de

10 years, 10 months

10
40
0 0

SimpleHLR: A web interface for OpenBSC

by Peter Caprioli

Hello everyone, I've just finnished writing together a small web interface for the OpenBSC HLR. It allows you to modify various parameters in the database and also provides a set of functions to modify the HLR or sending SMSes in your own scripts. The project is still very alpha but it seems to work reasonably good. Feel free to give any feedback! Screenshots and source code is available on my website: https://stormhub.org/simplehlr/ -- *Best regards, Peter Caprioli*

10 years, 10 months

3
6
0 0

Several questions

by jason mercury

I have some questions: 1) When I start bsc_hack bsc_init.c first establishes OML link and initializes the bts then it establishes RSL link and bts starts broadcasting. However, it takes so much time to start the bts. Instead of this I want to do the following: it establishes OML link at the beginning and only once, then when i want to start broadcasting it establishes just the RSL link and bts will start faster since i don't have to wait for OML link. What should be done for this? 2) If i send one or two word messages from telnet interface it is okay. But if i send a longer message the phone could't receive the end of the message correctly(last words may be incomplete). Did any one encounter with this problem? What is wrong with me? 3) Could I send SMS in which extension of the sender is text not integer. For example, i want to send an information SMS that this is a test network. For this purpose i want to send an SMS from 'OpenBSC'. I set the extension of the first subscriber in database as text and tried to send the SMS but SMS wasn't delivered. What should i do? 4) Can i add SMS externally to SMS table of database? Thanks. Jason

11 years, 4 months

4
3
0 0

Bounce action notification

by mailman＠lists.osmocom.org

This is a Mailman mailing list bounce action notice: List: OpenBSC Member: jledet07(a)student.aau.dk Action: Subscription disabled. Reason: Excessive or fatal bounces. The triggering bounce notice is attached below. Questions? Contact the Mailman site administrator at mailman(a)lists.osmocom.org.

11 years, 6 months

1
0
0 0

BS-11 to sell

by Harald Welte

Hi! In case anyone on this list is interested in owning a BS-11, I have decided to sell off one more of the units that I still had here for my personal use. I'm also able to sell a compatible HFC-E1 or DAHDI/Digium card along with it. Price is up to negotiation. I don't intend to give it away for free, unless it is somebody with a known track record of osmocom.org contributions. 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)

11 years, 6 months

1
0
0 0

Help needed with CSD/V.110 decoding

by Tobias Engel

Hi, I have been trying to implement some basic CSD functionality into openbsc. V.110 transparent mode, to be specific, since this should be the most simple to implement. At first I tried with a nanobts, but that didn't seem to work at all. Now I am using a bs-11. The two phones I use establish a connection, but they cannot exchange data and what I see on the Abis link also doesn't really make sense to me. (Needless to say everything works as expected when using the same phones on a production network.) I attached a pcap of a CSD call I made via the bs-11. The second attachment is the raw dump of the traffic frames I received from the BS-11 for _one_ of the phones. (It looks pretty much the same for the other phone.) The first idle data frames received look ok: 00000000 00 00 c5 ff ff ff ff ff fd ff ff ff ff ff ff ff 00000010 ff fd ff ff ff ff ff ff ff ff fd ff ff ff ff ff 00000020 ff ff ff fd ff ff ff ff C bits (Uplink data), D bits (all set to "1" == idle) and E bits (9.6 kbit/s) are all set as expected. But after the synchronisation phase, things start to get strange. The idle frames suddenly look like this: 00000460 00 00 8a ff ff fe fe fe fa fe fe fe fe fe fe fe 00000470 fe fa ff fe fe fe fe fe fe fe fa ff fe fe fe fe 00000480 fe fe fe fa ff fe fe fe The BTS "forgets" to set the first bit of every octet to "1" on most (but not all) octets. Also, the C bits now state that this is a 14.5kbit/s data frame. The E bits say the user rate now is 7.2 kbit/s. There are only four frames with actual payload data in the dump. These frames are at the positions I expect them to be (40600, 60520, 80440, 100400 - they were sent in intervals of 10 seconds). They look like this: 00009e90 00 00 8a ff 2b a2 fa aa 00009ea0 fa 86 02 22 22 6e fe 1a 26 fa d7 4e d6 52 36 56 00009eb0 4e d6 fa 53 36 56 4e d6 52 36 56 fa 4f d6 52 36 What has been sent by the phone is an eight byte timestamp followed by 22 bytes of 0xaa. But I only get one data frame for each of these transmissions (30 bytes of payload don't fit into one data frame), and if I parse it as V.110 data, I get these 20 bytes: 00000000 15 7d 0d 10 d5 ff 33 fb ae f5 ff ae ba ef fd ba 00000010 ef ae ba ff So no 0xaa bytes there... Does anybody have any idea what I might be doing wrong here? Thanks, -Tobias

11 years, 6 months

2
2
0 0

OpenBSC unsubscribe notification

by mailman-bounces＠lists.osmocom.org

akwonghk(a)gmail.com has been removed from OpenBSC.

11 years, 6 months

1
0
0 0

Re: OpenBSC Digest, Vol 45, Issue 15

by TAUFIQ WAHYUDI

@peter i have already installed libosmocore,libosmo-aabis,and openBsc,and have been clone and integrated all the items into eclipse via egit. i am a newbie in telco, does anyone in this forum know how to start up openBSC ? i do want to know how does the Box work, and really confuse how to start from.Would you guys send me a technical startup document globally, so then i have an understanding regarding this stuff Best Regards On 9/24/12, openbsc-request(a)lists.osmocom.org <openbsc-request(a)lists.osmocom.org> wrote: > Send OpenBSC mailing list submissions to > openbsc(a)lists.osmocom.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.osmocom.org/mailman/listinfo/openbsc > or, via email, send a message with subject or body 'help' to > openbsc-request(a)lists.osmocom.org > > You can reach the person managing the list at > openbsc-owner(a)lists.osmocom.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of OpenBSC digest..." > > > Today's Topics: > > 1. new comer (TAUFIQ WAHYUDI) > 2. Re: new comer (Peter Stuge) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 23 Sep 2012 21:36:30 -0700 > From: TAUFIQ WAHYUDI <taufiq.wahyudi.12(a)gmail.com> > To: openbsc(a)lists.osmocom.org > Subject: new comer > Message-ID: > <CACxKs184Ma=PeW5sPi=HWWJm6xb+sqywmHBEgMs+XKKqiXEy+g(a)mail.gmail.com> > Content-Type: text/plain; charset="iso-8859-1" > > hi all, > > i am new comer in this group, i already have installed openbsc until to > this step, i have problems would you mind all giving me a hand in the > future? > > thank you very much > > Best Regards >

11 years, 6 months

1
1
0 0

GPRS and PDP Context

by John Otten

Good Day, I have been working with OpenBSC for the past few weeks and I am able to make voice calls and send SMS messages within the private network without issues. I am now attempting to add GPRS to the mix, and have been having less success. I have been able to make it to the internet from my phones occasionally, but in general, there appears to be an issue between osmo-sgsn and OpenGSN. My hope is that it is a simple configuration issue. However, I suspect it may be due to an issue in the code, or perhaps something mentioned last May (I have been scouring the mail archive) regarding foreign vs local TLLIs. My current setup is: One Linux workstation which runs all three pertinent executables: osmo-nitb, osmo-sgsn and ggsn. A nanoBTS 165BU (PCS1900) Two Nokia 6013b phones I am working in an RF chamber. I have some T-Mobile SIMs so, I have the network set to T-Mobile rather than the test network. I had previously been able to connect to the internet perhaps 1 in 10 times, presumably because the PDP contexts were not being created (the ggsn output would not state that it was creating a context when I tried to connect from the phone). I modified gprs_llc.c to handle the issue that Frank Maas mentioned in May, regarding llme_alloc not localizing the TLLI. Now, I can usually connect with a phone more consistently (but not always) on a fresh restart of the three executables. However, after connecting to the internet via the phone, if I cycle the power on the phone, I am usually not able to connect to the internet again. Sometimes the ggsn states that it "Received create PDP context request," and sometimes it doesn't state it when the sgsn (apparently) makes a request. At times, the ggsn reports "Received packet with no destination!!!" During these times, when I check the PDP contexts in osmo-sgsn, I get: OsmoSGSN> show pdp-context all PDP Context IMSI: 310260XXXXXXXXX, SAPI: 3, NSAPI: 5 APN: epc.tmobile.com PDP Address: IPv4 192.168.100.3 SGSN PDP Context Statistics: User Data Messages ( In): 0 (0/s 0/m 0/h 0/d) User Data Messages (Out): 0 (0/s 0/m 0/h 0/d) User Data Bytes ( In): 0 (0/s 0/m 0/h 0/d) User Data Bytes (Out): 0 (0/s 0/m 0/h 0/d) The times when the ggsn does not state that it received a create PDP context request, the "show pdp-context all" command shows nothing. My newbie guess is that osmo-sgsn is saving the state of the phone's connection (based on the IMSI?), and is not releasing or clearing it when the phone is powered off. When the phone is powered back on, it will have different connection parameters, but it will use the original parameters after retrieving them based on the IMSI. I have started to look through the code in the src/gprs directory to see if this is the case. I am wondering if anyone might have some insight into why the connection is not fully restored. Or perhaps they can offer guidance where I might begin to look in the code. I can send logs and pcap files of a typical session if anyone is interested. Thanks! John

11 years, 6 months

8
20
0 0

new comer

by TAUFIQ WAHYUDI

hi all, i am new comer in this group, i already have installed openbsc until to this step, i have problems would you mind all giving me a hand in the future? thank you very much Best Regards

11 years, 6 months

2
1
0 0

[PATCH] fix segfault during show running-config

by Max

--- src/vty/logging_vty.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/vty/logging_vty.c b/src/vty/logging_vty.c index 6166f1f..71d926d 100644 --- a/src/vty/logging_vty.c +++ b/src/vty/logging_vty.c @@ -547,7 +547,7 @@ static int config_write_log_single(struct vty *vty, struct log_target *tgt) for (i = 0; i < osmo_log_info->num_cat; i++) { const struct log_category *cat = &tgt->categories[i]; char cat_lower[32]; - + if (!osmo_log_info->cat[i].name) continue; /* stupid old osmo logging API uses uppercase strings... */ osmo_str2lower(cat_lower, osmo_log_info->cat[i].name+1); osmo_str2lower(level_lower, log_level_str(cat->loglevel)); -- 1.7.9.5 --------------080000000307010502010601--

11 years, 7 months

1
0
0 0

[PATCH] logging.c: log_parse_category_mask(), skip log category name right away if name is NULL to prevent passing a NULL ptr to strlen

by Nico Golde

--- src/logging.c | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/src/logging.c b/src/logging.c index 0816570..f368bea 100644 --- a/src/logging.c +++ b/src/logging.c @@ -167,6 +167,7 @@ void log_parse_category_mask(struct log_target* target, const char *_mask) int i = 0; char *mask = strdup(_mask); char *category_token = NULL; + size_t length, cat_length; /* Disable everything to enable it afterwards */ for (i = 0; i < osmo_log_info->num_cat; ++i) @@ -176,16 +177,17 @@ void log_parse_category_mask(struct log_target* target, const char *_mask) do { for (i = 0; i < osmo_log_info->num_cat; ++i) { char* colon = strstr(category_token, ","); - int length = strlen(category_token); - int cat_length = strlen(osmo_log_info->cat[i].name); + + if (!osmo_log_info->cat[i].name) + continue; + + length = strlen(category_token); + cat_length = strlen(osmo_log_info->cat[i].name); /* Use longest length not to match subocurrences. */ if (cat_length > length) length = cat_length; - if (!osmo_log_info->cat[i].name) - continue; - if (colon) length = colon - category_token; -- 1.7.10.4 --sdtB3X0nJg68CQEu--

11 years, 7 months

1
0
0 0

Enabling keep-alive for sockets in libosmo-abis

by Holger Hans Peter Freyther

Dear Pablo, Daniel was adding keepalive support to the socket used to talk to the bts. This was done in commit 8c2591d95e17eb6fa868e4d886a63ac62f3ca8af of OpenBSC and somehow needs to find its way to master of OpenBSC or libosmo-abis. I think it belongs into libosmo-abis but I am not sure where exactly. Is the keepalive setting something that belongs into the e1inp_line and configuration? Do you have an idea where I should add it? thanks holger

11 years, 7 months

2
1
0 0

Sept 19, 8pm / Osmocom Berlin User Group meeting

by Harald Welte

Hi all! This is the announcement for the next Osmocom Berlin meeting. Sept 19, 8pm @ CCC Berlin, Marienstr. 11, 10113 Berlin There is no formal presentation scheduled for this meeting. If you are interested to show up, feel free to do so. There is no registration required. The meeting is free as in "free beer", despite no actual free beer being around. 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)

11 years, 7 months

2
1
0 0

ask protocol gsm

by anak galer

Hi I want asking about protocol GSM header like this. ex : /* A-bis Interface Management Messages */ NM_MT_ESTABLISH_TEI = 0x21, where it came from 0x21, explain please. anyone have more reference Thank You

11 years, 7 months

2
1
0 0

nanoBTS 165B

by Adolfo Cugat

I´m selling a ip.access nanoBTS 165B 1900Mhz EDGE BTS, this one is right now fully functional with openBSC. More info about it, email me out of the list. Adolfo.

11 years, 7 months

1
0
0 0

Buying a NanoBTS 165

by Patrick Klapper

Hello, I am interested in buying a NanoBTS 165AU for research and education. Does anyone sell a NanoBTS 165 with GSM (A5/1, A5/2) and GPRS/EDGE support? Regards Patrick

11 years, 7 months

2
1
0 0

Problem integrating OpenBSC (osmo-nitb) with LCR

by David Perez

Hi! First of all, let me thank you all the developers and contributors of both OpenBSC and LCR. Congratulations for your amazing work! I am stuck with a problem while trying to get LCR and openbsc to work together through their unix socket (/tmp/bsc_mncc), and I was wondering if anyone on this list would be kind enough to give me some pointers. I include more details below, but this is the executive summary: I have two MS that can call each other with no problem when I start openbsc (osmo-nitb) in standalone mode (i.e. without the "--mncc-sock" option). However, when I start omso-nitb with that option, and I also start LCR, a call between the two MS cannot be establised. I think the problem may be related with the fact that LCR is not being able to identify the calling number, nor the called number, nor the IMSI of the caller. This can be seen in the following trace/debug messages of LCR: --- 000000 TRACE 13.09.12 18:17:49.248 CH(1): MNCC_SETUP_IND LCR<->BSC calling imsi= dialing number= [...] 000000 DEBUG (in apppbx.cpp/ea_message_port() line 2476): EPOINT(1) incoming call from callerid=imsi-, dialing= --- AFAIK, I'm using the latest version of each tool: I am using clones of the following git repositories, made around 10:00 AM CET today (13sep12): --- git clone git://git.osmocom.org/libosmocore.git git clone git://git.osmocom.org/libosmo-abis.git git clone git://git.osmocom.org/openbsc.git git clone git://git.misdn.eu/lcr.git/ --- At the end of this message I include a list of the last commits of these repositories, for reference. --- Executive summary ends here --- The long version of the explanation of the problem follows. I hope to have included enough information, but if you need extra details, please do not hesitate to let me know. First, without LCR, I start openbsc (osmo-nitb) in standalone mode, make a call from 2203 to 2201 (extension numbers I assigned in hlr.sqlite3), and everything works fine (the call gets established and voice flows in both directions): --- root@tli-pc-2001:/usr/local/bin# cat start-bsc-standalone #!/bin/sh echo "" echo "Starting _new_ BSC (openbsc) (=osmo-nitb) standalone..." /opt/new/openbsc/bin/osmo-nitb -c /etc/opt/new/openbsc/openbsc.cfg \ -l /var/opt/new/openbsc/hlr.sqlite3 root@tli-pc-2001:/usr/local/bin# start-bsc-standalone Starting _new_ BSC (openbsc) (=osmo-nitb) standalone... <0019> input/ipaccess.c:923 enabling ipaccess BSC mode DB: Database initialized. DB: Database prepared. <0007> sms_queue.c:232 Attempting to send 20 SMS <0019> input/ipa.c:322 accept()ed new link from 10.10.10.21 to port 3002 Failure Event Report Type=communication failure Severity=critical failure Probable cause= 03 03 11 Additional Text= <0019> input/ipa.c:322 accept()ed new link from 10.10.10.21 to port 3003 <0004> bsc_init.c:282 bootstrapping RSL for BTS/TRX (0/0) on ARFCN 1 using MCC=001 MNC=01 LAC=2 CID=0 BSIC=63 TSC=7 <000b> bsc_api.c:374 Sending ChanModify for speech 33 1 <000b> osmo_msc.c:73 Assignment complete should not have been reached. <000b> bsc_api.c:374 Sending ChanModify for speech 33 1 <000b> osmo_msc.c:73 Assignment complete should not have been reached. --- Then, I shut down osmo_nitb with CTRL-C. Then, I start osmo-nitb for use with LCR (--mncc-sock): --- root@tli-pc-2001:/usr/local/bin# cat start-bsc-for_lcr #!/bin/sh echo "" echo "Starting _new_ BSC (openbsc) (=osmo-nitb) for use with LCR..." /opt/new/openbsc/bin/osmo-nitb -c /etc/opt/new/openbsc/openbsc.cfg \ -l /var/opt/new/openbsc/hlr.sqlite3 \ --mncc-sock --rtp-proxy root@tli-pc-2001:/usr/local/bin# start-bsc-for_lcr Starting _new_ BSC (openbsc) (=osmo-nitb) for use with LCR... <0019> input/ipaccess.c:923 enabling ipaccess BSC mode DB: Database initialized. DB: Database prepared. <0007> sms_queue.c:232 Attempting to send 20 SMS <0019> input/ipa.c:322 accept()ed new link from 10.10.10.21 to port 3002 <0019> input/ipa.c:322 accept()ed new link from 10.10.10.21 to port 3003 <0004> bsc_init.c:282 bootstrapping RSL for BTS/TRX (0/0) on ARFCN 1 using MCC=001 MNC=01 LAC=2 CID=0 BSIC=63 TSC=7 Failure Event Report Type=communication failure Severity=critical failure Probable cause= 03 03 11 Additional Text= --- Then, I start LCR: --- root@tli-pc-2001:/usr/local/bin# cat start-lcr #!/bin/sh echo "" echo "Starting _new_ LCR..." /opt/new/lcr/sbin/lcr start root@tli-pc-2001:/usr/local/bin# root@tli-pc-2001:/usr/local/bin# start-lcr Starting _new_ LCR... ** LCR Version 1.12 000000 DEBUG (in route.c/getrulesetbyname() line 1871): ruleset main found. 000000 DEBUG (in sip.cpp/sip_init() line 1913): SIP globals initialized 000000 DEBUG (in gsm.cpp/mncc_socket_retry_cb() line 1173): Connected to MNCC socket /tmp/bsc_mncc! LCR 1.12 started, waiting for calls... 000000 TRACE 13.09.12 18:16:22.091 --: LCR 1.12 started, waiting for calls... --- It attaches OK to the MNCC socket of openbsc. This message is displayed by openbsc: --- <0006> mncc_sock.c:274 MNCC Socket has connection with external call control application --- Then, I attempt to establish the same call as before, from 2203 to 2201. The call does not get established, and LCR shows the following messages: --- 000000 DEBUG (in port.cpp/Port() line 197): new port (1) of type 0x3101, name 'GSM-0-in' 000000 DEBUG (in gsm.cpp/Pgsm() line 194): Created new GSMPort(GSM-0-in). 000000 DEBUG (in gsm_bs.cpp/Pgsm_bs() line 56): Created new GSMBSPort(GSM-0-in). 000000 TRACE 13.09.12 18:17:49.248 CH(1): New call ref LCR<->BSC callref new=0x80000001 000000 TRACE 13.09.12 18:17:49.248 CH(1): Codec negotiation LCR<->BSC bearer capa='given by MS' speech version='AMR given' ignored='Not suitable for LCR' version='EFR given' ignored='Not suitable for LCR' version='Full Rate given' version='AMR Half Rate given' ignored='Not suitable for LCR' version='Half Rate given' ignored='Not suitable for LCR' 000000 TRACE 13.09.12 18:17:49.248 CH(1): MNCC_SETUP_IND LCR<->BSC calling imsi= dialing number= 000000 DEBUG (in endpoint.cpp/Endpoint() line 48): EPOINT(1): Allocating enpoint 1 and connecting it with: ioport 000000 DEBUG (in endpoint.cpp/portlist_new() line 150): EPOINT(1) allocating port_list, attaching to port 1 000000 DEBUG (in port.cpp/epointlist_new() line 128): PORT(1) allocating epoint_list. 000000 TRACE 13.09.12 18:17:49.249 CH(1): MNCC_LCHAN_MODIFY LCR<->BSC speech version='Full/Half Rate given' mode 0x01 000000 TRACE 13.09.12 18:17:49.249 CH(1): MNCC_CALL_PROC_REQ LCR<->BSC progress coding=3 location=1 descr=8 000000 DEBUG (in port.cpp/new_state() line 261): PORT(GSM-0-in) new state PORT_STATE_IDLE --> PORT_STATE_IN_PROCEEDING 000000 TRACE 13.09.12 18:17:49.249 CH(1): unknown LCR<->BSC 000000 DEBUG (in message.c/_message_put() line 61): message MESSAGE_SETUP written from 1 to 1 (memory 8bfaf48 at file gsm_bs.cpp, line 576) 000000 DEBUG (in message.c/message_get() line 106): message MESSAGE_SETUP reading from 1 to 1 (memory 8bfaf48) 000000 DEBUG (in apppbx.cpp/ea_message_port() line 2476): EPOINT(1) incoming call from callerid=imsi-, dialing= 000000 TRACE 13.09.12 18:17:49.249 EP(1): SETUP from CH(1) caller id number=imsi- present='not available' complete true 000000 DEBUG (in apppbx.cpp/port_setup() line 1372): EPOINT(1) incoming call is extension 000000 DEBUG (in apppbx.cpp/port_setup() line 1382): EPOINT(1) call from extension 'imsi-' the given extension doesn't exist: "/opt/new/lcr/var/lib/lcr/extensions/imsi-/settings" 000000 DEBUG (in extension.c/read_extension() line 58): the given extension doesn't exist: "/opt/new/lcr/var/lib/lcr/extensions/imsi-/settings" 000000 TRACE 13.09.12 18:17:49.250 EP(1): EXTENSION (not created) extension imsi- 000000 DEBUG (in message.c/_message_put() line 61): message MESSAGE_DISCONNECT written from 1 to 1 (memory 8bfe800 at file apppbx.cpp, line 4213) 000000 TRACE 13.09.12 18:17:49.250 EP(1): DISCONNECT to CH(1) cause value=21 location=1-Local-PBX 000000 DEBUG (in message.c/_message_put() line 61): message MESSAGE_TONE written from 1 to 1 (memory 8c020b8 at file apppbx.cpp, line 579) 000000 TRACE 13.09.12 18:17:49.250 EP(1): TONE to CH(1) directory default name cause_80 000000 DEBUG (in message.c/message_get() line 106): message MESSAGE_DISCONNECT reading from 1 to 1 (memory 8bfe800) 000000 TRACE 13.09.12 18:17:49.251 CH(1): MNCC_DISC_REQ LCR<->BSC progress coding=3 location=1 descr=8 cause coding=3 location=1 value=21 000000 DEBUG (in port.cpp/new_state() line 261): PORT(GSM-0-in) new state PORT_STATE_IN_PROCEEDING --> PORT_STATE_OUT_DISCONNECT 000000 DEBUG (in message.c/message_get() line 106): message MESSAGE_TONE reading from 1 to 1 (memory 8c020b8) 000000 DEBUG (in port.cpp/message_epoint() line 611): PORT(GSM-0-in) setting tone 'cause_80' dir '' 000000 TRACE 13.09.12 18:17:49.708 CH(1): MNCC_REL_IND LCR<->BSC 000000 DEBUG (in message.c/_message_put() line 61): message MESSAGE_RELEASE written from 1 to 1 (memory 8bf9950 at file gsm.cpp, line 585) 000000 DEBUG (in port.cpp/free_epointlist() line 84): PORT(1) removed epoint from port 000000 DEBUG (in port.cpp/new_state() line 261): PORT(GSM-0-in) new state PORT_STATE_OUT_DISCONNECT --> PORT_STATE_RELEASE 000000 DEBUG (in message.c/message_get() line 106): message MESSAGE_RELEASE reading from 1 to 1 (memory 8bf9950) 000000 DEBUG (in apppbx.cpp/ea_message_port() line 2562): EPOINT(1) release with cause=16 location=0 (terminal '', caller id 'imsi-') 000000 TRACE 13.09.12 18:17:49.709 EP(1): RELEASE from CH(1) cause value=16 location=0-User 000000 DEBUG (in apppbx.cpp/port_disconnect_release() line 2043): EPOINT(1) current multipoint cause 0 location 0, received cause 16 location 0. 000000 DEBUG (in apppbx.cpp/port_disconnect_release() line 2045): EPOINT(1) new multipoint cause 16 location 0. 000000 DEBUG (in action.cpp/process_hangup() line 2428): EPOINT(1): terminal '' 000000 DEBUG (in endpoint.cpp/free_portlist() line 189): EPOINT(1) removed port 1 from port_list of endpoint 000000 DEBUG (in apppbx.cpp/release() line 222): EPOINT(1): do pending release (joincause 16 location 0) 000000 DEBUG (in apppbx.cpp/release() line 240): EPOINT(1) do pending release (portcause 16 portlocation) 000000 DEBUG (in apppbx.cpp/release() line 319): EPOINT(1) do pending release of epoint itself. 000000 DEBUG (in gsm_bs.cpp/~Pgsm_bs() line 64): Destroyed GSM BS process(GSM-0-in). 000000 DEBUG (in gsm.cpp/~Pgsm() line 202): Destroyed GSM process(GSM-0-in). 000000 DEBUG (in port.cpp/~Port() line 209): removing port (1) of type 0x3101, name 'GSM-0-in' 000000 DEBUG (in endpoint.cpp/~Endpoint() line 138): removed endpoint 1. --- Latest commit of each tool: --- root@tli-pc-2001:/home/tliuser1/sw_openbsc_2/libosmocore# git log | head -6 commit eacba189b1a03c6a213b76df07dd766697017438 Author: Holger Hans Peter Freyther <zecke(a)selfish.org> Date: Tue Sep 11 12:27:47 2012 +0200 git: Ignore generated tests executables root@tli-pc-2001:/home/tliuser1/sw_openbsc_2/libosmocore# cd .. root@tli-pc-2001:/home/tliuser1/sw_openbsc_2# cd libosmo-abis/ root@tli-pc-2001:/home/tliuser1/sw_openbsc_2/libosmo-abis# git log | head -6 commit 84e5cb9b3496527d43af974f2f89396d8145d743 Author: Pablo Neira Ayuso <pablo(a)gnumonks.org> Date: Thu Aug 23 23:41:54 2012 +0200 ipaccess: fix leak of IPA control messages in the BTS side root@tli-pc-2001:/home/tliuser1/sw_openbsc_2/libosmo-abis# cd .. root@tli-pc-2001:/home/tliuser1/sw_openbsc_2# cd openbsc root@tli-pc-2001:/home/tliuser1/sw_openbsc_2/openbsc# cd openbsc root@tli-pc-2001:/home/tliuser1/sw_openbsc_2/openbsc/openbsc# git log | head -6 commit ca5d2111131101f7b8df40207b4c597b0e53f2cb Merge: c11889f 31b245b Author: Holger Hans Peter Freyther <zecke(a)selfish.org> Date: Tue Sep 11 18:02:46 2012 +0200 Merge branch 'feature/local-mscs' root@tli-pc-2001:/home/tliuser1/sw_openbsc_2/openbsc/openbsc# cd ../.. root@tli-pc-2001:/home/tliuser1/sw_openbsc_2# cd lcr root@tli-pc-2001:/home/tliuser1/sw_openbsc_2/lcr# git log | head -6 commit 6911e09b77aa1eaac35b595bb4082e1f4c59ca71 Author: Andreas Eversberg <jolly(a)eversberg.eu> Date: Sun Aug 19 20:50:10 2012 +0200 Allow calls to multiple interfaces simultaniosuly root@tli-pc-2001:/home/tliuser1/sw_openbsc_2/lcr# --- Any guidance would be appreciated. Best regards, David. ---- David Perez Founder & Senior Security Analyst Taddong david(a)taddong.com | +34-699982432 | www.taddong.com ---- 13sep12 19:50

11 years, 7 months

1
0
0 0

[PATCH] make example config usable

by ☎

Hello. Attached is a trivial patch which makes example config for libosmo-sgsn actually usable. Most likely it was typo. -- best regards, Max, http://fairwaves.ru

11 years, 7 months

1
0
0 0

[PATCH] Rename example config so it could be used right after copying.

by Max

--- openbsc/doc/examples/osmo-sgsn/osmo-sgsn.cfg | 26 -------------------------- openbsc/doc/examples/osmo-sgsn/osmo_sgsn.cfg | 26 ++++++++++++++++++++++++++ 2 files changed, 26 insertions(+), 26 deletions(-) delete mode 100644 openbsc/doc/examples/osmo-sgsn/osmo-sgsn.cfg create mode 100644 openbsc/doc/examples/osmo-sgsn/osmo_sgsn.cfg diff --git a/openbsc/doc/examples/osmo-sgsn/osmo-sgsn.cfg b/openbsc/doc/examples/osmo-sgsn/osmo-sgsn.cfg deleted file mode 100644 index 027c03d..0000000 --- a/openbsc/doc/examples/osmo-sgsn/osmo-sgsn.cfg +++ /dev/null @@ -1,26 +0,0 @@ -! -! Osmocom SGSN configuration -! -! -line vty - no login -! -sgsn - gtp local-ip 10.23.23.23 - ggsn 0 remote-ip 192.168.0.101 - ggsn 0 gtp-version 1 -! -ns - timer tns-block 3 - timer tns-block-retries 3 - timer tns-reset 3 - timer tns-reset-retries 3 - timer tns-test 30 - timer tns-alive 3 - timer tns-alive-retries 10 - encapsulation udp local-ip 192.168.0.101 - encapsulation udp local-port 23000 - encapsulation framerelay-gre enabled 0 -! -bssgp -! diff --git a/openbsc/doc/examples/osmo-sgsn/osmo_sgsn.cfg b/openbsc/doc/examples/osmo-sgsn/osmo_sgsn.cfg new file mode 100644 index 0000000..027c03d --- /dev/null +++ b/openbsc/doc/examples/osmo-sgsn/osmo_sgsn.cfg @@ -0,0 +1,26 @@ +! +! Osmocom SGSN configuration +! +! +line vty + no login +! +sgsn + gtp local-ip 10.23.23.23 + ggsn 0 remote-ip 192.168.0.101 + ggsn 0 gtp-version 1 +! +ns + timer tns-block 3 + timer tns-block-retries 3 + timer tns-reset 3 + timer tns-reset-retries 3 + timer tns-test 30 + timer tns-alive 3 + timer tns-alive-retries 10 + encapsulation udp local-ip 192.168.0.101 + encapsulation udp local-port 23000 + encapsulation framerelay-gre enabled 0 +! +bssgp +! -- 1.7.9.5 --------------060008010109090003040201--

11 years, 7 months

1
0
0 0

Introducing libosmosim

by Harald Welte

Hi! I've been hacking away a bit on a new library 'libosmosim' whihc is scheduled to become part of libosmocore. In fact, as the automake integration has been cleaned up, I'll probably merge it master any day now. The idea of this library is to * understand the EF/DF hierarchy if GSM SIM, ETSI UICC and 3GPP USIM * provide encoding and decoding routines for at least the most important EFs * decode the binary data into a generic data structure which can be used by some form of a GUI application * be able to re-encode from the generic parsed structure into the binary form, possibly after modification from the UI * be able to transact APDUs via T0 and T1 on PC/SC and other reader interfaces, e.g. the OsmocomBB SIM interface So the primary purpose of this is to be able to have a tool for meaningful (human-readable/writable) modification of all files on a programmable SIM card, such as the sysmoSIM-GR1 (and other cards where you have the ADM PIN that gives you write permission). Other useful purposes on the horizon of the library could be: * implementation of a generic SIM/UICC/USIM simulator based on user-created input, or based on 'ripped' SIM cards (well, you have to provide the key in some way). The current status is still quite experimental, but you can already see the major parts: * mapping of APDU and TPDU (only T=0 so far) on to 'struct msgb struct osim_file_ops encode and decode callbacks for a given file struct osim_file_desc node in the hierarchical description of filesystem tree struct osim_decoded_data the runtime representation of a decoded file: struct osim_decoded_element one decoded element in a decoded file struct osim_card_sw status + bitmask + human readable description struct osim_card_profile full description profile of card, including filesystem hierarchy, status words and card-specific commands struc osim_reader_hdl represents a card reader (currently a slot in a reader, not sure really how to represent multi-slot readers like sim-banks yet). primarily consist of osim_reader_ops struc osim_card_hdl representing a card inside a reader struc osim_chan_hdl currently just a dummy. intended for logical channel support most of the existing code is in src/sim/*.c, while some not-yet-cleaned-up example code is in utils/osmo-sim-test.c. There are gaps everywhere all over the place, and I think it will take quite some time to fill those gaps. Current roadmap: * properly integrate all parts, so with a single call you can read in the tree of all EFs of a card into their in-memory representation * verify that the APIs for encoding/decoding functions work the way they are before writing 'all' the EF decode/encode routines * add more decoded element types, such as location area codes and the like So if you survived this mail until this point, I think you are a prime candidate for contributing some code. Let me know if you're interested in helping out. 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)

11 years, 7 months

2
2
0 0

Tektronix K1103 pinout of the E-1 interface

by Tawanda

Sent on the Go

11 years, 7 months

2
1
0 0

MultiARFCN OpeBSC and SysmoBTS

by Daud Suleiman

Hi Harald, I can't tire of congratulating and the community for the great work you are doing in creating a free world in your own capacity! I thank you. Meanwhile, I would like to know a few things: 1. Is sysmoBTS capable of operating in MultiARFCN? Is multiARFCN implemented in OpenBSC and if so how does one go about configuring it. 2. Also after the successful implementation of CSD, are there plans for PTT over Cellular (PoC)?

11 years, 7 months

3
2
0 0

Sept 5, 8pm / Osmocom Berlin User Group meeting

by Harald Welte

Hi all! This is the announcement for the next Osmocom Berlin meeting. Sept 05, 8pm @ CCC Berlin, Marienstr. 11, 10113 Berlin There is no formal presentation scheduled for this meeting. If you are interested to show up, feel free to do so. There is no registration required. The meeting is free as in "free beer", despite no actual free beer being around. Regards, Harald [p.s.: I myself will not be able to attend tonight, but I'm sure you will be able to do just fine (or even better?)] -- - 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)

11 years, 7 months

1
0
0 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC September 2012