Got a problem with ipacces-telnet. My goal is to run osmo-nitb, and do some experimenting.
After a factory default reset, the following commands are given:
(192.168.1.11 is ip-address of the nanoBTS)
./ipaccess-config 192.168.1.11 -u 1808/0/0
./ipaccess-config 192.168.1.11 -o 192.168.1.1
./ipaccess-config 192.168.1.11 -r
(wait)
./ipaccess-config -n 0x400/0x400 192.168.1.11
Then I start ipaccess-telnet :
ipaccess-telnet 192.168.1.11 3210
And I start osmo-ntib:
osmo-nitb --config-file openbsc900.cfg
==========================================================
The biggest problem, that makes debugging difficult, is that I after having run osmo-nitb, I cannot use ipaccess-telnet anymore.
I have put in some additional prints into ip-access-auth.c to monitor the nanoBTS response:
Two examples of OK response, before osmo-nitb is run:
response: 3C 31 25 01 7C 3B B2 23 D6 7D 5D 84 17 62 9A 2E 9D 3E
= "<1% |;?#?}]? b?.?>" (length = 18)
response: 3C 76 B9 88 4C 43 D8 E3 1E 9A 2A 81 DD A0 C7 AC A5 3E
= "<v??LC?? ?*??O?>" (length = 18)
Two examples of response when nanoBTS refuse connection after having run osmo-nitb:
response: 7B 58 0D 7C A4 50 75 83 2B FB 38 F2 66 AD B0 B6 AA 7D
= {X?|?Pu?+?8?f????}" (length = 18)
response: 7B 43 4A E6 5B A7 E2 1D 1C 8D F4 88 FF FB 26 F6 69 7D
= "{CJ?[?? ?????&?i}" (length = 18)
Only a factory default reset will make ipaccess-telnet working again.
==========================================================
Output from osmo-nitb:
<0019> input/ipaccess.c:945 enabling ipaccess BSC mode
DB: Database initialized.
DB: Database prepared.
<001d> sms_queue.c:220 Attempting to send 20 SMS
<0019> input/ipa.c:308 accept()ed new link from 192.168.1.11 to port 3002
<0019> input/ipaccess.c:422 Sign link vanished, dead socket
<0019> input/ipaccess.c:260 Forcing socket shutdown with no signal link set
<0019> input/ipa.c:308 accept()ed new link from 192.168.1.11 to port 3002
<0019> input/ipa.c:308 accept()ed new link from 192.168.1.11 to port 3003
<0004> bsc_init.c:265 bootstrapping RSL for BTS/TRX (0/0) on ARFCN 33 using MCC=1 MNC=1 LAC=1 CID=0 BSIC=63 TSC=7
Failure Event Report Type=processing failure Severity=warning level failure Probable cause= 03 00 01 Additional Text=40065:WARN:DHCP:dhcp_msg.c#692:Router Address not not valid: clearing it
Failure Event Report Type=processing failure Severity=warning level failure Probable cause= 03 00 01 Additional Text=20233:WARN:DHCP:dhcp_msg.c#692:Router Address not not valid: clearing it
==========================================================
Output from ipaccess-telnet:
(NOT sure if this is exactly same run as shown in the osmo-nitb ouput)
nanoBTS (c) ip.access Ltd 2001
30351:DBG:CLI_SKT:Remote client 192.168.1.1 connected
3525:DBG:TIB:OCXO is now WARM
4032:DBG:IP_CHANNEL:Assigning RX Client A
4032:DBG:IP_CHAN_RX_A:4711:ipChanConn: EVENT 0x00001742 rxd in STATE notconnected
4032:DBG:IP_CHAN_RX_A:Attempting connection to 192.168.1.1:3002
4033:DBG:IP_CHAN_RX_A:4712:ipChanConn: EVENT 0x00001741 rxd in STATE outgoingconnecting
6198:DBG:IP_CHAN_RX_A:4789:ipChanConn: EVENT 0x00001744 rxd in STATE outgoingconnecting
19151:DBG:DHCP:Event 4 received in State 3
19151:DBG:DHCP:T1 expired, sending Request
19154:DBG:DHCP:Tr Timer started with period 112 secs
19155:DBG:DHCP:Event 2 received in State 4
19155:DBG:DHCP:ACK received
19155:WARN:DHCP:dhcp_msg.c#696:Router Address not not valid: clearing it
19161:DBG:DB_EE:Writing 232 bytes of DBX data to block 3
19161:DBG:DB_EE:Re-using existing DBX block
19200:DBG:DB_EE:NV block 3 - wrote block to NV, main and backup OK.
19200:DBG:DB_EE:EE update complete.
28158:DBG:IP_CHANNEL:Assigning RX Client A
28158:DBG:IP_CHAN_RX_A:5541:ipChanConn: EVENT 0x00001742 rxd in STATE notconnected
28158:DBG:IP_CHAN_RX_A:Attempting connection to 192.168.1.1:3002
28158:DBG:IP_CHAN_RX_A:5542:ipChanConn: EVENT 0x00001747 rxd in STATE outgoingconnecting
28593:DBG:OAM_IM:Changing SYSTEM LINK from 0.0 to 73.255
28650:DBG:DB_EE:EE update complete.
29719:DBG:OAM_IM:Stopping "Primary OML Fallback Client"
29719:DBG:OAM_IM:Stopping "Secondary OML Server"
29719:DBG:OAM_IM:Not stopping "Secure Secondary OML Server" - has not been started
29719:DBG:OAM_IM:Not stopping "IML Site Server" - has not been started
29719:DBG:OAM_IM:Not stopping "Secure IML Site Server" - has not been started
29719:DBG:OAM_IM:Stopping "IML Bts Server"
29719:DBG:OAM_IM:Not stopping "Secure IML Bts Server" - has not been started
29719:DBG:OAM_IM:Stopping "IRL Patched Routing Link"
29719:DBG:OAM_IM:Failed to inject event=1="STOP" into link source (token=7)
29744:DBG:IP_CHAN_SERVER:Closed server listening on port 3006
29745:DBG:IP_CHAN_SERVER:Closed server listening on port 3014
29935:DBG:IP_CHAN_RX_A:5705:ipChanConn: EVENT 0x00001743 rxd in STATE connected
29935:DBG:IP_CHAN_RX_A:5706:ipChanConn: EVENT 0x00001741 rxd in STATE disconnectclosing
==========================================================
Content of config file, openbsc900.cfg:
!
! OpenBSC configuration saved from vty
! !
password foo
!
log stderr
logging filter all 1
line vty
no login
!
e1_input
e1_line 0 driver ipa
network
network country code 1
mobile network code 1
short name OpenBSC
long name OpenBSC
auth policy closed
location updating reject cause 13
encryption a5 0
neci 1
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 t3101 10
timer t3103 0
timer t3105 0
timer t3107 0
timer t3109 4
timer t3111 0
timer t3113 60
timer t3115 0
timer t3117 0
timer t3119 0
timer t3141 0
bts 0
type nanobts
band DCS900
cell_identity 0
location_area_code 1
training_sequence_code 7
base_station_id_code 63
ms max power 15
cell reselection hysteresis 4
rxlev access min 0
channel allocator ascending
rach tx integer 9
rach max transmission 7
ip.access unit_id 1808 0
oml ip.access stream_id 255 line 0
gprs mode none
trx 0
rf_locked 0
arfcn 33
nominal power 23
max_power_red 20
rsl e1 tei 0
timeslot 0
phys_chan_config CCCH+SDCCH4
timeslot 1
phys_chan_config SDCCH8
timeslot 2
phys_chan_config TCH/F
timeslot 3
phys_chan_config TCH/F
timeslot 4
phys_chan_config TCH/F
timeslot 5
phys_chan_config TCH/F
timeslot 6
phys_chan_config TCH/F
timeslot 7
phys_chan_config TCH/F
Odd Trandem
SINTEF ICT
This is a continuation of the patch series for the SMS validity fixes in
libosmocore.
Note, that this patch is based on top of the SMS DB change to remove
receiver ID. It is also available in the achemeris/sms-validity-fix-master
branch in the git repo.
--
Regards,
Alexander Chemeris.
CEO, Fairwaves, Inc. / ООО УмРадио
https://fairwaves.co
In a production system we should not store messages longer than
needed, as it will quickly bloat our DB. In case one wants to store
messages for debug purposes, we could add one of the following
capabilities later:
- hexdump to a log file
- send to an SMPP entry on delivery
- send to Wireshark
--
Regards,
Alexander Chemeris.
CEO, Fairwaves, Inc. / ООО УмРадио
https://fairwaves.co