I made some progress over the weekend. I imported the WSDL's into SoapUI, and that helped me iron out any formatting issues in the requests. As far as DownloadNBRStorageFile timing out on me, I think SoapUI and Postman are just not built for files that size. I was able to fix this in Python by streaming the http request and writing it to a file in chunks.
I have made it to the point where I have a python script that retrieves the storage access ticket, and then uses that ticket to download the file. However, I am having difficulty parsing the response. I get 3 pieces of content in the response
1) XML listing the Content-ID's of the two files
2) The file containing the recordings file name and RecordID
3) The actual .arf file
After I download it, I can open it in a text editor and take out all of the content ID headers so that there is only binary left in the file, and after I do that it will open in the ARF player. It would be best if I could find a way to parse the header info and just write two files as intended. But I am not sure the best way to go about it.
----EDIT----
I've got something that is working in my tests, but I'm sure there has to be a better way to do this. I am downloading everything into one file, reopening the file, splitting it based on matching a series of two carriage returns and new lines, then rewriting the 4th part of the split into a new file and deleting the old one. I don't feel really good about it because if the formatting for the http response is off by a little it could hose the whole script. I will work on it more later. Uploading the files for where I am now with it.
