Jose P. Espinal
2010-Sep-20 16:01 UTC
[asterisk-users] Setting 'fname_base' variable doesn't affect 'automon' result file.
Hello List,
Maybe I'm mistaken, but, shouldn't the 'fname_base' variable of
'Monitor' application affect the file name generated through
'automon'
feature?
I initialized this variable with a value as follows:
Set(fname_base=auto-${CALLERID(num)}-${EXTEN}-${STRFTIME(${EPOCH},,%Y%m%d-%H%M%S)})
a. Should I use 'fname_base' in uppercase (FNAME_BASE)? or...
b. Is this variable independent of the 'automon' feature?
Thanks in advice,
PS.
version: Asterisk 1.4.33.1
OS: Slackware Linux 13.0
--
Jose P. Espinal
http://www.eSlackware.com
IRC: Khratos @ #asterisk / -doc / -bugs
Tilghman Lesher
2010-Sep-20 16:59 UTC
[asterisk-users] Setting 'fname_base' variable doesn't affect 'automon' result file.
On Monday 20 September 2010 11:01:36 Jose P. Espinal wrote:> Maybe I'm mistaken, but, shouldn't the 'fname_base' variable of > 'Monitor' application affect the file name generated through 'automon' > feature? > > I initialized this variable with a value as follows: > Set(fname_base=auto-${CALLERID(num)}-${EXTEN}-${STRFTIME(${EPOCH},,%Y%m%d-% >H%M%S)}) > > > a. Should I use 'fname_base' in uppercase (FNAME_BASE)? or... > b. Is this variable independent of the 'automon' feature?Where did you get the idea that fname_base is even a variable for you to set? It's always been a parameter to the Monitor application. -- Tilghman Lesher Digium, Inc. | Senior Software Developer twitter: Corydon76 | IRC: Corydon76-dig (Freenode) Check us out at: www.digium.com & www.asterisk.org
Maybe Matching Threads
- After wiki.asterisk.org was upgraded my user no loger exists.
- Extension notation in default ViciDial installation
- secret vs remotesecret on outgoing calls in Asterisk 1.6.2.16.1
- undefined symbol: cap_set_proc on several modules after installation from source
- Asterisk SlackBuilds for Slackware Linux