Hi,
sure I can help you.
- Recording script:
1. recording = Recording
2. Upload prompt (language, promptName) // this uploads the prompt into the local repo
if successful:
3. Create an URL document to an URL, which is actually a HTTP trigger on the other IVR server. You may use the prompt file name as a HTTP GET parameter.
- Syncing script (on the other side):
1. get the HTTP parameters, most specifically, the prompt file name
2. issue a Create URL Document call to the URL of the prompt on the first side
3. Cache it for instant download
4. Upload to the local repo.
I don't know whether this is a security flaw, but the prompts are exposed as http://ipaddress:9080/Prompts/lang/dir/prompt.wav so it's easy to access them.
Screenshot (the relevant parts):
Side A recording script:
The URL explained: 10.232.130.36 is the Side B IVR server, 9080 the port, and /ahpsync12 is the HTTP trigger set up to trigger a script with the name of ahpsync12.aef on the side B IVR server.
Now, the ahpsync12.aef script:
Again, the script issues a Create URL Document step towards the IVR A server (10.232.128.62) and this sort of downloads the prompt from A's repository.
So IVR A actually triggers a (HTTP) script on the IVR B server which in turn downloads the prompt previously saved on IVR A using HTTP and uploads it into its own local (side B) repository.
Of course, there will be a pair of scripts, A calling B to sync and B calling A to sync, but all you need to do is just to change the URLs as appropriate.
G.
