Bill Michaelson wrote:
A followup to my own inquiry...
pig*CLI feature show
Builtin Feature Default Current
--- --- ---
Pickup*8 *8
Blind Transfer# #
Attended Transfer
One Touch Monitor
Disconnect Call * *
Park Call
Dynamic Feature Default Current
--- --- ---
(none)
Call parking
Parking extension : 70
Parking context : parkedcalls
Parked call extensions: 71-79
I guess this narrows it down. So presumably, my feature code specs are
not finding their way into the process, but why? I'm looking, but
comments are most welcome.
There is a note in the features.conf sample which may answer this:
; Note that the DYNAMIC_FEATURES channel variable must be set to use the
features
; defined here. The value of DYNAMIC_FEATURES should be the names of the
features
; to allow the channel to use separated by '#'. For example:
;
;Set(DYNAMIC_FEATURES=myfeature1#myfeature2#myfeature3)
Did you remember to set the DYNAMIC_FEATURES variable? Something like:
exten = blah,n,Set(DYNAMIC_FEATURES=automon)
Mark Michelson
___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
AstriCon 2008 - September 22 - 25 Phoenix, Arizona
Register Now: http://www.astricon.net
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
