Re: [Openbts-discuss] getting started

[Joe S. <joe...@eu...>]

Hey Gabriel,

I don't know if I'm a good reference since my openBTS network isn't  
functional yet but i know that this openBTS for dummies document was  
really helpful. Even if it doesn't cover all the problems you may  
encounter it still provides you with the experience of previous  
newbies :), you get:

a useful roadmap, with step by step instructions
advice to change the USRP clock
and all the configs and patchs necessary to make your system (almsot  
:) ) work depending on your configuration.

But I believe it is written for openbts 2.6 and gnu radio 3.2.2 ...  
which are not the newest versions...

Hope this helps,

Good luck with your project !

Joe


Quoting Gabriel Zea <ze...@ra...>:

> Im planning to use openbts in a project.  It is a network for a public
> event with serveral hundreds of people asisting, ive seen openbts was
> used in burningman.  I will like to use a desktop computer with the
> hardware stack referenced in openbts for dummies [1]. before buying
> hardware I will like to know any recomendation about what is the best
> choice.
>
> Ive seen openbts for dummies[1] there they have some suggestions.
> Does anybody knows if it is an updated and reliable document ?
>
> [1] http://gnuradio.org/redmine/attachments/198/OpenBTS-for-dummies.pdf
>
> thanks for any info
> --
> Gabriel Zea
>
> work :: http://martinez-zea.info
> portfolio :: http://zea.randomlab.net
>
> @twitter | @identica :: z3a
> @flickr :: http://is.gd/1Mry9
> @skype :: g.z.e.a
>
> ------------------------------------------------------------------------------
> Colocation vs. Managed Hosting
> A question and answer guide to determining the best fit
> for your organization - today and in the future.
> http://p.sf.net/sfu/internap-sfd2d
> _______________________________________________
> Openbts-discuss mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/openbts-discuss
>
>



-------------------------------------------------------------------------------
This message was sent using EURECOM Webmail: http://webmail.eurecom.fr