Hello all

can anyone send me a openbsc.cfg file for nanobts 1900pcs....? because still i am struck with my nanobts pcs1900.....i can send sms but no voice calls.....do i need to install mISDN and LCR for single bts ? ....

thanks

regards

Rajitha Peiris

Sri lanka

________________________________ From: OpenBSC openbsc-bounces@lists.osmocom.org on behalf of openbsc-request@lists.osmocom.org openbsc-request@lists.osmocom.org Sent: Wednesday, February 8, 2017 8:56:30 PM To: openbsc@lists.osmocom.org Subject: OpenBSC Digest, Vol 28, Issue 5

Send OpenBSC mailing list submissions to openbsc@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@lists.osmocom.org

You can reach the person managing the list at openbsc-owner@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. Re: MS cannot connect; Location Update Request not received by BTS (Hossein Amini) 2. Re: [PATCH net-next v2 2/6] gtp: merge gtp_get_net and gtp_genl_find_dev (Harald Welte) 3. Re: [PATCH net-next v2 1/6] gtp: make GTP sockets in gtp_newlink optional (Harald Welte) 4. Re: [PATCH net-next v2 4/6] gtp: consolidate pdp context destruction into helper (Harald Welte) 5. Re: [PATCH net-next v2 5/6] gtp: add socket to pdp context (Harald Welte) 6. Re: [PATCH net-next v2 3/6] gtp: unify genl_find_pdp and prepare for per socket lookup (Harald Welte) 7. Re: [PATCH net-next v2 0/6] gtp: misc improvements (Harald Welte) 8. Re: weekly test report (w5 2017) (Neels Hofmeyr)

----------------------------------------------------------------------

Message: 1 Date: Mon, 6 Feb 2017 16:45:40 +0330 From: Hossein Amini hosseinamini2578@gmail.com To: openbsc@lists.osmocom.org Subject: Re: MS cannot connect; Location Update Request not received by BTS Message-ID: CAF81cShkO+JiamxQJXhqfpbOWxi9_8aEWsd5wTDhmZ0Vd912Xw@mail.gmail.com Content-Type: text/plain; charset="utf-8"

I installed master branch now(4/feb/2017 at 18:30) and retry, but I can not release channel and receive error in nitb. I do not access to a external timing source like octoClock, do you use external timing source? do you have a easy solution to check that? My NITB log is like your log by 20170203014240662 and repeat. I retried connecting about 10 min but nothing happened.

NITB log that repeat is:

20170204071216381 DRLL <0000> chan_alloc.c:352 (bts=0,trx=0,ts=0,pchan=CCCH+SDCCH4) Allocating lchan=0 as SDCCH 20170204071216381 DRSL <0004> abis_rsl.c:1819 (bts=0,trx=0,ts=0,ss=0) Activating ARFCN(0) SS(0) lctype SDCCH r=LOCATION_UPDATE ra=0x06 ta=0 20170204071216381 DRSL <0004> abis_rsl.c:580 (bts=0,trx=0,ts=0,pchan=CCCH+SDCCH4) Tx RSL Channel Activate with act_type=INITIAL 20170204071216381 DRSL <0004> abis_rsl.c:1189 (bts=0,trx=0,ts=0,ss=0) state NONE -> ACTIVATION REQUESTED 20170204071216381 DRSL <0004> abis_rsl.c:1546 (bts=0,trx=0,ts=0,ss=0) CHANNEL ACTIVATE ACK 20170204071216381 DRSL <0004> abis_rsl.c:1189 (bts=0,trx=0,ts=0,ss=0) state ACTIVATION REQUESTED -> ACTIVE 20170204071226381 DRSL <0004> abis_rsl.c:852 (bts=0,trx=0,ts=0,ss=0) RF Channel Release due to error: 1 20170204071226381 DRSL <0004> abis_rsl.c:762 (bts=0,trx=0,ts=0,ss=0) DEACTivate SACCH CMD 20170204071226381 DRSL <0004> abis_rsl.c:1189 (bts=0,trx=0,ts=0,ss=0) state ACTIVE -> RELEASE DUE ERROR 20170204071226382 DRSL <0004> abis_rsl.c:925 (bts=0,trx=0,ts=0,ss=0) RF CHANNEL RELEASE ACK 20170204071228382 DRSL <0004> abis_rsl.c:811 (bts=0,trx=0,ts=0,ss=0) is back in operation. 20170204071228382 DRSL <0004> abis_rsl.c:1189 (bts=0,trx=0,ts=0,ss=0) state RELEASE DUE ERROR -> NONE

On Fri, Feb 3, 2017 at 2:28 AM, Neels Hofmeyr neels@hofmeyr.de wrote:

Dear Hossein,

the mailing list is indeed the proper place to ask. If no-one replied to your question, it either means that no-one knows the answer, or that no-one has found the time to look into it. Don't be discouraged by that. Indeed I would prefer if you ask again on the mailing list instead of asking single mail addresses. I actually saw your mail on the list and did not know what to answer.

If you ask your question on-list again (possibly once a week), it might be that someone will come up with either an answer or with more questions that may lead you to a solution...

I sincerely hope that you will find a solution. It seems to me that it's merely a minor detail.

~N