Looks like a resurgence of the following bug: https://issues.asterisk.org/jira/browse/ASTERISK-17279 .. and this regression was caused by the fix for: https://issues.asterisk.org/jira/browse/ASTERISK-23818 Jeremy