From 29bc7cf6b3d7bf28adc869d7ccbea08f0897d12d Mon Sep 17 00:00:00 2001
From: Nasir Iqbal <nasir@ictinnovations.com>
Date: Tue, 21 May 2019 11:38:24 +0500
Subject: [PATCH] app_amd: issue with silence suppression fixed
Now AMD algorithm will not ignore AST_FRAME_NULL, As I think using manual
wait time instead of `framelength` is enough to fix timeout / TOOLONG issue.
ASTERISK-28419 #close
Change-Id: I16ea2d6295bc99b975e8c092e5f9fbd9214debdb
---
apps/app_amd.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/apps/app_amd.c b/apps/app_amd.c
index 5285287bfb..1a0af3fa2d 100644
--- a/apps/app_amd.c
+++ b/apps/app_amd.c
@@ -293,7 +293,7 @@ static void isAnsweringMachine(struct ast_channel *chan, const char *data)
break;
}
- if (f->frametype == AST_FRAME_VOICE || f->frametype == AST_FRAME_CNG) {
+ if (f->frametype == AST_FRAME_VOICE || f->frametype == AST_FRAME_NULL || f->frametype == AST_FRAME_CNG) {
/* Figure out how long the frame is in milliseconds */
if (f->frametype == AST_FRAME_VOICE) {
framelength = (ast_codec_samples_count(f) / DEFAULT_SAMPLES_PER_MS);
--
GitLab