@David-TP 

Hello David, thanks for your quick response.

 

Well the VOIP worked flawlessly until last week.

As I described, the "login" for VOIP in the webinterface did not work anymore.

I tried from the router's Wifi with the Linphone-Android-App, this worked immediately.

And later on I tried my spare router AVM 7390 which also functioned immediately.

I noticed some log-messages indicating problems resolving an IP-name, an DHCP enquiry remained unanswered.

My provider Telekom has changed the resolution method for their VOIP registrars from "DNS A-request to "SRV-Record", acording to:
(Just google telekom and srv-records)

So I think it quite possible, that the issue is related to this.

I also noticed some other customers in the forum were coming up over the weekend with similar issues.

At the moment I use the VR600V as a Wifi router connected to the 7390 for DSL and VOIP.

So I cannot try out any tweaks right now.

But maybe you could check out about the compatibility with srv-records meanwhile.

 

 

Best regards,

 

Skip

Same problem here with my VR600V V2 and Telekom VOIP. As far as I have read in the forum, other tp-link devices are affected by the same problem. And Telekom seems to point to tp-link, so they have to update their firmwares ASAP.

I suffer the same problem here in Germany. My Telekom VOIP is not working anymore, DSL connection and internet access is fine. Telekom tested the line and everything is fine, must be a VOIP protocol issue in the VR600V2 router.

 

*** URGENT *** TP-Link: Will this be fixed soon? Otherwise I have to trash my router that is not even two years old, would be a waste of money and resources.

Hello TP-Link,

 

I just retried and the issue persists.

 

Some Logs:

 

1    2022-03-26 18:59:20    DHCPC    Hinweis    Send DISCOVER with request ip 0.0.0.0 and unicast flag 0
2    2022-03-26 18:59:15    DHCPC    Hinweis    Send DISCOVER with request ip 0.0.0.0 and unicast flag 1
3    2022-03-26 18:59:12    DHCPC    Hinweis    Send DISCOVER with request ip 0.0.0.0 and unicast flag 1
4    2022-03-26 18:59:09    DHCPC    Hinweis    Send DISCOVER with request ip 0.0.0.0 and unicast flag 1
5    2022-03-26 18:58:58    DHCPC    Hinweis    Recv no OFFER, DHCP Service unavailable

 

1    2022-03-26 19:01:52    DHCPC    Hinweis    Recv no OFFER, DHCP Service unavailable
2    2022-03-26 19:01:49    DHCPC    Hinweis    Send DISCOVER with request ip 0.0.0.0 and unicast flag 0
3    2022-03-26 19:01:46    DHCPC    Hinweis    Send DISCOVER with request ip 0.0.0.0 and unicast flag 0
4    2022-03-26 19:01:41    DHCPC    Hinweis    Send DISCOVER with request ip 0.0.0.0 and unicast flag 1
5    2022-03-26 19:01:38    DHCPC    Hinweis    Send DISCOVER with request ip 0.0.0.0 and unicast flag 1
6    2022-03-26 19:01:35    DHCPC    Hinweis    Send DISCOVER with request ip 0.0.0.0 and unicast flag 1
7    2022-03-26 19:01:17    VOIP    Hinweis    enable SIP stack due to intf(...) is up.
8    2022-03-26 19:01:15    VOIP    Hinweis    restart SIP stack due to intf IP changed to ...

 

This really appears to me like a problem connection to the Telekom's SIP-servers.

Maybe this is related to their change to use srv-records to resolve the addresses of their servers as I mentioned.

 

You have to do something, quite urgently- Telekom is the largest provider here and when you stop supporting this you probably would run into a mass of complaints and people just returning their devices new bought to the stores in numbers.

 

Thanks in advance,

 

Skip

 Hello,

 

I tried out the Beta-Firmware for VR600V2 from today.

 

Archer_VR600vV2_0.7.0_0.9.1_up_boot(220329)

 

Basically it seems to work again - thank you.

 

I noticed a few things:

 

First I got some errors in the logs:

 

1    2022-03-29 18:56:13    VOIP    Vorsicht    every IP of the domain has been tried, but we didn't find the correct one!
2    2022-03-29 18:56:13    VOIP    Vorsicht    every IP of the domain has been tried, but we didn't find the correct one!
3    2022-03-29 18:56:13    VOIP    Vorsicht    every IP of the domain has been tried, but we didn't find the correct one!
4    2022-03-29 18:56:13    VOIP    Vorsicht    every IP of the domain has been tried, but we didn't find the correct one!
5    2022-03-29 18:56:13    VOIP    Vorsicht    every IP of the domain has been tried, but we didn't find the correct one!
6    2022-03-29 18:56:13    VOIP    Vorsicht    every IP of the domain has been tried, but we didn't find the correct one!
7    2022-03-29 18:56:04    DHCPC    Hinweis    Recv no OFFER, DHCP Service unavailable
8    2022-03-29 18:56:01    DHCPC    Hinweis    Send DISCOVER with request ip 0.0.0.0 and unicast flag 0

 

I believe I disabled IPV6 in the telefon provider dialogue and afterwards, it seems to work now. Had just a longer call.

 

There are a few messages left:

1    2022-03-29 19:15:54    DHCPC    Hinweis    Send DISCOVER with request ip 0.0.0.0 and unicast flag 1
2    2022-03-29 19:15:51    DHCPC    Hinweis    Send DISCOVER with request ip 0.0.0.0 and unicast flag 1
3    2022-03-29 19:15:40    VOIP    Hinweis    A flash writing operation is suspended by VoIP.

 

1	2022-03-29 19:56:19	VOIP	Hinweis	A flash writing operation is suspended by VoIP.
2	2022-03-29 19:54:25	DHCPC	Hinweis	Recv no OFFER, DHCP Service unavailable
3	2022-03-29 19:54:22	DHCPC	Hinweis	Send DISCOVER with request ip 0.0.0.0 and unicast flag 1
4	2022-03-29 19:54:19	DHCPC	Hinweis	Send DISCOVER with request ip 0.0.0.0 and unicast flag 1
5	2022-03-29 19:54:14	DHCPC	Hinweis	Send DISCOVER with request ip 0.0.0.0 and unicast flag 0
6	2022-03-29 19:54:11	DHCPC	Hinweis	Send DISCOVER with request ip 0.0.0.0 and unicast flag 0
7	2022-03-29 19:54:08	DHCPC	Hinweis	Send DISCOVER with request ip 0.0.0.0 and unicast flag 0

 

I do not know, whether this is harmful.

 

Again, thanks for the quick fix.

 

Best regards,

 

Skip