- OpenBSC - lists.osmocom.org

how to know GPRS channel coding
by John Wu 27 Oct '11

27 Oct '11

Hi all, I want to know how to know GPRS channel coding. GPRS using PDCH, both MAC/RLC data block and MAC/RLC control block is transmitted on PDCH, although there is PACCH, PTCH, PTCCH and so on it still PDCH. then the MAC/RLC control block is coded with cs-1 channel coding scheme and MAC/RLC data block may be coded with other channel coding scheme. so when received a burst how to know what kind of MAC/RLC block it belong to and which channel coding scheme it used? Thanks!

2 1

Way to invoke multiple imsi msisdn in sgnsemu
by anish achenkunju 21 Oct '11

21 Oct '11

Hi All, Wondering if there is a way to create pdp request for multple imsi or msisdn. Currently there is an option to emulate more than one pdp context, can we do the same for different imsi's or msisdn via sgsnemu as an input to sgsnemu.conf file? Thank you in advance. Anish

2 2

[PATCH] mncc: Introduce a hello packet that is sent to the client.
by Holger Hans Peter Freyther 21 Oct '11

21 Oct '11

Send a hello packet down to the client with the version number of the MNCC interface. The hello structure might be extended to include the endianes, size of each structure, etc. --- openbsc/include/openbsc/mncc.h | 8 ++++++++ openbsc/src/libmsc/mncc_sock.c | 24 ++++++++++++++++++++++++ 2 files changed, 32 insertions(+), 0 deletions(-) diff --git a/openbsc/include/openbsc/mncc.h b/openbsc/include/openbsc/mncc.h index 8c59fe2..9153d65 100644 --- a/openbsc/include/openbsc/mncc.h +++ b/openbsc/include/openbsc/mncc.h @@ -96,6 +96,8 @@ struct gsm_call { #define GSM_TCHF_FRAME 0x0300 #define GSM_TCHF_FRAME_EFR 0x0301 +#define MNCC_SOCKET_HELLO 0x0400 + #define GSM_MAX_FACILITY 128 #define GSM_MAX_SSVERSION 128 #define GSM_MAX_USERUSER 128 @@ -158,6 +160,12 @@ struct gsm_data_frame { unsigned char data[0]; }; +#define MNCC_SOCK_VERSION 1 +struct gsm_mncc_hello { + uint32_t msg_type; + uint32_t version; +}; + char *get_mncc_name(int value); void mncc_set_cause(struct gsm_mncc *data, int loc, int val); void cc_tx_to_mncc(struct gsm_network *net, struct msgb *msg); diff --git a/openbsc/src/libmsc/mncc_sock.c b/openbsc/src/libmsc/mncc_sock.c index d8caf07..b9ebdb0 100644 --- a/openbsc/src/libmsc/mncc_sock.c +++ b/openbsc/src/libmsc/mncc_sock.c @@ -213,6 +213,29 @@ static int mncc_sock_cb(struct osmo_fd *bfd, unsigned int flags) return rc; } +/** + * Send a version indication to the remote. + */ +static void queue_hello(struct mncc_sock_state *mncc) +{ + struct gsm_mncc_hello *hello; + struct msgb *msg; + + msg = msgb_alloc(512, "mncc hello"); + if (!msg) { + LOGP(DMNCC, LOGL_ERROR, "Failed to allocate hello.\n"); + mncc_sock_close(mncc); + return; + } + + hello = (struct gsm_mncc_hello *) msgb_put(msg, sizeof(*hello)); + hello->msg_type = MNCC_SOCKET_HELLO; + hello->version = MNCC_SOCK_VERSION; + + msgb_enqueue(&mncc->net->upqueue, msg); + mncc->conn_bfd.when |= BSC_FD_WRITE; +} + /* accept a new connection */ static int mncc_sock_accept(struct osmo_fd *bfd, unsigned int flags) { @@ -253,6 +276,7 @@ static int mncc_sock_accept(struct osmo_fd *bfd, unsigned int flags) LOGP(DMNCC, LOGL_NOTICE, "MNCC Socket has connection with external " "call control application\n"); + queue_hello(state); return 0; } -- 1.7.5.4 --------------020402070302030203020301 Content-Type: text/x-patch; name="0001-gsm-Verify-the-MNCC_VERSION-of-the-BSC-MS-and-close-.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename*0="0001-gsm-Verify-the-MNCC_VERSION-of-the-BSC-MS-and-close-.pa"; filename*1="tch"

1 0

[PATCH] gsm: Verify the MNCC_VERSION of the BSC/MS and close the socket on mismatch
by Holger Hans Peter Freyther 21 Oct '11

21 Oct '11

The BSC/MS will send a Hello packet that includes the version number, make LCR verify this version number and close the socket in case it does not match a supported version. --- gsm.cpp | 12 ++++++++++++ mncc.h | 7 +++++++ 2 files changed, 19 insertions(+), 0 deletions(-) diff --git a/gsm.cpp b/gsm.cpp index e6806c3..227d618 100644 --- a/gsm.cpp +++ b/gsm.cpp @@ -1042,6 +1042,7 @@ static int mncc_fd_read(struct lcr_fd *lfd, void *inst, int idx) int rc; static char buf[sizeof(struct gsm_mncc)+1024]; struct gsm_mncc *mncc_prim = (struct gsm_mncc *) buf; + struct gsm_mncc_hello *hello = (struct gsm_mncc_hello *) buf; memset(buf, 0, sizeof(buf)); rc = recv(lfd->fd, buf, sizeof(buf), 0); @@ -1050,6 +1051,17 @@ static int mncc_fd_read(struct lcr_fd *lfd, void *inst, int idx) if (rc < 0) return rc; + /* TODO: size check? */ + switch (mncc_prim->msg_type) { + case MNCC_SOCKET_HELLO: + if (hello->version != MNCC_SOCK_VERSION) { + PERROR("MNCC version different. BSC version is %u\n", hello->version); + mncc_fd_close(lcr_gsm, lfd); + return 0; + } + break; + } + /* Hand the MNCC message into LCR */ switch (lcr_gsm->type) { #ifdef WITH_GSM_BS diff --git a/mncc.h b/mncc.h index e5f8216..fac7145 100644 --- a/mncc.h +++ b/mncc.h @@ -56,6 +56,8 @@ #define GSM_TCHF_FRAME 0x0300 #define GSM_TCHF_FRAME_EFR 0x0301 +#define MNCC_SOCKET_HELLO 0x0400 + #define GSM_MAX_FACILITY 128 #define GSM_MAX_SSVERSION 128 #define GSM_MAX_USERUSER 128 @@ -185,3 +187,8 @@ struct gsm_data_frame { unsigned char data[0]; }; +#define MNCC_SOCK_VERSION 1 +struct gsm_mncc_hello { + u_int32_t msg_type; + u_int32_t version; +}; -- 1.7.5.4 --------------020402070302030203020301--

1 0

R: Re: LCR + Asterisk + NanoBTS: Strange Voice Behaviour "Dropping incompatible voice frame on lcr/1"
by Luca Bongiorni 20 Oct '11

20 Oct '11

Hi Gregory, here the log from "asterisk -vvvvv": http://pastebin.com/3brJ9NxC > please send me a complete call trace. [verbose 3] Cheers, Luca

1 0

[RFT] Couple of changes to nanoBTS and nokia insites bootup sequences to be tested
by Sylvain Munaut 20 Oct '11

20 Oct '11

Hi, I've just pushed a couples of changes to a branch sylvain/pending that need to be tested. They alter the startup process for the nanoBTS (fixing the issues some people had with starting GPRS support, when the bts was not connecting to the SGSN). And also a fix for the Nokia InSite startup sequence where the reset command was not sent due to missing initialization of .do_reset. Since I know initialization sequence can be a rather fragile process, if people could test this didn't break anything for them, it'd be nice. Cheers, Sylvain

3 3

Re: [RFT] Couple of changes to nanoBTS and nokia bootup sequences to be tested
by Sylvain Munaut 20 Oct '11

20 Oct '11

Hi, > That’s all I get, and it never bootstraps. In libosmo-abis, in src/input/lapd.c line 90, try replacing 0,240000, by 0,480000, Also, make sure you plugged the power like 10 min before trying. Cheers, Sylvain

2 1

authentication and encryption???
by GSM Driller 19 Oct '11

19 Oct '11

hello list, I found some some where in openbts archives that authentication and encryption has been implemented in openbsc, kindly advise how can i add these features in openbts???, i studied libosmocore libraby, but unable to figure out, how it can be done, please advise!!!

2 2

Re: [RFT] Couple of changes to nanoBTS and nokia bootup sequences to be tested
by Dieter Spaar 18 Oct '11

18 Oct '11

Hello Sylvain, On Mon, 17 Oct 2011 16:11:25 +0200, "Sylvain Munaut" <246tnt(a)gmail.com> wrote: > > Actually to get it to start I have to: > - After powering it, wait for like 10 min. (If I try to start openbsc > any sooner, it will never bootstrap) If I remember, I never had to wait longer than half a minute after power on. But this was with the version from August, so some changes in the code might cause this behaviour. > But I could add this 'reset' process as an nokia specific option to > the vty (i.e. reset_on_start or something ). A configuration option is fine, I would set the default to "always reset" and only if someone know what he does, he can turn the reset off (I think I had strange effects while changing the configuration and not doing a reset, so this situation should be avoided). Best regards, Dieter -- Dieter Spaar, Germany spaar(a)mirider.augusta.de

2 1

Legal situation when using auth policy token
by Lennart Müller 18 Oct '11

18 Oct '11

Hi, we own a frequency usage licence from the Bundesnetzagentur and ran our network with auth policy token. So every new phone trying to attach to our network will receive a SMS with information how to register and a token. Thereafter, the phone is kicked out and will no longer be able to register again. Now there was a problem with some phones from Cupertino which, as I heard, registered to our network, received the SMS, were kicked out again but did not try to re-register with their home network. So some "nice" guys threaten to call the Bundesnetzagentur if we will not shut down the network immediately. As a quick solution, we changed the registration procedure from Token-Input to IMEI-Input. My question is: Are there really legal problems when using the "Auth Token" policy? Many Thanks, Lennart

4 6