Con H-Farm nasce Innovation CoLab: la prima fase sperimentale ha raccolto le candidature di 39 team, per un totale di 231 dipendenti. Le proposte selezionate passeranno dal campus al confronto con il top management, con l’obiettivo di realizzarne almeno una L'articolo WindTre, giovani e senior insieme per sviluppare nuove idee di business proviene da CorCom.

La Super Fibra di WindTre combina connessione fissa fino a 2,5 Gigabit, modem Wi-Fi 7 e Giga illimitati sulle SIM compatibili. Il prezzo è di 24,99 euro al mese per i primi 12 mesi, poi 29,99 euro L'articolo WindTre Super Fibra fisso+mobile: Wi-Fi 7 e Giga illimitati proviene da CorCom.

WindTre Super Fibra propone fibra fino a 2,5 Gigabit, modem Wi-Fi 7, 12 mesi di Amazon Prime e GIGA illimitati sulle SIM compatibili. Inclusa anche la funzione Wi-Fi Calling, senza costi aggiuntivi L'articolo WindTre e convergenza fisso-mobile: Super Fibra con Wi-Fi 7, promo Amazon Prime e Wi-Fi Calling proviene da CorCom.

Il monitoraggio di Altroconsumo, condotto attraverso l’app CheBanda con il contributo di oltre 9.000 utenti, assegna a Fastweb la seconda posizione. Le prove sulla nuova generazione raggiungono il 43% del totale, rispetto a circa il 30% della rilevazione precedente L'articolo Qualità delle reti mobili, Vodafone al vertice. WindTre avanza sull’onda del 5G proviene da CorCom.

Il processo di assegnazione dei diritti d’uso della banda 24,25-26,50 GHz, destinata allo sviluppo delle reti wireless ad alte prestazioni e delle applicazioni 5G, entra nel vivo. Intermonte: “La presenza di lotti territoriali potrebbe risultare particolarmente interessante per operatori Fwa quali Eolo e OpNet (WindTre)” L'articolo Frequenze, in Gazzetta Ufficiale l’avviso di gara per la banda 26Ghz bassa proviene da CorCom.

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.

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.

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.

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.

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.

WindTre Super Fibra costa 24,99 euro al mese per 12 mesi, poi 29,99 euro, e include fibra fino a 2,5 Gbps, modem Wi-Fi 7, 12 mesi di Amazon Prime e GIGA illimitati su tre SIM compatibili. Previsti anche Wi-Fi Calling e attivazione a 1,99 euro al mese per 24 mesi L'articolo Wi-Fi 7: come la nuova offerta Super Fibra di WINDTRE spinge l’accesso ultrabroadband proviene da CorCom.

Scopri le offerte WINDTRE per Telefonia Mobile, Internet, Fibra Ottica, Smartphone, le offerte Luce e Gas e le Polizze Assicurative Casa, Salute e Mobilità

La gestione dei consumi dati e voce fuori dai confini nazionali rappresenta da sempre un punto critico per gli utenti, divisi tra la certezza delle tutele comunitarie e le insidie tariffarie dei viagg...

Il Cyber Arena Tour di WINDTRE Business coinvolge aziende e PMI italiane in simulazioni realistiche di attacchi cyber: gamification, decisioni sotto pressione e competenze specialistiche per trasformare la sicurezza informatica da tema tecnico a priorità strategica d'impresa

Problemi in corso sulla rete WINDTRE, down segnalati anche dagli utenti Very Mobile che utilizzano la stessa infrastruttura dell'operatore. The post WINDTRE down il 28 luglio: tutti gli aggiornamenti (risolto) appeared first on Punto Informatico.

Tra piattaforme, connessioni domestiche e servizi digitali cresce la complessità nella gestione dell’intrattenimento. Le soluzioni che riuniscono rete ultraveloce e contenuti in un unico pacchetto puntano a semplificare l’esperienza, rendere più prevedibile la spesa e garantire una visione stabile in HD. Il caso di Super Fibra & Netflix di WINDTRE. L'articolo Fibra e streaming, il valore del bundle: qualità e risparmio in un’unica offerta proviene da CorCom.