From: Axelle <aaf...@gm...> - 2011-08-24 15:33:22
|
On Wed, Aug 24, 2011 at 2:50 PM, Walter Barmak <wb...@pr...> wrote: > Hi Axelle, > > Thanks a lot for your answer. I'm thinking of using autoprovisioning > (letting all cell phones within the openbts range camp on my network). I > would like to mention that I've tried talking with 2 cell phones no > farther apart than 10 meters. I'm in an office bigger than 10 meters, so > I would like to ask whether you consider it safe. > > I've read the problems it may cause, like letting other cell phones from > the area camp, but can this be so when I cannot talk farther apart than > 10 meters? Could I possibly use autoprovisioning without causing any > consequences? Walter, I searched for you an explicit answer of David in the mailing-list. See below. I think you should get yourself a better clock. Regards, -- Axelle ---------- Forwarded message ---------- From: David A. Burgess <dbu...@jc...> Date: Mon, Oct 11, 2010 at 6:36 PM Subject: Re: [Openbts-discuss] TX failed to tune -> now tuning, but phone not registering ! To: Sylvain Munaut <24...@gm...> Cc: Axelle <aaf...@gm...>, ope...@li... This is why I would prefer to remove support for 64 MHz clocks from the public distribution of OpenBTS. I've had this discussion privately with a few people but will point out this example publicly. We put information about clock accuracy in the wiki (http://gnuradio.org/redmine/wiki/gnuradio/OpenBTSClocks), we have these discussions on the list on a regular basis, and still people keep trying to run OpenBTS on stock USRP hardware, even in the 1800/1900 bands, where it is almost certain to fail due to the crazy thermal clock drift. |