Yealink Forums

Hello,

I always get an "Unknown URI scheme" when I dial a number via VPN with leading 0 (all national numbers here in Germany). This only happens with numbers with leading 0. All other numbers work.
This only happens, when VPN is active, I tested with

28.73.0.50.rom
28.73.193.50.rom
28.73.0.50.rom
T46-28.80.0.70.rom

Just to stress it; this only happens, when a number is dialled with the phone registred via VPN to the telephony server. When VPN is on, but the phone is registered to the PBX with the normal, local PBX IP, it's fine.

Phones Syslog shows:

Code:

Dec 10 22:22:15 sua [591]: DNS <3+error > [SIP] Query error: 'Domain name not found'

Dec 10 22:22:15 sua [591]: DNS <4+warnin> [SIP] Here query have no record, so try A query last time...

Dec 10 22:22:15 sua [591]: DNS <6+info  > [SIP] New query: type=1 class=1 target=060811234567

Dec 10 22:22:15 sua [591]: DNS <6+info  > [SIP] Query result: status=4

Dec 10 22:22:15 sua [591]: DNS <3+error > [SIP] Query error: 'Domain name not found'

Dec 10 22:22:15 sua [591]: SUA <3+error > [016] DNS resolver fail, unknown destination...

Dec 10 22:22:15 sua [591]: DLG <5+notice> [016] cb_transport_error (id=93)^M

Dec 10 22:22:15 sua [591]: DLG <6+info  > [016] cb_nict_kill_transaction (id=93)^M

Dec 10 22:22:15 sua [591]: SUA <6+info  > [016] ****eCore event:(0x0012)ECORE_CALL_REQUESTFAILURE        ****

Dec 10 22:22:15 sua [591]: CAL <6+info  > [016] call no response! cid 32781

So he tries to makes a DNS query to a DNS server with the phone number (for other phone numbers it does not) and fails.

In fact, when grepping traffic from the phone on the DNS server, I can see that the phone tries to resolve the phone number

Code:

U 192.168.178.109:44784 -> 192.168.178.215:53

J............_sip._udp.06081123456..!..

#

U 192.168.178.215:53 -> 192.168.178.109:44784

J............_sip._udp.06081123456..!............@.a.root-servers.net..nstld.verisign-grs.com.x.Ni..........:...Q.

#

U 192.168.178.109:44784 -> 192.168.178.215:53

.............06081123456.....

#

U 192.168.178.215:53 -> 192.168.178.109:44784

.............06081123456.............!.@.a.root-servers.net..nstld.verisign-grs.com.x.Ni..........:...Q.

For me, this seems to be a bug in the Firmwares. Yelaink: Please correct this, as my customer using this phone cannot dial any Germany national number.

Question: Is there a way to overcome this? Can we somehow disable DNS queries for this case? Maybe through Provisioning?

Hi,

Please send us the syslog(level=6) to us.

BTW, if the account register without VPN, can it dial number with leading 0?

stone198

Karl_Yealink