Error 503 with Sky Wifi Italy and Keenetic Linear

[Barin86]

Hi everyone, as I wrote in the title, I have a problem with the Keenetic Linear and the configuration of the VoIP with my provider Sky Wifi (Italy). I tried to select the provider in the list that the Keenetic Linear offer, but at the end there is only a 503 error (No answer record in the DNS response), I tried also to configure by myself selecting in the provider's list the item "Others" but I had always the same error. 

In the log I always read this line: 

pjsua_acc.c .Unable to create/send REGISTER: No answer record in the DNS response [status=320047]

I attach some pictures of the problem.

Thank you.

Edited December 7, 2022 by Barin86

[KYTECHNGAMING]

@sips will fully help you as it has helped me before.

I can recommend you to make sure that the ISS 5060 port is open. When I had similar situation @sips asked me to try with vpn routing. So I saw that Linear works with vpn. Then I requested the ISP to open the 5060 port. This is how I continued using Linear without VPN.

 

[sips]

21 hours ago, Barin86 said:

there is only a 503 error (No answer record in the DNS response)

Keenetic Phone Station application (hereafter, the app) performs DNS SRV resolution for the SIP proxy domain name, which is “voip.it.isp.sky” in our case. If DNS SRV resolution returns an error, the app tries to perform DNS A resolution for the SIP proxy domain name. If DNS A resolution returns a error as well, we'll see the error 503 like shown on your screenshot. Therefore, in your case we have a DNS resolution issue, the app can’t get the IP address of the SIP proxy.

In order to verify DNS resolution, please execute the following commands in the command prompt on your PC connected to the internet via your Keenetic Hero DSL to which USB port the Keenetic Linear is plugged. I assume that you have a PC powered by MS Windows OS. In case your PC is powered with OS Linux, the command specified below will be the same, but the outputs will look slightly different from those given in the examples.

 

1. Check the ability to get DNS A records to resolve domain names into IPv4 addresses:

Command: nslookup -type=A google.com

Example:

C:\Users\sips>nslookup -type=A google.com

Address:  192.168.1.1

Non-authoritative answer:

    google.com

Addresses:  108.177.14.138

          108.177.14.100

          108.177.14.102

          108.177.14.101

          108.177.14.113

          108.177.14.139

 

2. Check the ability to get DNS AAAA records to resolve names into IPv6 addresses:

Command: nslookup -type=A google.com

Example:

C:\Users\sips>nslookup -type=AAAA google.com

Address:  192.168.1.1

Non-authoritative answer:

     google.com

Addresses:  2a00:1450:4010:c0f::8a

          2a00:1450:4010:c0f::65

          2a00:1450:4010:c0f::66

          2a00:1450:4010:c0f::71

 

3. In case of succes on the previous steps, check the DNS SRV record for the domain name “voip.it.isp.sky”
Command: nslookup -type=SRV _sip._udp.voip.it.isp.sky

Right now, I have no abilities to get DNS SRV record for the “voip.it.isp.sky”, this is why below there is an
example with another domain name:
C:\Users\sips>nslookup -type=SRV _sip._udp.sip.1und1.de

Address:  192.168.11.1

Non-authoritative answer:

_sip._udp.sip.1und1.de  SRV service location:

          priority       = 0

          weight         = 0

          port           = 5060

          svr hostname   = 1und1-1.sip.1und1.de

_sip._udp.sip.1und1.de  SRV service location:

          priority       = 1

          weight         = 0

          port           = 5060

          svr hostname   = 1und1-2.sip.1und1.de

In the output above, you can see two host names:  “1und1-1.sip.1und1.de” and “1und1-2.sip.1und1.de”. In case you successfully get DNS SRV for “voip.it.isp.sky”, the  hostnames will be different.

 

4. If you successfully get DNS SRV on the previous step, check DNS A record for the hostname with the priority 0 from the output you got on the previous step.
Command: nslookup -type=A hostname
In the above command,  replace “hostname” with the hostname from the output you got on step 3.
Example:

C:\Users\sips>nslookup -type=A 1und1-2.sip.1und1.de

Address:  192.168.1.1

Non-authoritative answer:

     1und1-2.sip.1und1.de

Addresses:  212.227.124.129

          212.227.124.130

In the above output we see two IPv4 addresses to which the hostname resolves.

 

5. If you successfully get DNS SRV earlier, check DNS AAAA. Execute the command “nslookup -type=AAAA hostname”, replace “hostname” with the hostname from the output you got on step 3.
Example:

C:\Users\sips>nslookup -type=AAAA 1und1-2.sip.1und1.de

Address:  192.168.1.1

Non-authoritative answer:

     1und1-2.sip.1und1.de

Addresses:  2001:8d8:104:100:212:227:124:129

          2001:8d8:104:100:212:227:124:130

In the above output, we see two IPv6 addresses to which the hostname resolves.

 

6) If you didn’t get the DNS SRV record for the domain name “voip.it.isp.sky” on step 3, try to get DNS A and AAAA records.
Commands:
nslookup -type=A voip.it.isp.sky
nslookup -type=AAAA voip.it.isp.sky
 

 

After performing the above steps 1-6, share the output of the commands, please.

 

[Barin86]

I tried but I stopped at the 3rd point 

C:\Users\mamba>nslookup -type=A google.com
Server:  UnKnown
Address:  fe80::52ff:20ff:fe6f:49e8

Risposta da un server non autorevole:
Nome:    google.com
Address:  142.250.184.78


C:\Users\mamba>nslookup -type=AAAA google.com
Server:  UnKnown
Address:  fe80::52ff:20ff:fe6f:49e8

Risposta da un server non autorevole:
Nome:    google.com
Address:  2a00:1450:4002:405::200e


C:\Users\mamba>nslookup -type=SRV _sip._udp.voip.it.isp.sky
Server:  UnKnown
Address:  fe80::52ff:20ff:fe6f:49e8

*** UnKnown non è in grado di trovare _sip._udp.voip.it.isp.sky: Non-existent domain

What is curious is that if I put a Fritzbox as client and I configure the voip with the fritzbox itself, all works perfectly.

[sips]

56 minutes ago, Barin86 said:

if I put a Fritzbox as client and I configure the voip with the fritzbox itself, all works perfectly

Please, repeat the steps 1-6 described above when your PC accesses the Internet via your FRITZ!Box router.

And, when you change to your Keenetic Hero DSL back, collect the diagnostic info:

1) open the web configurator of your Keenetic, go to Management>Diagnostics>Debug, click “Restart system in debug mode”;

2) wait for 1 minute;

3) click “Stop debugging”;

4) download the file self-test_xxxxx.txt and attach it here with your next post.

[Barin86]

The fritz!box is plugged to the keenetic because the fritzbox at the moment does not support the MAP-T protocol, so I tried to connect the FritzBox to the Keenetic Hero DSL and I configured only the VoIP section of the FritzBox that doesn't asked me parameters but only the phone number userID and Password, because I think it's pre-configured.

Days before I tried to ask also on an Italian forum and an user do this: https://forum.fibra.click/d/35411-problema-configurazione-linea-telefonica-sky-con-keenetic-linear/25

But I tried to replicate what he did but without the same result, I can't arrive to record AAAA like him.

Edited December 8, 2022 by Barin86

[sips]

20 hours ago, Barin86 said:

I tried to replicate what he did but without the same result, I can't arrive to record AAAA like him

Can you, please, check if you can get SRV and AAAA like in the following example?

 

$ nslookup -type=SRV _sip._udp.voip.glb.it.isp.sky
Server:        127.0.0.53
Address:    127.0.0.53#53

Non-authoritative answer:
_sip._udp.voip.glb.it.isp.sky    service = 20 10 5060 sbc.mica1.voip.glb.it.isp.sky.
_sip._udp.voip.glb.it.isp.sky    service = 40 10 5060 sbc.rmle1.voip.glb.it.isp.sky.
_sip._udp.voip.glb.it.isp.sky    service = 30 10 5060 sbc.mid41.voip.glb.it.isp.sky.

$ nslookup -type=AAAA sbc.mica1.voip.glb.it.isp.sky
Server:        127.0.0.53
Address:    127.0.0.53#53

Non-authoritative answer:
Name:    sbc.mica1.voip.glb.it.isp.sky
Address: 2a0e:402:100:200::7

$ nslookup -type=AAAA sbc.rmle1.voip.glb.it.isp.sky
Server:        127.0.0.53
Address:    127.0.0.53#53

Non-authoritative answer:
Name:    sbc.rmle1.voip.glb.it.isp.sky
Address: 2a0e:402:100::7

$ nslookup -type=AAAA sbc.mid41.voip.glb.it.isp.sky
Server:        127.0.0.53
Address:    127.0.0.53#53

Non-authoritative answer:
Name:    sbc.mid41.voip.glb.it.isp.sky
Address: 2a0e:402:100:300::7
 

[Barin86]

@sips I tried with the fritzbox connected with the keenetic Hero DSL and it works, but with the linear no.

This is the result with the fritzbox connected with the keenetic:

C:\Users\mamba>nslookup -type=SRV _sip._udp.voip.glb.it.isp.sky
Server:  UnKnown
Address:  fe80::52ff:20ff:fe6f:49e8

Risposta da un server non autorevole:
_sip._udp.voip.glb.it.isp.sky   SRV service location:
          priority       = 10
          weight         = 10
          port           = 5060
          svr hostname   = sbc.mica1.voip.glb.it.isp.sky
_sip._udp.voip.glb.it.isp.sky   SRV service location:
          priority       = 20
          weight         = 10
          port           = 5060
          svr hostname   = sbc.mid41.voip.glb.it.isp.sky
_sip._udp.voip.glb.it.isp.sky   SRV service location:
          priority       = 30
          weight         = 10
          port           = 5060
          svr hostname   = sbc.rmle1.voip.glb.it.isp.sky

C:\Users\mamba>nslookup -type=AAAA sbc.mica1.voip.glb.it.isp.sky
Server:  UnKnown
Address:  fe80::52ff:20ff:fe6f:49e8

Risposta da un server non autorevole:
Nome:    sbc.mica1.voip.glb.it.isp.sky
Address:  2a0e:402:100:200::7


C:\Users\mamba>nslookup -type=AAAA sbc.rmle1.voip.glb.it.isp.sky
Server:  UnKnown
Address:  fe80::52ff:20ff:fe6f:49e8

Risposta da un server non autorevole:
Nome:    sbc.rmle1.voip.glb.it.isp.sky
Address:  2a0e:402:100::7


C:\Users\mamba>nslookup -type=AAAA sbc.mid41.voip.glb.it.isp.sky
Server:  UnKnown
Address:  fe80::52ff:20ff:fe6f:49e8

Risposta da un server non autorevole:
Nome:    sbc.mid41.voip.glb.it.isp.sky
Address:  2a0e:402:100:300::7

 

Edited December 9, 2022 by Barin86

[PasKy]

Ciao Barin86, scusa se intervengo in Italiano, ma forse qualche incomprensione dovuta alla lingua,

ma sembra ti abbia chiesto di dare i comandi senza passare per il Fritz, ma solo con l'Hero DSL e Linear

inviando anche il file Debug della diagnostica, diversamente potrebbe non arrivare ad una diagnosi oggettiva

sull'esistenza di un reale problema sul linear, o ad errata configurazione dei parametri o qualsiasi altra cosa sia.

 

P.S. Certo che "Murdoch" continua a complicarci la vita, prima sul satellite, ora come fornitore di servizi ISP., se non rendeva complicato anche questo non riusciva a grattarsi le chiappe!

 

ENG. TRANSLATE-----

 

Hello Barin86, sorry if I intervene in Italian, but perhaps some misunderstanding due to the language,

but it seems he asked you to give the commands without going through the Fritz, but only with the Hero DSL and Linear

also sending the diagnostic Debug file, otherwise it may not arrive at an objective diagnosis

on the existence of a real problem on the linear, or a wrong configuration of the parameters or whatever it is.

P.S. Of course "Murdoch" continues to complicate our lives, first on satellite, now as an ISP service provider. If he didn't make it complicated, he couldn't scratch his ass!

 

 

Edited December 10, 2022 by PasKy