We have a web application called Calabrio AQM that doesn't work for users outside of our network. AQM is a call recording platform we use in our call center to store recorded calls. There's apparently some limitation within AQM that involves hard-coded URLs which reference whatever IP is assigned to the AQM box. So, even if you NAT the server, at some point you're going to encounter these URLs that reference some internal IP.
I am hoping that by setting up a reverse-proxy, we'll be able to work around this limitation. So far, I've just done a simple test by proxying the default Nginix site installed on my Debian test box via the proxy_pass variable to send any inbound request to the default Nginix site over to the Calabrio AQM web server. It does actually send traffic to the AQM server, the web pages generally seem to render up fine. Certain URLs are not working, though and instead we get the internal IP of the server.
Also, when you access a call recording, the audio does not stream to the client via web browser. You can see the recordings, you can even click play to start playing back the recording and watch the progress needle move, but there's only silence.
I am not exactly sure how the media player embedded in to the AQM web interface works, but my guess is that it's somehow pointing to the internal IP of the server, because that is exactly what you see when you, say, select a recording to export--the URL that displays when you export a call is pointing back to the internal IP of the box.
Hopefully I've made sense here, but please feel free to ask questions for clarification. I was thinking that the URLs need to be re-written somehow but even that seems to be ignored. This problem is driving me nuts!
Thank you for any feedback :)
I am hoping that by setting up a reverse-proxy, we'll be able to work around this limitation. So far, I've just done a simple test by proxying the default Nginix site installed on my Debian test box via the proxy_pass variable to send any inbound request to the default Nginix site over to the Calabrio AQM web server. It does actually send traffic to the AQM server, the web pages generally seem to render up fine. Certain URLs are not working, though and instead we get the internal IP of the server.
Also, when you access a call recording, the audio does not stream to the client via web browser. You can see the recordings, you can even click play to start playing back the recording and watch the progress needle move, but there's only silence.
I am not exactly sure how the media player embedded in to the AQM web interface works, but my guess is that it's somehow pointing to the internal IP of the server, because that is exactly what you see when you, say, select a recording to export--the URL that displays when you export a call is pointing back to the internal IP of the box.
Hopefully I've made sense here, but please feel free to ask questions for clarification. I was thinking that the URLs need to be re-written somehow but even that seems to be ignored. This problem is driving me nuts!
Thank you for any feedback :)