File Routing
This section will explain the route an audio file takes and where it is copied to along the way. Understanding this process will assist you in troubleshooting.
Skip to:
Telephony Files
PcDictate II Files
Dss Extractor Pro Files
iNet 3
Telephony Files
If you have the telephony feature for your Phoenix Server, authors can create a dictation from any telephone. As soon as they connect and enter their user ID, a file is created locally on the Phoenix Server. Note that the VoiceSolutions root mentioned below is, by default, located on C:\ but can be installed on a different partition.
| upon login, Phoenix Recorder service creates a file it continuously writes to at | when dictation is complete, Phoenix Recorder service moves file to | Phoenix File Manager service creates file entry in database & moves file to | ||
 |
 |
|
|
 |
| VoiceSolutions\CVRS\Files | VoiceSolutions\Import | VoiceSolutions\Files |
PcDictate II Files
There are two ways to upload audio files from PcDictate II to the Phoenix Server. The first requires that the server and PcDictate II be on the same network. PcDictate II can then upload dictation files directly to the Import network share, from which it is then imported.
The second method is via HTTP/HTTPS, which allows uploading across the internet and also bypasses the local Windows network authentication (which could block access to the Import share because of inadequate user permissions). This process is shown below.
| when sent thru PcDictate II via HTTP, Apache2.2 service creates a file it continuously writes to at | when HTTP upload is complete, Apache2.2 service moves file to | Phoenix File Manager service creates file entry in database & moves file to | ||
|
|
|
|
|
| VoiceSolutions\Upload | VoiceSolutions\Import | VoiceSolutions\Files |
Dss Extractor Pro and DSS Files
There are two ways to upload audio files from Dss Extractor Pro to the Phoenix Server. The first requires that the server and Dss Extractor Pro be on the same network. Dss Extractor Pro can then upload dictation files directly to the Import network share, from which it is then imported.
The second method is via HTTP/HTTPS, which allows uploading across the internet and also bypasses the local Windows network authentication (which could block access to the Import share because of inadequate user permissions). This process is shown below.
| when sent thru Dss Extractor Pro via HTTP, Apache2.2 service creates a file it continuously writes to at | when HTTP upload is complete, Apache2.2 service moves file to | for conversion, Phoenix File Manager service moves file to | Phoenix DSS Converter service converts file to WAVE format | Phoenix File Manager service creates file entry in database & moves file to | ||||
|
|
|
|
|
|
 |
|
|
| VoiceSolutions\Upload | VoiceSolutions\Import | VoiceSolutions\DSS | VoiceSolutions\Files |
iNet 3
iNet 3 is a transcription application, so it does not upload files but downloads them. The process is shown below.
| dictation file stored at | upon request, Apache2.2 service sends file via HTTP(S) as chunks named 12345-Stream.wav to user's PC at | when finished, iNet's local copy of file is deleted & Phoenix database updated | ||
|
|
|
|
 |
| VoiceSolutions\Files | C:\Program Files\iNet 3\Temp | local copy deleted |
Go back to TABLE OF CONTENTS
