Re: osmo-nitb and osmo-bts-trx problems with voice, no connection

I advanced here in putting the new split stack working. By mistake I put different ip.access unit_id between bts and bsc... sorry my last email. But still no luck. Osmo-BSC gives me: PART(T=Cause,L=4,D=00000300) 20180221033117954 DLSCCP <001e> sccp_scoc.c:1548 Received CO:RELRE for local reference 1 20180221033117954 DLSCCP <001e> sccp_scoc.c:1581 SCCP-SCOC(1)[0x55decef19a70]{ACTIVE}: Received Event RCOC-RELEASED.ind 20180221033117954 DLSCCP <001e> sccp_user.c:156 Delivering N-DISCONNECT.indication to SCCP User 'msc-0' 20180221033117954 DMSC <0008> osmo_bsc_sigtran.c:223 N-DISCONNECT.ind(1, cause=768) 20180221033117954 DMSC <0008> osmo_bsc_sigtran.c:364 sccp connection (id=1) not cleared (gsm subscriber connection still active) -- forcefully clearing it now! 20180221033117954 DMSC <0008> a_reset.c:175 A-RESET(msc-0)[0x55decef17b30]{CONN}: Received Event 1 20180221033117954 DLSS7 <001d> sccp_scrc.c:391 sccp_scrc_rx_scoc_conn_msg: HDR=(CO:RELCO,V=0,LEN=0), PART(T=Routing Context,L=4,D=00000000), PART(T=Destination Reference,L=4,D=00000002), PART(T=Source Reference,L=4,D=00000001) 20180221033117954 DLSS7 <001d> osmo_ss7_hmrt.c:278 m3ua_hmdc_rx_from_l2(): dpc=185=0.23.1 not local, message is for routing 20180221033117954 DLSS7 <001d> osmo_ss7_hmrt.c:227 Found route for dpc=185=0.23.1: pc=0=0.0.0 mask=0x0=0.0.0 via AS as-clnt-msc-0 proto=m3ua 20180221033117954 DLSS7 <001d> osmo_ss7_hmrt.c:233 rt->dest.as proto is M3UA for dpc=185=0.23.1 20180221033117954 DLSS7 <001d> m3ua.c:507 XUA_AS(as-clnt-msc-0)[0x55decef16d80]{AS_ACTIVE}: Received Event AS-TRANSFER.req 20180221033117954 DLSCCP <001e> sccp_scoc.c:972 SCCP-SCOC(1)[0x55decef19a70]{ACTIVE}: state_chg to IDLE 20180221033117954 DLSCCP <001e> sccp_scoc.c:420 SCCP-SCOC(1)[0x55decef19a70]{IDLE}: Terminating (cause = OSMO_FSM_TERM_REQUEST) 20180221033117954 DLSCCP <001e> sccp_scoc.c:420 SCCP-SCOC(1)[0x55decef19a70]{IDLE}: Freeing instance 20180221033117954 DLSCCP <001e> fsm.c:344 SCCP-SCOC(1)[0x55decef19a70]{IDLE}: Deallocated 20180221033117954 DLINP <0013> stream.c:279 connected write 20180221033117954 DLINP <0013> stream.c:204 sending data 20180221033117954 DLINP <0013> stream.c:279 connected write 20180221033117954 DLINP <0013> stream.c:204 sending data 20180221033118184 DRLL <0000> abis_rsl.c:2169 (bts=0,trx=0,ts=0,ss=1) SAPI=0 DATA INDICATION 20180221033118184 DRSL <0004> bsc_api.c:803 Got data in non active state(RELEASE REQUESTED), discarding. 20180221033118184 DLINP <0013> input/ipaccess.c:285 Bad signalling message, sign_link returned error: Operation not permitted. 20180221033118419 DRLL <0000> abis_rsl.c:2169 (bts=0,trx=0,ts=0,ss=1) SAPI=0 DATA INDICATION 20180221033118419 DRSL <0004> bsc_api.c:803 Got data in non active state(RELEASE REQUESTED), discarding. 20180221033118419 DLINP <0013> input/ipaccess.c:285 Bad signalling message, sign_link returned error: Operation not permitted. 20180221033118654 DRLL <0000> abis_rsl.c:2169 (bts=0,trx=0,ts=0,ss=1) SAPI=0 RELEASE INDICATION 20180221033120655 DRSL <0004> abis_rsl.c:1764 (bts=0,trx=0,ts=0,ss=1) T3111 expired: releasing RF Channel 20180221033120656 DRSL <0004> abis_rsl.c:872 (bts=0,trx=0,ts=0,ss=1) RF Channel Release 20180221033120657 DRSL <0004> abis_rsl.c:942 (bts=0,trx=0,ts=0,ss=1) RF CHANNEL RELEASE ACK 20180221033120657 DRSL <0004> abis_rsl.c:85 (bts=0,trx=0,ts=0,ss=1) state RELEASE REQUESTED -> NONE Thanks! Rafael Diniz On 02/19/2018 07:20 AM, Pau Espin Pedrol wrote: