Lots of news on yealink site
http://www.yealink.com/News_info.aspx?Ne...ateId=1252 , but lack to solve this problem. It's a shame.
(11-09-2015 04:21 PM)tekstep Wrote: (10-31-2015 11:18 AM)support_badger Wrote: i never got tls working with freeswitch and t22p. I came here to see if there had been any developments as i never received a solution from yealink support/r&d. It's a shame, as the phone hardware is nice enough, priced right and running embedded linux. the firmware is too buggy to provide advertised features, which in some places is still considered fraud. Firmware quality and security features(ZRTP!!! wishlist'd here in 2013! works fine in csipsimple! ) along with strong community interaction should be at the top of the list. the freeswitch wiki and other similar projects' resources should be contributed to regularly by yealink community liasons. Why is using your product a research project that ends in disapointment? Why not just start a ip phone distro that the community can help yealink with and we can build and flash ourselves? Quit trying to use Free software for your product cuz it's fr$$ then use closed source dev practices and biz models to screw it up. Same mistakes many other companies have made/are making. do you sell hardware or software, FFS?
yealink keeps claiming it's our freeswitch config or a bug in freeswitch. If it's a bug with a major voip server, go freakin' report it, yealink! You sell the clients, FFS! Otherwise, fix your $%%^ firmware!
The problem has two ways of solving: either FS developers will fix bugs whith Yealink phones or Yealink developers will make firmware able to work with FS bugs. I doubt that any of FS team or Yealink wants to make extra work like bugreporting. For me it seems mutual fault in TLS+SRTP problems, because as I change FS config in a way not related to TLS at all - it starts working properly, but TLS in Yealink phones seems poor: only TLS1.0 support,strange behavior when validating certificates etc.
