OpenBSC December 2025

openbsc@lists.osmocom.org

26 participants
38 discussions

Head Soccer: The Ultimate Football Face-Off
by louispalmer1098＠gmail.com 30 Dec '25

30 Dec '25

Head Soccer brings an electrifying twist to classic football. Players control big-headed characters in fast-paced one-on-one matches filled with power-ups, kicks, and strategy. Every character has unique abilities that can turn the tide of the game in seconds. Timing and skill are crucial as you jump, shoot, and block your opponent’s goals. Whether you’re challenging AI or real players, Head Soccer delivers an addictive mix of humor, chaos, and competitive fun that keeps you coming back. Play at https://sportsgamesaz.io/head-soccer

1 0

Wordle Unlimited Delivers Endless Word Challenges for Curious Minds
by blank.landfowl.rcmo＠protectsmail.net 29 Dec '25

29 Dec '25

Introduction to Wordle Unlimited Wordle Unlimited is a popular word puzzle game that expands the familiar daily word challenge into an unlimited experience. Unlike traditional daily word games that restrict players to one puzzle per day, Wordle Unlimited allows continuous play without waiting. This simple change transforms a short daily habit into a flexible and engaging activity suitable for all schedules. Players can enjoy quick rounds during breaks or long sessions dedicated to improving vocabulary and logic skills. https://wordleunlimitedgame.org/ The core idea remains easy to understand, making Wordle Unlimited accessible to beginners while still rewarding experienced puzzle fans. Each round encourages critical thinking, pattern recognition, and language awareness. These qualities explain why the game continues to attract a global audience. Core Gameplay Mechanics Basic Rules and Structure Wordle Unlimited follows a straightforward structure. Players attempt to guess a hidden five letter word within a limited number of tries. After each guess, the game provides visual feedback using color indicators. Correct letters in the correct position receive one color, correct letters in the wrong position receive another, and incorrect letters remain neutral. This feedback guides future guesses and helps players refine strategy. The absence of daily limits means players can restart immediately after finishing a round. This structure supports experimentation and learning through repetition. Over time, players begin to recognize common letter patterns and effective opening words. Difficulty and Learning Curve The difficulty level in Wordle Unlimited feels balanced. Early rounds often feel manageable, which builds confidence. As players continue, vocabulary depth and strategic thinking become more important. The game does not rely on complex rules, yet it rewards careful planning and attention to detail. New players can quickly grasp the basics, while dedicated players discover subtle strategies such as letter frequency analysis and elimination techniques. This gradual learning curve helps maintain long term engagement. Features That Make Wordle Unlimited Stand Out Unlimited Play Sessions The defining feature of Wordle Unlimited is unrestricted gameplay. Players no longer feel pressure to solve a puzzle within a single daily attempt. This freedom allows relaxed play and encourages experimentation with different word choices. Unlimited access also supports practice sessions, which help improve performance in other word games. This feature makes the game suitable for both casual entertainment and focused mental training. Players can choose their own pace without artificial limitations. Custom Word Length Options Many versions of Wordle Unlimited include adjustable word lengths. Players can choose shorter or longer words depending on preference. Shorter words offer quick challenges, while longer words increase complexity and demand deeper vocabulary knowledge. This customization adds variety and prevents monotony. Adjustable settings also allow players to tailor the experience to skill level. Beginners may start with simple options, while advanced players seek longer and more demanding puzzles. Cognitive and Educational Benefits Vocabulary Expansion Regular play encourages exposure to new words. Players often encounter unfamiliar terms and learn meanings through context. This natural learning process feels enjoyable rather than academic. Over time, vocabulary range improves without formal study. The game also reinforces spelling accuracy. Repeated interaction with letters and word structures helps players recognize correct patterns and avoid common mistakes. Logical Thinking and Focus Each round requires careful reasoning. Players must analyze feedback and adjust guesses logically. This process strengthens problem solving skills and attention to detail. The limited number of attempts encourages efficiency and thoughtful decision making. Wordle Unlimited also promotes focus. Short rounds require concentration without overwhelming the player. This balance makes the game suitable for mental refreshment during busy days. Community and Social Appeal Sharing Results and Strategies Many players enjoy sharing results with friends or online communities. Result grids provide a simple visual summary without revealing answers. This sharing culture fosters friendly competition and discussion about strategies. Community interaction adds motivation. Players compare approaches, discuss optimal starting words, and celebrate successful streaks. This social layer enhances enjoyment without requiring direct multiplayer modes. Accessibility Across Platforms Wordle Unlimited works smoothly across devices such as computers, tablets, and mobile phones. Simple design and minimal loading times improve accessibility. Players can enjoy consistent performance regardless of platform. This flexibility supports short play sessions anywhere. Easy access contributes to the game popularity and widespread adoption. Strategy Tips for Better Performance Choosing Strong Opening Words An effective opening word includes common vowels and consonants. This approach maximizes information gained from the first guess. Words with diverse letters help eliminate possibilities quickly and guide future attempts. Experimentation plays an important role. Unlimited rounds allow testing different starting words to identify what works best for personal style. Adapting Based on Feedback Successful play depends on adapting to feedback after each guess. Players should avoid repeating eliminated letters and focus on confirmed patterns. Careful observation prevents wasted attempts and increases success rates. Patience also matters. Rushing guesses often leads to mistakes. Thoughtful analysis improves outcomes and enhances satisfaction. Comparison With Daily Word Games Wordle Unlimited differs from daily word puzzles through flexibility. Daily formats create anticipation but limit practice opportunities. Unlimited play removes restrictions and supports continuous improvement. Both formats offer enjoyment, but Wordle Unlimited suits players who prefer freedom and repetition. The ability to replay instantly makes it ideal for learning and experimentation. Long Term Appeal and Replay Value Wordle Unlimited maintains interest through simplicity and variety. Custom settings, unlimited rounds, and evolving personal strategies prevent fatigue. Each puzzle feels familiar yet fresh due to changing word combinations. The game adapts well to different moods. Players can seek quick fun or deep focus depending on time and energy. This adaptability supports long term engagement. Conclusion Wordle Unlimited offers an engaging and flexible word puzzle experience that appeals to a wide audience. Simple rules, unlimited rounds, and cognitive benefits create a balanced mix of entertainment and mental exercise. Customization options and social sharing further enhance appeal.

1 0

Move vlr code from osmo-msc into a own library
by Alexander 'lynxis' Couzens 25 Dec '25

25 Dec '25

Hi, a couple month ago I proposed to make the VLR code of the osmo-msc independent of the osmo-msc and create a new library called libosmo-vlr. Later use the libosmo-vlr code to integrate it into osmo-sgsn. But after take more time of this approach, I'm not sure if it is a very good idea to guarantee high stability of libosmo-vlr as we do for other osmocom libraries. Because the code is heavily integrated with both daemon and some code path are quite complex and partly not fully understood. I would rather guarantee runtime stability within a library version, but not at build time. The strategy would be increasing the library major version more often. Any thoughts? Best, lynxis PS. The current concept (because of time pressure) is to keep 2 copies of libosmo-vlr in the code base of osmo-msc and osmo-sgsn and to move it later out of it into an own library.

4 3

Video Recordings of OsmoCon 2017
by Harald Welte 22 Dec '25

22 Dec '25

Hi all, the Osmocom Conference 2017 last week was an overwhelming success. We received lots of positive feedback from all sides. Thanks to all the speakers, to the attendees as well as to the anonymous sponsor of the travel grant funds. It is my great pleasure that due to the great support by C3VOC (The CCC Video Operation Center), we have full recordings of all talks given at OsmoCon 2017. You can find the videos on the C3VOC site at https://media.ccc.de/search/?q=osmocon They are also linked individually from the OsmoCon 2017 homepage at https://osmocom.org/projects/osmo-dev-con/wiki/OsmoCon2017 I hope the video recordings will be of help for everyone who could not make it to the event in person. We will also be collecting the slides and put them up on the wiki during the next few days. Please don't hesitate to raise any feedback and/or questions. Technical feedback/questions regarding Osmocom software / projects should be addressed to the appropriate mailing lists, such as openbsc(a)lists.osmocom.org. Feedback to the organizers should be sent to osmocon2017(a)sysmocom.de. Looking forward to the next OsmoCon, which we'll expect to be spanning ore than just a single day. 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)

2 1

Managing Complicated Laws in BSC Implementations
by Fennellmarian018＠gmail.com 21 Dec '25

21 Dec '25

The complexities of Base Station Controller (BSC) integration in open-source mobile networks have presented me with a number of overlapping areas pertaining to telecommunications legislation and regulatory compliance. In order to better comprehend how international legal standards affect open BSC installations in various jurisdictions, this intersection has unanticipatedly prompted me to seek [url=https://dissertationwritinghelp.uk/law-dissertation-help/]law dissertation help[/url]. I would love to hear from anyone else who has studied legal issues in their OpenBSC-related academic or practical work, as well as suggest some books.

3 2

How to Play and Experience Heardle: A Musical Challenge
by subtle.carp.skco＠protectsmail.net 19 Dec '25

19 Dec '25

Are you ready to put your music knowledge to the test? If you love games that challenge your memory and quick thinking, you’ll enjoy Heardle. This addictive game invites players to guess a song based on short audio clips, making it a delightful experience for music lovers and casual gamers alike. Either alone or with friends, Heardle can provide a fun and engaging way to connect through music. https://heardlefree.com/ Gameplay The aim of Heardle is simple: guess the song title using limited audio clues. When you begin, the game plays an initial snippet of a song—typically just a few seconds long. From there, players have six attempts to guess the correct title. Each incorrect guess prompts an additional segment of the song to be revealed, gradually giving you a better chance at making your correct guess. To start playing, visit Heardle, where you’ll find a user-friendly interface. Upon loading, you will be greeted with a "Play" button to kick off the challenge. Once you’ve made your guesses, the game provides immediate feedback, telling you whether your guess was correct and, if not, allowing you to try again until you either guess the song or run out of attempts. Heardle has a different song each day, keeping the experience fresh. There’s no way to repeat a level, which means every day offers a new challenge and a new chance to flex those musical muscles. Tips for Playing Know Your Genres: If you have a favorite genre of music, use that to your advantage! Often, the daily song will belong to a familiar genre, so leverage your own taste to narrow down your guesses. Pay Attention to Context: Sometimes the first snippet might give away an artist or specific musical characteristic—like a distinctive guitar riff or vocal style. Listen closely and let those nuances guide your guesses. Use a Process of Elimination: If you’re unsure but have a few songs in mind, start guessing songs you’re relatively sure of. As you hear more of the song, you can refine your guesses based on the additional snippets. Play with Friends: Heardle can be even more fun when played with friends. Compete to see who can guess the song first or who can guess it in the least attempts. This also adds a social aspect to your gameplay, making it a shared challenge. Practice Regularly: Like any skill, getting better at Heardle takes practice. The more you play, the more familiar you become with popular tracks, artists, and styles, enabling you to make quicker guesses down the road. Conclusion Heardle is not just an entertaining game; it’s also a fantastic way to engage with music on a daily basis. Whether you're a casual listener or a seasoned aficionado, the thrill of uncovering a song you love creates an exciting experience each day. With its engaging format and user-friendly interface, Heardle is a must-try for anyone looking to challenge their musical knowledge. So grab your headphones, gather your friends, and see who can guess the daily hit first! Remember to enjoy the process and celebrate those musical memories, one note at a time. Happy playing!

1 0

Glamified UK Olaplex No.4 Bond Maintenance Shampoo 1 L – Transform Your Hair from Root to Tip
by vemew27700＠datehype.com 19 Dec '25

19 Dec '25

Healthy, strong, and radiant hair starts with the right care, and Olaplex No.4 Bond Maintenance Shampoo 1 L is your ultimate solution. Available at Glamified UK, this revolutionary shampoo is designed to repair, strengthen, and protect your hair bonds, ensuring your locks look and feel their absolute best every day. Unlike ordinary shampoos, Olaplex No.4 Bond Maintenance Shampoo 1 L works on a molecular level to restore damaged and fragile hair. Whether your hair is color-treated, heat-styled, chemically processed, or naturally prone to breakage, this shampoo penetrates deep into the hair shaft to rebuild broken bonds. The result is hair that is not only healthier but also more resilient, manageable, and naturally shiny. Why Choose Olaplex No.4 Bond Maintenance Shampoo 1 L? Repairs and Strengthens Hair The star of this formula is Olaplex’s patented bond-building technology. Each wash actively repairs damaged disulfide bonds within the hair, reducing breakage and split ends. Over time, your hair becomes noticeably stronger, softer, and smoother. Safe for All Hair Types Whether you have fine, thick, curly, or straight hair, Olaplex No.4 Bond Maintenance Shampoo 1 L is suitable for everyone. It is free from sulfates, parabens, and harsh chemicals, making it gentle enough for daily use while still delivering salon-quality results. Enhances Hair Health and Shine Beyond repairing damage, this shampoo nourishes the scalp and hair follicles, promoting healthy growth and natural shine. Each strand is left silky and full of life, reflecting light for a glossy, vibrant finish. Economical and Long-Lasting With a generous 1 L size, this shampoo is perfect for both personal use and professional settings. A little goes a long way, making it an excellent investment for those seeking consistent hair care without constant repurchasing. Easy to Incorporate into Your Routine Using Olaplex No.4 Bond Maintenance Shampoo 1 L is simple. Apply a small amount to wet hair, massage into a rich lather, and rinse thoroughly. For optimal results, follow with Olaplex No.5 Bond Maintenance Conditioner to lock in moisture and further enhance strength. Customer Satisfaction Guaranteed At https://glamified.co.uk/, we are committed to offering authentic Olaplex products that transform hair care routines. Customers rave about the immediate improvement in hair texture and overall health after just a few washes. Whether you’re recovering from chemical treatments, heat styling, or environmental damage, Olaplex No.4 Bond Maintenance Shampoo 1 L ensures your hair gets the professional-grade care it deserves. Conclusion Say goodbye to brittle, lifeless hair and hello to strong, shiny, and beautifully nourished locks with Olaplex No.4 Bond Maintenance Shampoo 1 L. Glamified UK makes it easy to access this salon-quality treatment at home, giving your hair the love it needs every day. Transform your hair care routine and experience the magic of Olaplex today! https://glamified.co.uk/product/no-4-bond-maintenance-shampoo-liter/

1 0

Casual Chats on Picking Paper Ideas
by naomismith11399＠gmail.com 17 Dec '25

17 Dec '25

Lately, forum discussions around research paper topics feel more relatable than polished. People openly talk about how choosing the right angle matters more than chasing something complicated. Many start with curiosity, then refine ideas through reading, discussions, and everyday observations. The real pressure comes later, when those thoughts need to turn into clear writing within tight timelines. That’s when writing help naturally enters the conversation. Some members mention trying a writing service or assignment writing help to organize ideas without losing their own voice. MyAssignmentHelp- https://myassignmenthelp.com/blog/research-paper-topics/ comes up occasionally, usually shared as part of someone’s routine rather than a strong recommendation. What keeps these threads engaging is the honesty. Talking openly about confusion, revisions, and deadlines makes the process feel less overwhelming. In the end, research paper topics aren’t just about depth or originality, but about clarity, balance, and staying consistent until the final draft feels complete and confident.

1 0

Some phones cant receive SMS
by Henry Caga 16 Dec '25

16 Dec '25

Hi, I would like to ask for help regarding my osmo-bsc setup. I have 2 problems as of now. 1) My setup is working fine on my phones, i can send and receive sms. However, on some phones, i can only send sms or call. But i cannot receive sms. I attached the sample logs from the phone that can receive sms and phone that cannot receive sms. I also included my config files. 2) i have a GPSDO TCXO and i wanted to use the maximum setting like setting up the 10mhz reference. what should i set or configure at the config files in order to set it? 3) Is there a way to improve my setup? Im using 50w PA and are there any settings that i have missed? Thank you Henry Phone that can receive sms ========= 20220226175408907 DRLL <0000> chan_alloc.c:240 (bts=0) channel load average is 0.00% 20220226175408907 DRLL <0000> chan_alloc.c:253 (bts=0) T3122 wait indicator set to 10 seconds 20220226175409767 DNM <0004> abis_nm.c:345 BTS 0 reported connected PCU version 0.8.0.178-b75c2 20220226175414767 DNM <0004> abis_nm.c:345 BTS 0 reported connected PCU version 0.8.0.178-b75c2 20220226175415439 DLSCCP <0020> sccp_user.c:175 Delivering N-UNITDATA.indication to SCCP User 'msc-0' 20220226175415439 DMSC <0007> osmo_bsc_sigtran.c:231 N-UNITDATA.ind(00 16 52 08 08 59 51 20 20 02 00 04 21 09 04 23 1d 63 44 1a 03 05 03 f4 ) 20220226175415439 DMSC <0007> osmo_bsc_bssap.c:1259 Rx MSC UDT: 00 16 52 08 08 59 51 20 20 02 00 04 21 09 04 23 1d 63 44 1a 03 05 03 f4 20220226175415439 DMSC <0007> osmo_bsc_bssap.c:1116 Rx MSC UDT BSSMAP PAGING 20220226175415439 DMSC <0007> osmo_bsc_bssap.c:131 Paging request from MSC BTS: 0 IMSI: '515020220004012' TMSI: '0x231d6344/589128516' LAC: 0x3f4 20220226175416335 DRSL <0003> abis_rsl.c:1383 (bts=0) CHAN RQD: reason: answer to paging (ra=0x9e, neci=0x01, chreq_reason=0x01) 20220226175416335 DRLL <0000> lchan_select.c:173 (bts=0) lchan_select_by_type(SDCCH) 20220226175416335 DRLL <0000> lchan_select.c:87 looking for lchan CCCH+SDCCH4: (bts=0,trx=0,ts=0,pchan=CCCH+SDCCH4,state=UNUSED) ss=0 is available 20220226175416335 DRSL <0003> abis_rsl.c:476 (bts=0,trx=0,ts=0,pchan=CCCH+SDCCH4,state=IN_USE) Tx RSL Channel Activate with act_type=INITIAL 20220226175416662 DMSC <0007> fsm.c:461 SUBSCR_CONN[0x558560323460]{INIT}: Allocated 20220226175416662 DMSC <0007> gsm_08_08.c:489 Tx MSC COMPL L3 20220226175416662 DRSL <0003> gsm_08_08.c:232 RR GSM48_MT_RR_PAG_RESP: TMSI-0x231D6344 matches earlier Paging from msc 0 20220226175416662 DMSC <0007> osmo_bsc_sigtran.c:308 Initializing resources for new SCCP connection to MSC 0: RI=SSN_PC,PC=0.23.1,SSN=BSSAP... 20220226175416663 DMSC <0007> gsm_08_08.c:532 SUBSCR_CONN(msc0-conn4294967295_IMSI515020220004012)[0x558560323460]{INIT}: Received Event MO-CONNECT.req 20220226175416663 DMSC <0007> osmo_bsc_sigtran.c:350 Allocated new connection id: 7 20220226175416663 DMSC <0007> osmo_bsc_sigtran.c:354 Opening new SCCP connection (id=7) to MSC: RI=SSN_PC,PC=0.23.1,SSN=BSSAP 20220226175416663 DLSCCP <0020> sccp_scoc.c:1729 Received SCCP User Primitive (N-CONNECT.request) 20220226175416663 DLSCCP <0020> fsm.c:461 SCCP-SCOC(7)[0x55856030ca50]{IDLE}: Allocated 20220226175416663 DLSCCP <0020> sccp_scoc.c:1769 SCCP-SCOC(7)[0x55856030ca50]{IDLE}: Received Event N-CONNECT.req 20220226175416663 DLSCCP <0020> sccp_scoc.c:830 SCCP-SCOC(7)[0x55856030ca50]{IDLE}: state_chg to CONN_PEND_OUT 20220226175416663 DMSC <0007> bsc_subscr_conn_fsm.c:286 SUBSCR_CONN(msc0-conn4294967295_IMSI515020220004012)[0x558560323460]{INIT}: state_chg to WAIT_CC 20220226175416664 DLSCCP <0020> sccp_scoc.c:1662 Received CO:COAK for local reference 7 20220226175416664 DLSCCP <0020> sccp_scoc.c:1695 SCCP-SCOC(7)[0x55856030ca50]{CONN_PEND_OUT}: Received Event RCOC-CONNECT_CONFIRM.ind 20220226175416664 DLSCCP <0020> sccp_scoc.c:981 SCCP-SCOC(7)[0x55856030ca50]{CONN_PEND_OUT}: state_chg to ACTIVE 20220226175416664 DLSCCP <0020> sccp_user.c:175 Delivering N-CONNECT.confirm to SCCP User 'msc-0' 20220226175416664 DMSC <0007> osmo_bsc_sigtran.c:244 N-CONNECT.cnf(7, ) 20220226175416664 DMSC <0007> osmo_bsc_sigtran.c:247 SUBSCR_CONN(msc0-conn7_IMSI515020220004012)[0x558560323460]{WAIT_CC}: Received Event MO-CONNECT.cfm 20220226175416664 DMSC <0007> bsc_subscr_conn_fsm.c:354 SUBSCR_CONN(msc0-conn7_IMSI515020220004012)[0x558560323460]{WAIT_CC}: state_chg to ACTIVE 20220226175416664 DLSCCP <0020> sccp_scoc.c:1662 Received CO:CODT for local reference 7 20220226175416664 DLSCCP <0020> sccp_scoc.c:1695 SCCP-SCOC(7)[0x55856030ca50]{ACTIVE}: Received Event RCOC-DT1.ind 20220226175416664 DLSCCP <0020> sccp_user.c:175 Delivering N-DATA.indication to SCCP User 'msc-0' 20220226175416664 DMSC <0007> osmo_bsc_sigtran.c:261 N-DATA.ind(7, 00 0b 2f 08 08 59 51 20 20 02 00 04 21 ) 20220226175416664 DMSC <0007> a_reset.c:227 A-RESET(msc-0)[0x55856030c700]{CONN}: Received Event EV_N_CONNECT 20220226175416664 DMSC <0007> osmo_bsc_bssap.c:1153 Rx MSC DT1 BSSMAP COMMON ID 20220226175416664 DMSC <0007> osmo_bsc_bssap.c:1099 SUBSCR_CONN(msc0-conn7_IMSI515020220004012)[0x558560323460]{ACTIVE}: Received Event COMMON_ID.ind 20220226175416664 DLSCCP <0020> sccp_scoc.c:1662 Received CO:CODT for local reference 7 20220226175416664 DLSCCP <0020> sccp_scoc.c:1695 SCCP-SCOC(7)[0x55856030ca50]{ACTIVE}: Received Event RCOC-DT1.ind 20220226175416664 DLSCCP <0020> sccp_user.c:175 Delivering N-DATA.indication to SCCP User 'msc-0' 20220226175416664 DMSC <0007> osmo_bsc_sigtran.c:261 N-DATA.ind(7, 01 03 26 09 01 23 01 00 07 91 44 77 58 10 06 50 00 17 20 06 d1 32 99 0c 00 00 22 20 62 71 45 51 23 07 f4 f2 9c 9e 76 9f 01 ) 20220226175416664 DMSC <0007> a_reset.c:227 A-RESET(msc-0)[0x55856030c700]{CONN}: Received Event EV_N_CONNECT 20220226175416664 DMSC <0007> osmo_bsc_bssap.c:1208 Rx MSC DTAP: 01 03 26 09 01 23 01 00 07 91 44 77 58 10 06 50 00 17 20 06 d1 32 99 0c 00 00 22 20 62 71 45 51 23 07 f4 f2 9c 9e 76 9f 01 20220226175416664 DMSC <0007> osmo_bsc_bssap.c:1232 Rx MSC DTAP, SAPI: 3 CHAN: 0 20220226175416664 DMSC <0007> osmo_bsc_bssap.c:1249 SUBSCR_CONN(msc0-conn7_IMSI515020220004012)[0x558560323460]{ACTIVE}: Received Event MT_DTAP 20220226175416664 DRLL <0000> abis_rsl.c:833 (bts=0,trx=0,ts=0,ss=0) RSL RLL ESTABLISH REQ (link_id=0x03) 20220226175416757 DRSL <0003> abis_rsl.c:1082 (bts=0,trx=0,ts=0,ss=0): meas_rep_count++=1 meas_rep_last_seen_nr=0 20220226175416907 DRLL <0000> chan_alloc.c:240 (bts=0) channel load average is 0.20% 20220226175416907 DRLL <0000> chan_alloc.c:253 (bts=0) T3122 wait indicator set to 10 seconds 20220226175417227 DRSL <0003> abis_rsl.c:1082 (bts=0,trx=0,ts=0,ss=0): meas_rep_count++=2 meas_rep_last_seen_nr=1 20220226175417839 DMSC <0007> gsm_08_08.c:548 Tx MSC DTAP LINK_ID=0x03 20220226175417839 DMSC <0007> gsm_08_08.c:554 SUBSCR_CONN(msc0-conn7_IMSI515020220004012)[0x558560323460]{ACTIVE}: Received Event MO_DTAP 20220226175417839 DMSC <0007> osmo_bsc_sigtran.c:394 Tx MSC: DTAP 20220226175417839 DMSC <0007> osmo_bsc_sigtran.c:418 Sending connection (id=7) oriented data to MSC: RI=SSN_PC,PC=0.23.1,SSN=BSSAP (01 03 02 89 04 ) 20220226175417839 DLSCCP <0020> sccp_scoc.c:1729 Received SCCP User Primitive (N-DATA.request) 20220226175417839 DLSCCP <0020> sccp_scoc.c:1769 SCCP-SCOC(7)[0x55856030ca50]{ACTIVE}: Received Event N-DATA.req 20220226175418075 DMSC <0007> gsm_08_08.c:548 Tx MSC DTAP LINK_ID=0x03 20220226175418075 DMSC <0007> gsm_08_08.c:554 SUBSCR_CONN(msc0-conn7_IMSI515020220004012)[0x558560323460]{ACTIVE}: Received Event MO_DTAP 20220226175418075 DMSC <0007> osmo_bsc_sigtran.c:394 Tx MSC: DTAP 20220226175418076 DMSC <0007> osmo_bsc_sigtran.c:418 Sending connection (id=7) oriented data to MSC: RI=SSN_PC,PC=0.23.1,SSN=BSSAP (01 03 09 89 01 06 02 00 41 02 00 00 ) 20220226175418076 DLSCCP <0020> sccp_scoc.c:1729 Received SCCP User Primitive (N-DATA.request) 20220226175418076 DLSCCP <0020> sccp_scoc.c:1769 SCCP-SCOC(7)[0x55856030ca50]{ACTIVE}: Received Event N-DATA.req 20220226175418085 DLSCCP <0020> sccp_scoc.c:1662 Received CO:CODT for local reference 7 20220226175418085 DLSCCP <0020> sccp_scoc.c:1695 SCCP-SCOC(7)[0x55856030ca50]{ACTIVE}: Received Event RCOC-DT1.ind 20220226175418085 DLSCCP <0020> sccp_user.c:175 Delivering N-DATA.indication to SCCP User 'msc-0' 20220226175418085 DMSC <0007> osmo_bsc_sigtran.c:261 N-DATA.ind(7, 01 03 02 09 04 ) 20220226175418085 DMSC <0007> a_reset.c:227 A-RESET(msc-0)[0x55856030c700]{CONN}: Received Event EV_N_CONNECT 20220226175418085 DMSC <0007> osmo_bsc_bssap.c:1208 Rx MSC DTAP: 01 03 02 09 04 20220226175418085 DMSC <0007> osmo_bsc_bssap.c:1232 Rx MSC DTAP, SAPI: 3 CHAN: 0 20220226175418085 DMSC <0007> osmo_bsc_bssap.c:1249 SUBSCR_CONN(msc0-conn7_IMSI515020220004012)[0x558560323460]{ACTIVE}: Received Event MT_DTAP 20220226175418085 DLSCCP <0020> sccp_scoc.c:1662 Received CO:CODT for local reference 7 20220226175418085 DLSCCP <0020> sccp_scoc.c:1695 SCCP-SCOC(7)[0x55856030ca50]{ACTIVE}: Received Event RCOC-DT1.ind 20220226175418085 DLSCCP <0020> sccp_user.c:175 Delivering N-DATA.indication to SCCP User 'msc-0' 20220226175418085 DMSC <0007> osmo_bsc_sigtran.c:261 N-DATA.ind(7, 00 04 20 04 01 09 ) 20220226175418085 DMSC <0007> a_reset.c:227 A-RESET(msc-0)[0x55856030c700]{CONN}: Received Event EV_N_CONNECT 20220226175418085 DMSC <0007> osmo_bsc_bssap.c:1153 Rx MSC DT1 BSSMAP CLEAR COMMAND 20220226175418085 DMSC <0007> osmo_bsc_bssap.c:473 SUBSCR_CONN(msc0-conn7_IMSI515020220004012)[0x558560323460]{ACTIVE}: Received Event CLEAR_CMD 20220226175418085 DMSC <0007> bsc_subscr_conn_fsm.c:774 SUBSCR_CONN(msc0-conn7_IMSI515020220004012)[0x558560323460]{ACTIVE}: state_chg to CLEARING 20220226175418085 DMSC <0007> bsc_subscr_conn_fsm.c:775 SUBSCR_CONN(msc0-conn7_IMSI515020220004012)[0x558560323460]{CLEARING}: Releasing all lchans (if any) after BSSMAP Clear Command 20220226175418085 DMSC <0007> lchan_fsm.c:1458 SUBSCR_CONN(msc0-conn7_IMSI515020220004012)[0x558560323460]{CLEARING}: lchan lchan(0-0-0-CCCH_SDCCH4-0)[0x55856030cee0] detaches from conn 20220226175418085 DRR <0002> gsm_04_08_rr.c:323 Sending Channel Release: Chan: Number: 0 Type: 1 RR-Cause: 0x0 'Normal event' 20220226175418085 DRSL <0003> abis_rsl.c:644 (bts=0,trx=0,ts=0,ss=0) DEACTivate SACCH CMD 20220226175418085 DRLL <0000> abis_rsl.c:857 (bts=0,trx=0,ts=0,ss=0) RSL RLL RELEASE REQ (link_id=0x03, reason=1) 20220226175418085 DMSC <0007> osmo_bsc_sigtran.c:390 Tx MSC: BSSMAP: CLEAR COMPLETE 20220226175418085 DMSC <0007> osmo_bsc_sigtran.c:418 Sending connection (id=7) oriented data to MSC: RI=SSN_PC,PC=0.23.1,SSN=BSSAP (00 01 21 ) 20220226175418085 DLSCCP <0020> sccp_scoc.c:1729 Received SCCP User Primitive (N-DATA.request) 20220226175418085 DLSCCP <0020> sccp_scoc.c:1769 SCCP-SCOC(7)[0x55856030ca50]{ACTIVE}: Received Event N-DATA.req 20220226175418085 DLSCCP <0020> sccp_scoc.c:1662 Received CO:RELRE for local reference 7 20220226175418085 DLSCCP <0020> sccp_scoc.c:1695 SCCP-SCOC(7)[0x55856030ca50]{ACTIVE}: Received Event RCOC-RELEASED.ind 20220226175418085 DLSCCP <0020> sccp_user.c:175 Delivering N-DISCONNECT.indication to SCCP User 'msc-0' 20220226175418085 DMSC <0007> osmo_bsc_sigtran.c:274 N-DISCONNECT.ind(7, , cause=768) 20220226175418085 DMSC <0007> osmo_bsc_sigtran.c:281 SUBSCR_CONN(msc0-conn7_IMSI515020220004012)[0x558560323460]{CLEARING}: Received Event DISCONNET.ind 20220226175418085 DMSC <0007> bsc_subscr_conn_fsm.c:791 SUBSCR_CONN(msc0-conn7_IMSI515020220004012)[0x558560323460]{CLEARING}: Terminating (cause = OSMO_FSM_TERM_REGULAR) 20220226175418085 DMSC <0007> bsc_subscr_conn_fsm.c:862 SUBSCR_CONN(msc0-conn7_IMSI515020220004012)[0x558560323460]{CLEARING}: FSM instance already terminating, not dispatching event LCLS_FAIL 20220226175418085 DMSC <0007> bsc_subscr_conn_fsm.c:866 SUBSCR_CONN(msc0-conn7_IMSI515020220004012)[0x558560323460]{CLEARING}: Releasing all lchans (if any) because this conn is terminating 20220226175418085 DMSC <0007> bsc_subscr_conn_fsm.c:845 SUBSCR_CONN(msc0-conn7_IMSI515020220004012)[0x558560323460]{CLEARING}: Putting bsc_subscr 20220226175418085 DMSC <0007> bsc_subscr_conn_fsm.c:791 SUBSCR_CONN(msc0-conn7_IMSI515020220004012)[0x558560323460]{CLEARING}: Freeing instance 20220226175418085 DMSC <0007> fsm.c:573 SUBSCR_CONN(msc0-conn7_IMSI515020220004012)[0x558560323460]{CLEARING}: Deallocated 20220226175418085 DLSCCP <0020> sccp_scoc.c:1070 SCCP-SCOC(7)[0x55856030ca50]{ACTIVE}: state_chg to IDLE 20220226175418085 DLSCCP <0020> sccp_scoc.c:517 SCCP-SCOC(7)[0x55856030ca50]{IDLE}: Terminating (cause = OSMO_FSM_TERM_REQUEST) 20220226175418085 DLSCCP <0020> sccp_scoc.c:517 SCCP-SCOC(7)[0x55856030ca50]{IDLE}: Freeing instance 20220226175418085 DLSCCP <0020> fsm.c:573 SCCP-SCOC(7)[0x55856030ca50]{IDLE}: Deallocated 20220226175419767 DNM <0004> abis_nm.c:345 BTS 0 reported connected PCU version 0.8.0.178-b75c2 20220226175424767 DNM <0004> abis_nm.c:345 BTS 0 reported connected PCU version 0.8.0.178-b75c2 20220226175424910 DRLL <0000> chan_alloc.c:240 (bts=0) channel load average is 3.03% 20220226175424910 DRLL <0000> chan_alloc.c:253 (bts=0) T3122 wait indicator set to 10 seconds ========= Phone that doesnt receive sms ========== 20220226173512464 DNM <0004> abis_nm.c:345 BTS 0 reported connected PCU version 0.8.0.178-b75c2 20220226173514434 DRLL <0000> chan_alloc.c:240 (bts=0) channel load average is 0.00% 20220226173514434 DRLL <0000> chan_alloc.c:253 (bts=0) T3122 wait indicator set to 10 seconds 20220226173517464 DNM <0004> abis_nm.c:345 BTS 0 reported connected PCU version 0.8.0.178-b75c2 20220226173519748 DLSCCP <0020> sccp_user.c:175 Delivering N-UNITDATA.indication to SCCP User 'msc-0' 20220226173519748 DMSC <0007> osmo_bsc_sigtran.c:231 N-UNITDATA.ind(00 16 52 08 08 59 51 20 11 27 23 70 04 09 04 38 2a bc 18 1a 03 05 03 f4 ) 20220226173519748 DMSC <0007> osmo_bsc_bssap.c:1259 Rx MSC UDT: 00 16 52 08 08 59 51 20 11 27 23 70 04 09 04 38 2a bc 18 1a 03 05 03 f4 20220226173519748 DMSC <0007> osmo_bsc_bssap.c:1116 Rx MSC UDT BSSMAP PAGING 20220226173519748 DMSC <0007> osmo_bsc_bssap.c:131 Paging request from MSC BTS: 0 IMSI: '515021172320740' TMSI: '0x382abc18/942324760' LAC: 0x3f4 20220226173522006 DRSL <0003> abis_rsl.c:1383 (bts=0) CHAN RQD: reason: answer to paging (ra=0x87, neci=0x01, chreq_reason=0x01) 20220226173522006 DRLL <0000> lchan_select.c:173 (bts=0) lchan_select_by_type(SDCCH) 20220226173522006 DRLL <0000> lchan_select.c:87 looking for lchan CCCH+SDCCH4: (bts=0,trx=0,ts=0,pchan=CCCH+SDCCH4,state=UNUSED) ss=0 is available 20220226173522006 DRSL <0003> abis_rsl.c:476 (bts=0,trx=0,ts=0,pchan=CCCH+SDCCH4,state=IN_USE) Tx RSL Channel Activate with act_type=INITIAL 20220226173522295 DMSC <0007> fsm.c:461 SUBSCR_CONN[0x56450d5e3f80]{INIT}: Allocated 20220226173522295 DMSC <0007> gsm_08_08.c:489 Tx MSC COMPL L3 20220226173522295 DRSL <0003> gsm_08_08.c:232 RR GSM48_MT_RR_PAG_RESP: TMSI-0x382ABC18 matches earlier Paging from msc 0 20220226173522295 DMSC <0007> osmo_bsc_sigtran.c:308 Initializing resources for new SCCP connection to MSC 0: RI=SSN_PC,PC=0.23.1,SSN=BSSAP... 20220226173522295 DMSC <0007> gsm_08_08.c:532 SUBSCR_CONN(msc0-conn4294967295_IMSI515021172320740)[0x56450d5e3f80]{INIT}: Received Event MO-CONNECT.req 20220226173522295 DMSC <0007> osmo_bsc_sigtran.c:350 Allocated new connection id: 5 20220226173522295 DMSC <0007> osmo_bsc_sigtran.c:354 Opening new SCCP connection (id=5) to MSC: RI=SSN_PC,PC=0.23.1,SSN=BSSAP 20220226173522295 DLSCCP <0020> sccp_scoc.c:1729 Received SCCP User Primitive (N-CONNECT.request) 20220226173522295 DLSCCP <0020> fsm.c:461 SCCP-SCOC(5)[0x56450d5e2160]{IDLE}: Allocated 20220226173522295 DLSCCP <0020> sccp_scoc.c:1769 SCCP-SCOC(5)[0x56450d5e2160]{IDLE}: Received Event N-CONNECT.req 20220226173522295 DLSCCP <0020> sccp_scoc.c:830 SCCP-SCOC(5)[0x56450d5e2160]{IDLE}: state_chg to CONN_PEND_OUT 20220226173522295 DMSC <0007> bsc_subscr_conn_fsm.c:286 SUBSCR_CONN(msc0-conn4294967295_IMSI515021172320740)[0x56450d5e3f80]{INIT}: state_chg to WAIT_CC 20220226173522296 DLSCCP <0020> sccp_scoc.c:1662 Received CO:COAK for local reference 5 20220226173522296 DLSCCP <0020> sccp_scoc.c:1695 SCCP-SCOC(5)[0x56450d5e2160]{CONN_PEND_OUT}: Received Event RCOC-CONNECT_CONFIRM.ind 20220226173522296 DLSCCP <0020> sccp_scoc.c:981 SCCP-SCOC(5)[0x56450d5e2160]{CONN_PEND_OUT}: state_chg to ACTIVE 20220226173522296 DLSCCP <0020> sccp_user.c:175 Delivering N-CONNECT.confirm to SCCP User 'msc-0' 20220226173522296 DMSC <0007> osmo_bsc_sigtran.c:244 N-CONNECT.cnf(5, ) 20220226173522296 DMSC <0007> osmo_bsc_sigtran.c:247 SUBSCR_CONN(msc0-conn5_IMSI515021172320740)[0x56450d5e3f80]{WAIT_CC}: Received Event MO-CONNECT.cfm 20220226173522296 DMSC <0007> bsc_subscr_conn_fsm.c:354 SUBSCR_CONN(msc0-conn5_IMSI515021172320740)[0x56450d5e3f80]{WAIT_CC}: state_chg to ACTIVE 20220226173522296 DLSCCP <0020> sccp_scoc.c:1662 Received CO:CODT for local reference 5 20220226173522296 DLSCCP <0020> sccp_scoc.c:1695 SCCP-SCOC(5)[0x56450d5e2160]{ACTIVE}: Received Event RCOC-DT1.ind 20220226173522296 DLSCCP <0020> sccp_user.c:175 Delivering N-DATA.indication to SCCP User 'msc-0' 20220226173522296 DMSC <0007> osmo_bsc_sigtran.c:261 N-DATA.ind(5, 00 0b 2f 08 08 59 51 20 11 27 23 70 04 ) 20220226173522296 DMSC <0007> a_reset.c:227 A-RESET(msc-0)[0x56450d5d3700]{CONN}: Received Event EV_N_CONNECT 20220226173522296 DMSC <0007> osmo_bsc_bssap.c:1153 Rx MSC DT1 BSSMAP COMMON ID 20220226173522296 DMSC <0007> osmo_bsc_bssap.c:1099 SUBSCR_CONN(msc0-conn5_IMSI515021172320740)[0x56450d5e3f80]{ACTIVE}: Received Event COMMON_ID.ind 20220226173522296 DLSCCP <0020> sccp_scoc.c:1662 Received CO:CODT for local reference 5 20220226173522296 DLSCCP <0020> sccp_scoc.c:1695 SCCP-SCOC(5)[0x56450d5e2160]{ACTIVE}: Received Event RCOC-DT1.ind 20220226173522296 DLSCCP <0020> sccp_user.c:175 Delivering N-DATA.indication to SCCP User 'msc-0' 20220226173522296 DMSC <0007> osmo_bsc_sigtran.c:261 N-DATA.ind(5, 01 03 28 09 01 25 01 00 07 91 44 77 58 10 06 50 00 19 20 0c 91 36 39 71 82 34 93 00 00 22 20 62 71 53 91 23 06 f4 f2 9c 0e 92 01 ) 20220226173522296 DMSC <0007> a_reset.c:227 A-RESET(msc-0)[0x56450d5d3700]{CONN}: Received Event EV_N_CONNECT 20220226173522296 DMSC <0007> osmo_bsc_bssap.c:1208 Rx MSC DTAP: 01 03 28 09 01 25 01 00 07 91 44 77 58 10 06 50 00 19 20 0c 91 36 39 71 82 34 93 00 00 22 20 62 71 53 91 23 06 f4 f2 9c 0e 92 01 20220226173522296 DMSC <0007> osmo_bsc_bssap.c:1232 Rx MSC DTAP, SAPI: 3 CHAN: 0 20220226173522296 DMSC <0007> osmo_bsc_bssap.c:1249 SUBSCR_CONN(msc0-conn5_IMSI515021172320740)[0x56450d5e3f80]{ACTIVE}: Received Event MT_DTAP 20220226173522296 DRLL <0000> abis_rsl.c:833 (bts=0,trx=0,ts=0,ss=0) RSL RLL ESTABLISH REQ (link_id=0x03) 20220226173522439 DRLL <0000> chan_alloc.c:240 (bts=0) channel load average is 0.20% 20220226173522439 DRLL <0000> chan_alloc.c:253 (bts=0) T3122 wait indicator set to 10 seconds 20220226173522464 DNM <0004> abis_nm.c:345 BTS 0 reported connected PCU version 0.8.0.178-b75c2 20220226173522766 DMSC <0007> gsm_08_08.c:71 Tx MSC SAPI N REJECT DLCI=0x03 20220226173522766 DMSC <0007> gsm_08_08.c:74 SUBSCR_CONN(msc0-conn5_IMSI515021172320740)[0x56450d5e3f80]{ACTIVE}: Received Event TX_SCCP 20220226173522766 DMSC <0007> osmo_bsc_sigtran.c:390 Tx MSC: BSSMAP: SAPI N REJECT 20220226173522766 DMSC <0007> osmo_bsc_sigtran.c:418 Sending connection (id=5) oriented data to MSC: RI=SSN_PC,PC=0.23.1,SSN=BSSAP (00 06 25 18 03 04 01 25 ) 20220226173522766 DLSCCP <0020> sccp_scoc.c:1729 Received SCCP User Primitive (N-DATA.request) 20220226173522766 DLSCCP <0020> sccp_scoc.c:1769 SCCP-SCOC(5)[0x56450d5e2160]{ACTIVE}: Received Event N-DATA.req 20220226173522768 DLSCCP <0020> sccp_scoc.c:1662 Received CO:CODT for local reference 5 20220226173522768 DLSCCP <0020> sccp_scoc.c:1695 SCCP-SCOC(5)[0x56450d5e2160]{ACTIVE}: Received Event RCOC-DT1.ind 20220226173522768 DLSCCP <0020> sccp_user.c:175 Delivering N-DATA.indication to SCCP User 'msc-0' 20220226173522768 DMSC <0007> osmo_bsc_sigtran.c:261 N-DATA.ind(5, 00 04 20 04 01 09 ) 20220226173522768 DMSC <0007> a_reset.c:227 A-RESET(msc-0)[0x56450d5d3700]{CONN}: Received Event EV_N_CONNECT 20220226173522768 DMSC <0007> osmo_bsc_bssap.c:1153 Rx MSC DT1 BSSMAP CLEAR COMMAND 20220226173522768 DMSC <0007> osmo_bsc_bssap.c:473 SUBSCR_CONN(msc0-conn5_IMSI515021172320740)[0x56450d5e3f80]{ACTIVE}: Received Event CLEAR_CMD 20220226173522768 DMSC <0007> bsc_subscr_conn_fsm.c:774 SUBSCR_CONN(msc0-conn5_IMSI515021172320740)[0x56450d5e3f80]{ACTIVE}: state_chg to CLEARING 20220226173522768 DMSC <0007> bsc_subscr_conn_fsm.c:775 SUBSCR_CONN(msc0-conn5_IMSI515021172320740)[0x56450d5e3f80]{CLEARING}: Releasing all lchans (if any) after BSSMAP Clear Command 20220226173522768 DMSC <0007> lchan_fsm.c:1458 SUBSCR_CONN(msc0-conn5_IMSI515021172320740)[0x56450d5e3f80]{CLEARING}: lchan lchan(0-0-0-CCCH_SDCCH4-0)[0x56450d5e4240] detaches from conn 20220226173522768 DRR <0002> gsm_04_08_rr.c:323 Sending Channel Release: Chan: Number: 0 Type: 1 RR-Cause: 0x0 'Normal event' 20220226173522768 DRSL <0003> abis_rsl.c:644 (bts=0,trx=0,ts=0,ss=0) DEACTivate SACCH CMD 20220226173522768 DMSC <0007> osmo_bsc_sigtran.c:390 Tx MSC: BSSMAP: CLEAR COMPLETE 20220226173522768 DMSC <0007> osmo_bsc_sigtran.c:418 Sending connection (id=5) oriented data to MSC: RI=SSN_PC,PC=0.23.1,SSN=BSSAP (00 01 21 ) 20220226173522768 DLSCCP <0020> sccp_scoc.c:1729 Received SCCP User Primitive (N-DATA.request) 20220226173522768 DLSCCP <0020> sccp_scoc.c:1769 SCCP-SCOC(5)[0x56450d5e2160]{ACTIVE}: Received Event N-DATA.req 20220226173522768 DLSCCP <0020> sccp_scoc.c:1662 Received CO:RELRE for local reference 5 20220226173522768 DLSCCP <0020> sccp_scoc.c:1695 SCCP-SCOC(5)[0x56450d5e2160]{ACTIVE}: Received Event RCOC-RELEASED.ind 20220226173522768 DLSCCP <0020> sccp_user.c:175 Delivering N-DISCONNECT.indication to SCCP User 'msc-0' 20220226173522768 DMSC <0007> osmo_bsc_sigtran.c:274 N-DISCONNECT.ind(5, , cause=768) 20220226173522768 DMSC <0007> osmo_bsc_sigtran.c:281 SUBSCR_CONN(msc0-conn5_IMSI515021172320740)[0x56450d5e3f80]{CLEARING}: Received Event DISCONNET.ind 20220226173522768 DMSC <0007> bsc_subscr_conn_fsm.c:791 SUBSCR_CONN(msc0-conn5_IMSI515021172320740)[0x56450d5e3f80]{CLEARING}: Terminating (cause = OSMO_FSM_TERM_REGULAR) 20220226173522768 DMSC <0007> bsc_subscr_conn_fsm.c:862 SUBSCR_CONN(msc0-conn5_IMSI515021172320740)[0x56450d5e3f80]{CLEARING}: FSM instance already terminating, not dispatching event LCLS_FAIL 20220226173522768 DMSC <0007> bsc_subscr_conn_fsm.c:866 SUBSCR_CONN(msc0-conn5_IMSI515021172320740)[0x56450d5e3f80]{CLEARING}: Releasing all lchans (if any) because this conn is terminating 20220226173522768 DMSC <0007> bsc_subscr_conn_fsm.c:845 SUBSCR_CONN(msc0-conn5_IMSI515021172320740)[0x56450d5e3f80]{CLEARING}: Putting bsc_subscr 20220226173522768 DMSC <0007> bsc_subscr_conn_fsm.c:791 SUBSCR_CONN(msc0-conn5_IMSI515021172320740)[0x56450d5e3f80]{CLEARING}: Freeing instance 20220226173522768 DMSC <0007> fsm.c:573 SUBSCR_CONN(msc0-conn5_IMSI515021172320740)[0x56450d5e3f80]{CLEARING}: Deallocated 20220226173522768 DLSCCP <0020> sccp_scoc.c:1070 SCCP-SCOC(5)[0x56450d5e2160]{ACTIVE}: state_chg to IDLE 20220226173522768 DLSCCP <0020> sccp_scoc.c:517 SCCP-SCOC(5)[0x56450d5e2160]{IDLE}: Terminating (cause = OSMO_FSM_TERM_REQUEST) 20220226173522768 DLSCCP <0020> sccp_scoc.c:517 SCCP-SCOC(5)[0x56450d5e2160]{IDLE}: Freeing instance 20220226173522768 DLSCCP <0020> fsm.c:573 SCCP-SCOC(5)[0x56450d5e2160]{IDLE}: Deallocated ======== Osmo-bts-trx config ! ! OsmoBTS () configuration saved from vty !! ! log stderr logging color 1 logging timestamp 0 logging level rsl notice logging level oml notice logging level rll notice logging level rr notice logging level meas error logging level pag error logging level l1c error logging level l1p error logging level dsp error logging level abis error logging level loop debug ! line vty no login ! phy 0 instance 0 !COMMENT HERE FOR DEFAULT JOJO osmotrx rx-gain 50 osmotrx tx-attenuation 0 !osmotrx rx-gain 10 !osmotrx tx-attenuation oml !osmotrx maxdly 20 osmotrx ip local 127.0.0.1 osmotrx ip remote 127.0.0.1 bts 0 band 900 ipa unit-id 1012 0 oml remote-ip 127.0.0.1 gsmtap-sapi ccch gsmtap-sapi pdtch !ADDED FOR TEST JOJO gsmtap-sapi bcch gsmtap-sapi rach gsmtap-sapi agch gsmtap-sapi sdcch gsmtap-sapi sacch uplink-power-target -110 trx 0 !ms-power-control osmo !power-ramp max-initial 0 dBm !power-ramp step-size 2000 dB !power-ramp step-interval 10 phy 0 instance 0 ========= Osmo-bsc config ========= ! Configuration rendered by osmo-gsm-tester log stderr logging filter all 1 logging color 1 logging print category 1 logging print extended-timestamp 1 logging level all debug line vty no login bind 127.0.0.1 ctrl bind 127.0.0.1 e1_input e1_line 0 driver ipa ipa bind 127.0.0.1 network network country code 515 mobile network code 02 encryption a5 0 neci 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 4 handover maximum distance 9999 allow-unusable-timeslots bts 0 type sysmobts band 900 cell_identity 1012 location_area_code 1012 training_sequence_code 1 base_station_id_code 1 channel-description attach 0 !ms max power 40 cell reselection hysteresis 4 rxlev access min 0 channel allocator ascending rach tx integer 9 rach max transmission 7 ip.access unit_id 1012 0 oml ip.access stream_id 255 line 0 gprs mode none no force-combined-si trx 0 rf_locked 0 arfcn 27 !nominal power 40 nominal power 80 ! to use full TRX power, set max_power_red 0 max_power_red 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 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 PDCH hopping enabled 0 msc 0 !ip.access rtp-base 25000 no bsc-welcome-text no bsc-msc-lost-text no bsc-grace-text type normal allow-emergency allow !codec-list fr1 !amr-config 12_2k forbidden !amr-config 10_2k forbidden !amr-config 7_95k forbidden !amr-config 7_40k forbidden !amr-config 6_70k forbidden !amr-config 5_90k forbidden !amr-config 5_15k forbidden !amr-config 4_75k forbidden mgw remote-ip 127.0.0.1 mgw remote-port 2427 !mgw endpoint-range 1 31 mgw local-ip 127.0.0.1 bsc mid-call-timeout 0 ========== Osmo-msc config ========== ! ! OsmoMSC configuration saved from vty ! log stderr logging filter all 1 logging color 0 logging print category 1 logging timestamp 1 logging level all everything logging level rll notice logging level cc notice logging level mm notice logging level mm debug logging level rr notice logging level pag notice logging level msc notice logging level mgcp notice logging level ho notice logging level ref notice logging level ctrl notice 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 logging level all debug line vty no login bind 127.0.0.1 ! network network country code 515 mobile network code 02 short name GLOBE long name GLOBE encryption a5 0 rrlp mode none mm info 1 timezone 8 0 msc mgw remote-ip 127.0.0.1 mgw remote-port 2427 mgw local-ip 127.0.0.1 !mgw endpoint-range 1 31 !mgw bts-base 8000 assign-tmsi cs7-instance-a 0 check-imei-rqd early !timer vlr T3212 1 ctrl bind 127.0.0.1 mncc-int default-codec tch-f fr default-codec tch-h hr hlr remote-ip 127.0.0.1 smpp local-tcp-port 2775 policy accept-all smpp-first esme bhat password bhat default-route

3 2

Brazilian Knots Salon
by Amelia Emery 15 Dec '25

15 Dec '25

If you’re searching for a natural-looking, protective style that adds length and volume without heavy tension, <a href="https://ladybsalon.com/brazilian-knot-extensions-salon/">brazilian knots salon</a> might be the answer. This salon specializes in the knot method that blends extensions seamlessly with natural hair. From consultations to flawless installs and maintenance tips, this thread explores experiences, results, pricing, and care advice.

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC December 2025