From: Nathan G. <nat...@gm...> - 2009-09-29 18:03:16
|
All, I have been able to successfully install OpenBTS, and the other required dependancies, but there does not appear to be an OpenBTS.config file anywhere for the app to reference. Where do I obtain this file? Was it supposed to be part of the distribution from svn co http://gnuradio.org/svn/openbts/trunk/ openbts or was this file supposed to be created automatically during the install process? I have looked on the GNU Radio OpenBTS wiki and browsed the the source code, but have been unable to find the file itself. As far as I can tell, the version I downloaded from svn is 1.6 New Ibera. I am not sure if I missed something during the install process, or if the file was actually not part of the distribution. Please advise.... Thanks, |
From: Reynaldo B. <rey...@gm...> - 2009-09-29 18:18:57
|
On Tue, Sep 29, 2009 at 1:03 PM, Nathan Gray <nat...@gm...>wrote: > All, > > I have been able to successfully install OpenBTS, and the other required > dependancies, but there does not appear to be an OpenBTS.config file > anywhere for the app to reference. Where do I obtain this file? Was it > supposed to be part of the distribution from svn co > http://gnuradio.org/svn/openbts/trunk/ openbts or was this file supposed > to be created automatically during the install process? I have looked on the > GNU Radio OpenBTS wiki and browsed the the source code, but have been unable > to find the file itself. > > As far as I can tell, the version I downloaded from svn is 1.6 New Ibera. I > am not sure if I missed something during the install process, or if the file > was actually not part of the distribution. I believed it was provided with the distribution. > Please advise.... > Here you have one until that gets fixed http://dl.getdropbox.com/u/2158658/OpenBTS.config.example |
From: Nathan G. <nat...@gm...> - 2009-09-29 18:29:16
|
Thank you! Once I edit the example and save it as OpenBTS.config, should the file be located in the /openbts/apps directory? On Tue, Sep 29, 2009 at 11:18 AM, Reynaldo Baquerizo <rey...@gm...>wrote: > > > On Tue, Sep 29, 2009 at 1:03 PM, Nathan Gray <nat...@gm...>wrote: > >> All, >> >> I have been able to successfully install OpenBTS, and the other required >> dependancies, but there does not appear to be an OpenBTS.config file >> anywhere for the app to reference. Where do I obtain this file? Was it >> supposed to be part of the distribution from svn co >> http://gnuradio.org/svn/openbts/trunk/ openbts or was this file supposed >> to be created automatically during the install process? I have looked on the >> GNU Radio OpenBTS wiki and browsed the the source code, but have been unable >> to find the file itself. >> >> As far as I can tell, the version I downloaded from svn is 1.6 New Ibera. >> I am not sure if I missed something during the install process, or if the >> file was actually not part of the distribution. > > > I believed it was provided with the distribution. > > >> Please advise.... >> > > Here you have one until that gets fixed > http://dl.getdropbox.com/u/2158658/OpenBTS.config.example > > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9-12, 2009. Register now! > http://p.sf.net/sfu/devconf > _______________________________________________ > Openbts-discuss mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openbts-discuss > > |
From: Reynaldo B. <rey...@gm...> - 2009-09-29 18:35:21
|
Hi Nathan, On Tue, Sep 29, 2009 at 1:29 PM, Nathan Gray <nat...@gm...>wrote: > Thank you! Once I edit the example and save it as OpenBTS.config, should > the file be located in the /openbts/apps directory? > yes, it is its default location. |
From: Nathan G. <nat...@gm...> - 2009-09-29 18:37:27
|
Thank you again for your help. On Tue, Sep 29, 2009 at 11:34 AM, Reynaldo Baquerizo <rey...@gm...>wrote: > Hi Nathan, > > On Tue, Sep 29, 2009 at 1:29 PM, Nathan Gray <nat...@gm...>wrote: > >> Thank you! Once I edit the example and save it as OpenBTS.config, should >> the file be located in the /openbts/apps directory? >> > > yes, it is its default location. > > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9-12, 2009. Register now! > http://p.sf.net/sfu/devconf > _______________________________________________ > Openbts-discuss mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openbts-discuss > > |
From: Timur A. <tim...@um...> - 2009-09-29 19:08:47
|
Here's one that I found: # Sample OpenBTS configuration file. # Format of each line is. <key><space><value> # The key name can contain no spaces. # Everything between the first space and the end of the line becomes the value. # Comments must start with "#" at the beginning of the line. # Blank lines are OK. # As a gerenal rule, non-valid configuration values will crash OpenBTS. # # Logging parameters # # The initial global logging level: ERROR, WARNING, NOTICE, INFO, DEBUG, DEEPDEBUG LogLevel INFO # The log file path. If not set, logging goes to stdout. # LogFileName test.out # # Transceiver parameters # # Transceiver interface # This TRX.IP is not really adjustable. Just leave it as 127.0.0.1. TRX.IP 127.0.0.1 # This value is hard-coded in the transcevier. Just leave it alone. TRX.Port 5700 # Path to transceiver binary TRX.Path /home/timur/GSM-local/openbts/Transceiver/transceiver # TRX logging. # Logging level. TRX.LogLevel ERROR # Logging file. If not defined, logs to stdout. # TRX.LogFileName test.out # # SIP, RTP, servers # # Asterisk PBX Asterisk.IP 127.0.0.1 Asterisk.Port 5060 # Messaging server Messenger.IP 127.0.0.1 Messenger.Port 5063 # Local SIP/RTP ports SIP.Port 5062 RTP.Start 16484 RTP.Range 98 # Local SMS port for short code delivery. SMSLoopback.Port 5064 # # Special extensions. # # Routing extension for emergency calls. # PBX.Emergency 2101 # # SIP parameters # # SIP registration period in seconds. # Ideally, this should be slightly longer than GSM.T3212. SIP.RegistrationPeriod 3600 # # SIP Internal Timers. All timer values are given in millseconds. # These are from RFC-3261 Table A. # # SIP Timer A, the INVITE retry period, RFC-3261 Section 17.1.1.2 SIP.Timer.A 1000 # # SMS parameters # # ISDN address of source SMSC when we fake out a source SMSC. SMS.FakeSrcSMSC 0000 # ISDN address of destination SMSC when a fake value is needed. SMS.DefaultDestSMSC 0000 # The SMS HTTP gateway. # Comment out if you don't have one. # SMS.HTTP.Gateway api.clickatell.com # IF SMS.HTTP.Gateway IS DEFINED, SMS.HTTP.AccessString MUST ALSO BE DEFINED. # SMS.HTTP.AccessString sendmsg?user=xxxx&password=xxxx&api_id=xxxx # The "Welcome Message" is sent to uprovisioned handsets that try to register. # Comment out if you don't want this feature. # WELCOME MESSAGE MUST BE LESS THAN 161 CHARACTERS. # SMS.WelcomeMessage Welcome to OpenBTS # SMS.WelcomeMessage Your handset attempted to register with OpenBTS. # IF SMS.WelcomeMessage IS DEFINED, SMS.WelcomeShortCode MUST ALSO BE DEFINED. SMS.WelcomeShortCode 0000 # # GSM # # Network and cell identity. # Network Color Code, 0-7 GSM.NCC 0 # Basesation Color Code, 0-7 GSM.BCC 0 # Mobile Country Code, 3 digits. # MCC MUST BE 3 DIGITS. Prefix with 0s if needed. GSM.MCC 310 # Mobile Network Code, 2 or 3 digits. GSM.MNC 03 # Location Area Code, 0-65535 GSM.LAC 667 # Cell ID, 0-65535 GSM.CI 0 # Network "short name" to display on the handset. # SHORT NAME MUST BE LESS THAN 8 CHARACTERS. GSM.ShortName OpenBTS # Assignment type for call setup. # This is defined in an enum AssignmentType in GSMCommon.h. # 0=Early, 1=VeryEarly. GSM.AssignmentType 1 # Band and Frequency # Valid band values are 850, 900, 1800, 1900. GSM.Band 850 # Valid ARFCN range depends on the band. #GSM.ARFCN 29 GSM.ARFCN 180 # Downlink tx power level, dB wrt full power GSM.PowerAttenDB 0 # Beacon parameters. # L1 radio link timeout advertised on BCCH. # This is the RAW parameter sent on the BCCH. # See GSM 10.5.2.3 for encoding. # Value of 15 gives 64-frame timeout, about 30 seconds on the TCH. # This should be coordinated with T3109. GSM.RADIO_LINK_TIMEOUT 15 # Attach/detach flag. # Set to 1 to use attach/detach procedure, 0 otherwise. # This will make initial registration more prompt. # It will also cause an un-regstration if the handset powers off. GSM.ATT 1 # CCCH_CONF # See GSM 10.5.2.11 for encoding. # Value of 1 means we are using a C-V beacon. GSM.CCCH_CONF 1 # Maximum RACH retransmission attempts # This is the RAW parameter sent on the BCCH. # See GSM 04.08 10.5.2.29 for encoding. GSM.RACH.MaxRetrans 3 # Parameter to spread RACH busts over time. # This is the RAW parameter sent on the BCCH. # See GSM 04.08 10.5.2.29 for encoding. GSM.RACH.TxInteger 14 # Access class flags. # This is the RAW parameter sent on the BCCH. # See GSM 04.08 10.5.2.29 for encoding. # Set to 0 to allow full access. GSM.RACH.AC 0 # # GSM Timers. All timer values are given in milliseconds unless statedotherwise. # These come from GSM 04.08 11.2. # # T3212, registration timer. # Unlike most timers, this is given in MINUTES. # Actual period will be rounded down to a multiple of 6 minutes. # Any value below 6 minutes disables periodic registration. # Ideally, this should be slightly less than the SIP.RegistrationPeriod. GSM.T3212 6 Figured it'd be easy for others to grab off the mail directly. Timur On Tue, Sep 29, 2009 at 2:18 PM, Reynaldo Baquerizo <rey...@gm...> wrote: > > > On Tue, Sep 29, 2009 at 1:03 PM, Nathan Gray <nat...@gm...> > wrote: >> >> All, >> >> I have been able to successfully install OpenBTS, and the other required >> dependancies, but there does not appear to be an OpenBTS.config file >> anywhere for the app to reference. Where do I obtain this file? Was it >> supposed to be part of the distribution from svn co >> http://gnuradio.org/svn/openbts/trunk/ openbts or was this file supposed to >> be created automatically during the install process? I have looked on the >> GNU Radio OpenBTS wiki and browsed the the source code, but have been unable >> to find the file itself. >> >> As far as I can tell, the version I downloaded from svn is 1.6 New Ibera. >> I am not sure if I missed something during the install process, or if the >> file was actually not part of the distribution. > > I believed it was provided with the distribution. > >> >> Please advise.... > > Here you have one until that gets fixed > http://dl.getdropbox.com/u/2158658/OpenBTS.config.example > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9-12, 2009. Register now! > http://p.sf.net/sfu/devconf > _______________________________________________ > Openbts-discuss mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openbts-discuss |
From: Reynaldo B. <rey...@gm...> - 2009-09-29 19:21:33
|
Timur, What version of openBTS does it correspond to? One does support SMS, cause it might confuse others As for Nathan, he is using version 1.6 and SMS is not supported there. The one I posted it comes from a 1.6 distribution. Cheers, On Tue, Sep 29, 2009 at 2:08 PM, Timur Alperovich <tim...@um...>wrote: > Here's one that I found: > > # Sample OpenBTS configuration file. > # Format of each line is. <key><space><value> > # The key name can contain no spaces. > # Everything between the first space and the end of the line becomes the > value. > # Comments must start with "#" at the beginning of the line. > # Blank lines are OK. > # As a gerenal rule, non-valid configuration values will crash OpenBTS. > # > # Logging parameters > # > # The initial global logging level: ERROR, WARNING, NOTICE, INFO, > DEBUG, DEEPDEBUG > LogLevel INFO > > # The log file path. If not set, logging goes to stdout. > # LogFileName test.out > # > # Transceiver parameters > # > # Transceiver interface > # This TRX.IP is not really adjustable. Just leave it as 127.0.0.1. > TRX.IP 127.0.0.1 > > # This value is hard-coded in the transcevier. Just leave it alone. > TRX.Port 5700 > > # Path to transceiver binary > TRX.Path /home/timur/GSM-local/openbts/Transceiver/transceiver > > # TRX logging. > # Logging level. > TRX.LogLevel ERROR > > # Logging file. If not defined, logs to stdout. > # TRX.LogFileName test.out > # > > # SIP, RTP, servers > # > # Asterisk PBX > Asterisk.IP 127.0.0.1 > Asterisk.Port 5060 > > # Messaging server > Messenger.IP 127.0.0.1 > Messenger.Port 5063 > > # Local SIP/RTP ports > SIP.Port 5062 > RTP.Start 16484 > RTP.Range 98 > > # Local SMS port for short code delivery. > SMSLoopback.Port 5064 > > # > # Special extensions. > # > # Routing extension for emergency calls. > # PBX.Emergency 2101 > # > # SIP parameters > # > # SIP registration period in seconds. > # Ideally, this should be slightly longer than GSM.T3212. > SIP.RegistrationPeriod 3600 > > # > # SIP Internal Timers. All timer values are given in millseconds. > # These are from RFC-3261 Table A. > # > # SIP Timer A, the INVITE retry period, RFC-3261 Section 17.1.1.2 > SIP.Timer.A 1000 > > # > # SMS parameters > # > # ISDN address of source SMSC when we fake out a source SMSC. > SMS.FakeSrcSMSC 0000 > > # ISDN address of destination SMSC when a fake value is needed. > SMS.DefaultDestSMSC 0000 > > # The SMS HTTP gateway. > # Comment out if you don't have one. > # SMS.HTTP.Gateway api.clickatell.com > # IF SMS.HTTP.Gateway IS DEFINED, SMS.HTTP.AccessString MUST ALSO BE > DEFINED. > # SMS.HTTP.AccessString sendmsg?user=xxxx&password=xxxx&api_id=xxxx > # The "Welcome Message" is sent to uprovisioned handsets that try to > register. > # Comment out if you don't want this feature. > # WELCOME MESSAGE MUST BE LESS THAN 161 CHARACTERS. > # SMS.WelcomeMessage Welcome to OpenBTS > # SMS.WelcomeMessage Your handset attempted to register with OpenBTS. > # IF SMS.WelcomeMessage IS DEFINED, SMS.WelcomeShortCode MUST ALSO BE > DEFINED. > SMS.WelcomeShortCode 0000 > > # > # GSM > # > # Network and cell identity. > # Network Color Code, 0-7 > GSM.NCC 0 > > # Basesation Color Code, 0-7 > GSM.BCC 0 > > # Mobile Country Code, 3 digits. > # MCC MUST BE 3 DIGITS. Prefix with 0s if needed. > GSM.MCC 310 > > # Mobile Network Code, 2 or 3 digits. > GSM.MNC 03 > > # Location Area Code, 0-65535 > GSM.LAC 667 > > # Cell ID, 0-65535 > GSM.CI 0 > > # Network "short name" to display on the handset. > # SHORT NAME MUST BE LESS THAN 8 CHARACTERS. > GSM.ShortName OpenBTS > > # Assignment type for call setup. > # This is defined in an enum AssignmentType in GSMCommon.h. > # 0=Early, 1=VeryEarly. > GSM.AssignmentType 1 > > # Band and Frequency > # Valid band values are 850, 900, 1800, 1900. > GSM.Band 850 > > # Valid ARFCN range depends on the band. > #GSM.ARFCN 29 > GSM.ARFCN 180 > > # Downlink tx power level, dB wrt full power > GSM.PowerAttenDB 0 > > # Beacon parameters. > # L1 radio link timeout advertised on BCCH. > # This is the RAW parameter sent on the BCCH. > # See GSM 10.5.2.3 for encoding. > # Value of 15 gives 64-frame timeout, about 30 seconds on the TCH. > # This should be coordinated with T3109. > GSM.RADIO_LINK_TIMEOUT 15 > > # Attach/detach flag. > # Set to 1 to use attach/detach procedure, 0 otherwise. > # This will make initial registration more prompt. > # It will also cause an un-regstration if the handset powers off. > GSM.ATT 1 > > # CCCH_CONF > # See GSM 10.5.2.11 for encoding. > # Value of 1 means we are using a C-V beacon. > GSM.CCCH_CONF 1 > > # Maximum RACH retransmission attempts > # This is the RAW parameter sent on the BCCH. > # See GSM 04.08 10.5.2.29 for encoding. > GSM.RACH.MaxRetrans 3 > > # Parameter to spread RACH busts over time. > # This is the RAW parameter sent on the BCCH. > # See GSM 04.08 10.5.2.29 for encoding. > GSM.RACH.TxInteger 14 > > # Access class flags. > # This is the RAW parameter sent on the BCCH. > # See GSM 04.08 10.5.2.29 for encoding. > # Set to 0 to allow full access. > GSM.RACH.AC 0 > > # > # GSM Timers. All timer values are given in milliseconds unless > statedotherwise. > # These come from GSM 04.08 11.2. > # > # T3212, registration timer. > # Unlike most timers, this is given in MINUTES. > # Actual period will be rounded down to a multiple of 6 minutes. > # Any value below 6 minutes disables periodic registration. > # Ideally, this should be slightly less than the SIP.RegistrationPeriod. > GSM.T3212 6 > > Figured it'd be easy for others to grab off the mail directly. > > Timur > > On Tue, Sep 29, 2009 at 2:18 PM, Reynaldo Baquerizo > <rey...@gm...> wrote: > > > > > > On Tue, Sep 29, 2009 at 1:03 PM, Nathan Gray <nat...@gm...> > > wrote: > >> > >> All, > >> > >> I have been able to successfully install OpenBTS, and the other required > >> dependancies, but there does not appear to be an OpenBTS.config file > >> anywhere for the app to reference. Where do I obtain this file? Was it > >> supposed to be part of the distribution from svn co > >> http://gnuradio.org/svn/openbts/trunk/ openbts or was this file > supposed to > >> be created automatically during the install process? I have looked on > the > >> GNU Radio OpenBTS wiki and browsed the the source code, but have been > unable > >> to find the file itself. > >> > >> As far as I can tell, the version I downloaded from svn is 1.6 New > Ibera. > >> I am not sure if I missed something during the install process, or if > the > >> file was actually not part of the distribution. > > > > I believed it was provided with the distribution. > > > >> > >> Please advise.... > > > > Here you have one until that gets fixed > > http://dl.getdropbox.com/u/2158658/OpenBTS.config.example > > > > > ------------------------------------------------------------------------------ > > Come build with us! The BlackBerry® Developer Conference in SF, CA > > is the only developer event you need to attend this year. Jumpstart your > > developing skills, take BlackBerry mobile applications to market and stay > > ahead of the curve. Join us from November 9-12, 2009. Register > now! > > http://p.sf.net/sfu/devconf > > _______________________________________________ > > Openbts-discuss mailing list > > Ope...@li... > > https://lists.sourceforge.net/lists/listinfo/openbts-discuss > > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9-12, 2009. Register now! > http://p.sf.net/sfu/devconf > _______________________________________________ > Openbts-discuss mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openbts-discuss > |
From: Timur A. <tim...@um...> - 2009-09-29 19:29:41
|
Reynaldo, On Tue, Sep 29, 2009 at 3:20 PM, Reynaldo Baquerizo <rey...@gm...> wrote: > Timur, > > What version of openBTS does it correspond to? One does support SMS, cause > it might confuse others > As for Nathan, he is using version 1.6 and SMS is not supported there. > > The one I posted it comes from a 1.6 distribution. You're right - it's not 1.6 and I missed that part. I used this config file with 2.4 (I believe that's the version in the gnuradio trunk). > On Tue, Sep 29, 2009 at 2:08 PM, Timur Alperovich <tim...@um...> > wrote: >> >> Here's one that I found: >> >> # Sample OpenBTS configuration file. >> # Format of each line is. <key><space><value> >> # The key name can contain no spaces. >> # Everything between the first space and the end of the line becomes the >> value. >> # Comments must start with "#" at the beginning of the line. >> # Blank lines are OK. >> # As a gerenal rule, non-valid configuration values will crash OpenBTS. >> # >> # Logging parameters >> # >> # The initial global logging level: ERROR, WARNING, NOTICE, INFO, >> DEBUG, DEEPDEBUG >> LogLevel INFO >> >> # The log file path. If not set, logging goes to stdout. >> # LogFileName test.out >> # >> # Transceiver parameters >> # >> # Transceiver interface >> # This TRX.IP is not really adjustable. Just leave it as 127.0.0.1. >> TRX.IP 127.0.0.1 >> >> # This value is hard-coded in the transcevier. Just leave it alone. >> TRX.Port 5700 >> >> # Path to transceiver binary >> TRX.Path /home/timur/GSM-local/openbts/Transceiver/transceiver >> >> # TRX logging. >> # Logging level. >> TRX.LogLevel ERROR >> >> # Logging file. If not defined, logs to stdout. >> # TRX.LogFileName test.out >> # >> >> # SIP, RTP, servers >> # >> # Asterisk PBX >> Asterisk.IP 127.0.0.1 >> Asterisk.Port 5060 >> >> # Messaging server >> Messenger.IP 127.0.0.1 >> Messenger.Port 5063 >> >> # Local SIP/RTP ports >> SIP.Port 5062 >> RTP.Start 16484 >> RTP.Range 98 >> >> # Local SMS port for short code delivery. >> SMSLoopback.Port 5064 >> >> # >> # Special extensions. >> # >> # Routing extension for emergency calls. >> # PBX.Emergency 2101 >> # >> # SIP parameters >> # >> # SIP registration period in seconds. >> # Ideally, this should be slightly longer than GSM.T3212. >> SIP.RegistrationPeriod 3600 >> >> # >> # SIP Internal Timers. All timer values are given in millseconds. >> # These are from RFC-3261 Table A. >> # >> # SIP Timer A, the INVITE retry period, RFC-3261 Section 17.1.1.2 >> SIP.Timer.A 1000 >> >> # >> # SMS parameters >> # >> # ISDN address of source SMSC when we fake out a source SMSC. >> SMS.FakeSrcSMSC 0000 >> >> # ISDN address of destination SMSC when a fake value is needed. >> SMS.DefaultDestSMSC 0000 >> >> # The SMS HTTP gateway. >> # Comment out if you don't have one. >> # SMS.HTTP.Gateway api.clickatell.com >> # IF SMS.HTTP.Gateway IS DEFINED, SMS.HTTP.AccessString MUST ALSO BE >> DEFINED. >> # SMS.HTTP.AccessString sendmsg?user=xxxx&password=xxxx&api_id=xxxx >> # The "Welcome Message" is sent to uprovisioned handsets that try to >> register. >> # Comment out if you don't want this feature. >> # WELCOME MESSAGE MUST BE LESS THAN 161 CHARACTERS. >> # SMS.WelcomeMessage Welcome to OpenBTS >> # SMS.WelcomeMessage Your handset attempted to register with OpenBTS. >> # IF SMS.WelcomeMessage IS DEFINED, SMS.WelcomeShortCode MUST ALSO BE >> DEFINED. >> SMS.WelcomeShortCode 0000 >> >> # >> # GSM >> # >> # Network and cell identity. >> # Network Color Code, 0-7 >> GSM.NCC 0 >> >> # Basesation Color Code, 0-7 >> GSM.BCC 0 >> >> # Mobile Country Code, 3 digits. >> # MCC MUST BE 3 DIGITS. Prefix with 0s if needed. >> GSM.MCC 310 >> >> # Mobile Network Code, 2 or 3 digits. >> GSM.MNC 03 >> >> # Location Area Code, 0-65535 >> GSM.LAC 667 >> >> # Cell ID, 0-65535 >> GSM.CI 0 >> >> # Network "short name" to display on the handset. >> # SHORT NAME MUST BE LESS THAN 8 CHARACTERS. >> GSM.ShortName OpenBTS >> >> # Assignment type for call setup. >> # This is defined in an enum AssignmentType in GSMCommon.h. >> # 0=Early, 1=VeryEarly. >> GSM.AssignmentType 1 >> >> # Band and Frequency >> # Valid band values are 850, 900, 1800, 1900. >> GSM.Band 850 >> >> # Valid ARFCN range depends on the band. >> #GSM.ARFCN 29 >> GSM.ARFCN 180 >> >> # Downlink tx power level, dB wrt full power >> GSM.PowerAttenDB 0 >> >> # Beacon parameters. >> # L1 radio link timeout advertised on BCCH. >> # This is the RAW parameter sent on the BCCH. >> # See GSM 10.5.2.3 for encoding. >> # Value of 15 gives 64-frame timeout, about 30 seconds on the TCH. >> # This should be coordinated with T3109. >> GSM.RADIO_LINK_TIMEOUT 15 >> >> # Attach/detach flag. >> # Set to 1 to use attach/detach procedure, 0 otherwise. >> # This will make initial registration more prompt. >> # It will also cause an un-regstration if the handset powers off. >> GSM.ATT 1 >> >> # CCCH_CONF >> # See GSM 10.5.2.11 for encoding. >> # Value of 1 means we are using a C-V beacon. >> GSM.CCCH_CONF 1 >> >> # Maximum RACH retransmission attempts >> # This is the RAW parameter sent on the BCCH. >> # See GSM 04.08 10.5.2.29 for encoding. >> GSM.RACH.MaxRetrans 3 >> >> # Parameter to spread RACH busts over time. >> # This is the RAW parameter sent on the BCCH. >> # See GSM 04.08 10.5.2.29 for encoding. >> GSM.RACH.TxInteger 14 >> >> # Access class flags. >> # This is the RAW parameter sent on the BCCH. >> # See GSM 04.08 10.5.2.29 for encoding. >> # Set to 0 to allow full access. >> GSM.RACH.AC 0 >> >> # >> # GSM Timers. All timer values are given in milliseconds unless >> statedotherwise. >> # These come from GSM 04.08 11.2. >> # >> # T3212, registration timer. >> # Unlike most timers, this is given in MINUTES. >> # Actual period will be rounded down to a multiple of 6 minutes. >> # Any value below 6 minutes disables periodic registration. >> # Ideally, this should be slightly less than the SIP.RegistrationPeriod. >> GSM.T3212 6 >> >> Figured it'd be easy for others to grab off the mail directly. >> >> Timur >> >> On Tue, Sep 29, 2009 at 2:18 PM, Reynaldo Baquerizo >> <rey...@gm...> wrote: >> > >> > >> > On Tue, Sep 29, 2009 at 1:03 PM, Nathan Gray <nat...@gm...> >> > wrote: >> >> >> >> All, >> >> >> >> I have been able to successfully install OpenBTS, and the other >> >> required >> >> dependancies, but there does not appear to be an OpenBTS.config file >> >> anywhere for the app to reference. Where do I obtain this file? Was it >> >> supposed to be part of the distribution from svn co >> >> http://gnuradio.org/svn/openbts/trunk/ openbts or was this file >> >> supposed to >> >> be created automatically during the install process? I have looked on >> >> the >> >> GNU Radio OpenBTS wiki and browsed the the source code, but have been >> >> unable >> >> to find the file itself. >> >> >> >> As far as I can tell, the version I downloaded from svn is 1.6 New >> >> Ibera. >> >> I am not sure if I missed something during the install process, or if >> >> the >> >> file was actually not part of the distribution. >> > >> > I believed it was provided with the distribution. >> > >> >> >> >> Please advise.... >> > >> > Here you have one until that gets fixed >> > http://dl.getdropbox.com/u/2158658/OpenBTS.config.example >> > >> > >> > ------------------------------------------------------------------------------ >> > Come build with us! The BlackBerry® Developer Conference in SF, CA >> > is the only developer event you need to attend this year. Jumpstart your >> > developing skills, take BlackBerry mobile applications to market and >> > stay >> > ahead of the curve. Join us from November 9-12, 2009. Register >> > now! >> > http://p.sf.net/sfu/devconf >> > _______________________________________________ >> > Openbts-discuss mailing list >> > Ope...@li... >> > https://lists.sourceforge.net/lists/listinfo/openbts-discuss >> >> >> ------------------------------------------------------------------------------ >> Come build with us! The BlackBerry® Developer Conference in SF, CA >> is the only developer event you need to attend this year. Jumpstart your >> developing skills, take BlackBerry mobile applications to market and stay >> ahead of the curve. Join us from November 9-12, 2009. Register >> now! >> http://p.sf.net/sfu/devconf >> _______________________________________________ >> Openbts-discuss mailing list >> Ope...@li... >> https://lists.sourceforge.net/lists/listinfo/openbts-discuss > > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9-12, 2009. Register now! > http://p.sf.net/sfu/devconf > _______________________________________________ > Openbts-discuss mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openbts-discuss > > -- Cheers, Timur |
From: Reynaldo B. <rey...@gm...> - 2009-09-29 19:36:48
|
Timur, You're right - it's not 1.6 and I missed that part. I used this config > file with 2.4 (I believe that's the version in the gnuradio trunk). > Not quite right, last change was "Moving r1<http://gnuradio.org/trac/changeset/1>.6 "New Iberia" to GNU Radio." unless I'm wrong. |
From: Timur A. <tim...@um...> - 2009-09-29 19:49:20
|
Reynaldo, >> You're right - it's not 1.6 and I missed that part. I used this config >> file with 2.4 (I believe that's the version in the gnuradio trunk). > > Not quite right, last change was "Moving r1.6 "New Iberia" to GNU Radio." > unless I'm wrong. Ok, I see what you're saying. I went by the README, which made me think 2.2 was the trunk (not sure how I got 2.4 though - must've slipped somehow). I got the config file from a pdf document describing how to setup OpenBTS, but I guess I wasn't sure about the version of either. To answer your original question, I guess I have no idea which version that config file correlates to. > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9-12, 2009. Register now! > http://p.sf.net/sfu/devconf > _______________________________________________ > Openbts-discuss mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openbts-discuss -- Cheers, Timur |