Rameshkumar 0 Posted November 30, 2018 Report Share Posted November 30, 2018 Hi, I've Cisco 504G and Cisco-CP-8851-3PCC both are registering on UDP and TCP but not on TLS. I've version 60.0.3 and TLS port is 5061. Please advise. Quote Link to post Share on other sites
Rameshkumar 0 Posted November 30, 2018 Author Report Share Posted November 30, 2018 I've Yealink and Grandstream they works on TLS as well but only Cisco is not working. Quote Link to post Share on other sites
Rameshkumar 0 Posted November 30, 2018 Author Report Share Posted November 30, 2018 I tested the same cisco phone on freepbx at TLS and it works perfect. Quote Link to post Share on other sites
Vodia PBX 0 Posted December 3, 2018 Report Share Posted December 3, 2018 Try to move to 62.0, we have made a lot of changes to get the 8851 working perfectly, including settings the button profiles from the PBX web interface. Quote Link to post Share on other sites
Rameshkumar 0 Posted December 3, 2018 Author Report Share Posted December 3, 2018 I tested it's not working on 62.0 as well. Please advise. Quote Link to post Share on other sites
Rameshkumar 0 Posted December 5, 2018 Author Report Share Posted December 5, 2018 Hi, any update please? Quote Link to post Share on other sites
Support 0 Posted December 5, 2018 Report Share Posted December 5, 2018 Its working on our server here. Make sure it's not a K9 model and only 3PCC. What do your TLS logs say from PBX admin level? Quote Link to post Share on other sites
Rameshkumar 0 Posted December 5, 2018 Author Report Share Posted December 5, 2018 I'm testing on SPA 504G, but not registering. TLS logs does not say anything, only SIP logs are like this; [7] 22:25:34.436 SIP: Connection from 100.166.172.19:5067 closed Also I tested the same phone on TLS on old version 3.4 and it works fine. Only after 3.4 upgrade till now it's not getting register. Quote Link to post Share on other sites
Rameshkumar 0 Posted December 5, 2018 Author Report Share Posted December 5, 2018 Just now I tested on CISCO CP-8851-3PCC, and attached are TLS logs. Please check. TLS Logs.txt Quote Link to post Share on other sites
Vodia PBX 0 Posted December 5, 2018 Report Share Posted December 5, 2018 Cisco by default trust only certificated issued by Cisco. You'll need to import the Root CA that has signed the PBX certificate - e.g. the letsencrypt Root CA. Quote Link to post Share on other sites
Rameshkumar 0 Posted December 5, 2018 Author Report Share Posted December 5, 2018 Hi, How can I import and where can I get the Cisco certificate. Quote Link to post Share on other sites
Vodia PBX 0 Posted December 6, 2018 Report Share Posted December 6, 2018 Well getting the certificate is not so easy - IMHO near impossible definitively impractical. We will add something to the next template that will try to provision the certificate along with the other information. Quote Link to post Share on other sites
Rameshkumar 0 Posted December 6, 2018 Author Report Share Posted December 6, 2018 You mean in next build you will add? Quote Link to post Share on other sites
Support 0 Posted December 6, 2018 Report Share Posted December 6, 2018 Yes ! Quote Link to post Share on other sites
Rameshkumar 0 Posted December 6, 2018 Author Report Share Posted December 6, 2018 Okay, thanks Quote Link to post Share on other sites
Vodia PBX 0 Posted December 6, 2018 Report Share Posted December 6, 2018 The PBX has to provision the Custom_CA_Rule - this is no big deal. However as fas as I can see the PBX domain name needs to be a read DNS address - in other words this will not work if the domain name is "localhost". Quote Link to post Share on other sites
Recommended Posts