Troubleshooting



Here are some of the most common issues and steps on how to troubleshoot them.

Skip to:
Files are not importing
Dictation is incorrectly listed as In Trans
Dictation is listed as Auxiliary
Dictation will not play and incorrectly shows up as 0 seconds long
DSS files are not being converted
iNet cannot connect
iNet cannot not open a dictation
Telephony channels are not answering


Files are not importing


This may be due to the Phoenix File Manager service crashing.





Dictation is incorrectly listed as In Trans


Files listed In Trans have been opened for playback, whether in iNet 3 or via telephony, but when closed Phoenix incorrectly left the dictation as In Trans. This can be fixed in Navigator or iNet.

From Navigator:

From iNet:





Dictation is listed as Auxiliary


This occurs when the audio file the database entry references can no longer be found. Although this can happen with a dictation that shows up as 0 seconds long, typically it's simply a case of Phoenix not updating the audio file's filename after a database change. Reimporting the dictation will resolve this.





Dictation will not play and incorrectly shows up as 0 seconds long


Whether the dictation shows the correct time in the Length field but doesn't play, or incorrectly shows up as 0 seconds in the Length field, the cause is a corrupt audio file. If the file was corrupted during recording, there is typically nothing that can be done. However, in most cases the original dictation is not corrupt and simply needs to be reimported.





DSS files are not being converted


This may be due to the Phoenix Dss Converter service crashing.





iNet cannot connect


This could be due to the Apache2.2 service crashing, TCP port being blocked by a firewall or security software, or a change in the server's or public IP address.

Apache Service Crashing: TCP Port Blocked: IP Address Change:



iNet cannot not open a dictation


This may be due to the Apache2.2 service crashing, or a corrupt/invalid dictation.

Apache Service Crashing: Corrupt/invalid dictation:



Telephony channels are not answering


This may be due to the Phoenix Recorder service crashing, or a single channel that stopped responding. First, you need to determine if all of the telephony channels are not responding, or if it is just one of them.

If just one telephony channel is not answering: If all telephony channels are not answering:



Skip to:
Files are not importing
Dictation is incorrectly listed as In Trans
Dictation is listed as Auxiliary
Dictation will not play and incorrectly shows up as 0 seconds long
DSS files are not being converted
iNet cannot connect
iNet cannot not open a dictation
Telephony channels are not answering


Go back to TABLE OF CONTENTS