Answer the question
In order to leave comments, you need to log in
Where does __func_periodic_hook_context__ come from?
In /etc/asterisk only:
localhost*CLI> !ls /etc/asterisk
extensions.conf logger.conf modules.conf rtp.conf sip.conf
localhost*CLI> dialplan show
__func_periodic_hook_context__ local out phones
incoming
localhost*CLI> dialplan show __func_periodic_hook_context__
[ Context '__func_periodic_hook_context__' created by 'func_periodic_hook' ]
'beep' (CID match '') => 1. Answer() [func_periodic_hook]
2. Playback(beep) [func_periodic_hook]
'hook' (CID match '') => 1. Set(EncodedChannel=${CUT(HOOK_CHANNEL,-,1-2)}) [func_periodic_hook]
2. Set(GROUP_NAME=${EncodedChannel}${HOOK_ID}) [func_periodic_hook]
3. Set(GROUP(periodic-hook)=${GROUP_NAME}) [func_periodic_hook]
4. ExecIf($[${GROUP_COUNT(${GROUP_NAME}@periodic-hook)} > 1]?Hangup()) [func_periodic_hook]
5. Set(ChannelToSpy=${URIDECODE(${EncodedChannel})}) [func_periodic_hook]
6. ChanSpy(${ChannelToSpy},qEB) [func_periodic_hook]
-= 2 extensions (8 priorities) in 1 context. =-
Answer the question
In order to leave comments, you need to log in
Yes, I did not pay attention to the generated contexts - this functionality appeared. If you don't use it, feel free to disable it.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question