Hi Harald (sorry for the typo).
I think that line 10 is a log of the USSD call I made.
My configuration is: - Followed the tutorial. ( http://openbsc.osmocom.org/trac/wiki/network_from_scratch (using all configurations shown in the tutoria, except the network name, that I changed to DCG). - Using a Ettus USRP N210 - All libraries installed in my notebook, with Ubuntu 13.04 kernel 3.8.0-29-generic. - Starting osmo-nitb with the following command: osmo-nitb -c ~/.osmocom/open-bsc.cfg -l ~/.osmocom/hlr.sqlite3 -P -m -C --debug=DRLL:DCC:DMM:DRR:DRSL:DNM - I manually select the network in the Network Preferences. The phone is an old Motorola Z6.
Hope it helps. If you need more information, just ask. If you need, I can use other configurations or command options.
Best Regard,
On Sat, Aug 24, 2013 at 5:37 PM, Alexander Chemeris < alexander.chemeris@gmail.com> wrote:
Of-list: His name is "Harald", not "Herald" :)
On Sun, Aug 25, 2013 at 12:36 AM, Alexander Chemeris alexander.chemeris@gmail.com wrote:
Maicon,
Your log doesn't show any user activity, so you either (1) haven't enabled enough logging or (2) your phone is not attached to the OsmoNITB network.
If you followed instructions from http://openbsc.osmocom.org/trac/wiki/network_from_scratch, then you should have enough logging enabled. In this case we have only option (2) left and it would be great if you specify your software and hardware setup and describe the procedure you're using to select the network in your phone.
On Sat, Aug 24, 2013 at 11:46 PM, Maicon Kist maicon.kist@inf.ufrgs.br
wrote:
Hi Herald,
I'm trying to check the log messages. I'm trying to understand whats happening, but so far nothing came to my mind. I'm attaching the osmo-nitb log messages right before I call the *#100# number.
Do you have any suggestion?
PS: SMS and calls are working perfectly.
Best Regards,
On Sat, Aug 24, 2013 at 11:59 AM, Alexander Chemeris alexander.chemeris@gmail.com wrote:
On Thu, Aug 22, 2013 at 9:40 PM, Maicon Kist <maicon.kist@inf.ufrgs.br
wrote:
Is there a tutorial in how to make a USSD application work in a
OpenBSC
network? Firstly I'm want to implement a simple "Hello World" application. eg. the client enter with a valid USSD number (*something) and the "Hello
World"
application executes.
Look at the openbsc/src/libmsc/ussd.c file - it's very easy to extend it to respond to various USSD requests. It would be great if we have a kind of external API for implementing external USSD applications without touching the OsmoNITB code. Patches for this are welcome.
-- Regards, Alexander Chemeris. CEO, Fairwaves LLC / ООО УмРадио http://fairwaves.ru
-- Regards, Alexander Chemeris. CEO, Fairwaves LLC / ООО УмРадио http://fairwaves.ru
-- Regards, Alexander Chemeris. CEO, Fairwaves LLC / ООО УмРадио http://fairwaves.ru
Maicon,
On Sun, Aug 25, 2013 at 12:53 AM, Maicon Kist maicon.kist@inf.ufrgs.br wrote:
I think that line 10 is a log of the USSD call I made.
And after that your BTS restarts for some reason. Is that because you manually restart it?
Hope it helps. If you need more information, just ask. If you need, I can use other configurations or command options.
Could you enable GSMTAP in OsmoBTS by adding "-i 127.0.0.1" parameter to osmobts-trx, capture traffic on the 4729 UDP port with Wireshark/tshark and send the capture here?
It would be also helpful if you capture A-bis interface at the same capture (TCP port 3002/3003).
PS List of the various TCP/UDP ports, used by Osmocom is available here: http://openbsc.osmocom.org/trac/wiki/PortNumbers
Hi Alexander,
I didn't even notice that the BTS restarts (it wasn't me).
I will send the capture tomorrow.
Thank for all help.
Best Regards,
abc
On Sun, Aug 25, 2013 at 4:50 AM, Alexander Chemeris < alexander.chemeris@gmail.com> wrote:
Maicon,
On Sun, Aug 25, 2013 at 12:53 AM, Maicon Kist maicon.kist@inf.ufrgs.br wrote:
I think that line 10 is a log of the USSD call I made.
And after that your BTS restarts for some reason. Is that because you manually restart it?
Hope it helps. If you need more information, just ask. If you need, I can use other configurations or command options.
Could you enable GSMTAP in OsmoBTS by adding "-i 127.0.0.1" parameter to osmobts-trx, capture traffic on the 4729 UDP port with Wireshark/tshark and send the capture here?
It would be also helpful if you capture A-bis interface at the same capture (TCP port 3002/3003).
PS List of the various TCP/UDP ports, used by Osmocom is available here: http://openbsc.osmocom.org/trac/wiki/PortNumbers
-- Regards, Alexander Chemeris. CEO, Fairwaves LLC / ООО УмРадио http://fairwaves.ru
Hi Alexander,
I didn't even notice that the BTS restarts (it wasn't me).
I will send the capture as soon as possible.
Thank for all help.
Best Regards,
On Sun, Aug 25, 2013 at 4:50 AM, Alexander Chemeris < alexander.chemeris@gmail.com> wrote:
Maicon,
On Sun, Aug 25, 2013 at 12:53 AM, Maicon Kist maicon.kist@inf.ufrgs.br wrote:
I think that line 10 is a log of the USSD call I made.
And after that your BTS restarts for some reason. Is that because you manually restart it?
Hope it helps. If you need more information, just ask. If you need, I can use other configurations or command options.
Could you enable GSMTAP in OsmoBTS by adding "-i 127.0.0.1" parameter to osmobts-trx, capture traffic on the 4729 UDP port with Wireshark/tshark and send the capture here?
It would be also helpful if you capture A-bis interface at the same capture (TCP port 3002/3003).
PS List of the various TCP/UDP ports, used by Osmocom is available here: http://openbsc.osmocom.org/trac/wiki/PortNumbers
-- Regards, Alexander Chemeris. CEO, Fairwaves LLC / ООО УмРадио http://fairwaves.ru
Hi Alexander,
attached is the capture realized. I started the capture and realized two USSD calls. If you need something, just ask.
Beset Regards,
On Mon, Aug 26, 2013 at 7:51 AM, Maicon Kist maicon.kist@inf.ufrgs.brwrote:
Hi Alexander,
I didn't even notice that the BTS restarts (it wasn't me).
I will send the capture as soon as possible.
Thank for all help.
Best Regards,
On Sun, Aug 25, 2013 at 4:50 AM, Alexander Chemeris < alexander.chemeris@gmail.com> wrote:
Maicon,
On Sun, Aug 25, 2013 at 12:53 AM, Maicon Kist maicon.kist@inf.ufrgs.br wrote:
I think that line 10 is a log of the USSD call I made.
And after that your BTS restarts for some reason. Is that because you manually restart it?
Hope it helps. If you need more information, just ask. If you need, I
can
use other configurations or command options.
Could you enable GSMTAP in OsmoBTS by adding "-i 127.0.0.1" parameter to osmobts-trx, capture traffic on the 4729 UDP port with Wireshark/tshark and send the capture here?
It would be also helpful if you capture A-bis interface at the same capture (TCP port 3002/3003).
PS List of the various TCP/UDP ports, used by Osmocom is available here: http://openbsc.osmocom.org/trac/wiki/PortNumbers
-- Regards, Alexander Chemeris. CEO, Fairwaves LLC / ООО УмРадио http://fairwaves.ru
Hi List, (sorry for the flood).
Any news about this error ? I'm planning to debug this error this weekend. But, I'm not familiar with the code and would appreciate any suggestion of where to start.
Best Regards,
On Mon, Aug 26, 2013 at 2:16 PM, Maicon Kist maicon.kist@inf.ufrgs.brwrote:
Hi Alexander,
attached is the capture realized. I started the capture and realized two USSD calls. If you need something, just ask.
Beset Regards,
On Mon, Aug 26, 2013 at 7:51 AM, Maicon Kist maicon.kist@inf.ufrgs.brwrote:
Hi Alexander,
I didn't even notice that the BTS restarts (it wasn't me).
I will send the capture as soon as possible.
Thank for all help.
Best Regards,
On Sun, Aug 25, 2013 at 4:50 AM, Alexander Chemeris < alexander.chemeris@gmail.com> wrote:
Maicon,
On Sun, Aug 25, 2013 at 12:53 AM, Maicon Kist maicon.kist@inf.ufrgs.br wrote:
I think that line 10 is a log of the USSD call I made.
And after that your BTS restarts for some reason. Is that because you manually restart it?
Hope it helps. If you need more information, just ask. If you need, I
can
use other configurations or command options.
Could you enable GSMTAP in OsmoBTS by adding "-i 127.0.0.1" parameter to osmobts-trx, capture traffic on the 4729 UDP port with Wireshark/tshark and send the capture here?
It would be also helpful if you capture A-bis interface at the same capture (TCP port 3002/3003).
PS List of the various TCP/UDP ports, used by Osmocom is available here: http://openbsc.osmocom.org/trac/wiki/PortNumbers
-- Regards, Alexander Chemeris. CEO, Fairwaves LLC / ООО УмРадио http://fairwaves.ru
Hi list,
I`m trying to discover where is the problem. So far, I`m putting some debug messages when the user makes a USSD call.
I put a debug message in the function abis_rsl.c:rsl_data_request(struct msgb *, uint8_t). I notice that OpenBSC always restarts in the "return abis_rsl_sendmsg(msg)" function call (always). Also, the debug message I pyt in the abis_rsl_sendmsg function is never printed on screen.
Right after the debug message I put in the abis_rsl.c:rsl_data_request(struct msgb *, uint8_t), this message is shown on screen: <0004> abis_rsl.c:634 (bts=0,trx=0,ts=0,ss=0) DEACTivate SACCH CMD. Curiously, right after this debug message, the abis_rsl_sendmsg function is also called.
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?
Best Regards,
On Sat, Aug 31, 2013 at 11:25 AM, Maicon Kist maicon.kist@inf.ufrgs.brwrote:
Hi List, (sorry for the flood).
Any news about this error ? I'm planning to debug this error this weekend. But, I'm not familiar with the code and would appreciate any suggestion of where to start.
Best Regards,
On Mon, Aug 26, 2013 at 2:16 PM, Maicon Kist maicon.kist@inf.ufrgs.brwrote:
Hi Alexander,
attached is the capture realized. I started the capture and realized two USSD calls. If you need something, just ask.
Beset Regards,
On Mon, Aug 26, 2013 at 7:51 AM, Maicon Kist maicon.kist@inf.ufrgs.brwrote:
Hi Alexander,
I didn't even notice that the BTS restarts (it wasn't me).
I will send the capture as soon as possible.
Thank for all help.
Best Regards,
On Sun, Aug 25, 2013 at 4:50 AM, Alexander Chemeris < alexander.chemeris@gmail.com> wrote:
Maicon,
On Sun, Aug 25, 2013 at 12:53 AM, Maicon Kist maicon.kist@inf.ufrgs.br wrote:
I think that line 10 is a log of the USSD call I made.
And after that your BTS restarts for some reason. Is that because you manually restart it?
Hope it helps. If you need more information, just ask. If you need, I
can
use other configurations or command options.
Could you enable GSMTAP in OsmoBTS by adding "-i 127.0.0.1" parameter to osmobts-trx, capture traffic on the 4729 UDP port with Wireshark/tshark and send the capture here?
It would be also helpful if you capture A-bis interface at the same capture (TCP port 3002/3003).
PS List of the various TCP/UDP ports, used by Osmocom is available here: http://openbsc.osmocom.org/trac/wiki/PortNumbers
-- Regards, Alexander Chemeris. CEO, Fairwaves LLC / ООО УмРадио http://fairwaves.ru
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.
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)
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)
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
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
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
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
============================================================================ "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
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.brwrote:
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
============================================================================
"Privacy in residential applications is a desirable marketing
option."
(ETSI EN 300 175-7Ch. A6)
-- Regards, Alexander Chemeris. CEO, Fairwaves LLC / ООО УмРадио http://fairwaves.ru
-- Regards, Ivan Kluchnikov. http://fairwaves.ru
Hi Andreas,
the output of the openbsc-trx:
((*)) | / \ OsmoBTS Using MAC address of eth0: xxxxxxx <0006> scheduler.c:212 Init scheduler for trx=0 <000a> trx_if.c:484 Open transceiver for trx=0 <000a> trx_if.c:495 Waiting for transceiver send clock % rtp bind-ip is now deprecated <0006> scheduler.c:2933 initial GSM clock received: fn=686409 <0001> oml.c:249 OC=RADIO-CARRIER INST=(00,00,ff) AVAIL STATE Power off -> OK <0001> oml.c:256 OC=RADIO-CARRIER INST=(00,00,ff) OPER STATE NULL -> Disabled <0001> oml.c:217 OC=RADIO-CARRIER INST=(00,00,ff) Tx STATE CHG REP <000d> abis.c:59 Link down, dropping message. <0001> oml.c:358 OC=RADIO-CARRIER INST=(00,00,ff) Tx SW ACT REP <000d> abis.c:59 Link down, dropping message. <0001> oml.c:249 OC=BASEBAND-TRANSCEIVER INST=(00,00,ff) AVAIL STATE Power off -> OK <0001> oml.c:217 OC=BASEBAND-TRANSCEIVER INST=(00,00,ff) Tx STATE CHG REP
I started it with: osmobts-trx -c ~/.osmocom/osmo-bts.cfg
and osmo-nitb: osmo-nitb -c ~/.osmocom/open-bsc.cfg -l ~/.osmocom/hlr.sqlite3 -P -m -C --debug=DRLL:DCC:DMM:DRR:DRSL:DNM
with lcr and the transceiver started before these commands.
The configuration files are the default provided in http://openbsc.osmocom.org/trac/wiki/network_from_scratch
PS: Calls to 995 and 993 are working perfectly.
Best Regards,
abc
On Thu, Sep 19, 2013 at 9:52 AM, Andreas Eversberg andreas@eversberg.euwrote:
Maicon Kist wrote:
<000d> abis.c:428 Connection to BSC failed
is bsc running? did you set correct ip to openbsc? what does openbsc output show when you start osmobts-trx?
Hi Andreas,
the output of the openbsc-trx:
((*)) | / \ OsmoBTS Using MAC address of eth0: xxxxxxx <0006> scheduler.c:212 Init scheduler for trx=0 <000a> trx_if.c:484 Open transceiver for trx=0 <000a> trx_if.c:495 Waiting for transceiver send clock % rtp bind-ip is now deprecated <0006> scheduler.c:2933 initial GSM clock received: fn=686409 <0001> oml.c:249 OC=RADIO-CARRIER INST=(00,00,ff) AVAIL STATE Power off -> OK <0001> oml.c:256 OC=RADIO-CARRIER INST=(00,00,ff) OPER STATE NULL -> Disabled <0001> oml.c:217 OC=RADIO-CARRIER INST=(00,00,ff) Tx STATE CHG REP <000d> abis.c:59 Link down, dropping message. <0001> oml.c:358 OC=RADIO-CARRIER INST=(00,00,ff) Tx SW ACT REP <000d> abis.c:59 Link down, dropping message. <0001> oml.c:249 OC=BASEBAND-TRANSCEIVER INST=(00,00,ff) AVAIL STATE Power off -> OK <0001> oml.c:217 OC=BASEBAND-TRANSCEIVER INST=(00,00,ff) Tx STATE CHG REP
I started it with: osmobts-trx -c ~/.osmocom/osmo-bts.cfg
and osmo-nitb: osmo-nitb -c ~/.osmocom/open-bsc.cfg -l ~/.osmocom/hlr.sqlite3 -P -m -C --debug=DRLL:DCC:DMM:DRR:DRSL:DNM
with lcr and the transceiver started before these commands.
The configuration files are the default provided in http://openbsc.osmocom.org/trac/wiki/network_from_scratch
PS: Calls to 995 and 993 are working perfectly.
Best Regards,
On Thu, Sep 19, 2013 at 9:52 AM, Andreas Eversberg andreas@eversberg.euwrote:
Maicon Kist wrote:
<000d> abis.c:428 Connection to BSC failed
is bsc running? did you set correct ip to openbsc? what does openbsc output show when you start osmobts-trx?
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
Hi Ivan,
tried it. Same problem.
Best Regards,
On Thu, Sep 19, 2013 at 10:08 AM, Ivan Kluchnikov < Ivan.Kluchnikov@fairwaves.ru> wrote:
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
-- Regards, Ivan Kluchnikov. http://fairwaves.ru
Hi list,
USSD working! The problem was with the branches used. The working configuration is:
libosmocore in branch jolly/7bit_ussd (I was using master) libosmo-abit in branch master openbsc in branch jolly/testing osmo-bts in branch jolly/trx (master didn't compile)
Thanks for all your help. If somebody wants additional tests or configs, just ask.
Best Regards,
On 19/09/2013, at 15:11, Maicon Kist maicon.kist@inf.ufrgs.br wrote:
Hi Ivan,
tried it. Same problem.
Best Regards,
On Thu, Sep 19, 2013 at 10:08 AM, Ivan Kluchnikov Ivan.Kluchnikov@fairwaves.ru wrote: 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
-- Regards, Ivan Kluchnikov. http://fairwaves.ru
-
Alexander Chemeris -
Andreas Eversberg -
Harald Welte -
Ivan Kluchnikov -
Maicon Kist -
Maicon Kist