Hi Ivan,
thanks. Will try it tomorrow and give a feedback. Thanks.
Best Regards,
--- roses are #FF0000 violets are #0000FF
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
============================================================================ "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