10 Aug
2021
10 Aug
'21
12:36 p.m.
Hello Community!
Would like to as if anyone here have experience testing Half rate /AMR in osmo-nitb and
Freeswitch. Basically we are testing it in our lab with our devices Samsung Note 9 and
iPhone and we are having issue / errors as observed during testing. Below are the details
of the NITB we using:
OpenBSC# show version
OpenBSC 1.1.0.76-0bbb9 (OpenBSC).
Copyright (C) 2008-2016 Harald Welte, Holger Freyther
Contributions by Daniel Willmann, Jan Lübbe, Stefan Schmidt
Dieter Spaar, Andreas Eversberg, Sylvain Munaut, 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.
OpenBSC#
Osmo running-config:
stats interval 5
!
line vty
no login
!
e1_input
e1_line 0 driver ipa
e1_line 0 port 0
no e1_line 0 keepalive
network
network country code 10
mobile network code 1
short name testnetwork
long name testnetwork
auth policy closed
authorized-regexp .*
location updating reject cause 13
encryption a5 0
neci 1
paging any use tch 0
rrlp mode none
mm info 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 3
handover maximum distance 9999
timer t3113 60
timer t3103 1
timer t3101 10
timer t3109 1
timer t3122 10
timer t3105 1
dyn_ts_allow_tch_f 0
subscriber-keep-in-ram 1
bts 0
type sysmobts
band GSM900
cell_identity 1
location_area_code 1
base_station_id_code 63
ms max power 23
cell reselection hysteresis 4
rxlev access min 0
periodic location update 30
radio-link-timeout 32
channel allocator descending
rach tx integer 9
rach max transmission 7
channel-descrption attach 1
channel-descrption bs-pa-mfrms 5
channel-descrption bs-ag-blks-res 1
early-classmark-sending forbidden
ip.access unit_id 1000 0
oml ip.access stream_id 255 line 0
neighbor-list mode automatic
codec-support fr hr efr amr
amr tch-h modes 0
amr tch-h start-mode auto
trx 0
rf_locked 0
arfcn 122
nominal power 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 SDCCH8
hopping enabled 0
timeslot 3
phys_chan_config TCH/H
hopping enabled 0
timeslot 4
phys_chan_config TCH/H
hopping enabled 0
timeslot 5
phys_chan_config TCH/H
hopping enabled 0
timeslot 6
phys_chan_config TCH/H
hopping enabled 0
timeslot 7
phys_chan_config TCH/H
hopping enabled 0
trx 1
rf_locked 0
arfcn 42
nominal power 0
rsl e1 tei 0
timeslot 0
phys_chan_config CCCH+SDCCH4
hopping enabled 0
timeslot 1
phys_chan_config TCH/H
hopping enabled 0
timeslot 2
phys_chan_config TCH/H
hopping enabled 0
timeslot 3
phys_chan_config TCH/H
hopping enabled 0
timeslot 4
phys_chan_config TCH/H
hopping enabled 0
timeslot 5
phys_chan_config TCH/H
hopping enabled 0
timeslot 6
phys_chan_config TCH/H
hopping enabled 0
timeslot 7
phys_chan_config TCH/H
hopping enabled 0
mncc-int
default-codec tch-f fr
default-codec tch-h amr
nitb
subscriber-create-on-demand
subscriber-create-on-demand random 100000 199999
no assign-tmsi
smpp
local-tcp-ip 127.0.0.1 2776
system-id password
policy closed
smpp-first
esme admin
password password
default-route
NITB Logs:
Not Working:
Tue Aug 10 17:08:40 2021 <0004> abis_rsl.c:1848 (bts=0) CHAN RQD: reason: call
re-establishment (ra=0x49, neci=0x01, chreq_reason=0x02)
Tue Aug 10 17:08:40 2021 <0004> abis_rsl.c:1924 (bts=0,trx=1,ts=7,ss=0) Activating
ARFCN(73) SS(0) lctype TCH_H r=CALL ra=0x49 ta=0
Tue Aug 10 17:08:40 2021 <0004> abis_rsl.c:595 (bts=0,trx=1,ts=7,pchan=TCH/H) Tx RSL
Channel Activate with act_type=INITIAL
Tue Aug 10 17:08:40 2021 <0004> abis_rsl.c:1231 (bts=0,trx=1,ts=7,ss=0) state NONE
-> ACTIVATION REQUESTED
Tue Aug 10 17:08:40 2021 <0004> abis_rsl.c:1603 (bts=0,trx=1,ts=7,ss=0) CHANNEL
ACTIVATE ACK
Tue Aug 10 17:08:40 2021 <0004> abis_rsl.c:1231 (bts=0,trx=1,ts=7,ss=0) state
ACTIVATION REQUESTED -> ACTIVE
Tue Aug 10 17:08:41 2021 <000a> bsc_api.c:415 Sending (bts=0,trx=1,ts=7,ss=0)
ChanModify for speech: SPEECH_AMR on channel TCH_H
Tue Aug 10 17:08:41 2021 <0003> gsm_04_08_utils.c:517 -> CHANNEL MODE MODIFY
mode=0x41 <—————————————————————————————————————— This is what we observed, no Channel
Modify Ack
Tue Aug 10 17:08:47 2021 <000a> bsc_api.c:139 Assignment T10 timeout on 0x15b4350
Tue Aug 10 17:08:47 2021 <0003> osmo_msc.c:82 MSC assign failure (do nothing).
Tue Aug 10 17:08:51 2021 <0004> abis_rsl.c:1848 (bts=0) CHAN RQD: reason: call
re-establishment (ra=0x49, neci=0x01, chreq_reason=0x02)
Tue Aug 10 17:08:51 2021 <0004> abis_rsl.c:1924 (bts=0,trx=1,ts=7,ss=1) Activating
ARFCN(73) SS(1) lctype TCH_H r=CALL ra=0x49 ta=0
Tue Aug 10 17:08:51 2021 <0004> abis_rsl.c:595 (bts=0,trx=1,ts=7,pchan=TCH/H) Tx RSL
Channel Activate with act_type=INITIAL
Tue Aug 10 17:08:51 2021 <0004> abis_rsl.c:1231 (bts=0,trx=1,ts=7,ss=1) state NONE
-> ACTIVATION REQUESTED
Tue Aug 10 17:08:51 2021 <0004> abis_rsl.c:1603 (bts=0,trx=1,ts=7,ss=1) CHANNEL
ACTIVATE ACK
Tue Aug 10 17:08:51 2021 <0004> abis_rsl.c:1231 (bts=0,trx=1,ts=7,ss=1) state
ACTIVATION REQUESTED -> ACTIVE
Tue Aug 10 17:08:53 2021 <0017> smpp_smsc.c:746 [entropy] smpp_pdu_rx(00 00 00 10 00
00 00 15 00 00 00 00 00 00 00 24 )
Tue Aug 10 17:08:53 2021 <0017> smpp_smsc.c:595 [entropy] Rx Enquire Link
Tue Aug 10 17:08:53 2021 <0017> smpp_smsc.c:599 [entropy] Tx Enquire Link Response
Tue Aug 10 17:09:03 2021 <0004> abis_rsl.c:1848 (bts=0) CHAN RQD: reason: call
re-establishment (ra=0x47, neci=0x01, chreq_reason=0x02)
Tue Aug 10 17:09:03 2021 <0004> abis_rsl.c:1924 (bts=0,trx=1,ts=6,ss=0) Activating
ARFCN(73) SS(0) lctype TCH_H r=CALL ra=0x47 ta=0
Tue Aug 10 17:09:03 2021 <0004> abis_rsl.c:595 (bts=0,trx=1,ts=6,pchan=TCH/H) Tx RSL
Channel Activate with act_type=INITIAL
Tue Aug 10 17:09:03 2021 <0004> abis_rsl.c:1231 (bts=0,trx=1,ts=6,ss=0) state NONE
-> ACTIVATION REQUESTED
Tue Aug 10 17:09:03 2021 <0004> abis_rsl.c:1603 (bts=0,trx=1,ts=6,ss=0) CHANNEL
ACTIVATE ACK
Tue Aug 10 17:09:03 2021 <0004> abis_rsl.c:1231 (bts=0,trx=1,ts=6,ss=0) state
ACTIVATION REQUESTED -> ACTIVE
Tue Aug 10 17:09:13 2021 <0004> abis_rsl.c:1358 (bts=0,trx=1,ts=7,ss=0) CONNECTION
FAIL: RELEASING state ACTIVE CAUSE=0x01(Radio Link Failure)
Tue Aug 10 17:09:13 2021 <0004> abis_rsl.c:867 (bts=0,trx=1,ts=7,ss=0) RF Channel
Release due to error: 1
Tue Aug 10 17:09:13 2021 <0004> abis_rsl.c:777 (bts=0,trx=1,ts=7,ss=0) DEACTivate
SACCH CMD
Tue Aug 10 17:09:13 2021 <0004> abis_rsl.c:1231 (bts=0,trx=1,ts=7,ss=0) state ACTIVE
-> RELEASE DUE ERROR
Tue Aug 10 17:09:13 2021 <0004> abis_rsl.c:939 (bts=0,trx=1,ts=7,ss=0) RF CHANNEL
RELEASE ACK
Tue Aug 10 17:09:17 2021 <0004> abis_rsl.c:826 (bts=0,trx=1,ts=7,ss=0) is back in
operation.
Tue Aug 10 17:09:17 2021 <0004> abis_rsl.c:1231 (bts=0,trx=1,ts=7,ss=0) state
RELEASE DUE ERROR -> NONE
Tue Aug 10 17:09:19 2021 <0004> abis_rsl.c:1848 (bts=0) CHAN RQD: reason: Location
updating (ra=0x07, neci=0x01, chreq_reason=0x03)
Tue Aug 10 17:09:19 2021 <0004> abis_rsl.c:1924 (bts=0,trx=0,ts=1,ss=0) Activating
ARFCN(8) SS(0) lctype SDCCH r=LOCATION_UPDATE ra=0x07 ta=0
Tue Aug 10 17:09:19 2021 <0004> abis_rsl.c:595 (bts=0,trx=0,ts=1,pchan=SDCCH8) Tx
RSL Channel Activate with act_type=INITIAL
Tue Aug 10 17:09:19 2021 <0004> abis_rsl.c:1231 (bts=0,trx=0,ts=1,ss=0) state NONE
-> ACTIVATION REQUESTED
Tue Aug 10 17:09:19 2021 <0004> abis_rsl.c:1603 (bts=0,trx=0,ts=1,ss=0) CHANNEL
ACTIVATE ACK
Tue Aug 10 17:09:19 2021 <0004> abis_rsl.c:1231 (bts=0,trx=0,ts=1,ss=0) state
ACTIVATION REQUESTED -> ACTIVE
Osmo-sip-connector Logs:
<0000> sip.c:330 sip_release_call(): Release with MNCC cause(NORM_CALL_CLEAR)
<0000> sip.c:302 cause2status(): Mapping cause(NORM_CALL_CLEAR) to status(200)
<0000> sip.c:353 Ending leg(0x8dc700) in con
<0000> sip.c:223 SIP event(33) status(200) phrase(OK) 0x8dc700
<0000> sip.c:257 leg(0x8dc700) got resp to bye
<0000> sip.c:223 SIP event(9) status(200) phrase(Session Terminated) 0x8d7150
<0000> sip.c:265 leg(0x8d7150) got bye, releasing.
<0000> sip.c:223 SIP event(7) status(0) phrase(INVITE sent) 0x8d7150
<0000> sip.c:223 SIP event(1) status(100) phrase(Trying) (nil)
<0000> sip.c:89 Incoming call handle(0x8d96a0)
<0000> sip.c:223 SIP event(7) status(100) phrase(Trying) 0x8dc700
<0000> sip.c:330 sip_release_call(): Release with MNCC cause(RESOURCE_UNAVAIL)
<0000> sip.c:302 cause2status(): Mapping cause(RESOURCE_UNAVAIL) to status(503)
<0000> sip.c:341 Canceling leg(0x8dc700) in cnfd state
<0000> sip.c:223 SIP event(31) status(503) phrase(Service Unavailable) 0x8d7150
<0000> sip.c:242 leg(0x8d7150) unknown SIP status(503), releasing.
<0000> sip.c:248 Releasing other leg (0x8d6f30) with status(503)
<0001> mncc.c:54 cmd(0x204) never arrived for leg(2147483656)
<—————————————————————————————————————— Basically it didn’t arrived in B Leg.
<0001> mncc.c:495 call(2147483656) can not be found
Very well appreciated your help on this.
Best Regards,
Sonny
10 Aug
10 Aug
6:28 p.m.
On 10/08/2021 05:36, Sonny Lafuente wrote:
*OpenBSC# show version*
OpenBSC 1.1.0.76-0bbb9 (OpenBSC).
Hi Sonny. I don't think you are likely to get much response here about
OpenBSC (despite the name of the list still pending change)
All the same, I can tell you that it "Works for me", albeit with a
carefully chosen combination of versions of osmo-nitb, osmo-bts,
osmo-sip-connector, freeswitch and amr modules.
I don't even think that current osmo-sip-connector will connect to
"current" osmo-nitb though, and neither will current osmo-bts, (although
you do not specify what BTS you are using).
My question is: why are you testing this?
If you need more help, better might be a pcap of traffic including SIP
and RTP and freeswitch logs. osmo-bts log too, if you are using it. Not
necessarily suggesting you should post that to this list though. But if
you do, maybe include some info on what the project is for?
Thanks!
k.
8:19 p.m.
Hi Sonny,
I am really sorry to be *that guy* who is ruining all the fun, but I must chime in and
state:
Osmo NITB is end of life and it is highly unlikely to receive any fixes or support for
it.
I think it was clearly stated by main contributors of the project that basically the new,
more 3GPP-like network from osmocom is supposed to be used by all users. It is really not
that more complicated to deploy it once you get the hang of it compared to nitb in my
opinion.
Sorry again, and good luck Sonny.
Keith, obviously I did not mean the above to you, I am aware your use case is special and
you have a good reason(s) to do things the way you are doing them. In case of Sonny since
he mentioned a lab-setup I expect him to be more flexible and be able to rapidly move to
the new architecture - hence my comment above.
Kind regards,
Domi
10.08.2021 dátummal, 18:28 időpontban Keith
<keith(a)rhizomatica.org> írta:
On 10/08/2021 05:36, Sonny Lafuente wrote:
OpenBSC# show version
OpenBSC 1.1.0.76-0bbb9 (OpenBSC).
Hi Sonny. I don't think you are likely to get much response here about OpenBSC
(despite the name of the list still pending change)
All the same, I can tell you that it "Works for me", albeit with a carefully
chosen combination of versions of osmo-nitb, osmo-bts, osmo-sip-connector, freeswitch and
amr modules.
I don't even think that current osmo-sip-connector will connect to
"current" osmo-nitb though, and neither will current osmo-bts, (although you do
not specify what BTS you are using).
My question is: why are you testing this?
If you need more help, better might be a pcap of traffic including SIP and RTP and
freeswitch logs. osmo-bts log too, if you are using it. Not necessarily suggesting you
should post that to this list though. But if you do, maybe include some info on what the
project is for?
Thanks!
k.
1015
days inactive
1015
days old
2 comments
3 participants
participants (3)
-
Keith -
Sonny Lafuente -
Tomcsanyi, Domonkos