24 Mar
2022
24 Mar
'22
11:55 a.m.
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