- OpenBSC - lists.osmocom.org

by Paul Atreides

I just picked up this IPAccess model which supports band 2/5 and has the same housing as the other units on the accelerate3g5 project docs. I've been pouring over docs and trying a lot of network configurations in my home lab. I have the login information for the factory reset and can access the web gui on port 8089 during the reset process, but ssh and telnet DMI seem to be disabled. I've been fuzzing ports and i've tried static as well as DHCP for IP addresses. My thought was that if i point the nano3G to the IP of my osmo-hNodeB machine that it would at least stimulate the device and maybe i'd see some log messages in the HNodeB gateway, but so far i haven't seen anything in the logs. i've also tried abisip-find and that doesn't find anything. Wireshark shows basic 'who has' Layer 2 messages and also DHCP requests sent to 0.0.0.0, both from the nano3g. The nano3g does get an ip from my lab router and i can ping it. The LAN behind that router can also access the 0.ipaccess ntp server, but again no telnet DMI or ssh so i'm unsure where to go from here. Layer 1 seems to show nothing on the uarfcn in the web gui, so it seems that its not crossing all the right bridges. I will admit, i haven't run any other osmo network components for the network, but as far as i was reading the home nodeb and ntp should be the only things necessary to at least start the process. Any insight on what to try next would be very helpful. Does anyone have experience with this model? thanks

2 years, 6 months

1
0
0 0

Subscriber Auto Provision in new split stack OSMO-NITB version

by Justin

Hi Osmocom, May I ask if we have similar feature of auto provisioning of subscribers who are trying to camp to the network similar to auth-policy accept-all in osmo-nitb? Is the new version supports also the auto provisioning of subscribers? Regards, Justin Mark Repollo

2 years, 7 months

2
1
0 0

Amplifier Settings

by Henry Caga

Hello, im Using a default configuration for my osmo-bsc setup using B210. I managed to get a working amplifier with specifications below. My question is, what should be the best config that i should use in order to maximize tge power and range of my amplifier? What are the best configs for osmo-trx, osmo-bts, and other applications related to osmo-bsc. Proper settings such as osmotrx tx-attenuation, nominal power, ms max power and other related configurations that are valid or matched for my amplifier. Listed below is my amplifier's specification. AMPLIFIER SPECS: band: uplink 885-915MHz / downlink 930-960MHz Max output power: downlink 47±1dBm Max allow input power: uplink -10dBm / downlink +10dBm gain: Uplink 25±2dB Downlink 28 to 53±1dB ALC: Uplink ≥10dB Downlink ≥10dB SWR: Uplink ≤1.5 Downlink ≤1.5 Passband ripple: Uplink ≤2dB Downlink ≤2dB Noise floor: uplink ≤2dB third order intermodulation: Uplink ≤-55dBc@-8dBm/ch/2ch Downlink ≤-36dBc@2ch Voltage: 28V Currency: ≤4.5A Thanks a lot! Henry

2 years, 7 months

1
0
0 0

Question about Virtual-Um implementation

by Ivan Babanov

Hello all, We trying to bring up set of BTS with virtual Um with different configurations: 1 BTS -> 1 TRX -> 1 MS works fine as expected 1 BTS -> 1 TRX -> 2 MS works fine as well But I see some unpredictable behaviour when I have 1 BTS -> 2 TRX(872,873) -> 1 MS MS can attach on one ARFCN (872) but when it tries to attach on 873 looks like PRACH does not reach BTS and I do not see Channel Request on BSC side. So, the question is it workable configuration: Several TRX to 1 MS with different power level to allow MS to choose a best cell to attach? I have just one idea: to have several virtphy instances for MS connected to different UDP ports. Thank you Vania

2 years, 7 months

1
0
0 0

LCLS

by Keith

Hi All, I was again looking at advancing with LCLS support. I've made a couple of proposals, which at least get it to the stage where the global call reference it consistent from the A leg to B leg of a call, with both the internal mncc and external, and therefore osmo-bsc can make use of either the lcls-mode (mgw|bts)-loop. The implementation in the osmo-sip-connector doing nothing more than passing the GCR from leg to leg, but it's more complicated than this. We need to allow the PBX to have the audio streams until the PBX itself decides to remove itself from the stream. (as it is you won't even hear ringback) I know all this is spec-ed somewhere in LCLS, I'm just not sure where/how this SIP re-INVITE processing should be implemented, in the sip conn, or the MSC - which I guess, takes us back again to neels' long standing proposals for parsing SDP inside the MSC. Maybe it' s time to get that merged. Anyway.. I have some time scheduled to try to move this forward towards a definitive solution, just writing here in case anyone else can help. Thanks. k/

2 years, 7 months

2
2
0 0

Nano 3G Femtocell request

by Americo Colella

Hello everyone,I would like to play eith the nano 3g femtocell, Is there anybody who want to give it away /sell one ? Thanks a lot, Americo

2 years, 7 months

1
0
0 0

Cellspot v2 LTE femtocells available free of charge

by Harald Welte

Dear Osmocom community, some years ago sysmocom acquired a batch of > 30 T-Mobile Cellspot v2 femtocells, with the vague idea to "root" them and use them as a low-cost eNodeB with open5gs. They also seem to support HSPA in addition to LTE, with 8 simultaneous users on either of the two. Unfortunately we never found the time to really dig into them, and we primarily work with other more high-end eNodeBs these days. So we're giving them away for free. All you have to cover is the cost of shipping. Some information on those devices can be found at https://www.reddit.com/r/tmobile/comments/7ii5jm/4g_lte_cellspot_v2_virtual… - they are Alcatel-Lucent 9961 v2, based on a Qualcomm Femtocell chipset. Note: This really only makes sense for people who want to spend significant time to try to get them "owned" or "rooted" in order to use them with your own EPC rather than the one of T-Mobile. In case you're interested in one or multiple units: Please send an e-mail to sales(a)sysmocom.de stating the quantity as well as your shipping address. We will then get a shipping rete and send you a quote. Happy hacking, Harald -- - Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

2 years, 7 months

1
0
0 0

Osmo-BSC UL Power Loop

by Keith

Hi All, I am implementing uplink power control for the Ericsson RBS. I started with a vty command to force an ms power update on a timeslot and then I implemented a very crude loop and that "works". Next, I imported power_control.c from osmo-bts into osmo-bsc. This is where I began to wonder if this code is better moved some place where it can be shared by both projects. - There would be some small modifications necessary, I think. I also wonder if it is the right thing to do to integrate this bsc-side UL power control into the current (m|b)s-power control? Would it make sense to add a further "mode" there? ms-power-control mode dyn-bsc For example? Obviously one does not want both a BSC and BTS managing a power loop. Or maybe only allow the BSC side power loop to run with bts-type that is known to not do UL power control? There are some other issues I'm still unsure about, but this is enough by way of moving towards a patch fit for code review. Thanks! Keith.

2 years, 7 months

4
5
0 0

Announcement of "OsmoDevCall" on September 24, 2021

by Harald Welte

Dear Osmocom community, It's my pleasure to announce the next OsmoDevCall at September 24, 2021 at 20:00 CEST at https://meeting4.franken.de/b/har-xbc-bsx-wvs This meeting will have the following schedule: 20:00 meet + greet 20:15 presentation on "ISO 7816 smart card interface FPGA softcore" by tnt 21:00 USSE: unstructured supplementary social event [*] 22:00 close of call Attendance is free of charge and open to anyone with an interest in Osmocom. 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)

2 years, 7 months

1
0
0 0

Unable to program SIMs with pysim to use with srsRAN

by Andrea Valori

Hi everyone, I have a srsRAN installation, which works flawlessly with some Sysmocom SIMs I programmed some months ago using Pysim. Those SIMs still work perfectly, even if in the meantime I updated the srs installation. I am trying to program some other SIMs (bought in the same batch as the older ones which always worked), but failing miserably. Since the older programmed SIMs still work, I am focusing my attention on the SIM programming step, although I am fully aware that the issue might be on the enodeB side. For this reason I will post on both mailing lists. Apologise to the several people that may receive this twice being members of both communities. Many thanks in advance to everyone who might be able to help. Below are the steps I took and the results I got. *Programmed SIM with command (I believe this are exactly the parameters already programmed, doing this just for confirmation):* ./pySim-prog.py -p 0 -n Open5GS -i 901700000044987 -s 8988211000000449879 -k 833218D615B110706DB6E7FD69222BE9 -o D0C41ED07DFE2F9BB0DB083E5E347F5E -a 29728642 -x 001 -y 01 *Got the answer:* Using PC/SC reader interface Ready for Programming: Insert card now (or CTRL-C to cancel) Autodetected card type: sysmoISIM-SJA2 Generated card parameters : > Name : Open5GS > SMSP : e1ffffffffffffffffffffffff0581005155f5ffffffffffff000000 > ICCID : 8988211000000449879 > MCC/MNC : 001/01 > IMSI : 901700000044987 > Ki : 833218D615B110706DB6E7FD69222BE9 > OPC : D0C41ED07DFE2F9BB0DB083E5E347F5E > ACC : None > ADM1(hex): 3239373238363432 > OPMODE : None Programming ... Warning: Programming of the ICCID is not implemented for this type of card. Programming successful: Remove card from reader *Imported data into the HSS file:* # .csv to store UE's information in HSS # Kept in the following format: "Name,Auth,IMSI,Key,OP_Type,OP/OPc,AMF,SQN,QCI,IP_alloc" # # Name: Human readable name to help distinguish UE's. Ignored by the HSS # Auth: Authentication algorithm used by the UE. Valid algorithms are XOR # (xor) and MILENAGE (mil) # IMSI: UE's IMSI value # Key: UE's key, where other keys are derived from. Stored in hexadecimal # OP_Type: Operator's code type, either OP or OPc # OP/OPc: Operator Code/Cyphered Operator Code, stored in hexadecimal # AMF: Authentication management field, stored in hexadecimal # SQN: UE's Sequence number for freshness of the authentication # QCI: QoS Class Identifier for the UE's default bearer. # IP_alloc: IP allocation stratagy for the SPGW. # With 'dynamic' the SPGW will automatically allocate IPs # With a valid IPv4 (e.g. '172.16.0.2') the UE will have a statically assigned IP. # # Note: Lines starting by '#' are ignored and will be overwritten ue2,mil,001010123456780,00112233445566778899aabbccddeeff,opc,63bfa50ee6523365ff14c1f45f88737d,8000,000000001234,7,172.16.0.2 ue1,mil,901700000044980,82e9053a1882085ff2c020359938dae9,opc,bfd5771aaf4f6728e9bc6ef2c2533bdb,8437,00000000919a,7,172.16.0.3 ue3,mil,901700000044981,aa32df28e6f1ec860ed4b6d485d24c31,opc,d72f9533d860aea319d5dac95c6b5037,8438,0000000020cb,7,172.16.0.4 ue4,mil,901700000044982,8ca8891528cb25f046b13829283b0571,opc,c307259c2acc10253b68100bb249a117,8438,000000003407,7,172.16.0.5 ue5,mil,901700000044983,38d8c889d60b4cc9e6d5f00a0a1167cc,opc,166df27f5c79f2a1a2cb8349ec2f802a,8438,000000002ba3,7,172.16.0.6 ue6,mil,901700000044984,66c36c2b333b4d080e6913f51a7e9385,opc,17a44e6b270f1748ca7282d2b3da6899,8438,00000000386a,7,172.16.0.7 ue7,mil,901700000044985,e23b82b102293695c68931cd42a9e272,opc,c7a91401ec96a8a3284ec5b776da4b39,8438,000000002e16,7,172.16.0.8 ue8,mil,901700000044986,de98f28abd8caf114c5e968380a10153,opc,a72233bbc4e9860c60fdc85c30927716,9000,000000000000,9,172.16.0.9 *ue9,mil,901700000044987,833218d615b110706db6e7fd69222be9,opc,d0c41ed07dfe2f9bb0db083e5e347f5e,9000,0000000000c6,9,172.16.0.10* ue10,mil,901700000044988,df7720883094f1724e5f2158bc779bf3,opc,0ba0e79d6e79849beb40cd4badb803e5,9000,000000000000,9,172.16.0.11 *Started SRS (enb and epc), SIM in UE* *SRSepc stdout:* S1 Setup Request - eNB Name: srsenb01, eNB id: 0x19b S1 Setup Request - MCC:001, MNC:01 S1 Setup Request - TAC 7, B-PLMN 0xf110 S1 Setup Request - Paging DRX v128 Sending S1 Setup Response Initial UE message: LIBLTE_MME_MSG_TYPE_ATTACH_REQUEST Received Initial UE message -- Attach Request Attach request -- IMSI: 901700000044987 Attach request -- eNB-UE S1AP Id: 1 Attach request -- Attach type: 2 Attach Request -- UE Network Capabilities EEA: 11100000 Attach Request -- UE Network Capabilities EIA: 01100000 Attach Request -- MS Network Capabilities Present: true PDN Connectivity Request -- EPS Bearer Identity requested: 0 PDN Connectivity Request -- Procedure Transaction Id: 1 PDN Connectivity Request -- ESM Information Transfer requested: true Downlink NAS: Sending Authentication Request UL NAS: Authentication Failure MAC code failure Received UE Context Release Request. MME-UE S1AP Id 1 *epc.log (I have noticed that is two hours behind the computer time, which is probably GMT, not sure if it matters and is indication of timing used wrongly somewhere...):* 07:28:11.784226 [EPC ] [I] Built in Release mode using commit 89f16eed2 on branch master. --- Software Radio Systems EPC log --- 07:28:11.784232 [EPC ] [I] Using binary srsepc with arguments: 07:28:11.784294 [HSS ] [I] Opened DB file: /home/enodeb/.config/srsran/user_db.csv 07:28:11.784326 [HSS ] [D] Added user from DB, IMSI: 001010123456780 07:28:11.784327 [HSS ] [D] User Key : 0000: 00 11 22 33 44 55 66 77 88 99 aa bb cc dd ee ff 07:28:11.784328 [HSS ] [D] User OPc : 0000: 63 bf a5 0e e6 52 33 65 ff 14 c1 f4 5f 88 73 7d 07:28:11.784329 [HSS ] [D] AMF : 0000: 80 00 07:28:11.784330 [HSS ] [D] SQN : 0000: 00 00 00 00 12 34 07:28:11.784330 [HSS ] [D] Default Bearer QCI: 7 07:28:11.784336 [HSS ] [I] static ip addr 172.16.0.2 07:28:11.784347 [HSS ] [D] Added user from DB, IMSI: 901700000044980 07:28:11.784348 [HSS ] [D] User Key : 0000: 82 e9 05 3a 18 82 08 5f f2 c0 20 35 99 38 da e9 07:28:11.784348 [HSS ] [D] User OPc : 0000: bf d5 77 1a af 4f 67 28 e9 bc 6e f2 c2 53 3b db 07:28:11.784349 [HSS ] [D] AMF : 0000: 84 37 07:28:11.784349 [HSS ] [D] SQN : 0000: 00 00 00 00 91 9a 07:28:11.784349 [HSS ] [D] Default Bearer QCI: 7 07:28:11.784350 [HSS ] [I] static ip addr 172.16.0.3 07:28:11.784361 [HSS ] [D] Added user from DB, IMSI: 901700000044981 07:28:11.784361 [HSS ] [D] User Key : 0000: aa 32 df 28 e6 f1 ec 86 0e d4 b6 d4 85 d2 4c 31 07:28:11.784361 [HSS ] [D] User OPc : 0000: d7 2f 95 33 d8 60 ae a3 19 d5 da c9 5c 6b 50 37 07:28:11.784362 [HSS ] [D] AMF : 0000: 84 38 07:28:11.784362 [HSS ] [D] SQN : 0000: 00 00 00 00 20 cb 07:28:11.784362 [HSS ] [D] Default Bearer QCI: 7 07:28:11.784363 [HSS ] [I] static ip addr 172.16.0.4 07:28:11.784373 [HSS ] [D] Added user from DB, IMSI: 901700000044982 07:28:11.784373 [HSS ] [D] User Key : 0000: 8c a8 89 15 28 cb 25 f0 46 b1 38 29 28 3b 05 71 07:28:11.784374 [HSS ] [D] User OPc : 0000: c3 07 25 9c 2a cc 10 25 3b 68 10 0b b2 49 a1 17 07:28:11.784374 [HSS ] [D] AMF : 0000: 84 38 07:28:11.784374 [HSS ] [D] SQN : 0000: 00 00 00 00 34 07 07:28:11.784375 [HSS ] [D] Default Bearer QCI: 7 07:28:11.784375 [HSS ] [I] static ip addr 172.16.0.5 07:28:11.784386 [HSS ] [D] Added user from DB, IMSI: 901700000044983 07:28:11.784387 [HSS ] [D] User Key : 0000: 38 d8 c8 89 d6 0b 4c c9 e6 d5 f0 0a 0a 11 67 cc 07:28:11.784387 [HSS ] [D] User OPc : 0000: 16 6d f2 7f 5c 79 f2 a1 a2 cb 83 49 ec 2f 80 2a 07:28:11.784387 [HSS ] [D] AMF : 0000: 84 38 07:28:11.784387 [HSS ] [D] SQN : 0000: 00 00 00 00 2b a3 07:28:11.784388 [HSS ] [D] Default Bearer QCI: 7 07:28:11.784389 [HSS ] [I] static ip addr 172.16.0.6 07:28:11.784399 [HSS ] [D] Added user from DB, IMSI: 901700000044984 07:28:11.784399 [HSS ] [D] User Key : 0000: 66 c3 6c 2b 33 3b 4d 08 0e 69 13 f5 1a 7e 93 85 07:28:11.784399 [HSS ] [D] User OPc : 0000: 17 a4 4e 6b 27 0f 17 48 ca 72 82 d2 b3 da 68 99 07:28:11.784400 [HSS ] [D] AMF : 0000: 84 38 07:28:11.784400 [HSS ] [D] SQN : 0000: 00 00 00 00 38 6a 07:28:11.784401 [HSS ] [D] Default Bearer QCI: 7 07:28:11.784401 [HSS ] [I] static ip addr 172.16.0.7 07:28:11.784412 [HSS ] [D] Added user from DB, IMSI: 901700000044985 07:28:11.784412 [HSS ] [D] User Key : 0000: e2 3b 82 b1 02 29 36 95 c6 89 31 cd 42 a9 e2 72 07:28:11.784412 [HSS ] [D] User OPc : 0000: c7 a9 14 01 ec 96 a8 a3 28 4e c5 b7 76 da 4b 39 07:28:11.784413 [HSS ] [D] AMF : 0000: 84 38 07:28:11.784413 [HSS ] [D] SQN : 0000: 00 00 00 00 2e 16 07:28:11.784414 [HSS ] [D] Default Bearer QCI: 7 07:28:11.784414 [HSS ] [I] static ip addr 172.16.0.8 07:28:11.784425 [HSS ] [D] Added user from DB, IMSI: 901700000044986 07:28:11.784425 [HSS ] [D] User Key : 0000: de 98 f2 8a bd 8c af 11 4c 5e 96 83 80 a1 01 53 07:28:11.784426 [HSS ] [D] User OPc : 0000: a7 22 33 bb c4 e9 86 0c 60 fd c8 5c 30 92 77 16 07:28:11.784426 [HSS ] [D] AMF : 0000: 90 00 07:28:11.784426 [HSS ] [D] SQN : 0000: 00 00 00 00 00 00 07:28:11.784427 [HSS ] [D] Default Bearer QCI: 9 07:28:11.784427 [HSS ] [I] static ip addr 172.16.0.9 07:28:11.784438 [HSS ] [D] Added user from DB, IMSI: 901700000044987 07:28:11.784438 [HSS ] [D] User Key : 0000: 83 32 18 d6 15 b1 10 70 6d b6 e7 fd 69 22 2b e9 07:28:11.784438 [HSS ] [D] User OPc : 0000: d0 c4 1e d0 7d fe 2f 9b b0 db 08 3e 5e 34 7f 5e 07:28:11.784439 [HSS ] [D] AMF : 0000: 90 00 07:28:11.784439 [HSS ] [D] SQN : 0000: 00 00 00 00 00 e7 07:28:11.784439 [HSS ] [D] Default Bearer QCI: 9 07:28:11.784440 [HSS ] [I] static ip addr 172.16.0.10 07:28:11.784452 [HSS ] [D] Added user from DB, IMSI: 901700000044988 07:28:11.784454 [HSS ] [D] User Key : 0000: df 77 20 88 30 94 f1 72 4e 5f 21 58 bc 77 9b f3 07:28:11.784455 [HSS ] [D] User OPc : 0000: 0b a0 e7 9d 6e 79 84 9b eb 40 cd 4b ad b8 03 e5 07:28:11.784455 [HSS ] [D] AMF : 0000: 90 00 07:28:11.784457 [HSS ] [D] SQN : 0000: 00 00 00 00 00 00 07:28:11.784457 [HSS ] [D] Default Bearer QCI: 9 07:28:11.784458 [HSS ] [I] static ip addr 172.16.0.11 07:28:11.784465 [HSS ] [I] HSS Initialized. DB file /home/enodeb/.config/srsran/user_db.csv, MCC: 61441, MNC: 65281 07:28:11.784494 [S1AP ] [I] S1-MME Initializing 07:28:11.784543 [S1AP ] [I] S1AP Initialized 07:28:11.784544 [MME GTPC] [I] Initializing MME S11 interface. 07:28:11.784555 [MME GTPC] [I] MME S11 Initialized 07:28:11.784561 [MME GTPC] [I] MME GTP-C Initialized 07:28:11.784564 [S1AP ] [I] MME Initialized. MCC: 0xf001, MNC: 0xff01 07:28:11.784595 [GTPU ] [I] TUN file descriptor = 6 07:28:11.794434 [GTPU ] [I] Initialized SGi interface 07:28:11.794458 [GTPU ] [I] S1-U socket = 7 07:28:11.794463 [GTPU ] [I] S1-U IP = 127.0.1.100, Port = 2152 07:28:11.794463 [GTPU ] [I] Initialized S1-U interface 07:28:11.794464 [GTPU ] [I] SPGW GTP-U Initialized. 07:28:11.794770 [SPGW GTPC] [I] Initializing SPGW S11 interface. 07:28:11.794819 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.2 is reserved for imsi 001010123456780, not adding to pool 07:28:11.794826 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.3 is reserved for imsi 901700000044980, not adding to pool 07:28:11.794830 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.4 is reserved for imsi 901700000044981, not adding to pool 07:28:11.794833 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.5 is reserved for imsi 901700000044982, not adding to pool 07:28:11.794835 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.6 is reserved for imsi 901700000044983, not adding to pool 07:28:11.794836 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.7 is reserved for imsi 901700000044984, not adding to pool 07:28:11.794839 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.8 is reserved for imsi 901700000044985, not adding to pool 07:28:11.794841 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.9 is reserved for imsi 901700000044986, not adding to pool 07:28:11.794844 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.10 is reserved for imsi 901700000044987, not adding to pool 07:28:11.794845 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.11 is reserved for imsi 901700000044988, not adding to pool 07:28:11.794848 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.12 is added to pool 07:28:11.794850 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.13 is added to pool 07:28:11.794852 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.14 is added to pool 07:28:11.794853 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.15 is added to pool 07:28:11.794855 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.16 is added to pool 07:28:11.794857 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.17 is added to pool 07:28:11.794859 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.18 is added to pool 07:28:11.794860 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.19 is added to pool 07:28:11.794862 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.20 is added to pool 07:28:11.794864 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.21 is added to pool 07:28:11.794866 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.22 is added to pool 07:28:11.794867 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.23 is added to pool 07:28:11.794869 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.24 is added to pool 07:28:11.794871 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.25 is added to pool 07:28:11.794874 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.26 is added to pool 07:28:11.794875 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.27 is added to pool 07:28:11.794877 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.28 is added to pool 07:28:11.794878 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.29 is added to pool 07:28:11.794880 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.30 is added to pool 07:28:11.794881 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.31 is added to pool 07:28:11.794882 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.32 is added to pool 07:28:11.794884 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.33 is added to pool 07:28:11.794885 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.34 is added to pool 07:28:11.794887 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.35 is added to pool 07:28:11.794888 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.36 is added to pool 07:28:11.794890 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.37 is added to pool 07:28:11.794891 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.38 is added to pool 07:28:11.794893 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.39 is added to pool 07:28:11.794894 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.40 is added to pool 07:28:11.794895 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.41 is added to pool 07:28:11.794897 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.42 is added to pool 07:28:11.794898 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.43 is added to pool 07:28:11.794900 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.44 is added to pool 07:28:11.794901 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.45 is added to pool 07:28:11.794903 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.46 is added to pool 07:28:11.794904 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.47 is added to pool 07:28:11.794906 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.48 is added to pool 07:28:11.794907 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.49 is added to pool 07:28:11.794908 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.50 is added to pool 07:28:11.794910 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.51 is added to pool 07:28:11.794911 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.52 is added to pool 07:28:11.794913 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.53 is added to pool 07:28:11.794915 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.54 is added to pool 07:28:11.794916 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.55 is added to pool 07:28:11.794918 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.56 is added to pool 07:28:11.794920 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.57 is added to pool 07:28:11.794922 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.58 is added to pool 07:28:11.794924 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.59 is added to pool 07:28:11.794925 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.60 is added to pool 07:28:11.794927 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.61 is added to pool 07:28:11.794929 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.62 is added to pool 07:28:11.794930 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.63 is added to pool 07:28:11.794933 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.64 is added to pool 07:28:11.794934 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.65 is added to pool 07:28:11.794936 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.66 is added to pool 07:28:11.794937 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.67 is added to pool 07:28:11.794939 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.68 is added to pool 07:28:11.794941 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.69 is added to pool 07:28:11.794944 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.70 is added to pool 07:28:11.794946 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.71 is added to pool 07:28:11.794948 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.72 is added to pool 07:28:11.794949 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.73 is added to pool 07:28:11.794951 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.74 is added to pool 07:28:11.794953 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.75 is added to pool 07:28:11.794954 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.76 is added to pool 07:28:11.794956 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.77 is added to pool 07:28:11.794958 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.78 is added to pool 07:28:11.794960 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.79 is added to pool 07:28:11.794961 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.80 is added to pool 07:28:11.794963 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.81 is added to pool 07:28:11.794973 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.82 is added to pool 07:28:11.794979 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.83 is added to pool 07:28:11.794981 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.84 is added to pool 07:28:11.794982 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.85 is added to pool 07:28:11.794983 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.86 is added to pool 07:28:11.794984 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.87 is added to pool 07:28:11.794986 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.88 is added to pool 07:28:11.794987 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.89 is added to pool 07:28:11.794989 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.90 is added to pool 07:28:11.794991 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.91 is added to pool 07:28:11.794992 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.92 is added to pool 07:28:11.794994 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.93 is added to pool 07:28:11.794995 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.94 is added to pool 07:28:11.794997 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.95 is added to pool 07:28:11.794998 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.96 is added to pool 07:28:11.795000 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.97 is added to pool 07:28:11.795002 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.98 is added to pool 07:28:11.795003 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.99 is added to pool 07:28:11.795005 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.100 is added to pool 07:28:11.795007 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.101 is added to pool 07:28:11.795008 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.102 is added to pool 07:28:11.795010 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.103 is added to pool 07:28:11.795011 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.104 is added to pool 07:28:11.795013 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.105 is added to pool 07:28:11.795014 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.106 is added to pool 07:28:11.795016 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.107 is added to pool 07:28:11.795017 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.108 is added to pool 07:28:11.795019 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.109 is added to pool 07:28:11.795020 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.110 is added to pool 07:28:11.795022 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.111 is added to pool 07:28:11.795023 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.112 is added to pool 07:28:11.795025 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.113 is added to pool 07:28:11.795027 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.114 is added to pool 07:28:11.795028 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.115 is added to pool 07:28:11.795030 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.116 is added to pool 07:28:11.795032 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.117 is added to pool 07:28:11.795033 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.118 is added to pool 07:28:11.795035 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.119 is added to pool 07:28:11.795036 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.120 is added to pool 07:28:11.795038 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.121 is added to pool 07:28:11.795040 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.122 is added to pool 07:28:11.795043 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.123 is added to pool 07:28:11.795044 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.124 is added to pool 07:28:11.795046 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.125 is added to pool 07:28:11.795048 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.126 is added to pool 07:28:11.795049 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.127 is added to pool 07:28:11.795051 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.128 is added to pool 07:28:11.795054 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.129 is added to pool 07:28:11.795056 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.130 is added to pool 07:28:11.795058 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.131 is added to pool 07:28:11.795059 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.132 is added to pool 07:28:11.795061 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.133 is added to pool 07:28:11.795063 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.134 is added to pool 07:28:11.795065 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.135 is added to pool 07:28:11.795067 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.136 is added to pool 07:28:11.795068 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.137 is added to pool 07:28:11.795070 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.138 is added to pool 07:28:11.795071 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.139 is added to pool 07:28:11.795073 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.140 is added to pool 07:28:11.795074 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.141 is added to pool 07:28:11.795076 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.142 is added to pool 07:28:11.795077 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.143 is added to pool 07:28:11.795079 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.144 is added to pool 07:28:11.795081 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.145 is added to pool 07:28:11.795083 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.146 is added to pool 07:28:11.795085 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.147 is added to pool 07:28:11.795087 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.148 is added to pool 07:28:11.795088 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.149 is added to pool 07:28:11.795092 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.150 is added to pool 07:28:11.795094 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.151 is added to pool 07:28:11.795095 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.152 is added to pool 07:28:11.795097 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.153 is added to pool 07:28:11.795099 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.154 is added to pool 07:28:11.795100 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.155 is added to pool 07:28:11.795103 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.156 is added to pool 07:28:11.795104 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.157 is added to pool 07:28:11.795106 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.158 is added to pool 07:28:11.795108 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.159 is added to pool 07:28:11.795109 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.160 is added to pool 07:28:11.795111 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.161 is added to pool 07:28:11.795112 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.162 is added to pool 07:28:11.795114 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.163 is added to pool 07:28:11.795116 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.164 is added to pool 07:28:11.795117 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.165 is added to pool 07:28:11.795119 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.166 is added to pool 07:28:11.795120 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.167 is added to pool 07:28:11.795126 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.168 is added to pool 07:28:11.795127 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.169 is added to pool 07:28:11.795129 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.170 is added to pool 07:28:11.795132 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.171 is added to pool 07:28:11.795134 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.172 is added to pool 07:28:11.795135 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.173 is added to pool 07:28:11.795137 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.174 is added to pool 07:28:11.795138 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.175 is added to pool 07:28:11.795140 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.176 is added to pool 07:28:11.795141 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.177 is added to pool 07:28:11.795143 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.178 is added to pool 07:28:11.795145 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.179 is added to pool 07:28:11.795146 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.180 is added to pool 07:28:11.795150 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.181 is added to pool 07:28:11.795151 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.182 is added to pool 07:28:11.795153 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.183 is added to pool 07:28:11.795155 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.184 is added to pool 07:28:11.795156 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.185 is added to pool 07:28:11.795158 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.186 is added to pool 07:28:11.795160 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.187 is added to pool 07:28:11.795161 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.188 is added to pool 07:28:11.795163 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.189 is added to pool 07:28:11.795167 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.190 is added to pool 07:28:11.795168 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.191 is added to pool 07:28:11.795170 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.192 is added to pool 07:28:11.795171 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.193 is added to pool 07:28:11.795174 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.194 is added to pool 07:28:11.795176 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.195 is added to pool 07:28:11.795179 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.196 is added to pool 07:28:11.795181 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.197 is added to pool 07:28:11.795182 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.198 is added to pool 07:28:11.795184 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.199 is added to pool 07:28:11.795186 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.200 is added to pool 07:28:11.795187 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.201 is added to pool 07:28:11.795189 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.202 is added to pool 07:28:11.795190 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.203 is added to pool 07:28:11.795191 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.204 is added to pool 07:28:11.795193 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.205 is added to pool 07:28:11.795194 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.206 is added to pool 07:28:11.795196 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.207 is added to pool 07:28:11.795197 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.208 is added to pool 07:28:11.795199 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.209 is added to pool 07:28:11.795201 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.210 is added to pool 07:28:11.795202 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.211 is added to pool 07:28:11.795204 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.212 is added to pool 07:28:11.795205 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.213 is added to pool 07:28:11.795207 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.214 is added to pool 07:28:11.795208 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.215 is added to pool 07:28:11.795210 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.216 is added to pool 07:28:11.795212 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.217 is added to pool 07:28:11.795213 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.218 is added to pool 07:28:11.795215 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.219 is added to pool 07:28:11.795217 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.220 is added to pool 07:28:11.795219 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.221 is added to pool 07:28:11.795221 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.222 is added to pool 07:28:11.795223 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.223 is added to pool 07:28:11.795224 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.224 is added to pool 07:28:11.795226 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.225 is added to pool 07:28:11.795228 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.226 is added to pool 07:28:11.795231 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.227 is added to pool 07:28:11.795233 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.228 is added to pool 07:28:11.795234 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.229 is added to pool 07:28:11.795236 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.230 is added to pool 07:28:11.795238 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.231 is added to pool 07:28:11.795239 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.232 is added to pool 07:28:11.795241 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.233 is added to pool 07:28:11.795242 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.234 is added to pool 07:28:11.795245 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.235 is added to pool 07:28:11.795248 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.236 is added to pool 07:28:11.795250 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.237 is added to pool 07:28:11.795251 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.238 is added to pool 07:28:11.795254 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.239 is added to pool 07:28:11.795255 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.240 is added to pool 07:28:11.795257 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.241 is added to pool 07:28:11.795258 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.242 is added to pool 07:28:11.795260 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.243 is added to pool 07:28:11.795262 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.244 is added to pool 07:28:11.795264 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.245 is added to pool 07:28:11.795266 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.246 is added to pool 07:28:11.795267 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.247 is added to pool 07:28:11.795269 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.248 is added to pool 07:28:11.795272 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.249 is added to pool 07:28:11.795273 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.250 is added to pool 07:28:11.795275 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.251 is added to pool 07:28:11.795277 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.252 is added to pool 07:28:11.795278 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.253 is added to pool 07:28:11.795283 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.254 is added to pool 07:28:11.795283 [SPGW GTPC] [I] SPGW S11 Initialized. 07:28:11.795389 [SPGW ] [I] SP-GW Initialized. 07:28:11.845666 [S1AP ] [D] Waiting for S1-MME or S11 Message 07:28:11.845712 [SPGW ] [D] Message received at SPGW: SGi Message 07:28:11.845721 [GTPU ] [D] Received SGi PDU. Bytes 48 07:28:11.845722 [GTPU ] [I] IPv6 not supported yet. 07:28:11.927805 [S1AP ] [I] Received S1AP msg. Size: 49 07:28:11.927922 [S1AP ] [I] Received Initiating PDU 07:28:11.927926 [S1AP ] [I] Received S1 Setup Request. 07:28:11.927942 [S1AP ] [I] Received S1 Setup Request. 07:28:11.927948 [S1AP ] [D] eNB SCTP association Id: 16 07:28:11.927956 [S1AP ] [I] S1 Setup Request - eNB Name: srsenb01, eNB id: 0x19b 07:28:11.927958 [S1AP ] [I] S1 Setup Request - MCC:001, MNC:01, PLMN: 61712 07:28:11.927962 [S1AP ] [I] S1 Setup Request - TAC 7, B-PLMN 0xf110 07:28:11.927974 [S1AP ] [I] Adding new eNB context. eNB ID 411 07:28:11.927994 [S1AP ] [D] Sending S1 Setup Response 07:28:11.928008 [S1AP ] [D] Transmitting S1AP PDU. eNB SCTP association Id: 16 07:28:11.928055 [S1AP ] [D] S1 Setup Response sent 07:28:11.928070 [S1AP ] [I] Sending S1 Setup Response 07:28:11.928074 [S1AP ] [D] Waiting for S1-MME or S11 Message 07:28:15.607044 [SPGW ] [D] Message received at SPGW: SGi Message 07:28:15.607073 [GTPU ] [D] Received SGi PDU. Bytes 48 07:28:15.607075 [GTPU ] [I] IPv6 not supported yet. 07:28:23.035084 [SPGW ] [D] Message received at SPGW: SGi Message 07:28:23.035098 [GTPU ] [D] Received SGi PDU. Bytes 48 07:28:23.035099 [GTPU ] [I] IPv6 not supported yet. 07:28:37.623202 [SPGW ] [D] Message received at SPGW: SGi Message 07:28:37.623237 [GTPU ] [D] Received SGi PDU. Bytes 48 07:28:37.623240 [GTPU ] [I] IPv6 not supported yet. 07:29:08.599129 [SPGW ] [D] Message received at SPGW: SGi Message 07:29:08.599156 [GTPU ] [D] Received SGi PDU. Bytes 48 07:29:08.599158 [GTPU ] [I] IPv6 not supported yet. 07:30:10.039051 [SPGW ] [D] Message received at SPGW: SGi Message 07:30:10.039083 [GTPU ] [D] Received SGi PDU. Bytes 48 07:30:10.039086 [GTPU ] [I] IPv6 not supported yet. 07:32:06.775054 [SPGW ] [D] Message received at SPGW: SGi Message 07:32:06.775075 [GTPU ] [D] Received SGi PDU. Bytes 48 07:32:06.775078 [GTPU ] [I] IPv6 not supported yet. 07:32:46.340945 [S1AP ] [I] Received S1AP msg. Size: 114 07:32:46.341016 [S1AP ] [I] Received Initiating PDU 07:32:46.341024 [S1AP ] [I] Received Initial UE Message. 07:32:46.341121 [S1AP ] [I] Initial UE message: LIBLTE_MME_MSG_TYPE_ATTACH_REQUEST 07:32:46.341142 [S1AP ] [I] Received Initial UE message -- Attach Request 07:32:46.341229 [NAS ] [I] Attach request -- IMSI: 901700000044987 07:32:46.341249 [NAS ] [I] Attach request -- eNB-UE S1AP Id: 1 07:32:46.341256 [NAS ] [I] Attach request -- Attach type: 2 07:32:46.341266 [NAS ] [I] Attach Request -- UE Network Capabilities EEA: 11100000 07:32:46.341282 [NAS ] [I] Attach Request -- UE Network Capabilities EIA: 01100000 07:32:46.341299 [NAS ] [I] Attach Request -- MS Network Capabilities Present: true 07:32:46.341306 [NAS ] [I] PDN Connectivity Request -- EPS Bearer Identity requested: 0 07:32:46.341312 [NAS ] [I] PDN Connectivity Request -- Procedure Transaction Id: 1 07:32:46.341322 [NAS ] [I] PDN Connectivity Request -- ESM Information Transfer requested: true 07:32:46.341350 [NAS ] [D] NAS Context Initialized. MCC: 0xf001, MNC 0xff01 07:32:46.341359 [HSS ] [D] Generating AUTH info answer 07:32:46.341397 [HSS ] [D] User Key : 0000: 83 32 18 d6 15 b1 10 70 6d b6 e7 fd 69 22 2b e9 07:32:46.341405 [HSS ] [D] User OPc : 0000: d0 c4 1e d0 7d fe 2f 9b b0 db 08 3e 5e 34 7f 5e 07:32:46.341407 [HSS ] [D] User Rand : 0000: c6 0f b8 f2 fd 46 a9 c3 cf 05 50 7f e6 c3 e8 ad 07:32:46.341409 [HSS ] [D] User XRES: 0000: 9c f2 5e cf 5c ba 33 5c 07:32:46.341411 [HSS ] [D] User CK: 0000: e0 ea 1a 80 a2 14 18 8c bb cd 27 a3 f3 9d 69 b6 07:32:46.341413 [HSS ] [D] User IK: 0000: b4 09 56 cb 41 aa 18 2e 35 cd 8a 0a 91 b4 3f 8e 07:32:46.341414 [HSS ] [D] User AK: 0000: 80 63 4c 08 c8 05 07:32:46.341416 [HSS ] [D] User SQN : 0000: 00 00 00 00 00 e7 07:32:46.341418 [HSS ] [D] User MAC : 0000: bf 9b 72 8a 71 e8 26 01 07:32:46.341456 [HSS ] [D] User MCC : f001 MNC : ff01 07:32:46.341458 [HSS ] [D] User k_asme : 0000: 00 2d bf 35 52 67 fe 45 cb 66 62 c0 6c 5e 01 be 0010: 7f 25 d1 71 50 33 8a ce a1 bb 73 e8 4e 35 b1 57 07:32:46.341459 [HSS ] [D] User AUTN: 0000: 80 63 4c 08 c8 e2 90 00 bf 9b 72 8a 71 e8 26 01 07:32:46.341461 [HSS ] [D] Incremented SQN -- IMSI: 901700000044987 07:32:46.341462 [HSS ] [D] SQN: 0000: 00 00 00 00 01 08 07:32:46.341464 [S1AP ] [D] Saved UE context corresponding to IMSI 901700000044987 07:32:46.341465 [S1AP ] [D] Saved UE context corresponding to MME UE S1AP Id 1 07:32:46.341467 [S1AP ] [D] Added UE with MME-UE S1AP Id 1 to eNB with association 16 07:32:46.341468 [NAS ] [I] Packing Authentication Request 07:32:46.341481 [S1AP ] [D] Sending message to eNB with SCTP association 16. MME UE S1AP ID 1, eNB UE S1AP ID 1 07:32:46.341528 [S1AP ] [D] Transmitting S1AP PDU. eNB SCTP association Id: 16 07:32:46.341712 [NAS ] [I] Downlink NAS: Sending Authentication Request 07:32:46.341737 [S1AP ] [D] Waiting for S1-MME or S11 Message 07:32:46.389109 [S1AP ] [I] Received S1AP msg. Size: 49 07:32:46.389146 [S1AP ] [I] Received Initiating PDU 07:32:46.389150 [S1AP ] [I] Received Uplink NAS Transport Message. 07:32:46.389152 [S1AP ] [D] Received uplink NAS and found UE NAS context. MME-UE S1AP id: 1 07:32:46.389157 [S1AP ] [I] UL NAS: sec_hdr_type: LIBLTE_MME_SECURITY_HDR_TYPE_PLAIN_NAS, mac_vaild: no, msg_encrypted: no 07:32:46.389158 [S1AP ] [I] UL NAS: Authentication Failure 07:32:46.389189 [NAS ] [I] Received Authentication Failure 07:32:46.389201 [NAS ] [I] MAC code failure 07:32:46.389205 [S1AP ] [D] Waiting for S1-MME or S11 Message 07:33:16.341382 [S1AP ] [I] Received S1AP msg. Size: 25 07:33:16.341425 [S1AP ] [I] Received Initiating PDU 07:33:16.341428 [S1AP ] [I] Received UE Context Release Request Message. 07:33:16.341431 [S1AP ] [I] Received UE Context Release Request. MME-UE S1AP Id: 1 07:33:16.341477 [S1AP ] [I] UE is not ECM connected. No need to release S1-U. MME UE S1AP Id 1 07:33:16.341483 [S1AP ] [D] Waiting for S1-MME or S11 Message 07:36:00.247148 [SPGW ] [D] Message received at SPGW: SGi Message 07:36:00.247183 [GTPU ] [D] Received SGi PDU. Bytes 48 07:36:00.247187 [GTPU ] [I] IPv6 not supported yet. 07:36:31.885971 [S1AP ] [I] Received S1AP msg. Size: 114 07:36:31.886033 [S1AP ] [I] Received Initiating PDU 07:36:31.886041 [S1AP ] [I] Received Initial UE Message. 07:36:31.886194 [S1AP ] [I] Initial UE message: LIBLTE_MME_MSG_TYPE_ATTACH_REQUEST 07:36:31.886226 [S1AP ] [I] Received Initial UE message -- Attach Request 07:36:31.886259 [NAS ] [I] Attach request -- IMSI: 901700000044987 07:36:31.886277 [NAS ] [I] Attach request -- eNB-UE S1AP Id: 2 07:36:31.886289 [NAS ] [I] Attach request -- Attach type: 2 07:36:31.886301 [NAS ] [I] Attach Request -- UE Network Capabilities EEA: 11100000 07:36:31.886313 [NAS ] [I] Attach Request -- UE Network Capabilities EIA: 01100000 07:36:31.886330 [NAS ] [I] Attach Request -- MS Network Capabilities Present: true 07:36:31.886341 [NAS ] [I] PDN Connectivity Request -- EPS Bearer Identity requested: 0 07:36:31.886350 [NAS ] [I] PDN Connectivity Request -- Procedure Transaction Id: 1 07:36:31.886360 [NAS ] [I] PDN Connectivity Request -- ESM Information Transfer requested: true 07:36:31.886362 [NAS ] [I] Attach Request -- Found previously attached UE. 07:36:31.886372 [MME GTPC] [I] Sending GTP-C Delete Session Request request. IMSI 901700000044987 07:36:31.886374 [MME GTPC] [E] Could not find GTP-C context to remove 07:36:31.886377 [S1AP ] [E] UE is not ECM connected. No send context release command. MME UE S1AP Id 1 07:36:31.886383 [S1AP ] [I] Released UE ECM Context. 07:36:31.886387 [S1AP ] [I] Deleted UE Context. 07:36:31.886396 [NAS ] [D] NAS Context Initialized. MCC: 0xf001, MNC 0xff01 07:36:31.886399 [HSS ] [D] Generating AUTH info answer 07:36:31.886407 [HSS ] [D] User Key : 0000: 83 32 18 d6 15 b1 10 70 6d b6 e7 fd 69 22 2b e9 07:36:31.886409 [HSS ] [D] User OPc : 0000: d0 c4 1e d0 7d fe 2f 9b b0 db 08 3e 5e 34 7f 5e 07:36:31.886411 [HSS ] [D] User Rand : 0000: 16 06 1d 16 3d 19 dd 43 65 d5 c1 f5 f5 ac 00 bb 07:36:31.886413 [HSS ] [D] User XRES: 0000: 8c fc 70 3e d0 99 00 7c 07:36:31.886415 [HSS ] [D] User CK: 0000: 53 cc 5c 3e 5a ae 68 a5 7e 25 70 09 0a f9 4b bf 07:36:31.886417 [HSS ] [D] User IK: 0000: 0a 0b 34 c5 d8 53 da d4 57 f0 68 76 fc 31 b5 23 07:36:31.886419 [HSS ] [D] User AK: 0000: 2b 91 b0 a2 97 a8 07:36:31.886422 [HSS ] [D] User SQN : 0000: 00 00 00 00 01 08 07:36:31.886425 [HSS ] [D] User MAC : 0000: 94 de 12 11 56 0f a2 09 07:36:31.886445 [HSS ] [D] User MCC : f001 MNC : ff01 07:36:31.886447 [HSS ] [D] User k_asme : 0000: 59 09 e2 cd 49 f3 3f ea c1 7c 41 ea ee 02 08 0e 0010: 8b cc 13 ad 14 e0 7d 86 de 85 80 e9 4b 45 fb ff 07:36:31.886449 [HSS ] [D] User AUTN: 0000: 2b 91 b0 a2 96 a0 90 00 94 de 12 11 56 0f a2 09 07:36:31.886452 [HSS ] [D] Incremented SQN -- IMSI: 901700000044987 07:36:31.886454 [HSS ] [D] SQN: 0000: 00 00 00 00 01 29 07:36:31.886458 [S1AP ] [D] Saved UE context corresponding to IMSI 901700000044987 07:36:31.886460 [S1AP ] [D] Saved UE context corresponding to MME UE S1AP Id 2 07:36:31.886462 [S1AP ] [D] Added UE with MME-UE S1AP Id 2 to eNB with association 16 07:36:31.886464 [NAS ] [I] Packing Authentication Request 07:36:31.886468 [S1AP ] [D] Sending message to eNB with SCTP association 16. MME UE S1AP ID 2, eNB UE S1AP ID 2 07:36:31.886486 [S1AP ] [D] Transmitting S1AP PDU. eNB SCTP association Id: 16 07:36:31.886778 [NAS ] [I] Downlink NAS: Sending Authentication Request 07:36:31.886817 [S1AP ] [D] Waiting for S1-MME or S11 Message 07:36:31.925701 [S1AP ] [I] Received S1AP msg. Size: 49 07:36:31.925737 [S1AP ] [I] Received Initiating PDU 07:36:31.925742 [S1AP ] [I] Received Uplink NAS Transport Message. 07:36:31.925744 [S1AP ] [D] Received uplink NAS and found UE NAS context. MME-UE S1AP id: 2 07:36:31.925747 [S1AP ] [I] UL NAS: sec_hdr_type: LIBLTE_MME_SECURITY_HDR_TYPE_PLAIN_NAS, mac_vaild: no, msg_encrypted: no 07:36:31.925748 [S1AP ] [I] UL NAS: Authentication Failure 07:36:31.925769 [NAS ] [I] Received Authentication Failure 07:36:31.925777 [NAS ] [I] MAC code failure 07:36:31.925781 [S1AP ] [D] Waiting for S1-MME or S11 Message 07:37:01.885966 [S1AP ] [I] Received S1AP msg. Size: 25 07:37:01.885984 [S1AP ] [I] Received Initiating PDU 07:37:01.885985 [S1AP ] [I] Received UE Context Release Request Message. 07:37:01.885986 [S1AP ] [I] Received UE Context Release Request. MME-UE S1AP Id: 2 07:37:01.886006 [S1AP ] [I] UE is not ECM connected. No need to release S1-U. MME UE S1AP Id 2 07:37:01.886008 [S1AP ] [D] Waiting for S1-MME or S11 Message 07:37:25.148615 [S1AP ] [I] Received S1AP msg. Size: 114 07:37:25.148676 [S1AP ] [I] Received Initiating PDU 07:37:25.148679 [S1AP ] [I] Received Initial UE Message. 07:37:25.148725 [S1AP ] [I] Initial UE message: LIBLTE_MME_MSG_TYPE_ATTACH_REQUEST 07:37:25.148740 [S1AP ] [I] Received Initial UE message -- Attach Request 07:37:25.148772 [NAS ] [I] Attach request -- IMSI: 901700000044987 07:37:25.148796 [NAS ] [I] Attach request -- eNB-UE S1AP Id: 3 07:37:25.148809 [NAS ] [I] Attach request -- Attach type: 2 07:37:25.148828 [NAS ] [I] Attach Request -- UE Network Capabilities EEA: 11100000 07:37:25.148844 [NAS ] [I] Attach Request -- UE Network Capabilities EIA: 01100000 07:37:25.148861 [NAS ] [I] Attach Request -- MS Network Capabilities Present: true 07:37:25.148871 [NAS ] [I] PDN Connectivity Request -- EPS Bearer Identity requested: 0 07:37:25.148881 [NAS ] [I] PDN Connectivity Request -- Procedure Transaction Id: 2 07:37:25.148891 [NAS ] [I] PDN Connectivity Request -- ESM Information Transfer requested: true 07:37:25.148893 [NAS ] [I] Attach Request -- Found previously attached UE. 07:37:25.149300 [MME GTPC] [I] Sending GTP-C Delete Session Request request. IMSI 901700000044987 07:37:25.149315 [MME GTPC] [E] Could not find GTP-C context to remove 07:37:25.149319 [S1AP ] [E] UE is not ECM connected. No send context release command. MME UE S1AP Id 2 07:37:25.149326 [S1AP ] [I] Released UE ECM Context. 07:37:25.149330 [S1AP ] [I] Deleted UE Context. 07:37:25.149341 [NAS ] [D] NAS Context Initialized. MCC: 0xf001, MNC 0xff01 07:37:25.149345 [HSS ] [D] Generating AUTH info answer 07:37:25.149354 [HSS ] [D] User Key : 0000: 83 32 18 d6 15 b1 10 70 6d b6 e7 fd 69 22 2b e9 07:37:25.149363 [HSS ] [D] User OPc : 0000: d0 c4 1e d0 7d fe 2f 9b b0 db 08 3e 5e 34 7f 5e 07:37:25.149366 [HSS ] [D] User Rand : 0000: bc b8 ae b9 fe 57 7c cd 5c cc 4d 43 8f 35 f0 a5 07:37:25.149368 [HSS ] [D] User XRES: 0000: a5 e8 58 32 f9 59 28 07 07:37:25.149370 [HSS ] [D] User CK: 0000: 0b 72 c7 5c 11 0e a9 5b 88 4a e1 9e a6 21 f6 3b 07:37:25.149372 [HSS ] [D] User IK: 0000: 0a 96 88 bf f5 f7 5d 13 e7 20 cd d2 06 55 b6 a4 07:37:25.149374 [HSS ] [D] User AK: 0000: 2c ac 00 8a 54 53 07:37:25.149377 [HSS ] [D] User SQN : 0000: 00 00 00 00 01 29 07:37:25.149380 [HSS ] [D] User MAC : 0000: a4 62 ec c8 91 cb 82 6b 07:37:25.149402 [HSS ] [D] User MCC : f001 MNC : ff01 07:37:25.149406 [HSS ] [D] User k_asme : 0000: c0 3a f6 a2 91 97 a0 0e 9f 1c 1f 40 17 de 64 66 0010: 31 65 0d 76 6f 21 15 52 b9 08 72 20 3e 60 8a 58 07:37:25.149412 [HSS ] [D] User AUTN: 0000: 2c ac 00 8a 55 7a 90 00 a4 62 ec c8 91 cb 82 6b 07:37:25.149415 [HSS ] [D] Incremented SQN -- IMSI: 901700000044987 07:37:25.149514 [HSS ] [D] SQN: 0000: 00 00 00 00 01 4a 07:37:25.149519 [S1AP ] [D] Saved UE context corresponding to IMSI 901700000044987 07:37:25.149522 [S1AP ] [D] Saved UE context corresponding to MME UE S1AP Id 3 07:37:25.149524 [S1AP ] [D] Added UE with MME-UE S1AP Id 3 to eNB with association 16 07:37:25.149525 [NAS ] [I] Packing Authentication Request 07:37:25.149529 [S1AP ] [D] Sending message to eNB with SCTP association 16. MME UE S1AP ID 3, eNB UE S1AP ID 3 07:37:25.149546 [S1AP ] [D] Transmitting S1AP PDU. eNB SCTP association Id: 16 07:37:25.149648 [NAS ] [I] Downlink NAS: Sending Authentication Request 07:37:25.149690 [S1AP ] [D] Waiting for S1-MME or S11 Message 07:37:25.188933 [S1AP ] [I] Received S1AP msg. Size: 49 07:37:25.189031 [S1AP ] [I] Received Initiating PDU 07:37:25.189033 [S1AP ] [I] Received Uplink NAS Transport Message. 07:37:25.189036 [S1AP ] [D] Received uplink NAS and found UE NAS context. MME-UE S1AP id: 3 07:37:25.189042 [S1AP ] [I] UL NAS: sec_hdr_type: LIBLTE_MME_SECURITY_HDR_TYPE_PLAIN_NAS, mac_vaild: no, msg_encrypted: no 07:37:25.189043 [S1AP ] [I] UL NAS: Authentication Failure 07:37:25.189172 [NAS ] [I] Received Authentication Failure 07:37:25.189188 [NAS ] [I] MAC code failure 07:37:25.189194 [S1AP ] [D] Waiting for S1-MME or S11 Message 07:37:55.148782 [S1AP ] [I] Received S1AP msg. Size: 25 07:37:55.148863 [S1AP ] [I] Received Initiating PDU 07:37:55.148871 [S1AP ] [I] Received UE Context Release Request Message. 07:37:55.148874 [S1AP ] [I] Received UE Context Release Request. MME-UE S1AP Id: 3 07:37:55.148912 [S1AP ] [I] UE is not ECM connected. No need to release S1-U. MME UE S1AP Id 3 07:37:55.148917 [S1AP ] [D] Waiting for S1-MME or S11 Message 07:38:10.619267 [S1AP ] [I] Deleting eNB context. eNB Id: 0x19b 07:38:10.619320 [S1AP ] [I] Deleting UE EMM context. IMSI: 901700000044987 07:38:10.652215 [HSS ] [I] Opened DB file: /home/enodeb/.config/srsran/user_db.csv

2 years, 8 months

1
1
0 0

long long vs int64_t

by Neels Hofmeyr

On Wed, Sep 15, 2021 at 02:45:42AM +0000, scan-admin(a)coverity.com wrote: > >>> CID 240103: (CONSTANT_EXPRESSION_RESULT) > >>> "val < -9223372036854775808LL /* -9223372036854775807L - 1 */" is always false regardless of the values of its operands. This occurs as the logical operand of "if". > 1434 if (val < INT64_MIN) { > 1435 if (result) > 1436 *result = INT64_MIN; > 1437 return -ERANGE; > 1438 } Yes I know, but is it guaranteed on all archs in past and future that long long int is 64 bit? > >>> CID 240103: (CONSTANT_EXPRESSION_RESULT) > >>> "val > 9223372036854775807L" is always false regardless of the values of its operands. This occurs as the logical operand of "if". > 1439 if (val > INT64_MAX) { > 1440 if (result) > 1441 *result = INT64_MAX; > 1442 return -ERANGE; > 1443 } same. I'd just ignore these warnings if that's ok with everyone else. ~N

2 years, 8 months

2
2
0 0

Re: New Defects reported by Coverity Scan for Osmocom

by Neels Hofmeyr

On Tue, Sep 14, 2021 at 02:45:51AM +0000, scan-admin(a)coverity.com wrote: > 178 } else { > >>> CID 240100: Memory - illegal accesses (BUFFER_SIZE_WARNING) > >>> Calling "strncpy" with a maximum size argument of 64 bytes on destination array "codec->audio_name" of size 64 bytes might leave the destination string unterminated. > 179 strncpy(codec->audio_name, audio_name, sizeof(codec->audio_name)); strncpy() is another word for pitfall. We should *always* use osmo_strlcpy(), or OSMO_STRLCPY_ARRAY() to save typing 'sizeof'. osmith, could we put such a check in the linter maybe? i.e. forbid use of strncpy() and strcpy(). ~N

2 years, 8 months

2
1
0 0

Connect cell phone to real GSM network through OpenBTS

by Mario Lucas

Dear Osmocom society, I am trying to connect a cell phone (lets call it phone #1) through OpenBTS to real GSM network… To do so i have to introduce a osmocomBB phone which will be connected to my linux machine which runs OpenBTS So kind of it will be a following structure: Phone #1 → OpenBTS → OsmocomBB phone → real GSM netwok. No my goal is to have OpenBTS and OsmocomBB phone to talk to each other… for example authentication parameters which to be exchanged between phone #1 and real network to happen through the chain described above …. Has this case been or something like this done before ? Or are you aware of any cases when OpenBTS and OsmocomBB phone exchange data? Thank you very much -- Mario Lucas

2 years, 8 months

1
0
0 0

Announcement of "OsmoDevCall" on August 27, 2021

by Harald Welte

Dear Osmocom community, It's my pleasure to announce the next OsmoDevCall at August 27, 2021 at 20:00 CEST at https://meeting4.franken.de/b/har-xbc-bsx-wvs This meeting will have the following schedule: 20:00 meet + greet 20:15 presentation on "osmo-remsim in practice" 21:00 USSE: unstructured supplementary social event [*] 22:00 close of call Attendance is free of charge and open to anyone with an interest in Osmocom. 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)

2 years, 8 months

1
0
0 0

rsl_rx_bs_pwr_ctrl()

by Neels Hofmeyr

Hey Vadim, Just now I came across this code, with an early return in case of BCCH. But right below that, BCCH is still mentioned in the comment, and there are more IEs being parsed. So I get the impression the early return may prevent that OSMO_MIN limiting for BCCH, and that may not be intended? /* Osmocom specific extension for BCCH carrier power reduction */ if (dch->chan_nr == RSL_CHAN_BCCH) { int rc = bts_set_c0_pwr_red(trx->bts, new); if (rc != 0) { const uint8_t cause = (rc == -ENOTSUP) ? RSL_ERR_SERV_OPT_UNIMPL : RSL_ERR_IE_CONTENT; return rsl_tx_error_report(trx, cause, &dch->chan_nr, NULL, msg); } return 0; } /* BS power reduction is generally not allowed on BCCH/CCCH carrier. * However, we allow it in the BCCH carrier power reduction operation. * Constrain BS power value by the maximum reduction for this timeslot. */ if (trx->bts->c0 == trx) new = OSMO_MIN(new, lchan->ts->c0_power_red_db); /* 9.3.32 (TLV) BS Power Parameters IE (vendor specific) */ if ((ie = TLVP_GET(&tp, RSL_IE_BS_POWER_PARAM)) != NULL) { https://git.osmocom.org/osmo-bts/tree/src/common/rsl.c?id=6611e7f3059d26794…

2 years, 9 months

2
2
0 0

Announcement of "OsmoDevCall" on August 13, 2021

by Harald Welte

Dear Osmocom community, It's my pleasure to announce the next OsmoDevCall at August 13, 2021 at 20:00 CEST at https://meeting4.franken.de/b/har-xbc-bsx-wvs This meeting will have the following schedule: 20:00 meet + greet 20:15 presentation on "GSM-R and its differences to GSM" 21:00 USSE: unstructured supplementary social event [*] 22:00 close of call Attendance is free of charge and open to anyone with an interest in Osmocom. 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)

2 years, 9 months

1
0
0 0

HR / AMR Lab Testing Using OSMO-NITB

by Sonny Lafuente

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

2 years, 9 months

3
2
0 0

Harald's surplus telecom equipment for free

by Harald Welte

Hi all, as I currently have to clear my basement for water-damage related renovation, I'm going to use the opportunity to get rid of some of the things I'm unlikely going to use ever again https://osmocom.org/projects/miscellaneous-projects/wiki/LaForge_surplus_20… If anyone is interested: I'm not looking for any money in return. I just want to find a new home for it rather than actually disposing of it at some recycling facility. Let me know ASAP if you're interested in any of it, thanks. Happy hacking, Harald -- - Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

2 years, 9 months

1
0
0 0

Can't establish calls between two handsets [nanoBTS 165AU]

by Sebastian Mauer

Hello there, In my lab I have access to an ip.access nanoBTS 165AU which I have setup with OsmoBSC. Sending SMS between my two test handsets (Nokia 105) are working fine, however it seems there is a problem when making calls. From the logs it seems the radio is unable to assign a TCH_F channel. Any idea what could be causing this and how I would debug this further? Cheers, Sebastian <0003> abis_rsl.c:1533 (bts=0) CHAN RQD: reason: call re-establishment (ra=0x49, neci=0x01, chreq_reason=0x02) <000f> lchan_select.c:262 lchan(0-0-0-CCCH_SDCCH4-0)[0xaaaadc4251c0]{UNUSED}: (type=SDCCH) Selected <000f> lchan_fsm.c:636 lchan(0-0-0-CCCH_SDCCH4-0)[0xaaaadc4251c0]{WAIT_TS_READY}: (type=SDCCH) Activation requested: FOR_MS_CHANNEL_REQUEST voice=no MGW-ci=none type=SDCCH tch-mode=SIGNALLING encr-alg=A5/0 ck=none <0007> osmo_bsc_sigtran.c:297 Initializing resources for new SCCP connection to MSC 0: RI=SSN_PC,PC=0.23.1,SSN=BSSAP... <0007> osmo_bsc_sigtran.c:343 Opening new SCCP connection (id=4) to MSC 0: RI=SSN_PC,PC=0.23.1,SSN=BSSAP <0007> osmo_bsc_bssap.c:1147 Rx MSC DT1 BSSMAP COMMON ID <0007> osmo_bsc_bssap.c:1251 Rx MSC DTAP, SAPI: RR/MM/CC CHAN: 0 <0007> gsm_08_08.c:567 Tx MSC DTAP LINK_ID=0x00 <0007> osmo_bsc_sigtran.c:383 Tx MSC: DTAP <0007> osmo_bsc_bssap.c:1251 Rx MSC DTAP, SAPI: RR/MM/CC CHAN: 2 <0007> osmo_bsc_bssap.c:1110 Rx MSC UDT BSSMAP PAGING <0007> osmo_bsc_bssap.c:126 (msc0) Paging: subscr-IMSI-901700000050081-TMSI-0x06e8ff82: (bts0) Paging on LAC 1 <0007> osmo_bsc_bssap.c:1147 Rx MSC DT1 BSSMAP ASSIGNMENT REQ <000f> lchan_select.c:262 lchan(0-0-2-TCH_F-0)[0xaaaadc432ba0]{UNUSED}: (type=TCH_F) Selected <0011> assignment_fsm.c:570 assignment(msc0-conn4_subscr-IMSI-901700000050080-TMSI-0xbf4aa84d_0-0-2-TCH_F-0)[0xaaaadc43e930]{WAIT_LCHAN_ACTIVE}: (bts=0,trx=0,ts=2,ss=0) Starting Assignment: chan_mode=SPEECH_V1, chan_type=FR, aoip=yes MSC-rtp=192.168.148.159:4074 (osmux=no) <000f> lchan_fsm.c:636 lchan(0-0-2-TCH_F-0)[0xaaaadc432ba0]{WAIT_TS_READY}: (type=TCH_F) Activation requested: FOR_ASSIGNMENT voice=yes MGW-ci=new type=TCH_F tch-mode=SPEECH_V1 encr-alg=A5/0 ck=none <000f> lchan_fsm.c:81 lchan(0-0-2-TCH_F-0)[0xaaaadc432ba0]{WAIT_RLL_RTP_ESTABLISH}: (type=TCH_F) lchan-rtp failure in state WAIT_IPACC_CRCX_ACK: Received NACK on IPACC CRCX <000f> lchan_fsm.c:81 lchan(0-0-2-TCH_F-0)[0xaaaadc432ba0]{WAIT_RLL_RTP_ESTABLISH}: (type=TCH_F) lchan allocation failed in state WAIT_RLL_RTP_ESTABLISH: Failed to setup RTP stream: LCHAN_EV_RTP_ERROR in state WAIT_RLL_RTP_ESTABLISH <000f> lchan_fsm.c:116 lchan(0-0-2-TCH_F-0)[0xaaaadc432ba0]{WAIT_RLL_RTP_ESTABLISH}: (type=TCH_F) Signalling Assignment FSM of error (lchan allocation failed in state WAIT_RLL_RTP_ESTABLISH: Failed to setup RTP stream: LCHAN_EV_RTP_ERROR in state WAIT_RLL_RTP_ESTABLISH ) <0011> assignment_fsm.c:821 assignment(msc0-conn4_subscr-IMSI-901700000050080-TMSI-0xbf4aa84d_0-0-2-TCH_F-0)[0xaaaadc43e930]{WAIT_RR_ASS_COMPLETE}: (bts=0,trx=0,ts=2,ss=0) Assignment failed in state WAIT_RR_ASS_COMPLETE, cause RADIO INTERFACE MESSAGE FAILURE: Failed to activate lchan (bts=0,trx=0,ts=2,ss=0) <0007> osmo_bsc_sigtran.c:379 Tx MSC: BSSMAP: ASSIGNMENT FAIL <0011> assignment_fsm.c:148 assignment(msc0-conn4_subscr-IMSI-901700000050080-TMSI-0xbf4aa84d_0-0-2-TCH_F-0)[0xaaaadc43e930]{WAIT_RR_ASS_COMPLETE}: (bts=0,trx=0,ts=2,ss=0) Assignment failed <0007> osmo_bsc_bssap.c:1251 Rx MSC DTAP, SAPI: RR/MM/CC CHAN: 2 <0007> osmo_bsc_bssap.c:1147 Rx MSC DT1 BSSMAP CLEAR COMMAND <0007> osmo_bsc_sigtran.c:379 Tx MSC: BSSMAP: CLEAR COMPLETE <0005> paging.c:84 (bts=0) Going to send paging commands: subscr-IMSI-901700000050081-TMSI-0x06e8ff82 for ch. type 0 (attempt 0) <000f> gsm_04_08_rr.c:1021 lchan(0-0-0-CCCH_SDCCH4-0)[0xaaaadc4251c0]{WAIT_BEFORE_RF_RELEASE}: (type=SDCCH) Got data in non active state, discarding. <0005> paging.c:84 (bts=0) Going to send paging commands: subscr-IMSI-901700000050081-TMSI-0x06e8ff82 for ch. type 0 (attempt 1) <0005> paging.c:84 (bts=0) Going to send paging commands: subscr-IMSI-901700000050081-TMSI-0x06e8ff82 for ch. type 0 (attempt 2) <0003> abis_rsl.c:1533 (bts=0) CHAN RQD: reason: answer to paging (ra=0x9f, neci=0x01, chreq_reason=0x01) <000f> lchan_select.c:262 lchan(0-0-0-CCCH_SDCCH4-1)[0xaaaadc425390]{UNUSED}: (type=SDCCH) Selected <000f> lchan_fsm.c:636 lchan(0-0-0-CCCH_SDCCH4-1)[0xaaaadc425390]{WAIT_TS_READY}: (type=SDCCH) Activation requested: FOR_MS_CHANNEL_REQUEST voice=no MGW-ci=none type=SDCCH tch-mode=SIGNALLING encr-alg=A5/0 ck=none <0005> paging.c:84 (bts=0) Going to send paging commands: subscr-IMSI-901700000050081-TMSI-0x06e8ff82 for ch. type 0 (attempt 3) <0007> osmo_bsc_sigtran.c:297 Initializing resources for new SCCP connection to MSC 0: RI=SSN_PC,PC=0.23.1,SSN=BSSAP... <0007> osmo_bsc_sigtran.c:343 Opening new SCCP connection (id=5) to MSC 0: RI=SSN_PC,PC=0.23.1,SSN=BSSAP <0007> osmo_bsc_bssap.c:1147 Rx MSC DT1 BSSMAP COMMON ID <0007> osmo_bsc_bssap.c:1147 Rx MSC DT1 BSSMAP CLEAR COMMAND <0007> osmo_bsc_sigtran.c:379 Tx MSC: BSSMAP: CLEAR COMPLETE <0003> abis_rsl.c:1533 (bts=0) CHAN RQD: reason: answer to paging (ra=0x88, neci=0x01, chreq_reason=0x01) <000f> lchan_select.c:262 lchan(0-0-0-CCCH_SDCCH4-0)[0xaaaadc4251c0]{UNUSED}: (type=SDCCH) Selected <000f> lchan_fsm.c:636 lchan(0-0-0-CCCH_SDCCH4-0)[0xaaaadc4251c0]{WAIT_TS_READY}: (type=SDCCH) Activation requested: FOR_MS_CHANNEL_REQUEST voice=no MGW-ci=none type=SDCCH tch-mode=SIGNALLING encr-alg=A5/0 ck=none <0007> osmo_bsc_sigtran.c:297 Initializing resources for new SCCP connection to MSC 0: RI=SSN_PC,PC=0.23.1,SSN=BSSAP... <0007> osmo_bsc_sigtran.c:343 Opening new SCCP connection (id=6) to MSC 0: RI=SSN_PC,PC=0.23.1,SSN=BSSAP <0007> osmo_bsc_bssap.c:1147 Rx MSC DT1 BSSMAP COMMON ID <0007> osmo_bsc_bssap.c:1147 Rx MSC DT1 BSSMAP CLEAR COMMAND <0007> osmo_bsc_sigtran.c:379 Tx MSC: BSSMAP: CLEAR COMPLETE

2 years, 9 months

3
4
0 0

MS Power Transmit not changing

by Sonny Lafuente

Hello Neels and Community, Good day! We are doing some testing on our Lab specifically in Voice. During this testing we observed that the MS power transmit is not changing during ongoing call and the value is 5dbm. We also do walk test in order to lower the received power level and to observed if the MS Transmit power will increase. We tried to change some parameters in osmo-bts-trx uplink-power-target but however, the MS Transmit power still the same which is 5dbm. The MS power in the osmo-nitb config is set to 23dbm. Below is the version and configuration we used on our testing in Lab. Version: OpenBSC# show version OpenBSC 1.3.2.2-d2550 (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# OsmoBTS# show version OsmoBTS 1.2.0.48-6392 (OsmoBTS). Copyright (C) 2010, 2011 by Harald Welte, Andreas Eversberg and On-Waves 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. OsmoBTS# Logs: OpenBSC# show lchan BTS 0, TRX 1, Timeslot 0, Lchan 0: Type SDCCH Connection: 1, State: ACTIVE BS Power: 0 dBm, MS Power: 23 dBm Channel Mode / Codec: signalling Subscriber: ID: 1816, Authorized: 0 Extension: 164324 IMSI: 515039102991665 Use count: 1 Bound IP: 0.0.0.0 Port 0 RTP_TYPE2=0 CONN_ID=0 Measurement Report: Flags: DLinval RXL-FULL-ul: -50 dBm, RXL-SUB-ul: -50 dBm RXQ-FULL-ul: 7, RXQ-SUB-ul: 7 BTS 0, TRX 1, Timeslot 6, Lchan 0: Type TCH_F Connection: 1, State: ACTIVE BS Power: 0 dBm, MS Power: 23 dBm Channel Mode / Codec: FR or HR Subscriber: ID: 1782, Authorized: 1 Extension: 05837654321 IMSI: 515032920153135 Use count: 2 Bound IP: X.X.X.X Port 16386 RTP_TYPE2=0 CONN_ID=0 Measurement Report: Flags: MS Timing Offset: 0 L1 MS Power: 5 dBm, Timing Advance: 0 RXL-FULL-dl: -47 dBm, RXL-SUB-dl: -47 dBm RXQ-FULL-dl: 0, RXQ-SUB-dl: 0 RXL-FULL-ul: -47 dBm, RXL-SUB-ul: -47 dBm RXQ-FULL-ul: 0, RXQ-SUB-ul: 0 BTS 0, TRX 1, Timeslot 7, Lchan 0: Type TCH_F Connection: 1, State: ACTIVE BS Power: 0 dBm, MS Power: 23 dBm Channel Mode / Codec: FR or HR Subscriber: ID: 4, Authorized: 1 Extension: 05831234567 IMSI: 515032919099978 Use count: 2 Bound IP: X.X.X.X Port 16384 RTP_TYPE2=0 CONN_ID=0 Measurement Report: Flags: MS Timing Offset: 0 L1 MS Power: 5 dBm, Timing Advance: 0 RXL-FULL-dl: -47 dBm, RXL-SUB-dl: -47 dBm RXQ-FULL-dl: 4, RXQ-SUB-dl: 5 RXL-FULL-ul: -47 dBm, RXL-SUB-ul: -47 dBm RXQ-FULL-ul: 7, RXQ-SUB-ul: 7 OpenBSC# Ongoing Call Logs: OpenBSC# show lchan summary BTS 0, TRX 1, Timeslot 6 TCH/F, Lchan 0, Type TCH_F, State ACTIVE - L1 MS Power: 5 dBm RXL-FULL-dl: -47 dBm RXL-FULL-ul: -47 dBm BTS 0, TRX 1, Timeslot 7 TCH/F, Lchan 0, Type TCH_F, State ACTIVE - L1 MS Power: 5 dBm RXL-FULL-dl: -47 dBm RXL-FULL-ul: -47 dBm OpenBSC# Osmo-BTS current config: e1_input e1_line 0 driver ipa e1_line 0 port 0 no e1_line 0 keepalive phy 0 osmotrx ip local 127.0.0.1 osmotrx ip remote 127.0.0.1 no osmotrx ms-power-loop osmotrx base-port local 5800 osmotrx base-port remote 5700 osmotrx fn-advance 20 osmotrx rts-advance 5 instance 0 osmotrx rx-gain 0 osmotrx tx-attenuation 13 osmotrx maxdly 0 instance 1 osmotrx rx-gain 0 osmotrx tx-attenuation 10 osmotrx maxdly 0 bts 0 band GSM900 ipa unit-id 1000 0 oml remote-ip x.x.x.x rtp jitter-buffer 100 paging queue-size 200 paging lifetime 0 uplink-power-target -75 gsmtap-sapi ccch gsmtap-sapi pdtch min-qual-rach 50 min-qual-norm -5 max-ber10k-rach 1707 trx 0 power-ramp max-initial 0 mdBm power-ramp step-size 2000 mdB power-ramp step-interval 1 ms-power-control dsp phy 0 instance 0 trx 1 power-ramp max-initial 0 mdBm power-ramp step-size 2000 mdB power-ramp step-interval 1 ms-power-control dsp phy 0 instance 1 Osmo-Nitb Current Config: root@ubuntu:/etc/osmocom# cat osmo-nitb.cfg ! log stderr logging filter all 1 logging color 1 logging print category 0 logging timestamp 1 logging level all everything logging level rll notice logging level cc notice logging level mm notice logging level rr notice logging level rsl notice logging level nm info logging level mncc notice logging level pag notice logging level meas notice logging level sccp notice logging level msc notice logging level mgcp notice logging level ho notice logging level db notice logging level ref notice logging level gprs debug logging level ns info logging level bssgp debug logging level llc debug logging level sndcp debug logging level nat notice logging level ctrl notice logging level smpp debug logging level filter debug logging level ranap debug logging level sua debug logging level pcu debug 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 ! 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 gprs mode gprs gprs 11bit_rach_support_for_egprs 0 gprs routing area 1 gprs network-control-order nc0 gprs cell bvci 2 gprs cell timer blocking-timer 3 gprs cell timer blocking-retries 3 gprs cell timer unblocking-retries 3 gprs cell timer reset-timer 3 gprs cell timer reset-retries 3 gprs cell timer suspend-timer 10 gprs cell timer suspend-retries 3 gprs cell timer resume-timer 10 gprs cell timer resume-retries 3 gprs cell timer capability-update-timer 10 gprs cell timer capability-update-retries 3 gprs nsei 101 gprs ns timer tns-block 3 gprs ns timer tns-block-retries 3 gprs ns timer tns-reset 3 gprs ns timer tns-reset-retries 3 gprs ns timer tns-test 30 gprs ns timer tns-alive 3 gprs ns timer tns-alive-retries 10 gprs nsvc 0 nsvci 101 gprs nsvc 0 local udp port 23000 gprs nsvc 0 remote udp port 23000 gprs nsvc 0 remote ip 127.0.0.2 gprs nsvc 1 nsvci 0 gprs nsvc 1 local udp port 0 gprs nsvc 1 remote udp port 0 gprs nsvc 1 remote ip 0.0.0.0 no force-combined-si 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/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 TCH/F 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/F 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 TCH/F 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 Rootubuntu:/etc/osmocom# Regards, Sonny Lafuente | Systems Engineer | Entropy Solution Philippines Mobile: +639985365206 | Office: 028931781 | Email: sonny.lafuente(a)entropysolution.com<mailto:sonny.lafuente@entropysolution.com> Office Address: Unit 2103 Antel Corporate Centre 121 Valero St. Salcedo Village Makati City Philippines 1227 [cid:936BCCE1-8AAB-4E96-8413-E1075D00DBE3] Singapore * Philippines Products: Gridloc*Intelle*Hype*Lighthouse*Telco Services*Software Development This email (including any attachment to it) is confidential and intended only for the use of the individual named above and may contain information that is privileged. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this email is strictly prohibited. If you have received this email in error, please notify us immediately by return email or telephone and destroy the original message (including any attachment to it). Thank you.

2 years, 9 months

2
1
0 0

(no subject)

by Henry Caga

Hi, I would like to know if it is possible to disconnect a connected device to my osmo-bsc system? After running my osmo-bsc setup and my test phone is connected to my usrp via 2g, is it possible to send a vty command or what are the steps to make the connected device to detach to my bts? Thank you so much. Hnjojo

2 years, 9 months

3
4
0 0

Announcement of "OsmoDevCall" on July 23, 2021

by Harald Welte

Dear Osmocom community, It's my pleasure to announce the next OsmoDevCall at July 23, 2021 at 20:00 CEST at https://meeting4.franken.de/b/har-xbc-bsx-wvs This meeting will have the following schedule: 20:00 meet + greet 20:15 presentation on "high-level overview on IMS, VoLTE, VoWiFi" 21:00 USSE: unstructured supplementary social event [*] 22:00 close of call Attendance is free of charge and open to anyone with an interest in Osmocom. 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)

2 years, 10 months

1
0
0 0

How to program EFAD(Administrative Data)

by EmPa Kro

Hello develop, I want to program Administrative Data update the MS operation mode. Are there any option command can use on "pySim-prog.py" ? I saw "update_ad" in the pySIM/cards.py it mean Update Administrative Data. Please help me......, thank you so much. Best Regards, Kenny

2 years, 10 months

1
1
0 0

Nanobts will not correctly attach to osmo-bsc.

by Andreas Eversberg

Hi, after long time (may years), I do a "compileathlon"/"configathlon" with a osmo-bsc/osmo-stp/osmo-msc/osmo-sip-connector setup. If I interpret this the shown osmo-bsc output correctly, it attaches successfully through the osmo-stp with the osmo-msc. Then I start an ipaccess nanobts. It connects via OML, comes to a point where provisioning stops or times out. I use a fresh debian installation with am64 and todays master branches from git.osmocom.org repository. A pcap file of the OML connection is attached to this message. (The order of packets in the trace is messed up, due to my switch's port mirroring.) Also attached is the osmo-bsc.cfg. Any idea? Thank you, Andreas <0004> fsm.c:461 NM_BTS_SM_OP[0x558f2b1d17e0]{DISABLED_NOTINSTALLED}: Allocated <0004> fsm.c:461 NM_BTS_OP[0x558f2b1d5120]{DISABLED_NOTINSTALLED}: Allocated <0004> fsm.c:461 NM_GPRS_CELL_OP[0x558f2b1d5250]{DISABLED_NOTINSTALLED}: Allocated <0004> fsm.c:461 NM_RCARRIER_OP[0x558f2b1da770]{DISABLED_NOTINSTALLED}: Allocated <0004> fsm.c:461 NM_BB_TRANSC_OP[0x558f2b1da940]{DISABLED_NOTINSTALLED}: Allocated <0004> fsm.c:461 NM_CHAN_OP[0x558f2b1dac40]{DISABLED_NOTINSTALLED}: Allocated <0004> fsm.c:461 NM_CHAN_OP[0x558f2b1db340]{DISABLED_NOTINSTALLED}: Allocated <0004> fsm.c:461 NM_CHAN_OP[0x558f2b1dbb40]{DISABLED_NOTINSTALLED}: Allocated <0004> fsm.c:461 NM_CHAN_OP[0x558f2b1dc340]{DISABLED_NOTINSTALLED}: Allocated <0004> fsm.c:461 NM_CHAN_OP[0x558f2b1dcb40]{DISABLED_NOTINSTALLED}: Allocated <0004> fsm.c:461 NM_CHAN_OP[0x558f2b1dd3d0]{DISABLED_NOTINSTALLED}: Allocated <0004> fsm.c:461 NM_CHAN_OP[0x558f2b1ddc60]{DISABLED_NOTINSTALLED}: Allocated <0004> fsm.c:461 NM_CHAN_OP[0x558f2b1de4f0]{DISABLED_NOTINSTALLED}: Allocated <0004> fsm.c:461 NM_GPRS_NSE_OP[0x558f2b1debd0]{DISABLED_NOTINSTALLED}: Allocated <0004> fsm.c:461 NM_GPRS_NSVC_OP[0x558f2b1ded90]{DISABLED_NOTINSTALLED}: Allocated <0004> fsm.c:461 NM_GPRS_NSVC_OP[0x558f2b1defc0]{DISABLED_NOTINSTALLED}: Allocated <0015> telnet_interface.c:104 Available via telnet 127.0.0.1 4242 <0017> input/ipaccess.c:1035 enabling ipaccess BSC mode on 0.0.0.0 with OML 3002 and RSL 3003 TCP ports <001c> control_if.c:922 CTRL at 127.0.0.1 4249 <0025> mgcp_client.c:782 MGCP client: using endpoint domain '@mgw' <0007> osmo_bsc_sigtran.c:548 Initializing SCCP connection for A/m3ua on cs7 instance 0 <0022> sccp_user.c:548 A-0-m3ua: Using SS7 instance 0, pc:1.23.3 <0022> sccp_user.c:555 A-0-m3ua: Creating AS instance <0022> sccp_user.c:566 A-0-m3ua: Using AS instance as-clnt-A-0-m3ua <0022> sccp_user.c:571 A-0-m3ua: Creating default route <0022> sccp_user.c:605 A-0-m3ua: ASP my-asp for m3ua is not associated with any AS, using it <0022> sccp_user.c:638 A-0-m3ua: Using ASP instance my-asp <0021> osmo_ss7.c:456 0: Creating SCCP instance <0007> osmo_bsc_sigtran.c:600 A-0-m3ua msc-0: local (BSC) SCCP address: RI=SSN_PC,PC=1.23.3,SSN=BSSAP <0007> osmo_bsc_sigtran.c:602 A-0-m3ua msc-0: remote (MSC) SCCP address: RI=SSN_PC,PC=0.23.1,SSN=BSSAP <0007> osmo_bsc_sigtran.c:607 A-0-m3ua msc-0: binding SCCP user <0021> m3ua.c:507 XUA_AS(as-clnt-A-0-m3ua)[0x558f2b1e2c10]{AS_DOWN}: Event AS-TRANSFER.req not permitted <0024> m3ua.c:622 0: asp-my-asp: Received NOTIFY Type State Change:AS Inactive () <0021> xua_default_lm_fsm.c:361 xua_default_lm(my-asp)[0x558f2b1e2f40]{ACTIVE}: Ignoring primitive M-ASP_ACTIVE.confirm <0024> m3ua.c:622 0: asp-my-asp: Received NOTIFY Type State Change:AS Active () <0007> osmo_bsc_bssap.c:81 RESET ACK from MSC: RI=SSN_PC,PC=0.23.1,SSN=BSSAP <0014> bssmap_reset.c:83 bssmap_reset(msc-0)[0x558f2b1e3d50]{CONN}: link up <0007> a_reset.c:44 (msc0) BSSMAP assocation is up <0017> input/ipa.c:284 0.0.0.0:3002 accept()ed new link from 10.0.0.96:48280 <0004> abis_nm.c:258 OC=SITE-MANAGER(00) INST=(ff,ff,ff): STATE CHG: OP_STATE=Disabled AVAIL=Not installed(07) <0004> bts_ipaccess_nanobts.c:156 NM_BTS_SM_OP(bts_sm)[0x558f2b1d17e0]{DISABLED_NOTINSTALLED}: Received Event STATE_CHG_REP <0004> abis_nm.c:258 OC=BTS(01) INST=(00,ff,ff): STATE CHG: OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked <0004> bts_ipaccess_nanobts.c:160 NM_BTS_OP(bts0)[0x558f2b1d5120]{DISABLED_NOTINSTALLED}: Received Event STATE_CHG_REP <0004> abis_nm.c:258 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff): STATE CHG: OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked <0004> bts_ipaccess_nanobts.c:164 NM_BB_TRANSC_OP(bts0-trx0)[0x558f2b1da940]{DISABLED_NOTINSTALLED}: Received Event STATE_CHG_REP <0004> abis_nm.c:258 OC=CHANNEL(03) INST=(00,00,00): STATE CHG: OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked <0004> bts_ipaccess_nanobts.c:169 NM_CHAN_OP(bts0-trx0-ts0)[0x558f2b1dac40]{DISABLED_NOTINSTALLED}: Received Event STATE_CHG_REP <0004> abis_nm.c:258 OC=CHANNEL(03) INST=(00,00,01): STATE CHG: OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked <0004> bts_ipaccess_nanobts.c:169 NM_CHAN_OP(bts0-trx0-ts1)[0x558f2b1db340]{DISABLED_NOTINSTALLED}: Received Event STATE_CHG_REP <0004> abis_nm.c:258 OC=CHANNEL(03) INST=(00,00,02): STATE CHG: OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked <0004> bts_ipaccess_nanobts.c:169 NM_CHAN_OP(bts0-trx0-ts2)[0x558f2b1dbb40]{DISABLED_NOTINSTALLED}: Received Event STATE_CHG_REP <0004> abis_nm.c:258 OC=CHANNEL(03) INST=(00,00,03): STATE CHG: OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked <0004> bts_ipaccess_nanobts.c:169 NM_CHAN_OP(bts0-trx0-ts3)[0x558f2b1dc340]{DISABLED_NOTINSTALLED}: Received Event STATE_CHG_REP <0004> abis_nm.c:258 OC=CHANNEL(03) INST=(00,00,04): STATE CHG: OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked <0004> bts_ipaccess_nanobts.c:169 NM_CHAN_OP(bts0-trx0-ts4)[0x558f2b1dcb40]{DISABLED_NOTINSTALLED}: Received Event STATE_CHG_REP <0004> abis_nm.c:258 OC=CHANNEL(03) INST=(00,00,05): STATE CHG: OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked <0004> bts_ipaccess_nanobts.c:169 NM_CHAN_OP(bts0-trx0-ts5)[0x558f2b1dd3d0]{DISABLED_NOTINSTALLED}: Received Event STATE_CHG_REP <0004> abis_nm.c:258 OC=CHANNEL(03) INST=(00,00,06): STATE CHG: OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked <0004> bts_ipaccess_nanobts.c:169 NM_CHAN_OP(bts0-trx0-ts6)[0x558f2b1ddc60]{DISABLED_NOTINSTALLED}: Received Event STATE_CHG_REP <0004> abis_nm.c:258 OC=CHANNEL(03) INST=(00,00,07): STATE CHG: OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked <0004> bts_ipaccess_nanobts.c:169 NM_CHAN_OP(bts0-trx0-ts7)[0x558f2b1de4f0]{DISABLED_NOTINSTALLED}: Received Event STATE_CHG_REP <0004> abis_nm.c:258 OC=RADIO-CARRIER(02) INST=(00,00,ff): STATE CHG: OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked <0004> bts_ipaccess_nanobts.c:173 NM_RCARRIER_OP(bts0-trx0)[0x558f2b1da770]{DISABLED_NOTINSTALLED}: Received Event STATE_CHG_REP <0004> abis_nm.c:258 OC=GPRS-NSE(f0) INST=(00,ff,ff): STATE CHG: OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked <0004> bts_ipaccess_nanobts.c:177 NM_GPRS_NSE_OP(nse0)[0x558f2b1debd0]{DISABLED_NOTINSTALLED}: Received Event STATE_CHG_REP <0004> abis_nm.c:258 OC=GPRS-CELL(f1) INST=(00,00,ff): STATE CHG: OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked <0004> bts_ipaccess_nanobts.c:181 NM_GPRS_CELL_OP(gprs-cell0)[0x558f2b1d5250]{DISABLED_NOTINSTALLED}: Received Event STATE_CHG_REP <0004> abis_nm.c:258 OC=GPRS-NSVC(f2) INST=(00,00,ff): STATE CHG: OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked <0004> bts_ipaccess_nanobts.c:188 NM_GPRS_NSVC_OP(nsvc0)[0x558f2b1ded90]{DISABLED_NOTINSTALLED}: Received Event STATE_CHG_REP <0004> abis_nm.c:258 OC=GPRS-NSVC(f2) INST=(00,01,ff): STATE CHG: OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked <0004> abis_nm.c:724 OC=SITE-MANAGER(00) INST=(ff,ff,ff): Software Activate Request, ACKing and Activating <0004> abis_nm.c:743 OC=SITE-MANAGER(00) INST=(ff,ff,ff): Found SW config: 42 12 00 08 31 32 30 61 30 30 32 00 13 00 09 76 32 36 37 62 35 64 30 00 <0004> abis_nm.c:755 OC=SITE-MANAGER(00) INST=(ff,ff,ff): Selected sw description 0 of 1 <0004> abis_nm.c:258 OC=SITE-MANAGER(00) INST=(ff,ff,ff): STATE CHG: OP_STATE=Enabled AVAIL=OK(ff) <0004> bts_ipaccess_nanobts.c:156 NM_BTS_SM_OP(bts_sm)[0x558f2b1d17e0]{DISABLED_NOTINSTALLED}: Received Event STATE_CHG_REP <0004> abis_nm.c:2186 OC=SITE-MANAGER(00) INST=(ff,ff,ff): Sending OPSTART <0004> nm_bts_sm_fsm.c:83 NM_BTS_SM_OP(bts_sm)[0x558f2b1d17e0]{DISABLED_NOTINSTALLED}: state_chg to ENABLED <0004> abis_nm.c:478 OC=SITE-MANAGER(00) INST=(ff,ff,ff): Software Activated Report <0004> bts_ipaccess_nanobts.c:211 NM_BTS_SM_OP(bts_sm)[0x558f2b1d17e0]{ENABLED}: Received Event SW_ACT_REP <0004> bts_ipaccess_nanobts.c:211 NM_BTS_SM_OP(bts_sm)[0x558f2b1d17e0]{ENABLED}: Event SW_ACT_REP not permitted <0004> abis_nm.c:724 OC=BTS(01) INST=(00,ff,ff): Software Activate Request, ACKing and Activating <0004> abis_nm.c:743 OC=BTS(01) INST=(00,ff,ff): Found SW config: 42 12 00 08 31 32 30 61 30 30 32 00 13 00 09 76 32 36 37 62 35 64 30 00 <0004> abis_nm.c:755 OC=BTS(01) INST=(00,ff,ff): Selected sw description 0 of 1 <0004> abis_nm.c:724 OC=GPRS-NSE(f0) INST=(00,ff,ff): Software Activate Request, ACKing and Activating <0004> abis_nm.c:743 OC=GPRS-NSE(f0) INST=(00,ff,ff): Found SW config: 42 12 00 08 31 32 30 61 30 30 32 00 13 00 09 76 32 36 37 62 35 64 30 00 <0004> abis_nm.c:755 OC=GPRS-NSE(f0) INST=(00,ff,ff): Selected sw description 0 of 1 <0004> abis_nm.c:839 OC=SITE-MANAGER(00) INST=(ff,ff,ff): Opstart ACK <0004> bts_ipaccess_nanobts.c:271 NM_BTS_SM_OP(bts_sm)[0x558f2b1d17e0]{ENABLED}: Received Event OPSTART_ACK <0004> abis_nm.c:258 OC=BTS(01) INST=(00,ff,ff): STATE CHG: OP_STATE=Disabled AVAIL=Dependency(05) <0004> bts_ipaccess_nanobts.c:160 NM_BTS_OP(bts0)[0x558f2b1d5120]{DISABLED_NOTINSTALLED}: Received Event STATE_CHG_REP <0004> nm_bts_fsm.c:77 NM_BTS_OP(bts0)[0x558f2b1d5120]{DISABLED_NOTINSTALLED}: state_chg to DISABLED_DEPENDENCY <0004> nm_bts_fsm.c:153 NM_BTS_OP(bts0)[0x558f2b1d5120]{DISABLED_DEPENDENCY}: state_chg to DISABLED_OFFLINE <0004> abis_nm.c:1835 OC=BTS(01) INST=(00,ff,ff): Tx Get Attributes (Request) <0004> abis_nm.c:478 OC=BTS(01) INST=(00,ff,ff): Software Activated Report <0004> bts_ipaccess_nanobts.c:214 NM_BTS_OP(bts0)[0x558f2b1d5120]{DISABLED_OFFLINE}: Received Event SW_ACT_REP <0004> bts_ipaccess_nanobts.c:214 NM_BTS_OP(bts0)[0x558f2b1d5120]{DISABLED_OFFLINE}: Event SW_ACT_REP not permitted <0004> abis_nm.c:724 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff): Software Activate Request, ACKing and Activating <0004> abis_nm.c:743 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff): Found SW config: 42 12 00 08 31 32 30 61 30 30 31 00 13 00 09 76 32 36 37 62 35 64 30 00 42 12 00 08 31 32 30 61 30 30 32 00 13 00 09 76 32 36 37 62 35 64 30 00 <0004> abis_nm.c:755 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff): Selected sw description 0 of 2 <0004> abis_nm.c:724 OC=RADIO-CARRIER(02) INST=(00,00,ff): Software Activate Request, ACKing and Activating <0004> abis_nm.c:743 OC=RADIO-CARRIER(02) INST=(00,00,ff): Found SW config: 42 12 00 08 31 32 30 61 30 30 31 00 13 00 09 76 32 36 37 62 35 64 30 00 42 12 00 08 31 32 30 61 30 30 32 00 13 00 09 76 32 36 37 62 35 64 30 00 <0004> abis_nm.c:755 OC=RADIO-CARRIER(02) INST=(00,00,ff): Selected sw description 0 of 2 <0004> abis_nm.c:258 OC=GPRS-NSE(f0) INST=(00,ff,ff): STATE CHG: OP_STATE=Disabled AVAIL=Dependency(05) <0004> bts_ipaccess_nanobts.c:177 NM_GPRS_NSE_OP(nse0)[0x558f2b1debd0]{DISABLED_NOTINSTALLED}: Received Event STATE_CHG_REP <0004> nm_gprs_nse_fsm.c:76 NM_GPRS_NSE_OP(nse0)[0x558f2b1debd0]{DISABLED_NOTINSTALLED}: state_chg to DISABLED_DEPENDENCY <0004> nm_gprs_nse_fsm.c:131 NM_GPRS_NSE_OP(nse0)[0x558f2b1debd0]{DISABLED_DEPENDENCY}: state_chg to DISABLED_OFFLINE <0004> abis_nm.c:478 OC=GPRS-NSE(f0) INST=(00,ff,ff): Software Activated Report <0004> bts_ipaccess_nanobts.c:232 NM_GPRS_NSE_OP(nse0)[0x558f2b1debd0]{DISABLED_OFFLINE}: Received Event SW_ACT_REP <0004> bts_ipaccess_nanobts.c:232 NM_GPRS_NSE_OP(nse0)[0x558f2b1debd0]{DISABLED_OFFLINE}: Event SW_ACT_REP not permitted <0004> abis_nm.c:724 OC=GPRS-CELL(f1) INST=(00,00,ff): Software Activate Request, ACKing and Activating <0004> abis_nm.c:743 OC=GPRS-CELL(f1) INST=(00,00,ff): Found SW config: 42 12 00 08 31 32 30 61 30 30 32 00 13 00 09 76 32 36 37 62 35 64 30 00 <0004> abis_nm.c:755 OC=GPRS-CELL(f1) INST=(00,00,ff): Selected sw description 0 of 1 <0004> abis_nm.c:724 OC=GPRS-NSVC(f2) INST=(00,00,ff): Software Activate Request, ACKing and Activating <0004> abis_nm.c:743 OC=GPRS-NSVC(f2) INST=(00,00,ff): Found SW config: 42 12 00 08 31 32 30 61 30 30 32 00 13 00 09 76 32 36 37 62 35 64 30 00 <0004> abis_nm.c:755 OC=GPRS-NSVC(f2) INST=(00,00,ff): Selected sw description 0 of 1 <0004> abis_nm.c:724 OC=GPRS-NSVC(f2) INST=(00,01,ff): Software Activate Request, ACKing and Activating <0004> abis_nm.c:743 OC=GPRS-NSVC(f2) INST=(00,01,ff): Found SW config: 42 12 00 08 31 32 30 61 30 30 32 00 13 00 09 76 32 36 37 62 35 64 30 00 <0004> abis_nm.c:755 OC=GPRS-NSVC(f2) INST=(00,01,ff): Selected sw description 0 of 1 <0004> abis_nm.c:698 OC=BTS(01) INST=(00,ff,ff): Get Attributes Response <0004> abis_nm.c:592 OC=BTS(01) INST=(00,ff,ff): Get Attributes Response: reported unexpectedly long (13 bytes) feature vector - most likely it was compiled against newer BSC headers. Consider upgrading your BSC to later version. <0004> abis_nm.c:610 OC=BTS(01) INST=(00,ff,ff): Get Attributes Response: reported feature 'MULTI_TSC' is not supported, while we thought it is. <0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes Response: unknown feature 0x17. Consider upgrading osmo-bsc. <0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes Response: unknown feature 0x1a. Consider upgrading osmo-bsc. <0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes Response: unknown feature 0x1c. Consider upgrading osmo-bsc. <0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes Response: unknown feature 0x1d. Consider upgrading osmo-bsc. <0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes Response: unknown feature 0x1e. Consider upgrading osmo-bsc. <0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes Response: unknown feature 0x21. Consider upgrading osmo-bsc. <0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes Response: unknown feature 0x22. Consider upgrading osmo-bsc. <0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes Response: unknown feature 0x24. Consider upgrading osmo-bsc. <0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes Response: unknown feature 0x27. Consider upgrading osmo-bsc. <0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes Response: unknown feature 0x29. Consider upgrading osmo-bsc. <0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes Response: unknown feature 0x2a. Consider upgrading osmo-bsc. <0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes Response: unknown feature 0x2b. Consider upgrading osmo-bsc. <0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes Response: unknown feature 0x31. Consider upgrading osmo-bsc. <0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes Response: unknown feature 0x32. Consider upgrading osmo-bsc. <0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes Response: unknown feature 0x37. Consider upgrading osmo-bsc. <0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes Response: unknown feature 0x39. Consider upgrading osmo-bsc. <0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes Response: unknown feature 0x3a. Consider upgrading osmo-bsc. <0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes Response: unknown feature 0x3e. Consider upgrading osmo-bsc. <0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes Response: unknown feature 0x3f. Consider upgrading osmo-bsc. <0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes Response: unknown feature 0x41. Consider upgrading osmo-bsc. <0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes Response: unknown feature 0x42. Consider upgrading osmo-bsc. <0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes Response: unknown feature 0x46. Consider upgrading osmo-bsc. <0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes Response: unknown feature 0x47. Consider upgrading osmo-bsc. <0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes Response: unknown feature 0x49. Consider upgrading osmo-bsc. <0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes Response: unknown feature 0x4a. Consider upgrading osmo-bsc. <0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes Response: unknown feature 0x4d. Consider upgrading osmo-bsc. <0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes Response: unknown feature 0x4f. Consider upgrading osmo-bsc. <0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes Response: unknown feature 0x51. Consider upgrading osmo-bsc. <0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes Response: unknown feature 0x52. Consider upgrading osmo-bsc. <0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes Response: unknown feature 0x53. Consider upgrading osmo-bsc. <0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes Response: unknown feature 0x56. Consider upgrading osmo-bsc. <0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes Response: unknown feature 0x57. Consider upgrading osmo-bsc. <0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes Response: unknown feature 0x59. Consider upgrading osmo-bsc. <0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes Response: unknown feature 0x5a. Consider upgrading osmo-bsc. <0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes Response: unknown feature 0x5b. Consider upgrading osmo-bsc. <0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes Response: unknown feature 0x5e. Consider upgrading osmo-bsc. <0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes Response: unknown feature 0x5f. Consider upgrading osmo-bsc. <0004> abis_nm.c:633 OC=BTS(01) INST=(00,ff,ff): ARI reported sw[0/2]: 120a004 is v267b5d0 <0004> abis_nm.c:633 OC=BTS(01) INST=(00,ff,ff): ARI reported sw[1/2]: 120a002 is v267b5d0 <0004> bts_ipaccess_nanobts.c:361 NM_BTS_OP(bts0)[0x558f2b1d5120]{DISABLED_OFFLINE}: Received Event GET_ATTR_REP <0004> nm_bts_fsm.c:139 NM_GPRS_NSVC_OP(nsvc0)[0x558f2b1ded90]{DISABLED_NOTINSTALLED}: Received Event FEATURE_NEGOTIATED <0004> abis_nm.c:1847 OC=BTS(01) INST=(00,ff,ff): Set BTS Attr <0004> abis_nm.c:258 OC=GPRS-CELL(f1) INST=(00,00,ff): STATE CHG: OP_STATE=Disabled AVAIL=Dependency(05) <0004> bts_ipaccess_nanobts.c:181 NM_GPRS_CELL_OP(gprs-cell0)[0x558f2b1d5250]{DISABLED_NOTINSTALLED}: Received Event STATE_CHG_REP <0004> nm_gprs_cell_fsm.c:75 NM_GPRS_CELL_OP(gprs-cell0)[0x558f2b1d5250]{DISABLED_NOTINSTALLED}: state_chg to DISABLED_DEPENDENCY <0004> nm_gprs_cell_fsm.c:130 NM_GPRS_CELL_OP(gprs-cell0)[0x558f2b1d5250]{DISABLED_DEPENDENCY}: state_chg to DISABLED_OFFLINE <0004> abis_nm.c:478 OC=GPRS-CELL(f1) INST=(00,00,ff): Software Activated Report <0004> bts_ipaccess_nanobts.c:235 NM_GPRS_CELL_OP(gprs-cell0)[0x558f2b1d5250]{DISABLED_OFFLINE}: Received Event SW_ACT_REP <0004> bts_ipaccess_nanobts.c:235 NM_GPRS_CELL_OP(gprs-cell0)[0x558f2b1d5250]{DISABLED_OFFLINE}: Event SW_ACT_REP not permitted <0004> abis_nm.c:258 OC=GPRS-NSVC(f2) INST=(00,00,ff): STATE CHG: OP_STATE=Disabled AVAIL=Off line(03) <0004> bts_ipaccess_nanobts.c:188 NM_GPRS_NSVC_OP(nsvc0)[0x558f2b1ded90]{DISABLED_NOTINSTALLED}: Received Event STATE_CHG_REP <0004> nm_gprs_nsvc_fsm.c:83 NM_GPRS_NSVC_OP(nsvc0)[0x558f2b1ded90]{DISABLED_NOTINSTALLED}: state_chg to DISABLED_OFFLINE <0004> abis_nm.c:258 OC=GPRS-NSVC(f2) INST=(00,01,ff): STATE CHG: OP_STATE=Disabled AVAIL=Off line(03) <0004> abis_nm.c:478 OC=GPRS-NSVC(f2) INST=(00,00,ff): Software Activated Report <0004> bts_ipaccess_nanobts.c:240 NM_GPRS_NSVC_OP(nsvc0)[0x558f2b1ded90]{DISABLED_OFFLINE}: Received Event SW_ACT_REP <0004> bts_ipaccess_nanobts.c:240 NM_GPRS_NSVC_OP(nsvc0)[0x558f2b1ded90]{DISABLED_OFFLINE}: Event SW_ACT_REP not permitted <0004> abis_nm.c:478 OC=GPRS-NSVC(f2) INST=(00,01,ff): Software Activated Report <0004> bts_ipaccess_nanobts.c:240 NM_GPRS_NSVC_OP(nsvc1)[0x558f2b1defc0]{DISABLED_NOTINSTALLED}: Received Event SW_ACT_REP <0004> abis_nm.c:2852 OC=GPRS-NSE(f0) INST=(00,ff,ff): Rx IPACCESS(0xf6): 9d 00 02 00 00 a0 00 07 03 03 03 03 1e 03 0a a1 00 0b 03 03 03 03 03 0a 03 0a 03 0a 03 <0004> abis_nm.c:2909 OC=GPRS-NSE(f0) INST=(00,ff,ff): SET ATTR ACK <0004> bts_ipaccess_nanobts.c:431 NM_GPRS_NSE_OP(nse0)[0x558f2b1debd0]{DISABLED_OFFLINE}: Received Event SET_ATTR_ACK <0004> abis_nm.c:871 OC=BTS(01) INST=(00,ff,ff): Set BTS Attributes ACK <0004> bts_ipaccess_nanobts.c:383 NM_BTS_OP(bts0)[0x558f2b1d5120]{DISABLED_OFFLINE}: Received Event SET_ATTR_ACK <0004> abis_nm.c:780 OC=GPRS-NSE(f0) INST=(00,ff,ff): Rx Change Administrative State ACK Unlocked <0004> bts_ipaccess_nanobts.c:177 NM_GPRS_NSE_OP(nse0)[0x558f2b1debd0]{DISABLED_OFFLINE}: Received Event STATE_CHG_REP <0004> abis_nm.c:2186 OC=GPRS-NSE(f0) INST=(00,ff,ff): Sending OPSTART <0004> abis_nm.c:258 OC=GPRS-NSE(f0) INST=(00,ff,ff): STATE CHG: OP_STATE=Disabled AVAIL=Dependency(05) ADM=Unlocked (No State change detected) <0004> abis_nm.c:780 OC=BTS(01) INST=(00,ff,ff): Rx Change Administrative State ACK Unlocked <0004> bts_ipaccess_nanobts.c:160 NM_BTS_OP(bts0)[0x558f2b1d5120]{DISABLED_OFFLINE}: Received Event STATE_CHG_REP <0004> abis_nm.c:2186 OC=BTS(01) INST=(00,ff,ff): Sending OPSTART <0004> abis_nm.c:258 OC=BTS(01) INST=(00,ff,ff): STATE CHG: OP_STATE=Disabled AVAIL=Dependency(05) ADM=Unlocked (No State change detected) <0004> abis_nm.c:839 OC=GPRS-NSE(f0) INST=(00,ff,ff): Opstart ACK <0004> bts_ipaccess_nanobts.c:290 NM_GPRS_NSE_OP(nse0)[0x558f2b1debd0]{DISABLED_OFFLINE}: Received Event OPSTART_ACK <0004> abis_nm.c:839 OC=BTS(01) INST=(00,ff,ff): Opstart ACK <0004> bts_ipaccess_nanobts.c:274 NM_BTS_OP(bts0)[0x558f2b1d5120]{DISABLED_OFFLINE}: Received Event OPSTART_ACK After a while the OML connection is lost. <0004> abis_nm.c:258 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff): STATE CHG: OP_STATE=Disabled AVAIL=Dependency(05) <0004> bts_ipaccess_nanobts.c:164 NM_BB_TRANSC_OP(bts0-trx0)[0x56372d474940]{DISABLED_NOTINSTALLED}: Received Event STATE_CHG_REP <0004> nm_bb_transc_fsm.c:75 NM_BB_TRANSC_OP(bts0-trx0)[0x56372d474940]{DISABLED_NOTINSTALLED}: state_chg to DISABLED_DEPENDENCY <0004> nm_bb_transc_fsm.c:132 NM_BB_TRANSC_OP(bts0-trx0)[0x56372d474940]{DISABLED_DEPENDENCY}: state_chg to DISABLED_OFFLINE <0004> abis_nm.c:1835 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff): Tx Get Attributes (Request) <0004> abis_nm.c:698 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff): Get Attributes Response <0004> abis_nm.c:633 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff): ARI reported sw[0/3]: 120a004 is v267b5d0 <0004> abis_nm.c:633 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff): ARI reported sw[1/3]: 120a002 is v267b5d0 <0004> abis_nm.c:633 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff): ARI reported sw[2/3]: 120a001 is v267b5d0 <0004> abis_nm.c:551 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff): Get Attributes Response Info: 2 bytes total with 1 unreported attributes <0004> abis_nm.c:556 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff): Attribute Manufacturer Dependent State is unreported <0004> bts_ipaccess_nanobts.c:366 NM_BB_TRANSC_OP(bts0-trx0)[0x56372d474940]{DISABLED_OFFLINE}: Received Event GET_ATTR_REP <0004> abis_nm.c:945 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff): CHANGE ADMINISTRATIVE STATE NACK CAUSE=Message cannot be performed <0004> osmo_bsc_main.c:229 Got CHANGE ADMINISTRATIVE STATE NACK going to drop the OML links. <0017> bts_ipaccess_nanobts.c:620 (bts=0) Deferring Drop of OML link. <0017> bts_ipaccess_nanobts.c:555 (bts=0) Dropping OML link: Deferred link drop <0019> osmo_bsc_main.c:405 (bts=0,trx=0) Lost E1 OML link <0019> osmo_bsc_main.c:405 (bts=0,trx=0) Lost E1 OSMO link <0004> bts_ipaccess_nanobts.c:568 NM_BB_TRANSC_OP(bts0-trx0)[0x56372d474940]{DISABLED_OFFLINE}: Received Event OML_DOWN <0004> nm_bb_transc_fsm.c:291 NM_BB_TRANSC_OP(bts0-trx0)[0x56372d474940]{DISABLED_OFFLINE}: state_chg to DISABLED_NOTINSTALLED <0004> bts_ipaccess_nanobts.c:569 NM_RCARRIER_OP(bts0-trx0)[0x56372d474770]{DISABLED_NOTINSTALLED}: Received Event OML_DOWN <0004> bts_ipaccess_nanobts.c:572 NM_CHAN_OP(bts0-trx0-ts0)[0x56372d474c40]{DISABLED_NOTINSTALLED}: Received Event OML_DOWN <0004> bts_ipaccess_nanobts.c:572 NM_CHAN_OP(bts0-trx0-ts1)[0x56372d475340]{DISABLED_NOTINSTALLED}: Received Event OML_DOWN <0004> bts_ipaccess_nanobts.c:572 NM_CHAN_OP(bts0-trx0-ts2)[0x56372d475b40]{DISABLED_NOTINSTALLED}: Received Event OML_DOWN <0004> bts_ipaccess_nanobts.c:572 NM_CHAN_OP(bts0-trx0-ts3)[0x56372d476340]{DISABLED_NOTINSTALLED}: Received Event OML_DOWN <0004> bts_ipaccess_nanobts.c:572 NM_CHAN_OP(bts0-trx0-ts4)[0x56372d476b40]{DISABLED_NOTINSTALLED}: Received Event OML_DOWN <0004> bts_ipaccess_nanobts.c:572 NM_CHAN_OP(bts0-trx0-ts5)[0x56372d4773d0]{DISABLED_NOTINSTALLED}: Received Event OML_DOWN <0004> bts_ipaccess_nanobts.c:572 NM_CHAN_OP(bts0-trx0-ts6)[0x56372d477c60]{DISABLED_NOTINSTALLED}: Received Event OML_DOWN <0004> bts_ipaccess_nanobts.c:572 NM_CHAN_OP(bts0-trx0-ts7)[0x56372d4784f0]{DISABLED_NOTINSTALLED}: Received Event OML_DOWN <0004> bts_ipaccess_nanobts.c:576 NM_BTS_SM_OP(bts_sm)[0x56372d46b7e0]{ENABLED}: Received Event OML_DOWN <0004> nm_bts_sm_fsm.c:216 NM_BTS_SM_OP(bts_sm)[0x56372d46b7e0]{ENABLED}: state_chg to DISABLED_NOTINSTALLED <0004> bts_ipaccess_nanobts.c:577 NM_GPRS_NSE_OP(nse0)[0x56372d478bd0]{DISABLED_OFFLINE}: Received Event OML_DOWN <0004> nm_gprs_nse_fsm.c:298 NM_GPRS_NSE_OP(nse0)[0x56372d478bd0]{DISABLED_OFFLINE}: state_chg to DISABLED_NOTINSTALLED <0004> bts_ipaccess_nanobts.c:579 NM_GPRS_NSVC_OP(nsvc0)[0x56372d478d90]{DISABLED_OFFLINE}: Received Event OML_DOWN <0004> nm_gprs_nsvc_fsm.c:307 NM_GPRS_NSVC_OP(nsvc0)[0x56372d478d90]{DISABLED_OFFLINE}: state_chg to DISABLED_NOTINSTALLED <0004> bts_ipaccess_nanobts.c:579 NM_GPRS_NSVC_OP(nsvc1)[0x56372d478fc0]{DISABLED_NOTINSTALLED}: Received Event OML_DOWN <0004> bts_ipaccess_nanobts.c:581 NM_BTS_OP(bts0)[0x56372d46f120]{DISABLED_OFFLINE}: Received Event OML_DOWN <0004> nm_bts_fsm.c:319 NM_BTS_OP(bts0)[0x56372d46f120]{DISABLED_OFFLINE}: state_chg to DISABLED_NOTINSTALLED <0004> bts_ipaccess_nanobts.c:582 NM_GPRS_CELL_OP(gprs-cell0)[0x56372d46f250]{DISABLED_OFFLINE}: Received Event OML_DOWN <0004> nm_gprs_cell_fsm.c:296 NM_GPRS_CELL_OP(gprs-cell0)[0x56372d46f250]{DISABLED_OFFLINE}: state_chg to DISABLED_NOTINSTALLED ^Csignal 2 received <0004> bsc_init.c:66 shutting down OML for BTS 0

2 years, 10 months

3
4
0 0

Announcement of "OsmoDevCall" on July 9, 2021

by Harald Welte

Dear Osmocom community, It's my pleasure to announce the next OsmoDevCall at July 9, 2021 at 20:00 CEST at https://meeting4.franken.de/b/har-xbc-bsx-wvs This meeting will have the following schedule: 20:00 meet + greet 20:15 hands-on tutorial by miaoski: Setting up open5gs 21:00 USSE: unstructured supplementary social event [*] 22:00 close of call Attendance is free of charge and open to anyone with an interest in Osmocom. 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)

2 years, 10 months

1
0
0 0

inter-BSC handover

by Keith

Hi all. I'm testing to see if inter-BSC handover will work between RBS and osmo-bts, given that support for handover from an E1 to RTP call is not yet supported. Among all kinds of other things going on, I'm not finding it easy to understand how to configure everything for inter bsc handover. I know there are two videos (at least) from Neels at OsmoDevCon, on the subject of handover and then inter-MSC handover. I have one DUG/RUS configurarion with the e1d, bsc/msc/mgw/hlr running on the associated PC and one remote SysmoBTS, which is running osmo-bsc and it's associated MGW locally. All that is fine, I can call between the two BTSs successfully. I'm guessing I should add the neighbours manually in each bsc but I'm not sure what to configure in the MSC. Maybe I'll figure it out this evening, but I thought it best to also write most given the time zones and most of you guys will see this before I get back to work tomorrow. Thanks! k

2 years, 10 months

3
6
0 0

People.osmocom.org seems to be down

by Tomcsanyi, Domonkos

Hello All, Sorry about creating noise on this list, but I could not find the correct place to raise this: people.osmocom.org seems to be down. I have checked it from multiple internet connections and also with DownDetector and the result was always the same. I noticed this when I tried to watch a recording of the OsmoDevCall about SS7 and SIGTRAN - the link to the video timed out. Apologies again for asking for a sysadmin task on this list. In case there is anything I could help with or there is a mirror of these videos I don’t know of (yet) feel free to tell me about it. Thank you! Domi

2 years, 10 months

2
1
0 0

osmoSTP association establishment

by Madarassy László

Hi Devs, I have successfully compiled and integrated osmoSTP with our product. I have a question regarding to assotiaction establishment: Currently we'll initiate the associtation establishment from our product and STP will reply to our INIT message. Is it possible to start the establishment from STP side? I haven't found any cli command/configuration for this. Thanks, Laszlo

2 years, 10 months

2
1
0 0

Help on reading values of ISIM

by 程子帅

Dear Osmocom community, I am using pysim to read values of ISIM. However, it just returns "None, None". And the aids of my SIM card is ['a0000000871002ff86ffff89ffffffff']. It seems does not have ISIM application on my SIM card. How should I read values of ISIM? Best regards, Zishuai CHENG

2 years, 10 months

3
3
0 0

Announcement of "OsmoDevCall" on June 11, 2021

by Harald Welte

Dear Osmocom community, It's my pleasure to announce the next OsmoDevCall at June 11, 2021 at 20:00 CEST at https://meeting4.franken.de/b/har-xbc-bsx-wvs This meeting will have the following schedule: 20:00 meet + greet 20:15 presentation by keith: "Screen Sharing peek at TIC A.C. infrastructure in Oaxaca" 21:00 USSE: unstructured supplementary social event [*] 22:00 close of call TIC A.C. is an operator of Osmocom based community cellular networks in indigenous communities of the Mexican state of Oaxaca. Keith works with Rhizomatica and TIC A.C. and will give us some live insight into how they operate Attendance is free of charge and open to anyone with an interest in Osmocom. 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)

2 years, 11 months

1
0
0 0

PySim-shell: File not found errors

by bryan coxwell

Hi all, I'm using pySim-Shell with a SysmoISIM-SJA2 as well as a SysmoUSIM-SJS1 and on both cards I get quite a few "File not found" errors trying to access different EFs. I'll use EF.NCP-IP as an example to illustrate the issue I'm having below. My initial steps when I plug in the card are as follows: 1) ./pySim-shell -p0 2) verify_adm <adm1 key> 3) select ADF.USIM Now when I run "dir" in ADF.USIM it lists a number of EFs I'm interested in, including EF.NCP-IP. Since this requires service number 80 to be available in EF.UST, I run "select EF.UST" followed by "ust_service_activate 80". This runs without issue. When I run select ADF.USIM now followed by select EF.NCP-IP, the card returns a "File not found" error. So my questions are: Is this file not supported on the SJA2 and SJS1? Is there a way for me to add those files to ADF.USIM? Is there a list of the known supported EFs of the SJA2 and SJS1? I looked and couldn't find anything. Thank you in advance!

2 years, 11 months

3
3
0 0

No ISIM application on SysmoISIM-SJA2?

by bryan coxwell

Hi all, I feel like I may be missing something about how SIM cards work here, but I’m unable to figure out how to load the ISIM application on my SysmoISIM-SJA2s, so I’m reaching out here for some help. I started with pySim-shell and listed the directories under the MF directory and it shows only ADF.USIM, so I decided to use shadysim_isim.py to list out the applications on the card and was shown this: AID: a0000000620001, State: 01, Privs: 00 AID: 4a6176656c696e2e6a637265, State: 01, Privs: 00 AID: a0000000620101, State: 01, Privs: 00 AID: a0000000620102, State: 01, Privs: 00 AID: a0000000620201, State: 01, Privs: 00 AID: a000000062020801, State: 01, Privs: 00 AID: a00000006202080101, State: 01, Privs: 00 AID: a0000000620002, State: 01, Privs: 00 AID: a0000000620003, State: 01, Privs: 00 AID: a000000062010101, State: 01, Privs: 00 AID: a00000015100, State: 01, Privs: 00 AID: a0000000090005ffffffff8911000000, State: 01, Privs: 00 AID: a0000000090005ffffffff8912000000, State: 01, Privs: 00 AID: a0000000090005ffffffff8913000000, State: 01, Privs: 00 AID: a0000000090005ffffffff8911010000, State: 01, Privs: 00 AID: a0000000871005ffffffff8913100000, State: 01, Privs: 00 AID: a0000000871005ffffffff8913200000, State: 01, Privs: 00 AID: a0000000090003ffffffff8910710001, State: 01, Privs: 00 AID: a0000000090003ffffffff8910710002, State: 01, Privs: 00 AID: a0000000090005ffffffff8915000000, State: 01, Privs: 00 AID: a00000015141434c, State: 01, Privs: 00 Instance AID: a00000015141434c00 The SysmoUSIM/ISIM manual pointed me to Annex E of 3GPP 101.220 which says the prefix of the ISIM application is A00..00871004. So my questions are: Am I missing something and the app is installed? If not, is there a way to load and install the ISIM application? Thanks in advance everyone.

2 years, 11 months

2
1
0 0

Issue with LimeSDR Mini

by Akib Sayyed

Dear List I am trying to use latest Osmo-core suite (osmo:stp,hlr,msc,bsc,bts,mgw) with limesdr mini but facing issue as soon power rampup starts. is there any stable release which I can use with limesdr mini -- Akib Sayyed Matrix-Shell akibsayyed(a)gmail.com akibsayyed(a)matrixshell.com Mob:- +91-966-514-2243

2 years, 11 months

6
7
0 0

LCLS and osmo-sip-connector

by Keith

Hi all. I would like to implement some functionality that existed as a kind of happy accident?, in the osmocom-nitb That is - that media endpoints in INVITEs/200s and re-INVITEs from a SIP UA to osmo-sip-connector just ended up being transparently communicated to osmo-bts. This made it really easy to take the pbx out of the audio stream. I wanted to share where I am at with that. freeswitch even has a console command for this: "uuid_media" can switch the pbx in and out of the stream during the call. In the case of a MS to MS call on the same bts, we just connect the two osmo-bts media endpoints to each other. Freeswitch can schedule to playback message on calls and such like - for "your credit ran out" message for example - and it works pretty good. FS knows to put itself back into the stream with a re-INVITE with it's own IP in the SDP before playing the audio and invites itself back out of the stream as soon as playback is finished. I've been looking on and off, not that I've given it a huge amount of time, at how to replicate this with the BSC/MSC/MGW/SIP combination. First thing was to fix up the BSS messages and Global Call Reference generation. (TS 23.284) Given that Max had done most of this, that's pretty easy, although I got lost at one point down a rabbit hole of trying to figure out more than I needed to with the FSM and BSS messages, and that put me off working on it for a while. Anyway, https://gerrit.osmocom.org/c/osmo-msc/+/24236 exists and "works" - that is you can do LCLS with either mgw-loop or bts-loop configured on the BSC - but only for the internal mncc, obviously as the osmo-sip-connector still does not know what to do with the GCR (global call reference) I thought about various hackish things to do. (maintain a table of call-ids and their gcr on the sip conn and add an X-Osmo-CallID header to the SIP) but I've also been looking at the specs. TS 29.164 (section 6) says that the GCR should be encapsulated in a binary encoded ISUP payload, there are pointers in the spec to ITU Q.1912.5 (Section5 and thereabouts) So the ISUP messages should be added to SIP messages, requiring a multipart MIME attachment to the INVITE with the SDP and the ISUP. Also see RFC3204 What I don't know is how sip UEs will respond to these. I wonder will they decode them, I doubt it, some searching for SIP-I support in FreeSwitch confirms no support. So I'm thinking that I need to serialise the GCR and add it to an "X-" SIP header, so we at get it back on the B-leg. So yes, I need to just do this, but I got stalled a bit again with my lack on programming skills trying to learn how to serialise the GCR the "right" way. - but once I figure that out, then I can at least test what happens and see how the MSC and MGW behaves with the MNCC messages that result from SIP re-INVITES. Maybe that just works, but I don't think so, I think I will need to implement more BSS LCLS messages to actually change the LCLS states, not just update media endpoints. Sometimes I wonder here what should happen in the sip conn and what in the MSC. Anyway, It's been on my mind to write this up quickly to the ML just in case somebody has a "OH... better not do it like that" type comment.. Thanks k.

2 years, 11 months

2
1
0 0

Announcement of "OsmoDevCall" on May 28, 2021

by Harald Welte

Dear Osmocom community, It's my pleasure to announce the next OsmoDevCall at May 28, 2021 at 20:00 CEST at https://meeting4.franken.de/b/har-xbc-bsx-wvs This meeting will have the following schedule: 20:00 meet + greet 20:15 presentation by fixeria: "Hacking binary protocols with Pycrate" 21:00 USSE: unstructured supplementary social event [*] 22:00 close of call Attendance is free of charge and open to anyone with an interest in Osmocom. 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)

2 years, 11 months

1
0
0 0

Asking about Modification for USSD RESP

by Radiarisainana Sitraka

Hello, When the phone send *#100#, the ussd responds with "the extension is xxxx" and it gives option to accept after this like button "ok". My question is it possible to perform this response of ussd for two options "reply" and "cancel" and the phone could reply the answer of the network? Chears,

3 years

2
1
0 0

Announcement of "OsmoDevCall" on May 14, 2021

by Harald Welte

Dear Osmocom community, It's my pleasure to announce the next OsmoDevCall at May 14, 2021 at 20:00 CEST at https://meeting4.franken.de/b/har-xbc-bsx-wvs This meeting will have the following schedule: 20:00 meet + greet 20:15 presentation by laforge: "SS7 and SIGTRAN in 2G/3G networks" 21:00 USSE: unstructured supplementary social event [*] 22:00 close of call Presentation Abstract: This talk will cover some classic circuit-switched SS7 basics as well as SIGTRAN (SS7 over IP) and how this is used as underlying transport for a variety of interfaces in the 2G (GSM) and 3G (UMTS) cellular networks even today. Attendance is free of charge and open to anyone with an interest in Osmocom. 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

1
0
0 0

Sharing my mixed success story with Grcard SIMs

by Mychaela Falconia

Hello Osmocom community, I made some posts here earlier this year about my attempts to obtain some programmable SIM cards from Grcard (a well-known Chinese manufacturer of SIM and other smart cards) that are GSM SIM only, without USIM or ISIM applications - but I just realized that I never posted anything regarding the final outcome of those escapades. The present post is intended to summarize what I obtained and what I learned through that venture. The first point to be noted is that Grcard make many bazillion different card models, but frustratingly, they never let me see any kind of catalog of their different offerings. Instead what happened is that when I first approached them back in January and told them what I was looking for in very basic terms (I simply said that I wanted a GSM-only SIM card without any USIM or ISIM stuff), they offered me one of their card models based on those stated requirements, they first sent me a few sample pieces of this card model they selected for me, and then I ended up ordering 200 pieces of that same model with my own custom printing on the cards. The card model which Grcard offered to me back in January and of which I got 200 pcs a month ago in April turned out to be exactly the same in technical terms as the one that was once sold by Sysmocom as sysmoSIM-GR2: https://osmocom.org/projects/cellular-infrastructure/wiki/GrcardSIM2 As I understand it, Sysmocom had that sysmoSIM-GR2 as an offering back in late 2013, thus it was quite surprising to see that Grcard still readily sell that exact same model 7 and a half years later - but they do. As a result of having done a ton of work with these cards over the past few months, I now know a lot more about them than is said in the scant Osmocom wiki page above, and a lot more than the little bits of knowledge embedded in pySim code from 2013 supporting this model. Extensive write-ups about these cards can be found in my fc-sim-tools repository, but here is a basic summary of the good and the bad: The good: * These GrcardSIM2 aka FCSIM1 cards are truly native GSM 11.11 SIM, and do not speak the unwanted-innovation UICC protocol at all. * F=512 D=8 speed enhancement (the only SIM speed enhancement mode called for in the original GSM 11.11 spec and the only one implemented in most classic GSM MS hardware such as Calypso) is supported by these cards, thus if your GSM MS firmware has this speed enhancement enabled (at least with TI platform, many legacy fw versions have it disabled - don't know about other GSM chipset vendors), your phone will talk to the SIM at about 50781 bps, instead of the circa 8737 bps you get with the basic non-enhanced F=372 D=1 mode. * The security model on these cards works the way it is supposed to: they initially ship with a known default SUPER ADM key, but if you change both ADM5 and ADM11 (SUPER ADM) keys to your own secrets, then the card becomes fully secure in the traditional SIM security sense. I personally don't understand and will likely never understand what is so wrong with letting your paying service subscribers know their own Ki and letting them clone their SIM if they so wish, but if you wish to replicate the traditional security model where you program Ki and change ADM keys to some secret, you *can* do it with FCSIM1 cards. Standard PIN1/PIN2/PUK1/PUK2 can be freely reset if you authenticate with ADM5 or ADM11, but if you change those ADM keys to secrets, then the PIN system becomes fully secure too. Contrast the situation with Grcard's earlier model (sysmoSIM-GR1) where anyone can freely reset both regular and ADM PINs without any authentication, meaning no security whatsoever. * All 3 of COMP128v1, COMP128v2 and COMP128v3 are supported. I naturally choose COMP128v3 for my own deployments - A5/1 is weak enough to begin with, no need to weaken it further by reducing the effective key length to just 54 bits with COMP128v1 or v2. * As far as I can tell, there are NO unwanted STK applications on these cards. Harald said here earlier that Sysmocom's business relationship with Grcard ended when Grcard started shipping cards with some preinstalled STK applications displaying some pop-up messages in Chinese, but I see no evidence of any such applications being present on the FCSIM1 cards I got from them this year. I have tried issuing a feature-generous TERMINAL PROFILE toward the card (listing support for all common SAT features), and the SW response was 9000 - no matter what I tried, I never got the card to respond with SW of 91xx, indicating some proactive SIM command - thus as far as I can tell, these SIMs never issue any proactive commands. * The best good of all: no MOQ! Instead of being forced to buy 1000 or more cards and have them go to waste because I will never find that many people who have the same pattern of technology likes and dislikes as I do, I was able to buy just 200 cards - I could have ordered as few as 100, but I ordered 200 because they were cheap - and I got those 200 cards with my own custom printing and with my choice of form factor cut - I chose 2FF-only, of course. The bad: * The free reformatting ability that existed on sysmoSIM-GR1 has been taken away. On sysmoSIM-GR1 you could erase the card file system and recreate your own tree of DFs and EFs according to your own liking (with you deciding which files to include or omit, what size to allocate for each file, and what access conditions it should have), but those proprietary APDU commands from GR1 don't work on GrcardSIM2 (FCSIM1), and the official answer from Grcard is that such downstream reformatting is not allowed. I am guessing that what I want probably *can* be done by reformatting the card flash and reloading their CardOS at a lower level, but needless to say, Grcard won't divulge any of the knowledge that would be needed for such an endeavor. * The fixed formatting these cards came with (which we have no way of changing per above) is far from ideal: EF_AD is only 3 bytes and not 4, some files that aren't absolutely critical but would be nice to have like SDN and ECC are missing, and the allocated record size for EF_ADN is only 28 bytes, allowing only 14 characters for the contact name field. Contrast with old T-Mobile USA SIMs that have 44-byte ADN records (30 characters for contact name), or current Sysmocom cards that have 34-byte ADN records, allowing 20 characters. Grcard people told me that they can change this file system layout to a different one with MOQ of 10000 pcs, but of course such MOQs are absolutely not acceptable for "just for love" applications like mine. * There is no OTA programming capability on this card model. I was hoping that I could program EF_MSISDN over the air (yes, I know full well that a phone doesn't need to know its own MSISDN to make or answer calls, but all classic GSM phones have a menu command for "Show my number" or whatever it's called, and that's what EF_MSISDN on the SIM is for) like I can do on sysmoUSIM-SJS1 and sysmoISIM-SJA2 cards, but nope, this functionality just isn't there. Grcard folks were telling me that they have some other card model that supports OTA, but I never got a straight answer out of them as to whether that other card model is also GSM SIM only, or if it is UICC/USIM/ISIM - I suspect the latter, which would be totally uninteresting to me. * The worst badness of all is that Grcard people absolutely hate customers who ask too many technical questions, and when pressed, they typically respond only with non-answers. There is basically NO technical support of the kind we got used to in highly technical communities like Osmocom with vendors like Sysmocom, instead they are used to dealing with sales and marketing types. I also got the impression that selling to R&D customers is very foreign to them, instead they are set up for making cards for operator/MVNO type of customers who let the card vendor do all of the programming at the factory and don't get into any real technical stuff themselves. So here is what we got: https://www.freecalypso.org/members/falcon/pictures/SIMs/FCSIM1_front.jpeg https://www.freecalypso.org/members/falcon/pictures/SIMs/FCSIM1_back.jpeg The cards depicted in those photos are quite real, they are sitting right here at my FreeCalypso HQ in California, and they work in the sense that I can program everything including IMSI, Ki and COMP128v3 selection. I haven't set up my own GSM network yet - I already acquired a couple of nanoBTS units (one for 850 MHz, one for 1900 MHz), but I still need to acquire a better server machine for running Osmocom CNI software. Much like any other feeling and soulful human, I have a deep-rooted urge to share my work with others. When it comes to the present SIM card venture, I am doing everything I can to share my work with the community in 3 ways: 1) The software I developed for programming these cards is free to the world, with an explicit public domain license statement: https://www.freecalypso.org/hg/fc-sim-tools/ My fc-sim-tools suite is a direct competitor to pySim, written in C instead of Python, and split into separate fc-simtool and fc-uicc-tool for the two very different protocols that exist for talking to SIM cards. Oh, and my tools can be used to program Sysmocom webshop cards too, not just my Grcard-based FCSIM1. 2) If anyone else would like to buy similar cards from Grcard, I will be happy to put you in touch with my contact there and guide you through the process - and by encouraging anyone with a commercial interest to buy directly from Grcard instead of me acting as a reseller, I explicitly disavow any thought of commercially profiting from any related venture or acting as any kind of commercial entity myself. 3) If there is anyone in the world who shares my core philosophical position whose wording is imprinted on the plastic on my FCSIM1 cards (see the pictures above) and would like to get a few of these cards, please let me know, and I will be glad to send you however many cards you need, for the cost of shipping only, or at most covering my own cost of ordering more cards in the highly unlikely event that I get enough interest to run down my stock. In hacking fellowship, Mother Mychaela Hasta la Victoria, Siempre - 2G forever!

3 years

1
0
0 0

pySim ModuleNotFoundError: No module named 'construct'

by Niels ten Oever

Hi all, I am a happy user of pySim - thanks a lot for the work on it. Unfortunately, I think something broke during recent updates that might have to do with software versions. I went through a full reinstall and have done all the software installations mentioned in the README.md, but when I do: $ ./pySim-read.py -p0 I get: Traceback (most recent call last): File "./pySim-read.py", line 31, in <module> from pySim.ts_51_011 import EF, DF, EF_SST_map, EF_AD File "/home/gagarin/Data/pysim/pySim/ts_51_011.py", line 324, in <module> from construct import * ModuleNotFoundError: No module named 'construct' I tried: $ sudo pip3 install construct Requirement already satisfied: construct in /usr/local/lib/python3.8/dist-packages (2.10.67) But that did not solve the issue. Any pointers are very welcome. All the best, Niels PS FYI: $ cat /proc/version Linux version 5.8.0-50-generic (buildd@lgw01-amd64-051) (gcc (Ubuntu 10.2.0-13ubuntu1) 10.2.0, GNU ld (GNU Binutils for Ubuntu) 2.35.1) #56-Ubuntu SMP Mon Apr 12 17:18:36 UTC 2021 $ lsusb | grep OMNI Bus 001 Device 033: ID 076b:3031 OmniKey AG OMNIKEY 3x21 Smart Card Reader -- Niels ten Oever, PhD Postdoctoral Researcher - Media Studies Department - University of Amsterdam Research Fellow - Centre for Internet and Human Rights - European University Viadrina Associated Scholar - Centro de Tecnologia e Sociedade - Fundação Getúlio Vargas https://nielstenoever.net - mail(a)nielstenoever.net - @nielstenoever - +31629051853 PGP: 2458 0B70 5C4A FD8A 9488 643A 0ED8 3F3A 468A C8B3 Read my latest article on Internet infrastructure governance in New Media & Society here: https://journals.sagepub.com/doi/full/10.1177/1461444820929320

3 years

5
9
0 0

comparison of open source 4G and 5G implementations

by Niels ten Oever

Hi all, Slightly inspired by the excellent responses I got today on this list on another problem I wanted to ask a question about the comparison of open source 4G and 5G implementations. While there are several lists that provide overviews of said open source software for 4G and 5G networks [0], I have not found a paper, blogpost, or table that compares the implementations in a meaningful manner. Does such an overview exist, if so, could you point me to it, or if it doesn't exist, do you think such an overview would be helpful? Have a great weekend. Niels PS If this is the wrong list to post this (kind of) question to, feel free to tell me so :) [0] for instance https://github.com/ravens/awesome-telco and https://github.com/calee0219/awesome-5g -- Niels ten Oever, PhD Postdoctoral Researcher - Media Studies Department - University of Amsterdam Research Fellow - Centre for Internet and Human Rights - European University Viadrina Associated Scholar - Centro de Tecnologia e Sociedade - Fundação Getúlio Vargas Affiliated Factulty - Digital Democracy Insitute - Simon Fraser University https://nielstenoever.net - mail(a)nielstenoever.net - @nielstenoever - +31629051853 PGP: 2458 0B70 5C4A FD8A 9488 643A 0ED8 3F3A 468A C8B3 Read my latest article on Internet infrastructure governance in New Media & Society here: https://journals.sagepub.com/doi/full/10.1177/1461444820929320

3 years

1
0
0 0

Announcement of "OsmoDevCall" on April 23, 2021

by Harald Welte

Dear Osmocom community, It's my pleasure to announce the next OsmoDevCall at April 23, 2021 at 20:00 CEST at https://meeting4.franken.de/b/har-xbc-bsx-wvs This meeting will have the following schedule: 20:00 meet + greet 20:15 presentation by horiz0n: "YIG & YANG (Yet ANother yiG driver)" 21:00 USSE: unstructured supplementary social event [*] 22:00 close of call Presentation Abstract: This talk will briefly introduce the working principles of YIG (Yttrium Iron Garnet) microwave circuits, their applications and finally conclude with a presentation of a recently developed driver circuit. Attendance is free of charge and open to anyone with an interest in Osmocom. 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, 1 month

1
0
0 0

Announcement of "OsmoDevCall" on April 9, 2021

by Harald Welte

Dear Osmocom community, It's my pleasure to announce the next OsmoDevCall at April 9, 2021 at 20:00 CET at https://meeting4.franken.de/b/har-xbc-bsx-wvs This meeting will have the following schedule: 20:00 meet + greet 20:15 presentation: pySim-shell - the next generation of pySim 21:00 USSE: unstructured supplementary social event [*] 22:00 close of call Presentation Abstract: For more than a decade, pySim-prog has been the tool to configure/program SIM cards in research/lab/private cellular networks. Originally designed for very simplistic GSM-only SIM Cards, it was extended again and again to cover more use cases and parameters. There is a limit as to how far one can go with stuffing everything into command line arguments. In 2021, pySim-shell was created as the next generation tool. It features interactive navigation around the file system, editing capabilities, backup and restore of all [known] files, ... Attendance is free of charge and open to anyone with an interest in Osmocom. 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, 1 month

1
0
0 0

WIP / RFC for pysim 'next generation;' aka pysim-shell

by Harald Welte

Dear Osmocom community, pySim-prog was nice when there were only 5 parameters on a SIM that we could program, and where the use case was pretty limited. Today, we have SIM/USIM/ISIM cards with hundreds of files and even more parameters to program. We cannot add a command line argument for each file to pySim-prog. Instead, this introduces an interactive command-line shell / REPL, in which one can navigate the file system of the card, read and update files both in raw format and in decoded/parsed format. The idea is primarily inspired by Henryk Ploetz' venerable cyberflex-shell, but implemented on a more modern basis using the cmd2 python module. You can see the very first prototype in the laforge/shell branch of pysim.git You can do things with it like this: ===> Start-up and authenticate with adm pin ---------------------------------------------------------------------- $ ./pysim-shell.py -p 0 Using PC/SC reader interface Autodetected card type: sysmoISIM-SJA2 AIDs on card: ['a0000000871002ffffffff8907090000', 'a0000000871004ffffffff8907090000'] Welcome to pySim-shell! pySIM-shell (3f00)> verify_adm 92990895 ---------------------------------------------------------------------- ===> interactive help ---------------------------------------------------------------------- pySIM-shell (3f00)> help Documented commands (use 'help -v' for verbose/'help <topic>' for details): ISO7816 Commands ================ read_binary select_adf select_file update_binary update_record verify_chv pySim Commands ============== intro verify_adm USIM Commands ============= read_ehplmn ust_service_activate ust_service_deactivate pySim-shell built-in commands ============================= alias help macro quit run_script shell edit history py run_pyscript set shortcuts ---------------------------------------------------------------------- ===> more interactive help ---------------------------------------------------------------------- pySIM-shell (3f00)> help read_binary usage: read_binary [-h] [--file-id FILE_ID] [--offset OFFSET] [--length LENGTH] [--record-nr RECORD_NR] Read binary data from a transparent EF optional arguments: -h, --help show this help message and exit --file-id FILE_ID File ID --offset OFFSET Byte offset for start of read --length LENGTH Number of bytes to read --record-nr RECORD_NR Number of record to read ---------------------------------------------------------------------- ===> navigating the FS and reading files ---------------------------------------------------------------------- pySIM-shell (3f00)> select_file 7f20 ['622c8202782183027f20a509800171830400018d088a01058b032f0601c60f90017083010183018183010a83010b'] pySIM-shell (3f00/7f20)> read_binary --file-id 6f07 089910070000400310 ---------------------------------------------------------------------- ===> interaction with local filesystem, i.e. I/O redirect + shell commands ---------------------------------------------------------------------- pySIM-shell (3f00)> select_adf a0000000871002 pySIM-shell (a0000000871002)> select_file 5f3b pySIM-shell (a0000000871002/5f3b)> read_binary --file-id 4f20 > /tmp/f pySIM-shell (a0000000871002/5f3b)> !cat /tmp/f ffffffffffffffff07 ---------------------------------------------------------------------- ===> piping output through shell tools like grep ---------------------------------------------------------------------- pySIM-shell (3f00)> read_ust | grep 86 Service 86 - Allowed CSG Lists and corresponding indications ---------------------------------------------------------------------- ===> enabling/disabling services ---------------------------------------------------------------------- pySIM-shell (3f00/7f20)> ust_service_activate 123 pySIM-shell (3f00/7f20)> ust_service_deactivate 123 ---------------------------------------------------------------------- It's a very first prototype, but it is really promising. The major tasks I see to make this go anywhere is: * have "File" class with encoder/decoder methods, which are registered automatically with a 'file system' layer that knows about the DF/ADF hierarchy ** this allows us to have a "read-decoded" command, which will call the decode method of the file, automatically resolved by the selected FID/path * automatic mapping of file-name -> FID and FID -> file name ** when printing (like in the path), use the human-readable names ** allow users to use human-readable names in SELECT * decode + display the TLVs / FCPs after a SELECT (like cyberflex-shell * ability to enable/disable APDU trace * dynamically register/deregster commands based on the path, i.e. offer USIM commands only when in ADF_USIM We have quite a bit of that infrastructure in the c-language libosmosim, (part of libosmocore.git), but unfortunately not in python :/ Let me know if anyone is interested in joining this effort. Regards, Harald -- - Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

3 years, 1 month

6
17
0 0

Question about establishing stable internet link between UE and HNB connected to our developed network core.

by morteza ali Ahmadi

Hi, osmocom team members. In order to have an internet connection in UE, we have run OsmoGGSN project to set up GGSN. Also, SGSN is developed in our system. At this step, UE connects to our network core and we can query to an arbitrary site in the UE browser and we see the answer of the query without any problem and everything is OK. But after about 30 or 40 seconds, UE sends "Deactivate PDP Context Request" with SM Cause "SM Cause: Protocol error, unspecified (111)" and the connection is reset and a new "Activate PDP Context Request" is required. What is the reason and how can we solve it? -- *When there is much light, The shadow is deep...*

3 years, 1 month

4
5
0 0

Idea for 2021: Regular "OsmoDevCall"

by Harald Welte

Dear Osmocom community, as the pandemic continues and physical meetings are out of the question for the forseeable future, it would be a good idea to have a periodic virtual online meeting of the interested Osmocom community. I was thinking of a format where we would serve two major purposes: 1) technical talks about osmocom relevant topics - ideally current/recent developments * can be pre-recorded to avoid any problems with technical setup, streaming, ... * should ideally have a Q+A session at their initial "airing" during one OsmoDevCall 2) unstructured solicited social event (USSE) * random chat in audio (optionally video) * not recorded, obviously The recording of the technical presentation should then be permanently made available (like the presentations of our prior OsmoCon / OsmoDevCon). Not every OsmoDevCall would neccessarily need the two parts, but I think it would be great if we can make that happen. We could also have e.g. a two-weekly schedule for the USSE and a monthly schedule for the technical presentation. We'd need somebody to volunteer to "manage" the "broadcast" side of this, preferably somebody with at least some prior exposure to online events (like the c3voc). I'm using https://osmocom.org/issues/4928 to collect a tentative list of topics. Feel free to add your ideas there, as well as any comment/ feedback you may have. Regards, Harald -- - 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, 1 month

2
5
0 0

where to send pySim patches

by Riemer, Björn

Hello list, we are working on extensions to pySim for the sjs2 card mainly to make our 5G phones to accept our network. How should we send this patches? Via this mailing list or should we wait a little longer until Harald finished restructuring the mailing lists? Best Regards Bjoern

3 years, 2 months

4
4
0 0

sysmoISIM-SJA2 clock stop discrepancy

by Mychaela Falconia

Hello esteemed masters of Osmocom and Sysmocom, As I am doing some experiments with sysmoISIM-SJA2 cards in order to make a contingency plan in case I am not able to buy cards from Grcard beyond the 5 sample cards I got in February (my contact person there hasn't been responding to email for the past 3 days), I have noticed a discrepancy between this card's ATR and the file characteristics byte it returns in response to SELECT in the GSM 11.11 SIM protocol, regarding allowed levels for clock stop. My sysmoISIM-SJA2 cards (bought from the webshop in late Jan into early Feb) return the following ATR: 3B 9F 96 80 1F 87 80 31 E0 73 FE 21 1B 67 4A 4C 75 30 34 05 4B A9 The TA byte for T=15 indicates allowed voltage classes and allowed levels for clock stop. On this card this byte equals 0x87, meaning all 3 voltage classes (good), but also indicating that when the clock is stopped, it should be HIGH. However, the file characteristics byte returned in response to SELECT (both MF and DF_GSM) in the GSM 11.11 SIM protocol is 0xB1; decoding this byte per 3GPP TS 51.011, it says "clock stop allowed, no preferred level". Thus the file characteristics byte says that there is no preferred level, yet ATR says that HIGH level is preferred - or not just preferred, but required? (7816-3 seems to say it is only a preference, not a requirement; I seem to recall some other spec that said it's a requirement, but I can't find it now.) This discrepancy poses a potential problem if these cards are to be used in classic GSM/2G dumbphones whose original firmwares are based on the reference from TI. That reference fw code does not look at ATR for the purpose of determining allowed clock stop levels (most classic SIMs didn't have that T=15 TA byte in their ATR, it became commonly present when UICC/USIM stuff came along), instead it looks at the file characteristics byte returned in response to SELECT of DF_GSM. Furthermore, if the file characteristics byte says that there is no preferred level for clock stop, TI's reference fw configures the hw to leave the clock LOW during idle. I can only reason that other classic dumbphone firmwares (from other chip vendors) may very likely do the same: GSM SIM specs (11.11 and 51.011) don't require ME implementations to look at T=15 bytes in ATR, instead they direct MEs to follow the file characteristics byte. Can someone from Sysmocom officially confirm whether or not it is OK to operate sysmoISIM-SJA2 cards with clock stop at LOW level, contrary to ATR asking it to be HIGH? I have done a limited test of putting one of these cards into an FCDEV3B (with this aspect of the firmware left unmodified, so the clock line was low during idle) and the SIM interface appeared to still be alive after some deep sleep (clock stop) cycles. However, it was a very limited test, and I don't have my own network set up yet to make a more thorough test - and in any case, an official confirmation would be much better than anecdotal observations. TIA, Mychaela

3 years, 2 months

1
0
0 0

Osmocom Mailing List re-organization

by Harald Welte

Dear Osmocom community, This topic has been past due for way too many years by now: A re-organization of our major mailing lists. I would like to propose the following changes. Pleas let me know if you have any comments or feedback. I'm aware that renaming will mean people have to update their mail filter rules, but I think we're long past the point where the names of some of our lists started to confuse users. == openbsc(a)lists.osmocom.org == * openbsc doesn't exist anymore since OsmoNITB, which is also obsolete * does already cover anything "Osmocom CNI" related * Proposed new name: osmocom-cni(a)lists.osmocom.org == osmocom-net-gprs(a)lists.osmocom.org == This date back to when GPRS was a highly experimental add-on to our GSM code base. This list should simply be merged with openbsc@ as osmocom-cni(a)lists.osmocom.org == simtrace(a)lists.osmocom.org == Historically was created to cover only the simtrace project. We should rename this to osmocom-simcard(a)lists.osmocom.org or something along those lines. I would like to suggest it covers * SIMtrace / SIMtrace2 hardware + firmware * pySim and related tools for working with SIM/USIM/UICC cards * any other information / discussion related to SIM/USIM/UICC cards, like OTA, ARA-M, ... == osmodevcon(a)lists.osmocom.org == This has been a private list for people attending OsmoDevCon I would like to open up list membership to the general public, and ensure it also covers the new OsmoDevCall. We could then have discussions regarding feedback, topics, scheduling, etc. on that list. Maybe rename it to osmocom-events(a)lists.osmocom.org instead? To differentiate: osmocom-event-orga(a)lists.osmocom.org should remain a private list related to organizational / administrative topics of those involved with organizing future events. == nextepc(a)lists.osmocom.org == Should have been renamed to open5gs(a)lists.osmocom.org quite some time ago, I simply forgot about it. My apologies. -- - 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, 2 months

4
5
0 0

Bringing back GrcardSIM2

by Mychaela Falconia

Hello esteemed masters of Osmocom, (asking here because Harald's proposed osmocom-simcard list hasn't been created yet) I have some questions and experience-based corrections related to the gold nuggets contained in this wiki page: https://osmocom.org/projects/cellular-infrastructure/wiki/GrcardSIM2 First let me establish relevance: even though Sysmocom stopped selling these GR2 cards ages ago and it looks like the wider Osmocom community also stopped playing with them once sysmoUSIM-SJS1 came out, these same GrcardSIM2 cards are still available from Grcard in the present day. A week and a half ago I received 5 sample cards (plain white, no printing, unprogrammed) from Grcard that return the same ATR as is listed for sysmoSIM-GR2, and all of the card-model-specific proprietary commands described on the above wiki page work exactly the same on these cards as they once worked on sysmoSIM-GR2. I am now in the process of ordering a batch of 200 of these cards from Grcard, with my own custom printing applied (so they will look pretty, not plain white and not black like sysmoISIM-SJA2) - essentially I am bringing back an exact equivalent of the discontinued sysmoSIM-GR2. With relevance thus established, let's move on technical questions: * The wiki page describes a file named EF.WEKI, file ID 0001 under DF.GSM. Whoever wrote this wiki page, how did you get this fancy name EF.WEKI? Was there some kind of document from Grcard that described this card-model-specific proprietary file? Does that document still exist somewhere? Can there be some way for mere mortals like me to see that document? * The wiki page describes byte 3 of EF.WEKI as selecting COMP128 algorithm version. It lists 0 as selecting COMP128v1 and 1 as selecting COMP128v2, and these two codes are correct - confirmed by programming these codes, doing a RUN GSM ALGO command, and comparing returned SRES and Kc against osmo-auc-gen. However, the page lists 3 as selecting COMP128v3, and this part is not correct - writing 3 in there results in COMP128v2 being selected, just like code 1. Instead I need to write 2 into the lower nibble of this byte in order to get COMP128v3 SRES and Kc in response to RUN GSM ALGO. * The COMP128 selection code is just the lower nibble of byte 3 of EF.WEKI - the upper nibble is something else that currently eludes my understanding. The wiki page instructs users to write 0 into the upper nibble, and so does pySim-prog - yet in the initial "unprogrammed" state of the cards I received from Grcard, this upper nibble is set to 2, not 0. I could not see any observable difference in card behaviour whether the upper nibble is set to 0 or 2 - either way the lower nibble selects COMP128 version for RUN GSM ALGO operations. * The wiki page gives the impression that EF.WEKI is 19 bytes long in total. However, the actual size of this transparent EF on the card is 35 bytes, i.e., there is another 16-byte field (some other key?) after Ki. Of the people who were once privileged with proper official documentation for these cards, might anyone be able to tell what this other key is for? Could it perhaps be some kind of key for OTA? Before someone tells me that I should direct these questions to Grcard, given that I am buying cards from them, let me assure everyone that yes, of course I am doing everything I can to pry this information out of them. However, they seem to have the same attitude as most Chinese companies where they just want you to buy their product and not ask any technical questions, and whatever answers they do give are so terse that they feel like non-answers. But there is also the undeniable fact that once upon a time these cards were resold by Sysmocom, once upon a time this Osmocom community right here worked with these cards, and someone in this community (or on Sysmocom staff) must have gotten enough documentation to write the wiki page and pySim-prog support for them. Thus I feel at least somewhat justified in asking this community for help with bringing back this lost knowledge. On a happier note, my fc-pcsc-tools suite (fc-simtool and its limited- function companion fc-uicc-tool) is advancing quite a bit in functionality. I don't know how it compares to pysim-shell since I gave up trying to get the latter to run under Slackware (just too many difficult dependencies), but from what I read in mailing list posts, pysim-shell seems to be rather UICC-centric - I couldn't tell if it is supposed to work on non-UICC GSM 11.11 protocol cards or not. In contrast, my fc-simtool (written in C, zero dependencies beyond libpcsclite) speaks the classic GSM 11.11 SIM protocol and does everything that is possible within this protocol, including innovative hacks like brute force search of the file ID space. This tool should be ideal for cards like GrcardSIM2 which are non-UICC and for which the classic GSM 11.11 SIM protocol is native. The companion utility fc-uicc-tool for the UICC protocol is quite minimal in functionality, just enough to satisfy the few areas of curiosity I had in relation to that protocol and the cards I have around that speak it. These new C-language SIM tools live here: https://www.freecalypso.org/hg/fc-pcsc-tools/ The code is 100% my own original work and there is a LICENSE file at the top of the repository declaring it as public domain, so there should be no problem with Free Software status of the work. In hacking fellowship, Mother Mychaela

3 years, 2 months

3
5
0 0

Jenkins: 2 new raspberry pi nodes / running on raspbian10

by Oliver Smith

Hey all, short FYI regarding jenkins.osmocom.org: two new raspberry pi nodes are available, in order to reduce wait times for free build slots during heavy osmo-trx development. All three pis execute the jenkins jobs on top of raspbian10 now, unlike the old setup where it was on top of debian 9 in a LXC running in raspbian10. In other words, the LXC layer is gone now, and there might be slight differences related to debian9 vs. debian 10 packages. For all the jobs running in docker instead of directly on the host, there should be no difference at all. Details are in OS#5055. Best, Oliver -- - Oliver Smith <osmith(a)sysmocom.de> https://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, 2 months

1
0
0 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC