Join us on facebook 1-855-DAIRTEL (toll free 1-855-324-7835)
1-650-494-7081 (local tel)
email: DennisR@dair.com

DairTel Call Progress Messages

The issue: In the usual case, DairTel simply takes a phone message and transcribes it to text. However, there are a number of circumstances when there will will be no transcript when you check the message. One particularly ordinary case is the caller has not finished leaving their message. The transcript is not ready until the caller has hung up *and* the recording has completed analysis by the speech recognition engine.

State:A call passes through the following states: open, auto-answered, and transcript. A call is in the open state as soon as DairTel detects the phone ringing. The call enters auto-answered as soon as the caller hangs up. A short time later, the recording of the call is obtained. The recording is passed to the speech recognition engine and enters the transcript state when the speech recognition engine has completed its analysis.

DairTel may issue a call progress record in any of two later states. The chart below shows the state, message, and detail explanation:

state message detail
auto_answer (DairTel) caller has hung up. Waiting for mp3. If none, no message recorded. The call is over but the recording has not yet been received. DairTel always receives hangup status before it obtains the actual recording. So, for a few seconds, this is an expected status message. Once the recording is received, the message is replaced with transcript status.

After a minute or so, if this message is not replaced, there is no recording. A perfectly normal reason for no recording is that the caller did not leave a message.

transcript (DairTel) mp3 received. starting transcript. The recording is received and the recording is queued for analysis by the speech recognition engine. The engine listens to the recording in real time so the *minimum* time for the analysis is the duration of the recording. There could be other recordings needing analysis which are already queued for analysis and the time could be longer than minimum. Our typical response is under 5 minutes plus message duration.
transcript (DairTel) mp3 received. starting transcript. The recording is received and the recording is queued for analysis by the speech recognition engine. The engine listens to the recording in real time so the *minimum* time for the analysis is the duration of the recording. There could be other recordings needing analysis which are already queued for analysis and the time could be longer than minimum. Our typical response is under 5 minutes plus message duration.
transcript (DairTel) under 6 seconds long The speech recognition engine is unreliable with very short messages. The software detects when there is not enough possible speech recorded and provides this status rather than submit the recording for transcription. Recording has not been queued to speech recognition engine.
transcript (DairTel) could not start transcript. An unspecified problem prevented the recording from being submitted to the speech recognition engine. This is exceedingly rare and the instance which comes to mind is when mal-formed recording was received. Recording has not been queued to speech recognition engine.
transcript (DairTel) speech_not_detected. The speech recognition engine is unable to detect any intelligible speech. This often occurs when caller stays on the line but does not say anything. It has also been seen when there is music playing loudly, side conversations, or other sounds which prevent the speech recognition engine from performing an analysis.
transcript (DairTel) + more at end? The speech recognition engine has returned results. However, the results do not appear to cover the entire recording. The recording duration exceeds the duration of transcribed material. We recommend listening to the recording manually if partial transcript poses an issue.
transcript (DairTel) after fragment The agent has modified the ticket prior to completion of the transcript. DairTel messages always are written to fragment 1. If there are any higher fragment numbers in the ticket, this message notes the number at the time the transcript is written. This message is not necessarily an error but is provided so that the chronology of events is documented.