Syslog auf 1930EF zeigt seltsame Einträge des VCM

Forum zu LANCOM Systems VoIP Router/Gateways und zur LANCOM VoIP Option

Moderator: Lancom-Systems Moderatoren

Antworten
Benutzeravatar
fildercom
Beiträge: 1139
Registriert: 23 Jul 2007, 19:50
Wohnort: Stuttgart

Syslog auf 1930EF zeigt seltsame Einträge des VCM

Beitrag von fildercom »

Hallo zusammen,

ich hatte im November von meinem 1781VA auf den 1930EF migriert und dabei die gesamte VCM-Config per Skript gesichert und auf den neuen Router wieder eingespielt.

Seitdem habe ich im Syslog ständig solche Einträge:

Code: Alles auswählen

14 	2026-01-05 12:47:00 	AUTHPRIV 	Hinweis
	[VCM] SIP-Line 0711XXXX23 switched to status 'registered'
15 	2026-01-05 12:47:00 	LOCAL0 	Fehler
	[VCM] SIP-Line 0711XXXX23 switched to status 'un-registered'
16 	2026-01-05 12:47:00 	LOCAL0 	Fehler
	[VCM] SIP-Line 0711XXXX23 switched to status 'generic failure'
17 	2026-01-05 11:01:18 	AUTHPRIV 	Hinweis
	[VCM] SIP-Line 0711XXXX21 switched to status 'registered'
18 	2026-01-05 11:01:18 	AUTHPRIV 	Hinweis
	[VCM] SIP-Line 0711XXXX26 switched to status 'registered'
19 	2026-01-05 11:01:18 	LOCAL0 	Fehler
	[VCM] SIP-Line 0711XXXX26 switched to status 'un-registered'
20 	2026-01-05 11:01:18 	LOCAL0 	Fehler
	[VCM] SIP-Line 0711XXXX26 switched to status 'first server should be used'
21 	2026-01-05 11:01:18 	LOCAL0 	Fehler
	[VCM] SIP-Line 0711XXXX21 switched to status 'un-registered'
22 	2026-01-05 11:01:18 	LOCAL0 	Fehler
	[VCM] SIP-Line 0711XXXX21 switched to status 'first server should be used'
23 	2026-01-05 10:41:22 	AUTHPRIV 	Hinweis
	[VCM] SIP-Line 0711XXXX21 switched to status 'registered'
24 	2026-01-05 10:41:22 	AUTHPRIV 	Hinweis
	[VCM] SIP-Line 0711XXXX26 switched to status 'registered'
25 	2026-01-05 10:41:22 	LOCAL0 	Fehler
	[VCM] SIP-Line 0711XXXX21 switched to status 'un-registered'
26 	2026-01-05 10:41:22 	LOCAL0 	Fehler
	[VCM] SIP-Line 0711XXXX21 switched to status 'generic failure'
27 	2026-01-05 10:41:22 	LOCAL0 	Fehler
	[VCM] SIP-Line 0711XXXX26 switched to status 'un-registered'
28 	2026-01-05 10:41:22 	LOCAL0 	Fehler
	[VCM] SIP-Line 0711XXXX26 switched to status 'generic failure'
Das betrifft eigentlich rundum alle 10 MSN, der Anbieter ist die Telekom Deutschland GmbH. Was ist die Ursache dafür, was läuft da schief und was kann man dagegen tun? Auf dem 1900EF, welcher an einem anderen Telekom-Anschluss hängt und exakt die identische VCM-Config hat (natürlich mit anderen MSN) gibt es dieses "Problem" nicht.

Vielen Dank und viele Grüße
fildercom
Router: 2 x 1900EF (Vodafone Business 600/20; Telekom ADSL2+); 1930EF (Telekom VDSL 250/40);
Wireless: WLC-4006+; 4 x L-452agn;
Switches: 4 x aruba 6100 12G; 2 x Cisco 3560-CX; 2 x Extreme X440G2-12p-10GE4; 2 x Juniper EX2300-C-12P; 3 x Zyxel XS1930-12F
Nach oben
Benutzeravatar
Jirka
Beiträge: 5468
Registriert: 03 Jan 2005, 13:39
Wohnort: Ex-OPAL-Gebiet
Kontaktdaten:
Kontaktdaten von Jirka

Re: Syslog auf 1930EF zeigt seltsame Einträge des VCM

Beitrag von Jirka »

Hi,

da sollte man sicherlich mal den SIP-Packet-Trace und ggf. auch den Callmanager-Trace zu Rate ziehen.
Die Log-Einträge machen aber den Eindruck, als ob es zumindest keine Ausfälle gibt.

Viele Grüße
Jirka
Nach oben
Benutzeravatar
fildercom
Beiträge: 1139
Registriert: 23 Jul 2007, 19:50
Wohnort: Stuttgart

Re: Syslog auf 1930EF zeigt seltsame Einträge des VCM

Beitrag von fildercom »

Ich versuche es in einem Trace mitzuschneiden und melde mich dann wieder. Gerade habe ich den LANtracer laufen und es tut sich natürlich nichts...
Router: 2 x 1900EF (Vodafone Business 600/20; Telekom ADSL2+); 1930EF (Telekom VDSL 250/40);
Wireless: WLC-4006+; 4 x L-452agn;
Switches: 4 x aruba 6100 12G; 2 x Cisco 3560-CX; 2 x Extreme X440G2-12p-10GE4; 2 x Juniper EX2300-C-12P; 3 x Zyxel XS1930-12F
Nach oben
Dr.Einstein
Beiträge: 3451
Registriert: 12 Jan 2010, 14:10

Re: Syslog auf 1930EF zeigt seltsame Einträge des VCM

Beitrag von Dr.Einstein »

Ergänze noch den Trace VCM-DNS. Klingt nach Umschaltung der Prioritäten seitens der Telekom.
Nach oben
Benutzeravatar
fildercom
Beiträge: 1139
Registriert: 23 Jul 2007, 19:50
Wohnort: Stuttgart

Re: Syslog auf 1930EF zeigt seltsame Einträge des VCM

Beitrag von fildercom »

Ich habe da etwas, allerdings noch ohne VCM-DNS:

Code: Alles auswählen

[Callmanager] 2026/01/05 16:58:20,966  Devicetime: 2026/01/05 16:58:20,062 [SIP-Provider] : 0711XXXXXX24: Timeout_F: no answer from registrar, timer F expired  --  this: 0ad8f080

[Callmanager] 2026/01/05 16:58:20,966  Devicetime: 2026/01/05 16:58:20,062 [SIP]: cSipCallDb::FindCall - CallId: +49711XXXXXX24-tel.t-online.de-c486daf9@00a0579c46e6, pCall->GetCallId(): +49711XXXXXX24-tel.t-online.de-c486daf9@00a0579c46e6

[Callmanager] 2026/01/05 16:58:20,966  Devicetime: 2026/01/05 16:58:20,062 [SIP-CALL] : stop session timer for call 0x19794080

[Callmanager] 2026/01/05 16:58:20,966  Devicetime: 2026/01/05 16:58:20,062 [SIP-CALL] : stop session refresh timer for call 0x19794080

[Callmanager] 2026/01/05 16:58:20,966  Devicetime: 2026/01/05 16:58:20,062 [CALL-INFO] : create new media stub with given dialog id

[Callmanager] 2026/01/05 16:58:20,966  Devicetime: 2026/01/05 16:58:20,063 [SIP]: cSipCallDb::RemoveCall - CallId: +49711XXXXXX24-tel.t-online.de-c486daf9@00a0579c46e6

[Callmanager] 2026/01/05 16:58:20,966  Devicetime: 2026/01/05 16:58:20,063 [CALL-INFO] : Destruct CallInfo(19794080)  -> Caller:05eb1998,  Cln.Number:+49711XXXXXX24, Cld.Number:+49711XXXXXX24

[Callmanager] 2026/01/05 16:58:20,966  Devicetime: 2026/01/05 16:58:20,063 [CALL-INFO] : ~cCmCallInfo 0

[Callmanager] 2026/01/05 16:58:20,966  Devicetime: 2026/01/05 16:58:20,063 [CALL-INFO] : ~cCmCallInfo 2

[Callmanager] 2026/01/05 16:58:20,966  Devicetime: 2026/01/05 16:58:20,063 [VCM] : cCmCall::ClearCall

[Callmanager] 2026/01/05 16:58:20,966  Devicetime: 2026/01/05 16:58:20,063 [VCM] : Destruct CmCall(196c2050)  Cln.Number:, Cld.Number:

[Callmanager] 2026/01/05 16:58:20,966  Devicetime: 2026/01/05 16:58:20,063 [SIP-Provider] : 0711XXXXXX24: registrar transport failed

[Callmanager] 2026/01/05 16:58:20,966  Devicetime: 2026/01/05 16:58:20,063 [SIP-Provider] : 0711XXXXXX24: Tear down registrar transport for SipLineTransport 0x0ad930c0

[Callmanager] 2026/01/05 16:58:20,966  Devicetime: 2026/01/05 16:58:20,063 [SIP-Provider] : 0711XXXXXX24: Line's own SipLineTransport

[Callmanager] 2026/01/05 16:58:20,966  Devicetime: 2026/01/05 16:58:20,063 [SIP-Provider] : 0711XXXXXX24: stopRegistration: this:0ad8f080, caller:03a69aec, registration:enabled, register_info:active

[Callmanager] 2026/01/05 16:58:20,966  Devicetime: 2026/01/05 16:58:20,063 [SIP-Provider] : Line '0711XXXXXX24' changed status to 'NOT operable'

[Callmanager] 2026/01/05 16:58:20,966  Devicetime: 2026/01/05 16:58:20,063 [0711XXXXXX24 Registrar Transport]: New restart backoff is 1 seconds

[Callmanager] 2026/01/05 16:58:20,966  Devicetime: 2026/01/05 16:58:20,063 [0711XXXXXX24 Registrar Transport]: (Re)Starting with domain name "tel.t-online.de"

[Callmanager] 2026/01/05 16:58:20,966  Devicetime: 2026/01/05 16:58:20,063 [0711XXXXXX24 Registrar Transport]: m_spDnsObserver is valid

[Callmanager] 2026/01/05 16:58:20,982  Devicetime: 2026/01/05 16:58:20,064 [0711XXXXXX24 Registrar Transport]: DnsUpdate - SipLineTransport(0ad930c0) - is_auto: 0, is_initial: 1, is_sp_cache: 0, is_fallback: 0, DnsIndex: 1

[Callmanager] 2026/01/05 16:58:20,982  Devicetime: 2026/01/05 16:58:20,064 [0711XXXXXX24 Registrar Transport]: DnsUpdate - SipLineTransport(0ad930c0) - m_State: 3, Time since (Re)Start: 0 seconds, m_spTransport: 0aee9660

[Callmanager] 2026/01/05 16:58:20,982  Devicetime: 2026/01/05 16:58:20,064 [0711XXXXXX24 Registrar Transport]: Got valid IP address from DNS cache

[Callmanager] 2026/01/05 16:58:20,982  Devicetime: 2026/01/05 16:58:20,064 [0711XXXXXX24 Registrar Transport]: remote port from dns: 5060, set remote port: 0

[Callmanager] 2026/01/05 16:58:20,982  Devicetime: 2026/01/05 16:58:20,064 [0711XXXXXX24 Registrar Transport]: New transport endpoint is 217.0.147.197:5060, transport state is "Disconnected"

[Callmanager] 2026/01/05 16:58:20,982  Devicetime: 2026/01/05 16:58:20,064 [0711XXXXXX24 Registrar Transport]: MakeRegistrarTransport with type 0

[Callmanager] 2026/01/05 16:58:20,982  Devicetime: 2026/01/05 16:58:20,065 [0711XXXXXX24 Registrar Transport]: SipLineTransport(0ad930c0) - IP Transport ready

[Callmanager] 2026/01/05 16:58:20,982  Devicetime: 2026/01/05 16:58:20,066 [SIP-Provider] : 0711XXXXXX24: registrar transport is ready

[Callmanager] 2026/01/05 16:58:20,982  Devicetime: 2026/01/05 16:58:20,066 [SIP-Provider] : 0711XXXXXX24: startRegistration: this:0ad8f080, caller:03a71b68, registration:enabled, register_info:NOT active

[Callmanager] 2026/01/05 16:58:20,982  Devicetime: 2026/01/05 16:58:20,066 [SIP]: cRegBackoffState::reset

[Callmanager] 2026/01/05 16:58:20,982  Devicetime: 2026/01/05 16:58:20,066 [SIP]: cRegBackoffState::resetOk  -- Time: 500

[Callmanager] 2026/01/05 16:58:20,982  Devicetime: 2026/01/05 16:58:20,066 [SIP-Provider] : 0711XXXXXX24: RegisterTimeout: isNotAvailable:no, TimerExpired:no, this:0ad8f080

[Callmanager] 2026/01/05 16:58:20,982  Devicetime: 2026/01/05 16:58:20,066 [SIP-Provider] : 0711XXXXXX24: RegisterTimeout: Register finally failed earlier -  backoff status: 0, RegTime: 500

[Callmanager] 2026/01/05 16:58:20,998  Devicetime: 2026/01/05 16:58:20,066 [SIP-Provider] : 0711XXXXXX24: RegisterTimeout:TriedFirstServer: 0

[Callmanager] 2026/01/05 16:58:20,998  Devicetime: 2026/01/05 16:58:20,066 [SIP-Provider] : 0711XXXXXX24: RegisterTimeout:get backoff status: 0

[Callmanager] 2026/01/05 16:58:20,998  Devicetime: 2026/01/05 16:58:20,066 [SIP-Provider] : 0711XXXXXX24: RegisterTimeout: Start Timer F

[Callmanager] 2026/01/05 16:58:20,998  Devicetime: 2026/01/05 16:58:20,066 [SIP-Provider] : 0711XXXXXX24: RegisterTimeout: eNaRegister

[Callmanager] 2026/01/05 16:58:20,998  Devicetime: 2026/01/05 16:58:20,066 [SIP-Provider] : 0711XXXXXX24: Register: CallId:+49711XXXXXX24-tel.t-online.de-c486daf9@00a0579c46e6
Kann man daraus bereits sehen, was da schief läuft? Ich versuche es nun nochmal mit VCM-DNS zu "erwischen"...
Router: 2 x 1900EF (Vodafone Business 600/20; Telekom ADSL2+); 1930EF (Telekom VDSL 250/40);
Wireless: WLC-4006+; 4 x L-452agn;
Switches: 4 x aruba 6100 12G; 2 x Cisco 3560-CX; 2 x Extreme X440G2-12p-10GE4; 2 x Juniper EX2300-C-12P; 3 x Zyxel XS1930-12F
Nach oben
Benutzeravatar
fildercom
Beiträge: 1139
Registriert: 23 Jul 2007, 19:50
Wohnort: Stuttgart

Re: Syslog auf 1930EF zeigt seltsame Einträge des VCM

Beitrag von fildercom »

Und hier habe ich noch einen Trace VCM-DNS während so einem Syslog-Eintrag:

Code: Alles auswählen

[VCM-DNS] 2026/01/05 19:14:48,552  Devicetime: 2026/01/05 19:14:46,901 [SIP DNS Cache]: IsIpAddressValid - Cache Key: <_sip._udp.tel.t-online.de, Tag 0>, Address: 217.0.148.133

[VCM-DNS] 2026/01/05 19:14:48,552  Devicetime: 2026/01/05 19:14:46,901 [SIP DNS Cache]: No change of srv record order in cache <_sip._udp.tel.t-online.de, Tag 0> detected - but check if first address is used by transport, currently used address is 217.0.148.133

[VCM-DNS] 2026/01/05 19:14:48,552  Devicetime: 2026/01/05 19:14:46,901 [SIP DNS Cache]: Check if given ip address 217.0.148.133 belongs to server with highest priority for key <_sip._udp.tel.t-online.de, Tag 0>

[VCM-DNS] 2026/01/05 19:14:48,552  Devicetime: 2026/01/05 19:14:46,901 [SIP DNS Cache]: srv: kln000-l01-mav-pc-rt-001.edns.t-ipnet.de

[VCM-DNS] 2026/01/05 19:14:48,552  Devicetime: 2026/01/05 19:14:46,901 [SIP DNS Cache]: CurrentDns: kln000-l01-mav-pc-rt-001.edns.t-ipnet.de

[VCM-DNS] 2026/01/05 19:14:48,552  Devicetime: 2026/01/05 19:14:46,901 [SIP DNS Cache]: IP address 217.0.148.133 for DNS name "kln000-l01-mav-pc-rt-001.edns.t-ipnet.de", which is target for SRV record "_sip._udp.tel.t-online.de" with priority 10 and weight 0

[VCM-DNS] 2026/01/05 19:14:48,552  Devicetime: 2026/01/05 19:14:46,901 [SIP DNS Cache]: Found IP address 217.0.148.133 for DNS name "kln000-l01-mav-pc-rt-001.edns.t-ipnet.de", which is target for SRV record "_sip._udp.tel.t-online.de" with priority 10 and weight 0

[VCM-DNS] 2026/01/05 19:14:48,552  Devicetime: 2026/01/05 19:14:46,901 [SIP DNS Cache]: Addr: 217.0.148.133 matches with Address: 217.0.148.133

[VCM-DNS] 2026/01/05 19:14:48,552  Devicetime: 2026/01/05 19:14:46,901 [SIP DNS Cache]: First address equal to currently used remote address

[Callmanager] 2026/01/05 19:14:48,552  Devicetime: 2026/01/05 19:14:46,901 [0711XXXXXX26 Registrar Transport]: DnsUpdate - SipLineTransport(0ada14c0) - m_State: 0, Time since (Re)Start: 964 seconds, m_spTransport: 196a7c60

[Callmanager] 2026/01/05 19:14:48,552  Devicetime: 2026/01/05 19:14:46,901 [0711XXXXXX26 Registrar Transport]: Ignoring DNS update event (not bootstrapping)

[Callmanager] 2026/01/05 19:14:48,552  Devicetime: 2026/01/05 19:14:46,901 [Monitoring-Line Registrar Transport]: SipLineTransport(1814acc0) - IP Transport ready

[Callmanager] 2026/01/05 19:14:48,552  Devicetime: 2026/01/05 19:14:46,902 [SIP-MONITORING] : Monitoring-Line: registrar transport is ready

[Callmanager] 2026/01/05 19:14:48,552  Devicetime: 2026/01/05 19:14:46,902 [SIP-MONITORING] : Monitoring-Line(19637080): send OPTIONS request to sip server to check if it is available again - tel.t-online.de

[Callmanager] 2026/01/05 19:14:48,552  Devicetime: 2026/01/05 19:14:46,902 [VCM] : Construct CmCall(1981a050)

[Callmanager] 2026/01/05 19:14:48,552  Devicetime: 2026/01/05 19:14:46,902 [cCldE164Addr] : - info       : cCldE164Addr::cCldE164Addr B - Number: , Len: 0

[Callmanager] 2026/01/05 19:14:48,552  Devicetime: 2026/01/05 19:14:46,902 [CALL-INFO] : Construct CallInfo(196a0080) A - stored Entity(19637080)

[Callmanager] 2026/01/05 19:14:48,552  Devicetime: 2026/01/05 19:14:46,903 [SIP-CALL] : cSipCall constructor (type 2) --- call=196a0080, MediaStub=0a7a0458, SIP call-id=770979658@00a0579c46e6, Cld: 

[Callmanager] 2026/01/05 19:14:48,552  Devicetime: 2026/01/05 19:14:46,903 [SIP]: cSipCallDb::InsertCall - CallId: 770979658@00a0579c46e6

[Callmanager] 2026/01/05 19:14:48,552  Devicetime: 2026/01/05 19:14:46,903 [SIP-MONITORING] : Monitoring-Line: processing pending messages -> registrar transport state:Ready, database has calls

[Callmanager] 2026/01/05 19:14:48,552  Devicetime: 2026/01/05 19:14:46,903 [SIP-MONITORING] : cSipMonitoringLine(19637080) -----[ GENERATE OPTIONS to monitor first server

[SIP-Packet] 2026/01/05 19:14:48,552  Devicetime: 2026/01/05 19:14:46,903 [Packet]: 
Sending datagram (352 Bytes) from XXX.XXX.XXX.XXX:10886 to 217.0.148.133:5060 using UDP (RtgTag 0):
OPTIONS sip:217.0.148.133 SIP/2.0\r\n
Via: SIP/2.0/UDP XXX.XXX.XXX.XXX:10886;branch=z9hG4bK-9c904b9f-207ccbec;rport\r\n
From: <sip:217.0.148.133>;tag=379125312-869749533\r\n
To: <sip:217.0.148.133>\r\n
Call-ID: 770979658@00a0579c46e6\r\n
CSeq: 1 OPTIONS\r\n
Max-Forwards: 70\r\n
Accept: application/sdp\r\n
Contact: <sip:XXX.XXX.XXX.XXX:10886;transport=UDP>\r\n
Content-Length: 0\r\n
\r\n

[Callmanager] 2026/01/05 19:14:48,607  Devicetime: 2026/01/05 19:14:46,903 [CALL-INFO] : cSipCall::setWaitingForResponse - method: 3, sequence: 1

[SIP-Packet] 2026/01/05 19:14:48,607  Devicetime: 2026/01/05 19:14:46,935 [Packet]: 
Receiving datagram (351 Bytes) at XXX.XXX.XXX.XXX:10886 from 217.0.148.133:5060 using UDP (RtgTag 0):
SIP/2.0 200 OK\r\n
Via: SIP/2.0/UDP XXX.XXX.XXX.XXX:10886;received=XXX.XXX.XXX.XXX;branch=z9hG4bK-9c904b9f-207ccbec;rport=10886\r\n
From: <sip:217.0.148.133>;tag=379125312-869749533\r\n
To: <sip:217.0.148.133>;tag=MavenirUA_028B1010CECD-14dd-b3655700-2ca7230-695bff97-c82a7\r\n
Call-ID: 770979658@00a0579c46e6\r\n
CSeq: 1 OPTIONS\r\n
Supported: timer\r\n
Content-Length: 0\r\n
\r\n

[Callmanager] 2026/01/05 19:14:48,607  Devicetime: 2026/01/05 19:14:46,935 [SIP]: cSipCallDb::FindCall - CallId: 770979658@00a0579c46e6, pCall->GetCallId(): 770979658@00a0579c46e6

[Callmanager] 2026/01/05 19:14:48,607  Devicetime: 2026/01/05 19:14:46,935 [SIP-CALL] : restart session timer if it is already running for call 0x196a0080

[Callmanager] 2026/01/05 19:14:48,607  Devicetime: 2026/01/05 19:14:46,935 [SIP]: cSipCallDb::FindCall - CallId: 770979658@00a0579c46e6, pCall->GetCallId(): 770979658@00a0579c46e6

[Callmanager] 2026/01/05 19:14:48,607  Devicetime: 2026/01/05 19:14:46,935 [SIP-MONITORING] : cSipMonitoringLine(19637080) -----[ Received 200 Ok on OPTIONS request -> first server available again

[Callmanager] 2026/01/05 19:14:48,607  Devicetime: 2026/01/05 19:14:46,935 [SIP]: cSipCallDb::FindCall - CallId: 770979658@00a0579c46e6, pCall->GetCallId(): 770979658@00a0579c46e6

[Callmanager] 2026/01/05 19:14:48,643  Devicetime: 2026/01/05 19:14:46,935 [SIP-CALL] : - info       : cSipCall(196a0080) - StopRetryTimer() - caller: 03ab568c

[Callmanager] 2026/01/05 19:14:48,643  Devicetime: 2026/01/05 19:14:46,935 [SIP-CALL] : stop session timer for call 0x196a0080

[Callmanager] 2026/01/05 19:14:48,643  Devicetime: 2026/01/05 19:14:46,935 [SIP-CALL] : stop session refresh timer for call 0x196a0080

[Callmanager] 2026/01/05 19:14:48,643  Devicetime: 2026/01/05 19:14:46,936 [SIP]: cSipCallDb::RemoveCall - CallId: 770979658@00a0579c46e6

[Callmanager] 2026/01/05 19:14:48,643  Devicetime: 2026/01/05 19:14:46,936 [CALL-INFO] : Destruct CallInfo(196a0080)  -> Caller:05eb1998,  Cln.Number:, Cld.Number:

[Callmanager] 2026/01/05 19:14:48,643  Devicetime: 2026/01/05 19:14:46,936 [CALL-INFO] : ~cCmCallInfo 0

[Callmanager] 2026/01/05 19:14:48,643  Devicetime: 2026/01/05 19:14:46,936 [CALL-INFO] : ~cCmCallInfo 2

[Callmanager] 2026/01/05 19:14:48,643  Devicetime: 2026/01/05 19:14:46,936 [VCM] : cCmCall::ClearCall

[Callmanager] 2026/01/05 19:14:48,643  Devicetime: 2026/01/05 19:14:46,936 [VCM] : Destruct CmCall(1981a050)  Cln.Number:, Cld.Number:

[Callmanager] 2026/01/05 19:14:48,685  Devicetime: 2026/01/05 19:14:46,936 [SIP-MONITORING] : Line Monitoring-Line dying

[Callmanager] 2026/01/05 19:14:48,685  Devicetime: 2026/01/05 19:14:46,936 [Monitoring-Line Registrar Transport]: Destroy SipLineTransport: 0x1814acc0

[VCM-DNS] 2026/01/05 19:14:48,685  Devicetime: 2026/01/05 19:14:46,936 [SIP DNS Cache]: Unregister: Srv string: 

[VCM-DNS] 2026/01/05 19:14:48,685  Devicetime: 2026/01/05 19:14:46,936 [SIP DNS Cache]: Unregister Naptr for 217.0.148.133

[VCM-DNS] 2026/01/05 19:14:48,685  Devicetime: 2026/01/05 19:14:46,936 [SIP DNS Cache]: Looking for NaptrCacheKey: <217.0.148.133, Tag 0>

[VCM-DNS] 2026/01/05 19:14:48,685  Devicetime: 2026/01/05 19:14:46,936 [SIP Local SRV]: Unregister domain "tel.t-online.de", new use count is 10

[Callmanager] 2026/01/05 19:14:48,732  Devicetime: 2026/01/05 19:14:46,936 [SIP-MONITORING] : Destruct cEntity(19637080)

[Callmanager] 2026/01/05 19:14:48,732  Devicetime: 2026/01/05 19:14:46,936 [SIP-Provider] : 0711XXXXXXX(0ad54080): cSipWanLine::OnOptionsResult - received 200 Ok on OPTIONS request

[Callmanager] 2026/01/05 19:14:48,732  Devicetime: 2026/01/05 19:14:46,936 [SIP-Provider] : 0711XXXXXXX: cSipWanLine::OnRegistrarTransportExpired - passed transport: 0ad53cc0, own transport: 0ad53cc0

[Callmanager] 2026/01/05 19:14:48,732  Devicetime: 2026/01/05 19:14:46,936 [SIP-Provider] : 0711XXXXXXX: renewing registrar transport due to expiration with expire_reason: 3

[Callmanager] 2026/01/05 19:14:48,732  Devicetime: 2026/01/05 19:14:46,937 [SIP-Provider] : 0711XXXXXXX: Unregister line with transport for SipLineTransport 0x0ad53cc0

[Callmanager] 2026/01/05 19:14:48,777  Devicetime: 2026/01/05 19:14:46,937 [SIP-Provider] : 0711XXXXXXX: Start UnregisterNotAnsweredTimer for SipLineTransport 0x0ad53cc0

[Callmanager] 2026/01/05 19:14:48,777  Devicetime: 2026/01/05 19:14:46,937 [SIP-Provider] : 0711XXXXXXX: Unregister: CallId:+49711XXXXXXX-tel.t-online.de-9868922e@00a0579c46e6, RegisterInfo: idle

[Callmanager] 2026/01/05 19:14:48,777  Devicetime: 2026/01/05 19:14:46,937 [VCM] : Construct CmCall(0afce050)

[Callmanager] 2026/01/05 19:14:48,777  Devicetime: 2026/01/05 19:14:46,937 [cCldE164Addr] : - info       : cCldE164Addr::cCldE164Addr B - Number: +49711XXXXXXX, Len: 13

[Callmanager] 2026/01/05 19:14:48,777  Devicetime: 2026/01/05 19:14:46,937 [CALL-INFO] : Construct CallInfo(19c20080) A - stored Entity(0ad54080)

[Callmanager] 2026/01/05 19:14:48,777  Devicetime: 2026/01/05 19:14:46,937 [SIP-CALL] : cSipCall constructor (type 2) --- call=19c20080, MediaStub=196e2c58, SIP call-id=385489829@00a0579c46e6, Cld: +49711XXXXXXX

[Callmanager] 2026/01/05 19:14:48,777  Devicetime: 2026/01/05 19:14:46,937 [SIP]: cSipCallDb::InsertCall - CallId: +49711XXXXXXX-tel.t-online.de-9868922e@00a0579c46e6

[Callmanager] 2026/01/05 19:14:48,777  Devicetime: 2026/01/05 19:14:46,937 [SIP-Provider] : 0711XXXXXXX: Unregister: created SIP call

[Callmanager] 2026/01/05 19:14:48,777  Devicetime: 2026/01/05 19:14:46,937 [SIP-Provider] : 0711XXXXXXX: processing pending messages -> registrar transport state:Ready, database has calls

[Callmanager] 2026/01/05 19:14:48,777  Devicetime: 2026/01/05 19:14:46,937 [SIP-Provider] : -----[ GENERATE REGISTER, call-id=677079

[Callmanager] 2026/01/05 19:14:48,777  Devicetime: 2026/01/05 19:14:46,937 [SIP-Provider] : m_RegisterContactUri:"+49711XXXXXXX" <sip:+49711XXXXXXX@XXX.XXX.XXX.XXX:13810>

[Callmanager] 2026/01/05 19:14:48,777  Devicetime: 2026/01/05 19:14:46,937 [SIP-Provider] : m_RegisterContactUri:"+49711XXXXXXX" <sip:+49711XXXXXXX@XXX.XXX.XXX.XXX:13810>

[SIP-Packet] 2026/01/05 19:14:48,777  Devicetime: 2026/01/05 19:14:46,937 [Packet]: 
Sending datagram (860 Bytes) from XXX.XXX.XXX.XXX:13810 to 217.0.147.197:5060 using UDP (RtgTag 0):
REGISTER sip:tel.t-online.de SIP/2.0\r\n
Via: SIP/2.0/UDP XXX.XXX.XXX.XXX:13810;branch=z9hG4bK-23248d9a-4d8b94f2;rport\r\n
From: "+49711XXXXXXX"<sip:+49711XXXXXXX@tel.t-online.de>;tag=-51628261--1180069421\r\n
To: "+49711XXXXXXX"<sip:+49711XXXXXXX@tel.t-online.de>\r\n
Call-ID: +49711XXXXXXX-tel.t-online.de-9868922e@00a0579c46e6\r\n
CSeq: 11524 REGISTER\r\n
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, REFER, NOTIFY, OPTIONS, PRACK, UPDATE, SUBSCRIBE, INFO\r\n
Max-Forwards: 70\r\n
Contact: <sip:+49711XXXXXXX@XXX.XXX.XXX.XXX:13810;transport=UDP>;expires=0\r\n
User-Agent: LANCOM 1930EF 10.92.0227\r\n
Authorization: Digest username="anonymous@t-online.de", realm="tel.t-online.de", algorithm=MD5, uri="sip:tel.t-online.de", nonce="4e42414e42419b0b37cf81b53c59326b2d18890b2ae1",qop=auth, cnonce="e6c58ef27362c779", nc=00000004, response="09db1fcc7a17bba542b1cdc429a1c4db"\r\n
Content-Length: 0\r\n
\r\n

[Callmanager] 2026/01/05 19:14:48,777  Devicetime: 2026/01/05 19:14:46,937 [CALL-INFO] : cSipCall::setWaitingForResponse - method: 6, sequence: 11524

[SIP-Packet] 2026/01/05 19:14:48,777  Devicetime: 2026/01/05 19:14:47,021 [Packet]: 
Receiving datagram (922 Bytes) at XXX.XXX.XXX.XXX:13810 from 217.0.147.197:5060 using UDP (RtgTag 0):
SIP/2.0 200 OK\r\n
Via: SIP/2.0/UDP XXX.XXX.XXX.XXX:13810;received=XXX.XXX.XXX.XXX;branch=z9hG4bK-23248d9a-4d8b94f2;rport=13810\r\n
From: "+49711XXXXXXX" <sip:+49711XXXXXXX@tel.t-online.de>;tag=-51628261--1180069421\r\n
To: "+49711XXXXXXX" <sip:+49711XXXXXXX@tel.t-online.de>;tag=mavodi-0-4b-c3-1-ffffffc7-881-ffffffffffffffff-6d990000-693750d1-_02DC415E9095-15fd-7d916700-1a2098f-695bff97-dab3d\r\n
Call-ID: +49711XXXXXXX-tel.t-online.de-9868922e@00a0579c46e6\r\n
CSeq: 11524 REGISTER\r\n
Contact: <sip:+49711XXXXXXX@XXX.XXX.XXX.XXX:13810;transport=UDP>;expires=0;+sip.instance="<urn:uuid:f467fbac-5c20-434c-4c67-9e18c5563d7f>"\r\n
Reason: SIP;cause=200;text="CC_NO_ERROR"\r\n
Session-ID: 00000000000000000000000000000000; remote=c70267d43111e6924ae40d912f5ae015\r\n
Service-Route: <sip:mavodi-0-272-3fffffff-2-0-82182004-64642e16baa6e-96c@217.0.147.197:5060;transport=UDP;lr;mpcftk=0-269-b53-2-ffffffff-82182004-64642e16baa6e-96c>\r\n
Content-Length: 0\r\n
\r\n

[Callmanager] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,021 [SIP]: cSipCallDb::FindCall - CallId: +49711XXXXXXX-tel.t-online.de-9868922e@00a0579c46e6, pCall->GetCallId(): +49711XXXXXXX-tel.t-online.de-9868922e@00a0579c46e6

[Callmanager] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,021 [SIP-CALL] : restart session timer if it is already running for call 0x19c20080

[Callmanager] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,021 [SIP]: cSipCallDb::FindCall - CallId: +49711XXXXXXX-tel.t-online.de-9868922e@00a0579c46e6, pCall->GetCallId(): +49711XXXXXXX-tel.t-online.de-9868922e@00a0579c46e6

[Callmanager] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,021 [SIP]: cSipUa::SipResponseHndl 1 - Found SipCall - method: 6, sequence: 11524

[Callmanager] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,021 [CALL-INFO] : cSipCall::isWaitingForResponse 2 - method-it: 6, sequence-it: 11524

[Callmanager] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,021 [CALL-INFO] : cSipCall::removeWaitingForResponse 1 - method: 6, sequence: 11524

[Callmanager] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,021 [CALL-INFO] : cSipCall::removeWaitingForResponse 2 - method-it: 6, sequence-it: 11524

[Callmanager] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,021 [SIP-Provider] : SIP WAN line OkHndl(): sequence valid:yes, message method:6

[Callmanager] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,021 [SIP]: cSipCallDb::FindCall - CallId: +49711XXXXXXX-tel.t-online.de-9868922e@00a0579c46e6, pCall->GetCallId(): +49711XXXXXXX-tel.t-online.de-9868922e@00a0579c46e6

[Callmanager] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,021 [SIP-Provider] : -----[ 200 REGISTER OK HANDLE, call 19c20080, message's sequence 11524, call's sequence 11524

[Callmanager] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,021 [SIP-CALL] : - info       : cSipCall(19c20080) - StopRetryTimer() - caller: 03aa68ac

[Callmanager] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,021 [SIP-Provider] : RegisterOkHndl: Unregister -> restartShortRegisterTimer

[Callmanager] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,021 [SIP]: cRegBackoffState::resetOk  -- Time: 500

[Callmanager] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,021 [SIP-Provider] : 0711XXXXXXX: Tear down registrar transport for SipLineTransport 0x0ad53cc0

[Callmanager] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,022 [SIP-Provider] : 0711XXXXXXX: Line's own SipLineTransport

[Callmanager] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,022 [SIP-Provider] : 0711XXXXXXX: stopRegistration: this:0ad54080, caller:03a69aec, registration:enabled, register_info:active

[Callmanager] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,022 [SIP-Provider] : Line '0711XXXXXXX' changed status to 'NOT operable'

[Callmanager] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,022 [0711XXXXXXX Registrar Transport]: New restart backoff is 1 seconds

[Callmanager] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,022 [0711XXXXXXX Registrar Transport]: (Re)Starting with domain name "tel.t-online.de"

[Callmanager] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,022 [0711XXXXXXX Registrar Transport]: m_spDnsObserver is valid

[Callmanager] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,022 [0711XXXXXXX Registrar Transport]: DnsUpdate - SipLineTransport(0ad53cc0) - is_auto: 0, is_initial: 1, is_sp_cache: 0, is_fallback: 0, DnsIndex: 0

[VCM-DNS] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,022 [SIP DNS Cache]: IsIpAddressValid - Cache Key: <_sip._udp.tel.t-online.de, Tag 0>, Address: 217.0.147.197

[VCM-DNS] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,022 [SIP DNS Cache]: No change of srv record order in cache <_sip._udp.tel.t-online.de, Tag 0> detected - but check if first address is used by transport, currently used address is 217.0.147.197

[VCM-DNS] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,023 [SIP DNS Cache]: Check if given ip address 217.0.147.197 belongs to server with highest priority for key <_sip._udp.tel.t-online.de, Tag 0>

[VCM-DNS] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,023 [SIP DNS Cache]: srv: kln000-l01-mav-pc-rt-001.edns.t-ipnet.de

[VCM-DNS] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,023 [SIP DNS Cache]: CurrentDns: kln000-l01-mav-pc-rt-001.edns.t-ipnet.de

[VCM-DNS] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,023 [SIP DNS Cache]: IP address 217.0.148.133 for DNS name "kln000-l01-mav-pc-rt-001.edns.t-ipnet.de", which is target for SRV record "_sip._udp.tel.t-online.de" with priority 10 and weight 0

[VCM-DNS] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,023 [SIP DNS Cache]: Found IP address 217.0.148.133 for DNS name "kln000-l01-mav-pc-rt-001.edns.t-ipnet.de", which is target for SRV record "_sip._udp.tel.t-online.de" with priority 10 and weight 0

[VCM-DNS] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,023 [SIP DNS Cache]: First address not equal to currently used remote address

[Callmanager] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,023 [0711XXXXXXX Registrar Transport]: DnsUpdate - SipLineTransport(0ad53cc0) - m_State: 3, Time since (Re)Start: 0 seconds, m_spTransport: 0af33860

[VCM-DNS] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,023 [SIP DNS Cache]: Searching 1. most preferred IP address for key <_sip._udp.tel.t-online.de, Tag 0>

[VCM-DNS] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,023 [SIP DNS Cache]: CurrentDns: kln000-l01-mav-pc-rt-001.edns.t-ipnet.de, Port: 5060

[VCM-DNS] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,023 [SIP DNS Cache]: IP address(Index 0) 217.0.148.133 for DNS name "kln000-l01-mav-pc-rt-001.edns.t-ipnet.de", which is target for SRV record "_sip._udp.tel.t-online.de" with priority 10 and weight 0

[VCM-DNS] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,023 [SIP DNS Cache]: Found IP address 217.0.148.133 for DNS name "kln000-l01-mav-pc-rt-001.edns.t-ipnet.de", which is target for SRV record "_sip._udp.tel.t-online.de" with priority 10 and weight 0

[Callmanager] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,023 [0711XXXXXXX Registrar Transport]: Got valid IP address from DNS cache

[Callmanager] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,023 [0711XXXXXXX Registrar Transport]: remote port from dns: 5060, set remote port: 0

[Callmanager] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,023 [0711XXXXXXX Registrar Transport]: New transport endpoint is 217.0.148.133:5060, transport state is "Disconnected"

[Callmanager] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,023 [0711XXXXXXX Registrar Transport]: MakeRegistrarTransport with type 0

[Callmanager] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,023 [SIP-CALL] : stop session timer for call 0x19c20080

[Callmanager] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,023 [SIP-CALL] : stop session refresh timer for call 0x19c20080

[Callmanager] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,023 [CALL-INFO] : create new media stub with given dialog id

[Callmanager] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,024 [SIP]: cSipCallDb::RemoveCall - CallId: +49711XXXXXXX-tel.t-online.de-9868922e@00a0579c46e6

[Callmanager] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,024 [CALL-INFO] : Destruct CallInfo(19c20080)  -> Caller:05eb1998,  Cln.Number:+49711XXXXXXX, Cld.Number:+49711XXXXXXX

[Callmanager] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,024 [CALL-INFO] : ~cCmCallInfo 0

[Callmanager] 2026/01/05 19:14:48,869  Devicetime: 2026/01/05 19:14:47,024 [CALL-INFO] : ~cCmCallInfo 2

[Callmanager] 2026/01/05 19:14:48,869  Devicetime: 2026/01/05 19:14:47,024 [VCM] : cCmCall::ClearCall

[Callmanager] 2026/01/05 19:14:48,869  Devicetime: 2026/01/05 19:14:47,024 [VCM] : Destruct CmCall(0afce050)  Cln.Number:, Cld.Number:

[Callmanager] 2026/01/05 19:14:48,869  Devicetime: 2026/01/05 19:14:47,024 [0711XXXXXXX Registrar Transport]: SipLineTransport(0ad53cc0) - IP Transport ready

[Callmanager] 2026/01/05 19:14:48,869  Devicetime: 2026/01/05 19:14:47,025 [SIP-Provider] : 0711XXXXXXX: registrar transport is ready

[Callmanager] 2026/01/05 19:14:48,869  Devicetime: 2026/01/05 19:14:47,025 [SIP-Provider] : 0711XXXXXXX: startRegistration: this:0ad54080, caller:03a71b68, registration:enabled, register_info:NOT active

[Callmanager] 2026/01/05 19:14:48,869  Devicetime: 2026/01/05 19:14:47,025 [SIP]: cRegBackoffState::reset

[Callmanager] 2026/01/05 19:14:48,869  Devicetime: 2026/01/05 19:14:47,025 [SIP]: cRegBackoffState::resetOk  -- Time: 500

[Callmanager] 2026/01/05 19:14:48,869  Devicetime: 2026/01/05 19:14:47,025 [SIP-Provider] : 0711XXXXXXX: RegisterTimeout: isNotAvailable:no, TimerExpired:no, this:0ad54080

[Callmanager] 2026/01/05 19:14:48,869  Devicetime: 2026/01/05 19:14:47,025 [SIP-Provider] : 0711XXXXXXX: RegisterTimeout: Register finally failed earlier -  backoff status: 0, RegTime: 500

[Callmanager] 2026/01/05 19:14:48,869  Devicetime: 2026/01/05 19:14:47,025 [SIP-Provider] : 0711XXXXXXX: RegisterTimeout:TriedFirstServer: 2

[Callmanager] 2026/01/05 19:14:48,869  Devicetime: 2026/01/05 19:14:47,025 [SIP-Provider] : 0711XXXXXXX: RegisterTimeout:get backoff status: 0

[Callmanager] 2026/01/05 19:14:48,918  Devicetime: 2026/01/05 19:14:47,025 [SIP-Provider] : 0711XXXXXXX: RegisterTimeout: Start Timer F

[Callmanager] 2026/01/05 19:14:48,918  Devicetime: 2026/01/05 19:14:47,025 [SIP-Provider] : 0711XXXXXXX: RegisterTimeout: eNaRegister

[Callmanager] 2026/01/05 19:14:48,918  Devicetime: 2026/01/05 19:14:47,025 [SIP-Provider] : 0711XXXXXXX: Register: CallId:+49711XXXXXXX-tel.t-online.de-9868922e@00a0579c46e6

[Callmanager] 2026/01/05 19:14:48,918  Devicetime: 2026/01/05 19:14:47,025 [VCM] : Construct CmCall(19c24050)

[Callmanager] 2026/01/05 19:14:48,918  Devicetime: 2026/01/05 19:14:47,025 [cCldE164Addr] : - info       : cCldE164Addr::cCldE164Addr B - Number: +49711XXXXXXX, Len: 13

[Callmanager] 2026/01/05 19:14:48,918  Devicetime: 2026/01/05 19:14:47,026 [CALL-INFO] : Construct CallInfo(196fc080) A - stored Entity(0ad54080)

[Callmanager] 2026/01/05 19:14:48,918  Devicetime: 2026/01/05 19:14:47,026 [SIP-CALL] : cSipCall constructor (type 2) --- call=196fc080, MediaStub=19718058, SIP call-id=3557417116@00a0579c46e6, Cld: +49711XXXXXXX

[Callmanager] 2026/01/05 19:14:48,918  Devicetime: 2026/01/05 19:14:47,026 [SIP]: cSipCallDb::InsertCall - CallId: +49711XXXXXXX-tel.t-online.de-9868922e@00a0579c46e6

[Callmanager] 2026/01/05 19:14:48,918  Devicetime: 2026/01/05 19:14:47,026 [SIP-Provider] : 0711XXXXXXX: Register: created SIP call

[Callmanager] 2026/01/05 19:14:48,918  Devicetime: 2026/01/05 19:14:47,026 [SIP-Provider] : 0711XXXXXXX: processing pending messages -> registrar transport state:Ready, database has calls

[Callmanager] 2026/01/05 19:14:48,918  Devicetime: 2026/01/05 19:14:47,026 [SIP-Provider] : -----[ GENERATE REGISTER, call-id=677080

[Callmanager] 2026/01/05 19:14:48,918  Devicetime: 2026/01/05 19:14:47,026 [SIP-Provider] : m_RegisterContactUri:"+49711XXXXXXX" <sip:+49711XXXXXXX@XXX.XXX.XXX.XXX:13810>

[Callmanager] 2026/01/05 19:14:48,918  Devicetime: 2026/01/05 19:14:47,026 [SIP-Provider] : m_RegisterContactUri:"+49711XXXXXXX" <sip:+49711XXXXXXX@XXX.XXX.XXX.XXX:9667>

[SIP-Packet] 2026/01/05 19:14:48,918  Devicetime: 2026/01/05 19:14:47,026 [Packet]: 
Sending datagram (862 Bytes) from XXX.XXX.XXX.XXX:9667 to 217.0.148.133:5060 using UDP (RtgTag 0):
REGISTER sip:tel.t-online.de SIP/2.0\r\n
Via: SIP/2.0/UDP XXX.XXX.XXX.XXX:9667;branch=z9hG4bK-42ed511e-f63c4d47;rport\r\n
From: "+49711XXXXXXX"<sip:+49711XXXXXXX@tel.t-online.de>;tag=-597041274--555315401\r\n
To: "+49711XXXXXXX"<sip:+49711XXXXXXX@tel.t-online.de>\r\n
Call-ID: +49711XXXXXXX-tel.t-online.de-9868922e@00a0579c46e6\r\n
CSeq: 11525 REGISTER\r\n
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, REFER, NOTIFY, OPTIONS, PRACK, UPDATE, SUBSCRIBE, INFO\r\n
Max-Forwards: 70\r\n
Contact: <sip:+49711XXXXXXX@XXX.XXX.XXX.XXX:9667;transport=UDP>\r\n
Expires: 480\r\n
User-Agent: LANCOM 1930EF 10.92.0227\r\n
Authorization: Digest username="anonymous@t-online.de", realm="tel.t-online.de", algorithm=MD5, uri="sip:tel.t-online.de", nonce="4e42414e42419b0b37cf81b53c59326b2d18890b2ae1",qop=auth, cnonce="6a04f04e35027827", nc=00000005, response="73a7764c5355477d5cd1813b55686c00"\r\n
Content-Length: 0\r\n
\r\n

[Callmanager] 2026/01/05 19:14:48,964  Devicetime: 2026/01/05 19:14:47,026 [CALL-INFO] : cSipCall::setWaitingForResponse - method: 6, sequence: 11525

[Callmanager] 2026/01/05 19:14:48,964  Devicetime: 2026/01/05 19:14:47,026 [SIP]: cRegBackoffState::resetState  -- Status: 0

[Callmanager] 2026/01/05 19:14:48,964  Devicetime: 2026/01/05 19:14:47,026 [SIP-Provider] : 0711XXXXXXX: restartShortRegisterTimer -> time:500, this:0ad54080, Caller:03aa8f38

[Callmanager] 2026/01/05 19:14:48,964  Devicetime: 2026/01/05 19:14:47,026 [SIP-Provider] : 0711XXXXXXX: processing pending messages -> registrar transport state:Ready, database has calls

[Callmanager] 2026/01/05 19:14:48,964  Devicetime: 2026/01/05 19:14:47,026 [SIP-Provider] : 0711XXXXXXX: No messages were pending!

[SIP-Packet] 2026/01/05 19:14:48,964  Devicetime: 2026/01/05 19:14:47,151 [Packet]: 
Receiving datagram (775 Bytes) at XXX.XXX.XXX.XXX:9667 from 217.0.148.133:5060 using UDP (RtgTag 0):
SIP/2.0 401 Unauthorized\r\n
Via: SIP/2.0/UDP XXX.XXX.XXX.XXX:9667;received=XXX.XXX.XXX.XXX;branch=z9hG4bK-42ed511e-f63c4d47;rport=9667\r\n
WWW-Authenticate: Digest algorithm=MD5,realm="tel.t-online.de",nonce="4e42414e4241368316ffb3ebf5566a5a0359c80e2342",qop="auth",stale=true\r\n
From: "+49711XXXXXXX" <sip:+49711XXXXXXX@tel.t-online.de>;tag=-597041274--555315401\r\n
To: "+49711XXXXXXX" <sip:+49711XXXXXXX@tel.t-online.de>;tag=mavodi-0-4b-b-1-ffffffc7-881-ffffffffffffffff-6da30000-693750d1-_02DC415E9095-15fd-7d916700-1a20992-695bff98-80cf\r\n
Call-ID: +49711XXXXXXX-tel.t-online.de-9868922e@00a0579c46e6\r\n
CSeq: 11525 REGISTER\r\n
Reason: SIP;cause=401;text="CC_SIP_UNAUTHORIZED_401"\r\n
Session-ID: 00000000000000000000000000000000; remote=13fa04adc8a0eae726499c2e9f0a37c2\r\n
Content-Length: 0\r\n
\r\n

[Callmanager] 2026/01/05 19:14:49,005  Devicetime: 2026/01/05 19:14:47,151 [SIP]: cSipCallDb::FindCall - CallId: +49711XXXXXXX-tel.t-online.de-9868922e@00a0579c46e6, pCall->GetCallId(): +49711XXXXXXX-tel.t-online.de-9868922e@00a0579c46e6

[Callmanager] 2026/01/05 19:14:49,005  Devicetime: 2026/01/05 19:14:47,151 [SIP-CALL] : restart session timer if it is already running for call 0x196fc080

[Callmanager] 2026/01/05 19:14:49,005  Devicetime: 2026/01/05 19:14:47,151 [SIP]: cSipCallDb::FindCall - CallId: +49711XXXXXXX-tel.t-online.de-9868922e@00a0579c46e6, pCall->GetCallId(): +49711XXXXXXX-tel.t-online.de-9868922e@00a0579c46e6

[Callmanager] 2026/01/05 19:14:49,005  Devicetime: 2026/01/05 19:14:47,151 [SIP]: cSipUa::SipResponseHndl 1 - Found SipCall - method: 6, sequence: 11525

[Callmanager] 2026/01/05 19:14:49,005  Devicetime: 2026/01/05 19:14:47,151 [CALL-INFO] : cSipCall::isWaitingForResponse 2 - method-it: 6, sequence-it: 11525

[Callmanager] 2026/01/05 19:14:49,005  Devicetime: 2026/01/05 19:14:47,151 [CALL-INFO] : cSipCall::removeWaitingForResponse 1 - method: 6, sequence: 11525

[Callmanager] 2026/01/05 19:14:49,005  Devicetime: 2026/01/05 19:14:47,151 [CALL-INFO] : cSipCall::removeWaitingForResponse 2 - method-it: 6, sequence-it: 11525

[Callmanager] 2026/01/05 19:14:49,005  Devicetime: 2026/01/05 19:14:47,151 [SIP]: cSipUa::SipResponseHndl 1.1 - IsTransfer: 0, isReplaceCallOngoing: 0, wasReplaceCallOngoing: 0

[Callmanager] 2026/01/05 19:14:49,006  Devicetime: 2026/01/05 19:14:47,151 [SIP-Provider] : cSipProviderLine::UnauthorizedHndl 1

[Callmanager] 2026/01/05 19:14:49,006  Devicetime: 2026/01/05 19:14:47,151 [SIP]: cSipCallDb::FindCall - CallId: +49711XXXXXXX-tel.t-online.de-9868922e@00a0579c46e6, pCall->GetCallId(): +49711XXXXXXX-tel.t-online.de-9868922e@00a0579c46e6

[Callmanager] 2026/01/05 19:14:49,006  Devicetime: 2026/01/05 19:14:47,151 [SIP-Provider] : cSipProviderLine::UnauthorizedHndl 2  set true

[Callmanager] 2026/01/05 19:14:49,006  Devicetime: 2026/01/05 19:14:47,151 [SIP-CALL] : - info       : cSipCall(196fc080) - StopRetryTimer() - caller: 03a9dbd8

[Callmanager] 2026/01/05 19:14:49,006  Devicetime: 2026/01/05 19:14:47,151 [SIP-Provider] : cSipProviderLine::UnauthorizedHndl 2.1  --  CurrentType: UDP, Domain: tel.t-online.de, mediasec: 0

[Callmanager] 2026/01/05 19:14:49,006  Devicetime: 2026/01/05 19:14:47,151 [CALL-INFO] : cSipCall::setWaitingForResponse - method: 6, sequence: 11526

[SIP-Packet] 2026/01/05 19:14:49,006  Devicetime: 2026/01/05 19:14:47,152 [Packet]: 
Sending datagram (862 Bytes) from XXX.XXX.XXX.XXX:9667 to 217.0.148.133:5060 using UDP (RtgTag 0):
REGISTER sip:tel.t-online.de SIP/2.0\r\n
Via: SIP/2.0/UDP XXX.XXX.XXX.XXX:9667;branch=z9hG4bK-65d74c0f-2eebd38a;rport\r\n
From: "+49711XXXXXXX"<sip:+49711XXXXXXX@tel.t-online.de>;tag=-597041274--555315401\r\n
To: "+49711XXXXXXX"<sip:+49711XXXXXXX@tel.t-online.de>\r\n
Call-ID: +49711XXXXXXX-tel.t-online.de-9868922e@00a0579c46e6\r\n
CSeq: 11526 REGISTER\r\n
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, REFER, NOTIFY, OPTIONS, PRACK, UPDATE, SUBSCRIBE, INFO\r\n
Max-Forwards: 70\r\n
Contact: <sip:+49711XXXXXXX@XXX.XXX.XXX.XXX:9667;transport=UDP>\r\n
Expires: 480\r\n
User-Agent: LANCOM 1930EF 10.92.0227\r\n
Authorization: Digest username="anonymous@t-online.de", realm="tel.t-online.de", algorithm=MD5, uri="sip:tel.t-online.de", nonce="4e42414e4241368316ffb3ebf5566a5a0359c80e2342",qop=auth, cnonce="f739bf3396245cb9", nc=00000001, response="682a93393f6a38c7681f393b8e0e740b"\r\n
Content-Length: 0\r\n
\r\n

[Callmanager] 2026/01/05 19:14:49,006  Devicetime: 2026/01/05 19:14:47,152 [SIP]: cRegBackoffState::resetNoAnswer  -- Status: 0

[Callmanager] 2026/01/05 19:14:49,006  Devicetime: 2026/01/05 19:14:47,152 [SIP]: increase error count

[Callmanager] 2026/01/05 19:14:49,006  Devicetime: 2026/01/05 19:14:47,152 [SIP-Provider] : 0711XXXXXXX: restartShortRegisterTimer -> time:1000, this:0ad54080, Caller:03a9e168

[SIP-Packet] 2026/01/05 19:14:49,006  Devicetime: 2026/01/05 19:14:47,253 [Packet]: 
Receiving datagram (1268 Bytes) at XXX.XXX.XXX.XXX:9667 from 217.0.148.133:5060 using UDP (RtgTag 0):
SIP/2.0 200 OK\r\n
Via: SIP/2.0/UDP XXX.XXX.XXX.XXX:9667;received=XXX.XXX.XXX.XXX;branch=z9hG4bK-65d74c0f-2eebd38a;rport=9667\r\n
From: "+49711XXXXXXX" <sip:+49711XXXXXXX@tel.t-online.de>;tag=-597041274--555315401\r\n
To: "+49711XXXXXXX" <sip:+49711XXXXXXX@tel.t-online.de>;tag=mavodi-0-4b-b-1-ffffffc7-881-ffffffffffffffff-6da30000-693750d1-_02DC415E9095-15fd-7d916700-1a20995-695bff98-20a9e\r\n
Call-ID: +49711XXXXXXX-tel.t-online.de-9868922e@00a0579c46e6\r\n
CSeq: 11526 REGISTER\r\n
Contact: <sip:+49711XXXXXXX@XXX.XXX.XXX.XXX:15277;transport=UDP>;expires=3600;+sip.instance="<urn:uuid:900c05a5-2da8-fc1f-b528-182cde0a0f6c>"\r\n
Contact: <sip:+49711XXXXXXX@XXX.XXX.XXX.XXX:9667;transport=UDP>;expires=480;+sip.instance="<urn:uuid:7e7c8d56-2bfa-93d4-2d99-93d4249c577d>"\r\n
P-Associated-URI: <sip:+49711XXXXXXX@tel.t-online.de>\r\n
P-Associated-URI: <tel:+49711XXXXXXX>\r\n
Authentication-Info: nc=00000001,cnonce="f739bf3396245cb9",rspauth="682a93393f6a38c7681f393b8e0e740b",qop=auth\r\n
Reason: SIP;cause=200;text="CC_NO_ERROR"\r\n
Session-ID: 00000000000000000000000000000000; remote=13fa04adc8a0eae726499c2e9f0a37c2\r\n
Service-Route: <sip:mavodi-0-272-3fffffff-2-0-def02004-646055118963f-93b@217.0.148.133:5060;transport=UDP;lr;mpcftk=0-269-1ad1-2-ffffffff-def02004-646055118963f-93b>\r\n
Content-Length: 0\r\n
\r\n

[Callmanager] 2026/01/05 19:14:49,006  Devicetime: 2026/01/05 19:14:47,254 [SIP]: cSipCallDb::FindCall - CallId: +49711XXXXXXX-tel.t-online.de-9868922e@00a0579c46e6, pCall->GetCallId(): +49711XXXXXXX-tel.t-online.de-9868922e@00a0579c46e6

[Callmanager] 2026/01/05 19:14:49,006  Devicetime: 2026/01/05 19:14:47,254 [SIP-CALL] : restart session timer if it is already running for call 0x196fc080

[Callmanager] 2026/01/05 19:14:49,006  Devicetime: 2026/01/05 19:14:47,254 [SIP]: cSipCallDb::FindCall - CallId: +49711XXXXXXX-tel.t-online.de-9868922e@00a0579c46e6, pCall->GetCallId(): +49711XXXXXXX-tel.t-online.de-9868922e@00a0579c46e6

[Callmanager] 2026/01/05 19:14:49,044  Devicetime: 2026/01/05 19:14:47,254 [SIP]: cSipUa::SipResponseHndl 1 - Found SipCall - method: 6, sequence: 11526

[Callmanager] 2026/01/05 19:14:49,044  Devicetime: 2026/01/05 19:14:47,254 [CALL-INFO] : cSipCall::isWaitingForResponse 2 - method-it: 6, sequence-it: 11526

[Callmanager] 2026/01/05 19:14:49,044  Devicetime: 2026/01/05 19:14:47,254 [CALL-INFO] : cSipCall::removeWaitingForResponse 1 - method: 6, sequence: 11526

[Callmanager] 2026/01/05 19:14:49,044  Devicetime: 2026/01/05 19:14:47,254 [CALL-INFO] : cSipCall::removeWaitingForResponse 2 - method-it: 6, sequence-it: 11526

[Callmanager] 2026/01/05 19:14:49,044  Devicetime: 2026/01/05 19:14:47,254 [SIP-Provider] : SIP WAN line OkHndl(): sequence valid:yes, message method:6

[Callmanager] 2026/01/05 19:14:49,044  Devicetime: 2026/01/05 19:14:47,254 [SIP]: cSipCallDb::FindCall - CallId: +49711XXXXXXX-tel.t-online.de-9868922e@00a0579c46e6, pCall->GetCallId(): +49711XXXXXXX-tel.t-online.de-9868922e@00a0579c46e6

[Callmanager] 2026/01/05 19:14:49,044  Devicetime: 2026/01/05 19:14:47,254 [SIP-Provider] : -----[ 200 REGISTER OK HANDLE, call 196fc080, message's sequence 11526, call's sequence 11526

[Callmanager] 2026/01/05 19:14:49,044  Devicetime: 2026/01/05 19:14:47,254 [SIP-CALL] : - info       : cSipCall(196fc080) - StopRetryTimer() - caller: 03aa68ac

[Callmanager] 2026/01/05 19:14:49,044  Devicetime: 2026/01/05 19:14:47,254 [SIP-Provider] : RegisterOkHndl: found contact with expires value: Contact.Expires:480, ResponseUri:<sip:+49711XXXXXXX@XXX.XXX.XXX.XXX:9667;transport=UDP>, RegisterUri:"+49711XXXXXXX" <sip:+49711XXXXXXX@XXX.XXX.XXX.XXX:9667>

[Callmanager] 2026/01/05 19:14:49,044  Devicetime: 2026/01/05 19:14:47,254 [SIP-Provider] : RegisterOkHndl: new expires: 480

[Callmanager] 2026/01/05 19:14:49,044  Devicetime: 2026/01/05 19:14:47,254 [SIP-Provider] : RegisterOkHndl: found contact with expires value: Contact.Expires:3600, ResponseUri:<sip:+49711XXXXXXX@XXX.XXX.XXX.XXX:15277;transport=UDP>, RegisterUri:"+49711XXXXXXX" <sip:+49711XXXXXXX@XXX.XXX.XXX.XXX:9667>

[Callmanager] 2026/01/05 19:14:49,044  Devicetime: 2026/01/05 19:14:47,254 [SIP-Provider] : Line '0711XXXXXXX' changed status to 'operable'

[Callmanager] 2026/01/05 19:14:49,044  Devicetime: 2026/01/05 19:14:47,255 [SIP]: cRegBackoffState::resetOk  -- Time: 480000

[Callmanager] 2026/01/05 19:14:49,100  Devicetime: 2026/01/05 19:14:47,255 [SIP-Provider] : 0711XXXXXXX: restartRegisterTimer -> MinExpiresTime:0s, time:480000ms, this:0ad54080, Caller:03aa6c64

[Callmanager] 2026/01/05 19:14:49,100  Devicetime: 2026/01/05 19:14:47,255 [SIP-CALL] : stop session timer for call 0x196fc080

[Callmanager] 2026/01/05 19:14:49,100  Devicetime: 2026/01/05 19:14:47,255 [SIP-CALL] : stop session refresh timer for call 0x196fc080

[Callmanager] 2026/01/05 19:14:49,100  Devicetime: 2026/01/05 19:14:47,255 [CALL-INFO] : create new media stub with given dialog id

[Callmanager] 2026/01/05 19:14:49,100  Devicetime: 2026/01/05 19:14:47,256 [SIP]: cSipCallDb::RemoveCall - CallId: +49711XXXXXXX-tel.t-online.de-9868922e@00a0579c46e6

[Callmanager] 2026/01/05 19:14:49,100  Devicetime: 2026/01/05 19:14:47,256 [CALL-INFO] : Destruct CallInfo(196fc080)  -> Caller:05eb1998,  Cln.Number:+49711XXXXXXX, Cld.Number:+49711XXXXXXX

[Callmanager] 2026/01/05 19:14:49,100  Devicetime: 2026/01/05 19:14:47,256 [CALL-INFO] : ~cCmCallInfo 0

[Callmanager] 2026/01/05 19:14:49,100  Devicetime: 2026/01/05 19:14:47,256 [CALL-INFO] : ~cCmCallInfo 2

[Callmanager] 2026/01/05 19:14:49,100  Devicetime: 2026/01/05 19:14:47,256 [VCM] : cCmCall::ClearCall

[Callmanager] 2026/01/05 19:14:49,100  Devicetime: 2026/01/05 19:14:47,256 [VCM] : Destruct CmCall(19c24050)  Cln.Number:, Cld.Number:
Ich hoffe, dass die Experten da jetzt etwas dazu sagen können...
Router: 2 x 1900EF (Vodafone Business 600/20; Telekom ADSL2+); 1930EF (Telekom VDSL 250/40);
Wireless: WLC-4006+; 4 x L-452agn;
Switches: 4 x aruba 6100 12G; 2 x Cisco 3560-CX; 2 x Extreme X440G2-12p-10GE4; 2 x Juniper EX2300-C-12P; 3 x Zyxel XS1930-12F
Nach oben
Dr.Einstein
Beiträge: 3451
Registriert: 12 Jan 2010, 14:10

Re: Syslog auf 1930EF zeigt seltsame Einträge des VCM

Beitrag von Dr.Einstein »

Code: Alles auswählen

[VCM-DNS] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,023 [SIP DNS Cache]: First address not equal to currently used remote address
217.0.148.133 vs 217.0.147.197

Kann es sein, dass du zwei Rufnummern mitgeschnitten hast? Du hast leider bis zur letzten Stelle zensiert was es schwerer macht zu erkennen, welche Zeilen zu welcher Rufnummer/Leitung gehören.

Hast du die Leitungsüberwachung explizit auf OPTION gestellt? Wenn ja, warum?
Nach oben
Benutzeravatar
fildercom
Beiträge: 1139
Registriert: 23 Jul 2007, 19:50
Wohnort: Stuttgart

Re: Syslog auf 1930EF zeigt seltsame Einträge des VCM

Beitrag von fildercom »

Dr.Einstein hat geschrieben: 05 Jan 2026, 22:13 Kann es sein, dass du zwei Rufnummern mitgeschnitten hast? Du hast leider bis zur letzten Stelle zensiert was es schwerer macht zu erkennen, welche Zeilen zu welcher Rufnummer/Leitung gehören.

Hast du die Leitungsüberwachung explizit auf OPTION gestellt? Wenn ja, warum?
1. Ja, es sind verschiedene Rufnummern in dem Mitschnitt vorhanden. Ich habe das Trace jetzt nochmal weniger stark zensiert:

Code: Alles auswählen

[VCM-DNS] 2026/01/05 19:14:48,552  Devicetime: 2026/01/05 19:14:46,900 [SIP DNS Cache]: Found IP address 217.0.148.133 for DNS name "kln000-l01-mav-pc-rt-001.edns.t-ipnet.de", which is target for SRV record "_sip._udp.tel.t-online.de" with priority 10 and weight 0

[VCM-DNS] 2026/01/05 19:14:48,552  Devicetime: 2026/01/05 19:14:46,900 [SIP DNS Cache]: Addr: 217.0.148.133 matches with Address: 217.0.148.133

[VCM-DNS] 2026/01/05 19:14:48,552  Devicetime: 2026/01/05 19:14:46,900 [SIP DNS Cache]: First address equal to currently used remote address

[Callmanager] 2026/01/05 19:14:48,552  Devicetime: 2026/01/05 19:14:46,900 [0711XXXXXX25 Registrar Transport]: DnsUpdate - SipLineTransport(0ad9a0c0) - m_State: 0, Time since (Re)Start: 72704 seconds, m_spTransport: 0af1e260

[Callmanager] 2026/01/05 19:14:48,552  Devicetime: 2026/01/05 19:14:46,901 [0711XXXXXX25 Registrar Transport]: Ignoring DNS update event (not bootstrapping)

[Callmanager] 2026/01/05 19:14:48,552  Devicetime: 2026/01/05 19:14:46,901 [0711XXXXXX26 Registrar Transport]: DnsUpdate - SipLineTransport(0ada14c0) - is_auto: 0, is_initial: 1, is_sp_cache: 1, is_fallback: 0, DnsIndex: 1

[Callmanager] 2026/01/05 19:14:48,552  Devicetime: 2026/01/05 19:14:46,901 [0711XXXXXX26 Registrar Transport]: IsValidNotification -  target_name: tel.t-online.de, dns_name: tel.t-online.de, line's routing tag: 0, event's routing tag: 0

[VCM-DNS] 2026/01/05 19:14:48,552  Devicetime: 2026/01/05 19:14:46,901 [SIP DNS Cache]: IsIpAddressValid - Cache Key: <_sip._udp.tel.t-online.de, Tag 0>, Address: 217.0.148.133

[VCM-DNS] 2026/01/05 19:14:48,552  Devicetime: 2026/01/05 19:14:46,901 [SIP DNS Cache]: No change of srv record order in cache <_sip._udp.tel.t-online.de, Tag 0> detected - but check if first address is used by transport, currently used address is 217.0.148.133

[VCM-DNS] 2026/01/05 19:14:48,552  Devicetime: 2026/01/05 19:14:46,901 [SIP DNS Cache]: Check if given ip address 217.0.148.133 belongs to server with highest priority for key <_sip._udp.tel.t-online.de, Tag 0>

[VCM-DNS] 2026/01/05 19:14:48,552  Devicetime: 2026/01/05 19:14:46,901 [SIP DNS Cache]: srv: kln000-l01-mav-pc-rt-001.edns.t-ipnet.de

[VCM-DNS] 2026/01/05 19:14:48,552  Devicetime: 2026/01/05 19:14:46,901 [SIP DNS Cache]: CurrentDns: kln000-l01-mav-pc-rt-001.edns.t-ipnet.de

[VCM-DNS] 2026/01/05 19:14:48,552  Devicetime: 2026/01/05 19:14:46,901 [SIP DNS Cache]: IP address 217.0.148.133 for DNS name "kln000-l01-mav-pc-rt-001.edns.t-ipnet.de", which is target for SRV record "_sip._udp.tel.t-online.de" with priority 10 and weight 0

[VCM-DNS] 2026/01/05 19:14:48,552  Devicetime: 2026/01/05 19:14:46,901 [SIP DNS Cache]: Found IP address 217.0.148.133 for DNS name "kln000-l01-mav-pc-rt-001.edns.t-ipnet.de", which is target for SRV record "_sip._udp.tel.t-online.de" with priority 10 and weight 0

[VCM-DNS] 2026/01/05 19:14:48,552  Devicetime: 2026/01/05 19:14:46,901 [SIP DNS Cache]: Addr: 217.0.148.133 matches with Address: 217.0.148.133

[VCM-DNS] 2026/01/05 19:14:48,552  Devicetime: 2026/01/05 19:14:46,901 [SIP DNS Cache]: First address equal to currently used remote address

[Callmanager] 2026/01/05 19:14:48,552  Devicetime: 2026/01/05 19:14:46,901 [0711XXXXXX26 Registrar Transport]: DnsUpdate - SipLineTransport(0ada14c0) - m_State: 0, Time since (Re)Start: 964 seconds, m_spTransport: 196a7c60

[Callmanager] 2026/01/05 19:14:48,552  Devicetime: 2026/01/05 19:14:46,901 [0711XXXXXX26 Registrar Transport]: Ignoring DNS update event (not bootstrapping)

[Callmanager] 2026/01/05 19:14:48,552  Devicetime: 2026/01/05 19:14:46,901 [Monitoring-Line Registrar Transport]: SipLineTransport(1814acc0) - IP Transport ready

[Callmanager] 2026/01/05 19:14:48,552  Devicetime: 2026/01/05 19:14:46,902 [SIP-MONITORING] : Monitoring-Line: registrar transport is ready

[Callmanager] 2026/01/05 19:14:48,552  Devicetime: 2026/01/05 19:14:46,902 [SIP-MONITORING] : Monitoring-Line(19637080): send OPTIONS request to sip server to check if it is available again - tel.t-online.de

[Callmanager] 2026/01/05 19:14:48,552  Devicetime: 2026/01/05 19:14:46,902 [VCM] : Construct CmCall(1981a050)

[Callmanager] 2026/01/05 19:14:48,552  Devicetime: 2026/01/05 19:14:46,902 [cCldE164Addr] : - info       : cCldE164Addr::cCldE164Addr B - Number: , Len: 0

[Callmanager] 2026/01/05 19:14:48,552  Devicetime: 2026/01/05 19:14:46,902 [CALL-INFO] : Construct CallInfo(196a0080) A - stored Entity(19637080)

[Callmanager] 2026/01/05 19:14:48,552  Devicetime: 2026/01/05 19:14:46,903 [SIP-CALL] : cSipCall constructor (type 2) --- call=196a0080, MediaStub=0a7a0458, SIP call-id=770979658@00a0579c46e6, Cld: 

[Callmanager] 2026/01/05 19:14:48,552  Devicetime: 2026/01/05 19:14:46,903 [SIP]: cSipCallDb::InsertCall - CallId: 770979658@00a0579c46e6

[Callmanager] 2026/01/05 19:14:48,552  Devicetime: 2026/01/05 19:14:46,903 [SIP-MONITORING] : Monitoring-Line: processing pending messages -> registrar transport state:Ready, database has calls

[Callmanager] 2026/01/05 19:14:48,552  Devicetime: 2026/01/05 19:14:46,903 [SIP-MONITORING] : cSipMonitoringLine(19637080) -----[ GENERATE OPTIONS to monitor first server

[SIP-Packet] 2026/01/05 19:14:48,552  Devicetime: 2026/01/05 19:14:46,903 [Packet]: 
Sending datagram (352 Bytes) from XXX.XXX.XXX.XXX:10886 to 217.0.148.133:5060 using UDP (RtgTag 0):
OPTIONS sip:217.0.148.133 SIP/2.0\r\n
Via: SIP/2.0/UDP XXX.XXX.XXX.XXX:10886;branch=z9hG4bK-9c904b9f-207ccbec;rport\r\n
From: <sip:217.0.148.133>;tag=379125312-869749533\r\n
To: <sip:217.0.148.133>\r\n
Call-ID: 770979658@00a0579c46e6\r\n
CSeq: 1 OPTIONS\r\n
Max-Forwards: 70\r\n
Accept: application/sdp\r\n
Contact: <sip:XXX.XXX.XXX.XXX:10886;transport=UDP>\r\n
Content-Length: 0\r\n
\r\n

[Callmanager] 2026/01/05 19:14:48,607  Devicetime: 2026/01/05 19:14:46,903 [CALL-INFO] : cSipCall::setWaitingForResponse - method: 3, sequence: 1

[SIP-Packet] 2026/01/05 19:14:48,607  Devicetime: 2026/01/05 19:14:46,935 [Packet]: 
Receiving datagram (351 Bytes) at XXX.XXX.XXX.XXX:10886 from 217.0.148.133:5060 using UDP (RtgTag 0):
SIP/2.0 200 OK\r\n
Via: SIP/2.0/UDP XXX.XXX.XXX.XXX:10886;received=XXX.XXX.XXX.XXX;branch=z9hG4bK-9c904b9f-207ccbec;rport=10886\r\n
From: <sip:217.0.148.133>;tag=379125312-869749533\r\n
To: <sip:217.0.148.133>;tag=MavenirUA_028B1010CECD-14dd-b3655700-2ca7230-695bff97-c82a7\r\n
Call-ID: 770979658@00a0579c46e6\r\n
CSeq: 1 OPTIONS\r\n
Supported: timer\r\n
Content-Length: 0\r\n
\r\n

[Callmanager] 2026/01/05 19:14:48,607  Devicetime: 2026/01/05 19:14:46,935 [SIP]: cSipCallDb::FindCall - CallId: 770979658@00a0579c46e6, pCall->GetCallId(): 770979658@00a0579c46e6

[Callmanager] 2026/01/05 19:14:48,607  Devicetime: 2026/01/05 19:14:46,935 [SIP-CALL] : restart session timer if it is already running for call 0x196a0080

[Callmanager] 2026/01/05 19:14:48,607  Devicetime: 2026/01/05 19:14:46,935 [SIP]: cSipCallDb::FindCall - CallId: 770979658@00a0579c46e6, pCall->GetCallId(): 770979658@00a0579c46e6

[Callmanager] 2026/01/05 19:14:48,607  Devicetime: 2026/01/05 19:14:46,935 [SIP-MONITORING] : cSipMonitoringLine(19637080) -----[ Received 200 Ok on OPTIONS request -> first server available again

[Callmanager] 2026/01/05 19:14:48,607  Devicetime: 2026/01/05 19:14:46,935 [SIP]: cSipCallDb::FindCall - CallId: 770979658@00a0579c46e6, pCall->GetCallId(): 770979658@00a0579c46e6

[Callmanager] 2026/01/05 19:14:48,643  Devicetime: 2026/01/05 19:14:46,935 [SIP-CALL] : - info       : cSipCall(196a0080) - StopRetryTimer() - caller: 03ab568c

[Callmanager] 2026/01/05 19:14:48,643  Devicetime: 2026/01/05 19:14:46,935 [SIP-CALL] : stop session timer for call 0x196a0080

[Callmanager] 2026/01/05 19:14:48,643  Devicetime: 2026/01/05 19:14:46,935 [SIP-CALL] : stop session refresh timer for call 0x196a0080

[Callmanager] 2026/01/05 19:14:48,643  Devicetime: 2026/01/05 19:14:46,936 [SIP]: cSipCallDb::RemoveCall - CallId: 770979658@00a0579c46e6

[Callmanager] 2026/01/05 19:14:48,643  Devicetime: 2026/01/05 19:14:46,936 [CALL-INFO] : Destruct CallInfo(196a0080)  -> Caller:05eb1998,  Cln.Number:, Cld.Number:

[Callmanager] 2026/01/05 19:14:48,643  Devicetime: 2026/01/05 19:14:46,936 [CALL-INFO] : ~cCmCallInfo 0

[Callmanager] 2026/01/05 19:14:48,643  Devicetime: 2026/01/05 19:14:46,936 [CALL-INFO] : ~cCmCallInfo 2

[Callmanager] 2026/01/05 19:14:48,643  Devicetime: 2026/01/05 19:14:46,936 [VCM] : cCmCall::ClearCall

[Callmanager] 2026/01/05 19:14:48,643  Devicetime: 2026/01/05 19:14:46,936 [VCM] : Destruct CmCall(1981a050)  Cln.Number:, Cld.Number:

[Callmanager] 2026/01/05 19:14:48,685  Devicetime: 2026/01/05 19:14:46,936 [SIP-MONITORING] : Line Monitoring-Line dying

[Callmanager] 2026/01/05 19:14:48,685  Devicetime: 2026/01/05 19:14:46,936 [Monitoring-Line Registrar Transport]: Destroy SipLineTransport: 0x1814acc0

[VCM-DNS] 2026/01/05 19:14:48,685  Devicetime: 2026/01/05 19:14:46,936 [SIP DNS Cache]: Unregister: Srv string: 

[VCM-DNS] 2026/01/05 19:14:48,685  Devicetime: 2026/01/05 19:14:46,936 [SIP DNS Cache]: Unregister Naptr for 217.0.148.133

[VCM-DNS] 2026/01/05 19:14:48,685  Devicetime: 2026/01/05 19:14:46,936 [SIP DNS Cache]: Looking for NaptrCacheKey: <217.0.148.133, Tag 0>

[VCM-DNS] 2026/01/05 19:14:48,685  Devicetime: 2026/01/05 19:14:46,936 [SIP Local SRV]: Unregister domain "tel.t-online.de", new use count is 10

[Callmanager] 2026/01/05 19:14:48,732  Devicetime: 2026/01/05 19:14:46,936 [SIP-MONITORING] : Destruct cEntity(19637080)

[Callmanager] 2026/01/05 19:14:48,732  Devicetime: 2026/01/05 19:14:46,936 [SIP-Provider] : 071184XXX94(0ad54080): cSipWanLine::OnOptionsResult - received 200 Ok on OPTIONS request

[Callmanager] 2026/01/05 19:14:48,732  Devicetime: 2026/01/05 19:14:46,936 [SIP-Provider] : 071184XXX94: cSipWanLine::OnRegistrarTransportExpired - passed transport: 0ad53cc0, own transport: 0ad53cc0

[Callmanager] 2026/01/05 19:14:48,732  Devicetime: 2026/01/05 19:14:46,936 [SIP-Provider] : 071184XXX94: renewing registrar transport due to expiration with expire_reason: 3

[Callmanager] 2026/01/05 19:14:48,732  Devicetime: 2026/01/05 19:14:46,937 [SIP-Provider] : 071184XXX94: Unregister line with transport for SipLineTransport 0x0ad53cc0

[Callmanager] 2026/01/05 19:14:48,777  Devicetime: 2026/01/05 19:14:46,937 [SIP-Provider] : 071184XXX94: Start UnregisterNotAnsweredTimer for SipLineTransport 0x0ad53cc0

[Callmanager] 2026/01/05 19:14:48,777  Devicetime: 2026/01/05 19:14:46,937 [SIP-Provider] : 071184XXX94: Unregister: CallId:+4971184XXX94-tel.t-online.de-9868922e@00a0579c46e6, RegisterInfo: idle

[Callmanager] 2026/01/05 19:14:48,777  Devicetime: 2026/01/05 19:14:46,937 [VCM] : Construct CmCall(0afce050)

[Callmanager] 2026/01/05 19:14:48,777  Devicetime: 2026/01/05 19:14:46,937 [cCldE164Addr] : - info       : cCldE164Addr::cCldE164Addr B - Number: +4971184XXX94, Len: 13

[Callmanager] 2026/01/05 19:14:48,777  Devicetime: 2026/01/05 19:14:46,937 [CALL-INFO] : Construct CallInfo(19c20080) A - stored Entity(0ad54080)

[Callmanager] 2026/01/05 19:14:48,777  Devicetime: 2026/01/05 19:14:46,937 [SIP-CALL] : cSipCall constructor (type 2) --- call=19c20080, MediaStub=196e2c58, SIP call-id=385489829@00a0579c46e6, Cld: +4971184XXX94

[Callmanager] 2026/01/05 19:14:48,777  Devicetime: 2026/01/05 19:14:46,937 [SIP]: cSipCallDb::InsertCall - CallId: +4971184XXX94-tel.t-online.de-9868922e@00a0579c46e6

[Callmanager] 2026/01/05 19:14:48,777  Devicetime: 2026/01/05 19:14:46,937 [SIP-Provider] : 071184XXX94: Unregister: created SIP call

[Callmanager] 2026/01/05 19:14:48,777  Devicetime: 2026/01/05 19:14:46,937 [SIP-Provider] : 071184XXX94: processing pending messages -> registrar transport state:Ready, database has calls

[Callmanager] 2026/01/05 19:14:48,777  Devicetime: 2026/01/05 19:14:46,937 [SIP-Provider] : -----[ GENERATE REGISTER, call-id=677079

[Callmanager] 2026/01/05 19:14:48,777  Devicetime: 2026/01/05 19:14:46,937 [SIP-Provider] : m_RegisterContactUri:"+4971184XXX94" <sip:+4971184XXX94@XXX.XXX.XXX.XXX:13810>

[Callmanager] 2026/01/05 19:14:48,777  Devicetime: 2026/01/05 19:14:46,937 [SIP-Provider] : m_RegisterContactUri:"+4971184XXX94" <sip:+4971184XXX94@XXX.XXX.XXX.XXX:13810>

[SIP-Packet] 2026/01/05 19:14:48,777  Devicetime: 2026/01/05 19:14:46,937 [Packet]: 
Sending datagram (860 Bytes) from XXX.XXX.XXX.XXX:13810 to 217.0.147.197:5060 using UDP (RtgTag 0):
REGISTER sip:tel.t-online.de SIP/2.0\r\n
Via: SIP/2.0/UDP XXX.XXX.XXX.XXX:13810;branch=z9hG4bK-23248d9a-4d8b94f2;rport\r\n
From: "+4971184XXX94"<sip:+4971184XXX94@tel.t-online.de>;tag=-51628261--1180069421\r\n
To: "+4971184XXX94"<sip:+4971184XXX94@tel.t-online.de>\r\n
Call-ID: +4971184XXX94-tel.t-online.de-9868922e@00a0579c46e6\r\n
CSeq: 11524 REGISTER\r\n
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, REFER, NOTIFY, OPTIONS, PRACK, UPDATE, SUBSCRIBE, INFO\r\n
Max-Forwards: 70\r\n
Contact: <sip:+4971184XXX94@XXX.XXX.XXX.XXX:13810;transport=UDP>;expires=0\r\n
User-Agent: LANCOM 1930EF 10.92.0227\r\n
Authorization: Digest username="anonymous@t-online.de", realm="tel.t-online.de", algorithm=MD5, uri="sip:tel.t-online.de", nonce="4e42414e42419b0b37cf81b53c59326b2d18890b2ae1",qop=auth, cnonce="e6c58ef27362c779", nc=00000004, response="09db1fcc7a17bba542b1cdc429a1c4db"\r\n
Content-Length: 0\r\n
\r\n

[Callmanager] 2026/01/05 19:14:48,777  Devicetime: 2026/01/05 19:14:46,937 [CALL-INFO] : cSipCall::setWaitingForResponse - method: 6, sequence: 11524

[SIP-Packet] 2026/01/05 19:14:48,777  Devicetime: 2026/01/05 19:14:47,021 [Packet]: 
Receiving datagram (922 Bytes) at XXX.XXX.XXX.XXX:13810 from 217.0.147.197:5060 using UDP (RtgTag 0):
SIP/2.0 200 OK\r\n
Via: SIP/2.0/UDP XXX.XXX.XXX.XXX:13810;received=XXX.XXX.XXX.XXX;branch=z9hG4bK-23248d9a-4d8b94f2;rport=13810\r\n
From: "+4971184XXX94" <sip:+4971184XXX94@tel.t-online.de>;tag=-51628261--1180069421\r\n
To: "+4971184XXX94" <sip:+4971184XXX94@tel.t-online.de>;tag=mavodi-0-4b-c3-1-ffffffc7-881-ffffffffffffffff-6d990000-693750d1-_02DC415E9095-15fd-7d916700-1a2098f-695bff97-dab3d\r\n
Call-ID: +4971184XXX94-tel.t-online.de-9868922e@00a0579c46e6\r\n
CSeq: 11524 REGISTER\r\n
Contact: <sip:+4971184XXX94@XXX.XXX.XXX.XXX:13810;transport=UDP>;expires=0;+sip.instance="<urn:uuid:f467fbac-5c20-434c-4c67-9e18c5563d7f>"\r\n
Reason: SIP;cause=200;text="CC_NO_ERROR"\r\n
Session-ID: 00000000000000000000000000000000; remote=c70267d43111e6924ae40d912f5ae015\r\n
Service-Route: <sip:mavodi-0-272-3fffffff-2-0-82182004-64642e16baa6e-96c@217.0.147.197:5060;transport=UDP;lr;mpcftk=0-269-b53-2-ffffffff-82182004-64642e16baa6e-96c>\r\n
Content-Length: 0\r\n
\r\n

[Callmanager] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,021 [SIP]: cSipCallDb::FindCall - CallId: +4971184XXX94-tel.t-online.de-9868922e@00a0579c46e6, pCall->GetCallId(): +4971184XXX94-tel.t-online.de-9868922e@00a0579c46e6

[Callmanager] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,021 [SIP-CALL] : restart session timer if it is already running for call 0x19c20080

[Callmanager] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,021 [SIP]: cSipCallDb::FindCall - CallId: +4971184XXX94-tel.t-online.de-9868922e@00a0579c46e6, pCall->GetCallId(): +4971184XXX94-tel.t-online.de-9868922e@00a0579c46e6

[Callmanager] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,021 [SIP]: cSipUa::SipResponseHndl 1 - Found SipCall - method: 6, sequence: 11524

[Callmanager] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,021 [CALL-INFO] : cSipCall::isWaitingForResponse 2 - method-it: 6, sequence-it: 11524

[Callmanager] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,021 [CALL-INFO] : cSipCall::removeWaitingForResponse 1 - method: 6, sequence: 11524

[Callmanager] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,021 [CALL-INFO] : cSipCall::removeWaitingForResponse 2 - method-it: 6, sequence-it: 11524

[Callmanager] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,021 [SIP-Provider] : SIP WAN line OkHndl(): sequence valid:yes, message method:6

[Callmanager] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,021 [SIP]: cSipCallDb::FindCall - CallId: +4971184XXX94-tel.t-online.de-9868922e@00a0579c46e6, pCall->GetCallId(): +4971184XXX94-tel.t-online.de-9868922e@00a0579c46e6

[Callmanager] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,021 [SIP-Provider] : -----[ 200 REGISTER OK HANDLE, call 19c20080, message's sequence 11524, call's sequence 11524

[Callmanager] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,021 [SIP-CALL] : - info       : cSipCall(19c20080) - StopRetryTimer() - caller: 03aa68ac

[Callmanager] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,021 [SIP-Provider] : RegisterOkHndl: Unregister -> restartShortRegisterTimer

[Callmanager] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,021 [SIP]: cRegBackoffState::resetOk  -- Time: 500

[Callmanager] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,021 [SIP-Provider] : 071184XXX94: Tear down registrar transport for SipLineTransport 0x0ad53cc0

[Callmanager] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,022 [SIP-Provider] : 071184XXX94: Line's own SipLineTransport

[Callmanager] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,022 [SIP-Provider] : 071184XXX94: stopRegistration: this:0ad54080, caller:03a69aec, registration:enabled, register_info:active

[Callmanager] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,022 [SIP-Provider] : Line '071184XXX94' changed status to 'NOT operable'

[Callmanager] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,022 [071184XXX94 Registrar Transport]: New restart backoff is 1 seconds

[Callmanager] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,022 [071184XXX94 Registrar Transport]: (Re)Starting with domain name "tel.t-online.de"

[Callmanager] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,022 [071184XXX94 Registrar Transport]: m_spDnsObserver is valid

[Callmanager] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,022 [071184XXX94 Registrar Transport]: DnsUpdate - SipLineTransport(0ad53cc0) - is_auto: 0, is_initial: 1, is_sp_cache: 0, is_fallback: 0, DnsIndex: 0

[VCM-DNS] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,022 [SIP DNS Cache]: IsIpAddressValid - Cache Key: <_sip._udp.tel.t-online.de, Tag 0>, Address: 217.0.147.197

[VCM-DNS] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,022 [SIP DNS Cache]: No change of srv record order in cache <_sip._udp.tel.t-online.de, Tag 0> detected - but check if first address is used by transport, currently used address is 217.0.147.197

[VCM-DNS] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,023 [SIP DNS Cache]: Check if given ip address 217.0.147.197 belongs to server with highest priority for key <_sip._udp.tel.t-online.de, Tag 0>

[VCM-DNS] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,023 [SIP DNS Cache]: srv: kln000-l01-mav-pc-rt-001.edns.t-ipnet.de

[VCM-DNS] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,023 [SIP DNS Cache]: CurrentDns: kln000-l01-mav-pc-rt-001.edns.t-ipnet.de

[VCM-DNS] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,023 [SIP DNS Cache]: IP address 217.0.148.133 for DNS name "kln000-l01-mav-pc-rt-001.edns.t-ipnet.de", which is target for SRV record "_sip._udp.tel.t-online.de" with priority 10 and weight 0

[VCM-DNS] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,023 [SIP DNS Cache]: Found IP address 217.0.148.133 for DNS name "kln000-l01-mav-pc-rt-001.edns.t-ipnet.de", which is target for SRV record "_sip._udp.tel.t-online.de" with priority 10 and weight 0

[VCM-DNS] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,023 [SIP DNS Cache]: First address not equal to currently used remote address

[Callmanager] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,023 [071184XXX94 Registrar Transport]: DnsUpdate - SipLineTransport(0ad53cc0) - m_State: 3, Time since (Re)Start: 0 seconds, m_spTransport: 0af33860

[VCM-DNS] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,023 [SIP DNS Cache]: Searching 1. most preferred IP address for key <_sip._udp.tel.t-online.de, Tag 0>

[VCM-DNS] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,023 [SIP DNS Cache]: CurrentDns: kln000-l01-mav-pc-rt-001.edns.t-ipnet.de, Port: 5060

[VCM-DNS] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,023 [SIP DNS Cache]: IP address(Index 0) 217.0.148.133 for DNS name "kln000-l01-mav-pc-rt-001.edns.t-ipnet.de", which is target for SRV record "_sip._udp.tel.t-online.de" with priority 10 and weight 0

[VCM-DNS] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,023 [SIP DNS Cache]: Found IP address 217.0.148.133 for DNS name "kln000-l01-mav-pc-rt-001.edns.t-ipnet.de", which is target for SRV record "_sip._udp.tel.t-online.de" with priority 10 and weight 0

[Callmanager] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,023 [071184XXX94 Registrar Transport]: Got valid IP address from DNS cache

[Callmanager] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,023 [071184XXX94 Registrar Transport]: remote port from dns: 5060, set remote port: 0

[Callmanager] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,023 [071184XXX94 Registrar Transport]: New transport endpoint is 217.0.148.133:5060, transport state is "Disconnected"

[Callmanager] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,023 [071184XXX94 Registrar Transport]: MakeRegistrarTransport with type 0

[Callmanager] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,023 [SIP-CALL] : stop session timer for call 0x19c20080

[Callmanager] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,023 [SIP-CALL] : stop session refresh timer for call 0x19c20080

[Callmanager] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,023 [CALL-INFO] : create new media stub with given dialog id

[Callmanager] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,024 [SIP]: cSipCallDb::RemoveCall - CallId: +4971184XXX94-tel.t-online.de-9868922e@00a0579c46e6

[Callmanager] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,024 [CALL-INFO] : Destruct CallInfo(19c20080)  -> Caller:05eb1998,  Cln.Number:+4971184XXX94, Cld.Number:+4971184XXX94

[Callmanager] 2026/01/05 19:14:48,815  Devicetime: 2026/01/05 19:14:47,024 [CALL-INFO] : ~cCmCallInfo 0

[Callmanager] 2026/01/05 19:14:48,869  Devicetime: 2026/01/05 19:14:47,024 [CALL-INFO] : ~cCmCallInfo 2

[Callmanager] 2026/01/05 19:14:48,869  Devicetime: 2026/01/05 19:14:47,024 [VCM] : cCmCall::ClearCall

[Callmanager] 2026/01/05 19:14:48,869  Devicetime: 2026/01/05 19:14:47,024 [VCM] : Destruct CmCall(0afce050)  Cln.Number:, Cld.Number:

[Callmanager] 2026/01/05 19:14:48,869  Devicetime: 2026/01/05 19:14:47,024 [071184XXX94 Registrar Transport]: SipLineTransport(0ad53cc0) - IP Transport ready

[Callmanager] 2026/01/05 19:14:48,869  Devicetime: 2026/01/05 19:14:47,025 [SIP-Provider] : 071184XXX94: registrar transport is ready

[Callmanager] 2026/01/05 19:14:48,869  Devicetime: 2026/01/05 19:14:47,025 [SIP-Provider] : 071184XXX94: startRegistration: this:0ad54080, caller:03a71b68, registration:enabled, register_info:NOT active

[Callmanager] 2026/01/05 19:14:48,869  Devicetime: 2026/01/05 19:14:47,025 [SIP]: cRegBackoffState::reset

[Callmanager] 2026/01/05 19:14:48,869  Devicetime: 2026/01/05 19:14:47,025 [SIP]: cRegBackoffState::resetOk  -- Time: 500

[Callmanager] 2026/01/05 19:14:48,869  Devicetime: 2026/01/05 19:14:47,025 [SIP-Provider] : 071184XXX94: RegisterTimeout: isNotAvailable:no, TimerExpired:no, this:0ad54080

[Callmanager] 2026/01/05 19:14:48,869  Devicetime: 2026/01/05 19:14:47,025 [SIP-Provider] : 071184XXX94: RegisterTimeout: Register finally failed earlier -  backoff status: 0, RegTime: 500

[Callmanager] 2026/01/05 19:14:48,869  Devicetime: 2026/01/05 19:14:47,025 [SIP-Provider] : 071184XXX94: RegisterTimeout:TriedFirstServer: 2

[Callmanager] 2026/01/05 19:14:48,869  Devicetime: 2026/01/05 19:14:47,025 [SIP-Provider] : 071184XXX94: RegisterTimeout:get backoff status: 0

[Callmanager] 2026/01/05 19:14:48,918  Devicetime: 2026/01/05 19:14:47,025 [SIP-Provider] : 071184XXX94: RegisterTimeout: Start Timer F

[Callmanager] 2026/01/05 19:14:48,918  Devicetime: 2026/01/05 19:14:47,025 [SIP-Provider] : 071184XXX94: RegisterTimeout: eNaRegister

[Callmanager] 2026/01/05 19:14:48,918  Devicetime: 2026/01/05 19:14:47,025 [SIP-Provider] : 071184XXX94: Register: CallId:+4971184XXX94-tel.t-online.de-9868922e@00a0579c46e6

[Callmanager] 2026/01/05 19:14:48,918  Devicetime: 2026/01/05 19:14:47,025 [VCM] : Construct CmCall(19c24050)

[Callmanager] 2026/01/05 19:14:48,918  Devicetime: 2026/01/05 19:14:47,025 [cCldE164Addr] : - info       : cCldE164Addr::cCldE164Addr B - Number: +4971184XXX94, Len: 13

[Callmanager] 2026/01/05 19:14:48,918  Devicetime: 2026/01/05 19:14:47,026 [CALL-INFO] : Construct CallInfo(196fc080) A - stored Entity(0ad54080)

[Callmanager] 2026/01/05 19:14:48,918  Devicetime: 2026/01/05 19:14:47,026 [SIP-CALL] : cSipCall constructor (type 2) --- call=196fc080, MediaStub=19718058, SIP call-id=3557417116@00a0579c46e6, Cld: +4971184XXX94

[Callmanager] 2026/01/05 19:14:48,918  Devicetime: 2026/01/05 19:14:47,026 [SIP]: cSipCallDb::InsertCall - CallId: +4971184XXX94-tel.t-online.de-9868922e@00a0579c46e6

[Callmanager] 2026/01/05 19:14:48,918  Devicetime: 2026/01/05 19:14:47,026 [SIP-Provider] : 071184XXX94: Register: created SIP call

[Callmanager] 2026/01/05 19:14:48,918  Devicetime: 2026/01/05 19:14:47,026 [SIP-Provider] : 071184XXX94: processing pending messages -> registrar transport state:Ready, database has calls

[Callmanager] 2026/01/05 19:14:48,918  Devicetime: 2026/01/05 19:14:47,026 [SIP-Provider] : -----[ GENERATE REGISTER, call-id=677080

[Callmanager] 2026/01/05 19:14:48,918  Devicetime: 2026/01/05 19:14:47,026 [SIP-Provider] : m_RegisterContactUri:"+4971184XXX94" <sip:+4971184XXX94@XXX.XXX.XXX.XXX:13810>

[Callmanager] 2026/01/05 19:14:48,918  Devicetime: 2026/01/05 19:14:47,026 [SIP-Provider] : m_RegisterContactUri:"+4971184XXX94" <sip:+4971184XXX94@XXX.XXX.XXX.XXX:9667>

[SIP-Packet] 2026/01/05 19:14:48,918  Devicetime: 2026/01/05 19:14:47,026 [Packet]: 
Sending datagram (862 Bytes) from XXX.XXX.XXX.XXX:9667 to 217.0.148.133:5060 using UDP (RtgTag 0):
REGISTER sip:tel.t-online.de SIP/2.0\r\n
Via: SIP/2.0/UDP XXX.XXX.XXX.XXX:9667;branch=z9hG4bK-42ed511e-f63c4d47;rport\r\n
From: "+4971184XXX94"<sip:+4971184XXX94@tel.t-online.de>;tag=-597041274--555315401\r\n
To: "+4971184XXX94"<sip:+4971184XXX94@tel.t-online.de>\r\n
Call-ID: +4971184XXX94-tel.t-online.de-9868922e@00a0579c46e6\r\n
CSeq: 11525 REGISTER\r\n
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, REFER, NOTIFY, OPTIONS, PRACK, UPDATE, SUBSCRIBE, INFO\r\n
Max-Forwards: 70\r\n
Contact: <sip:+4971184XXX94@XXX.XXX.XXX.XXX:9667;transport=UDP>\r\n
Expires: 480\r\n
User-Agent: LANCOM 1930EF 10.92.0227\r\n
Authorization: Digest username="anonymous@t-online.de", realm="tel.t-online.de", algorithm=MD5, uri="sip:tel.t-online.de", nonce="4e42414e42419b0b37cf81b53c59326b2d18890b2ae1",qop=auth, cnonce="6a04f04e35027827", nc=00000005, response="73a7764c5355477d5cd1813b55686c00"\r\n
Content-Length: 0\r\n
\r\n

[Callmanager] 2026/01/05 19:14:48,964  Devicetime: 2026/01/05 19:14:47,026 [CALL-INFO] : cSipCall::setWaitingForResponse - method: 6, sequence: 11525

[Callmanager] 2026/01/05 19:14:48,964  Devicetime: 2026/01/05 19:14:47,026 [SIP]: cRegBackoffState::resetState  -- Status: 0

[Callmanager] 2026/01/05 19:14:48,964  Devicetime: 2026/01/05 19:14:47,026 [SIP-Provider] : 071184XXX94: restartShortRegisterTimer -> time:500, this:0ad54080, Caller:03aa8f38

[Callmanager] 2026/01/05 19:14:48,964  Devicetime: 2026/01/05 19:14:47,026 [SIP-Provider] : 071184XXX94: processing pending messages -> registrar transport state:Ready, database has calls

[Callmanager] 2026/01/05 19:14:48,964  Devicetime: 2026/01/05 19:14:47,026 [SIP-Provider] : 071184XXX94: No messages were pending!

[SIP-Packet] 2026/01/05 19:14:48,964  Devicetime: 2026/01/05 19:14:47,151 [Packet]: 
Receiving datagram (775 Bytes) at XXX.XXX.XXX.XXX:9667 from 217.0.148.133:5060 using UDP (RtgTag 0):
SIP/2.0 401 Unauthorized\r\n
Via: SIP/2.0/UDP XXX.XXX.XXX.XXX:9667;received=XXX.XXX.XXX.XXX;branch=z9hG4bK-42ed511e-f63c4d47;rport=9667\r\n
WWW-Authenticate: Digest algorithm=MD5,realm="tel.t-online.de",nonce="4e42414e4241368316ffb3ebf5566a5a0359c80e2342",qop="auth",stale=true\r\n
From: "+4971184XXX94" <sip:+4971184XXX94@tel.t-online.de>;tag=-597041274--555315401\r\n
To: "+4971184XXX94" <sip:+4971184XXX94@tel.t-online.de>;tag=mavodi-0-4b-b-1-ffffffc7-881-ffffffffffffffff-6da30000-693750d1-_02DC415E9095-15fd-7d916700-1a20992-695bff98-80cf\r\n
Call-ID: +4971184XXX94-tel.t-online.de-9868922e@00a0579c46e6\r\n
CSeq: 11525 REGISTER\r\n
Reason: SIP;cause=401;text="CC_SIP_UNAUTHORIZED_401"\r\n
Session-ID: 00000000000000000000000000000000; remote=13fa04adc8a0eae726499c2e9f0a37c2\r\n
Content-Length: 0\r\n
\r\n

[Callmanager] 2026/01/05 19:14:49,005  Devicetime: 2026/01/05 19:14:47,151 [SIP]: cSipCallDb::FindCall - CallId: +4971184XXX94-tel.t-online.de-9868922e@00a0579c46e6, pCall->GetCallId(): +4971184XXX94-tel.t-online.de-9868922e@00a0579c46e6

[Callmanager] 2026/01/05 19:14:49,005  Devicetime: 2026/01/05 19:14:47,151 [SIP-CALL] : restart session timer if it is already running for call 0x196fc080

[Callmanager] 2026/01/05 19:14:49,005  Devicetime: 2026/01/05 19:14:47,151 [SIP]: cSipCallDb::FindCall - CallId: +4971184XXX94-tel.t-online.de-9868922e@00a0579c46e6, pCall->GetCallId(): +4971184XXX94-tel.t-online.de-9868922e@00a0579c46e6

[Callmanager] 2026/01/05 19:14:49,005  Devicetime: 2026/01/05 19:14:47,151 [SIP]: cSipUa::SipResponseHndl 1 - Found SipCall - method: 6, sequence: 11525

[Callmanager] 2026/01/05 19:14:49,005  Devicetime: 2026/01/05 19:14:47,151 [CALL-INFO] : cSipCall::isWaitingForResponse 2 - method-it: 6, sequence-it: 11525

[Callmanager] 2026/01/05 19:14:49,005  Devicetime: 2026/01/05 19:14:47,151 [CALL-INFO] : cSipCall::removeWaitingForResponse 1 - method: 6, sequence: 11525

[Callmanager] 2026/01/05 19:14:49,005  Devicetime: 2026/01/05 19:14:47,151 [CALL-INFO] : cSipCall::removeWaitingForResponse 2 - method-it: 6, sequence-it: 11525

[Callmanager] 2026/01/05 19:14:49,005  Devicetime: 2026/01/05 19:14:47,151 [SIP]: cSipUa::SipResponseHndl 1.1 - IsTransfer: 0, isReplaceCallOngoing: 0, wasReplaceCallOngoing: 0

[Callmanager] 2026/01/05 19:14:49,006  Devicetime: 2026/01/05 19:14:47,151 [SIP-Provider] : cSipProviderLine::UnauthorizedHndl 1

[Callmanager] 2026/01/05 19:14:49,006  Devicetime: 2026/01/05 19:14:47,151 [SIP]: cSipCallDb::FindCall - CallId: +4971184XXX94-tel.t-online.de-9868922e@00a0579c46e6, pCall->GetCallId(): +4971184XXX94-tel.t-online.de-9868922e@00a0579c46e6

[Callmanager] 2026/01/05 19:14:49,006  Devicetime: 2026/01/05 19:14:47,151 [SIP-Provider] : cSipProviderLine::UnauthorizedHndl 2  set true

[Callmanager] 2026/01/05 19:14:49,006  Devicetime: 2026/01/05 19:14:47,151 [SIP-CALL] : - info       : cSipCall(196fc080) - StopRetryTimer() - caller: 03a9dbd8

[Callmanager] 2026/01/05 19:14:49,006  Devicetime: 2026/01/05 19:14:47,151 [SIP-Provider] : cSipProviderLine::UnauthorizedHndl 2.1  --  CurrentType: UDP, Domain: tel.t-online.de, mediasec: 0

[Callmanager] 2026/01/05 19:14:49,006  Devicetime: 2026/01/05 19:14:47,151 [CALL-INFO] : cSipCall::setWaitingForResponse - method: 6, sequence: 11526

[SIP-Packet] 2026/01/05 19:14:49,006  Devicetime: 2026/01/05 19:14:47,152 [Packet]: 
Sending datagram (862 Bytes) from XXX.XXX.XXX.XXX:9667 to 217.0.148.133:5060 using UDP (RtgTag 0):
REGISTER sip:tel.t-online.de SIP/2.0\r\n
Via: SIP/2.0/UDP XXX.XXX.XXX.XXX:9667;branch=z9hG4bK-65d74c0f-2eebd38a;rport\r\n
From: "+4971184XXX94"<sip:+4971184XXX94@tel.t-online.de>;tag=-597041274--555315401\r\n
To: "+4971184XXX94"<sip:+4971184XXX94@tel.t-online.de>\r\n
Call-ID: +4971184XXX94-tel.t-online.de-9868922e@00a0579c46e6\r\n
CSeq: 11526 REGISTER\r\n
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, REFER, NOTIFY, OPTIONS, PRACK, UPDATE, SUBSCRIBE, INFO\r\n
Max-Forwards: 70\r\n
Contact: <sip:+4971184XXX94@XXX.XXX.XXX.XXX:9667;transport=UDP>\r\n
Expires: 480\r\n
User-Agent: LANCOM 1930EF 10.92.0227\r\n
Authorization: Digest username="anonymous@t-online.de", realm="tel.t-online.de", algorithm=MD5, uri="sip:tel.t-online.de", nonce="4e42414e4241368316ffb3ebf5566a5a0359c80e2342",qop=auth, cnonce="f739bf3396245cb9", nc=00000001, response="682a93393f6a38c7681f393b8e0e740b"\r\n
Content-Length: 0\r\n
\r\n

[Callmanager] 2026/01/05 19:14:49,006  Devicetime: 2026/01/05 19:14:47,152 [SIP]: cRegBackoffState::resetNoAnswer  -- Status: 0

[Callmanager] 2026/01/05 19:14:49,006  Devicetime: 2026/01/05 19:14:47,152 [SIP]: increase error count

[Callmanager] 2026/01/05 19:14:49,006  Devicetime: 2026/01/05 19:14:47,152 [SIP-Provider] : 071184XXX94: restartShortRegisterTimer -> time:1000, this:0ad54080, Caller:03a9e168

[SIP-Packet] 2026/01/05 19:14:49,006  Devicetime: 2026/01/05 19:14:47,253 [Packet]: 
Receiving datagram (1268 Bytes) at XXX.XXX.XXX.XXX:9667 from 217.0.148.133:5060 using UDP (RtgTag 0):
SIP/2.0 200 OK\r\n
Via: SIP/2.0/UDP XXX.XXX.XXX.XXX:9667;received=XXX.XXX.XXX.XXX;branch=z9hG4bK-65d74c0f-2eebd38a;rport=9667\r\n
From: "+4971184XXX94" <sip:+4971184XXX94@tel.t-online.de>;tag=-597041274--555315401\r\n
To: "+4971184XXX94" <sip:+4971184XXX94@tel.t-online.de>;tag=mavodi-0-4b-b-1-ffffffc7-881-ffffffffffffffff-6da30000-693750d1-_02DC415E9095-15fd-7d916700-1a20995-695bff98-20a9e\r\n
Call-ID: +4971184XXX94-tel.t-online.de-9868922e@00a0579c46e6\r\n
CSeq: 11526 REGISTER\r\n
Contact: <sip:+4971184XXX94@XXX.XXX.XXX.XXX:15277;transport=UDP>;expires=3600;+sip.instance="<urn:uuid:900c05a5-2da8-fc1f-b528-182cde0a0f6c>"\r\n
Contact: <sip:+4971184XXX94@XXX.XXX.XXX.XXX:9667;transport=UDP>;expires=480;+sip.instance="<urn:uuid:7e7c8d56-2bfa-93d4-2d99-93d4249c577d>"\r\n
P-Associated-URI: <sip:+4971184XXX94@tel.t-online.de>\r\n
P-Associated-URI: <tel:+4971184XXX94>\r\n
Authentication-Info: nc=00000001,cnonce="f739bf3396245cb9",rspauth="682a93393f6a38c7681f393b8e0e740b",qop=auth\r\n
Reason: SIP;cause=200;text="CC_NO_ERROR"\r\n
Session-ID: 00000000000000000000000000000000; remote=13fa04adc8a0eae726499c2e9f0a37c2\r\n
Service-Route: <sip:mavodi-0-272-3fffffff-2-0-def02004-646055118963f-93b@217.0.148.133:5060;transport=UDP;lr;mpcftk=0-269-1ad1-2-ffffffff-def02004-646055118963f-93b>\r\n
Content-Length: 0\r\n
\r\n

[Callmanager] 2026/01/05 19:14:49,006  Devicetime: 2026/01/05 19:14:47,254 [SIP]: cSipCallDb::FindCall - CallId: +4971184XXX94-tel.t-online.de-9868922e@00a0579c46e6, pCall->GetCallId(): +4971184XXX94-tel.t-online.de-9868922e@00a0579c46e6

[Callmanager] 2026/01/05 19:14:49,006  Devicetime: 2026/01/05 19:14:47,254 [SIP-CALL] : restart session timer if it is already running for call 0x196fc080

[Callmanager] 2026/01/05 19:14:49,006  Devicetime: 2026/01/05 19:14:47,254 [SIP]: cSipCallDb::FindCall - CallId: +4971184XXX94-tel.t-online.de-9868922e@00a0579c46e6, pCall->GetCallId(): +4971184XXX94-tel.t-online.de-9868922e@00a0579c46e6

[Callmanager] 2026/01/05 19:14:49,044  Devicetime: 2026/01/05 19:14:47,254 [SIP]: cSipUa::SipResponseHndl 1 - Found SipCall - method: 6, sequence: 11526

[Callmanager] 2026/01/05 19:14:49,044  Devicetime: 2026/01/05 19:14:47,254 [CALL-INFO] : cSipCall::isWaitingForResponse 2 - method-it: 6, sequence-it: 11526

[Callmanager] 2026/01/05 19:14:49,044  Devicetime: 2026/01/05 19:14:47,254 [CALL-INFO] : cSipCall::removeWaitingForResponse 1 - method: 6, sequence: 11526

[Callmanager] 2026/01/05 19:14:49,044  Devicetime: 2026/01/05 19:14:47,254 [CALL-INFO] : cSipCall::removeWaitingForResponse 2 - method-it: 6, sequence-it: 11526

[Callmanager] 2026/01/05 19:14:49,044  Devicetime: 2026/01/05 19:14:47,254 [SIP-Provider] : SIP WAN line OkHndl(): sequence valid:yes, message method:6

[Callmanager] 2026/01/05 19:14:49,044  Devicetime: 2026/01/05 19:14:47,254 [SIP]: cSipCallDb::FindCall - CallId: +4971184XXX94-tel.t-online.de-9868922e@00a0579c46e6, pCall->GetCallId(): +4971184XXX94-tel.t-online.de-9868922e@00a0579c46e6

[Callmanager] 2026/01/05 19:14:49,044  Devicetime: 2026/01/05 19:14:47,254 [SIP-Provider] : -----[ 200 REGISTER OK HANDLE, call 196fc080, message's sequence 11526, call's sequence 11526

[Callmanager] 2026/01/05 19:14:49,044  Devicetime: 2026/01/05 19:14:47,254 [SIP-CALL] : - info       : cSipCall(196fc080) - StopRetryTimer() - caller: 03aa68ac

[Callmanager] 2026/01/05 19:14:49,044  Devicetime: 2026/01/05 19:14:47,254 [SIP-Provider] : RegisterOkHndl: found contact with expires value: Contact.Expires:480, ResponseUri:<sip:+4971184XXX94@XXX.XXX.XXX.XXX:9667;transport=UDP>, RegisterUri:"+4971184XXX94" <sip:+4971184XXX94@XXX.XXX.XXX.XXX:9667>

[Callmanager] 2026/01/05 19:14:49,044  Devicetime: 2026/01/05 19:14:47,254 [SIP-Provider] : RegisterOkHndl: new expires: 480

[Callmanager] 2026/01/05 19:14:49,044  Devicetime: 2026/01/05 19:14:47,254 [SIP-Provider] : RegisterOkHndl: found contact with expires value: Contact.Expires:3600, ResponseUri:<sip:+4971184XXX94@XXX.XXX.XXX.XXX:15277;transport=UDP>, RegisterUri:"+4971184XXX94" <sip:+4971184XXX94@XXX.XXX.XXX.XXX:9667>

[Callmanager] 2026/01/05 19:14:49,044  Devicetime: 2026/01/05 19:14:47,254 [SIP-Provider] : Line '071184XXX94' changed status to 'operable'

[Callmanager] 2026/01/05 19:14:49,044  Devicetime: 2026/01/05 19:14:47,255 [SIP]: cRegBackoffState::resetOk  -- Time: 480000

[Callmanager] 2026/01/05 19:14:49,100  Devicetime: 2026/01/05 19:14:47,255 [SIP-Provider] : 071184XXX94: restartRegisterTimer -> MinExpiresTime:0s, time:480000ms, this:0ad54080, Caller:03aa6c64

[Callmanager] 2026/01/05 19:14:49,100  Devicetime: 2026/01/05 19:14:47,255 [SIP-CALL] : stop session timer for call 0x196fc080

[Callmanager] 2026/01/05 19:14:49,100  Devicetime: 2026/01/05 19:14:47,255 [SIP-CALL] : stop session refresh timer for call 0x196fc080

[Callmanager] 2026/01/05 19:14:49,100  Devicetime: 2026/01/05 19:14:47,255 [CALL-INFO] : create new media stub with given dialog id

[Callmanager] 2026/01/05 19:14:49,100  Devicetime: 2026/01/05 19:14:47,256 [SIP]: cSipCallDb::RemoveCall - CallId: +4971184XXX94-tel.t-online.de-9868922e@00a0579c46e6

[Callmanager] 2026/01/05 19:14:49,100  Devicetime: 2026/01/05 19:14:47,256 [CALL-INFO] : Destruct CallInfo(196fc080)  -> Caller:05eb1998,  Cln.Number:+4971184XXX94, Cld.Number:+4971184XXX94

[Callmanager] 2026/01/05 19:14:49,100  Devicetime: 2026/01/05 19:14:47,256 [CALL-INFO] : ~cCmCallInfo 0

[Callmanager] 2026/01/05 19:14:49,100  Devicetime: 2026/01/05 19:14:47,256 [CALL-INFO] : ~cCmCallInfo 2

[Callmanager] 2026/01/05 19:14:49,100  Devicetime: 2026/01/05 19:14:47,256 [VCM] : cCmCall::ClearCall

[Callmanager] 2026/01/05 19:14:49,100  Devicetime: 2026/01/05 19:14:47,256 [VCM] : Destruct CmCall(19c24050)  Cln.Number:, Cld.Number:
2. Nein, die Leitungsüberwachung steht bei allen 10 MSN auf "Automatisch", habe es extra nochmal kontrolliert.

Kannst du bitte nochmal drüber schauen, was da los ist?

Vielen Dank und viele Grüße
fildercom
Router: 2 x 1900EF (Vodafone Business 600/20; Telekom ADSL2+); 1930EF (Telekom VDSL 250/40);
Wireless: WLC-4006+; 4 x L-452agn;
Switches: 4 x aruba 6100 12G; 2 x Cisco 3560-CX; 2 x Extreme X440G2-12p-10GE4; 2 x Juniper EX2300-C-12P; 3 x Zyxel XS1930-12F
Nach oben
Antworten

Zurück zu „Fragen zu LANCOM Systems VoIP Router“