+- Yealink Forums (http://forum.yealink.com/forum)
+-- Forum: IP Phone Series (/forumdisplay.php?fid=4)
+--- Forum: General topics (/forumdisplay.php?fid=15)
+--- Thread: Multiple OpenVPN connections needed (/showthread.php?tid=613)
Pages: 1 2
RE: Multiple OpenVPN connections needed - Yealink Support - 04-24-2014 08:40 PM
I am sorry i can't help you in this problem. I think you can ask your distributor for help.
If they can't help you , they will ask the corresponding technical specialist for help.
Please don't remember to share with us if you have figured this out.
RE: Multiple OpenVPN connections needed - funchaser - 04-28-2014 12:35 AM
(04-24-2014 08:40 PM)Yealink Support Wrote: I am sorry i can't help you in this problem. I think you can ask your distributor for help.
If they can't help you , they will ask the corresponding technical specialist for help.
Please don't remember to share with us if you have figured this out.
Unfortunately, the distributor can't help, could you please pass my question to the Yealink's technical support? This is clearly an error in the phone's firmware. Here is extract from the phone's debug log:
ifconfig -
Quote:esw0 Link encap:Ethernet HWaddr 00:15:65:2A:33:72
inet addr:192.168.182.192 Bcast:192.168.182.255 Mask:255.255.255.0
inet6 addr: fe80::215:65ff:fe2a:3372/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1198 errors:0 dropped:0 overruns:0 frame:0
TX packets:926 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:180929 (176.6 KiB) TX bytes:618344 (603.8 KiB)
tun0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:10.8.3.197 P-t-P:10.8.3.198 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:49 errors:0 dropped:0 overruns:0 frame:0
TX packets:41 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:20026 (19.5 KiB) TX bytes:12176 (11.8 KiB)
The line one -
Quote:Apr 27 16:02:18 syslog[418]: REGISTER sip:192.168.182.230:5061 SIP/2.0^M
Apr 27 16:02:18 syslog[418]: Via: SIP/2.0/TLS 10.8.3.197:54384;rport;branch=z9hG4bK1643959849^M
Apr 27 16:02:18 syslog[418]: From: "First line" <sip:200@192.168.182.230:5061>;tag=1205994677^M
Apr 27 16:02:18 syslog[418]: To: "First line" <sip:200@192.168.182.230:5061>^M
Apr 27 16:02:18 syslog[418]: Call-ID: 1712982267@10.8.3.197^M
Apr 27 16:02:18 syslog[418]: CSeq: 1 REGISTER^M
Apr 27 16:02:18 syslog[418]: Contact: <sip:200@10.8.3.197:54384;transport=TLS>^M
Apr 27 16:02:18 syslog[418]: Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH, UPDATE, MESSAGE^M
Apr 27 16:02:18 syslog[418]: Max-Forwards: 70^M
Apr 27 16:02:18 syslog[418]: User-Agent: Yealink SIP-T32G 32.70.0.130^M
Apr 27 16:02:18 syslog[418]: Expires: 3600^M
Apr 27 16:02:18 syslog[418]: Content-Length: 0^M
Apr 27 16:02:18 syslog[418]: ^M
Apr 27 16:02:18 syslog[418]: (to dest=192.168.182.230:5061)
The line two -
Quote:Apr 27 16:02:18 syslog[418]: REGISTER sip:10.8.3.1:5061 SIP/2.0^M
Apr 27 16:02:18 syslog[418]: Via: SIP/2.0/TLS 10.8.3.197:9466;rport;branch=z9hG4bK1294991015^M
Apr 27 16:02:18 syslog[418]: From: "Second line" <sip:199@10.8.3.1:5061>;tag=220694478^M
Apr 27 16:02:18 syslog[418]: To: "Second line" <sip:199@10.8.3.1:5061>^M
Apr 27 16:02:18 syslog[418]: Call-ID: 868799650@10.8.3.197^M
Apr 27 16:02:18 syslog[418]: CSeq: 1 REGISTER^M
Apr 27 16:02:18 syslog[418]: Contact: <sip:199@10.8.3.197:9466;transport=TLS>^M
Apr 27 16:02:18 syslog[418]: Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH, UPDATE, MESSAGE^M
Apr 27 16:02:18 syslog[418]: Max-Forwards: 70^M
Apr 27 16:02:18 syslog[418]: User-Agent: Yealink SIP-T32G 32.70.0.130^M
Apr 27 16:02:18 syslog[418]: Expires: 3600^M
Apr 27 16:02:18 syslog[418]: Content-Length: 0^M
Apr 27 16:02:18 syslog[418]: ^M
Apr 27 16:02:18 syslog[418]: (to dest=10.8.3.1:5061)
The IP address 10.8.3.197 belongs to the tun0 interface, it is correctly reflected in the Register message from the Second line and incorrectly placed in the Register message from the First line, here should be 192.168.182.192 address of the esw0 interface!
RE: Multiple OpenVPN connections needed - Yealink Support - 04-28-2014 09:59 AM
Sorry. I consult my our engineer about this issue. He said that we don't support this scenario. All phone accounts will connect to VPN network.