Hi, the list of created mountpoints doesn’t include the details of each one (for example the port on which it is listening), while they are present in the info request.
In my opinion they would also be useful in the list request, obviously protecting the most sensitive data with admin_key.
If it makes sense in your opinion, I can start working on it.
We have explictly kept list as lightweight as possible, since a server may have a ton of mountpoints configured. I’d rather keep any per-mountpoint specific detail to info only.
Thanks Lorenzo for your feedback.
It would have been useful for me to have the listening port in the list request to find a free port when creating a new mountpoint without having to save ports in use elsewhere.
A more specific response might be useful when creating a mountpoint on a port already in use, rather than “456 Can’t add ‘rtp’ stream, error creating audio source stream”.
Have a nice day
Makes sense, I’ll see if there’s an easy way to do that, as it may require changing some internal signatures to bobble up the actual reason for a failure.