You’re welcome but yes, looks like it doesn’t apply to your setup with the Cisco phones. Interesting you got another function (call flow rule) to light.
Parking Hints not showing InUse status, BLF won't light
Parking Hints not showing InUse status, BLF won't light
I’ve got every other status that I want to light (night mode, extensions in use, alternate voicemail boxes) bot for some reason it doesn’t appear like the parking lot module updates the hints.
Force IVR to ignore invalid user entries
Each IVR has an “invalid destination” (and a timeout destination), just send it back to the same IVR
Force IVR to ignore invalid user entries
But what I want is for the announcement to continue not stop and start again. Basically what I need is:
Caller calls - IVR starts announcement - Caller enters wrong extension - IVR continues like nothing happened - Caller enters correct extension - IVR transfers the call to the extension
Now, the last 2 parts I know how to do. The problem is in the first 3 parts
Force IVR to ignore invalid user entries
You would have to rewrite that part of the logic in the dialplan that currently returns an invalid entry to the IVR’s invalid destination. Likely a ‘gosub’ routine could do that, but human engineering would require you to let the caller know he ‘effed up’ and to retry , you would need to reset the timeout counter also.
Force IVR to ignore invalid user entries
When you say “rewrite that part of the logic in the dialplan” what do you mean?
A200 Analog Card Missing
Thank you for the reply. The ports have lights on them, would they be on if they weren’t seated properly?
Force IVR to ignore invalid user entries
You can rewrite any context of the dial plan as it comes from FreePBX and put that context in
/etc/asterisk/extensions_override_freepbx.conf
This is not trivial and takes quite a lot of RTFM’ing I suggest you start with
http://asterisk-service.com/downloads/Asterisk-%20The%20Definitive%20Guide,%204th%20Edition.pdf
the context you might want to override would start with
[ivr-n] ; yourivrname
and ends with
;--== end of [ivr-n] ==--;
in the /etc/asterisk/extensions_additional.conf
file
The bits you need to rewrite are the ones that start with
exten => i,1 . . . . .
most folks are happy with appropriate settings for the
Invalid Retries
Invalid Retry Recording
fields in the IVR
Force IVR to ignore invalid user entries
If I change it, won’t it change back when I save something in the GUI?
Force IVR to ignore invalid user entries
No that’s why you put it in the override file
/etc/asterisk/extensions.conf
;--------------------------------------------------------------------------------;
; Do NOT edit this file as it is auto-generated by FreePBX. All modifications to ;
; this file must be done via the web gui. There are alternative files to make ;
; custom modifications, details at: http://freepbx.org/configuration_files ;
;--------------------------------------------------------------------------------;
;*******************************************************************************
; AUTO-GENERATED AND CUSOTM USER DIALPLAN INCLUDED HERE *
;*******************************************************************************
;--------------------------------------------------------------------------------;
; Customizations to this dialplan should be made in extensions_custom.conf
; See extensions_custom.conf.sample for an example.
;
; If you need to use [macro-dialout-trunk-predial-hook], [ext-did-custom], or
; [from-internal-custom] for example, place these in this file or they will get overwritten.
;
; WARNING ABOUT: #include extensions_override_freepbx.conf
;
; This include file is put first to allow the auto-generated dialplan in FreePBX
; to be overwritten if necessary. Overriding auto-generated dialplan should be done
; with extreme caution. In almost all cases any custom dialplan SHOULD be put in
; extensions_custom.conf which will not hurt a FreePBX generated dialplan. In some
; very rare and custom situations users may have a need to override what FreePBX
; automatically generates. If so anything in this file will do that. If you come up
; with situations where you need to modify the existing dialplan or macros, put it
; here.
;
#include extensions_override_freepbx.conf
#include extensions_additional.conf
#include extensions_custom.conf
(and yes , yours is indeed a ‘very rare case’)
.
.
.
.
A200 Analog Card Missing
Probably not, but just to be on the safe side, try to reseat them. Only other possibilities are incorrect/missing wanpipe/DAHDI configuration or DOA card. Have you run the wanpipe initial setup script?
Force IVR to ignore invalid user entries
I think that if you use 0 in the invalid retries, it means infinite retries
Force IVR to ignore invalid user entries
From the dialplan’s ‘invalid’ extension (where the loop count was 5 and failover destination was rg 600)
exten => i,1,Set(INVALID_LOOPCOUNT=$[${INVALID_LOOPCOUNT}+1])
exten => i,n,GotoIf($[${INVALID_LOOPCOUNT} > 5]?final)
exten => i,n,Set(IVR_MSG=no-valid-responce-pls-try-again)
exten => i,n,Goto(s,start)
exten => i,n(final),Playback(no-valid-responce-transfering)
exten => i,n,Goto(ext-group,600,1)
so likely ${INVALID_LOOPCOUNT} would always be > 0 resulting in ‘once around the block’
I stand to be corrected of course.
A200 Analog Card Missing
Do you plugin the 12V power cable?
Endpoint Manager Grandstream Can't make or receive calls
Thanks for the response. Files are here:
https://pastebin.freepbx.org/view/5b794d84
https://pastebin.freepbx.org/view/0eb654aa
Unable to write to /etc/wanpipe/global.conf in overview in
in upper left corner of dashboard after new install. Getting Please change permissions on /etc/wanpipe/global.conf or disable Sangoma DIGIUM mode when expanding it. Tried searching and doing some of the suggestions and still getting the same error. Any help would be greatly appreciated.
thanks
AB
Sangoma S500 Phone Firmware
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
How does vage 200 gateway docking two FreePBX
Hello:
I want to know vage 200G gateway equipment docking two FreePBX
If so, how should I configure it?
Thank you!
Unable to write to /etc/wanpipe/global.conf in overview in
Try
fwconsole chown
Activate IVR by calling
Queues with *45, or Phone Apps, should pretty much do everything you want.