+- Yealink Forums (http://forum.yealink.com/forum)
+-- Forum: IP Phone Series (/forumdisplay.php?fid=4)
+--- Forum: General topics (/forumdisplay.php?fid=15)
+--- Thread: T38G 38.70.0.125 -> 38.70.0.132 IPv6 broken (/showthread.php?tid=730)
T38G 38.70.0.125 -> 38.70.0.132 IPv6 broken - bschmidt - 08-10-2013 12:15 AM
Hello,
I have a testing T38G that connects to my FreeSWITCH PBX with IPv6. This works just fine up to 38.70.0.125 (when you have figured out a few configuration knobs, VoIPv6 seems to be quite low priority for most vendors), but 38.70.0.132 does not work.
The phone registers just fine, call signalling works as well, but it does not seem to emit RTP packets. Therefor the line is dead. Downgrading fixes it.
Has anyone seen that as well? Is anyone actually using IPv6? :-)
Thanks,
Bernhard
RE: T38G 38.70.0.125 -> 38.70.0.132 IPv6 broken - Yealink Support - 08-16-2013 02:35 PM
Hi Bernhard,
You mean when you set IPV6 as Static IP Address on 38.70.0.125, everything works fine.
But when you set the same IPV6 as Static IP Address on 38.70.0.132, during the call, there's no any voice? But the account is register, and the can can also be made?
Did you try to reset to factory default?
Could you provide PCAP trace, syslog(level 6) and config.bin file from these two different firmware to us, so we can analyze?
Before you export the syslog, please set log level as 6, and reboot the phone, then click Start,and reproduce the issue, then click Stop,and export the trace, syslog, config,bin to us.
(About where to export these files, please refer to attached screenshot.)
These three files are very important for us, hope you can kindly understand.
Thanks.
RE: T38G 38.70.0.125 -> 38.70.0.132 IPv6 broken - bschmidt - 08-19-2013 11:32 PM
(08-16-2013 02:35 PM)Yealink Support Wrote: Hi Bernhard,
You mean when you set IPV6 as Static IP Address on 38.70.0.125, everything works fine.
But when you set the same IPV6 as Static IP Address on 38.70.0.132, during the call, there's no any voice? But the account is register, and the can can also be made?
Yes, that's correct. The phone pings, is registered, is accessible via HTTP and calls can be made. Just no audio.
(08-16-2013 02:35 PM)Yealink Support Wrote: Did you try to reset to factory default?
Could you provide PCAP trace, syslog(level 6) and config.bin file from these two different firmware to us, so we can analyze?
Before you export the syslog, please set log level as 6, and reboot the phone, then click Start,and reproduce the issue, then click Stop,and export the trace, syslog, config,bin to us.
(About where to export these files, please refer to attached screenshot.)
These three files are very important for us, hope you can kindly understand.
Sorry, no. The phone is broken at the moment, see my other thread at http://forum.yealink.com:81/forum/showthread.php?tid=737 . I have sent it to the distributor, as soon as I got a replacement I will try again.
BTW, are there any plans to get full IPv6 support? As far as I can tell there is not that much missing, just SLAAC (address autoconfiguration) and stateless DHCPv6. If you are afraid of regressions I would not mind a "global" IPv4-only/IPv6-only switch. Fully dual-stack would of course be preferred, but I have the feeling people are afraid of that.
Thanks,
Bernhard
RE: T38G 38.70.0.125 -> 38.70.0.132 IPv6 broken - Yealink Support - 08-21-2013 10:50 AM
Hi Bernhard,
Our V71 firmware will support dynamic IPV6(get IPV6 via DHCP), for T38G, the release date of V71 is still not confirm.
But our T2x V71 firmware will release at the early of next month, if you have T2x phones, you can have a test at that time.