pbx.c: Channel ‘Dongle/dongle0-0100000000’ sent to invalid extension but no invalid handler: context,exten,priority= custom-restart-server,restartserver,1
Daniel: I did the what you wrote (changed [custom-restart-server] and ( custom destination), The same. the call is hangup.
[2015-11-04 19:07:36] DTMF[1839][C-00000003] channel.c: DTMF begin ‘8’ received on Dongle/dongle0-0100000003
[2015-11-04 19:07:36] DTMF[1839][C-00000003] channel.c: DTMF begin ignored ‘8’ on Dongle/dongle0-0100000003
[2015-11-04 19:07:36] DTMF[1839][C-00000003] channel.c: DTMF end ‘8’ received on Dongle/dongle0-0100000003, duration 280 ms
[2015-11-04 19:07:36] DTMF[1839][C-00000003] channel.c: DTMF end passthrough ‘8’ on Dongle/dongle0-0100000003
Why are you not showing all the log? I do not need to see the DTMF. I need to know what is going on after you are pressing on the 8 digit.
From your previous log it seems that you do not change your custom destinations.
pbx.c: Channel 'Dongle/dongle0-0100000000' sent to invalid extension but
no invalid handler: context,exten,priority=custom-restart-server,restartserver,1
You should see something like that:
pbx.c: Channel 'Dongle/dongle0-0100000000' sent to invalid extension but
no invalid handler: context,exten,priority=custom-restart-server,8,1
Lorne, You right, my dialplan was good but with wrong sound file, I fix it and with a little change I can now restart the server from the IVR, BIG THANKS.
Daniel , Your dialplan didn’t work for me but thanks anyway.
You had a mistake in your custom destination name and in your audio file name. Your dial plan is bad and you should not write it in this style. Always keep a strict dial plan to avoid breaking to your pbx through the IVR. If you would have attached the logs to your post, I would have told you immediately that you had a mistake in your audio file name.
I took a second look at my dialplan sample and realize that I made a mistake during writing it. I have corrected it at the previous post and I am attaching it here again. It is a better approach to write it.
[custom-restart-server]
exten => _X!,1,Answer
same => n,Playback(agent-logoff)
same => n,Hangup()
Your dial plan fine, but you repeatedly miss your error; which is your advice to structure the Custom Destination. If we create a Custom Destination in the GUI then examine extensions_additional.conf, we will see content like this:
The part in parentheses on the goto line is the content of the field in the GUI for the custom destination. Note the extension “dest-6”, the user has no control over that, it is generated by FreePBX. Your advice to use ${EXTEN} as part of the Custom Destination and _X! for the dial plan won’t work because they will never match. I can’t envision any circumstance where it would be useful or correct to use ${EXTEN} in a custom destination.
Your first post to this thread has the misinformation, it has been edited twice and is still wrong. Please test and confirm for yourself. The op’s very first post had dial plan and a custom destination definition that work fine except for the sound file issue.
I am doing that for years and I think that you do not understand what I am doing.
Every time I need to bypass the Freepbx dial plan, this is the way I do it through the GUI.
I am writing my own context in the extension_custom.conf file and sending the channel to this context.
My mistake in the example I have provided was the typo of the same extension and that is why I have corrected it.
There is nothing wrong to learn something new once in while, so please have respect to other people experience.