nebbin Posted April 19, 2018 Report Share Posted April 19, 2018 This suppose to be in place by April 26, 2018. We have registered and transferred our account... Is there anything else we need to do? What about download parameter from snom RDS Service - Moving to SRAPS? Newbie and need to know before deadline. Thanks, NE Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted April 23, 2018 Report Share Posted April 23, 2018 This seems to be essentially about the URL and the certificate that the PBX needs to trust. We have already changed it in 60.1 (test build) but it seems that the "old" way is still available. There was only a short time window when we had the chance the make the changes. We'll include it in the latest 60.0 version. Quote Link to comment Share on other sites More sharing options...
nebbin Posted April 25, 2018 Author Report Share Posted April 25, 2018 When is that to be released? I now understand the deadline is moved to May 6th... Quote Link to comment Share on other sites More sharing options...
Cld007 Posted April 30, 2018 Report Share Posted April 30, 2018 Hi guys, Can you confirm if versions prior to 60 will support the new Snom SRAPS redirection server? If not, will we still be able to use these versions for remote provisioning Snom handsets? Thank you. Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted April 30, 2018 Report Share Posted April 30, 2018 The 60.0.3 build will include the required changes. It is actually only a tiny change, the URL has slightly changed. And you will have to make sure that the letsencrypt root certificate is trusted, which is the case if you use the default certificates. Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted May 1, 2018 Report Share Posted May 1, 2018 We have now made 60.0.3 for CentOS, Debian and Windows the rest will follow today. Quote Link to comment Share on other sites More sharing options...
chrispopp Posted June 13, 2018 Report Share Posted June 13, 2018 Ignore plz Quote Link to comment Share on other sites More sharing options...
chrispopp Posted June 14, 2018 Report Share Posted June 14, 2018 Tried this, but it doesn't seem that the provisioning works. The reason is that it does not specify a Profile. Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted June 14, 2018 Report Share Posted June 14, 2018 Hard to say, looks like a problem in the SRAPS end. When registering a phone, the API returns "Ok" and shows the (unknown) provisioning profile. As far as we know there is no way to assign profiles through the API in snom SRAPS like Yealink does (http://wiki.snom.com/Category:HowTo:XMLRPC_Redirection#redirect.getPhoneRedirection). Quote Link to comment Share on other sites More sharing options...
chrispopp Posted June 14, 2018 Report Share Posted June 14, 2018 Wouldn't this make the service unusable? What's the point if we cannot redirect it back to our service? Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted June 18, 2018 Report Share Posted June 18, 2018 Well, we are not operating the snom redirection service. IMHO it would have been easier to keep everything backward compatible plus we don't see a reason why it cannot be backward compatible. Anyway we have to deal with the situation. Quote Link to comment Share on other sites More sharing options...
Cld007 Posted June 20, 2018 Report Share Posted June 20, 2018 Hi team, From your previous post, it sounds like SRAPS will not redirect the handsets back to the PBX. Instead it will serve the provisioning profile to the handset directly from SRAPS. Can you please confirm if this is correct? Thank you. Quote Link to comment Share on other sites More sharing options...
chrispopp Posted June 20, 2018 Report Share Posted June 20, 2018 From the logs it seems that the vodia send s the information correctly, it's the SRAPS that is not adding the profile... Opened a ticket with Snom and they don't seem to know where the problem is. Quote Link to comment Share on other sites More sharing options...
chrispopp Posted July 6, 2018 Report Share Posted July 6, 2018 Changed the API address for Snom to: https://provisioning.snom.com:8083/xmlrpc But it still does not work. [8] 15:29:45.217 PROV: RPS sub 000413XXXXXX [8] 15:29:45.217 PROV: Other request pending Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted July 8, 2018 Report Share Posted July 8, 2018 I would turn on logging for the web client to see the traffic between the PBX and SRAPS. 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.