In verto calls since yesterday, I've been able to hear only the first automated prompt played in a conference, even though the mp4 recording reveals later prompts were played. The first prompt I don't hear is at 18:38:58 (based on the clock of another machine in the same AWS cluster), that occurs between these lines from the FS log: 237113d5-a985-4527-9d2c-67a3681b5202 2019-11-12 18:37:27.385974 [DEBUG] switch_rtp.c:8187 Correct audio ip/port confirmed. 2019-11-12 18:40:00.685949 [ALERT] mod_verto.c:1411 READ ((public IP of FS)):60168 [{ "jsonrpc": "2.0", "method": "verto.bye", Our server has been handling calls well for months. It's FreeSWITCH Version 20.19.4-release-12-fc9d51c~64bit (-release-12-fc9d51c 64bit) on debian9. The call used a relay candidate from our coturn server, and its log shows nothing obviously wrong during this approximate period, but due to its lack of timestamps, it seems practically impossible to align its session info with FS's. I haven't found a way to relate ice IP numbers in the FS log with IP numbers in coturn's. Before I turn to the coturn mailing list for help, is there anything on the FS side you can suggest?