GavinJ Posted June 7, 2021 Report Share Posted June 7, 2021 In the yealink_common provisioning template there is the following block: {if rps == "1"} # We still need to set the provisioning server auto_provision.server.url = {get http_scheme}{get http_host}/yealink-{mac}.cfg {elif https != "true" && model != "t38g" && provision_https == "true"} static.trusted_certificates.url = http://{get host}:{http-port}/yealink_cert.pem auto_provision.server.url = https://{get host}:{https-port}/yealink-{mac}.cfg {fi} We are seeing our new customers handsets that we setup with the Yealink RPS service not have the auto_provision url set, and therefor requests for the handsets to resync are failing because they don't have a provisioning URL. I think this needs to be changed to: {if rps == "1"} # We still need to set the provisioning server static.auto_provision.server.url = {get http_scheme}{get http_host}/yealink-{mac}.cfg {elif https != "true" && model != "t38g" && provision_https == "true"} static.trusted_certificates.url = http://{get host}:{http-port}/yealink_cert.pem static.auto_provision.server.url = https://{get host}:{https-port}/yealink-{mac}.cfg {fi} so that the phones are able to keep updating as required. There is also this block that I assume would need to be updated to have the "static." {if mac != ""} auto_provision.server.username = {mac} auto_provision.server.password = {mac-hash} {fi} I have updated the template on my server to reflect this, however, would be nice for this to be the default so I can leave the default template in place when new updates come through. Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted June 7, 2021 Report Share Posted June 7, 2021 We introduced the ups flag in the URL to tell the PBX to set the URL, so that for the re-sync the phones would not go to the RPS but to the PBX directly (which seems to to work beautiful for us). I was trying to read up on the static keyword with not much success... It sounds like there is a shadow configuration that the user can override? The provisioning guide mentions the static here and there but there is no explanation about it. Quote Link to comment Share on other sites More sharing options...
GavinJ Posted June 9, 2021 Author Report Share Posted June 9, 2021 The RPS flag all works perfectly for us too, it's just the filling of the "static" parameter. Without the "static" parameter, the provisioning URL isn't visible in the GUI of the Yealink handsets. Not sure if this might have been an intentional change on Yealink's behalf with newer firmware. Essentially what it looks like from what I can see is that if you don't have the "static" keyword, then the phone will request a provision from the URL once and then drop the url config. Which is where we run into trouble if we make a button layout change and then trigger a provision remotely the handset no longer has the provisioning settings. It was all working really well for us, it changed around about the version where it was discovered that Vodia needed to parse the Yealink config first. it was at that same time that we pushed out handset upgrades too, so I never took notice if they keyword had changed in the template or not. Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted June 22, 2021 Report Share Posted June 22, 2021 Lets try this out in the 67.1 branch and see if it causes any unwanted surprises! Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.