Yealink Forums

Full Version: OpenVPN and DNS Servers
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Hi,

How are phones connected with OpenVPN supposed to work with DNS Servers?

My assumption was that the phone will first start to initiate an OpenVPN connection if possible. If successful and DNS servers are pushed by the OpenVPN server, the phone will use these DNS servers as the preferred over the DNS servers first received from the initial DHCP on the LAN.

Then these DNS servers pushed by OpenVPN will be used for resolution of

- Autoprovisioning Server
- SIP Server
- Outbound Proxy Servers

However I am finding that even connecting to OpenVPN the DNS servers pushed by DHCP are used for resolution of the above.

Could you please confirm this

I've tried this with a T40P

Firmware Version 54.82.0.20

also with a T23G

Firmware Version 44.82.0.20

Here are some of the settings I am using

auto_provision.dhcp_option.enable = 1
account.1.outbound_proxy_enable = 1
account.1.sip_server.1.address = sip.xxx.net
account.1.outbound_proxy.1.address = sipproxyc.xxx.net
account.1.outbound_proxy.2.address = sipproxyd.xxx.net
account.1.outbound_proxy.1.port = 0
account.1.outbound_proxy.2.port = 0
account.1.outbound_proxy.1.retry_counts = 3
account.1.outbound_proxy.1.invite_retry_counts = 3
account.1.outbound_proxy.1.register_on_enable = 1
account.1.outbound_proxy.2.register_on_enable = 1
account.1.outbound_proxy.1.only_signal_with_registered = 1
account.1.outbound_proxy.1.failback_mode = 3
account.1.outbound_proxy.1.failback_timeout = 60
account.1.outbound_proxy_fallback_interval = 60
account.1.outbound_proxy.1.failback_subscribe.enable = 1
account.1.sip_server.1.transport_type = 3
sip.use_out_bound_in_dialog = 0
account.1.outbound_port = 0

Thanks
(10-15-2017 08:58 PM)_DJ Wrote: [ -> ]Hi,

How are phones connected with OpenVPN supposed to work with DNS Servers?

My assumption was that the phone will first start to initiate an OpenVPN connection if possible. If successful and DNS servers are pushed by the OpenVPN server, the phone will use these DNS servers as the preferred over the DNS servers first received from the initial DHCP on the LAN.

Then these DNS servers pushed by OpenVPN will be used for resolution of

- Autoprovisioning Server
- SIP Server
- Outbound Proxy Servers

However I am finding that even connecting to OpenVPN the DNS servers pushed by DHCP are used for resolution of the above.

Could you please confirm this

I've tried this with a T40P

Firmware Version 54.82.0.20

also with a T23G

Firmware Version 44.82.0.20

Here are some of the settings I am using

auto_provision.dhcp_option.enable = 1
account.1.outbound_proxy_enable = 1
account.1.sip_server.1.address = sip.xxx.net
account.1.outbound_proxy.1.address = sipproxyc.xxx.net
account.1.outbound_proxy.2.address = sipproxyd.xxx.net
account.1.outbound_proxy.1.port = 0
account.1.outbound_proxy.2.port = 0
account.1.outbound_proxy.1.retry_counts = 3
account.1.outbound_proxy.1.invite_retry_counts = 3
account.1.outbound_proxy.1.register_on_enable = 1
account.1.outbound_proxy.2.register_on_enable = 1
account.1.outbound_proxy.1.only_signal_with_registered = 1
account.1.outbound_proxy.1.failback_mode = 3
account.1.outbound_proxy.1.failback_timeout = 60
account.1.outbound_proxy_fallback_interval = 60
account.1.outbound_proxy.1.failback_subscribe.enable = 1
account.1.sip_server.1.transport_type = 3
sip.use_out_bound_in_dialog = 0
account.1.outbound_port = 0

Thanks

Hi This is Kevin from Yealink support team, nice to know you.

If yealink phone connect openVPN, it suppoort to use DNS server which push by openVPN when resolute DNS-NATPR. So it should match your question.

For the issue, i need your kindly help provide PCPA, syslog, config.bin files with open.tar. to do more troubleshooting. Please reproduce the issue and export those files to me.
For how to export those files, you can refer to the FAQ: http://support.yealink.com/faq/faqInfo?id=311

BTW, may i know how many phones do you have and how many phones are affected.

BR
Kevin
Reference URL's