OpenBSC

openbsc@lists.osmocom.org

8 participants
4171 discussions

by Sipos Csaba

Hi Harald, I just stumbled upon your GTP load gen code on the Osmocom git. My question is: can I use this tool to "act" as an enodeb and test GTP-U performance? The issue is my S/PGW is a combo one, so if this GTP load gen tool acts as an SGSN/SGW, I cannot attach it to the network, as there is no externally accessible S5 interface, just the 2152 GTP-U port used by S1-U. Thanks! Csaba

3 years, 4 months

Some phones cant receive SMS

by Henry Caga

Hi, I would like to ask for help regarding my osmo-bsc setup. I have 2 problems as of now. 1) My setup is working fine on my phones, i can send and receive sms. However, on some phones, i can only send sms or call. But i cannot receive sms. I attached the sample logs from the phone that can receive sms and phone that cannot receive sms. I also included my config files. 2) i have a GPSDO TCXO and i wanted to use the maximum setting like setting up the 10mhz reference. what should i set or configure at the config files in order to set it? 3) Is there a way to improve my setup? Im using 50w PA and are there any settings that i have missed? Thank you Henry Phone that can receive sms ========= 20220226175408907 DRLL <0000> chan_alloc.c:240 (bts=0) channel load average is 0.00% 20220226175408907 DRLL <0000> chan_alloc.c:253 (bts=0) T3122 wait indicator set to 10 seconds 20220226175409767 DNM <0004> abis_nm.c:345 BTS 0 reported connected PCU version 0.8.0.178-b75c2 20220226175414767 DNM <0004> abis_nm.c:345 BTS 0 reported connected PCU version 0.8.0.178-b75c2 20220226175415439 DLSCCP <0020> sccp_user.c:175 Delivering N-UNITDATA.indication to SCCP User 'msc-0' 20220226175415439 DMSC <0007> osmo_bsc_sigtran.c:231 N-UNITDATA.ind(00 16 52 08 08 59 51 20 20 02 00 04 21 09 04 23 1d 63 44 1a 03 05 03 f4 ) 20220226175415439 DMSC <0007> osmo_bsc_bssap.c:1259 Rx MSC UDT: 00 16 52 08 08 59 51 20 20 02 00 04 21 09 04 23 1d 63 44 1a 03 05 03 f4 20220226175415439 DMSC <0007> osmo_bsc_bssap.c:1116 Rx MSC UDT BSSMAP PAGING 20220226175415439 DMSC <0007> osmo_bsc_bssap.c:131 Paging request from MSC BTS: 0 IMSI: '515020220004012' TMSI: '0x231d6344/589128516' LAC: 0x3f4 20220226175416335 DRSL <0003> abis_rsl.c:1383 (bts=0) CHAN RQD: reason: answer to paging (ra=0x9e, neci=0x01, chreq_reason=0x01) 20220226175416335 DRLL <0000> lchan_select.c:173 (bts=0) lchan_select_by_type(SDCCH) 20220226175416335 DRLL <0000> lchan_select.c:87 looking for lchan CCCH+SDCCH4: (bts=0,trx=0,ts=0,pchan=CCCH+SDCCH4,state=UNUSED) ss=0 is available 20220226175416335 DRSL <0003> abis_rsl.c:476 (bts=0,trx=0,ts=0,pchan=CCCH+SDCCH4,state=IN_USE) Tx RSL Channel Activate with act_type=INITIAL 20220226175416662 DMSC <0007> fsm.c:461 SUBSCR_CONN[0x558560323460]{INIT}: Allocated 20220226175416662 DMSC <0007> gsm_08_08.c:489 Tx MSC COMPL L3 20220226175416662 DRSL <0003> gsm_08_08.c:232 RR GSM48_MT_RR_PAG_RESP: TMSI-0x231D6344 matches earlier Paging from msc 0 20220226175416662 DMSC <0007> osmo_bsc_sigtran.c:308 Initializing resources for new SCCP connection to MSC 0: RI=SSN_PC,PC=0.23.1,SSN=BSSAP... 20220226175416663 DMSC <0007> gsm_08_08.c:532 SUBSCR_CONN(msc0-conn4294967295_IMSI515020220004012)[0x558560323460]{INIT}: Received Event MO-CONNECT.req 20220226175416663 DMSC <0007> osmo_bsc_sigtran.c:350 Allocated new connection id: 7 20220226175416663 DMSC <0007> osmo_bsc_sigtran.c:354 Opening new SCCP connection (id=7) to MSC: RI=SSN_PC,PC=0.23.1,SSN=BSSAP 20220226175416663 DLSCCP <0020> sccp_scoc.c:1729 Received SCCP User Primitive (N-CONNECT.request) 20220226175416663 DLSCCP <0020> fsm.c:461 SCCP-SCOC(7)[0x55856030ca50]{IDLE}: Allocated 20220226175416663 DLSCCP <0020> sccp_scoc.c:1769 SCCP-SCOC(7)[0x55856030ca50]{IDLE}: Received Event N-CONNECT.req 20220226175416663 DLSCCP <0020> sccp_scoc.c:830 SCCP-SCOC(7)[0x55856030ca50]{IDLE}: state_chg to CONN_PEND_OUT 20220226175416663 DMSC <0007> bsc_subscr_conn_fsm.c:286 SUBSCR_CONN(msc0-conn4294967295_IMSI515020220004012)[0x558560323460]{INIT}: state_chg to WAIT_CC 20220226175416664 DLSCCP <0020> sccp_scoc.c:1662 Received CO:COAK for local reference 7 20220226175416664 DLSCCP <0020> sccp_scoc.c:1695 SCCP-SCOC(7)[0x55856030ca50]{CONN_PEND_OUT}: Received Event RCOC-CONNECT_CONFIRM.ind 20220226175416664 DLSCCP <0020> sccp_scoc.c:981 SCCP-SCOC(7)[0x55856030ca50]{CONN_PEND_OUT}: state_chg to ACTIVE 20220226175416664 DLSCCP <0020> sccp_user.c:175 Delivering N-CONNECT.confirm to SCCP User 'msc-0' 20220226175416664 DMSC <0007> osmo_bsc_sigtran.c:244 N-CONNECT.cnf(7, ) 20220226175416664 DMSC <0007> osmo_bsc_sigtran.c:247 SUBSCR_CONN(msc0-conn7_IMSI515020220004012)[0x558560323460]{WAIT_CC}: Received Event MO-CONNECT.cfm 20220226175416664 DMSC <0007> bsc_subscr_conn_fsm.c:354 SUBSCR_CONN(msc0-conn7_IMSI515020220004012)[0x558560323460]{WAIT_CC}: state_chg to ACTIVE 20220226175416664 DLSCCP <0020> sccp_scoc.c:1662 Received CO:CODT for local reference 7 20220226175416664 DLSCCP <0020> sccp_scoc.c:1695 SCCP-SCOC(7)[0x55856030ca50]{ACTIVE}: Received Event RCOC-DT1.ind 20220226175416664 DLSCCP <0020> sccp_user.c:175 Delivering N-DATA.indication to SCCP User 'msc-0' 20220226175416664 DMSC <0007> osmo_bsc_sigtran.c:261 N-DATA.ind(7, 00 0b 2f 08 08 59 51 20 20 02 00 04 21 ) 20220226175416664 DMSC <0007> a_reset.c:227 A-RESET(msc-0)[0x55856030c700]{CONN}: Received Event EV_N_CONNECT 20220226175416664 DMSC <0007> osmo_bsc_bssap.c:1153 Rx MSC DT1 BSSMAP COMMON ID 20220226175416664 DMSC <0007> osmo_bsc_bssap.c:1099 SUBSCR_CONN(msc0-conn7_IMSI515020220004012)[0x558560323460]{ACTIVE}: Received Event COMMON_ID.ind 20220226175416664 DLSCCP <0020> sccp_scoc.c:1662 Received CO:CODT for local reference 7 20220226175416664 DLSCCP <0020> sccp_scoc.c:1695 SCCP-SCOC(7)[0x55856030ca50]{ACTIVE}: Received Event RCOC-DT1.ind 20220226175416664 DLSCCP <0020> sccp_user.c:175 Delivering N-DATA.indication to SCCP User 'msc-0' 20220226175416664 DMSC <0007> osmo_bsc_sigtran.c:261 N-DATA.ind(7, 01 03 26 09 01 23 01 00 07 91 44 77 58 10 06 50 00 17 20 06 d1 32 99 0c 00 00 22 20 62 71 45 51 23 07 f4 f2 9c 9e 76 9f 01 ) 20220226175416664 DMSC <0007> a_reset.c:227 A-RESET(msc-0)[0x55856030c700]{CONN}: Received Event EV_N_CONNECT 20220226175416664 DMSC <0007> osmo_bsc_bssap.c:1208 Rx MSC DTAP: 01 03 26 09 01 23 01 00 07 91 44 77 58 10 06 50 00 17 20 06 d1 32 99 0c 00 00 22 20 62 71 45 51 23 07 f4 f2 9c 9e 76 9f 01 20220226175416664 DMSC <0007> osmo_bsc_bssap.c:1232 Rx MSC DTAP, SAPI: 3 CHAN: 0 20220226175416664 DMSC <0007> osmo_bsc_bssap.c:1249 SUBSCR_CONN(msc0-conn7_IMSI515020220004012)[0x558560323460]{ACTIVE}: Received Event MT_DTAP 20220226175416664 DRLL <0000> abis_rsl.c:833 (bts=0,trx=0,ts=0,ss=0) RSL RLL ESTABLISH REQ (link_id=0x03) 20220226175416757 DRSL <0003> abis_rsl.c:1082 (bts=0,trx=0,ts=0,ss=0): meas_rep_count++=1 meas_rep_last_seen_nr=0 20220226175416907 DRLL <0000> chan_alloc.c:240 (bts=0) channel load average is 0.20% 20220226175416907 DRLL <0000> chan_alloc.c:253 (bts=0) T3122 wait indicator set to 10 seconds 20220226175417227 DRSL <0003> abis_rsl.c:1082 (bts=0,trx=0,ts=0,ss=0): meas_rep_count++=2 meas_rep_last_seen_nr=1 20220226175417839 DMSC <0007> gsm_08_08.c:548 Tx MSC DTAP LINK_ID=0x03 20220226175417839 DMSC <0007> gsm_08_08.c:554 SUBSCR_CONN(msc0-conn7_IMSI515020220004012)[0x558560323460]{ACTIVE}: Received Event MO_DTAP 20220226175417839 DMSC <0007> osmo_bsc_sigtran.c:394 Tx MSC: DTAP 20220226175417839 DMSC <0007> osmo_bsc_sigtran.c:418 Sending connection (id=7) oriented data to MSC: RI=SSN_PC,PC=0.23.1,SSN=BSSAP (01 03 02 89 04 ) 20220226175417839 DLSCCP <0020> sccp_scoc.c:1729 Received SCCP User Primitive (N-DATA.request) 20220226175417839 DLSCCP <0020> sccp_scoc.c:1769 SCCP-SCOC(7)[0x55856030ca50]{ACTIVE}: Received Event N-DATA.req 20220226175418075 DMSC <0007> gsm_08_08.c:548 Tx MSC DTAP LINK_ID=0x03 20220226175418075 DMSC <0007> gsm_08_08.c:554 SUBSCR_CONN(msc0-conn7_IMSI515020220004012)[0x558560323460]{ACTIVE}: Received Event MO_DTAP 20220226175418075 DMSC <0007> osmo_bsc_sigtran.c:394 Tx MSC: DTAP 20220226175418076 DMSC <0007> osmo_bsc_sigtran.c:418 Sending connection (id=7) oriented data to MSC: RI=SSN_PC,PC=0.23.1,SSN=BSSAP (01 03 09 89 01 06 02 00 41 02 00 00 ) 20220226175418076 DLSCCP <0020> sccp_scoc.c:1729 Received SCCP User Primitive (N-DATA.request) 20220226175418076 DLSCCP <0020> sccp_scoc.c:1769 SCCP-SCOC(7)[0x55856030ca50]{ACTIVE}: Received Event N-DATA.req 20220226175418085 DLSCCP <0020> sccp_scoc.c:1662 Received CO:CODT for local reference 7 20220226175418085 DLSCCP <0020> sccp_scoc.c:1695 SCCP-SCOC(7)[0x55856030ca50]{ACTIVE}: Received Event RCOC-DT1.ind 20220226175418085 DLSCCP <0020> sccp_user.c:175 Delivering N-DATA.indication to SCCP User 'msc-0' 20220226175418085 DMSC <0007> osmo_bsc_sigtran.c:261 N-DATA.ind(7, 01 03 02 09 04 ) 20220226175418085 DMSC <0007> a_reset.c:227 A-RESET(msc-0)[0x55856030c700]{CONN}: Received Event EV_N_CONNECT 20220226175418085 DMSC <0007> osmo_bsc_bssap.c:1208 Rx MSC DTAP: 01 03 02 09 04 20220226175418085 DMSC <0007> osmo_bsc_bssap.c:1232 Rx MSC DTAP, SAPI: 3 CHAN: 0 20220226175418085 DMSC <0007> osmo_bsc_bssap.c:1249 SUBSCR_CONN(msc0-conn7_IMSI515020220004012)[0x558560323460]{ACTIVE}: Received Event MT_DTAP 20220226175418085 DLSCCP <0020> sccp_scoc.c:1662 Received CO:CODT for local reference 7 20220226175418085 DLSCCP <0020> sccp_scoc.c:1695 SCCP-SCOC(7)[0x55856030ca50]{ACTIVE}: Received Event RCOC-DT1.ind 20220226175418085 DLSCCP <0020> sccp_user.c:175 Delivering N-DATA.indication to SCCP User 'msc-0' 20220226175418085 DMSC <0007> osmo_bsc_sigtran.c:261 N-DATA.ind(7, 00 04 20 04 01 09 ) 20220226175418085 DMSC <0007> a_reset.c:227 A-RESET(msc-0)[0x55856030c700]{CONN}: Received Event EV_N_CONNECT 20220226175418085 DMSC <0007> osmo_bsc_bssap.c:1153 Rx MSC DT1 BSSMAP CLEAR COMMAND 20220226175418085 DMSC <0007> osmo_bsc_bssap.c:473 SUBSCR_CONN(msc0-conn7_IMSI515020220004012)[0x558560323460]{ACTIVE}: Received Event CLEAR_CMD 20220226175418085 DMSC <0007> bsc_subscr_conn_fsm.c:774 SUBSCR_CONN(msc0-conn7_IMSI515020220004012)[0x558560323460]{ACTIVE}: state_chg to CLEARING 20220226175418085 DMSC <0007> bsc_subscr_conn_fsm.c:775 SUBSCR_CONN(msc0-conn7_IMSI515020220004012)[0x558560323460]{CLEARING}: Releasing all lchans (if any) after BSSMAP Clear Command 20220226175418085 DMSC <0007> lchan_fsm.c:1458 SUBSCR_CONN(msc0-conn7_IMSI515020220004012)[0x558560323460]{CLEARING}: lchan lchan(0-0-0-CCCH_SDCCH4-0)[0x55856030cee0] detaches from conn 20220226175418085 DRR <0002> gsm_04_08_rr.c:323 Sending Channel Release: Chan: Number: 0 Type: 1 RR-Cause: 0x0 'Normal event' 20220226175418085 DRSL <0003> abis_rsl.c:644 (bts=0,trx=0,ts=0,ss=0) DEACTivate SACCH CMD 20220226175418085 DRLL <0000> abis_rsl.c:857 (bts=0,trx=0,ts=0,ss=0) RSL RLL RELEASE REQ (link_id=0x03, reason=1) 20220226175418085 DMSC <0007> osmo_bsc_sigtran.c:390 Tx MSC: BSSMAP: CLEAR COMPLETE 20220226175418085 DMSC <0007> osmo_bsc_sigtran.c:418 Sending connection (id=7) oriented data to MSC: RI=SSN_PC,PC=0.23.1,SSN=BSSAP (00 01 21 ) 20220226175418085 DLSCCP <0020> sccp_scoc.c:1729 Received SCCP User Primitive (N-DATA.request) 20220226175418085 DLSCCP <0020> sccp_scoc.c:1769 SCCP-SCOC(7)[0x55856030ca50]{ACTIVE}: Received Event N-DATA.req 20220226175418085 DLSCCP <0020> sccp_scoc.c:1662 Received CO:RELRE for local reference 7 20220226175418085 DLSCCP <0020> sccp_scoc.c:1695 SCCP-SCOC(7)[0x55856030ca50]{ACTIVE}: Received Event RCOC-RELEASED.ind 20220226175418085 DLSCCP <0020> sccp_user.c:175 Delivering N-DISCONNECT.indication to SCCP User 'msc-0' 20220226175418085 DMSC <0007> osmo_bsc_sigtran.c:274 N-DISCONNECT.ind(7, , cause=768) 20220226175418085 DMSC <0007> osmo_bsc_sigtran.c:281 SUBSCR_CONN(msc0-conn7_IMSI515020220004012)[0x558560323460]{CLEARING}: Received Event DISCONNET.ind 20220226175418085 DMSC <0007> bsc_subscr_conn_fsm.c:791 SUBSCR_CONN(msc0-conn7_IMSI515020220004012)[0x558560323460]{CLEARING}: Terminating (cause = OSMO_FSM_TERM_REGULAR) 20220226175418085 DMSC <0007> bsc_subscr_conn_fsm.c:862 SUBSCR_CONN(msc0-conn7_IMSI515020220004012)[0x558560323460]{CLEARING}: FSM instance already terminating, not dispatching event LCLS_FAIL 20220226175418085 DMSC <0007> bsc_subscr_conn_fsm.c:866 SUBSCR_CONN(msc0-conn7_IMSI515020220004012)[0x558560323460]{CLEARING}: Releasing all lchans (if any) because this conn is terminating 20220226175418085 DMSC <0007> bsc_subscr_conn_fsm.c:845 SUBSCR_CONN(msc0-conn7_IMSI515020220004012)[0x558560323460]{CLEARING}: Putting bsc_subscr 20220226175418085 DMSC <0007> bsc_subscr_conn_fsm.c:791 SUBSCR_CONN(msc0-conn7_IMSI515020220004012)[0x558560323460]{CLEARING}: Freeing instance 20220226175418085 DMSC <0007> fsm.c:573 SUBSCR_CONN(msc0-conn7_IMSI515020220004012)[0x558560323460]{CLEARING}: Deallocated 20220226175418085 DLSCCP <0020> sccp_scoc.c:1070 SCCP-SCOC(7)[0x55856030ca50]{ACTIVE}: state_chg to IDLE 20220226175418085 DLSCCP <0020> sccp_scoc.c:517 SCCP-SCOC(7)[0x55856030ca50]{IDLE}: Terminating (cause = OSMO_FSM_TERM_REQUEST) 20220226175418085 DLSCCP <0020> sccp_scoc.c:517 SCCP-SCOC(7)[0x55856030ca50]{IDLE}: Freeing instance 20220226175418085 DLSCCP <0020> fsm.c:573 SCCP-SCOC(7)[0x55856030ca50]{IDLE}: Deallocated 20220226175419767 DNM <0004> abis_nm.c:345 BTS 0 reported connected PCU version 0.8.0.178-b75c2 20220226175424767 DNM <0004> abis_nm.c:345 BTS 0 reported connected PCU version 0.8.0.178-b75c2 20220226175424910 DRLL <0000> chan_alloc.c:240 (bts=0) channel load average is 3.03% 20220226175424910 DRLL <0000> chan_alloc.c:253 (bts=0) T3122 wait indicator set to 10 seconds ========= Phone that doesnt receive sms ========== 20220226173512464 DNM <0004> abis_nm.c:345 BTS 0 reported connected PCU version 0.8.0.178-b75c2 20220226173514434 DRLL <0000> chan_alloc.c:240 (bts=0) channel load average is 0.00% 20220226173514434 DRLL <0000> chan_alloc.c:253 (bts=0) T3122 wait indicator set to 10 seconds 20220226173517464 DNM <0004> abis_nm.c:345 BTS 0 reported connected PCU version 0.8.0.178-b75c2 20220226173519748 DLSCCP <0020> sccp_user.c:175 Delivering N-UNITDATA.indication to SCCP User 'msc-0' 20220226173519748 DMSC <0007> osmo_bsc_sigtran.c:231 N-UNITDATA.ind(00 16 52 08 08 59 51 20 11 27 23 70 04 09 04 38 2a bc 18 1a 03 05 03 f4 ) 20220226173519748 DMSC <0007> osmo_bsc_bssap.c:1259 Rx MSC UDT: 00 16 52 08 08 59 51 20 11 27 23 70 04 09 04 38 2a bc 18 1a 03 05 03 f4 20220226173519748 DMSC <0007> osmo_bsc_bssap.c:1116 Rx MSC UDT BSSMAP PAGING 20220226173519748 DMSC <0007> osmo_bsc_bssap.c:131 Paging request from MSC BTS: 0 IMSI: '515021172320740' TMSI: '0x382abc18/942324760' LAC: 0x3f4 20220226173522006 DRSL <0003> abis_rsl.c:1383 (bts=0) CHAN RQD: reason: answer to paging (ra=0x87, neci=0x01, chreq_reason=0x01) 20220226173522006 DRLL <0000> lchan_select.c:173 (bts=0) lchan_select_by_type(SDCCH) 20220226173522006 DRLL <0000> lchan_select.c:87 looking for lchan CCCH+SDCCH4: (bts=0,trx=0,ts=0,pchan=CCCH+SDCCH4,state=UNUSED) ss=0 is available 20220226173522006 DRSL <0003> abis_rsl.c:476 (bts=0,trx=0,ts=0,pchan=CCCH+SDCCH4,state=IN_USE) Tx RSL Channel Activate with act_type=INITIAL 20220226173522295 DMSC <0007> fsm.c:461 SUBSCR_CONN[0x56450d5e3f80]{INIT}: Allocated 20220226173522295 DMSC <0007> gsm_08_08.c:489 Tx MSC COMPL L3 20220226173522295 DRSL <0003> gsm_08_08.c:232 RR GSM48_MT_RR_PAG_RESP: TMSI-0x382ABC18 matches earlier Paging from msc 0 20220226173522295 DMSC <0007> osmo_bsc_sigtran.c:308 Initializing resources for new SCCP connection to MSC 0: RI=SSN_PC,PC=0.23.1,SSN=BSSAP... 20220226173522295 DMSC <0007> gsm_08_08.c:532 SUBSCR_CONN(msc0-conn4294967295_IMSI515021172320740)[0x56450d5e3f80]{INIT}: Received Event MO-CONNECT.req 20220226173522295 DMSC <0007> osmo_bsc_sigtran.c:350 Allocated new connection id: 5 20220226173522295 DMSC <0007> osmo_bsc_sigtran.c:354 Opening new SCCP connection (id=5) to MSC: RI=SSN_PC,PC=0.23.1,SSN=BSSAP 20220226173522295 DLSCCP <0020> sccp_scoc.c:1729 Received SCCP User Primitive (N-CONNECT.request) 20220226173522295 DLSCCP <0020> fsm.c:461 SCCP-SCOC(5)[0x56450d5e2160]{IDLE}: Allocated 20220226173522295 DLSCCP <0020> sccp_scoc.c:1769 SCCP-SCOC(5)[0x56450d5e2160]{IDLE}: Received Event N-CONNECT.req 20220226173522295 DLSCCP <0020> sccp_scoc.c:830 SCCP-SCOC(5)[0x56450d5e2160]{IDLE}: state_chg to CONN_PEND_OUT 20220226173522295 DMSC <0007> bsc_subscr_conn_fsm.c:286 SUBSCR_CONN(msc0-conn4294967295_IMSI515021172320740)[0x56450d5e3f80]{INIT}: state_chg to WAIT_CC 20220226173522296 DLSCCP <0020> sccp_scoc.c:1662 Received CO:COAK for local reference 5 20220226173522296 DLSCCP <0020> sccp_scoc.c:1695 SCCP-SCOC(5)[0x56450d5e2160]{CONN_PEND_OUT}: Received Event RCOC-CONNECT_CONFIRM.ind 20220226173522296 DLSCCP <0020> sccp_scoc.c:981 SCCP-SCOC(5)[0x56450d5e2160]{CONN_PEND_OUT}: state_chg to ACTIVE 20220226173522296 DLSCCP <0020> sccp_user.c:175 Delivering N-CONNECT.confirm to SCCP User 'msc-0' 20220226173522296 DMSC <0007> osmo_bsc_sigtran.c:244 N-CONNECT.cnf(5, ) 20220226173522296 DMSC <0007> osmo_bsc_sigtran.c:247 SUBSCR_CONN(msc0-conn5_IMSI515021172320740)[0x56450d5e3f80]{WAIT_CC}: Received Event MO-CONNECT.cfm 20220226173522296 DMSC <0007> bsc_subscr_conn_fsm.c:354 SUBSCR_CONN(msc0-conn5_IMSI515021172320740)[0x56450d5e3f80]{WAIT_CC}: state_chg to ACTIVE 20220226173522296 DLSCCP <0020> sccp_scoc.c:1662 Received CO:CODT for local reference 5 20220226173522296 DLSCCP <0020> sccp_scoc.c:1695 SCCP-SCOC(5)[0x56450d5e2160]{ACTIVE}: Received Event RCOC-DT1.ind 20220226173522296 DLSCCP <0020> sccp_user.c:175 Delivering N-DATA.indication to SCCP User 'msc-0' 20220226173522296 DMSC <0007> osmo_bsc_sigtran.c:261 N-DATA.ind(5, 00 0b 2f 08 08 59 51 20 11 27 23 70 04 ) 20220226173522296 DMSC <0007> a_reset.c:227 A-RESET(msc-0)[0x56450d5d3700]{CONN}: Received Event EV_N_CONNECT 20220226173522296 DMSC <0007> osmo_bsc_bssap.c:1153 Rx MSC DT1 BSSMAP COMMON ID 20220226173522296 DMSC <0007> osmo_bsc_bssap.c:1099 SUBSCR_CONN(msc0-conn5_IMSI515021172320740)[0x56450d5e3f80]{ACTIVE}: Received Event COMMON_ID.ind 20220226173522296 DLSCCP <0020> sccp_scoc.c:1662 Received CO:CODT for local reference 5 20220226173522296 DLSCCP <0020> sccp_scoc.c:1695 SCCP-SCOC(5)[0x56450d5e2160]{ACTIVE}: Received Event RCOC-DT1.ind 20220226173522296 DLSCCP <0020> sccp_user.c:175 Delivering N-DATA.indication to SCCP User 'msc-0' 20220226173522296 DMSC <0007> osmo_bsc_sigtran.c:261 N-DATA.ind(5, 01 03 28 09 01 25 01 00 07 91 44 77 58 10 06 50 00 19 20 0c 91 36 39 71 82 34 93 00 00 22 20 62 71 53 91 23 06 f4 f2 9c 0e 92 01 ) 20220226173522296 DMSC <0007> a_reset.c:227 A-RESET(msc-0)[0x56450d5d3700]{CONN}: Received Event EV_N_CONNECT 20220226173522296 DMSC <0007> osmo_bsc_bssap.c:1208 Rx MSC DTAP: 01 03 28 09 01 25 01 00 07 91 44 77 58 10 06 50 00 19 20 0c 91 36 39 71 82 34 93 00 00 22 20 62 71 53 91 23 06 f4 f2 9c 0e 92 01 20220226173522296 DMSC <0007> osmo_bsc_bssap.c:1232 Rx MSC DTAP, SAPI: 3 CHAN: 0 20220226173522296 DMSC <0007> osmo_bsc_bssap.c:1249 SUBSCR_CONN(msc0-conn5_IMSI515021172320740)[0x56450d5e3f80]{ACTIVE}: Received Event MT_DTAP 20220226173522296 DRLL <0000> abis_rsl.c:833 (bts=0,trx=0,ts=0,ss=0) RSL RLL ESTABLISH REQ (link_id=0x03) 20220226173522439 DRLL <0000> chan_alloc.c:240 (bts=0) channel load average is 0.20% 20220226173522439 DRLL <0000> chan_alloc.c:253 (bts=0) T3122 wait indicator set to 10 seconds 20220226173522464 DNM <0004> abis_nm.c:345 BTS 0 reported connected PCU version 0.8.0.178-b75c2 20220226173522766 DMSC <0007> gsm_08_08.c:71 Tx MSC SAPI N REJECT DLCI=0x03 20220226173522766 DMSC <0007> gsm_08_08.c:74 SUBSCR_CONN(msc0-conn5_IMSI515021172320740)[0x56450d5e3f80]{ACTIVE}: Received Event TX_SCCP 20220226173522766 DMSC <0007> osmo_bsc_sigtran.c:390 Tx MSC: BSSMAP: SAPI N REJECT 20220226173522766 DMSC <0007> osmo_bsc_sigtran.c:418 Sending connection (id=5) oriented data to MSC: RI=SSN_PC,PC=0.23.1,SSN=BSSAP (00 06 25 18 03 04 01 25 ) 20220226173522766 DLSCCP <0020> sccp_scoc.c:1729 Received SCCP User Primitive (N-DATA.request) 20220226173522766 DLSCCP <0020> sccp_scoc.c:1769 SCCP-SCOC(5)[0x56450d5e2160]{ACTIVE}: Received Event N-DATA.req 20220226173522768 DLSCCP <0020> sccp_scoc.c:1662 Received CO:CODT for local reference 5 20220226173522768 DLSCCP <0020> sccp_scoc.c:1695 SCCP-SCOC(5)[0x56450d5e2160]{ACTIVE}: Received Event RCOC-DT1.ind 20220226173522768 DLSCCP <0020> sccp_user.c:175 Delivering N-DATA.indication to SCCP User 'msc-0' 20220226173522768 DMSC <0007> osmo_bsc_sigtran.c:261 N-DATA.ind(5, 00 04 20 04 01 09 ) 20220226173522768 DMSC <0007> a_reset.c:227 A-RESET(msc-0)[0x56450d5d3700]{CONN}: Received Event EV_N_CONNECT 20220226173522768 DMSC <0007> osmo_bsc_bssap.c:1153 Rx MSC DT1 BSSMAP CLEAR COMMAND 20220226173522768 DMSC <0007> osmo_bsc_bssap.c:473 SUBSCR_CONN(msc0-conn5_IMSI515021172320740)[0x56450d5e3f80]{ACTIVE}: Received Event CLEAR_CMD 20220226173522768 DMSC <0007> bsc_subscr_conn_fsm.c:774 SUBSCR_CONN(msc0-conn5_IMSI515021172320740)[0x56450d5e3f80]{ACTIVE}: state_chg to CLEARING 20220226173522768 DMSC <0007> bsc_subscr_conn_fsm.c:775 SUBSCR_CONN(msc0-conn5_IMSI515021172320740)[0x56450d5e3f80]{CLEARING}: Releasing all lchans (if any) after BSSMAP Clear Command 20220226173522768 DMSC <0007> lchan_fsm.c:1458 SUBSCR_CONN(msc0-conn5_IMSI515021172320740)[0x56450d5e3f80]{CLEARING}: lchan lchan(0-0-0-CCCH_SDCCH4-0)[0x56450d5e4240] detaches from conn 20220226173522768 DRR <0002> gsm_04_08_rr.c:323 Sending Channel Release: Chan: Number: 0 Type: 1 RR-Cause: 0x0 'Normal event' 20220226173522768 DRSL <0003> abis_rsl.c:644 (bts=0,trx=0,ts=0,ss=0) DEACTivate SACCH CMD 20220226173522768 DMSC <0007> osmo_bsc_sigtran.c:390 Tx MSC: BSSMAP: CLEAR COMPLETE 20220226173522768 DMSC <0007> osmo_bsc_sigtran.c:418 Sending connection (id=5) oriented data to MSC: RI=SSN_PC,PC=0.23.1,SSN=BSSAP (00 01 21 ) 20220226173522768 DLSCCP <0020> sccp_scoc.c:1729 Received SCCP User Primitive (N-DATA.request) 20220226173522768 DLSCCP <0020> sccp_scoc.c:1769 SCCP-SCOC(5)[0x56450d5e2160]{ACTIVE}: Received Event N-DATA.req 20220226173522768 DLSCCP <0020> sccp_scoc.c:1662 Received CO:RELRE for local reference 5 20220226173522768 DLSCCP <0020> sccp_scoc.c:1695 SCCP-SCOC(5)[0x56450d5e2160]{ACTIVE}: Received Event RCOC-RELEASED.ind 20220226173522768 DLSCCP <0020> sccp_user.c:175 Delivering N-DISCONNECT.indication to SCCP User 'msc-0' 20220226173522768 DMSC <0007> osmo_bsc_sigtran.c:274 N-DISCONNECT.ind(5, , cause=768) 20220226173522768 DMSC <0007> osmo_bsc_sigtran.c:281 SUBSCR_CONN(msc0-conn5_IMSI515021172320740)[0x56450d5e3f80]{CLEARING}: Received Event DISCONNET.ind 20220226173522768 DMSC <0007> bsc_subscr_conn_fsm.c:791 SUBSCR_CONN(msc0-conn5_IMSI515021172320740)[0x56450d5e3f80]{CLEARING}: Terminating (cause = OSMO_FSM_TERM_REGULAR) 20220226173522768 DMSC <0007> bsc_subscr_conn_fsm.c:862 SUBSCR_CONN(msc0-conn5_IMSI515021172320740)[0x56450d5e3f80]{CLEARING}: FSM instance already terminating, not dispatching event LCLS_FAIL 20220226173522768 DMSC <0007> bsc_subscr_conn_fsm.c:866 SUBSCR_CONN(msc0-conn5_IMSI515021172320740)[0x56450d5e3f80]{CLEARING}: Releasing all lchans (if any) because this conn is terminating 20220226173522768 DMSC <0007> bsc_subscr_conn_fsm.c:845 SUBSCR_CONN(msc0-conn5_IMSI515021172320740)[0x56450d5e3f80]{CLEARING}: Putting bsc_subscr 20220226173522768 DMSC <0007> bsc_subscr_conn_fsm.c:791 SUBSCR_CONN(msc0-conn5_IMSI515021172320740)[0x56450d5e3f80]{CLEARING}: Freeing instance 20220226173522768 DMSC <0007> fsm.c:573 SUBSCR_CONN(msc0-conn5_IMSI515021172320740)[0x56450d5e3f80]{CLEARING}: Deallocated 20220226173522768 DLSCCP <0020> sccp_scoc.c:1070 SCCP-SCOC(5)[0x56450d5e2160]{ACTIVE}: state_chg to IDLE 20220226173522768 DLSCCP <0020> sccp_scoc.c:517 SCCP-SCOC(5)[0x56450d5e2160]{IDLE}: Terminating (cause = OSMO_FSM_TERM_REQUEST) 20220226173522768 DLSCCP <0020> sccp_scoc.c:517 SCCP-SCOC(5)[0x56450d5e2160]{IDLE}: Freeing instance 20220226173522768 DLSCCP <0020> fsm.c:573 SCCP-SCOC(5)[0x56450d5e2160]{IDLE}: Deallocated ======== Osmo-bts-trx config ! ! OsmoBTS () configuration saved from vty !! ! log stderr logging color 1 logging timestamp 0 logging level rsl notice logging level oml notice logging level rll notice logging level rr notice logging level meas error logging level pag error logging level l1c error logging level l1p error logging level dsp error logging level abis error logging level loop debug ! line vty no login ! phy 0 instance 0 !COMMENT HERE FOR DEFAULT JOJO osmotrx rx-gain 50 osmotrx tx-attenuation 0 !osmotrx rx-gain 10 !osmotrx tx-attenuation oml !osmotrx maxdly 20 osmotrx ip local 127.0.0.1 osmotrx ip remote 127.0.0.1 bts 0 band 900 ipa unit-id 1012 0 oml remote-ip 127.0.0.1 gsmtap-sapi ccch gsmtap-sapi pdtch !ADDED FOR TEST JOJO gsmtap-sapi bcch gsmtap-sapi rach gsmtap-sapi agch gsmtap-sapi sdcch gsmtap-sapi sacch uplink-power-target -110 trx 0 !ms-power-control osmo !power-ramp max-initial 0 dBm !power-ramp step-size 2000 dB !power-ramp step-interval 10 phy 0 instance 0 ========= Osmo-bsc config ========= ! Configuration rendered by osmo-gsm-tester log stderr logging filter all 1 logging color 1 logging print category 1 logging print extended-timestamp 1 logging level all debug line vty no login bind 127.0.0.1 ctrl bind 127.0.0.1 e1_input e1_line 0 driver ipa ipa bind 127.0.0.1 network network country code 515 mobile network code 02 encryption a5 0 neci 1 handover 0 handover window rxlev averaging 10 handover window rxqual averaging 1 handover window rxlev neighbor averaging 10 handover power budget interval 6 handover power budget hysteresis 4 handover maximum distance 9999 allow-unusable-timeslots bts 0 type sysmobts band 900 cell_identity 1012 location_area_code 1012 training_sequence_code 1 base_station_id_code 1 channel-description attach 0 !ms max power 40 cell reselection hysteresis 4 rxlev access min 0 channel allocator ascending rach tx integer 9 rach max transmission 7 ip.access unit_id 1012 0 oml ip.access stream_id 255 line 0 gprs mode none no force-combined-si trx 0 rf_locked 0 arfcn 27 !nominal power 40 nominal power 80 ! to use full TRX power, set max_power_red 0 max_power_red 0 rsl e1 tei 0 timeslot 0 phys_chan_config CCCH+SDCCH4 hopping enabled 0 timeslot 1 phys_chan_config SDCCH8 hopping enabled 0 timeslot 2 phys_chan_config TCH/F hopping enabled 0 timeslot 3 phys_chan_config TCH/F hopping enabled 0 timeslot 4 phys_chan_config TCH/F hopping enabled 0 timeslot 5 phys_chan_config TCH/F hopping enabled 0 timeslot 6 phys_chan_config TCH/F hopping enabled 0 timeslot 7 phys_chan_config PDCH hopping enabled 0 msc 0 !ip.access rtp-base 25000 no bsc-welcome-text no bsc-msc-lost-text no bsc-grace-text type normal allow-emergency allow !codec-list fr1 !amr-config 12_2k forbidden !amr-config 10_2k forbidden !amr-config 7_95k forbidden !amr-config 7_40k forbidden !amr-config 6_70k forbidden !amr-config 5_90k forbidden !amr-config 5_15k forbidden !amr-config 4_75k forbidden mgw remote-ip 127.0.0.1 mgw remote-port 2427 !mgw endpoint-range 1 31 mgw local-ip 127.0.0.1 bsc mid-call-timeout 0 ========== Osmo-msc config ========== ! ! OsmoMSC configuration saved from vty ! log stderr logging filter all 1 logging color 0 logging print category 1 logging timestamp 1 logging level all everything logging level rll notice logging level cc notice logging level mm notice logging level mm debug logging level rr notice logging level pag notice logging level msc notice logging level mgcp notice logging level ho notice logging level ref notice logging level ctrl notice logging level lglobal notice logging level llapd notice logging level linp notice logging level lmux notice logging level lmi notice logging level lmib notice logging level lsms notice logging level lctrl notice logging level lgtp notice logging level lstats notice logging level lgsup notice logging level loap notice logging level lss7 notice logging level lsccp notice logging level lsua notice logging level lm3ua notice logging level lmgcp notice logging level all debug line vty no login bind 127.0.0.1 ! network network country code 515 mobile network code 02 short name GLOBE long name GLOBE encryption a5 0 rrlp mode none mm info 1 timezone 8 0 msc mgw remote-ip 127.0.0.1 mgw remote-port 2427 mgw local-ip 127.0.0.1 !mgw endpoint-range 1 31 !mgw bts-base 8000 assign-tmsi cs7-instance-a 0 check-imei-rqd early !timer vlr T3212 1 ctrl bind 127.0.0.1 mncc-int default-codec tch-f fr default-codec tch-h hr hlr remote-ip 127.0.0.1 smpp local-tcp-port 2775 policy accept-all smpp-first esme bhat password bhat default-route

3 years, 4 months

RFC: migrating git.osmocom.org to gitea?

by Harald Welte

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)

3 years, 4 months

OSMO HnbGW MGW instance config problem

by Sjur Thomas Lien

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

3 years, 4 months

OSMO HnbGW , M3UA problems real MSC and SGSN

by Sjur Thomas Lien

Hi, I've run into problems with M3UA, getting the link up. Our MSC sends a M3UA DAUD message ( Destination Audit ), which is unknown to HnbGw. This might not be a big problem, but the MSC does not support registering of routing-key. And it looks like because MSC rejects the REG-REQ, the HnbGw restarts the signalling link by sending SCTP SHUTDOWN to MSC. I tried to drop the line routing-key in config file, but REG_REQ was sent anyway. I also tried to enter routing-key with context=0, same thing. Capturing on 'eno2' 1 2022-03-26 09:26:41.480666703 10.30.50.124 -> 10.40.33.6 SCTP 86 INIT 2 2022-03-26 09:26:41.480710694 10.30.50.100 -> 10.40.2.66 SCTP 86 INIT 3 2022-03-26 09:26:41.480971008 10.40.2.66 -> 10.30.50.100 SCTP 206 INIT_ACK 4 2022-03-26 09:26:41.481112284 10.40.33.6 -> 10.30.50.124 SCTP 298 INIT_ACK 5 2022-03-26 09:26:41.481213421 10.30.50.100 -> 10.40.2.66 SCTP 86 INIT 6 2022-03-26 09:26:41.481266735 10.40.2.66 -> 10.30.50.100 SCTP 206 INIT_ACK 7 2022-03-26 09:26:41.483522819 10.30.50.124 -> 10.40.33.6 SCTP 254 COOKIE_ECHO 8 2022-03-26 09:26:41.483629506 10.30.50.100 -> 10.40.2.66 SCTP 162 COOKIE_ECHO 9 2022-03-26 09:26:41.483690725 10.40.2.66 -> 10.30.50.100 SCTP 60 COOKIE_ACK 10 2022-03-26 09:26:41.484110760 10.40.33.6 -> 10.30.50.124 SCTP 64 COOKIE_ACK 11 2022-03-26 09:26:41.484117880 10.40.33.7 -> 10.30.50.124 SCTP 130 HEARTBEAT 12 2022-03-26 09:26:41.486512775 10.30.50.124 -> 10.40.33.7 SCTP 130 HEARTBEAT_ACK 13 2022-03-26 09:26:41.486513593 10.30.50.100 -> 10.40.2.66 M3UA (RFC 3332) 74 ASPUP 14 2022-03-26 09:26:41.486682342 10.40.2.66 -> 10.30.50.100 SCTP 66 SACK 15 2022-03-26 09:26:41.486694401 10.40.2.66 -> 10.30.50.100 M3UA (RFC 3332) 74 ASPUP_ACK 16 2022-03-26 09:26:41.488189055 10.40.2.74 -> 10.30.50.100 SCTP 78 HEARTBEAT 17 2022-03-26 09:26:41.489702157 10.30.50.100 -> 10.40.2.66 SCTP 66 SACK 18 2022-03-26 09:26:41.489730294 10.40.2.66 -> 10.30.50.100 M3UA (RFC 3332) 82 DAUD 19 2022-03-26 09:26:41.492451543 10.30.50.100 -> 10.40.2.66 M3UA (RFC 3332) 118 SACK ERR 20 2022-03-26 09:26:41.532141583 10.40.2.66 -> 10.30.50.100 SCTP 66 SACK 21 2022-03-26 09:26:42.488369158 10.40.2.74 -> 10.30.50.100 SCTP 78 HEARTBEAT 22 2022-03-26 09:26:43.491352631 10.30.50.100 -> 10.40.2.66 M3UA (RFC 3332) 110 REG_REQ 23 2022-03-26 09:26:43.491554237 10.40.2.66 -> 10.30.50.100 M3UA (RFC 3332) 142 SACK ERR 24 2022-03-26 09:26:43.688325732 10.40.2.74 -> 10.30.50.100 SCTP 78 HEARTBEAT 25 2022-03-26 09:26:43.698031665 10.30.50.100 -> 10.40.2.66 SCTP 66 SACK 26 2022-03-26 09:26:44.888336483 10.40.2.74 -> 10.30.50.100 SCTP 78 HEARTBEAT 27 2022-03-26 09:26:46.088347715 10.40.2.74 -> 10.30.50.100 SCTP 78 HEARTBEAT 28 2022-03-26 09:26:53.501539305 10.30.50.100 -> 10.40.2.66 SCTP 60 SHUTDOWN 29 2022-03-26 09:26:53.501628420 10.40.2.66 -> 10.30.50.100 SCTP 60 SHUTDOWN_ACK 30 2022-03-26 09:26:53.504324344 10.30.50.100 -> 10.40.2.66 SCTP 60 SHUTDOWN_COMPLETE ^C30 packets captured [root@tmabuotshark10 ~]# 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 52905 2905 m3ua local-ip 10.30.50.100 remote-ip 10.40.2.66 remote-ip 10.40.2.74 sctp-role client as msc-as m3ua asp asp-clnt-OsmoHNBGW sccp-address msc routing-indicator PC point-code 0.27.4 asp asp-clnt-OsmoHNBGW2 2905 2905 m3ua local-ip 10.30.50.124 remote-ip 10.40.33.6 remote-ip 10.40.33.7 sctp-role client as sgsn-as m3ua asp asp-clnt-OsmoHNBGW2 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 Log from Osmo-Hnbgw: 20220326092641479 DLGLOBAL NOTICE Available via telnet 127.0.0.1 4261 (telnet_interface.c:104) 20220326092641479 DLCTRL NOTICE CTRL at 127.0.0.1 4262 (control_if.c:1017) 20220326092641479 DRANAP NOTICE Remote IuCS SCCP addr: RI=SSN_PC,PC=0.27.4,SSN=RANAP (hnbgw_cn.c:488) 20220326092641479 DRANAP NOTICE Remote IuPS SCCP addr: RI=SSN_PC,PC=0.113.6,SSN=RANAP (hnbgw_cn.c:488) 20220326092641479 DRANAP NOTICE Local SCCP addr: RI=SSN_PC,PC=0.69.3,SSN=RANAP (hnbgw_cn.c:524) 20220326092641479 DLSCCP NOTICE OsmoHNBGW: Using SS7 instance 0, pc:0.69.3 (sccp_user.c:549) 20220326092641479 DLSCCP NOTICE OsmoHNBGW: Using AS instance msc-as (sccp_user.c:567) 20220326092641479 DLSCCP NOTICE OsmoHNBGW: Creating default route (sccp_user.c:572) 20220326092641479 DLSS7 INFO 0: Creating route: pc=0=0.0.0 mask=0x0 via AS 'msc-as' (osmo_ss7.c:830) 20220326092641479 DLSS7 INFO 0: asp-asp-clnt-OsmoHNBGW: Restarting ASP asp-clnt-OsmoHNBGW, r=(10.40.2.66|10.40.2.74):52905<->l=10.30.50.100:2905 (osmo_ss7.c:1596) 20220326092641479 DLSCCP NOTICE OsmoHNBGW: Using ASP instance asp-clnt-OsmoHNBGW (sccp_user.c:643) 20220326092641479 DLSS7 NOTICE 0: Creating SCCP instance (osmo_ss7.c:457) 20220326092641479 DLSCCP INFO Binding user 'SCCP Maangement' to SSN=1 PC=(no PC) (sccp_user.c:108) 20220326092641479 DLSCCP INFO Binding user 'OsmoHNBGW' to SSN=142 PC=0.69.3 (sccp_user.c:108) 20220326092641479 DRANAP NOTICE Remote SCCP addr: IuCS: RI=SSN_PC,PC=0.27.4,SSN=RANAP (hnbgw_cn.c:549) 20220326092641479 DRANAP NOTICE Remote SCCP addr: IuPS: RI=SSN_PC,PC=0.113.6,SSN=RANAP (hnbgw_cn.c:551) 20220326092641479 DHNBAP NOTICE Using RNC-Id 23 (hnbgw.c:660) 20220326092641479 DMAIN NOTICE Listening for Iuh at 10.30.50.69 29169 (hnbgw.c:665) 20220326092641485 DLINP INFO sizes of 'struct sctp_event_subscribe': compile-time 14, kernel: 14 (stream.c:114) 20220326092641485 DLSS7 INFO 0: asp-asp-clnt-OsmoHNBGW2: Client connected (r=10.40.33.7:2905<->l=10.30.50.124:2905) (osmo_ss7.c:1856) 20220326092641485 DLSS7 ERROR XUA_ASP(asp-clnt-OsmoHNBGW2)[0x55fc0cbdd780]{ASP_DOWN}: event M-ASP_UP.req not permitted in role SG (xua_asp_fsm.c:420) 20220326092641485 DLSS7 INFO 0: asp-asp-clnt-OsmoHNBGW: Client connected (r=10.40.2.74:52905<->l=10.30.50.100:2905) (osmo_ss7.c:1856) 20220326092641490 DLM3UA ERROR 0: asp-asp-clnt-OsmoHNBGW: Rx M3UA SNM not permitted while ASP in state ASP_INACTIVE (m3ua.c:954) 20220326092643492 DLM3UA ERROR 0: asp-asp-clnt-OsmoHNBGW: Received MGMT_ERR 'Unsupported Message Class': HDR=(MGMT:ERROR,V=1,LEN=1006632960), PART(T=Error Code,L=4,D=00000003), PART(T=Diagnostic Info,L=40,D=010009010000002c02070024020a0008000000010006000800000000000b000800000001020b0008) (m3ua.c:588) 20220326092643492 DLSS7 NOTICE xua_default_lm(asp-clnt-OsmoHNBGW)[0x55fc0cbd80f0]{RKM_REG}: Ignoring primitive M-ERROR.indication (xua_default_lm_fsm.c:361) 20220326092653499 DLSS7 INFO 0: asp-asp-clnt-OsmoHNBGW: Restarting ASP asp-clnt-OsmoHNBGW, r=(10.40.2.66|10.40.2.74):52905<->l=10.30.50.100:2905 (osmo_ss7.c:1596) 20220326092653499 DLGLOBAL ERROR unable to connect socket: (10.40.2.66|10.40.2.74):52905: Cannot assign requested address (socket.c:848) 20220326092653499 DLINP INFO [WAIT_RECONNECT] osmo_stream_cli_reconnect(): retrying in 5 seconds... (stream.c:286) 20220326092653499 DLSS7 ERROR 0: asp-asp-clnt-OsmoHNBGW: Unable to open stream client for ASP asp-clnt-OsmoHNBGW, 10.30.50.100:2905 ==> (10.40.2.66|10.40.2.74):52905 (osmo_ss7.c:1629) 20220326092658509 DLSS7 INFO 0: asp-asp-clnt-OsmoHNBGW: Client connected (r=10.40.2.74:52905<->l=10.30.50.100:2905) (osmo_ss7.c:1856) 20220326092658515 DLM3UA ERROR 0: asp-asp-clnt-OsmoHNBGW: Rx M3UA SNM not permitted while ASP in state ASP_INACTIVE (m3ua.c:954) 20220326092700517 DLM3UA ERROR 0: asp-asp-clnt-OsmoHNBGW: Received MGMT_ERR 'Unsupported Message Class': HDR=(MGMT:ERROR,V=1,LEN=1006632960), PART(T=Error Code,L=4,D=00000003), PART(T=Diagnostic Info,L=40,D=010009010000002c02070024020a0008000000010006000800000000000b000800000001020b0008) (m3ua.c:588) 20220326092700517 DLSS7 NOTICE xua_default_lm(asp-clnt-OsmoHNBGW)[0x55fc0cbd80f0]{RKM_REG}: Ignoring primitive M-ERROR.indication (xua_default_lm_fsm.c:361) 20220326092710520 DLSS7 INFO 0: asp-asp-clnt-OsmoHNBGW: Restarting ASP asp-clnt-OsmoHNBGW, r=(10.40.2.66|10.40.2.74):52905<->l=10.30.50.100:2905 (osmo_ss7.c:1596) 20220326092710520 DLGLOBAL ERROR unable to connect socket: (10.40.2.66|10.40.2.74):52905: Cannot assign requested address (socket.c:848) 20220326092710520 DLINP INFO [WAIT_RECONNECT] osmo_stream_cli_reconnect(): retrying in 5 seconds... (stream.c:286) 20220326092710520 DLSS7 ERROR 0: asp-asp-clnt-OsmoHNBGW: Unable to open stream client for ASP asp-clnt-OsmoHNBGW, 10.30.50.100:2905 ==> (10.40.2.66|10.40.2.74):52905 (osmo_ss7.c:1629) 20220326092715530 DLSS7 INFO 0: asp-asp-clnt-OsmoHNBGW: Client connected (r=10.40.2.74:52905<->l=10.30.50.100:2905) (osmo_ss7.c:1856) 20220326092715536 DLM3UA ERROR 0: asp-asp-clnt-OsmoHNBGW: Rx M3UA SNM not permitted while ASP in state ASP_INACTIVE (m3ua.c:954) 20220326092717538 DLM3UA ERROR 0: asp-asp-clnt-OsmoHNBGW: Received MGMT_ERR 'Unsupported Message Class': HDR=(MGMT:ERROR,V=1,LEN=1006632960), PART(T=Error Code,L=4,D=00000003), PART(T=Diagnostic Info,L=40,D=010009010000002c02070024020a0008000000010006000800000000000b000800000001020b0008) (m3ua.c:588) 20220326092717538 DLSS7 NOTICE xua_default_lm(asp-clnt-OsmoHNBGW)[0x55fc0cbd80f0]{RKM_REG}: Ignoring primitive M-ERROR.indication (xua_default_lm_fsm.c:361) ^C All ideas/help highly appreciated! Best regards, /Sjur -----Original Message----- From: Sjur Thomas Lien Sent: Friday, March 25, 2022 10:45 AM To: OpenBSC <openbsc(a)lists.osmocom.org> Subject: RE: OSMO HnbGW , problems with SCTP towards real MSC and SGSN Hi, I figured it out by myself😊 Regards, /Sjur -----Original Message----- From: Sjur Thomas Lien <sjur.lien(a)telenormaritime.com> Sent: Friday, March 25, 2022 10:23 AM To: OpenBSC <openbsc(a)lists.osmocom.org> Subject: OSMO HnbGW , problems with SCTP towards real MSC and SGSN 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 Internal Internal

3 years, 5 months

OSMO HnbGW , problems with SCTP towards real MSC and SGSN

by Sjur Thomas Lien

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

3 years, 5 months

OsmoDevCall on Mar 25, 2022: "Iridium reverse engineering update"

by Harald Welte

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)

3 years, 5 months

OSMO HnbGW gives socket error

by Sjur Thomas Lien

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

3 years, 5 months

Whitelisting/Blocklisting

by Justin

Hi Osmocom, Do we have feature/functionality in OSMO-BSC similar to authorized-regex of OSMO-NITB where a IMSI prefix or regex is used to determine if the subscriber is permitted to register to the network or not. I've tried to looked at the osmo-bsc manual but I haven't seen any configurations related to the said feature/functionality. I've tried also the access-list configuration but I think it's no longer supported in latest version. Regards, Justin

3 years, 5 months

Re: OsmoHNBGW, libosmocore make error , CentOS Linux release 7.9.2009

by Pau Espin Pedrol

Hi, please reply to the ML, not only to me. according to [1] osmo-hnbw is available in CentOS_8, but I think you are using CentOS_7. Maybe try using the package from CentOS_8. [1] https://build.opensuse.org/project/monitor/network:osmocom:nightly On 3/18/22 08:46, Sjur Thomas Lien wrote: > Hi, > > Thanks for quick feedback. > First of all, I can't find OsmoHNBGW executable, so that at least needs to be compiled. And I totally agree, I'll use prebuilt packages if I can find them. I did find prebuilt libosmocore, but did not find prebuilt osmo-mgw. > So when running 'make ' on osmo-mgw, I see that file osmocom/netif/osmux.h is missing. Netif was not available, so I did a git clone of netif, and tried a ./configure. > > That's when I got this fault: > > checking for osmo_sock_init2_multiaddr in -losmocore... no > configure: error: libosmocore built without libsctp support > [root@tmaeurcellmngr libosmo-netif]# > > So my conclusion was that the prebuilt libosmocore could not be used in my case. That's why I tried to compile libosmocore from scratch. > > But thanks for advice, I'll give it another go. > > BR, > /Sjur > -- - Pau Espin Pedrol <pespin(a)sysmocom.de> http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Director: Harald Welte

3 years, 5 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC