Hello All,
Tried to setup Osmo-NITB + OsmoSGSN + GGSN installation using sysmoBTS station. To connect to the network I use custom SIM card programmed with appropriate MCC and MNC. That is what I get:
osmo-nitb log: ==================== <0005> abis_nm.c:2414 OC=GPRS-CELL(f1) INST=(00,00,ff) IPACCESS(0xf6): SET ATTR ACK <0005> abis_nm.c:2414 OC=GPRS-NSVC(f2) INST=(00,00,ff) IPACCESS(0xf6): SET ATTR ACK <0004> abis_rsl.c:1431 (bts=0,trx=0,ts=0,ss=0) Activating ARFCN(666) SS(0) lctype SDCCH r=LOCATION_UPDATE ra=0x0f ta=0 <0004> abis_rsl.c:1165 (bts=0,trx=0,ts=0,ss=0) CHANNEL ACTIVATE ACK <0000> abis_rsl.c:1621 (bts=0,trx=0,ts=0,ss=0) SAPI=0 ESTABLISH INDICATION <0002> gsm_04_08.c:1055 LOCATION UPDATING REQUEST: mi_type=0x01 MI(250770000002339) type=NORMAL <0001> gsm_04_08.c:119 (bts 0 trx 0 ts 0 pd 05) Sending 0x18 to MS. <0000> abis_rsl.c:1621 (bts=0,trx=0,ts=0,ss=0) SAPI=0 DATA INDICATION <0003> bsc_api.c:479 CLASSMARK CHANGE CM2(len=3) CM3(len=9) <0000> abis_rsl.c:1621 (bts=0,trx=0,ts=0,ss=0) SAPI=0 DATA INDICATION <0002> gsm_04_08.c:462 IDENTITY RESPONSE: mi_type=0x02 MI(358279013039780) <0002> gsm_04_08.c:426 -> LOCATION UPDATE ACCEPT <0001> gsm_04_08.c:119 (bts 0 trx 0 ts 0 pd 05) Sending 0x02 to MS. <0002> gsm_04_08.c:768 -> MM INFO <0001> gsm_04_08.c:119 (bts 0 trx 0 ts 0 pd 05) Sending 0x32 to MS. <0002> gsm_subscriber.c:361 Subscriber 250770000002339 ATTACHED LAC=1 <0000> abis_rsl.c:1621 (bts=0,trx=0,ts=0,ss=0) SAPI=0 DATA INDICATION <0002> gsm_04_08.c:1071 TMSI Reallocation Completed. Subscriber: 250770000002339 <0000> chan_alloc.c:405 (bts=0,trx=0,ts=0,ss=0) starting release sequence <0003> gsm_04_08_utils.c:231 Sending Channel Release: Chan: Number: 0 Type: 1 <0004> abis_rsl.c:633 (bts=0,trx=0,ts=0,ss=0) DEACTivate SACCH CMD <0000> abis_rsl.c:1621 (bts=0,trx=0,ts=0,ss=0) SAPI=0 RELEASE INDICATION <0004> abis_rsl.c:679 (bts=0,trx=0,ts=0,ss=0) RF Channel Release CMD due error 0 <0004> abis_rsl.c:731 (bts=0,trx=0,ts=0,ss=0) RF CHANNEL RELEASE ACK =====================
Thus, I see that GPRS attributes were set successfully and the subscriber was granted access to the network. Then, I look into osmo-sgsn log:
===================== <0010> gprs_ns.c:679 NSEI=101 Rx NS RESET (NSVCI=101, cause=O&M intervention) <0010> gprs_ns.c:538 NSEI=101 Tx NS RESET ACK (NSVCI=101) <0010> gprs_ns.c:679 NSEI=101 Rx NS RESET (NSVCI=101, cause=PDU not compatible with protocol state) <0010> gprs_ns.c:538 NSEI=101 Tx NS RESET ACK (NSVCI=101) <0010> gprs_ns.c:865 NSEI=101 Rx NS UNBLOCK <0010> gprs_ns.c:865 NSEI=101 Rx NS UNBLOCK <0011> gprs_bssgp.c:1000 NSEI=101/BVCI=2 Rejecting PDU type 1 for unknown BVCI <0011> gprs_bssgp_util.c:103 BSSGP BVCI=0 Tx STATUS, cause=Unknown BVCI <0011> gprs_bssgp.c:1000 NSEI=101/BVCI=2 Rejecting PDU type 1 for unknown BVCI <0011> gprs_bssgp_util.c:103 BSSGP BVCI=0 Tx STATUS, cause=Unknown BVCI =====================
So, PDU is rejected and I don't see any GPRS availability on a phone.
Has anybody ever seen this message?
Regards, Sergey.
On Wed, Aug 14, 2013 at 07:42:30PM +0400, Sergey V. Efimov wrote:
Hello All,
<0011> gprs_bssgp.c:1000 NSEI=101/BVCI=2 Rejecting PDU type 1 for unknown BVCI <0011> gprs_bssgp_util.c:103 BSSGP BVCI=0 Tx STATUS, cause=Unknown BVCI <0011> gprs_bssgp.c:1000 NSEI=101/BVCI=2 Rejecting PDU type 1 for unknown BVCI <0011> gprs_bssgp_util.c:103 BSSGP BVCI=0 Tx STATUS, cause=Unknown BVCI
without your NITB/BSC config it is difficult to judge. What doesn't work for sure is to restart the SGSN once the PCU has exchanged some messages with it.
holger
Hello,
I used step-by-step instruction from the osmocom.org site.
Here is my openbsc config:
==== e1_input e1_line 0 driver ipa network network country code 250 mobile network code 77 short name ABC long name ABC auth policy accept-all 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 DCS1800 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 1234 0 oml ip.access stream_id 255 line 0 gprs mode gprs gprs routing area 0 gprs cell bvci 2 gprs nsei 101 gprs nsvc 0 nsvci 101 gprs nsvc 0 local udp port 23000 gprs nsvc 0 remote udp port 23000 gprs nsvc 0 remote ip 192.168.168.98 trx 0 rf_locked 0 arfcn 666 nominal power 23 max_power_red 20 rsl e1 tei 0 timeslot 0 phys_chan_config CCCH+SDCCH4 timeslot 1 phys_chan_config PDCH timeslot 2 phys_chan_config PDCH 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 ====
Here is my osmo-sgsn.cfg
==== sgsn gtp local-ip 192.168.168.98 ggsn 0 remote-ip 192.168.168.230 ggsn 0 gtp-version 1 ! ns timer tns-block 3 timer tns-block-retries 3 timer tns-reset 3 timer tns-reset-retries 3 timer tns-test 30 timer tns-alive 3 timer tns-alive-retries 10 encapsulation udp local-ip 192.168.168.98 encapsulation udp local-port 23000 encapsulation framerelay-gre enabled 0
====
Here is my ggsn.cfg
=== listen 192.168.168.230 net 192.168.168.0/24 dynip 192.168.168.240/30 ===
Here is my open-bts.cfg
=== bts 0 band 1800 ipa unit-id 1234 0 oml remote-ip 192.168.168.98 ===
Regards, Sergey.
On Aug 14, 2013, at 8:17 PM, Holger Hans Peter Freyther wrote:
On Wed, Aug 14, 2013 at 07:42:30PM +0400, Sergey V. Efimov wrote:
Hello All,
<0011> gprs_bssgp.c:1000 NSEI=101/BVCI=2 Rejecting PDU type 1 for unknown BVCI <0011> gprs_bssgp_util.c:103 BSSGP BVCI=0 Tx STATUS, cause=Unknown BVCI <0011> gprs_bssgp.c:1000 NSEI=101/BVCI=2 Rejecting PDU type 1 for unknown BVCI <0011> gprs_bssgp_util.c:103 BSSGP BVCI=0 Tx STATUS, cause=Unknown BVCI
without your NITB/BSC config it is difficult to judge. What doesn't work for sure is to restart the SGSN once the PCU has exchanged some messages with it.
holger
-
Holger Hans Peter Freyther -
Sergey V. Efimov