As a side note, if you already have RADIUS working with other tokens, there are two ways to get push tokens working as well. Note: neither of these will provide any feedback to the user beyond the request for the users PIN/tokencode. It will appear as if the authentication request has stalled until the user confirms on their device.
On the current release, you can set the push_wait within a policy to be the same length as your RADIUS request timeout (we have ours set to 60 seconds). This gives the user 60 seconds to respond to the push token before it times out.
If that option is not available in the version you are running, I have written an update to the RADIUS plugin that will poll the privacyIDEA installation while the push is in process. The pull request on the github page has this modification.
We have had success in our environment using both methods with our push tokens. But RADIUS must be working for at least software/hardware tokens first.