#WINDTRE
WindTre?
September 26, 2026 at 6:04 AM
WindTre, giovani e senior insieme per sviluppare nuove idee di business
September 24, 2026 at 10:31 AM
WindTre Super Fibra fisso+mobile: Wi-Fi 7 e Giga illimitati
September 22, 2026 at 1:11 PM
WindTre e convergenza fisso-mobile: Super Fibra con Wi-Fi 7, promo Amazon Prime e Wi-Fi Calling
September 17, 2026 at 8:47 AM
Qualità delle reti mobili, Vodafone al vertice. WindTre avanza sull’onda del 5G
September 9, 2026 at 2:12 PM
Repeated call attempts (~5s apart) coinciding with brief service state transition — normal signaling or worth investigating?
Hi all, I’m trying to understand a pattern captured in my Android device’s logcat (Telecom framework logs) and would appreciate input from people familiar with GSM/LTE call setup and paging behavior. **Context:** WindTre (Italy), LTE (MCC 222, MNC 88), device Motorola G75. **What I observed:** a burst of 5 incoming call attempts, same calling number, at regular ~5 second intervals. All calls were auto-rejected by a call-blocking configuration (unknown/non-contact numbers are rejected automatically on this device) — not a manual reject each time, but the standard behavior for non-contact numbers on this setup. Timestamps from logcat (Telecom `TC@` call IDs): Call | Created | Ringing | Disconnected | Reject delay | Interval from previous ---|---|---|---|---|--- TC@22 | 14:12:00.708 | 14:12:00.773 | 14:12:01.997 | ~1.29s | — TC@23 | 14:12:05.508 | 14:12:05.576 | 14:12:06.547 | ~1.04s | 4.80s TC@24 | 14:12:10.062 | 14:12:10.144 | 14:12:11.194 | ~1.13s | 4.55s TC@25 | 14:12:16.911 | 14:12:16.969 | 14:12:18.076 | ~1.17s | 6.85s TC@26 | 14:12:21.585 | 14:12:21.651 | 14:12:22.726 | ~1.14s | 4.67s All disconnects show `DisconnectCause REJECTED, ImsReasonInfo: CODE_LOCAL_CALL_DECLINE`. **Additional detail:** right after the first call’s disconnect (14:12:01.797), the log shows a brief `mVoiceRegState=OUT_OF_SERVICE`, followed within ~100ms by return to `IN_SERVICE`, with `isUsingCarrierAggregation` switching from false to true and `mCellBandwidths` going from `[20000]` to `[20000, 20000]`. **My questions:** 1. Is a ~5s regular retry interval typical of a specific dialer/PBX retry logic, or could it indicate SIP/SS7-level signaling retries (e.g. unanswered INVITE with short timeout)? 2. Is the coincidental service-state blip / CA activation likely just routine network optimization, or could it be related to the call attempts themselves (e.g. paging-triggered reconfiguration)? 3. Any suggestions on what additional data (from `dumpsys telephony.registry`, radio logs, or an app like Network Survey) would help clarify the mechanism? 4. Given that active network signaling (paging, call setup) is known to force a device to report its current cell, could a deliberate burst of repeated call attempts like this be used as a way to force more frequent location updates on a target device? Or would a single attempt already provide equivalent signaling for that purpose, making repeated attempts technically redundant for such a use case? Happy to share the full logcat excerpt if useful. Thanks in advance.
discourse.osmocom.org
August 21, 2026 at 10:09 PM
Repeated call attempts (~5s apart) coinciding with brief service state transition — normal signaling or worth investigating?
Hi all, I’m trying to understand a pattern captured in my Android device’s logcat (Telecom framework logs) and would appreciate input from people familiar with GSM/LTE call setup and paging behavior. **Context:** WindTre (Italy), LTE (MCC 222, MNC 88), device Motorola G75. **What I observed:** a burst of 5 incoming call attempts, same calling number, at regular ~5 second intervals. All calls were auto-rejected by a call-blocking configuration (unknown/non-contact numbers are rejected automatically on this device) — not a manual reject each time, but the standard behavior for non-contact numbers on this setup. Timestamps from logcat (Telecom `TC@` call IDs): Call | Created | Ringing | Disconnected | Reject delay | Interval from previous ---|---|---|---|---|--- TC@22 | 14:12:00.708 | 14:12:00.773 | 14:12:01.997 | ~1.29s | — TC@23 | 14:12:05.508 | 14:12:05.576 | 14:12:06.547 | ~1.04s | 4.80s TC@24 | 14:12:10.062 | 14:12:10.144 | 14:12:11.194 | ~1.13s | 4.55s TC@25 | 14:12:16.911 | 14:12:16.969 | 14:12:18.076 | ~1.17s | 6.85s TC@26 | 14:12:21.585 | 14:12:21.651 | 14:12:22.726 | ~1.14s | 4.67s All disconnects show `DisconnectCause REJECTED, ImsReasonInfo: CODE_LOCAL_CALL_DECLINE`. **Additional detail:** right after the first call’s disconnect (14:12:01.797), the log shows a brief `mVoiceRegState=OUT_OF_SERVICE`, followed within ~100ms by return to `IN_SERVICE`, with `isUsingCarrierAggregation` switching from false to true and `mCellBandwidths` going from `[20000]` to `[20000, 20000]`. **My questions:** 1. Is a ~5s regular retry interval typical of a specific dialer/PBX retry logic, or could it indicate SIP/SS7-level signaling retries (e.g. unanswered INVITE with short timeout)? 2. Is the coincidental service-state blip / CA activation likely just routine network optimization, or could it be related to the call attempts themselves (e.g. paging-triggered reconfiguration)? 3. Any suggestions on what additional data (from `dumpsys telephony.registry`, radio logs, or an app like Network Survey) would help clarify the mechanism? 4. Given that active network signaling (paging, call setup) is known to force a device to report its current cell, could a deliberate burst of repeated call attempts like this be used as a way to force more frequent location updates on a target device? Or would a single attempt already provide equivalent signaling for that purpose, making repeated attempts technically redundant for such a use case? Happy to share the full logcat excerpt if useful. Thanks in advance.
discourse.osmocom.org
August 17, 2026 at 4:19 AM
Repeated call attempts (~5s apart) coinciding with brief service state transition — normal signaling or worth investigating?
Hi all, I’m trying to understand a pattern captured in my Android device’s logcat (Telecom framework logs) and would appreciate input from people familiar with GSM/LTE call setup and paging behavior. **Context:** WindTre (Italy), LTE (MCC 222, MNC 88), device Motorola G75. **What I observed:** a burst of 5 incoming call attempts, same calling number, at regular ~5 second intervals. All calls were auto-rejected by a call-blocking configuration (unknown/non-contact numbers are rejected automatically on this device) — not a manual reject each time, but the standard behavior for non-contact numbers on this setup. Timestamps from logcat (Telecom `TC@` call IDs): Call | Created | Ringing | Disconnected | Reject delay | Interval from previous ---|---|---|---|---|--- TC@22 | 14:12:00.708 | 14:12:00.773 | 14:12:01.997 | ~1.29s | — TC@23 | 14:12:05.508 | 14:12:05.576 | 14:12:06.547 | ~1.04s | 4.80s TC@24 | 14:12:10.062 | 14:12:10.144 | 14:12:11.194 | ~1.13s | 4.55s TC@25 | 14:12:16.911 | 14:12:16.969 | 14:12:18.076 | ~1.17s | 6.85s TC@26 | 14:12:21.585 | 14:12:21.651 | 14:12:22.726 | ~1.14s | 4.67s All disconnects show `DisconnectCause REJECTED, ImsReasonInfo: CODE_LOCAL_CALL_DECLINE`. **Additional detail:** right after the first call’s disconnect (14:12:01.797), the log shows a brief `mVoiceRegState=OUT_OF_SERVICE`, followed within ~100ms by return to `IN_SERVICE`, with `isUsingCarrierAggregation` switching from false to true and `mCellBandwidths` going from `[20000]` to `[20000, 20000]`. **My questions:** 1. Is a ~5s regular retry interval typical of a specific dialer/PBX retry logic, or could it indicate SIP/SS7-level signaling retries (e.g. unanswered INVITE with short timeout)? 2. Is the coincidental service-state blip / CA activation likely just routine network optimization, or could it be related to the call attempts themselves (e.g. paging-triggered reconfiguration)? 3. Any suggestions on what additional data (from `dumpsys telephony.registry`, radio logs, or an app like Network Survey) would help clarify the mechanism? 4. Given that active network signaling (paging, call setup) is known to force a device to report its current cell, could a deliberate burst of repeated call attempts like this be used as a way to force more frequent location updates on a target device? Or would a single attempt already provide equivalent signaling for that purpose, making repeated attempts technically redundant for such a use case? Happy to share the full logcat excerpt if useful. Thanks in advance.
discourse.osmocom.org
August 15, 2026 at 10:03 PM
Repeated call attempts (~5s apart) coinciding with brief service state transition — normal signaling or worth investigating?
Hi all, I’m trying to understand a pattern captured in my Android device’s logcat (Telecom framework logs) and would appreciate input from people familiar with GSM/LTE call setup and paging behavior. **Context:** WindTre (Italy), LTE (MCC 222, MNC 88), device Motorola G75. **What I observed:** a burst of 5 incoming call attempts, same calling number, at regular ~5 second intervals. All calls were auto-rejected by a call-blocking configuration (unknown/non-contact numbers are rejected automatically on this device) — not a manual reject each time, but the standard behavior for non-contact numbers on this setup. Timestamps from logcat (Telecom `TC@` call IDs): Call | Created | Ringing | Disconnected | Reject delay | Interval from previous ---|---|---|---|---|--- TC@22 | 14:12:00.708 | 14:12:00.773 | 14:12:01.997 | ~1.29s | — TC@23 | 14:12:05.508 | 14:12:05.576 | 14:12:06.547 | ~1.04s | 4.80s TC@24 | 14:12:10.062 | 14:12:10.144 | 14:12:11.194 | ~1.13s | 4.55s TC@25 | 14:12:16.911 | 14:12:16.969 | 14:12:18.076 | ~1.17s | 6.85s TC@26 | 14:12:21.585 | 14:12:21.651 | 14:12:22.726 | ~1.14s | 4.67s All disconnects show `DisconnectCause REJECTED, ImsReasonInfo: CODE_LOCAL_CALL_DECLINE`. **Additional detail:** right after the first call’s disconnect (14:12:01.797), the log shows a brief `mVoiceRegState=OUT_OF_SERVICE`, followed within ~100ms by return to `IN_SERVICE`, with `isUsingCarrierAggregation` switching from false to true and `mCellBandwidths` going from `[20000]` to `[20000, 20000]`. **My questions:** 1. Is a ~5s regular retry interval typical of a specific dialer/PBX retry logic, or could it indicate SIP/SS7-level signaling retries (e.g. unanswered INVITE with short timeout)? 2. Is the coincidental service-state blip / CA activation likely just routine network optimization, or could it be related to the call attempts themselves (e.g. paging-triggered reconfiguration)? 3. Any suggestions on what additional data (from `dumpsys telephony.registry`, radio logs, or an app like Network Survey) would help clarify the mechanism? 4. Given that active network signaling (paging, call setup) is known to force a device to report its current cell, could a deliberate burst of repeated call attempts like this be used as a way to force more frequent location updates on a target device? Or would a single attempt already provide equivalent signaling for that purpose, making repeated attempts technically redundant for such a use case? Happy to share the full logcat excerpt if useful. Thanks in advance.
discourse.osmocom.org
August 15, 2026 at 5:25 AM
Repeated call attempts (~5s apart) coinciding with brief service state transition — normal signaling or worth investigating?
Hi all, I’m trying to understand a pattern captured in my Android device’s logcat (Telecom framework logs) and would appreciate input from people familiar with GSM/LTE call setup and paging behavior. **Context:** WindTre (Italy), LTE (MCC 222, MNC 88), device Motorola G75. **What I observed:** a burst of 5 incoming call attempts, same calling number, at regular ~5 second intervals. All calls were auto-rejected by a call-blocking configuration (unknown/non-contact numbers are rejected automatically on this device) — not a manual reject each time, but the standard behavior for non-contact numbers on this setup. Timestamps from logcat (Telecom `TC@` call IDs): Call | Created | Ringing | Disconnected | Reject delay | Interval from previous ---|---|---|---|---|--- TC@22 | 14:12:00.708 | 14:12:00.773 | 14:12:01.997 | ~1.29s | — TC@23 | 14:12:05.508 | 14:12:05.576 | 14:12:06.547 | ~1.04s | 4.80s TC@24 | 14:12:10.062 | 14:12:10.144 | 14:12:11.194 | ~1.13s | 4.55s TC@25 | 14:12:16.911 | 14:12:16.969 | 14:12:18.076 | ~1.17s | 6.85s TC@26 | 14:12:21.585 | 14:12:21.651 | 14:12:22.726 | ~1.14s | 4.67s All disconnects show `DisconnectCause REJECTED, ImsReasonInfo: CODE_LOCAL_CALL_DECLINE`. **Additional detail:** right after the first call’s disconnect (14:12:01.797), the log shows a brief `mVoiceRegState=OUT_OF_SERVICE`, followed within ~100ms by return to `IN_SERVICE`, with `isUsingCarrierAggregation` switching from false to true and `mCellBandwidths` going from `[20000]` to `[20000, 20000]`. **My questions:** 1. Is a ~5s regular retry interval typical of a specific dialer/PBX retry logic, or could it indicate SIP/SS7-level signaling retries (e.g. unanswered INVITE with short timeout)? 2. Is the coincidental service-state blip / CA activation likely just routine network optimization, or could it be related to the call attempts themselves (e.g. paging-triggered reconfiguration)? 3. Any suggestions on what additional data (from `dumpsys telephony.registry`, radio logs, or an app like Network Survey) would help clarify the mechanism? 4. Given that active network signaling (paging, call setup) is known to force a device to report its current cell, could a deliberate burst of repeated call attempts like this be used as a way to force more frequent location updates on a target device? Or would a single attempt already provide equivalent signaling for that purpose, making repeated attempts technically redundant for such a use case? Happy to share the full logcat excerpt if useful. Thanks in advance.
discourse.osmocom.org
August 14, 2026 at 8:28 PM
Wi-Fi 7: come la nuova offerta Super Fibra di WINDTRE spinge l’accesso ultrabroadband
August 13, 2026 at 9:47 AM
🟠🟢🟢🟢🟢🟣

RICORDO A TUTTI CHE WINDTRE È UNA AZIENDA 100% CINESE; PERTANTO QUANDO ACQUISTATE DA LEI AIUTATE I CINESI A METTERVELO IN....

www.windtre.it
WINDTRE semplifica Connessioni, Energia, Assicurazioni
Scopri le offerte WINDTRE per Telefonia Mobile, Internet, Fibra Ottica, Smartphone, le offerte Luce e Gas e le Polizze Assicurative Casa, Salute e Mobilità
www.windtre.it
August 8, 2026 at 12:34 PM
Non sapendo come era evoluto il mercato in Italia, WindTre bloccava il funzionamento del roaming in Italia. Se eventualmente faranno roaming anche su Fastweb S.p.A, non ci saranno blocchi del roaming voluti per concorrenza.
August 3, 2026 at 8:57 AM
Ciao O2 ha cambiato operatore di roaming su TIM, perché prima aveva come operatore Wind Italia. Wind Italia non esiste più. Dalla fusione con Tre Italia ha dato vita a WindTre S.p.A. Nel Regno Unito TheeUK adesso VodafoneThree UK è competitor di O2 Telefonica UK. In Italia Vodafone è Fastweb S.p.A.
August 3, 2026 at 8:54 AM
That company (Tre) now merged with another company called Wind to form WindTre
July 25, 2026 at 12:12 AM