This is will not work. It’s a POTS/PRI CallerID setting. It’s not used in SIP.
If this is a SIP phone sending the call to Asterisk then the dialed digits are 811 (in this case) when it hits the dialplan it will be the ${EXTEN} variable and when you send it to the Macro() you need to send ${EXTEN} as the argument in the Macro call. So it would be more like
What I’d like to do is change it so that the entire code goes into from-internal-custom, but the FreePBX variable aren’t defined at that stage, so I’d have to use the Asterisk variables for everyone. I’m going to experiment with ${CALLERID(name)} and ${CALLERID(num)} to see if I can get the entire thing working there.
Where would the additional “exten => 811,1…” line that you’ve proposed go?
I do the occasional consult on emergency dialing. This is the framework I start with. It does not require that you anticipate dialed digits it only requires that the outbound call use a route that is marked as an emergency route:
[macro-dialout-trunk-predial-hook]
exten => s,1,Noop(Entering user defined context macro-dialout-trunk-predial-hook in extensions_custom.conf)
exten => s,n,GoSubIf($["${EMERGENCYROUTE}"="YES"]?to-emerg-custom,s,1)
exten => s,n,MacroExit
[to-emerg-custom]
exten => s,1,Noop(Entering user defined context to-emerg-custom in extensions_custom.conf)
; exten => s,n,dumpchan ; uncomment for debug
; additional dialplan lines as req'd
exten => s,n,Return
Per OP subject line, the Already Be Conferencing solution I assembled currently supports Email, SMS Text, Voicemail and Conference Call notifications (but not dashboard widget or - yet - paging, great idea!) More information in this other post. Latest version is from today v16f.