Moin in die Runde,
ich beobachte nun seit mehreren Wochen zunehmende Verbindungsabbrüche bzw. -versuche von Mobilfunkteilnehmern (Echolink für Android, Apfel,..). Das Verhalten bei gesperrten Ports der ISP ist ja hinlänglich bekannt, aber heute kam eine eingehenden Echolinkverbindung über Mobilfunk bei mir (DL7ATA) nicht zustande, wohl aber bei einem völlig identischen System im gleichen svxreflector-Verbund (DL7ATO). Hier der Logauszug von beiden Systemen:
QuoteDisplay MoreDL7ATA [ISP: Telefonica]
==========...
25.09.2017 11:34:23: Spurious audio packet received from 44.137.75.248
25.09.2017 11:34:24: Incoming EchoLink connection from DL3JST (samsung) at 44.137.75.248
25.09.2017 11:34:24: ### Register incoming station, count 1 of 3 possible number of connects
25.09.2017 11:34:24: SimplexLogic: Activating module EchoLink...
25.09.2017 11:34:24: DL3JST: Accepting connection. EchoLink ID is 480738...
25.09.2017 11:34:24: DL3JST: EchoLink QSO state changed to CONNECTED
25.09.2017 11:34:24: --- EchoLink info message received from DL3JST ---
25.09.2017 11:34:24: Station DL3JST
25.09.2017 11:34:24: samsung GT-S6310N User
25.09.2017 11:34:24:
25.09.2017 11:34:24: samsung GT-S6310N User
25.09.2017 11:34:24:
25.09.2017 11:34:24: DL3JST is running EchoLink for Android on a samsung GT-S6310N, with Android version 4.1.2.
25.09.2017 11:34:24: DL3JST: EchoLink QSO state changed to BYE_RECEIVED
25.09.2017 11:34:24: DL3JST: EchoLink QSO state changed to DISCONNECTED
25.09.2017 11:34:24: SimplexLogic: Deactivating module EchoLink...
25.09.2017 11:34:24: Tx1: Turning the transmitter ON
25.09.2017 11:34:26: Ignoring audio/info/chat packet from 44.137.75.248 since we are disconnected.
25.09.2017 11:34:27: Ignoring audio/info/chat packet from 44.137.75.248 since we are disconnected.
25.09.2017 11:34:29: Spurious ctrl packet received from 44.137.75.248
25.09.2017 11:34:29: Spurious ctrl packet received from 44.137.75.248
25.09.2017 11:34:29: Spurious ctrl packet received from 44.137.75.248
25.09.2017 11:34:29: Spurious audio packet received from 44.137.75.248
25.09.2017 11:34:30: Incoming EchoLink connection from DL3JST (samsung) at 44.137.75.248
25.09.2017 11:34:30: ### Station DL3JST, count 2 of 3 possible number of connects
25.09.2017 11:34:30: SimplexLogic: Activating module EchoLink...
25.09.2017 11:34:30: DL3JST: Accepting connection. EchoLink ID is 480738...Dann nach 3 Versuchen gem. "ModuleEcholink.conf" gesperrt.
DL7ATO [ISP: Telekom]
=======
25.09.2017 11:31:29: Tx1: Turning the transmitter OFF
25.09.2017 11:34:59: Spurious audio packet received from 44.137.75.248
25.09.2017 11:35:00: Incoming EchoLink connection from DL3JST (samsung) at 44.137.75.248
25.09.2017 11:35:00: ### Register incoming station, count 1 of 2 possible number of connects
25.09.2017 11:35:00: SimplexLogic: Activating module EchoLink...
25.09.2017 11:35:00: DL3JST: Accepting connection. EchoLink ID is 480738...
25.09.2017 11:35:00: DL3JST: EchoLink QSO state changed to CONNECTED
25.09.2017 11:35:00: Tx1: Turning the transmitter ON
25.09.2017 11:35:05: --- EchoLink info message received from DL3JST ---
25.09.2017 11:35:05: Station DL3JST
25.09.2017 11:35:05: samsung GT-S6310N User
25.09.2017 11:35:05:
25.09.2017 11:35:05: samsung GT-S6310N User
25.09.2017 11:35:05:
25.09.2017 11:35:05: DL3JST is running EchoLink for Android on a samsung GT-S6310N, with Android version 4.1.2.
25.09.2017 11:35:07: Tx1: Turning the transmitter OFF
25.09.2017 11:35:27: Tx1: Turning the transmitter ON
25.09.2017 11:35:27: ### NetLogic: MsgTalkerStart(DL7ATO)
25.09.2017 11:35:53: ### NetLogic: MsgTalkerStop(DL7ATO)Verbindung hergestellt.
M.E. kann es nur an meinem ISP liegen.
Habt Ihr ähnliche Erfahrungen gemacht?