> 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.
On Tue, Jun 28, 2016 at 10:05:28AM +0200, Harald Welte wrote:
> [translated from german]
> is it certain that we switch a channel to PDCH only when
> gprs mode != none?
A TS can be GSM_PCHAN_TCH_F_PDCH; those are the only ones for which we
send a PDCH ACT message.
We send a PDCH ACT message
- during init (CHANNEL OML's state changed to enabled -> send PDCH ACT),
- and upon channel release ack when pchan == GSM_PCHAN_TCH_F_PDCH.
So the question is, when we receive a channel release ack, could that be
the PDCH release and we switch PDCH right back on by accident? No, because
we only receive a chan rel ack when the *TCH/F* is being released.
That is because the PDCH release is initiated "internally" from the PDCH
DEACT, and thus this condition in common/rsl.c rsl_tx_rf_rel_ack() catches
on, which existed before dyn PDCH:
if (lchan->rel_act_kind != LCHAN_REL_ACT_RSL) {
LOGP(DRSL, LOGL_NOTICE, "%s not sending REL ACK\n",
gsm_lchan_name(lchan));
return 0;
}
In rsl_rx_rf_chan_rel() the rel_act_kind is set to LCHAN_REL_ACT_RSL, but
not in the rsl_rx_dyn_pdch().
This is analogous to the ip.access way -- the ip.access nanobts replies to
a PDCH DEACT with a PDCH DEACT ACK and doesn't send a separate channel
release ack.
Maybe we could set rel_act_kind to some new LCHAN_REL_ACT_IPAC_DYN_PDCH
for clarity? (But we shouldn't actually send a release ack, to stay
compatible.)
Even though it works as-is, we should indeed add another flag check:
- We do check the flags that no ACT/DEACT is already pending;
- And we do send a PDCH DEACT only if ts->flags & TS_F_PDCH_ACTIVE;
- But we would send a PDCH ACT despite ts->flags & TS_F_PDCH_ACTIVE.
This should never happen, but it would make sense to ensure that.
~Neels
Hi all,
Just wanted to share an issue and a quick workaround I found for it in case
anyone else has the same problem. I believe a cmd2 update is causing
pySim-shell to fail. After installing it on a fresh install of Ubuntu
Server 20.04 and getting the following error when I run "python3
pySim-shell -p0":
>Using PC/SC reader interface
>Autodetected card type: sysmoUSIM-SJS1
>AIDs on card:
> USIM: a0000000871002ffffffff8907090000
>Traceback (most recent call last):
> File "pySim-shell.py", line 512, in <module>
> app = PysimApp(card, rs, opts.script)
> File "pySim-shell.py", line 59, in __init__
> super().__init__(persistent_history_file='~/.pysim_shell_history',
allow_cli_args=False, use_ipython=True, auto_load_commands=False,
command_sets=basic_commands, >startup_script=script)
>TypeError: __init__() got an unexpected keyword argument 'use_ipython'
If you run into this you can fix it by uninstalling cmd2 and reinstalling
cmd2 with "pip3 install cmd2==1.5".
Best,
Bryan
Hi,
My name is Brackley Cassinga Form DRC, we run a community network called
pamoja net where we offer gsm services using osmocom open source software
and OC Base station.
Recently I have tried to install another base station as the same installed
but I could not find any resource guiding through all the steps to take to
run NIB on a base station.
I'm currently running Ubuntu and I will appreciate if you could guide me on
the installation of BSC,hlr,MSC , in order to run a basic gsm network.
Thank you. Regards
--
*Ir Brackley heshima Casinga **Pacifique*
*CEO and Founder of kwanzatechnologie*
KwanzaTechnologies ,GlobalElectronics
+243977265291 | +243977265291 | Pcassinga(a)gmail.com/
brackley(a)ensemblepourladifference.org
www.kwantechnologies.jimdosite.com <http://www.kwantechnologies.com/> |
Skype: Brackley cassinga <https://webapp.wisestamp.com/#>
Av Semliki N 43
Hi all!
[please follow-up-to the openbsc(a)lists.osmocom.org mailing list, if
there is any discussion, we don't want to drag it over tons of mailing
lists in parallel]
Some weeks ago, I created https://osmocom.org/issues/5397 but it seems nobody
noticed the ticket or had any comments to it.
So let me post this as RFC here on the mailing list:
In the past, we had a gitolite/gitosis setup, which was fine in the
early days of git, but it means that people cannot easily create new
repositories, see who has permissions, and we cannot delegate ownership.
Even updating SSH keys requires manual interaction of a sysadmin like
me.
I would therefore suggest to migrate git.osmocom.org to gitea[1]
This would allow the following features:
* users can self-create any number of personal repositories (like gitlab/github)
* we can create 'organizations' along the line of reasonably independent
osmocom member projects like op25, who can then manage their own
repos/permissions/...
* gitea can link to redmine wiki and redmine issue trackers (rather than
using its own built-in)
For those repositories hosted in gerrit (mainly CNI), we would still
keep git.osmocom.org a read-only mirror, like we do it right now.
For those repositories not hosted in gerrit, users/projects could then
accept merge requests in gitea. Coupling this with 3rd party
authentication via github/gitlab/etc should make it easier for the
occasional contributor to submit changes.
There is a downside, of course; A lot of repo URLs have to change. Most
of our current repositories are at git.osmocom.org/project.git while
gitea follows a git.osmocom.org/organization/project.git scheme. I'm not
sure there is any way to help to mitigate this...
Any thoughts, comments?
[1] https://gitea.io/
--
- Harald Welte <laforge(a)osmocom.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
Hi Osmocom,
I'm setting up osmo-hnbgw and osm-stp ( on centos 8 ) to work with Spidercloud Hnb, and Ericsson MSC/SGSN.
Today I had a major breakthrough. I've done my first PS and CS attach, even got voice call up. But it's silent. I see in hnbgw manual that I should configure a co-located MGW instance.
I've installed the osmo-mgw, but my problem is the osmo-hnbgw config.
There is no option "mgcp" under node hnbgw, so I'm not able to do the config.
From my osmo-mgw:
OsmoHNBGW(config-hnbgw)#
OsmoHNBGW(config-hnbgw)#
OsmoHNBGW(config-hnbgw)# list
help
list [with-flags]
show vty-attributes
show vty-attributes (application|library|global)
write terminal
write file [PATH]
write memory
write
show running-config
exit
end
rnc-id <0-65535>
log-prefix (hnb-id|umts-cell-id)
iuh
iucs
iups
OsmoHNBGW(config-hnbgw)#
OsmoHNBGW(config-hnbgw)#
OsmoHNBGW(config-hnbgw)# mgcp
% Unknown command.
OsmoHNBGW(config-hnbgw)#
OsmoHNBGW(config-hnbgw)#
OsmoHNBGW(config-hnbgw)#
I'm using version
[root@tmaeurosmohnbgw osmo_hngw_rpms]# osmo-hnbgw -V
OsmoHNBGW version 1.2.1
OsmoHNBGW - Osmocom Home Node B Gateway implementation
Copyright (C) 2016 by sysmocom s.f.m.c. GmbH <info(a)sysmocom.de>
Contributions by Daniel Willmann, Harald Welte, Neels Hofmeyr
License AGPLv3+: GNU AGPL version 3 or later <http://gnu.org/licenses/agpl-3.0.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
[root@tmaeurosmohnbgw osmo_hngw_rpms]#
All help highly appreciated.
Best regards,
/Sjur
Internal
Hi,
I'm getting closer. But SCTP does not come up, both my real MSC and SGSN sends SCTP ABORT:
283 2022-03-25 08:14:08.200734109 10.30.50.124 -> 10.40.33.6 SCTP 86 INIT
284 2022-03-25 08:14:08.201189770 10.40.33.6 -> 10.30.50.124 SCTP 298 INIT_ACK
285 2022-03-25 08:14:08.201286756 10.30.50.100 -> 10.40.2.66 SCTP 86 INIT
286 2022-03-25 08:14:08.201405921 10.40.2.66 -> 10.30.50.100 SCTP 60 ABORT
287 2022-03-25 08:14:08.204033135 10.30.50.124 -> 10.40.33.6 SCTP 254 COOKIE_ECHO
288 2022-03-25 08:14:08.204405432 10.40.33.7 -> 10.30.50.124 SCTP 130 HEARTBEAT
289 2022-03-25 08:14:08.204423695 10.40.33.6 -> 10.30.50.124 SCTP 64 COOKIE_ACK
290 2022-03-25 08:14:08.204595511 10.40.33.6 -> 10.30.50.124 SCTP 64 ABORT
291 2022-03-25 08:14:08.207135400 10.30.50.124 -> 10.40.33.7 SCTP 60 ABORT
SCTP endpoints:
SGSN HnbGw MSC
-------------------------------------------------------------------------------
10.40.33.6| <---------> 10.30.40.124 |10.40.2.66
10.40.33.7| 10.30.40.100 <---------> |10.40.2.74
I suspect the source port on HnbGw:
Source: 10.30.50.100
Destination: 10.40.2.66
Stream Control Transmission Protocol, Src Port: 38989 (38989), Dst Port: 2905 (2905)
Source port: 38989
Destination port: 2905
The MSC sends ABORT as answer to SCTP-INIT. But our SGSN seems to accept INIT and COOKIE, but eventually sends ABORT.
OsmoHNBGW> show version
OsmoHNBGW 1.2.1 (OsmoHNBGW).
So a few questions:
- I tried to set local port to 2905 under asp in config file, but was rejected ( no such command ). So is there a way to set source port ?
- In MSC and SGSN we must give local and remote port for the SCTP link. Have you tested HnbGW with real Ericsson MSC and SGSN ?
- There are many parameters and timers connected to SCTP protocol:
HBInterval 3;
MaxAssociationRetransmits 10;
MaxInitRetransmits 3;
MaxPathRetransmits 5;
RTOInitial 3000;
RTOMax 6000;
RTOMin 1000;
ValCookieLife 60000;
Are these hardcoded, or could they be configured ?
Thanks,
/Sjur
Internal
Dear Osmocom community,
It's my pleasure to announce the next OsmoDevCall on
March 25, 2022 at 20:00 CET
at
https://meeting5.franken.de/b/har-xbc-bsx-wvs
In this edition, Sec and schneider will present an
"Iridium reverse engineering update".
This meeting will have the following schedule:
20:00 meet + greet
20:10 presentation as outlined above
21:00 unstructured supplementary social event [*]
Attendance is free of charge and open to anyone with an interest
in Osmocom or open source cellular technologies.
NOTE: There will be no recording of this talk, so if interested,
please make sure you don't miss it!
More information about OsmoDevCall, including the schedule
for further upcoming events can be found at
https://osmocom.org/projects/osmo-dev-con/wiki/OsmoDevCall
Looking forward to meeting you on Friday.
Best regards,
Harald
[*] this is how we started to call the "unstructured" part of osmocom
developer conferences in the past, basically where anyone can talk about
anything, no formal schedule or structure.
--
- Harald Welte <laforge(a)osmocom.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
Hi,
I've managed to install HnbGW on a Centos 8 machine.
But at startup I get many errors of type
socket.c:658 Unable to create socket: Protocol not supported
[root@tmaeurosmohnbgw osmo_hngw_rpms]# osmo-hnbgw
<0004> socket.c:658 Unable to create socket: Protocol not supported
<0010> osmo_ss7.c:1629 0: asp-asp-clnt-OsmoHNBGW: Unable to open stream client for ASP asp-clnt-OsmoHNBGW, 0.0.0.0:0 ==> 10.40.2.66:2905
<0004> socket.c:658 Unable to create socket: Protocol not supported
<0010> osmo_ss7.c:1629 0: asp-asp-clnt-OsmoHNBGW2: Unable to open stream client for ASP asp-clnt-OsmoHNBGW2, 0.0.0.0:0 ==> 10.40.33.6:2905
20220324104532635 DLGLOBAL NOTICE Available via telnet 127.0.0.1 4261 (telnet_interface.c:104)
20220324104532635 DLCTRL NOTICE CTRL at 127.0.0.1 4262 (control_if.c:1017)
20220324104532635 DRANAP NOTICE Remote IuCS SCCP addr: RI=SSN_PC,PC=0.27.4,SSN=RANAP (hnbgw_cn.c:488)
20220324104532636 DRANAP NOTICE Remote IuPS SCCP addr: RI=SSN_PC,PC=0.113.6,SSN=RANAP (hnbgw_cn.c:488)
20220324104532636 DRANAP NOTICE Local SCCP addr: RI=SSN_PC,PC=0.69.3,SSN=RANAP (hnbgw_cn.c:524)
20220324104532636 DLSCCP NOTICE OsmoHNBGW: Using SS7 instance 0, pc:0.69.3 (sccp_user.c:549)
20220324104532636 DLSCCP NOTICE OsmoHNBGW: Using AS instance msc-as (sccp_user.c:567)
20220324104532636 DLSCCP NOTICE OsmoHNBGW: Creating default route (sccp_user.c:572)
20220324104532636 DLSS7 INFO 0: Creating route: pc=0=0.0.0 mask=0x0 via AS 'msc-as' (osmo_ss7.c:830)
20220324104532636 DLSS7 INFO 0: asp-asp-clnt-OsmoHNBGW: Restarting ASP asp-clnt-OsmoHNBGW, r=10.40.2.66:2905<->l=0.0.0.0:0 (osmo_ss7.c:1596)
20220324104532638 DLGLOBAL ERROR Unable to create socket: Protocol not supported (socket.c:658)
20220324104532638 DLINP INFO [WAIT_RECONNECT] osmo_stream_cli_reconnect(): retrying in 5 seconds... (stream.c:286)
20220324104532638 DLSS7 ERROR 0: asp-asp-clnt-OsmoHNBGW: Unable to open stream client for ASP asp-clnt-OsmoHNBGW, 0.0.0.0:0 ==> 10.40.2.66:2905 (osmo_ss7.c:1629)
20220324104532638 DLSCCP NOTICE OsmoHNBGW: Using ASP instance asp-clnt-OsmoHNBGW (sccp_user.c:643)
20220324104532638 DLSS7 NOTICE 0: Creating SCCP instance (osmo_ss7.c:457)
20220324104532638 DLSCCP INFO Binding user 'SCCP Maangement' to SSN=1 PC=(no PC) (sccp_user.c:108)
20220324104532638 DLSCCP INFO Binding user 'OsmoHNBGW' to SSN=142 PC=0.69.3 (sccp_user.c:108)
20220324104532638 DRANAP NOTICE Remote SCCP addr: IuCS: RI=SSN_PC,PC=0.27.4,SSN=RANAP (hnbgw_cn.c:549)
20220324104532638 DRANAP NOTICE Remote SCCP addr: IuPS: RI=SSN_PC,PC=0.113.6,SSN=RANAP (hnbgw_cn.c:551)
20220324104532638 DHNBAP NOTICE Using RNC-Id 23 (hnbgw.c:660)
20220324104532638 DMAIN NOTICE Listening for Iuh at 10.30.50.69 29169 (hnbgw.c:665)
20220324104532640 DLGLOBAL ERROR Unable to create socket: Protocol not supported (socket.c:658)
Cannot open server: Protocol not supported
[root@tmaeurosmohnbgw osmo_hngw_rpms]#
So, does anyone know why I get this socket error ?
I use real MSC and SGSN, here's my config file:
hnbgw
iuh
local-ip 10.30.50.69
local-port 29169
iucs
remote-addr msc
iups
remote-addr sgsn
cs7 instance 0
point-code 0.69.3
asp asp-clnt-OsmoHNBGW 2905 0 m3ua
remote-ip 10.40.2.66
sctp-role client
as msc-as m3ua
asp asp-clnt-OsmoHNBGW
routing-key 2 0.69.3
sccp-address msc
routing-indicator PC
point-code 0.27.4
asp asp-clnt-OsmoHNBGW2 2905 0 m3ua
remote-ip 10.40.33.6
sctp-role client
as sgsn-as m3ua
asp asp-clnt-OsmoHNBGW2
routing-key 2 0.113.6
sccp-address sgsn
routing-indicator PC
point-code 0.113.6
log stderr
logging filter all 1
logging print extended-timestamp 1
logging print category 1
logging print category-hex 0
logging print level 1
logging print file basename last
logging level set-all info
And since I use real MSC and SGSN, I don't need to use osmo-stp, right? As the real nodes act as SCTP servers?
Internal
