VOIP, vr900v, german ISP (1und1) just an engaged tone
VOIP, vr900v, german ISP (1und1) just an engaged tone
VOIP, vr900v, german ISP (1und1) just an engaged tone
2019-04-08 07:38:48 - last edited 2019-04-11 18:10:18
Model: Archer-VR900v
Hardware Version: V2
Firmware Version: Archer VR900v(DE)_V2_181108

I am having no luck with telephony/voip and a vr900v.
The VDSL network connection is OK with IPv4 over DS-Lite and apparently native IPv6.
I have a german provider (einsundeins/1und1) which is one of the known brands listed in the pull-down menu for telephony.
I have an old telephone connected.
Whenever I try a call, I get an engaged tone.
When I call myself, I am told that I am not reachable at the moment.

The telephone works fine if I reconnect my old modem (fritz 3692).
I check the connection from phone to vr900v. I have a dial tone and the fritz box knows the phone is there. I can use the dial codes to do things like switch WiFi on and off.
I check my dial-in authorisation using the old box. Everything is known and works.
I tried connecting to "1&1 Internet". There are not many parameters and not much room for mistakes.
I tried connecting to "others" and putting in parameters manually.

I went to the system log and set it to debug level. I see lots of confirmations every 10 seconds that PPP is alive, but absolutely nothing from VOIP. There are no authorisation rejections and no other error messages.

Now, I do not know where to look further.
What can I do, if there is no information in the system log and I cannot see an error message anywhere ?

0
0
#1
Options
1 Accepted Solution
Fixed: Re:VOIP, vr900v, german ISP (1und1) just an engaged tone-Solution
2019-04-11 18:09:42 - last edited 2019-04-12 07:09:55

The problem is fixed.

My ISP swapped me from DS-Lite to proper dual stack. The telephone worked immediately.

 

It is hard to say anything nice about TP-Link here.

DS-Lite was working in as much as most traffic was tunnelled properly. Browsing the web or ssh'ing worked fine.

SIP connections do not seem happy over DS-Lite.

Worse was the complete lack of diagnostics. Absolutely nothing in the system logs.

Best Solution
0
0
#3
Options
3 Replies
a bit more information Re:VOIP, vr900v, german ISP (1und1) just an engaged tone
2019-04-09 18:18:25

I have a bit more information. By switching handsets, I could get to some lines in the system log.

Can anybody interpret this ?

Every time I try to call, I get

Neu laden
Alle löschen
ID Uhrzeit Typ Ebene Information
1 2019-04-09 20:15:15 VOIP Debug port 2 dsp 2 rtp -1 int 0 cur -1 conf -1 cnt 0 back 0 data 0 cb 0 tone 6 cx -1 trans -1:49/6
2 2019-04-09 20:15:15 VOIP Debug port 2 dsp 2 rtp -1 int 0 cur -1 conf -1 cnt 0 back 0 data 0 cb 0 tone 7 cx -1 trans -1:68/6
3 2019-04-09 20:15:13 VOIP Debug port 2 dsp 2 rtp -1 int 0 cur -1 conf -1 cnt 0 back 0 data 0 cb 0 tone 0 cx -1 trans -1:69/1
 
0
0
#2
Options
Fixed: Re:VOIP, vr900v, german ISP (1und1) just an engaged tone-Solution
2019-04-11 18:09:42 - last edited 2019-04-12 07:09:55

The problem is fixed.

My ISP swapped me from DS-Lite to proper dual stack. The telephone worked immediately.

 

It is hard to say anything nice about TP-Link here.

DS-Lite was working in as much as most traffic was tunnelled properly. Browsing the web or ssh'ing worked fine.

SIP connections do not seem happy over DS-Lite.

Worse was the complete lack of diagnostics. Absolutely nothing in the system logs.

Best Solution
0
0
#3
Options
Re:Fixed: Re:VOIP, vr900v, german ISP (1und1) just an engaged tone
2019-04-19 06:55:12

Hi,

 

glad to hear that you solved it finally. Congrats. ^_^

 

And thanks a lot for your kindly feedback.

 

If need more help in the future, just let us know.

 

Nice day. 

mimble wrote

The problem is fixed.

My ISP swapped me from DS-Lite to proper dual stack. The telephone worked immediately.

 

It is hard to say anything nice about TP-Link here.

DS-Lite was working in as much as most traffic was tunnelled properly. Browsing the web or ssh'ing worked fine.

SIP connections do not seem happy over DS-Lite.

Worse was the complete lack of diagnostics. Absolutely nothing in the system logs.

 

0
0
#4
Options