Hello! I Need Help I install these three programs OpenBTS, OsmocomBB, Asterisk Then run them, Everything works well OpenBTS sent an SMS to my phones I answered and he checked me I registered into OpenBTS a second phone I tried to transfer SMS between phones - all good but when I try to call from one to another I did not get Asterisk writes ================================================================ *CLI> Retransmission timeout reached on transmission 755803415@127.0.0.1 for seqno 179 (Critical Response) -- See wiki.asterisk.org/wiki/display/AST/SIP+Retransmissions Packet timed out after 32001ms with no response ================================================================ Why? What do I do? -- View this message in context: http://baseband-devel.722152.n3.nabble.com/OpenBTS-OsmocomBB-Asterisk-tp4026... Sent from the baseband-devel mailing list archive at Nabble.com.
I use motorola c118 as hardware for OpenBTS <http://baseband-devel.722152.n3.nabble.com/file/n4026435/11.jpg> here's what I see in my osmocomBB: ======================================= BAT-ADC: 567 7 0 0 1023 360 336 219 Charger at 60 mV. Battery at 3876 mV. Charging at 0 mA. Battery capacity is 85%. Battery range is 3199..3999 mV. Battery full at 468 LSB .. full at 585 LSB Charging at 239 LSB (204 mA). BCICTL2=0x3ff battery-info.flags=0x00000000 bat_compal_e88_chg_state=0 LOST 1882! LOST 1868! LOST 1877! LOST 1873! ... ... BAT-ADC: 572 8 0 0 1023 386 359 219 Charger at 68 mV. Battery at 3910 mV. Charging at 0 mA. Battery capacity is 89%. Battery range is 3199..3999 mV. Battery full at 468 LSB .. full at 585 LSB Charging at 239 LSB (204 mA). BCICTL2=0x3ff battery-info.flags=0x00000000 bat_compal_e88_chg_state=0 ### NB ### (0799 10ed) ... ... BAT-ADC: 565 8 0 0 1023 359 336 219 Charger at 68 mV. Battery at 3862 mV. Charging at 0 mA. Battery capacity is 83%. Battery range is 3199..3999 mV. Battery full at 468 LSB .. full at 585 LSB Charging at 239 LSB (204 mA). BCICTL2=0x3ff battery-info.flags=0x00000000 bat_compal_e88_chg_state=0 LOST 1892! LOST 1858! TOA AVG is not 16 qbits, correcting (got 13) ... ... BAT-ADC: 563 8 0 0 1023 357 332 212 Charger at 68 mV. Battery at 3849 mV. Charging at 0 mA. Battery capacity is 81%. Battery range is 3199..3999 mV. Battery full at 468 LSB .. full at 585 LSB Charging at 239 LSB (204 mA). BCICTL2=0x3ff battery-info.flags=0x00000000 bat_compal_e88_chg_state=0 ### RACH ### (15f0 0773 - 0004) ### NB ### (15ae 4000) ### NB ### (15a9 4000) ### NB ### (15c8 4000) ### NB ### (15c8 4000) ... ... ### NB ### (0f65 4000) ### NB ### (0f65 4000) ### NB ### (0f5f 4000) ### NB ### (0f52 4000) BAT-ADC: 563 9 0 0 1023 356 332 212 Charger at 77 mV. Battery at 3849 mV. Charging at 0 mA. Battery capacity is 81%. Battery range is 3199..3999 mV. Battery full at 468 LSB .. full at 585 LSB Charging at 239 LSB (204 mA). BCICTL2=0x3ff battery-info.flags=0x00000000 bat_compal_e88_chg_state=0 ### RACH ### (15b3 06fe - 0005) STALE BURST 1767427 STALE BURST 1767428 STALE BURST 1767429 STALE BURST 1767430 ### NB ### (159b 4000) ### NB ### (15a0 4000) ### NB ### (159b 4000) ### NB ### (158c 4000) ### NB ### (1576 4000) ... ... ======================================= what is STALE BURST -? what is ### RACH ### (15b3 06fe - 0005) -? what is ### NB ### (159b 4000) -? what is LOST 1858! -? what isTOA AVG is not 16 qbits, correcting (got 13) -? thank you for your attention! -- View this message in context: http://baseband-devel.722152.n3.nabble.com/OpenBTS-OsmocomBB-Asterisk-tp4026... Sent from the baseband-devel mailing list archive at Nabble.com.
Have you also installed linux call router as is instructed in the network_from_scratch wiki? I only tried the basic setup(without voice) last year,i.e registering phones to broadcasted network but also saw stale burst messages sometimes just after launching the transceiver. Den Mandag, 21. april 2014 17.42 skrev trixbox.t <trixbox.t@yandex.ru>: I use motorola c118 as hardware for OpenBTS <http://baseband-devel.722152.n3.nabble.com/file/n4026435/11.jpg> here's what I see in my osmocomBB: ======================================= BAT-ADC: 567 7 0 0 1023 360 336 219 Charger at 60 mV. Battery at 3876 mV. Charging at 0 mA. Battery capacity is 85%. Battery range is 3199..3999 mV. Battery full at 468 LSB .. full at 585 LSB Charging at 239 LSB (204 mA). BCICTL2=0x3ff battery-info.flags=0x00000000 bat_compal_e88_chg_state=0 LOST 1882! LOST 1868! LOST 1877! LOST 1873! ... ... BAT-ADC: 572 8 0 0 1023 386 359 219 Charger at 68 mV. Battery at 3910 mV. Charging at 0 mA. Battery capacity is 89%. Battery range is 3199..3999 mV. Battery full at 468 LSB .. full at 585 LSB Charging at 239 LSB (204 mA). BCICTL2=0x3ff battery-info.flags=0x00000000 bat_compal_e88_chg_state=0 ### NB ### (0799 10ed) ... ... BAT-ADC: 565 8 0 0 1023 359 336 219 Charger at 68 mV. Battery at 3862 mV. Charging at 0 mA. Battery capacity is 83%. Battery range is 3199..3999 mV. Battery full at 468 LSB .. full at 585 LSB Charging at 239 LSB (204 mA). BCICTL2=0x3ff battery-info.flags=0x00000000 bat_compal_e88_chg_state=0 LOST 1892! LOST 1858! TOA AVG is not 16 qbits, correcting (got 13) ... ... BAT-ADC: 563 8 0 0 1023 357 332 212 Charger at 68 mV. Battery at 3849 mV. Charging at 0 mA. Battery capacity is 81%. Battery range is 3199..3999 mV. Battery full at 468 LSB .. full at 585 LSB Charging at 239 LSB (204 mA). BCICTL2=0x3ff battery-info.flags=0x00000000 bat_compal_e88_chg_state=0 ### RACH ### (15f0 0773 - 0004) ### NB ### (15ae 4000) ### NB ### (15a9 4000) ### NB ### (15c8 4000) ### NB ### (15c8 4000) ... ... ### NB ### (0f65 4000) ### NB ### (0f65 4000) ### NB ### (0f5f 4000) ### NB ### (0f52 4000) BAT-ADC: 563 9 0 0 1023 356 332 212 Charger at 77 mV. Battery at 3849 mV. Charging at 0 mA. Battery capacity is 81%. Battery range is 3199..3999 mV. Battery full at 468 LSB .. full at 585 LSB Charging at 239 LSB (204 mA). BCICTL2=0x3ff battery-info.flags=0x00000000 bat_compal_e88_chg_state=0 ### RACH ### (15b3 06fe - 0005) STALE BURST 1767427 STALE BURST 1767428 STALE BURST 1767429 STALE BURST 1767430 ### NB ### (159b 4000) ### NB ### (15a0 4000) ### NB ### (159b 4000) ### NB ### (158c 4000) ### NB ### (1576 4000) ... ... ======================================= what is STALE BURST -? what is ### RACH ### (15b3 06fe - 0005) -? what is ### NB ### (159b 4000) -? what is LOST 1858! -? what isTOA AVG is not 16 qbits, correcting (got 13) -? thank you for your attention! -- View this message in context: http://baseband-devel.722152.n3.nabble.com/OpenBTS-OsmocomBB-Asterisk-tp4026... Sent from the baseband-devel mailing list archive at Nabble.com.
I guess you need to install the other packages as well since they are listed in the wiki. As I understand Linux call Router must be present to somehow "interface" the traffic/voice/channels to asterisk. NB in your logs stands for Normal Bursts Den Onsdag, 23. april 2014 2.32 skrev al red <trixbox.t@yandex.ru>: thank you very much for the help! I do not have installed Linux-Call-Router (LCR) except the Linux-Call-Router (LCR) have yet to install something? for example oRTP, opencore-amr, Sip-Sofia, libosmo-abis, OsmoNITB, OsmoBTS, OsmoTRX, I understood from the "network_from_scratch wiki" that I need to have more than one phone "motorola c118" The "network_from_scratch wiki" says: ======================================================================================== Now you should start with a single phone for one timeslot only. If it works, you can try two phones to serve two timeslots. Since you have only one slot, you will only be able to transmit broadcast, do location updating and send/receive SMS. Here is the "osmo-bts.cfg" for a single timeslot: ... ... slotmask 1 0 0 0 0 0 0 0 and further When using two phones, two timeslots can be served. I suggest to configure second timeslot (TS 1) as TCH/H at openbsc.cnf. This way it is possible to allow two traffic channels on a single timeslot. If you do a call from one phone to another, you will need one channel for each phone. In order to use two phones, you need to change the alot map of osmo-bts.cnf: slotmask 1 1 0 0 0 0 0 0 ============================================================================================== how many phones can I connect -? slotmask 1 1 1 1 1 1 1 1 8 - am I right? what opportunities does it give? 22.04.2014, 15:42, "Erich Dachleger" <edachleger@yahoo.com>: Have you also installed linux call router as is instructed in the network_from_scratch wiki?
I only tried the basic setup(without voice) last year,i.e registering phones to broadcasted network but also saw stale burst messages sometimes just after launching the transceiver.
Den Mandag, 21. april 2014 17.42 skrev trixbox.t <trixbox.t@yandex.ru>:
I use motorola c118 as hardware for OpenBTS
<http://baseband-devel.722152.n3.nabble.com/file/n4026435/11.jpg>
here's what I see in my osmocomBB: ======================================= BAT-ADC: 567 7 0 0 1023 360 336 219 Charger at 60 mV. Battery at 3876 mV. Charging at 0 mA. Battery capacity is 85%. Battery range is 3199..3999 mV. Battery full at 468 LSB .. full at 585 LSB Charging at 239 LSB (204 mA). BCICTL2=0x3ff battery-info.flags=0x00000000 bat_compal_e88_chg_state=0 LOST 1882! LOST 1868! LOST 1877! LOST 1873! ... ... BAT-ADC: 572 8 0 0 1023 386 359 219 Charger at 68 mV. Battery at 3910 mV. Charging at 0 mA. Battery capacity is 89%. Battery range is 3199..3999 mV. Battery full at 468 LSB .. full at 585 LSB Charging at 239 LSB (204 mA). BCICTL2=0x3ff battery-info.flags=0x00000000 bat_compal_e88_chg_state=0 ### NB ### (0799 10ed) ... ... BAT-ADC: 565 8 0 0 1023 359 336 219 Charger at 68 mV. Battery at 3862 mV. Charging at 0 mA. Battery capacity is 83%. Battery range is 3199..3999 mV. Battery full at 468 LSB .. full at 585 LSB Charging at 239 LSB (204 mA). BCICTL2=0x3ff battery-info.flags=0x00000000 bat_compal_e88_chg_state=0 LOST 1892! LOST 1858! TOA AVG is not 16 qbits, correcting (got 13) ... ... BAT-ADC: 563 8 0 0 1023 357 332 212 Charger at 68 mV. Battery at 3849 mV. Charging at 0 mA. Battery capacity is 81%. Battery range is 3199..3999 mV. Battery full at 468 LSB .. full at 585 LSB Charging at 239 LSB (204 mA). BCICTL2=0x3ff battery-info.flags=0x00000000 bat_compal_e88_chg_state=0 ### RACH ### (15f0 0773 - 0004) ### NB ### (15ae 4000) ### NB ### (15a9 4000) ### NB ### (15c8 4000) ### NB ### (15c8 4000) ... ... ### NB ### (0f65 4000) ### NB ### (0f65 4000) ### NB ### (0f5f 4000) ### NB ### (0f52 4000) BAT-ADC: 563 9 0 0 1023 356 332 212 Charger at 77 mV. Battery at 3849 mV. Charging at 0 mA. Battery capacity is 81%. Battery range is 3199..3999 mV. Battery full at 468 LSB .. full at 585 LSB Charging at 239 LSB (204 mA). BCICTL2=0x3ff battery-info.flags=0x00000000 bat_compal_e88_chg_state=0 ### RACH ### (15b3 06fe - 0005) STALE BURST 1767427 STALE BURST 1767428 STALE BURST 1767429 STALE BURST 1767430 ### NB ### (159b 4000) ### NB ### (15a0 4000) ### NB ### (159b 4000) ### NB ### (158c 4000) ### NB ### (1576 4000) ... ... =======================================
what is STALE BURST -?
what is ### RACH ### (15b3 06fe - 0005) -?
what is ### NB ### (159b 4000) -?
what is LOST 1858! -?
what isTOA AVG is not 16 qbits, correcting (got 13) -?
thank you for your attention!
-- View this message in context: http://baseband-devel.722152.n3.nabble.com/OpenBTS-OsmocomBB-Asterisk-tp4026... Sent from the baseband-devel mailing list archive at Nabble.com.
Hello! I tried all suggestions and I still have a question "how to connect 3 phone to transceiver ?" i.e. 1. phone - # osmocon -p /dev/ttyUSB0 -m c123xor -c path_to/trx.highram.bin -r 99 2. phone - # osmocon -p /dev/ttyUSB1 -s /tmp/osmocom_l2.2 -m c123xor -c path_to/trx.highram.bin -r 99 3. phone - # osmocon -p /dev/ttyUSB2 -s /tmp/osmocom_l2.3 -m c123xor -c path_to/trx.highram.bin -r 99 and transceiver -e 5 -r 99 -3 what I need to change in osmocom-bb2/src/host/layer23/src/transceiver/, to get it working??? thank you all !!! -- View this message in context: http://baseband-devel.722152.n3.nabble.com/OpenBTS-OsmocomBB-Asterisk-tp4026... Sent from the baseband-devel mailing list archive at Nabble.com.
Is it possible to use Three phones to support more than 2 timeslots?Do you use another branch? I cannot find tjhat info anywhere in the network-from-scratch page, two phones ,however work ok. And in the help output from transceiver app I find only the -2 option explicitly mentioned. However a third socket, osmocom_l2.3 is established after connecting third phone and launching the trx-firmware, but transceiver says: invalid option -- '3'. regards erich Den Onsdag, 2. juli 2014 23.23 skrev trixbox.t <trixbox.t@yandex.ru>: Hello! I tried all suggestions and I still have a question "how to connect 3 phone to transceiver ?" i.e. 1. phone - # osmocon -p /dev/ttyUSB0 -m c123xor -c path_to/trx.highram.bin -r 99 2. phone - # osmocon -p /dev/ttyUSB1 -s /tmp/osmocom_l2.2 -m c123xor -c path_to/trx.highram.bin -r 99 3. phone - # osmocon -p /dev/ttyUSB2 -s /tmp/osmocom_l2.3 -m c123xor -c path_to/trx.highram.bin -r 99 and transceiver -e 5 -r 99 -3 what I need to change in osmocom-bb2/src/host/layer23/src/transceiver/, to get it working??? thank you all !!! -- View this message in context: http://baseband-devel.722152.n3.nabble.com/OpenBTS-OsmocomBB-Asterisk-tp4026... Sent from the baseband-devel mailing list archive at Nabble.com.
It is my understanding that much of the work for this has been done in the jolly/testing branch: https://github.com/osmocom/osmocom-bb/commit/687bc2318d18073d02756ef6ea5b967... Hopefully all that is needed is to add code for a -3, -4, etc command-line option and all the underlying data structures are already in place. I keep meaning to look into it further one of these days but have not gotten around to it yet. Cheers, Rusty On Mon, Jul 7, 2014 at 12:39 PM, Erich Dachleger <edachleger@yahoo.com> wrote:
Is it possible to use Three phones to support more than 2 timeslots?Do you use another branch? I cannot find tjhat info anywhere in the network-from-scratch page, two phones ,however work ok. And in the help output from transceiver app I find only the -2 option explicitly mentioned. However a third socket, osmocom_l2.3 is established after connecting third phone and launching the trx-firmware, but transceiver says: invalid option -- '3'.
regards erich
Den Onsdag, 2. juli 2014 23.23 skrev trixbox.t <trixbox.t@yandex.ru>:
Hello!
I tried all suggestions and I still have a question "how to connect 3 phone to transceiver ?" i.e. 1. phone - # osmocon -p /dev/ttyUSB0 -m c123xor -c path_to/trx.highram.bin -r 99 2. phone - # osmocon -p /dev/ttyUSB1 -s /tmp/osmocom_l2.2 -m c123xor -c path_to/trx.highram.bin -r 99 3. phone - # osmocon -p /dev/ttyUSB2 -s /tmp/osmocom_l2.3 -m c123xor -c path_to/trx.highram.bin -r 99
and transceiver -e 5 -r 99 -3
what I need to change in osmocom-bb2/src/host/layer23/src/transceiver/, to get it working???
thank you all !!!
-- View this message in context: http://baseband-devel.722152.n3.nabble.com/OpenBTS-OsmocomBB-Asterisk-tp4026... Sent from the baseband-devel mailing list archive at Nabble.com.
*Thanks to all who responded !!!* In a network from scratch page describes how to connect the 2 phones. open-bsc.cfg 2 time-slots: *timeslot 0 - phys_chan_config CCCH+SDCCH4 timeslot 1 - phys_chan_config TCH/H* When I run this option, then when I do a test call at 995 (hold music) lcr I get: *000000 ERROR (in gsm.cpp/audio_send() line 461): HR frame, but encoder not created. 000000 ERROR (in gsm.cpp/frame_receive() line 320): HR frame, but decoder not created. * Because http://openbsc.osmocom.org/trac/wiki/OpenBSC says following: *«TCH/H voice calls (they work in osmo-bsc, but not in osmo-nitb)»* then I set timeslot 0 - phys_chan_config CCCH+SDCCH4 timeslot 1 - phys_chan_config TCH/F and the test call 995 (hold music) lcr works well. I register in the test network is the second phone to call on the first phone I need another channel TCH/F i.e. timeslot 2 - phys_chan_config TCH/F I looked commit 687bc2318d18073d02756ef6ea5b96799f4b9aa7 *Allow transceiver application to handle multiple TRX and multiple phones* There is no more one-to-one relation between application state, trx instance and l1ctl link to the phone. An application can have many trx instances and many l1ctl links to phones. Additionally each trx can have up to 8 relations to one or different l1ctl links, one for each time slot. This allows to split one TRX into several phones. (use only one ARFCN) Also it allows to use multiple phones for multiple TRX. (use multiple ARFCN) Then I looked commit 50dd2b33d80902f3c0bc30e5cadb3c66a059f208 *Add option to transceiver application, to use second phone for TS 1* @@ -43,6 +43,7 @@ void *l23_ctx = NULL; static int arfcn_sync = 0; static int daemonize = 0; +static int second_phone = 0; static void print_help(char *argv[]) { @@ -56,6 +57,7 @@ static void print_help(char *argv[]) " -s --disable-color Don't use colors in stderr log output\n" " -a --arfcn-sync ARFCN Set ARFCN to sync to\n" " -p --arfcn-sync-pcs The ARFCN above is PCS\n" + " -2 --second-phone Use second phone for TS 1\n" ); } @@ -71,9 +73,10 @@ static void handle_options(int argc, char **argv, struct app_state *as) { "disable-color", 0, 0, 's' }, { "arfcn-sync", 1, 0, 'a' }, { "arfcn-sync-pcs", 0, 0, 'p' }, + { "second-phone", 0, 0, '2' }, }; - c = getopt_long(argc, argv, "hd:e:Dsa:p", + c = getopt_long(argc, argv, "hd:e:Dsa:p2", long_options, &option_idx); if (c == -1) @@ -103,6 +106,9 @@ static void handle_options(int argc, char **argv, struct app_state *as) case 'e': log_set_log_level(as->stderr_target, atoi(optarg)); break; + case '2': + second_phone = 1; + break; default: fprintf(stderr, "Unknow option %s\n", optarg); exit(0); @@ -172,6 +178,23 @@ int main(int argc, char *argv[]) /* Reset phone */ l1ctl_tx_reset_req(&as->l1l[0], L1CTL_RES_T_FULL); + if (second_phone) { + /* Establish l1ctl link */ + rv = l1l_open(&as->l1l[1], "/tmp/osmocom_l2.2", l1ctl_recv, &as->l1l[1]); + if (rv) + exit(-1); + as->l1l[1].trx = as->trx[0]; + as->l1l[1].as = as; + as->l1l[1].tx_mask = 0x02; /* TS 1 */ + as->l1l[1].rx_mask = 0x02; /* TS 1 */ + as->l1l[0].tx_mask = 0xe1; /* TS 5,6,7,0 */ + as->l1l[0].rx_mask = 0x01; /* TS 0 */ + as->trx[0]->l1l[1] = &as->l1l[1]; + + /* Reset phone */ + l1ctl_tx_reset_req(&as->l1l[1], L1CTL_RES_T_FULL); + } + if (daemonize) { rv = osmo_daemonize(); if (rv < 0) { how to add third_phone for TS 2??? -- View this message in context: http://baseband-devel.722152.n3.nabble.com/OpenBTS-OsmocomBB-Asterisk-tp4026... Sent from the baseband-devel mailing list archive at Nabble.com.
On Mon, Jul 7, 2014 at 3:55 PM, trixbox.t <trixbox.t@yandex.ru> wrote:
how to add third_phone for TS 2???
One would have to add at least the code that accepts the -3, -4, etc option on the command line and set up the transceiver data structures as appropriate. It is possible that more work beyond this is needed; I haven't looked at it closely yet. Cheers, Rusty D
Thank you! Seems logical, but not working... can't understand the meaning of the string: as -> l1[0].tx_mask = 0xdf /* TS 5,6,7,0 */ ??? was as->l1l[0].tx_mask = 0xe3; /* TS 5,6,7,0,1 */ then as->l1l[0].tx_mask = 0xe1; /* TS 5,6,7,0 */ what does 5,6,7,0,1 and why they don't ordered, and where 2,3,4 ??? I changed the line struct l1ctl_link l1l[3]; and line struct trx *trx[3]; in the app.h , otherwise have been seg.fault... /regards alex 09.07.2014, 23:37, "Erich Dachleger" <edachleger@yahoo.com>:
From http://lists.osmocom.org/pipermail/osmocom-commitlog/2013-February/003570.ht... I read : "Calypso BTS uses tx_mask and rx_mask to define which slots to TX or RX"
Then, when looking at the case for 3 phones and trying to modify tx_mask and rx_mask for TS 2 could it be something like this?
as -> l1[2].tx_mask=0x03 /* TS 2 */ as -> l1[2].rx_mask=0x03 /* TS 2 */ as -> l1[1].tx_mask=0x02 /* TS 1 */ as -> l1[1].rx_mask=0x02 /* TS 1 */ as -> l1[0].tx_mask=0xdf /* TS 5,6,7,0 */ as -> l1[0].rx_mask=0x01 /* TS 0 */
/regards erich
Den Mandag, 7. juli 2014 23.12 skrev Rusty Dekema <rdekema@gmail.com>:
On Mon, Jul 7, 2014 at 3:55 PM, trixbox.t <trixbox.t@yandex.ru> wrote:
how to add third_phone for TS 2???
One would have to add at least the code that accepts the -3, -4, etc option on the command line and set up the transceiver data structures as appropriate. It is possible that more work beyond this is needed; I haven't looked at it closely yet.
Cheers, Rusty D
hi see this site http://www.mail-archive.com/baseband-devel@lists.osmocom.org/msg00095.html sylvan respond some your Question are you get respond for management three phone? _______________________ -- View this message in context: http://baseband-devel.722152.n3.nabble.com/OpenBTS-OsmocomBB-Asterisk-tp4026... Sent from the baseband-devel mailing list archive at Nabble.com.
However a third socket, osmocom_l2.3 is established after connecting third phone and launching the trx-firmware, but transceiver says: invalid option -- '3'. -- Sent from: http://baseband-devel.722152.n3.nabble.com/
Hello!I tried all suggestions and I still have a question "how to connect 3 phoneto transceiver ?"i.e.1. phone - # osmocon -p /dev/ttyUSB0 -m c123xor -c path_to/trx.highram.bin-r 99 2. phone - # osmocon -p /dev/ttyUSB1 -s /tmp/osmocom_l2.2 -m c123xor -cpath_to/trx.highram.bin -r 993. phone - # osmocon -p /dev/ttyUSB2 -s /tmp/osmocom_l2.3 -m c123xor -cpath_to/trx.highram.bin -r 99and transceiver -e 5 -r 99 -3what I need to change in osmocom-bb2/src/host/layer23/src/transceiver/, to get it working???thank you all !!! hossein wrote
hi see this site http://www.mail-archive.com/baseband-devel@lists.osmocom.org/msg00095.htmlsy... respond some your Questionare you get respond for management three phone? _______________________
-- Sent from: http://baseband-devel.722152.n3.nabble.com/
participants (6)
-
al red -
Erich Dachleger -
hossein -
morad00077 -
Rusty Dekema -
trixbox.t