try in 1900 band. For me it works fine.

What all component you are running ?  

BR

Dhananjay

On Mon, Jan 23, 2017 at 11:43 AM, Snehasish Kar <snehasish.cse@live.com> wrote:

Problem is usrp x310 doesnot support the gsmband, it works above 1.2GHz. Also if I still change the MCC and MNC I am not not able to find the network on the phone, and any clue on this error "check_rx_md_err: An internal receive buffer has filled", it comes in osmo-trx.

---

From: Dhananjay kumar <dhananjay.cse@gmail.com>
Sent: Monday, January 23, 2017 11:37:38 AM
To: Snehasish Kar
Cc: nhofmeyr@sysmocom.de

Subject: Re: Omsobts -osmotrx communication problem

 

hi,

network country code 404

 mobile network code 31

Change it to 

network country code 001

 mobile network code 01

 short name  TESTPLMN

 long name TESTPLMN

Try it in Band 850 . 

900 and 1800 and widely used in India by commercial  operates.

Remove all neighbor cell list.

You are using 404 31 , it might match some real network, and you will not able to see your test network.

BR

Dhananjay

On Mon, Jan 23, 2017 at 11:20 AM, Snehasish Kar <snehasish.cse@live.com> wrote:

Hi I have attached my config as requested, also in osmo-trx I am getting the following error "check_rx_md_err: An internal receive buffer has filled" and I am not able to view the network in my phone.  I am using usrp x310 and os UBUNTU.

BR

Snehasish

---

From: Neels Hofmeyr <nhofmeyr@sysmocom.de>
Sent: Saturday, January 21, 2017 4:35:06 AM
To: Snehasish Kar
Cc: openbsc@lists.osmocom.org
Subject: Re: Omsobts -osmotrx communication problem

 

On Fri, Jan 20, 2017 at 11:58:53AM +0000, Snehasish Kar wrote:
> Hi
>
> I have installed osmobts and osmotrx  with openbsc, to enable openbsc with usrp. But whenever I tried running the three applications, I gave the following error in osmobts. Please help me with it.

>
>
> <000b> trx_if.c:490 Tx burst length 0 invalid
> > <000b> trx_if.c:490 Tx burst length 0 invalid
> > <000b> trx_if.c:490 Tx burst length 0 invalid
> > <000b> trx_if.c:490 Tx burst length 0 invalid
> > <000b> trx_if.c:490 Tx burst length 0 invalid
> > <000b> trx_if.c:490 Tx burst length 0 invalid
> > <000b> trx_if.c:490 Tx burst length 0 invalid
> > <000b> trx_if.c:490 Tx burst length 0 invalid
> > <000b> trx_if.c:490 Tx burst length 0 invalid
> > <000b> trx_if.c:490 Tx burst length 0 invalid
> > <000b> trx_if.c:490 Tx burst length 0 invalid
> > <000b> trx_if.c:490 Tx burst length 0 invalid
> > <000b> trx_if.c:490 Tx burst length 0 invalid
> > <000b> trx_if.c:490 Tx burst length 0 invalid
> > <000b> trx_if.c:490 Tx burst length 0 invalid
> > <000b> trx_if.c:490 Tx burst length 0 invalid
> > <000b> trx_if.c:490 Tx burst length 0 invalid

If I remember correctly, osmo-bts-trx will at startup show a bunch of these and
then continue normally.

To clarify, you need to run 'osmo-trx', 'osmo-bts-trx' and 'osmo-nitb'.
We can't help further with this little information on your config.

~N


--
- Neels Hofmeyr <nhofmeyr@sysmocom.de>          http://www.sysmocom.de/
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschäftsführer / Managing Directors: Harald Welte

--

Thanks & Regards

Dhananjay

9686184214

Luck is what happens when preparation meets opportunity.

--

Thanks & Regards

Dhananjay

9686184214

Luck is what happens when preparation meets opportunity.