1HANGUP-MESSAGE-SKEL(1) NCID HANGUP-MESSAGE-SKEL(1)
2
3
4
6 hangup-message-skel
7
9 hangup-message-skel [-h]
10 hangup-message-skel [-v] <string>
11
12 where string is in this format:
13 "*DATE*<mmddyyyy>*TIME*<hhmm>*LINE*<lineid>\
14 *NMBR*<number>*NAME*<name>*MODE*<hupmode>*"
15
17 Hangup-message-skel is a template for leaving caller specific messages
18 prior to terminating a call. Your script name should be the same name
19 without -skel. Script names use the format: hangup-<name>
20
21 The example below assumes you have copied hangup-message-skel to
22 hangup-message for your customized version of hangup-message-skel.
23
24 Delete the caller and message lines that are in hangup-message. If you
25 want to detect a name, comment the NMBR line and uncomment the NAME
26 line:
27
28 Add your own caller and message lines to hangup-message:
29
30 CALLER="${NMBR}"
31 caller[1]="<number>" message[1]="<recording file>"
32
33 CALLER="$(NAME)"
34 caller[1]="<name>" message[1]="<recording file>"
35
36 You can add as many caller-message lines as you want. You would need
37 to record the message files if you want to leave a personalized mes‐
38 sage.
39
40 Use this format for a message name for your recording: <number>.rmd
41
42 Server hangup extensions are only executed by the server unless test‐
43 ing.
44
45 Execute your custom hangup-message in a terminal window by itself for
46 testing. Only fields used in the script are needed for the input
47 string. To test your custom hangup-message script with a number:
48
49 /usr/share/ncid/extensions/hangup-message -v "*NMBR*4075551212*"
50
52 -h show help message
53
54 -v turn on verbose and send additional data to STDOUT for trou‐
55 bleshooting
56
58 /usr/share/ncid/extensions/hangup-message-skel
59 /usr/share/ncid/recording/*.rmd
60 /etc/ncid/ncidd.whitelist
61
63 ncidd.8, ncidd.whitelist.5, hangup-calls.1, hangup-closed-skel.1,
64 hangup-skel.1, hangup-combo-skel.1, hangup-nohangup.1
65
66
67
68NCID 2019-08-17 HANGUP-MESSAGE-SKEL(1)