<div dir="ltr">Hi Ivan,<div><br></div><div>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:</div>
<div><br></div><div>.....</div><div><div><000d> abis.c:428 Connection to BSC failed</div><div><0001> oml.c:249 OC=RADIO-CARRIER INST=(00,00,ff) AVAIL STATE Off line -> OK</div><div><0001> oml.c:256 OC=RADIO-CARRIER INST=(00,00,ff) OPER STATE Disabled -> Disabled</div>
<div><0001> oml.c:217 OC=RADIO-CARRIER INST=(00,00,ff) Tx STATE CHG REP</div><div><000d> abis.c:501 Abis socket closed.</div><div><000d> abis.c:433 Connection to BSC failed, retrying in 5 seconds.</div>
<div>
<0006> scheduler.c:2867 No more clock from traneiver</div><div><0006> scheduler.c:236 Exit scheduler for trx=0</div><div><0006> scheduler.c:212 Init scheduler for trx=0</div><div><0001> oml.c:249 OC=RADIO-CARRIER INST=(00,00,ff) AVAIL STATE OK -> Off line</div>
<div><0001> oml.c:256 OC=RADIO-CARRIER INST=(00,00,ff) OPER STATE Disabled -> Disabled</div><div><0001> oml.c:217 OC=RADIO-CARRIER INST=(00,00,ff) Tx STATE CHG REP</div><div><000d> abis.c:59 Link down, dropping message.</div>
</div><div>.....</div><div><br></div><div>Any help ?</div><div><br></div><div>Best Regards,</div><div><br></div></div><div class="gmail_extra"><br clear="all"><div></div>
<br><br><div class="gmail_quote">On Wed, Sep 18, 2013 at 2:49 PM, Maicon Kist <span dir="ltr"><<a href="mailto:maicon.kist@inf.ufrgs.br" target="_blank">maicon.kist@inf.ufrgs.br</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im HOEnZb">Hi Ivan,<br>
<br>
thanks. Will try it tomorrow and give a feedback. Thanks.<br>
<br>
Best Regards,<br>
<br>
<br>
</div><div class="im HOEnZb">On 18/09/2013, at 14:18, Ivan Kluchnikov <<a href="mailto:Ivan.Kluchnikov@fairwaves.ru">Ivan.Kluchnikov@fairwaves.ru</a>> wrote:<br>
<br>
</div><div class="HOEnZb"><div class="h5">> Hi Maicon,<br>
><br>
> Pull the last version of libosmocore from master branch and after that<br>
> recompile libosmo-abis, openbsc and osmo-bts.<br>
><br>
> 2013/9/18 Maicon Kist <<a href="mailto:maicon.kist@inf.ufrgs.br">maicon.kist@inf.ufrgs.br</a>>:<br>
>> Hi Alexander,<br>
>><br>
>> can you tell me in what version of OpenBSC the USSD is working?<br>
>><br>
>> Thanks.<br>
>><br>
>><br>
>><br>
>> On Tue, Sep 10, 2013 at 1:57 PM, Alexander Chemeris<br>
>> <<a href="mailto:alexander.chemeris@gmail.com">alexander.chemeris@gmail.com</a>> wrote:<br>
>>><br>
>>> Maicon,<br>
>>><br>
>>> Sorry for dropping off the discussion - busy time here.<br>
>>><br>
>>> It seems we're seeing a similar issue here after we updated the code,<br>
>>> so we'll check what's happening. Our older installs never had any USSD<br>
>>> issues.<br>
>>><br>
>>> On Sat, Sep 7, 2013 at 11:02 PM, Maicon Kist <<a href="mailto:maicon.kist@inf.ufrgs.br">maicon.kist@inf.ufrgs.br</a>><br>
>>> wrote:<br>
>>>> Thanks for you reply.<br>
>>>><br>
>>>> I'm searching for the problem here, but is really hard for me.<br>
>>>> I captured some packets targeted to UDP port 4729. In this capture, I<br>
>>>> realize an USSD call. Whats bothering me is the packet number 37, the<br>
>>>> only<br>
>>>> with less than 83 bytes.<br>
>>>><br>
>>>> Does anybody know if this may be a problem ?<br>
>>>><br>
>>>> Thanks.<br>
>>>><br>
>>>><br>
>>>><br>
>>>><br>
>>>><br>
>>>><br>
>>>><br>
>>>> On Sat, Sep 7, 2013 at 1:48 PM, Harald Welte <<a href="mailto:laforge@gnumonks.org">laforge@gnumonks.org</a>><br>
>>>> wrote:<br>
>>>>><br>
>>>>> Hi Maicon,<br>
>>>>><br>
>>>>> I don't have much input, but:<br>
>>>>><br>
>>>>> On Thu, Sep 05, 2013 at 09:41:19AM -0300, Maicon Kist wrote:<br>
>>>>>> I don't know how the OpenBSC works, but what it seems to me is that<br>
>>>>>> two<br>
>>>>>> separate threads are calling this fuction, maybe this is the problem<br>
>>>>>> ?<br>
>>>>>> Do<br>
>>>>>> you guys know what I can try to do next?<br>
>>>>><br>
>>>>> OpenBSC (and much of osmocom software) is a single-thread event-loop<br>
>>>>> design, so there are no separete therads that are calling any function.<br>
>>>>><br>
>>>>> --<br>
>>>>> - Harald Welte <<a href="mailto:laforge@gnumonks.org">laforge@gnumonks.org</a>><br>
>>>>> <a href="http://laforge.gnumonks.org/" target="_blank">http://laforge.gnumonks.org/</a><br>
>>>>><br>
>>>>><br>
>>>>> ============================================================================<br>
>>>>> "Privacy in residential applications is a desirable marketing option."<br>
>>>>> (ETSI EN 300 175-7<br>
>>>>> Ch.<br>
>>>>> A6)<br>
>>>><br>
>>>><br>
>>><br>
>>><br>
>>><br>
>>> --<br>
>>> Regards,<br>
>>> Alexander Chemeris.<br>
>>> CEO, Fairwaves LLC / οοο υΝςΑΔΙΟ<br>
>>> <a href="http://fairwaves.ru" target="_blank">http://fairwaves.ru</a><br>
>><br>
>><br>
><br>
><br>
><br>
> --<br>
> Regards,<br>
> Ivan Kluchnikov.<br>
> <a href="http://fairwaves.ru" target="_blank">http://fairwaves.ru</a><br>
<br>
<br>
</div></div></blockquote></div><br></div>