Looks like that issue patch made it in, but it wasn’t properly documented. Patch says it’s looking for overrideswitch=yes in the general section of extensions.conf.
I have folloving data in table
id context exten priority app appdata
1 menues 333 1 Goto menu1,s,1
3 menu1 s 1 Background /var/lib/asterisk/sounds/odeko/phrases/a19028bc4e3…
4 menu1 0 1 Dial Local/3001@inbound
And the only change in CLI output is that some new WARNINGs about ‘no such switch’ appeared:
[Jul 21 22:05:22] WARNING[22980]: pbx.c:2634 pbx_find_extension: No such switch ‘yes’
[Jul 21 22:05:22] WARNING[22980]: pbx.c:2634 pbx_find_extension: No such switch ‘yes’
[Jul 21 22:05:22] WARNING[23964]: pbx.c:2634 pbx_find_extension: No such switch ‘yes’
[Jul 21 22:05:22] WARNING[23964]: pbx.c:2634 pbx_find_extension: No such switch ‘yes’
– Executing [333@bypass_switch:1] Goto(“SIP/max_test-00000006”, “menu1,s,1”)
– Goto (menu1,s,1)
[Jul 21 22:05:22] WARNING[23964]: pbx.c:4812 __ast_pbx_run: Channel ‘SIP/max_test-00000006’ sent into invalid extension ‘s’ in context ‘menu1’, but no invalid handler
I feel that solution should be somewhere close but I can’t find it.