Re-enabled uuid_display found the real problem to the dtmf detection lag was caused by uuid_display with an incorrect rtp packet size (aka ptime) set wrong on the SPA504g. It was set to 0.030 but needs to be set to 0.020.

This commit is contained in:
Mark Crane
2013-08-20 23:54:46 +00:00
parent 57f1c145c7
commit bdd7ed37d8
2 changed files with 6 additions and 6 deletions
@@ -32,9 +32,9 @@
--flush dtmf digits from the input buffer
session:flushDigits();
--set the display
--if (session:ready()) then
-- reply = api:executeString("uuid_display "..session:get_uuid().." "..caller_id_number);
--end
if (session:ready()) then
reply = api:executeString("uuid_display "..session:get_uuid().." "..caller_id_number);
end
--say the message number
if (session:ready()) then
if (string.len(dtmf_digits) == 0) then
@@ -99,9 +99,9 @@
end
--set the display
--if (session:ready()) then
-- reply = api:executeString("uuid_display "..session:get_uuid().." "..destination_number);
--end
if (session:ready()) then
reply = api:executeString("uuid_display "..session:get_uuid().." "..destination_number);
end
--send back to the main menu
if (session:ready()) then