【Discussion】VOIP platform integrate with RPS

[jolouis]

Hi Karl,
We already implemented this with RPS several years ago when it was first launched. We configure devices on our Management portal, and the information automatically gets setup on RPS through the XML API.

What we did find is that although Yealink initially seemed to have great plans for RPS, it seems they built it "enough to work" and stopped any further development. It looks like you are now taking up control/efforts of that again which is great. The current XML API has a number of "gaps" in it that make it not a complete solution right now, it would be great to see those finally fixed.

A few examples:
a) In XML API, there is an option "redirect.listDevices" which lists all devices registered to your account. However the result does not tell you which server the device is associated with. Since our management is devided up by several config servers this is makes the results very difficult to process as we have to then search on our side to find which one.

Compared, in the web-gui when you view devices, there is a column that shows what server each device is associated with. Could that be put into the XML API?

b) In XML API there is no way to list defined servers... all you can do is "redirect.addServer" and if it fails, assume your server already exists. Again in web-gui it is very easy to list all defined servers.

Could some kind of "redirect.listServers" be created?

Finally, for us, something like "redirect.listDevicesForServer" would be very handy. Often our system knows the provisioning URL and is trying to check to see if devices have been setup in RPS for it. To do that in the current API is difficult as we have to:
1) call "redirect.addServer" and hope that it fails with "name exists".
2) Then call "redirect.listDevices" to get all devices on our RPS account
3) Then blindly call "redirect.registerDevice" with the found MAC and server, hoping that "Error Existing MAC" means things are correct.

Would be much better and more complete with those extra API methods I described...

Thanks,
-Rob