From edachleger at yahoo.com Tue Aug 1 09:44:41 2017 From: edachleger at yahoo.com (Erich Dachleger) Date: Tue, 1 Aug 2017 09:44:41 +0000 (UTC) Subject: nano 3g s8 References: <1131472750.4957826.1501580681351.ref@mail.yahoo.com> Message-ID: <1131472750.4957826.1501580681351@mail.yahoo.com> Hi,Does anybody now if the nano 3g s8 is available anywhere. They seem to be out of stock on ebay. Regards -------------- next part -------------- An HTML attachment was scrubbed... URL: From antgorka at gmail.com Wed Aug 2 18:00:38 2017 From: antgorka at gmail.com (Anton Gorbachev) Date: Wed, 2 Aug 2017 21:00:38 +0300 Subject: RRLP Message-ID: Dear developers, I found that RRLP requests are possible within OsmoNITB. http://security.osmocom.org/trac/wiki/RRLP The popular Free Software implementations of the GSM network ?OpenBSC and ?OpenBTS both support RRLP inquiries to mobile phones And I found it's possible to acrivate some setting in OnmoNITB but how can I do the actual request? I cannot find anything in the user manual, vty manual or in the menu... Thanks in advance! -------------- next part -------------- An HTML attachment was scrubbed... URL: From axilirator at gmail.com Thu Aug 3 11:25:38 2017 From: axilirator at gmail.com (Vadim Yanitskiy) Date: Thu, 3 Aug 2017 17:25:38 +0600 Subject: RRLP Message-ID: Hi, > And I found it's possible to acrivate some setting in > OnmoNITB but how can I do the actual request? I cannot > find anything in the user manual, vty manual or in the menu... This request is being sent automatically every time when a dedicated channel between MS and BTS is established. With best regards, Vadim Yanitskiy. -------------- next part -------------- An HTML attachment was scrubbed... URL: From mawais.aslam985 at gmail.com Tue Aug 15 09:46:29 2017 From: mawais.aslam985 at gmail.com (Muhammad Awais Aslam) Date: Tue, 15 Aug 2017 14:46:29 +0500 Subject: Fwd: OSMOCOM-BB HandOver In-Reply-To: References: <4B0B2FB7-BDA7-428F-B9DA-C0AE28F2C912@gnumonks.org> Message-ID: Hi, We have been working on the handover feature in OsmocomBB and have managed to make some progress including SB/BSIC detection in dedicated mode which was not previously being successfully done in firmware. I wanted to share it and seek guidance on the last bit of handover implementation on which we are stuck. I hope someone would be able to help us or make use of our work. We took code related to handover from the osmocom-bb jolly branch by manually adding/deleting stuff in the master branch as updating to the latest copy was giving us issues. We added code from the ?Safely change TPU offset on TS change or sync change? commit till the ?Use only sel_si for information about the current cell? commit. Using the handover code in the jolly branch and after making the changes explained below we were able to obtain the handover command from the BTS. The synchronized handover case works sometimes though still not every time, however the non-synchronized case doesn't work at all as we are not able to get the physical information command from the new cell. I'll explain the changes/additions we made to achieve this. Firstly, we noted that in dedicated mode SB burst was not being detected. Changes were required at three main places in order to correctly perform FB/SB detection: - It was seen that the results for SB were being read from DSP API location dsp_api.db_r->a_sch which is for the idle mode. The results had to be read from the dsp_api.ndb->a_sch26 location for the dedicated case if TCH_SB_DSP_TASK is used. - After reading the FB we needed to update the quarter-bit offset of the TPU using the TOA of the FB to sync it with the start of frame of the neighbour cell in order to catch the SB (by changing the vaule of l1s.tpu_offset using the TOA of the FB). - Frequency compensation needed to be performed using the afc_correct function before reading the SB. * We actually kind of cheated a bit by adding 3 frames to the original idle frame in order to give us more time to perform FB/SB detection including the synchronizations mentioned above. This was because we weren't that proficient with the code and someone with more understanding could do this better. The call did not get dropped. We used the initial added ?idle? frame to perform the quarter-bit and frequency compensation which was reversed in the idle frame with the response function to tune back to the serving cell. These things, when added to the code did the trick and BSIC of the neighbours was obtained. Once the BSICs were decoded the measurement report sent to the BTS became meaningful and the handover command was received. Upon receiving handover command, access bursts needed to be sent on the new channel which again was not currently being implemented properly as in order to tune to the new cell we needed to know its quarter-bit offset for start of frame, frequency compensation and absolute frame number which were not previously being obtained. Now that we were able to detect FB and SB these values were stored for the neighbours following detection of these bursts and were used to tune to a neighbour cell in case of a handover to it before the sending of access bursts. However, here is where we are stuck. We were expecting a physical information message following the access bursts but were not able to receive it due to which the handover failed. If only that could be achieved we believe handover should be successful. Either we are not syncing properly to the new cell or we might not be following GSM protocol properly. We also might not be reading the FACCH properly for physical information message after tuning to the new cell as we couldn't really understand that bit very well. We wanted someone expertise on this matter and were hoping our work could be of use. We were more interested in getting the work done first up. Best Regards, M. Awais Aslam -------------- next part -------------- An HTML attachment was scrubbed... URL: From msuraev at sysmocom.de Tue Aug 15 11:40:02 2017 From: msuraev at sysmocom.de (Max) Date: Tue, 15 Aug 2017 13:40:02 +0200 Subject: Fwd: OSMOCOM-BB HandOver In-Reply-To: References: <4B0B2FB7-BDA7-428F-B9DA-C0AE28F2C912@gnumonks.org> Message-ID: <02ad8a41-0952-91ca-4723-c924c6bdc635@sysmocom.de> Hi! Great to see you working on this. Is your current work-in-progress code published somewhere? That would make it easier for people to comment on it. Also, you can probably split out some patches/fixes and send them for review to gerrit already - see https://osmocom.org/projects/cellular-infrastructure/wiki/Gerrit for details. -- Max Suraev http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Director: Harald Welte From tyruskam at gmail.com Thu Aug 24 14:46:08 2017 From: tyruskam at gmail.com (ty) Date: Thu, 24 Aug 2017 17:46:08 +0300 Subject: Osmocombb on Ubuntu 16.04 Message-ID: Hi. My name is tyrus and I have been working with OsmocomBB since 2014 but had given it a break. I decided to go back to the project only that this time I am running a machine on Ubuntu 16.04 LTS. I get the following error during the make stage of the installation: libmobile.a(gsm48_rr.o): In function `gsm48_rr_enc_cm3': */home/tyrus/osmocom-bb/src/host/layer23/src/mobile/gsm48_rr.c:1210: undefined reference to `bitvec_fill'* *libmobile.a(vty_interface.o): In function `cfg_ms_rename':* */home/tyrus/osmocom-bb/src/host/layer23/src/mobile/vty_interface.c:1283: undefined reference to `osmo_talloc_replace_string'* collect2: error: ld returned 1 exit status Makefile:377: recipe for target 'mobile' failed make[3]: *** [mobile] Error 1 make[3]: Leaving directory '/home/tyrus/osmocom-bb/src/host/layer23/src/mobile' Makefile:322: recipe for target 'all-recursive' failed make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory '/home/tyrus/osmocom-bb/src/host/layer23/src' Makefile:348: recipe for target 'all-recursive' failed make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory '/home/tyrus/osmocom-bb/src/host/layer23' Makefile:84: recipe for target 'host/layer23/layer23' failed make: *** [host/layer23/layer23] Error 2 Anyone else experienced this? I have *gcc-arm-none-eabi* toolchain installed Much appreciated. -ty -------------- next part -------------- An HTML attachment was scrubbed... URL: From laforge at gnumonks.org Thu Aug 24 15:32:54 2017 From: laforge at gnumonks.org (Harald Welte) Date: Thu, 24 Aug 2017 17:32:54 +0200 Subject: Osmocombb on Ubuntu 16.04 In-Reply-To: References: Message-ID: <0E79A3A0-7F68-44B8-8204-D48ABFB1EA44@gnumonks.org> Your libosmocore on the host pc is too old -- Sent from a mobile device. Please excuse my brevity. From tyruskam at gmail.com Thu Aug 24 16:03:51 2017 From: tyruskam at gmail.com (ty) Date: Thu, 24 Aug 2017 19:03:51 +0300 Subject: Osmocombb on Ubuntu 16.04 In-Reply-To: <0E79A3A0-7F68-44B8-8204-D48ABFB1EA44@gnumonks.org> References: <0E79A3A0-7F68-44B8-8204-D48ABFB1EA44@gnumonks.org> Message-ID: Thanks Harald for your quick response. I just updated the libosmocore version and run make again, this time with a different error. usr/bin/ld: main.o: undefined reference to symbol '_talloc_zero_array@ @TALLOC_2.0.2' //usr/lib/i386-linux-gnu/libtalloc.so.2: error adding symbols: DSO missing from command line collect2: error: ld returned 1 exit status Makefile:388: recipe for target 'bcch_scan' failed I've tried adding the math library to configure.ac but it still fails. Many thanks -tyrus On Thu, Aug 24, 2017 at 6:32 PM, Harald Welte wrote: > Your libosmocore on the host pc is too old > -- > Sent from a mobile device. Please excuse my brevity. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From pespin at sysmocom.de Thu Aug 24 16:21:47 2017 From: pespin at sysmocom.de (Pau Espin Pedrol) Date: Thu, 24 Aug 2017 18:21:47 +0200 Subject: Osmocombb on Ubuntu 16.04 In-Reply-To: References: <0E79A3A0-7F68-44B8-8204-D48ABFB1EA44@gnumonks.org> Message-ID: <00a140a8-5220-d982-1b0b-df8fb16c1c63@sysmocom.de> On 24/08/17 18:03, ty wrote: > Thanks Harald for your quick response. I just updated the libosmocore > version and run make again, this time with a different error. > > usr/bin/ld: main.o: undefined reference to symbol > '_talloc_zero_array@@TALLOC_2.0.2' > //usr/lib/i386-linux-gnu/libtalloc.so.2: error adding symbols: DSO > missing from command line > collect2: error: ld returned 1 exit status > Makefile:388: recipe for target 'bcch_scan' failed > > I've tried adding the math library to configure.ac > but it still fails. It seems the libtalloc installed in your host pc is too old. I have libtalloc.2.1.10 and the symbol is there: $ strings /usr/lib/libtalloc.so.2.1.10 | grep _talloc_zero_array _talloc_zero_array Please make sure the libtalloc in your system has that symbol in, otherwise update it to a newer version. You can check through git log to see when was that symbol added, and infer from that which minimum libtalloc verison you need. I guess we should be checking that during configure time in osmocom-bb. -- - Pau Espin Pedrol http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Director: Harald Welte From tyruskam at gmail.com Fri Aug 25 11:15:19 2017 From: tyruskam at gmail.com (ty) Date: Fri, 25 Aug 2017 14:15:19 +0300 Subject: Osmocombb on Ubuntu 16.04 In-Reply-To: <00a140a8-5220-d982-1b0b-df8fb16c1c63@sysmocom.de> References: <0E79A3A0-7F68-44B8-8204-D48ABFB1EA44@gnumonks.org> <00a140a8-5220-d982-1b0b-df8fb16c1c63@sysmocom.de> Message-ID: Hi Pau Much appreciate your response. I did update the version of libtalloc and I can confirm it is available after running the following; tyrus at the-jedi-council:~/osmocom-bb/src$ strings /usr/lib/libtalloc.so.2.1.10 | grep _talloc_zero_array _talloc_zero_array _talloc_zero_array However, the same error persists at the same break point. On Thu, Aug 24, 2017 at 7:21 PM, Pau Espin Pedrol wrote: > > > On 24/08/17 18:03, ty wrote: > >> Thanks Harald for your quick response. I just updated the libosmocore >> version and run make again, this time with a different error. >> >> usr/bin/ld: main.o: undefined reference to symbol '_talloc_zero_array@ >> @TALLOC_2.0.2' >> //usr/lib/i386-linux-gnu/libtalloc.so.2: error adding symbols: DSO >> missing from command line >> collect2: error: ld returned 1 exit status >> Makefile:388: recipe for target 'bcch_scan' failed >> >> I've tried adding the math library to configure.ac >> but it still fails. >> > > It seems the libtalloc installed in your host pc is too old. > > I have libtalloc.2.1.10 and the symbol is there: > $ strings /usr/lib/libtalloc.so.2.1.10 | grep _talloc_zero_array > _talloc_zero_array > > Please make sure the libtalloc in your system has that symbol in, > otherwise update it to a newer version. You can check through git log to > see when was that symbol added, and infer from that which minimum libtalloc > verison you need. I guess we should be checking that during configure time > in osmocom-bb. > > -- > - Pau Espin Pedrol http://www.sysmocom.de/ > ======================================================================= > * sysmocom - systems for mobile communications GmbH > * Alt-Moabit 93 > * 10559 Berlin, Germany > * Sitz / Registered office: Berlin, HRB 134158 B > * Geschaeftsfuehrer / Managing Director: Harald Welte > -------------- next part -------------- An HTML attachment was scrubbed... URL: From pespin at sysmocom.de Fri Aug 25 11:19:05 2017 From: pespin at sysmocom.de (Pau Espin Pedrol) Date: Fri, 25 Aug 2017 13:19:05 +0200 Subject: Osmocombb on Ubuntu 16.04 In-Reply-To: References: <0E79A3A0-7F68-44B8-8204-D48ABFB1EA44@gnumonks.org> <00a140a8-5220-d982-1b0b-df8fb16c1c63@sysmocom.de> Message-ID: On 25/08/17 13:15, ty wrote: > Hi Pau > > Much appreciate your response. I did update the version of libtalloc and > I can confirm it is available after running the following; > tyrus at the-jedi-council:~/osmocom-bb/src$ strings > /usr/lib/libtalloc.so.2.1.10 | grep _talloc_zero_array > _talloc_zero_array > _talloc_zero_array > > However, the same error persists at the same break point. > Is the build really using that new library? I see your new library is in /usr/lib/libtalloc.so.2.1.10 but it's in a different path that the old one (/usr/lib/i386-linux-gnu/libtalloc.so.2). Please provide output of the log error you have now. My guess is that it may still be taking the old one. -- - Pau Espin Pedrol http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Director: Harald Welte From tyruskam at gmail.com Fri Aug 25 14:02:26 2017 From: tyruskam at gmail.com (ty) Date: Fri, 25 Aug 2017 17:02:26 +0300 Subject: Osmocombb on Ubuntu 16.04 In-Reply-To: References: <0E79A3A0-7F68-44B8-8204-D48ABFB1EA44@gnumonks.org> <00a140a8-5220-d982-1b0b-df8fb16c1c63@sysmocom.de> Message-ID: Thanks once again Pau. I managed to fix the above error. It was a symlink issue which forced the build to use the old libtalloc. However, the build now fails with this error: arm-none-eabi-ld: section .text.exceptions VMA [0080001c,00800037] overlaps section .compal.reservedram VMA [00800000,008000fe] Makefile.inc:135: recipe for target 'board/compal_e88/hello_world.e88flash.elf' failed make[1]: *** [board/compal_e88/hello_world.e88flash.elf] Error 1 make[1]: Leaving directory '/home/tyrus/osmocom-bb/src/target/firmware' Makefile:89: recipe for target 'firmware' failed make: *** [firmware] Error 2 On Fri, Aug 25, 2017 at 2:19 PM, Pau Espin Pedrol wrote: > > > On 25/08/17 13:15, ty wrote: > >> Hi Pau >> >> Much appreciate your response. I did update the version of libtalloc and >> I can confirm it is available after running the following; >> tyrus at the-jedi-council:~/osmocom-bb/src$ strings >> /usr/lib/libtalloc.so.2.1.10 | grep _talloc_zero_array >> _talloc_zero_array >> _talloc_zero_array >> >> However, the same error persists at the same break point. >> >> > Is the build really using that new library? I see your new library is in > /usr/lib/libtalloc.so.2.1.10 but it's in a different path that the old one > (/usr/lib/i386-linux-gnu/libtalloc.so.2). Please provide output of the > log error you have now. My guess is that it may still be taking the old one. > > > -- > - Pau Espin Pedrol http://www.sysmocom.de/ > ======================================================================= > * sysmocom - systems for mobile communications GmbH > * Alt-Moabit 93 > * 10559 Berlin, Germany > * Sitz / Registered office: Berlin, HRB 134158 B > * Geschaeftsfuehrer / Managing Director: Harald Welte > -------------- next part -------------- An HTML attachment was scrubbed... URL: From laforge at gnumonks.org Thu Aug 31 06:46:43 2017 From: laforge at gnumonks.org (Harald Welte) Date: Thu, 31 Aug 2017 08:46:43 +0200 Subject: redmine e-mails broken from 08/26 through 08/31 Message-ID: <20170831064643.lyhdk5nhlahrsrsr@nataraja> Dear Osmocom community, from August 26th 06:54 UTC through August 31st 06:22 UTC our Osmocom.org redmine could not send any e-mails. This was due to a configuration file syntax error introduced by me, my apologies. If you rely on redmine e-mail notifications to the issues you have subscribed to, please double-check as related notifications during that interval were unfortunately lost. Best regards, Harald p.s.: The reason for the config change was to enable e-mail notifications from jenkins.osmocom.org (which it now has, if you want to configure e.g. post-build notification actions). -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From devilp at protonmail.com Tue Aug 8 19:28:47 2017 From: devilp at protonmail.com (Devil) Date: Tue, 08 Aug 2017 19:28:47 -0000 Subject: ccch_scan error Message-ID: Hello, I have this error when I try to choose channel of baseband near me: <000c> l1ctl.c:114 FBSB RESP: result=255 I'm using Motorola C115 Phone, flashed layer1.compalram.bin, burst_ind branch Are there any solutions of this problem? Sent with [ProtonMail](https://protonmail.com) Secure Email. -------------- next part -------------- An HTML attachment was scrubbed... URL: From asgharimohsen at yahoo.com Wed Aug 16 15:20:40 2017 From: asgharimohsen at yahoo.com (Mohsen Asghari) Date: Wed, 16 Aug 2017 15:20:40 -0000 Subject: simple question References: <137714091.2949619.1502896595308.ref@mail.yahoo.com> Message-ID: <137714091.2949619.1502896595308@mail.yahoo.com> Hi My name is Mohsen Asghari, master student in Computer EngineeringI have to create a communication center based on GSM with OpenBTS,everything is OK, I have tested osmocom-bb with SMS in vty and it was perfectbut there is call problem. in both of real and virtual network this problem is bothering me finishing my thesiscan you help me understand whats wrong with my packages and installation? it is five months that I am trying to fix this problem but I cant.in the cm-service command I have a channel release from ms which the comments shows that the problem is about there is no free socket for voice....!?_____________ yours sincerely, Mohsen Asghari -------------- next part -------------- An HTML attachment was scrubbed... URL: From olegtsss at mail.ru Thu Aug 31 16:20:59 2017 From: olegtsss at mail.ru (=?UTF-8?B?0J7Qu9C10LMg0KHRg9Cy0L7RgNC+0LI=?=) Date: Thu, 31 Aug 2017 19:20:59 +0300 Subject: =?UTF-8?B?aGVscCBtZQ==?= Message-ID: <1504196459.483934499@f415.i.mail.ru> Hello, I am from Russia, can you help me with Filter Replacement! I have to mobile, Motorolla C115 and C118. I was bye all elements to make filter replacement. Motorolla C115 look like your instruction and I was done filter replacement. Motorolla C115 nice work after it. But Motorolla C118 don`t look like in your instruction. I read:? "Different circuit Sometimes the input (at the bottom of the balun) is not with caps in series and a resistor in parallel. Instead it might be without the resistors in parallel and resistors in series. Remove the resistors and place 2x the appropriate cap in series (22 pF for GSM90, 15 pF for DCS1800". But I don`t understand what I must do. I do like my picture (?118_2.jpg), but after it Motorolla don`t work: No signal from Network. Can you help me? With Best Regards, Oleg Syvorov -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ?115.JPG Type: image/jpeg Size: 1291432 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ?118.JPG Type: image/jpeg Size: 585351 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ?118_2.JPG Type: image/jpeg Size: 1358807 bytes Desc: not available URL: From tyruskam at gmail.com Thu Aug 31 17:11:44 2017 From: tyruskam at gmail.com (ty) Date: Thu, 31 Aug 2017 20:11:44 +0300 Subject: Osmocombb on Ubuntu 16.04 In-Reply-To: References: <0E79A3A0-7F68-44B8-8204-D48ABFB1EA44@gnumonks.org> <00a140a8-5220-d982-1b0b-df8fb16c1c63@sysmocom.de> Message-ID: ?Hello. Resending after seeing Harald's email about the outage. I hadn't received a response so I suspect my mail never got delivered.? On Fri, Aug 25, 2017 at 5:02 PM, ty wrote: > Thanks once again Pau. > > I managed to fix the above error. It was a symlink issue which forced the > build to use the old libtalloc. > > However, the build now fails with this error: > > arm-none-eabi-ld: section .text.exceptions VMA [0080001c,00800037] > overlaps section .compal.reservedram VMA [00800000,008000fe] > Makefile.inc:135: recipe for target 'board/compal_e88/hello_world.e88flash.elf' > failed > make[1]: *** [board/compal_e88/hello_world.e88flash.elf] Error 1 > make[1]: Leaving directory '/home/tyrus/osmocom-bb/src/target/firmware' > Makefile:89: recipe for target 'firmware' failed > make: *** [firmware] Error 2 > > > On Fri, Aug 25, 2017 at 2:19 PM, Pau Espin Pedrol > wrote: > >> >> >> On 25/08/17 13:15, ty wrote: >> >>> Hi Pau >>> >>> Much appreciate your response. I did update the version of libtalloc and >>> I can confirm it is available after running the following; >>> tyrus at the-jedi-council:~/osmocom-bb/src$ strings >>> /usr/lib/libtalloc.so.2.1.10 | grep _talloc_zero_array >>> _talloc_zero_array >>> _talloc_zero_array >>> >>> However, the same error persists at the same break point. >>> >>> >> Is the build really using that new library? I see your new library is in >> /usr/lib/libtalloc.so.2.1.10 but it's in a different path that the old one >> (/usr/lib/i386-linux-gnu/libtalloc.so.2). Please provide output of the >> log error you have now. My guess is that it may still be taking the old one. >> >> >> -- >> - Pau Espin Pedrol http://www.sysmocom.de/ >> ======================================================================= >> * sysmocom - systems for mobile communications GmbH >> * Alt-Moabit 93 >> * 10559 Berlin, Germany >> * Sitz / Registered office: Berlin, HRB 134158 B >> * Geschaeftsfuehrer / Managing Director: Harald Welte >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From domi at tomcsanyi.net Thu Aug 31 17:06:51 2017 From: domi at tomcsanyi.net (=?utf-8?B?VG9tY3PDoW55aSwgRG9tb25rb3M=?=) Date: Thu, 31 Aug 2017 19:06:51 +0200 (CEST) Subject: simple question In-Reply-To: <137714091.2949619.1502896595308@mail.yahoo.com> References: <137714091.2949619.1502896595308.ref@mail.yahoo.com> <137714091.2949619.1502896595308@mail.yahoo.com> Message-ID: <8BBF1929-6E9A-4750-80C0-00579C67DD4D@tomcsanyi.net> Hi, Please send logs/outputs as text files (NO PICTURES please). Also if possible send small pcap files demonstrating your issue. Kind regards, Domi 2017. aug. 31. d?tummal, 19:54 id?pontban Mohsen Asghari ?rta: > Hi > My name is Mohsen Asghari, master student in Computer Engineering > I have to create a communication center based on GSM with OpenBTS, > everything is OK, I have tested osmocom-bb with SMS in vty and it was perfect > but there is call problem. in both of real and virtual network this problem is bothering me finishing my thesis > can you help me understand whats wrong with my packages and installation? > > it is five months that I am trying to fix this problem but I cant. > in the cm-service command I have a channel release from ms which the comments shows that the problem is about there is no free socket for voice....! > > _____________ > yours sincerely, > Mohsen Asghari -------------- next part -------------- An HTML attachment was scrubbed... URL: