Hi Maicon,
It is strange, I will check with my installation. Now you can try to use more older version of libosmocore. Just checkout your libosmocore: git checkout a652abc5bf75435ba7f1c96ed914cf5805fc326f After that recompile and reinstall libosmocore, libosmo-abis, openbsc and osmo-bts.
2013/9/19 Maicon Kist maicon.kist@inf.ufrgs.br:
Hi Ivan,
tred the latest version of openbsc (jolly/testing branch), osmocore-abis (master branch) and osmo-bts (jolly/trx branch). The problem I'm having continues. When I make a USSD call, osmo-nitb and osmo-trx show this error messages:
..... <000d> abis.c:428 Connection to BSC failed <0001> oml.c:249 OC=RADIO-CARRIER INST=(00,00,ff) AVAIL STATE Off line -> OK <0001> oml.c:256 OC=RADIO-CARRIER INST=(00,00,ff) OPER STATE Disabled -> Disabled <0001> oml.c:217 OC=RADIO-CARRIER INST=(00,00,ff) Tx STATE CHG REP <000d> abis.c:501 Abis socket closed. <000d> abis.c:433 Connection to BSC failed, retrying in 5 seconds. <0006> scheduler.c:2867 No more clock from traneiver <0006> scheduler.c:236 Exit scheduler for trx=0 <0006> scheduler.c:212 Init scheduler for trx=0 <0001> oml.c:249 OC=RADIO-CARRIER INST=(00,00,ff) AVAIL STATE OK -> Off line <0001> oml.c:256 OC=RADIO-CARRIER INST=(00,00,ff) OPER STATE Disabled -> Disabled <0001> oml.c:217 OC=RADIO-CARRIER INST=(00,00,ff) Tx STATE CHG REP <000d> abis.c:59 Link down, dropping message. .....
Any help ?
Best Regards,
On Wed, Sep 18, 2013 at 2:49 PM, Maicon Kist maicon.kist@inf.ufrgs.br wrote:
Hi Ivan,
thanks. Will try it tomorrow and give a feedback. Thanks.
Best Regards,
On 18/09/2013, at 14:18, Ivan Kluchnikov Ivan.Kluchnikov@fairwaves.ru wrote:
Hi Maicon,
Pull the last version of libosmocore from master branch and after that recompile libosmo-abis, openbsc and osmo-bts.
2013/9/18 Maicon Kist maicon.kist@inf.ufrgs.br:
Hi Alexander,
can you tell me in what version of OpenBSC the USSD is working?
Thanks.
On Tue, Sep 10, 2013 at 1:57 PM, Alexander Chemeris alexander.chemeris@gmail.com wrote:
Maicon,
Sorry for dropping off the discussion - busy time here.
It seems we're seeing a similar issue here after we updated the code, so we'll check what's happening. Our older installs never had any USSD issues.
On Sat, Sep 7, 2013 at 11:02 PM, Maicon Kist maicon.kist@inf.ufrgs.br wrote:
Thanks for you reply.
I'm searching for the problem here, but is really hard for me. I captured some packets targeted to UDP port 4729. In this capture, I realize an USSD call. Whats bothering me is the packet number 37, the only with less than 83 bytes.
Does anybody know if this may be a problem ?
Thanks.
On Sat, Sep 7, 2013 at 1:48 PM, Harald Welte laforge@gnumonks.org wrote: > > Hi Maicon, > > I don't have much input, but: > > On Thu, Sep 05, 2013 at 09:41:19AM -0300, Maicon Kist wrote: >> I don't know how the OpenBSC works, but what it seems to me is that >> two >> separate threads are calling this fuction, maybe this is the >> problem >> ? >> Do >> you guys know what I can try to do next? > > OpenBSC (and much of osmocom software) is a single-thread event-loop > design, so there are no separete therads that are calling any > function. > > -- > - Harald Welte laforge@gnumonks.org > http://laforge.gnumonks.org/ > > > > ============================================================================ > "Privacy in residential applications is a desirable marketing > option." > (ETSI EN 300 175-7 > Ch. > A6)
-- Regards, Alexander Chemeris. CEO, Fairwaves LLC / ООО УмРадио http://fairwaves.ru
-- Regards, Ivan Kluchnikov. http://fairwaves.ru