Difference between revisions of "OpenBTS: Database SQLite"

From OnnoWiki
Jump to navigation Jump to search
 
(30 intermediate revisions by the same user not shown)
Line 1: Line 1:
OpenBTS P2.8 menggunakan file database sqlite untuk mengkonfigurasi maupun membuat informasi status tersedia untuk aplikasi external. Sqlite adalah sebuah database SQL yang serverless, self-contained awalnya di kembangkan untuk guided missile dan sekarang banyak digunakan untuk banyak aplikasi, termasuk Blackberry, Symbian, iOS dan sistem operasi Android operating systems. Untuk informasi lebih lanjut tentang sqlite dapat dilihat di situs http://www.sqlite.org
+
OpenBTS P2.8 menggunakan file [[database]] [[sqlite]] untuk mengkonfigurasi maupun membuat informasi status tersedia untuk aplikasi external. Sqlite adalah sebuah [[database]] [[SQL]] yang serverless, self-contained awalnya di kembangkan untuk peluru kendali (''guided missile'') dan sekarang banyak digunakan untuk banyak aplikasi, termasuk Blackberry, Symbian, iOS dan [[sistem operasi]] [[Android]] operating systems. Untuk informasi lebih lanjut tentang [[sqlite]] dapat dilihat di situs http://www.sqlite.org
  
 
==Mengedit database di Sqlite3==
 
==Mengedit database di Sqlite3==
  
Ada beberapa metoda yang dapat digunakan untuk mengedit dan melihat file OpenBTS sqlite3 database, yaitu,
+
Ada beberapa metoda yang dapat digunakan untuk mengedit dan melihat file database sqlite3 [[OpenBTS]] sqlite3, yaitu,
  
* Sqlite3 command line tool. Access Point Range Network membawa serta sqlite3 command line tool yang dapat digunakan untuk melihat dan memodifikasi database yang ada menggunakan sintaks SQL.
+
* Sqlite3 tool command line. Access Point Range Network membawa serta sqlite3 tool command line yang dapat digunakan untuk melihat dan memodifikasi [[database]] yang ada menggunakan sintaks SQL.
 +
** [[database]] dapat dimanipulasi secara langsung menggunakan sintaks [[SQL]] secara [[realtime]].
 +
** Untuk editing secara offline, sqlite3 dapat mengexport kode [[SQL]] ke text file menggunakan ".dump". Setelah di edit, dapat di import kembali menggunakan ".read".
  
** database dapat dimanipulasi secara langsung menggunakan sintaks SQL secara realtime.
+
* Menggunakan editor database pihak lain. Ada beberapa GUI database editor yang tersedia untuk file database sqlite3, contoh:  
** Untuk editing secara offline, sqlite3 da[at mengexport kode SQL ke text file menggunakan ".dump". Setelah di edit, dapat di import kembali menggunakan ".read".
+
** “SQLite Database Browser” – Free browser untuk OS X & Linux tersedia dari sourceforge.net.
 
+
** “RazorSQL” – [[database]] [[GUI]] komersial tersedia dari razorsql.com.
 
+
** Firefox – Mozilla menawarkan add-on Firefox gratis yang di namakan SQLite Manager yang memungkinkan Firefox web browser untuk digunakan untuk melihat dan mengedit database sqlite3, tersedia dari addons.mozilla.org.
* Menggunakan editor database pihak lain.  
 
• Third-party database editors. Generic GUI-based editors are available for sqlite3 database files.
 
Examples:
 
“SQLite Database Browser” – A free browser for OS X and Linux available from sourceforge.net.
 
“RazorSQL” – A commercial database GUI available from razorsql.com.
 
Firefox – Mozilla offers a free Firefox add-on called SQLite Manager that allows the Firefox web
 
browser to be used to view and edit sqlite3 databases, available from addons.mozilla.org.
 
  
 
* Melalui OpenBTS sendiri. Perintah OpenBTS CLI "config" dan "unconfig" dapat digunakan untuk mengedit tabel konfigurasi secara realtime. Perubahan konfigurasi melalui CLI akan di tulis ke database OpenBTS.db dan akan persistent.
 
* Melalui OpenBTS sendiri. Perintah OpenBTS CLI "config" dan "unconfig" dapat digunakan untuk mengedit tabel konfigurasi secara realtime. Perubahan konfigurasi melalui CLI akan di tulis ke database OpenBTS.db dan akan persistent.
Line 23: Line 18:
 
==Tabel Konfigurasi==
 
==Tabel Konfigurasi==
  
The parameters that control the OpenBTS application are stored in a database table called the configura-
+
Parameter yang mengontrol aplikasi OpenBTS di simpan dalam tabel database yang di sebut configuration table.
tion table. Some parameters are dynamic, meaning that a parameter change will have an immediate effec.
+
Beberapa parameter ada yang dynamic, artinya jika parameter tersebut di ubah maka akan menimbulkan effek secara langsung.
 
+
Beberapa parameter lainnya sifatnya statik dan perubahan pada parameter ini tidak akan menimbulkan effek sampai [[OpenBTS]] di restart.
24
+
Beberapa parameter ada yang sifatnya statik dan match ke hardware yang spesifik dan sebaiknya tidak diubah sama sekali.
4.2. THE CONFIGURATION TABLE
+
Comment dalam database konfigurasi menjelaskan setiap parameter dan untuk kondisi apa parameter tersebut bisa di ubah.
25
+
Flag dalam database schema menunjukan parameter mana yang statik.
Some of these parameters are static and changes to them do not take effect until OpenBTS is restarted.
+
Schema untuk tabel konfigurasi di P2.8 adalah:
Some of these static parameters are matched to the hardware of a specific implementation and should not
 
be changed at all. Comments within the configuration database describe each parameter and under what
 
conditions it can be changed. Flags within the database schema indicate which parameters are static. The
 
schema for the P2.8 configuration table is:
 
  
 
  CREATE TABLE CONFIG (
 
  CREATE TABLE CONFIG (
Line 43: Line 34:
 
   )
 
   )
  
Note that the database itself contains comments, available to the operator at all times and repeated in this
+
Perhatian bahwa database itu sendiri berisi comment, tersedia untuk operator setiap waktu. Comment ini akan dijelaskan lebih lanjut di manual ini.
manual.
 
To change a dynamic configuration parameter in real time, edit the table using one of the methods described
 
in Section 4.1. The effect will be immediate, although in-progress transactions may continue to use the
 
parameters with which they started. (For example, a change in SIP.Proxy.Speech will not affect in-progress
 
telephone calls, but any new calls will use the new proxy.)
 
To change a static configuration parameter. edit the table using one of the methods described in Section 4.1
 
and then restart the OpenBTS application. In standard-configuration embedded Linux systems, this restart
 
can be accomplished with the “exit” command, described in Section 5.5.8 or by rebooting the BTS unit.
 
In some cases, NULL is a valid value for a configuration parameter. In SQL terminology, the NULL value
 
is a special tag that indicates that a value is not defined. This is not the same as the string “NULL”,
 
which is an actual string value with a value of “NULL”. To make a value NULL from the CLI, use the
 
“unconfig” command.
 
The configuration parameters are listed here briefly, but some parameters of particular importance are
 
covered in later sections.
 
• CLI.Prompt – Prompt for the OpenBTS command line interface.
 
• Control.Emergency.Destination.Host – SIP destination host to be used for the ”To:” header of emer-
 
gency calls. This host may be different from the address given for SIP.Proxy.Emergency.
 
• Control.Emergency.Destination.User – SIP destination user or extension to be used for the ”To:”
 
header of emegency calls. IMS specifies ”sos”, but correct value must be matched to your switch
 
configuration and PSAP interface.
 
• Control.Emergency.GatewaySwitch – Gateway SIP switch for inbound calls from other networks.
 
This host is used to form the return path for emergency calls, so it should be a host address that will
 
route from your serving PSAP.
 
• Control.Emergency.Geolocation – If defined, send this location as an RFC-4119 XML GEOPRIV
 
object during SIP emergency call establishment. Format is dd:mm:ss[NS] ddd:dd:dd[EW].
 
• Control.Emergency.QueueTime – Maximum time to wait for a channel to open up for an emegency
 
call in a congested system, in milliseconds.
 
26
 
  
CHAPTER 4. EXTERNAL DATABASES
+
Untuk mengubah sebuah parameter konfigurasi yang dynamic secara real time, kita dapat mengedit tabel menggunakan cara yang di jelaskan di atas.
• Control.Emergency.RFC5031 – If not NULL, use the RFC-5031 URN sip:sos@SIP.Proxy.Emergency
+
Effek yang terjadi akan langsung di rasakan, walaupun transaksi yang sedang berjalan akan tetap menggunakan parameter yang diset waktu memulai transaksi. Contoh, perubahaan pada parameter SIP.Proxy.Speech tidak akan memberikan effek ke sambungan telepon yang sedang in-progress, tapi call yang baru akan menggunakan proxy yang baru.
as the request URN for outbound emergency calls over SIP, regardless of the value of Emergency.Destination.User.
 
The ”To:” header will still be Emergency.Destination.User@Emergency.Destination.Host.
 
• Control.Emergency.Source.User – SIP identity to use if no IMSI is available. IMS specifies ”anony-
 
mous” but other values might be more useful depending on your configuration.
 
• Control.GSMTAP.TargetIP – Target IP address for GSMTAP packets; the IP address of Wireshark,
 
if you use it for GSM.
 
• Control.LUR.AttachDetach – Attach/detach flag. Set to 1 to use attach/detach procedure, 0 other-
 
wise. This will make initial LUR more prompt. It will also cause an un-regstration if the handset
 
powers off and really heavy LUR loads in areas with spotty coverage.
 
• Control.LUR.CachedAuthentication – If not NULL, use RAND-SRES pairs cached in the TMSI
 
table for authentication. If this method is used, it is important that the TMSI Table be in persistent
 
storage.
 
• Control.LUR.DefaultAuthenticationAccept – If not NULL, provisioned handsets will be accepted for
 
authentication in the absence of any defined authentication method. For commercial networks this
 
value should probably be NULL.
 
• Control.LUR.FailedRegistration.Message – If defined, send this text message, followed by the IMSI,
 
to unprovisioned handsets that are denied registration.
 
• Control.LUR.FailedRegistration.ShortCode – The return address for the failed registration message.
 
If the message is defined, this must also be defined.
 
• Control.LUR.NormalRegistration.Message – If defined, send this text message, followed by the IMSI,
 
to provisioned handsets when they attach on Um.
 
• Control.LUR.NormalRegistration.ShortCode – The return address for the normal registration mes-
 
sage. If the message is defined, this must also be defined.
 
• Control.LUR.OpenRegistration – A regular expression. If not NULL, allow unprovisioned handsets
 
with matching IMSIs to attach in Um.
 
• Control.LUR.OpenRegistration.Message – If defined, send this text message, followed by the IMSI,
 
to unprovisioned handsets when they attach on Um due to open registration.
 
• Control.LUR.OpenRegistration.ShortCode – The return address for the open registration message.
 
If the message is defined, this must also be defined.
 
• Control.LUR.QueryClassmark – If not NULL, query every MS for classmark during LUR.
 
• Control.LUR.QueryIMEI – If not NULL, query every MS for IMSI during LUR.
 
• Control.LUR.SR-HTTPAuthentication – If not NULL, use the HTTP interface of the subscriber
 
registry server for authentication.
 
• Control.LUR.SendTMSIs – If not NULL, send new TMSI assignments to handsets that are allowed
 
to attach.
 
  
4.2. THE CONFIGURATION TABLE
+
Untuk mengubah parameter konfigurasi statik, edit tabel menggunakan salah satu metoda yang di jelaskan di atas kemudian restart aplikasi OpenBTS.
27
+
Dalam Linux embedded system yang standard, restart ini dapat di peroleh dengan perintah "exit", atau dengan cara me-reboot BTS tersebut.
• Control.LUR.UnprovisionedRejectCause – Reject cause for location updating failures for unprovi-
 
sioned phones. Reject causes come from GSM 04.08 10.5.3.6. Reject cause 0x04, IMSI not in VLR,
 
is usually the right one.
 
• Control.NumSQLTries – Number of times to retry SQL queries before declaring a database access
 
failure.
 
• Control.Reporting.PhysStatusTable – File path for channel status reporting database. Static.
 
• Control.Reporting.TMSITable – File path for TMSITable database. Static.
 
• Control.TMSITable.MaxAge – Maximum allowed age for a TMSI in hours.
 
• Control.TMSITable.MaxSize – Maximum size of TMSI table before oldest TMSIs are discarded.
 
• Control.TestCall.Port – Port for exchanging L3 packets with the testcall feature.
 
• Control.VEA – If not NULL, user very early assignment for speech call establishment. See GSM 04.08
 
Section 7.3.2 for a detailed explanation of assignment types. If VEA is selection, GSM.CellSelection.NECI
 
should be set to 1. See GSM 04.08 Sections 9.1.8 and 10.5.2.4 for an explanation of the NECI bit.
 
• GSM.CCCH.AGCH.QMax – Maximum number of access grants to be queued for transmission on
 
AGCH before declaring congrestion.
 
• GSM.CCCH.CCCH-CONF – CCCH configuration type. See GSM 10.5.2.11 for encoding. Value of
 
1 means we are using a C-V beacon. Any other value selects a C-IV beacon.
 
• GSM.CCCH.PCH.Reserve – Number of CCCH subchannels to reserve for paging.
 
• GSM.CellSelection.CELL-RESELECT-HYSTERESIS – Cell Reselection Hysteresis. See GSM 04.08
 
10.5.2.4, Table 10.5.23 for encoding. Encoding is 2N dB, values of N are 0...7 for 0...14 dB.
 
• GSM.CellSelection.MS-TXPWR-MAX-CCH – Cell selection parameters. See GSM 04.08 10.5.2.4.
 
• GSM.CellSelection.NCCsPermitted – NCCs Permitted. An 8-bit mask of allowed NCCs. Unless you
 
are coordinating with another carrier, this should probably just select your own NCC.
 
• GSM.CellSelection.NECI – NECI, New Establishment Causes. This must be set to ”1” if you want
 
to support very early assignment. See GSM 04.08 10.5.2.4, Table 10.5.23 and 04.08 9.1.8, Table 9.9.
 
• GSM.CellSelection.Neighbors – ARFCNs of neighboring cells.
 
• GSM.CellSelection.RXLEV-ACCESS-MIN – Cell selection parameters. See GSM 04.08 10.5.2.4.
 
• GSM.Channels.C1sFirst – If not NULL, allocate C-I slots first, starting at C0T1. Otherwise, allocate
 
C-VII slots first. Static.
 
• GSM.Channels.NumC1s – Number of Combination-I timeslots to configure. The C-I slot carries a
 
single full-rate TCH, used for speech calling. Static.
 
• GSM.Channels.NumC7s – Number of Combination-VII timeslots to configure. The C-VII slot carries
 
8 SDCCHs, useful to handle high registration loads or SMS. If C0T0 is C-IV, you must have at least
 
one C-VII also. Static.
 
28
 
  
CHAPTER 4. EXTERNAL DATABASES
+
Dalam beberapa kasus, NULL adalah nilai yang valid untuk sebuha parameter konfigurasi.
• GSM.Identity.BSIC.BCC GSM basestation color code; lower 3 bits of the BSIC. BCC values in a
+
Dalam terminologi SQL, nilai NULL adalah sebuah tag khusus yang menunjukan bahwa nilai tersebut tidak terdefinisi.Ini tidak sama dengan sebuah string "NULL", yang merupakan sebuah string yang berisi "NULL".
multi-BTS network should be assigned so that BTS units with overlapping coverage do not share a
+
Untuk membuat nilai NULL dari CLI, gunaan perintah "unconfig".
BCC. This value will also select the training sequence used for all slots on this unit.
+
 
• GSM.Identity.BSIC.NCC GSM network color code; upper 3 bits of the BSIC. Assigned by your
+
Daftar Parameter konfigurasi secara umum terlampir di bawaj ini, beberapa parameter yang penting akan di jelaskan di bagian yang lain,
national regulator. Must be distinct from NCCs of other GSM operators in your area.
+
 
• GSM.Identity.CI – Cell ID, 16 bits. Should be unique.
+
* CLI.Prompt Prompt for the OpenBTS command line interface.
• GSM.Identity.LAC Location area code, 16 bits, values 0xFFxx are reserved. For multi-BTS net-
+
* Control.Emergency.Destination.Host – SIP destination host to be used for the ”To:” header of emergency calls. This host may be different from the address given for SIP.Proxy.Emergency.
works, assign a unique LAC to each BTS unit. (That is not the normal procedure in conventional
+
* Control.Emergency.Destination.User SIP destination user or extension to be used for the ”To:” header of emegency calls. IMS specifies ”sos”, but correct value must be matched to your switch configuration and PSAP interface.
GSM networks, but is the correct procedure in OpenBTS networks.)
+
* Control.Emergency.GatewaySwitch – Gateway SIP switch for inbound calls from other networks. This host is used to form the return path for emergency calls, so it should be a host address that will route from your serving PSAP.
• GSM.Identity.MCC Mobile country code, 2 or 3 digits. Defined in ITU-T E.212.
+
* Control.Emergency.Geolocation If defined, send this location as an RFC-4119 XML GEOPRIV object during SIP emergency call establishment. Format is dd:mm:ss[NS] ddd:dd:dd[EW].
• GSM.Identity.MNC – Mobile network code; Must be 3 dgits. Assigned by your national regulator.
+
* Control.Emergency.QueueTime – Maximum time to wait for a channel to open up for an emegency call in a congested system, in milliseconds.
• GSM.Identity.ShortName Network short name, displayed on some phones. Optional but must be
+
* Control.Emergency.RFC5031 If not NULL, use the RFC-5031 URN sip:sos@SIP.Proxy.Emergency as the request URN for outbound emergency calls over SIP, regardless of the value of Emergency.Destination.User. The ”To:” header will still be Emergency.Destination.User@Emergency.Destination.Host.
defined if you also want the network to send time-of-day.
+
* Control.Emergency.Source.User SIP identity to use if no IMSI is available. IMS specifies ”anonymous” but other values might be more useful depending on your configuration.
• GSM.Identity.ShowCountry If not NULL, tell the phone to show the country name based on the
+
* Control.GSMTAP.TargetIP Target IP address for GSMTAP packets; the IP address of Wireshark, if you use it for GSM.
MCC.
+
* Control.LUR.AttachDetach – Attach/detach flag. Set to 1 to use attach/detach procedure, 0 otherwise. This will make initial LUR more prompt. It will also cause an un-regstration if the handset powers off and really heavy LUR loads in areas with spotty coverage.
• GSM.MS.Power.Damping – Damping value for MS power control loop.
+
* Control.LUR.CachedAuthentication If not NULL, use RAND-SRES pairs cached in the TMSI table for authentication. If this method is used, it is important that the TMSI Table be in persistent storage.
• GSM.MS.Power.Max Maximum commanded MS power level in dBm.
+
* Control.LUR.DefaultAuthenticationAccept If not NULL, provisioned handsets will be accepted for authentication in the absence of any defined authentication method. For commercial networks this value should probably be NULL.
• GSM.MS.Power.Min Minimum commanded MS power level in dBm.
+
* Control.LUR.FailedRegistration.Message If defined, send this text message, followed by the IMSI, to unprovisioned handsets that are denied registration.
• GSM.MS.TA.Damping Damping value for timing advance control loop.
+
* Control.LUR.FailedRegistration.ShortCode The return address for the failed registration message. If the message is defined, this must also be defined.
• GSM.MS.TA.Max Maximum allowed timing advance in symbol periods. Ignore RACH bursts with
+
* Control.LUR.NormalRegistration.Message If defined, send this text message, followed by the IMSI, to provisioned handsets when they attach on Um.
delays greater than this. Can be used to limit service range.
+
* Control.LUR.NormalRegistration.ShortCode The return address for the normal registration message. If the message is defined, this must also be defined.
• GSM.MaxSpeechLatency Maximum allowed speech buffering latency, in 20 ms frames. If the jitter
+
* Control.LUR.OpenRegistration – A regular expression. If not NULL, allow unprovisioned handsets with matching IMSIs to attach in Um.
is larger than this delay, frames will be lost.
+
* Control.LUR.OpenRegistration.Message If defined, send this text message, followed by the IMSI, to unprovisioned handsets when they attach on Um due to open registration.
• GSM.RACH.AC Access class flags. This is the raw parameter sent on the BCCH. See GSM 04.08
+
* Control.LUR.OpenRegistration.ShortCode – The return address for the open registration message. If the message is defined, this must also be defined.
10.5.2.29 for encoding. Set to 0 to allow full access. If you do not have proper PSAP integration, set
+
* Control.LUR.QueryClassmark – If not NULL, query every MS for classmark during LUR.
to 0x0400 to indicate no support for emergency calls.
+
* Control.LUR.QueryIMEI If not NULL, query every MS for IMSI during LUR.
• GSM.RACH.MaxRetrans Maximum RACH retransmission attempts. This is the raw parameter
+
* Control.LUR.SR-HTTPAuthentication – If not NULL, use the HTTP interface of the subscriber registry server for authentication.
sent on the BCCH. See GSM 04.08 10.5.2.29 for encoding.
+
* Control.LUR.SendTMSIs If not NULL, send new TMSI assignments to handsets that are allowed to attach.
• GSM.RACH.TxInteger Parameter to spread RACH busts over time. This is the raw parameter
+
* Control.LUR.UnprovisionedRejectCause – Reject cause for location updating failures for unprovisioned phones. Reject causes come from GSM 04.08 10.5.3.6. Reject cause 0x04, IMSI not in VLR, is usually the right one.
sent on the BCCH. See GSM 04.08 10.5.2.29 for encoding.
+
* Control.NumSQLTries Number of times to retry SQL queries before declaring a database access failure.
• GSM.RADIO-LINK-TIMEOUT L1 radio link timeout. This is the raw parameter sent on the
+
* Control.Reporting.PhysStatusTable – File path for channel status reporting database. Static.
BCCH; see GSM 10.5.2.3 for encoding. Should be coordinated with T3109.
+
* Control.Reporting.TMSITable – File path for TMSITable database. Static.
• GSM.RRLP.ACCURACY Requested accuracy of location request. K in 10(1.1**K-1). See 3GPP
+
* Control.TMSITable.MaxAge Maximum allowed age for a TMSI in hours.
03.32, sect 6.2
+
* Control.TMSITable.MaxSize Maximum size of TMSI table before oldest TMSIs are discarded.
• GSM.RRLP.ALMANAC.REFRESH.TIME How often the almanac is refreshed, in hours
+
* Control.TestCall.Port – Port for exchanging L3 packets with the testcall feature.
4.2. THE CONFIGURATION TABLE
+
* Control.VEA If not NULL, user very early assignment for speech call establishment. See GSM 04.08 Section 7.3.2 for a detailed explanation of assignment types. If VEA is selection, GSM.CellSelection.NECI should be set to 1. See GSM 04.08 Sections 9.1.8 and 10.5.2.4 for an explanation of the NECI bit.
29
+
* GSM.CCCH.AGCH.QMax Maximum number of access grants to be queued for transmission on AGCH before declaring congrestion.
• GSM.RRLP.ALMANAC.URL URL of almanac source.
+
* GSM.CCCH.CCCH-CONF CCCH configuration type. See GSM 10.5.2.11 for encoding. Value of 1 means we are using a C-V beacon. Any other value selects a C-IV beacon.
• GSM.RRLP.EPHEMERIS.REFRESH.TIME How often the ephemeris is refreshed, in hours.
+
* GSM.CCCH.PCH.Reserve Number of CCCH subchannels to reserve for paging.
GSM.RRLP.EPHEMERIS.URL – URL of ephemeris source.
+
* GSM.CellSelection.CELL-RESELECT-HYSTERESIS Cell Reselection Hysteresis. See GSM 04.08 10.5.2.4, Table 10.5.23 for encoding. Encoding is 2N dB, values of N are 0...7 for 0...14 dB.
GSM.RRLP.RESPONSETIME – Mobile timeout. (OpenBTS timeout is 130 sec = max response
+
* GSM.CellSelection.MS-TXPWR-MAX-CCH – Cell selection parameters. See GSM 04.08 10.5.2.4.
time + 2.) N in 2**N. See 3GPP 04.31 sect A.2.2.1
+
* GSM.CellSelection.NCCsPermitted NCCs Permitted. An 8-bit mask of allowed NCCs. Unless you are coordinating with another carrier, this should probably just select your own NCC.
GSM.RRLP.SEED.ALTITUDE Seed altitude in meters wrt geoidal surface.
+
* GSM.CellSelection.NECI – NECI, New Establishment Causes. This must be set to ”1” if you want to support very early assignment. See GSM 04.08 10.5.2.4, Table 10.5.23 and 04.08 9.1.8, Table 9.9.
GSM.RRLP.SEED.LATITUDE Seed latitude in degrees. -90 (south pole) .. +90 (north pole)
+
* GSM.CellSelection.Neighbors – ARFCNs of neighboring cells.
• GSM.RRLP.SEED.LONGITUDE – Seed longitude in degrees. -180 (west of greenwich) .. 180 (east)
+
* GSM.CellSelection.RXLEV-ACCESS-MIN Cell selection parameters. See GSM 04.08 10.5.2.4.
GSM.RRLP.SERVER.URL URL of RRLP server.
+
* GSM.Channels.C1sFirst If not NULL, allocate C-I slots first, starting at C0T1. Otherwise, allocate C-VII slots first. Static.
GSM.Radio.Band The GSM operating band. Valid values are 850 (GSM850), 900 (PGSM900), 1800
+
* GSM.Channels.NumC1s Number of Combination-I timeslots to configure. The C-I slot carries a single full-rate TCH, used for speech calling. Static.
(DCS1800) and 1900 (PCS1900). For most Range models, this value is dictated by the hardware and
+
* GSM.Channels.NumC7s – Number of Combination-VII timeslots to configure. The C-VII slot carries 8 SDCCHs, useful to handle high registration loads or SMS. If C0T0 is C-IV, you must have at least one C-VII also. Static.
should not be changed. Static.
+
* GSM.Identity.BSIC.BCC GSM basestation color code; lower 3 bits of the BSIC. BCC values in a multi-BTS network should be assigned so that BTS units with overlapping coverage do not share a BCC. This value will also select the training sequence used for all slots on this unit.
• GSM.Radio.C0 – The C0 ARFCN. Static.
+
* GSM.Identity.BSIC.NCC – GSM network color code; upper 3 bits of the BSIC. Assigned by your national regulator. Must be distinct from NCCs of other GSM operators in your area.
GSM.Radio.MaxExpectedDelaySpread Expected worst-case delay spread in symbol periods, roughly
+
* GSM.Identity.CI Cell ID, 16 bits. Should be unique.
3.7 us or 1.1 km per unit.
+
* GSM.Identity.LAC Location area code, 16 bits, values 0xFFxx are reserved. For multi-BTS networks, assign a unique LAC to each BTS unit. (That is not the normal procedure in conventional GSM networks, but is the correct procedure in OpenBTS networks.)
GSM.Radio.PowerManager.MaxAttenDB – Maximum transmitter attenuation level, in dB wrt full
+
* GSM.Identity.MCC – Mobile country code, 2 or 3 digits. Defined in ITU-T E.212.
scale on the D/A output. This sets the minimum power output level in the output power control
+
* GSM.Identity.MNC Mobile network code; Must be 3 dgits. Assigned by your national regulator.
loop.
+
* GSM.Identity.ShortName Network short name, displayed on some phones. Optional but must be defined if you also want the network to send time-of-day.
GSM.Radio.PowerManager.MinAttenDB – Minimum transmitter attenuation level, in dB wrt full
+
* GSM.Identity.ShowCountry If not NULL, tell the phone to show the country name based on the MCC.
scale on the D/A output. This sets the maximum power output level in the output power control
+
* GSM.MS.Power.Damping Damping value for MS power control loop.
loop.
+
* GSM.MS.Power.Max Maximum commanded MS power level in dBm.
GSM.Radio.PowerManager.NumSamples Number of samples averaged by the output power control
+
* GSM.MS.Power.Min Minimum commanded MS power level in dBm.
loop.
+
* GSM.MS.TA.Damping Damping value for timing advance control loop.
GSM.Radio.PowerManager.SamplePeriod – Sample period for the output power control loop.
+
* GSM.MS.TA.Max – Maximum allowed timing advance in symbol periods. Ignore RACH bursts with delays greater than this. Can be used to limit service range.
GSM.Radio.PowerManager.TargetT3122 Target value for T3122, the random access hold-off timer,
+
* GSM.MaxSpeechLatency Maximum allowed speech buffering latency, in 20 ms frames. If the jitter is larger than this delay, frames will be lost.
for the power control loop.
+
* GSM.RACH.AC 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. If you do not have proper PSAP integration, set to 0x0400 to indicate no support for emergency calls.
GSM.Radio.RSSITarget Target uplink RSSI for MS power control loop, in dB wrt to A/D full scale.
+
* GSM.RACH.MaxRetrans Maximum RACH retransmission attempts. This is the raw parameter sent on the BCCH. See GSM 04.08 10.5.2.29 for encoding.
Should be 6-10 dB above the noise floor.
+
* GSM.RACH.TxInteger 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.Radio.RxGain Receiver gain setting in dB. Ideal value is dictacted by the hardware. This
+
* GSM.RADIO-LINK-TIMEOUT L1 radio link timeout. This is the raw parameter sent on the BCCH; see GSM 10.5.2.3 for encoding. Should be coordinated with T3109.
database parameter is static but the receiver gain can be modified in real time with the CLI rxgain
+
* GSM.RRLP.ACCURACY Requested accuracy of location request. K in 10(1.1**K-1). See 3GPP 03.32, sect 6.2
command. Static.
+
* GSM.RRLP.ALMANAC.REFRESH.TIME How often the almanac is refreshed, in hours
GSM.Timer.T3113 – Paging timer T3113 in ms. This is the timeout for a handset to respond to a
+
* GSM.RRLP.ALMANAC.URL – URL of almanac source.
paging request. This should usually be the same as SIP.Timer.B in your VoIP network.
+
* GSM.RRLP.EPHEMERIS.REFRESH.TIME How often the ephemeris is refreshed, in hours.
GSM.Timer.T3122Max Maximum allowed value for T3122, the RACH holdoff timer, in milliseconds.
+
* GSM.RRLP.EPHEMERIS.URL – URL of ephemeris source.
GSM.Timer.T3122Min Minimum allowed value for T3122, the RACH holdoff timer, in milliseconds.
+
* GSM.RRLP.RESPONSETIME Mobile timeout. (OpenBTS timeout is 130 sec = max response time + 2.) N in 2**N. See 3GPP 04.31 sect A.2.2.1
30
+
* GSM.RRLP.SEED.ALTITUDE Seed altitude in meters wrt geoidal surface.
CHAPTER 4. EXTERNAL DATABASES
+
* GSM.RRLP.SEED.LATITUDE Seed latitude in degrees. -90 (south pole) .. +90 (north pole)
GSM.Timer.T3212 – Registration timer T3212 period in minutes. Should be a factor of 6. Set to 0
+
* GSM.RRLP.SEED.LONGITUDE Seed longitude in degrees. -180 (west of greenwich) .. 180 (east)
to disable periodic registration. Should be smaller than SIP registration period.
+
* GSM.RRLP.SERVER.URL URL of RRLP server.
• Log.Alarms.Max Maximum number of alarms to remember inside the application.
+
* GSM.Radio.Band The GSM operating band. Valid values are 850 (GSM850), 900 (PGSM900), 1800 (DCS1800) and 1900 (PCS1900). For most Range models, this value is dictated by the hardware and should not be changed. Static.
• Log.Level – Default logging level when no other level is defined for a file.
+
* GSM.Radio.C0 The C0 ARFCN. Static.
• Log.Level.CallControl.cpp Default configuration logs a trace at L3.
+
* GSM.Radio.MaxExpectedDelaySpread Expected worst-case delay spread in symbol periods, roughly 3.7 us or 1.1 km per unit.
• Log.Level.MobilityManagement.cpp Default configuration logs a trace at L3.
+
* GSM.Radio.PowerManager.MaxAttenDB Maximum transmitter attenuation level, in dB wrt full scale on the D/A output. This sets the minimum power output level in the output power control loop.
• Log.Level.RadioResource.cpp Default configuration logs a trace at L3.
+
* GSM.Radio.PowerManager.MinAttenDB – Minimum transmitter attenuation level, in dB wrt full scale on the D/A output. This sets the maximum power output level in the output power control loop.
• Log.Level.SMSControl.cpp Default configuration logs a trace at L3.
+
* GSM.Radio.PowerManager.NumSamples Number of samples averaged by the output power control loop.
• NTP.Server NTP server(s) for time-of-day clock syncing. For multiple servers, use a space-delimited
+
* GSM.Radio.PowerManager.SamplePeriod Sample period for the output power control loop.
list. If left undefined, NTP will not be used, but it is strongly recommended.
+
* GSM.Radio.PowerManager.TargetT3122 Target value for T3122, the random access hold-off timer, for the power control loop.
• RTP.Range Range of RTP port pool. Pool is RTP.Start to RTP.Range-1. Static.
+
* GSM.Radio.RSSITarget Target uplink RSSI for MS power control loop, in dB wrt to A/D full scale. Should be 6-10 dB above the noise floor.
• RTP.Start – Base of RTP port pool. Pool is RTP.Start to RTP.Range-1. Static.
+
* GSM.Radio.RxGain Receiver gain setting in dB. Ideal value is dictacted by the hardware. This database parameter is static but the receiver gain can be modified in real time with the CLI rxgain command. Static.
• SIP.DTMF.RFC2833 If not NULL, use RFC-2833 (RTP event signalling) for in-call DTMF.
+
* GSM.Timer.T3113 Paging timer T3113 in ms. This is the timeout for a handset to respond to a paging request. This should usually be the same as SIP.Timer.B in your VoIP network.
• SIP.DTMF.RFC2833.PayloadType Payload type to use for RFC-2833 telephone event packets. If
+
* GSM.Timer.T3122Max Maximum allowed value for T3122, the RACH holdoff timer, in milliseconds.
SIP.DTMF.2833 is defined, this must also be defined.
+
* GSM.Timer.T3122Min – Minimum allowed value for T3122, the RACH holdoff timer, in milliseconds.
• SIP.DTMF.RFC2967 – If not NULL, use RFC-2967 (SIP INFO method) for in-call DTMF.
+
* GSM.Timer.T3212 – Registration timer T3212 period in minutes. Should be a factor of 6. Set to 0 to disable periodic registration. Should be smaller than SIP registration period.
• SIP.Local.IP IP address of the OpenBTS machine as seen by its proxies. If these are all local, this
+
* Log.Alarms.Max – Maximum number of alarms to remember inside the application.
can be localhost. Static.
+
* Log.Level – Default logging level when no other level is defined for a file.
• SIP.Local.Port IP port that OpenBTS uses for its SIP interface. Static.
+
* Log.Level.CallControl.cpp – Default configuration logs a trace at L3.
• SIP.MaxForwards – Maximum allowed number of referrals.
+
* Log.Level.MobilityManagement.cpp – Default configuration logs a trace at L3.
• SIP.Proxy.Emergency – The IP host and port of the proxy to be used for emergency calls.
+
* Log.Level.RadioResource.cpp – Default configuration logs a trace at L3.
• SIP.Proxy.Registration The IP host and port of the proxy to be used for registration and authen-
+
* Log.Level.SMSControl.cpp – Default configuration logs a trace at L3.
tication. This is the subscriber registry, for example.
+
* NTP.Server – NTP server(s) for time-of-day clock syncing. For multiple servers, use a space-delimited list. If left undefined, NTP will not be used, but it is strongly recommended.
• SIP.Proxy.SMS – The IP host and port of the proxy to be used for text messaging. This is smqueue,
+
* RTP.Range – Range of RTP port pool. Pool is RTP.Start to RTP.Range-1. Static.
for example.
+
* RTP.Start – Base of RTP port pool. Pool is RTP.Start to RTP.Range-1. Static.
• SIP.Proxy.Speech The IP host and port of the proxy to be used for normal speech calls. This is
+
* SIP.DTMF.RFC2833 – If not NULL, use RFC-2833 (RTP event signalling) for in-call DTMF.
Asterisk, for example.
+
* SIP.DTMF.RFC2833.PayloadType – Payload type to use for RFC-2833 telephone event packets. If SIP.DTMF.2833 is defined, this must also be defined.
• SIP.RegistrationPeriod – Registration period in minutes for MS SIP users. Should be longer than
+
* SIP.DTMF.RFC2967 – If not NULL, use RFC-2967 (SIP INFO method) for in-call DTMF.
GSM T3212.
+
* SIP.Local.IP – IP address of the OpenBTS machine as seen by its proxies. If these are all local, this can be localhost. Static.
• SIP.SMSC The SMSC handler in smqueue. This is the entity that handles full 3GPP MIME-
+
* SIP.Local.Port – IP port that OpenBTS uses for its SIP interface. Static.
encapsulted TPDUs. If not defined, use direct numeric addressing. Normally the value is NULL if
+
* SIP.MaxForwards – Maximum allowed number of referrals.
SMS.MIMIEType is ”text/plain” or ”smsc” if SMS.MIMEType is ”application/vnd.3gpp”.
+
* SIP.Proxy.Emergency – The IP host and port of the proxy to be used for emergency calls.
• SIP.Timer.A INVITE retransmit period in ms.
+
* SIP.Proxy.Registration – The IP host and port of the proxy to be used for registration and authentication. This is the subscriber registry, for example.
4.3. TMSI TABLE
+
* SIP.Proxy.SMS – The IP host and port of the proxy to be used for text messaging. This is smqueue,for example.
31
+
* SIP.Proxy.Speech – The IP host and port of the proxy to be used for normal speech calls. This is Asterisk, for example.
• SIP.Timer.B INVITE transaction timeout in ms. This value should usually match GSM.Timer.T3113.
+
* SIP.RegistrationPeriod – Registration period in minutes for MS SIP users. Should be longer than GSM T3212.
• SIP.Timer.E Non-INVITE initial request retransmit period in ms.
+
* SIP.SMSC – The SMSC handler in smqueue. This is the entity that handles full 3GPP MIME-encapsulted TPDUs. If not defined, use direct numeric addressing. Normally the value is NULL if SMS.MIMIEType is ”text/plain” or ”smsc” if SMS.MIMEType is ”application/vnd.3gpp”.
• SIP.Timer.F Non-INVITE initial request timeout in ms.
+
* SIP.Timer.A – INVITE retransmit period in ms.
• SIP.Timer.H ACK timeout period in ms.
+
* SIP.Timer.B – INVITE transaction timeout in ms. This value should usually match GSM.Timer.T3113.
• SIP.Timer.I ACK retransmit period in ms.
+
* SIP.Timer.E – Non-INVITE initial request retransmit period in ms.
• SIP.Timer.J Non-INVITE non-initial request retransmit period in ms.
+
* SIP.Timer.F – Non-INVITE initial request timeout in ms.
• SIP.myPort – Port used by the SIP Authentication Server
+
* SIP.Timer.H – ACK timeout period in ms.
• SMS.DefaultDestSMSC Use this to fill in L4 SMSC address in SMS submission.
+
* SIP.Timer.I – ACK retransmit period in ms.
• SMS.FakeSrcSMSC Use this to fill in L4 SMSC address in SMS delivery.
+
* SIP.Timer.J – Non-INVITE non-initial request retransmit period in ms.
• SMS.MIMEType – This is the MIME Type that OpenBTS will use for RFC-3428 SIP MESSAGE
+
* SIP.myPort – Port used by the SIP Authentication Server
payloads. Valid values are ”application/vnd.3gpp.sms” and ”text/plain”.
+
* SMS.DefaultDestSMSC – Use this to fill in L4 SMSC address in SMS submission.
• SubscriberRegistry.A3A8 URL of upstream subscriber registry server. Blank (not NULL) if there
+
* SMS.FakeSrcSMSC – Use this to fill in L4 SMSC address in SMS delivery.
is none.
+
* SMS.MIMEType – This is the MIME Type that OpenBTS will use for RFC-3428 SIP MESSAGE payloads. Valid values are ”application/vnd.3gpp.sms” and ”text/plain”.
• SubscriberRegistry.HTTP.Server URL of the subscriber registry server.
+
* SubscriberRegistry.A3A8 – URL of upstream subscriber registry server. Blank (not NULL) if there is none.
• SubscriberRegistry.Manager.Title – Title of subscriber registry database manager web page.
+
* SubscriberRegistry.HTTP.Server – URL of the subscriber registry server.
• SubscriberRegistry.Manager.Url URL of the subscriber registry database manager.
+
* SubscriberRegistry.Manager.Title – Title of subscriber registry database manager web page.
• SubscriberRegistry.Manager.VisibleColumns Field names in subscriber registry visible in the database
+
* SubscriberRegistry.Manager.Url – URL of the subscriber registry database manager.
manager.
+
* SubscriberRegistry.Manager.VisibleColumns – Field names in subscriber registry visible in the database manager.
• SubscriberRegistry.db The location of the sqlite3 database holding the subscriber registry.
+
* SubscriberRegistry.db – The location of the sqlite3 database holding the subscriber registry.
• TRX.IP IP address of the transceiver application. Static.
+
* TRX.IP – IP address of the transceiver application. Static.
• TRX.Port – IP port of the transceiver application. Static.
+
* TRX.Port – IP port of the transceiver application. Static.
• TRX.RadioFrequencyOffset Fine-tuning adjustment for the transceiver. Static.
+
* TRX.RadioFrequencyOffset – Fine-tuning adjustment for the transceiver. Static.
4.3
+
 
TMSI Table
+
==TMSI Table==
To reduce dependence on a backhaul link, OpenBTS tracks TMSIs internally. To accomplish this, OpenBTS
+
 
tracks TMSI-IMSI relationships in an sqlite3 database table called the TMSI table. TMSIs are assigned
+
Untuk mengurangi ketergantungan ke sambungan backhaul, OpenBTS men-track TMSI secara internal. Untuk memenuhi hal ini, OpenBTS men-track hubungan TMSI-IMSI menggunakan sqlite3 dalam tabel TMSI.TMSI dimasukan menggunakan nomor urut. OpenBTS mengalokasikan TMSI di tabel TMSI untuk setiap MS yang mengirimkan Location Updating Request, baik MS yang di ijinkan untuk register maupun tidak.
by a counter in increasing order. OpenBTS allocates a TMSI in the TMSI table for every MS that sends
+
Tabel TMSI akan dapat di read-write oleh OpenBTS tapi hanya read-only oleh aplikasi lain. Path dari file database yang digunakan di tabel is di definisikan di parameter konfigurasi Control.DBPath.TMSITable. Di system. tabel di simpan di partisi ramdisk biasanya standard lokasi-nya di /var/run. Schema TMSI tabel adalah:
a Location Updating Request, whether the MS is allowed to register or not.
+
 
The TMSI table is treated as read-write by OpenBTS but should be treated as read-only by other ap-
+
CREATE TABLE IF NOT EXISTS TMSI_TABLE (
plications. The path of the database file used for this table is defined in the configuration parameter
+
  TMSI INTEGER PRIMARY KEY AUTOINCREMENT -- this value is used as the TMSI
Control.DBPath.TMSITable. In flash-based systems, this table should be stored in a ramdisk partition
+
  CREATED INTEGER NOT NULL, -- Unix time of record creation
and its standard location is in /var/run. The schema is:
+
  ACCESSED INTEGER NOT NULL, -- Unix time of last encounter
32
+
  IMSI TEXT UNIQUE NOT NULL, -- IMSI of the SIM
CHAPTER 4. EXTERNAL DATABASES
+
  IMEI TEXT, -- IMEI of the MS, if requested
CREATE TABLE IF NOT EXISTS TMSI_TABLE (
+
  L3TI INTEGER DEFAULT 0, -- L3 transaction identifier last used with this MS
TMSI INTEGER PRIMARY KEY AUTOINCREMENT -- this value is used as the TMSI
+
  A5_SUPPORT INTEGER, -- encryption support in the MS, if requested
CREATED INTEGER NOT NULL, -- Unix time of record creation
+
  POWER_CLASS INTEGER, -- power class of the MS. if requested
ACCESSED INTEGER NOT NULL, -- Unix time of last encounter
+
  OLD_TMSI INTEGER, -- previous TMSI from another cell or network
IMSI TEXT UNIQUE NOT NULL, -- IMSI of the SIM
+
  PREV_MCC INTEGER, -- previous network MCC
IMEI TEXT, -- IMEI of the MS, if requested
+
  PREV_MNC INTEGER, -- previous network MNC
L3TI INTEGER DEFAULT 0, -- L3 transaction identifier last used with this MS
+
  PREV_LAC INTEGER, -- previous network LAC
A5_SUPPORT INTEGER, -- encryption support in the MS, if requested
+
  RANDUPPER INTEGER -- cached authentication token
POWER_CLASS INTEGER, -- power class of the MS. if requested
+
  RANDLOWER INTEGER -- cached authentication token
OLD_TMSI INTEGER, -- previous TMSI from another cell or network
+
  SRES INTEGER, -- cached authentication token
PREV_MCC INTEGER, -- previous network MCC
+
  DEG_LAT FLOAT, -- cached RRLP result
PREV_MNC INTEGER, -- previous network MNC
+
  DEG_LONG FLOAT -- cached RRLP result
PREV_LAC INTEGER, -- previous network LAC
+
  )
RANDUPPER INTEGER -- cached authentication token
+
 
RANDLOWER INTEGER -- cached authentication token
+
==Channel Table==
SRES INTEGER, -- cached authentication token
+
 
DEG_LAT FLOAT, -- cached RRLP result
+
OpenBTS melaporkan secara real time informasi status fisik untuk kanal yang aktif ke tabel sqlite3 external bernama PHYSTATUS. Tabel ini dilihat sebagai write-only oleh OpenBTS tapi harus dilihat sebagai read-only oleh aplikasi lainnya. Data dari channel ini akan di update setiap ada message sistem infomasi yang di terima untuk berasosiasi ke channel SACCH. Path dari file database yang digunakan di tabel ini di definisikan di parameter konfigurasi GSM.DBPath.PhysStatusTable. Schema tabel adalah:
DEG_LONG FLOAT -- cached RRLP result
+
 
)
+
CREATE TABLE IF NOT EXISTS PHYSTATUS (
4.4
+
  CN_TN_TYPE_AND_OFFSET STRING PRIMARY KEY, -- cross-refs TRANSACTION_TABLE
Channel Table
+
  ARFCN INTEGER DEFAULT NULL, -- actual ARFCN
OpenBTS reports real-time physical status information for active dedicated channels to an external sqlite3
+
  ACCESSED INTEGER DEFAULT 0, -- Unix time of last update
database table called PHYSTATUS. This table is treated as write-only by OpenBTS but should be treated
+
  RXLEV_FULL_SERVING_CELL INTEGER DEFAULT NULL, -- from most recent measurement report
as read-only by other applications. The entry for a channel is updated every time a system information
+
  RXLEV_SUB_SERVING_CELL INTEGER DEFAULT NULL, -- from most recent measurement report
message is received on the channel’s associated SACCH. The path of the database file used for this table
+
  RXQUAL_FULL_SERVING_CELL_BER FLOAT DEFAULT NULL, -- from most recent measurement report
is defined in the configuration parameter GSM.DBPath.PhysStatusTable. The schema is:
+
  RXQUAL_SUB_SERVING_CELL_BER FLOAT DEFAULT NULL, -- from most recent measurement report
CREATE TABLE IF NOT EXISTS PHYSTATUS (
+
  RSSI FLOAT DEFAULT NULL, -- RSSI relative to full scale input
CN_TN_TYPE_AND_OFFSET STRING PRIMARY KEY, -- cross-refs TRANSACTION_TABLE
+
  TIME_ERR FLOAT DEFAULT NULL, -- timing advance error in symbol periods
ARFCN INTEGER DEFAULT NULL, -- actual ARFCN
+
  TRANS_PWR INTEGER DEFAULT NULL, -- MS tx power in dBm
ACCESSED INTEGER DEFAULT 0, -- Unix time of last update
+
  TIME_ADVC INTEGER DEFAULT NULL, -- MS timing advance in symbol periods
RXLEV_FULL_SERVING_CELL INTEGER DEFAULT NULL, -- from most recent measurement report
+
  FER FLOAT DEFAULT NULL -- uplink FER
RXLEV_SUB_SERVING_CELL INTEGER DEFAULT NULL,
+
  )
-- from most recent measurement report
+
 
RXQUAL_FULL_SERVING_CELL_BER FLOAT DEFAULT NULL, -- from most recent measurement report
+
Field CN TN TYPE AND OFFSET adalah string yang menerangkan sebuah channel dalam bentuk
RXQUAL_SUB_SERVING_CELL_BER FLOAT DEFAULT NULL, -- from most recent measurement report
 
RSSI FLOAT DEFAULT NULL, -- RSSI relative to full scale input
 
TIME_ERR FLOAT DEFAULT NULL, -- timing advance error in symbol periods
 
TRANS_PWR INTEGER DEFAULT NULL, -- MS tx power in dBm
 
TIME_ADVC INTEGER DEFAULT NULL, -- MS timing advance in symbol periods
 
FER FLOAT DEFAULT NULL -- uplink FER
 
)
 
The CN TN TYPE AND OFFSET field is a channel description string of the form
 
 
C<n>T<n> <channelType>-<subchannelIndex>
 
C<n>T<n> <channelType>-<subchannelIndex>
4.4. CHANNEL TABLE
 
For example
 
• “C0T1 TCH/F” is a full rate traffic channel on timeslot 1 of the C0 ARFCN and
 
• “C0T0 SDCCH-0/4” is the #0 SDCCH (of 4 available) on C0T0.
 
Strings of the same format are used in the transaction table.
 
 
  
 +
===TABEL CHANNEL===
  
 +
Contoh
  
 +
* “C0T1 TCH/F” is a full rate traffic channel on timeslot 1 of the C0 ARFCN
 +
* “C0T0 SDCCH-0/4” is the #0 SDCCH (of 4 available) on C0T0.
  
 +
String dengan format yang sama digunakan di tabel transaction.
  
 
==Pranala Menarik==
 
==Pranala Menarik==
  
 
* [[OpenBTS]]
 
* [[OpenBTS]]
 +
* [[OpenBTS: Arsitektur secara umum]]
  
===Persiapan Hardware===
+
===Persiapan===
  
 
* [[USRP: High Precision Clock]]
 
* [[USRP: High Precision Clock]]
 +
* [[USRP: Menyambungkan ClockTamer ke USRP1]]
 +
* [[USRP: Kalibrasi ClockTamer]]
 +
* [[USRP: ClockTamer Control Protocol]]
 
* [[USRP: Instalasi Board]]
 
* [[USRP: Instalasi Board]]
 +
* [[OpenBTS: GIT Source Code]]
 +
* [[USRP: Rangkaian Board USRP]]
 +
* [[OpenBTS: Tethr untuk Bencana Alam]]
 +
* [[USRP: Tip Pemesanan]]
  
 
===OpenBTS 2.6===
 
===OpenBTS 2.6===
  
 +
* [[GNURadio]]
 
* [[GNURadio: Ubuntu Install]]
 
* [[GNURadio: Ubuntu Install]]
 +
* [[GNURadio: Menggunakan UHD]]
 +
* [[GNURadio: Ubuntu Install GNURadio 3.4.2]] '''RECOMMENDED'''
 +
* [[GNURadio: Ubuntu Install GNURadio 3.4.2 Clock 52MHz]] '''RECOMMENDED'''
 +
* [[GNURadio: Contoh Aplikasi]]
 
* [[GNURadio: Spectrum Analizer GSM]]
 
* [[GNURadio: Spectrum Analizer GSM]]
 
* [[GNURadio: Mengubah board RFX1800 menjadi RFX900]]
 
* [[GNURadio: Mengubah board RFX1800 menjadi RFX900]]
* [[OpenBTS: Ubuntu Install]]
+
* [[GNURadio: Programming Untuk Pemula]]
* [[OpenBTS: Konfigurasi]]
+
* [[OpenBTS: Ubuntu Install]] '''RECOMMENDED'''
 +
* [[OpenBTS: Ubuntu Install OpenBTS 2.6 Clock 52MHz]] '''RECOMMENDED'''
 +
* [[OpenBTS: Konfigurasi]] '''RECOMMENDED'''
 
* [[OpenBTS: Kalibrasi]]
 
* [[OpenBTS: Kalibrasi]]
* [[OpenBTS: Konfigurasi Asterisk untuk OpenBTS]]
+
* [[OpenBTS: Konfigurasi Asterisk untuk OpenBTS]] '''RECOMMENDED'''
 
* [[OpenBTS: Menjalankan smqueue]]
 
* [[OpenBTS: Menjalankan smqueue]]
* [[OpenBTS: Mengoperasikan BTS]]
+
* [[OpenBTS: Mengoperasikan BTS]] '''RECOMMENDED'''
 
* [[OpenBTS: Tampilan di Nokia saat pakai OpenBTS]]
 
* [[OpenBTS: Tampilan di Nokia saat pakai OpenBTS]]
 
* [[OpenBTS: Operasi 1800 MHz]]
 
* [[OpenBTS: Operasi 1800 MHz]]
Line 373: Line 272:
 
* [[OpenBTS: Amplifier]]
 
* [[OpenBTS: Amplifier]]
 
* [[OpenBTS: SMS]]
 
* [[OpenBTS: SMS]]
 +
* [[AirProbe]]
  
 
===OpenBTS 2.8===
 
===OpenBTS 2.8===
  
* [[GNURadio: Ubuntu 11.10 Install]]
+
* [[GNURadio: Ubuntu 11.10 Install]] ''NOT RECOMMENED''
 +
* [[GNURadio: Ubuntu 11.10 instalasi menggunakan Repo]] ''NOT RECOMMENDED''
 +
* [[GNURadio: Download GNURadio]]
 +
* [[GNURadio: Install UHD]]
 +
* [[GNURadio: Ubuntu 11.10 Instal GNURadio 3.3.0]]
 +
* [[GNURadio: Ubuntu 12.10 Instal GNURadio 3.3.0]]
 +
* [[GNURadio: Ubuntu 12.10 Instal GNURadio 3.4.1]] ''NOT RECOMMENDED''
 +
* [[GNURadio: Ubuntu 11.10 Instal GNURadio 3.4.2]] '''RECOMMENDED'''
 +
* [[GNURadio: Ubuntu 12.04 Instal GNURadio 3.4.2]] '''RECOMMENDED'''
 +
* [[GNURadio: Ubuntu 12.04.1 Instal GNURadio 3.4.2]] '''RECOMMENDED'''
 +
* [[GNURadio: Ubuntu 12.10 Instal GNURadio 3.4.2]] ''NOT RECOMMENDED''
 +
* [[GNURadio: Ubuntu 11.10 Instal GNURadio 3.5.0]] ''NOT RECOMMENDED''
 +
* [[GNURadio: Ubuntu 11.10 Instal GNURadio 3.5.3.2]] ''NOT RECOMMENDED''
 +
* [[GNURadio: Ubuntu 11.10 Instal GNURadio 3.6.0]] ''NOT RECOMMENDED''
 +
* [[GNURadio: Ubuntu 11.10 Install dari GIT GNURadio]] ''NOT RECOMMENDED''
 +
* [[GNURadio: Ubuntu 11.10 cek USRP Daughter Board]]
 +
* [[GNURadio: UHD]] ''NOT RECOMMENDED''
 +
* [[GNURadio: UHD Image]] ''NOT RECOMMENDED''
 +
* [[GNURadio: UHD burn EEPROM RFX Board di USRP1]] ''NOT RECOMMENDED''
 +
* [[GNURadio: UHD Identifikasi Device]]
 
* [[OpenBTS: Ubuntu 11.10 Install]]
 
* [[OpenBTS: Ubuntu 11.10 Install]]
 +
* [[OpenBTS: dari GIT ttsou]]
 
* [[OpenBTS: 2.8 dari SVN Install]]
 
* [[OpenBTS: 2.8 dari SVN Install]]
* [[OpenBTS: 2.8 Instalasi Real Time Asterisk]]
+
* [[OpenBTS: 2.8 dari SVN Install Clock 52MHz]] '''RECOMMENDED'''
 +
* [[OpenBTS: 2.8 dari SVN Install Clock 52MHz di Ubuntu 12.10]] '''RECOMMENDED'''
 +
* [[OpenBTS: 2.8 dari SVN Install Clock 52MHz dengan UHD tanpa GNURadio]] ''NOT RECOMMENDED''
 +
* [[OpenBTS: 2.8 Edit User di sqlite3.db]] '''RECOMMEND'''
 +
* [[OpenBTS: Yate Softswitch]] '''RECOMMENDED'''
 +
* [[OpenBTS: Yate Softswitch install Ubuntu 12.10]] '''RECOMMENDED'''
 +
* [[OpenBTS: Yate Config Test]]
 +
* [[OpenBTS: 2.8 Instalasi Real Time Asterisk]] '''RECOMMENDED'''
 +
* [[OpenBTS: 2.8 Menjalankan]] '''RECOMMENDED'''
 +
* [[OpenBTS: 2.8 Konfigurasi]]
 +
* [[OpenBTS: 2.8 Konfigurasi Subscriber Registery]]
 
* [[OpenBTS: Database SQLite]]
 
* [[OpenBTS: Database SQLite]]
 +
 +
===Multi OpenBTS 2.8===
 +
 +
* [[OpenBTS: Pola Multi OpenBTS]] '''RECOMMENDED'''
 +
* [[Multi OpenBTS: Catatan Konfigurasi]] '''RECOMMENDED'''
  
 
===Ettus E110===
 
===Ettus E110===
  
 
* [[OpenBTS: E110 Cara Login]]
 
* [[OpenBTS: E110 Cara Login]]
* [[OpenBTS: E110 Install Image di MicroSD]]
+
* [[OpenBTS: E110 Install Image di MicroSD]] '''*RECOMMENDED*'''
 +
* [[OpenBTS: E110 Cek Daughter Board]]
 +
* [[OpenBTS: E110 Mengubah Master Clock]]
 +
* [[OpenBTS: E110 Kalibrasi Clock]]
 
* [[OpenBTS: E110 Bekerja dengan opkg]]
 
* [[OpenBTS: E110 Bekerja dengan opkg]]
 +
* [[OpenBTS: E110 GNURadio]]
 +
* [[OpenBTS: E110 Compile UHD]] '''*RECOMMENDED*'''
 +
* [[OpenBTS: E110 UHD burn EEPROM RFX Board]] '''*RECOMMENDED*'''
 +
* [[OpenBTS: E110 Install UHD Image]] '''*RECOMMENDED*'''
 
* [[OpenBTS: E110 Instalasi OpenBTS]]
 
* [[OpenBTS: E110 Instalasi OpenBTS]]
 +
* [[OpenBTS: E110 Instalasi OpenBTS 2.6]] ''NOT RECOMMENDED''
 +
* [[OpenBTS: E110 Instalasi OpenBTS 2.8 untuk MultiBTS]] '''*RECOMMENDED*'''
 +
 +
===GPRS===
 +
 +
* [[OpenBTS: GPRS]]
 +
 +
===Power Amplifier===
 +
 +
* [[Driver 900MHz]]
 +
* [[Power Amplifier 900MHz]]
 +
* [[Duplexer]]
 +
* [[OpenBTS: Menaikan Jangkauan OpenBTS]]
  
 
===Lain Lain===
 
===Lain Lain===
  
 +
* [[OpenBTS: Materi Magang di ICTWATCH]]
 +
* [[OpenBTS: Seminar Outline]]
 +
* [[OpenBTS: Workshop Outline]]
 
* [[Membuat Base Station GSM Open Source]]
 
* [[Membuat Base Station GSM Open Source]]
 
* [[Teknologi Selular]]
 
* [[Teknologi Selular]]
Line 406: Line 364:
 
* [[Siapa Bilang OpenBTS Ilegal?]]
 
* [[Siapa Bilang OpenBTS Ilegal?]]
 
* [[OpenBTS: Catatan MNC dan MCC Indonesia]]
 
* [[OpenBTS: Catatan MNC dan MCC Indonesia]]
 +
* [[OpenBTS: Catatan MNC dan MCC COOL]]
 
* [[OpenBTS : Alokasi Frekuensi Operator GSM Indonesia]]
 
* [[OpenBTS : Alokasi Frekuensi Operator GSM Indonesia]]
 +
* [[GSM: Daftar Channel Frekuensi]]
  
 
===Catatan Sejarah===
 
===Catatan Sejarah===
Line 413: Line 373:
 
* [[OpenBTS: Daftar Workshop atau Seminar yang pernah dilakukan]]
 
* [[OpenBTS: Daftar Workshop atau Seminar yang pernah dilakukan]]
 
* [[OpenBTS: Daftar Artikel di Media]]
 
* [[OpenBTS: Daftar Artikel di Media]]
 +
* [[OpenBTS: Permohonan Kanal dan DID untuk OpenBTS]]
 +
 +
===Dokumentasi Video===
 +
 +
* http://www.metrotvnews.com/read/newsprograms/2012/10/14/14624/212/Teknologi-BTS
 +
* http://youtu.be/8ogOcUSpINU (1/6)
 +
* http://youtu.be/F5d7HGuhppk (2/6)
 +
* http://youtu.be/90Jgq6bOgrQ (3/6)
 +
* http://youtu.be/cNkx_qNqdfc (4/6)
 +
* http://youtu.be/6LCuoeI57ak (5/6)
 +
* http://youtu.be/-dEqcHoIlYk (6/6)
  
 
[[Category: Wireless]]
 
[[Category: Wireless]]
 
[[Category: Selular]]
 
[[Category: Selular]]

Latest revision as of 08:33, 24 December 2012

OpenBTS P2.8 menggunakan file database sqlite untuk mengkonfigurasi maupun membuat informasi status tersedia untuk aplikasi external. Sqlite adalah sebuah database SQL yang serverless, self-contained awalnya di kembangkan untuk peluru kendali (guided missile) dan sekarang banyak digunakan untuk banyak aplikasi, termasuk Blackberry, Symbian, iOS dan sistem operasi Android operating systems. Untuk informasi lebih lanjut tentang sqlite dapat dilihat di situs http://www.sqlite.org

Mengedit database di Sqlite3

Ada beberapa metoda yang dapat digunakan untuk mengedit dan melihat file database sqlite3 OpenBTS sqlite3, yaitu,

  • Sqlite3 tool command line. Access Point Range Network membawa serta sqlite3 tool command line yang dapat digunakan untuk melihat dan memodifikasi database yang ada menggunakan sintaks SQL.
    • database dapat dimanipulasi secara langsung menggunakan sintaks SQL secara realtime.
    • Untuk editing secara offline, sqlite3 dapat mengexport kode SQL ke text file menggunakan ".dump". Setelah di edit, dapat di import kembali menggunakan ".read".
  • Menggunakan editor database pihak lain. Ada beberapa GUI database editor yang tersedia untuk file database sqlite3, contoh:
    • “SQLite Database Browser” – Free browser untuk OS X & Linux tersedia dari sourceforge.net.
    • “RazorSQL” – database GUI komersial tersedia dari razorsql.com.
    • Firefox – Mozilla menawarkan add-on Firefox gratis yang di namakan SQLite Manager yang memungkinkan Firefox web browser untuk digunakan untuk melihat dan mengedit database sqlite3, tersedia dari addons.mozilla.org.
  • Melalui OpenBTS sendiri. Perintah OpenBTS CLI "config" dan "unconfig" dapat digunakan untuk mengedit tabel konfigurasi secara realtime. Perubahan konfigurasi melalui CLI akan di tulis ke database OpenBTS.db dan akan persistent.

Tabel Konfigurasi

Parameter yang mengontrol aplikasi OpenBTS di simpan dalam tabel database yang di sebut configuration table. Beberapa parameter ada yang dynamic, artinya jika parameter tersebut di ubah maka akan menimbulkan effek secara langsung. Beberapa parameter lainnya sifatnya statik dan perubahan pada parameter ini tidak akan menimbulkan effek sampai OpenBTS di restart. Beberapa parameter ada yang sifatnya statik dan match ke hardware yang spesifik dan sebaiknya tidak diubah sama sekali. Comment dalam database konfigurasi menjelaskan setiap parameter dan untuk kondisi apa parameter tersebut bisa di ubah. Flag dalam database schema menunjukan parameter mana yang statik. Schema untuk tabel konfigurasi di P2.8 adalah:

CREATE TABLE CONFIG (
  KEYSTRING TEXT UNIQUE NOT NULL,
  VALUESTRING TEXT,
  STATIC INTEGER DEFAULT 0,
  OPTIONAL INTEGER DEFAULT 0,
  COMMENTS TEXT DEFAULT ’’
  )

Perhatian bahwa database itu sendiri berisi comment, tersedia untuk operator setiap waktu. Comment ini akan dijelaskan lebih lanjut di manual ini.

Untuk mengubah sebuah parameter konfigurasi yang dynamic secara real time, kita dapat mengedit tabel menggunakan cara yang di jelaskan di atas. Effek yang terjadi akan langsung di rasakan, walaupun transaksi yang sedang berjalan akan tetap menggunakan parameter yang diset waktu memulai transaksi. Contoh, perubahaan pada parameter SIP.Proxy.Speech tidak akan memberikan effek ke sambungan telepon yang sedang in-progress, tapi call yang baru akan menggunakan proxy yang baru.

Untuk mengubah parameter konfigurasi statik, edit tabel menggunakan salah satu metoda yang di jelaskan di atas kemudian restart aplikasi OpenBTS. Dalam Linux embedded system yang standard, restart ini dapat di peroleh dengan perintah "exit", atau dengan cara me-reboot BTS tersebut.

Dalam beberapa kasus, NULL adalah nilai yang valid untuk sebuha parameter konfigurasi. Dalam terminologi SQL, nilai NULL adalah sebuah tag khusus yang menunjukan bahwa nilai tersebut tidak terdefinisi.Ini tidak sama dengan sebuah string "NULL", yang merupakan sebuah string yang berisi "NULL". Untuk membuat nilai NULL dari CLI, gunaan perintah "unconfig".

Daftar Parameter konfigurasi secara umum terlampir di bawaj ini, beberapa parameter yang penting akan di jelaskan di bagian yang lain,

  • CLI.Prompt – Prompt for the OpenBTS command line interface.
  • Control.Emergency.Destination.Host – SIP destination host to be used for the ”To:” header of emergency calls. This host may be different from the address given for SIP.Proxy.Emergency.
  • Control.Emergency.Destination.User – SIP destination user or extension to be used for the ”To:” header of emegency calls. IMS specifies ”sos”, but correct value must be matched to your switch configuration and PSAP interface.
  • Control.Emergency.GatewaySwitch – Gateway SIP switch for inbound calls from other networks. This host is used to form the return path for emergency calls, so it should be a host address that will route from your serving PSAP.
  • Control.Emergency.Geolocation – If defined, send this location as an RFC-4119 XML GEOPRIV object during SIP emergency call establishment. Format is dd:mm:ss[NS] ddd:dd:dd[EW].
  • Control.Emergency.QueueTime – Maximum time to wait for a channel to open up for an emegency call in a congested system, in milliseconds.
  • Control.Emergency.RFC5031 – If not NULL, use the RFC-5031 URN sip:sos@SIP.Proxy.Emergency as the request URN for outbound emergency calls over SIP, regardless of the value of Emergency.Destination.User. The ”To:” header will still be Emergency.Destination.User@Emergency.Destination.Host.
  • Control.Emergency.Source.User – SIP identity to use if no IMSI is available. IMS specifies ”anonymous” but other values might be more useful depending on your configuration.
  • Control.GSMTAP.TargetIP – Target IP address for GSMTAP packets; the IP address of Wireshark, if you use it for GSM.
  • Control.LUR.AttachDetach – Attach/detach flag. Set to 1 to use attach/detach procedure, 0 otherwise. This will make initial LUR more prompt. It will also cause an un-regstration if the handset powers off and really heavy LUR loads in areas with spotty coverage.
  • Control.LUR.CachedAuthentication – If not NULL, use RAND-SRES pairs cached in the TMSI table for authentication. If this method is used, it is important that the TMSI Table be in persistent storage.
  • Control.LUR.DefaultAuthenticationAccept – If not NULL, provisioned handsets will be accepted for authentication in the absence of any defined authentication method. For commercial networks this value should probably be NULL.
  • Control.LUR.FailedRegistration.Message – If defined, send this text message, followed by the IMSI, to unprovisioned handsets that are denied registration.
  • Control.LUR.FailedRegistration.ShortCode – The return address for the failed registration message. If the message is defined, this must also be defined.
  • Control.LUR.NormalRegistration.Message – If defined, send this text message, followed by the IMSI, to provisioned handsets when they attach on Um.
  • Control.LUR.NormalRegistration.ShortCode – The return address for the normal registration message. If the message is defined, this must also be defined.
  • Control.LUR.OpenRegistration – A regular expression. If not NULL, allow unprovisioned handsets with matching IMSIs to attach in Um.
  • Control.LUR.OpenRegistration.Message – If defined, send this text message, followed by the IMSI, to unprovisioned handsets when they attach on Um due to open registration.
  • Control.LUR.OpenRegistration.ShortCode – The return address for the open registration message. If the message is defined, this must also be defined.
  • Control.LUR.QueryClassmark – If not NULL, query every MS for classmark during LUR.
  • Control.LUR.QueryIMEI – If not NULL, query every MS for IMSI during LUR.
  • Control.LUR.SR-HTTPAuthentication – If not NULL, use the HTTP interface of the subscriber registry server for authentication.
  • Control.LUR.SendTMSIs – If not NULL, send new TMSI assignments to handsets that are allowed to attach.
  • Control.LUR.UnprovisionedRejectCause – Reject cause for location updating failures for unprovisioned phones. Reject causes come from GSM 04.08 10.5.3.6. Reject cause 0x04, IMSI not in VLR, is usually the right one.
  • Control.NumSQLTries – Number of times to retry SQL queries before declaring a database access failure.
  • Control.Reporting.PhysStatusTable – File path for channel status reporting database. Static.
  • Control.Reporting.TMSITable – File path for TMSITable database. Static.
  • Control.TMSITable.MaxAge – Maximum allowed age for a TMSI in hours.
  • Control.TMSITable.MaxSize – Maximum size of TMSI table before oldest TMSIs are discarded.
  • Control.TestCall.Port – Port for exchanging L3 packets with the testcall feature.
  • Control.VEA – If not NULL, user very early assignment for speech call establishment. See GSM 04.08 Section 7.3.2 for a detailed explanation of assignment types. If VEA is selection, GSM.CellSelection.NECI should be set to 1. See GSM 04.08 Sections 9.1.8 and 10.5.2.4 for an explanation of the NECI bit.
  • GSM.CCCH.AGCH.QMax – Maximum number of access grants to be queued for transmission on AGCH before declaring congrestion.
  • GSM.CCCH.CCCH-CONF – CCCH configuration type. See GSM 10.5.2.11 for encoding. Value of 1 means we are using a C-V beacon. Any other value selects a C-IV beacon.
  • GSM.CCCH.PCH.Reserve – Number of CCCH subchannels to reserve for paging.
  • GSM.CellSelection.CELL-RESELECT-HYSTERESIS – Cell Reselection Hysteresis. See GSM 04.08 10.5.2.4, Table 10.5.23 for encoding. Encoding is 2N dB, values of N are 0...7 for 0...14 dB.
  • GSM.CellSelection.MS-TXPWR-MAX-CCH – Cell selection parameters. See GSM 04.08 10.5.2.4.
  • GSM.CellSelection.NCCsPermitted – NCCs Permitted. An 8-bit mask of allowed NCCs. Unless you are coordinating with another carrier, this should probably just select your own NCC.
  • GSM.CellSelection.NECI – NECI, New Establishment Causes. This must be set to ”1” if you want to support very early assignment. See GSM 04.08 10.5.2.4, Table 10.5.23 and 04.08 9.1.8, Table 9.9.
  • GSM.CellSelection.Neighbors – ARFCNs of neighboring cells.
  • GSM.CellSelection.RXLEV-ACCESS-MIN – Cell selection parameters. See GSM 04.08 10.5.2.4.
  • GSM.Channels.C1sFirst – If not NULL, allocate C-I slots first, starting at C0T1. Otherwise, allocate C-VII slots first. Static.
  • GSM.Channels.NumC1s – Number of Combination-I timeslots to configure. The C-I slot carries a single full-rate TCH, used for speech calling. Static.
  • GSM.Channels.NumC7s – Number of Combination-VII timeslots to configure. The C-VII slot carries 8 SDCCHs, useful to handle high registration loads or SMS. If C0T0 is C-IV, you must have at least one C-VII also. Static.
  • GSM.Identity.BSIC.BCC – GSM basestation color code; lower 3 bits of the BSIC. BCC values in a multi-BTS network should be assigned so that BTS units with overlapping coverage do not share a BCC. This value will also select the training sequence used for all slots on this unit.
  • GSM.Identity.BSIC.NCC – GSM network color code; upper 3 bits of the BSIC. Assigned by your national regulator. Must be distinct from NCCs of other GSM operators in your area.
  • GSM.Identity.CI – Cell ID, 16 bits. Should be unique.
  • GSM.Identity.LAC – Location area code, 16 bits, values 0xFFxx are reserved. For multi-BTS networks, assign a unique LAC to each BTS unit. (That is not the normal procedure in conventional GSM networks, but is the correct procedure in OpenBTS networks.)
  • GSM.Identity.MCC – Mobile country code, 2 or 3 digits. Defined in ITU-T E.212.
  • GSM.Identity.MNC – Mobile network code; Must be 3 dgits. Assigned by your national regulator.
  • GSM.Identity.ShortName – Network short name, displayed on some phones. Optional but must be defined if you also want the network to send time-of-day.
  • GSM.Identity.ShowCountry – If not NULL, tell the phone to show the country name based on the MCC.
  • GSM.MS.Power.Damping – Damping value for MS power control loop.
  • GSM.MS.Power.Max – Maximum commanded MS power level in dBm.
  • GSM.MS.Power.Min – Minimum commanded MS power level in dBm.
  • GSM.MS.TA.Damping – Damping value for timing advance control loop.
  • GSM.MS.TA.Max – Maximum allowed timing advance in symbol periods. Ignore RACH bursts with delays greater than this. Can be used to limit service range.
  • GSM.MaxSpeechLatency – Maximum allowed speech buffering latency, in 20 ms frames. If the jitter is larger than this delay, frames will be lost.
  • GSM.RACH.AC – 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. If you do not have proper PSAP integration, set to 0x0400 to indicate no support for emergency calls.
  • GSM.RACH.MaxRetrans – 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.TxInteger – 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.RADIO-LINK-TIMEOUT – L1 radio link timeout. This is the raw parameter sent on the BCCH; see GSM 10.5.2.3 for encoding. Should be coordinated with T3109.
  • GSM.RRLP.ACCURACY – Requested accuracy of location request. K in 10(1.1**K-1). See 3GPP 03.32, sect 6.2
  • GSM.RRLP.ALMANAC.REFRESH.TIME – How often the almanac is refreshed, in hours
  • GSM.RRLP.ALMANAC.URL – URL of almanac source.
  • GSM.RRLP.EPHEMERIS.REFRESH.TIME – How often the ephemeris is refreshed, in hours.
  • GSM.RRLP.EPHEMERIS.URL – URL of ephemeris source.
  • GSM.RRLP.RESPONSETIME – Mobile timeout. (OpenBTS timeout is 130 sec = max response time + 2.) N in 2**N. See 3GPP 04.31 sect A.2.2.1
  • GSM.RRLP.SEED.ALTITUDE – Seed altitude in meters wrt geoidal surface.
  • GSM.RRLP.SEED.LATITUDE – Seed latitude in degrees. -90 (south pole) .. +90 (north pole)
  • GSM.RRLP.SEED.LONGITUDE – Seed longitude in degrees. -180 (west of greenwich) .. 180 (east)
  • GSM.RRLP.SERVER.URL – URL of RRLP server.
  • GSM.Radio.Band – The GSM operating band. Valid values are 850 (GSM850), 900 (PGSM900), 1800 (DCS1800) and 1900 (PCS1900). For most Range models, this value is dictated by the hardware and should not be changed. Static.
  • GSM.Radio.C0 – The C0 ARFCN. Static.
  • GSM.Radio.MaxExpectedDelaySpread – Expected worst-case delay spread in symbol periods, roughly 3.7 us or 1.1 km per unit.
  • GSM.Radio.PowerManager.MaxAttenDB – Maximum transmitter attenuation level, in dB wrt full scale on the D/A output. This sets the minimum power output level in the output power control loop.
  • GSM.Radio.PowerManager.MinAttenDB – Minimum transmitter attenuation level, in dB wrt full scale on the D/A output. This sets the maximum power output level in the output power control loop.
  • GSM.Radio.PowerManager.NumSamples – Number of samples averaged by the output power control loop.
  • GSM.Radio.PowerManager.SamplePeriod – Sample period for the output power control loop.
  • GSM.Radio.PowerManager.TargetT3122 – Target value for T3122, the random access hold-off timer, for the power control loop.
  • GSM.Radio.RSSITarget – Target uplink RSSI for MS power control loop, in dB wrt to A/D full scale. Should be 6-10 dB above the noise floor.
  • GSM.Radio.RxGain – Receiver gain setting in dB. Ideal value is dictacted by the hardware. This database parameter is static but the receiver gain can be modified in real time with the CLI rxgain command. Static.
  • GSM.Timer.T3113 – Paging timer T3113 in ms. This is the timeout for a handset to respond to a paging request. This should usually be the same as SIP.Timer.B in your VoIP network.
  • GSM.Timer.T3122Max – Maximum allowed value for T3122, the RACH holdoff timer, in milliseconds.
  • GSM.Timer.T3122Min – Minimum allowed value for T3122, the RACH holdoff timer, in milliseconds.
  • GSM.Timer.T3212 – Registration timer T3212 period in minutes. Should be a factor of 6. Set to 0 to disable periodic registration. Should be smaller than SIP registration period.
  • Log.Alarms.Max – Maximum number of alarms to remember inside the application.
  • Log.Level – Default logging level when no other level is defined for a file.
  • Log.Level.CallControl.cpp – Default configuration logs a trace at L3.
  • Log.Level.MobilityManagement.cpp – Default configuration logs a trace at L3.
  • Log.Level.RadioResource.cpp – Default configuration logs a trace at L3.
  • Log.Level.SMSControl.cpp – Default configuration logs a trace at L3.
  • NTP.Server – NTP server(s) for time-of-day clock syncing. For multiple servers, use a space-delimited list. If left undefined, NTP will not be used, but it is strongly recommended.
  • RTP.Range – Range of RTP port pool. Pool is RTP.Start to RTP.Range-1. Static.
  • RTP.Start – Base of RTP port pool. Pool is RTP.Start to RTP.Range-1. Static.
  • SIP.DTMF.RFC2833 – If not NULL, use RFC-2833 (RTP event signalling) for in-call DTMF.
  • SIP.DTMF.RFC2833.PayloadType – Payload type to use for RFC-2833 telephone event packets. If SIP.DTMF.2833 is defined, this must also be defined.
  • SIP.DTMF.RFC2967 – If not NULL, use RFC-2967 (SIP INFO method) for in-call DTMF.
  • SIP.Local.IP – IP address of the OpenBTS machine as seen by its proxies. If these are all local, this can be localhost. Static.
  • SIP.Local.Port – IP port that OpenBTS uses for its SIP interface. Static.
  • SIP.MaxForwards – Maximum allowed number of referrals.
  • SIP.Proxy.Emergency – The IP host and port of the proxy to be used for emergency calls.
  • SIP.Proxy.Registration – The IP host and port of the proxy to be used for registration and authentication. This is the subscriber registry, for example.
  • SIP.Proxy.SMS – The IP host and port of the proxy to be used for text messaging. This is smqueue,for example.
  • SIP.Proxy.Speech – The IP host and port of the proxy to be used for normal speech calls. This is Asterisk, for example.
  • SIP.RegistrationPeriod – Registration period in minutes for MS SIP users. Should be longer than GSM T3212.
  • SIP.SMSC – The SMSC handler in smqueue. This is the entity that handles full 3GPP MIME-encapsulted TPDUs. If not defined, use direct numeric addressing. Normally the value is NULL if SMS.MIMIEType is ”text/plain” or ”smsc” if SMS.MIMEType is ”application/vnd.3gpp”.
  • SIP.Timer.A – INVITE retransmit period in ms.
  • SIP.Timer.B – INVITE transaction timeout in ms. This value should usually match GSM.Timer.T3113.
  • SIP.Timer.E – Non-INVITE initial request retransmit period in ms.
  • SIP.Timer.F – Non-INVITE initial request timeout in ms.
  • SIP.Timer.H – ACK timeout period in ms.
  • SIP.Timer.I – ACK retransmit period in ms.
  • SIP.Timer.J – Non-INVITE non-initial request retransmit period in ms.
  • SIP.myPort – Port used by the SIP Authentication Server
  • SMS.DefaultDestSMSC – Use this to fill in L4 SMSC address in SMS submission.
  • SMS.FakeSrcSMSC – Use this to fill in L4 SMSC address in SMS delivery.
  • SMS.MIMEType – This is the MIME Type that OpenBTS will use for RFC-3428 SIP MESSAGE payloads. Valid values are ”application/vnd.3gpp.sms” and ”text/plain”.
  • SubscriberRegistry.A3A8 – URL of upstream subscriber registry server. Blank (not NULL) if there is none.
  • SubscriberRegistry.HTTP.Server – URL of the subscriber registry server.
  • SubscriberRegistry.Manager.Title – Title of subscriber registry database manager web page.
  • SubscriberRegistry.Manager.Url – URL of the subscriber registry database manager.
  • SubscriberRegistry.Manager.VisibleColumns – Field names in subscriber registry visible in the database manager.
  • SubscriberRegistry.db – The location of the sqlite3 database holding the subscriber registry.
  • TRX.IP – IP address of the transceiver application. Static.
  • TRX.Port – IP port of the transceiver application. Static.
  • TRX.RadioFrequencyOffset – Fine-tuning adjustment for the transceiver. Static.

TMSI Table

Untuk mengurangi ketergantungan ke sambungan backhaul, OpenBTS men-track TMSI secara internal. Untuk memenuhi hal ini, OpenBTS men-track hubungan TMSI-IMSI menggunakan sqlite3 dalam tabel TMSI.TMSI dimasukan menggunakan nomor urut. OpenBTS mengalokasikan TMSI di tabel TMSI untuk setiap MS yang mengirimkan Location Updating Request, baik MS yang di ijinkan untuk register maupun tidak. Tabel TMSI akan dapat di read-write oleh OpenBTS tapi hanya read-only oleh aplikasi lain. Path dari file database yang digunakan di tabel is di definisikan di parameter konfigurasi Control.DBPath.TMSITable. Di system. tabel di simpan di partisi ramdisk biasanya standard lokasi-nya di /var/run. Schema TMSI tabel adalah:

CREATE TABLE IF NOT EXISTS TMSI_TABLE (
  TMSI INTEGER PRIMARY KEY AUTOINCREMENT -- this value is used as the TMSI
  CREATED INTEGER NOT NULL, -- Unix time of record creation
  ACCESSED INTEGER NOT NULL, -- Unix time of last encounter
  IMSI TEXT UNIQUE NOT NULL, -- IMSI of the SIM
  IMEI TEXT, -- IMEI of the MS, if requested
  L3TI INTEGER DEFAULT 0, -- L3 transaction identifier last used with this MS
  A5_SUPPORT INTEGER, -- encryption support in the MS, if requested
  POWER_CLASS INTEGER, -- power class of the MS. if requested
  OLD_TMSI INTEGER, -- previous TMSI from another cell or network
  PREV_MCC INTEGER, -- previous network MCC
  PREV_MNC INTEGER, -- previous network MNC
  PREV_LAC INTEGER, -- previous network LAC
  RANDUPPER INTEGER -- cached authentication token
  RANDLOWER INTEGER -- cached authentication token
  SRES INTEGER, -- cached authentication token
  DEG_LAT FLOAT, -- cached RRLP result
  DEG_LONG FLOAT -- cached RRLP result
  )

Channel Table

OpenBTS melaporkan secara real time informasi status fisik untuk kanal yang aktif ke tabel sqlite3 external bernama PHYSTATUS. Tabel ini dilihat sebagai write-only oleh OpenBTS tapi harus dilihat sebagai read-only oleh aplikasi lainnya. Data dari channel ini akan di update setiap ada message sistem infomasi yang di terima untuk berasosiasi ke channel SACCH. Path dari file database yang digunakan di tabel ini di definisikan di parameter konfigurasi GSM.DBPath.PhysStatusTable. Schema tabel adalah:

CREATE TABLE IF NOT EXISTS PHYSTATUS (
  CN_TN_TYPE_AND_OFFSET STRING PRIMARY KEY, -- cross-refs TRANSACTION_TABLE
  ARFCN INTEGER DEFAULT NULL, -- actual ARFCN
  ACCESSED INTEGER DEFAULT 0, -- Unix time of last update
  RXLEV_FULL_SERVING_CELL INTEGER DEFAULT NULL, -- from most recent measurement report
  RXLEV_SUB_SERVING_CELL INTEGER DEFAULT NULL, -- from most recent measurement report
  RXQUAL_FULL_SERVING_CELL_BER FLOAT DEFAULT NULL, -- from most recent measurement report
  RXQUAL_SUB_SERVING_CELL_BER FLOAT DEFAULT NULL, -- from most recent measurement report
  RSSI FLOAT DEFAULT NULL, -- RSSI relative to full scale input
  TIME_ERR FLOAT DEFAULT NULL, -- timing advance error in symbol periods
  TRANS_PWR INTEGER DEFAULT NULL, -- MS tx power in dBm
  TIME_ADVC INTEGER DEFAULT NULL, -- MS timing advance in symbol periods
  FER FLOAT DEFAULT NULL -- uplink FER
  )

Field CN TN TYPE AND OFFSET adalah string yang menerangkan sebuah channel dalam bentuk C<n>T<n> <channelType>-<subchannelIndex>

TABEL CHANNEL

Contoh

  • “C0T1 TCH/F” is a full rate traffic channel on timeslot 1 of the C0 ARFCN
  • “C0T0 SDCCH-0/4” is the #0 SDCCH (of 4 available) on C0T0.

String dengan format yang sama digunakan di tabel transaction.

Pranala Menarik

Persiapan

OpenBTS 2.6

OpenBTS 2.8

Multi OpenBTS 2.8

Ettus E110

GPRS

Power Amplifier

Lain Lain

Catatan Legal dan Pendukung

Catatan Sejarah

Dokumentasi Video