From the 3CX notes, we know that voice recording file names have the following format.
DisplayName_Ext_DialedNum_YearMonthDayHourMinuteSecond.wav, where
DisplayName - caller name
Ext- caller Extension
DialedNum - called number
YearMonthDayHourMinuteSecond - time of the call
We have noticed that the position of the Ext in the file name changes for incoming and outgoing call recordings. For outgoing calls (calls made from the 3CX system to an external number) the format shown above seems to be used where the extension number comes before the dialled number and this seems to be consistent for all outgoing calls.
However, for most incoming calls the format is:
DisplayName_CallingNum_Ext_YearMonthDayHourMinuteSecond.wav
In these cases, the extension number comes after the calling number.
However for some other incoming calls, we are seeing:
DisplayName_Ext_CallingNum_YearMonthDayHourMinuteSecond.wav
So in this case the extension number comes before the calling number.
Our questions are:
Why is there sometimes for some incoming calls a reversal of where we would expect the the Ext to be located in the file name? It would seem logical if for all incoming calls the Ext comes after the calling number but this does not seem to be the case. We have seen this on both Windows and Debian systems!
We would like if it is possible to use the Ext position in the recording file name to indicate if the recording was an inbound or outbound call recording, but with the above differences, this does not seem possible or reliable.
Is there another way to identify the call recording direction from the recording file name?
If there is no reliable way to determine the direction of call recordings from the recording file names what other methods can be used.
DisplayName_Ext_DialedNum_YearMonthDayHourMinuteSecond.wav, where
DisplayName - caller name
Ext- caller Extension
DialedNum - called number
YearMonthDayHourMinuteSecond - time of the call
We have noticed that the position of the Ext in the file name changes for incoming and outgoing call recordings. For outgoing calls (calls made from the 3CX system to an external number) the format shown above seems to be used where the extension number comes before the dialled number and this seems to be consistent for all outgoing calls.
However, for most incoming calls the format is:
DisplayName_CallingNum_Ext_YearMonthDayHourMinuteSecond.wav
In these cases, the extension number comes after the calling number.
However for some other incoming calls, we are seeing:
DisplayName_Ext_CallingNum_YearMonthDayHourMinuteSecond.wav
So in this case the extension number comes before the calling number.
Our questions are:
Why is there sometimes for some incoming calls a reversal of where we would expect the the Ext to be located in the file name? It would seem logical if for all incoming calls the Ext comes after the calling number but this does not seem to be the case. We have seen this on both Windows and Debian systems!
We would like if it is possible to use the Ext position in the recording file name to indicate if the recording was an inbound or outbound call recording, but with the above differences, this does not seem possible or reliable.
Is there another way to identify the call recording direction from the recording file name?
If there is no reliable way to determine the direction of call recordings from the recording file names what other methods can be used.
