Hi,
I have a problem with running 2 software programs OpenBSC (osmo-nitb
and osmo-sgsn).
When I run osmo-nitb:
ROOT: /media/obsc_gprs/gitrep/openbsc/openbsc/src/osmo-nitb# ./osmo-nitb
There is no such command.
Error occurred during reading below line:
logging level mi notice
<0005> bsc_init.c:496 Failed to parse the config file: 'openbsc.cfg'
______________________________________________________________
However, when I run osmo-sgsn:
ROOT: /media/obsc_gprs/gitrep/openbsc/openbsc/src/gprs# ./osmo-sgsn
<0011> gprs_ns.c:171 NSVCI=65534 Creating NS-VC
<0010> sgsn_libgtp.c:571 Failed to create GTP: -1
<0010> sgsn_main.c:348 Cannot bind/listen on GTP socket
Anybody help?
Hi All
We're selling some of our pico cell stock that has been on our shelf for a few months. We have 1 x brand new model 139 pico cell (1800 MHz GPRS), 1 x model 165g (1800 MHz GPRS/EDGE) and 1 x model 165cu (900 MHz GPRS/EDGE).
These on on offer first come first served.
Kind Regards
Stuart Baggs
Managing Director
BlueWave Communications Limited
Disclaimer: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender immediately . This message contains confidential information and is intended solely for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.
Hi Andreas, Harald,
the recent "SI generation" fix broke multi trx setups. This is because
when the first (c0) TRX is going up bts->si_valid will include SI2 and
other SIs scheduled on the BCCH and once the second trx is going up the
code decides it only needs to generate the SI5 (and more).
But si_valid still includes SI2 and it will be set on the second trx. I
have fixed it locally by setting si_valid to 0 early in the set_system_infos
routine and added a warning for this case.
How should this be properly fixed for master? Will the content of a specific
SI differ from TRX0 to TRX1 of a BTS? Should the si_valid be moved to the
trx data structure?
I have attached my local patch and would like to have a review for it.
comments? ideas?
holger
Hey guys i wanted to buy Osmo -NITB is it on sale ??
please let me know
--
Akib Sayyed
Matrix-Shell
akibsayyed(a)gmail.com
akibsayyed(a)matrixshell.com
Mob:- +91-966-514-2243
Hi all,
in case you follow the changelog, you will already have seen this
coming: OsmoNITB now has a SMPP interface for submitting MT-SMS.
This is by no means some kind of competition to a more complete SMSC
developed by other people on this list, but it was a quick solution to
a requirement of a commercial user.
You can use it to submit SMS identifying the recipient subscriber either
by his extension or his IMSI. OsmoNITB will also send SMPP ALERT
NOTIFICATION in case a previously detached subscriber comes online
again. Contrary to the spec, you don't have to subscribe ot ALERT
NOTIFICATIONS, but they will be sent to all ESME's registered.
The SMPP interface supports both store-and-forward (via database) as
well as forward/transactoin mdoe, where the SMS is attempted for
immediate delivery, not buffered and will only send a positive SUBMIT-SM
result in case it was acknowledged by the MS.
You can submit both GSM charset as well as binary messages. UCS2 is not
tested. multi-part SMS (or anything else using UDH) only works with
binary SMS at this point, i.e. GSM alphabet encoded multi-part messages
are broken.
The interface will soon be extended to also cover MO-SMS, where you
would configure a given destination address by VTY and then messages to
that address would be forwarded to the ESME.
Only SMPP 3.4 is currently supported. You will need libsmpp34 from
git://git.osmocom.org/libsmpp34.git and need to build openbsc with
'--enable-smpp'
Regards,
Harald
--
- Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
Hi all,
I have rebased jolly/sms and split it up (first use the routines that were
moved to libosmocore and that create compile errors, then begin to use the
DLSMS debug area, then the actual patches in a way that all of them compile
to allow to bisect them). I am now manually testing them with the help of
the sysmocom modem bank.
There are various issues that needs to be resolved before the 29C3 to be
able to use the code. I am just listing them here for reference.
There is a double trans_free in the new code now that will lead to segfaults
and various 'soft' failures. I am just including some log messages:
gsm0411_smc.c:308 Cannot release yet current state: WAIT_CP_ACK
gsm0411_smc.c:511 Message 0x332/1 unhandled at this state WAIT_CP_ACK.
gsm0411_smc.c:517 RX Unimplemented CP msg_type: 0x332
gsm0411_smc.c:134 TX CP-ERROR, cause 97 (Message Type doesn't exist)
gsm_04_11.c:913 Transaction contains SMS.
gsm_04_11.c:441 RP-DATA (MO) without DST or TPDU ?!?
gsm_04_11.c:420 TX: SMS RP ERROR, cause 96 (Invalid Mandatory Information)
cheers
holger
hi list,
we (ccc meber and me) are trying to get a pri access line (primary rate
isdn) this year. it will provide external connection for the poc
(eventphone) and will also allow interconnection of gsm network with the
rest of the world. it is not yet clear if we get this line, but we are
working on it. the hardware and software side is already tested in our
"labs".
for connection between poc and gsm network (openbsc), we like to use lcr
(linux-call-router via mncc interface). there are two ways to connect to
eventphone, one via isdn line (or virtual isdn over ip) and another one
via sip trunk. we like to use both ways for better testing.
the registration process for gsm extensions is already set up by
evenphone. visit https://www.eventphone.de to register your gsm
extension. for syncing eventphone's database with hlr of openbsc, i can
provide help. also i will provide helpdesk for gsm questions this year
again.
regards,
andreas