> I don't understand. This callback will be called with data you need to
write
> to the network. In case of MTP Level3 you will need to wrap that around
the
> msgb you got.
I means: is the interaction with mtp3 layer implemented (is sending sccp
data by mtp3 implemented by the library?)?
Also, what about the reception of data from mtp3 layer. is that implemented
in the sccp lib.
I am asking these questions because I see the code of mtp3 in the lib but no
significant call is present in the sccp part of the lib.
Thank you for your help.
So far three persons have indicated their interest to join
a meeting at my place.
Considering the time it takes to drive to my place, it
probably makes sense to have the meeting at the weekend
(either Saturday or Sunday) so that there is more time
for the meeting itself. I can suggest one of the following
dates for the first meeting, somewhere between 10:00 to
18:00 on each day:
25.8. (Sa) or 26.8. (Su)
1.9. (Sa) or 2.9. (Su)
8.9. (Sa) or 9.9. (Su)
So please let me know when you have time and also make
suggestions in which Osmocom topic you are interested
in so that we can have some sort of agenda for the
meeting to make best use of the time.
Best regards,
Dieter
--
Dieter Spaar, Germany spaar(a)mirider.augusta.de
Hello everyone,
I've just finnished writing together a small web interface for the OpenBSC
HLR. It allows you to modify various parameters in the database and also
provides a set of functions to modify the HLR or sending SMSes in your own
scripts.
The project is still very alpha but it seems to work reasonably good. Feel
free to give any feedback!
Screenshots and source code is available on my website:
https://stormhub.org/simplehlr/
--
*Best regards,
Peter Caprioli*
I have some questions:
1) When I start bsc_hack bsc_init.c first establishes OML link and
initializes the bts then it establishes RSL link and bts starts
broadcasting. However, it takes so much time to start the bts. Instead of
this I want to do the following: it establishes OML link at the beginning
and only once, then when i want to start broadcasting it establishes just
the RSL link and bts will start faster since i don't have to wait for OML
link. What should be done for this?
2) If i send one or two word messages from telnet interface it is okay. But
if i send a longer message the phone could't receive the end of the message
correctly(last words may be incomplete). Did any one encounter with this
problem? What is wrong with me?
3) Could I send SMS in which extension of the sender is text not integer.
For example, i want to send an information SMS that this is a test network.
For this purpose i want to send an SMS from 'OpenBSC'. I set the extension
of the first subscriber in database as text and tried to send the SMS but
SMS wasn't delivered. What should i do?
4) Can i add SMS externally to SMS table of database?
Thanks.
Jason
hi,
after having solved an LCR issue, i patched rtp_proxy.c the same way,
because it has the same issue.
1. when next_udp_port (in rtp_socket_bind) reaches 0xfffe, the bind
process will fail next time.
2. if rtp_sub_socket_bind of rtp socket succeeds and rtp_sub_socket_bind
of rtcp socket fails, the rtp socket must be re-created, because it
cannot not be bound again to the next higher port.
3. the port range will not wrap arround and start at 0, but at
RTP_PORT_BASE. (after reaching RTP_PORT_MAX)
andreas
As already mentioned, the Osmocom Meeting will
take place this Saturday, 1.9.2012 at 10:00.
Three people have confirmed that they will come,
I have send them an email with the location details.
Harald is not yet sure if he can attend.
A few suggestions for the meeting:
- I will run a GSM-1800 network with my test license so
you can try out OsmocomBB. If you are interested to
do so please bring your Osmocom phone plus Laptop with
the already installed OsmocomBB software.
- We can do some experiments with SIMtrace if there is any
interest.
- There should still be enough time for other things, we
can decide what to do during the meeting.
Best regards,
Dieter
--
Dieter Spaar, Germany spaar(a)mirider.augusta.de
All,
Apologies if this is the wrong mailing list for this question. If so,
please redirect me to the appropriate Osmocom list. Thanks!
I'm having trouble with some older 2G cellular modules. When they initiate
GPRS, the GPRS Attach Accept response from the SGSN seems to be dropped on
the floor. I thought this was because the inbound TLLI generated by the ME
was not included in the subsequent response. However, I verified that the
LLC correctly generates the response and attaches the TLLI. I'm not quite
sure why these particular 2G modules are not receiving the response as the
message seems to be correctly submitted from the SGSN to the BTS.
The result is that the GPRS state will get "stuck" on the ME side, which
will keep attempting to Attach until it gives up and issues a Detach
message (under the same TLLI).
Can anyone clue me in on what potential issues may be caused by this ME and
how/if I can patch this problem in the SGSN?
Thank you,
D
From: Pablo Neira Ayuso <pablo(a)gnumonks.org>
Hi,
This is the second version of the libosmo-abis patchset. Mostly
aiming to improve robustness and fix leaks in error paths.
I have tried to address all Holger comments, I leave two things
for my TODO list:
1) automate testing via automated testing while compilation
2) check the bfd->fd = -1 to make sure we need it in all cases
I have also intensively tested (although it was quite manual)
this changes with the IPA BSC/BTS tests, running valgrind to
check for leaks.
If you find any issue or you think it's OK, please ACK/NACK.
Thanks.
Pablo Neira Ayuso (13):
ipa: fix missing set of write_cb for IPA client connection
ipaccess: fix leak of e1inp_line
tests: e1inp_ipa_bsc_test: fix crash
ipaccess: improve error handling
tests: e1inp_ipa_bts_test: fix compilation warnings
lapd: use C99 structure initialization for profile templates
input: dahdi: use logging facilities instead of fprintf and stderr
input: dahdi: replace exit by return
input: add generic PCAP interface for LAPD
tests: fix CPU suckup e1inp_ipa_bts_test after test finish
tests: e1inp_ipa_*_test: add signal handling for process termination
tests: e1inp_ipa_*_test: fix leak of msgb in ->sign_link path
ipaccess: fix leak of IPA control messages in the BTS side
include/Makefile.am | 2 +-
include/osmocom/abis/lapd.h | 1 +
include/osmocom/abis/lapd_pcap.h | 11 ++
src/Makefile.am | 1 +
src/e1_input.c | 1 +
src/input/dahdi.c | 54 ++++++----
src/input/hsl.c | 3 -
src/input/ipa.c | 3 +
src/input/ipaccess.c | 210 ++++++++++++++++++++++++++------------
src/input/lapd.c | 66 +++++++-----
src/input/lapd_pcap.c | 159 +++++++++++++++++++++++++++++
tests/e1inp_ipa_bsc_test.c | 26 ++++-
tests/e1inp_ipa_bts_test.c | 31 +++++-
13 files changed, 443 insertions(+), 125 deletions(-)
create mode 100644 include/osmocom/abis/lapd_pcap.h
create mode 100644 src/input/lapd_pcap.c
--
1.7.10.4
The attached message was received as a bounce, but either the bounce
format was not recognized, or no member addresses could be extracted
from it. This mailing list has been configured to send all
unrecognized bounce messages to the list administrator(s).
For more information see:
https://lists.osmocom.org/mailman/admin/openbsc/bounce
From: Pablo Neira Ayuso <pablo(a)netfilter.org>
Hi,
The following patchset contain updates for libosmo-abis:
* fix for leak of e1inp_line reported by Holger.
* more robust handling of error codes in several parts of the ipaccess driver.
* minor cleanups for LAPD and dahdi, fix some compilations warnings.
* generic LAPD PCAP interface to create PCAP files containing the LAPD frames,
so far it was only possible to store the OML/RSL traces, without the LAPD
frames.
* fix crash of IPA BTS example test
If you're OK with those, let me know. I can push them myself if you want or
you can manually apply them.
Pablo Neira Ayuso (11):
ipa: fix missing set of write_cb for IPA client connection
ipaccess: fix leak of e1inp_line
tests: e1inp_ipa_bsc_test: fix crash
ipaccess: more robust error handle in receival path
ipaccess: more robust error handling in the accept patch
ipaccess: more robust error handling in the send path
tests: e1inp_ipa_bts_test: fix compilation warnings
lapd: use C99 structure initialization for profile templates
input: dahdi: use logging facilities instead of fprintf and stderr
input: dahdi: replace exit by return
input: add generic PCAP interface for LAPD
include/Makefile.am | 2 +-
include/osmocom/abis/lapd.h | 1 +
include/osmocom/abis/lapd_pcap.h | 11 +++
src/Makefile.am | 1 +
src/input/dahdi.c | 54 ++++++++-----
src/input/ipa.c | 13 +++-
src/input/ipaccess.c | 107 ++++++++++++++++++++-----
src/input/lapd.c | 66 +++++++++-------
src/input/lapd_pcap.c | 160 ++++++++++++++++++++++++++++++++++++++
tests/e1inp_ipa_bsc_test.c | 8 +-
tests/e1inp_ipa_bts_test.c | 7 +-
11 files changed, 353 insertions(+), 77 deletions(-)
create mode 100644 include/osmocom/abis/lapd_pcap.h
create mode 100644 src/input/lapd_pcap.c
--
1.7.10.4
