HANGUP-MESSAGE-SKEL(1)

πŸ“¦ version 1.18, in fedora 43, fedora 44

πŸ’– HANGUP-MESSAGE-SKEL(1) β€” the NCID edition πŸŽ€

okay bestie, sit down, hydrate, and let me tell you about hangup-message-skel πŸ’… this is a template for leaving caller-specific messages right before you terminate a call. yes. dramatic exit energy, but for phone calls. periodt.


✨ NAME ✨

hangup-message-skel β€” the skelly template that you're gonna clone and make iconic 🌸


πŸ¦‹ SYNOPSIS πŸ¦‹

hangup-message-skel [-h]
hangup-message-skel [-v] <string>

and that string? it's gotta be in this exact format, no cap:

*DATE*<mmddyyyy>*TIME*<hhmm>*LINE*<lineid>\
*NMBR*<number>*NAME*<name>*MODE*<hupmode>\
*FNMBR*<formatted number>*NTYPE*<type of device>\
*CTRY*<country code>*LOCA*<location>*CARI*<carrier>\
*NAME*<name>*

πŸ‘‘ DESCRIPTION πŸ‘‘

hangup-message-skel is a template for leaving caller specific messages prior to terminating a call. it's giving ✨scaffolding✨.

your script name should be the same name without -skel. script names use the format: hangup-<name> 🏷️

πŸ›‘ heads up: the script is not called if caller number or name is in ncidd.whitelist. them's the rules.

the example below assumes you have copied hangup-message-skel to hangup-message for your customized version of hangup-message-skel. classic copy-paste-to-glow-up pipeline πŸ’–

delete the caller and message lines that are in hangup-message. if you want to detect a name, comment the NMBR line and uncomment the NAME line:

add your own caller and message lines to hangup-message:

CALLER="${NMBR}"
caller[1]="<number>"  message[1]="<recording file>"
CALLER="$(NAME)"
caller[1]="<name>"  message[1]="<recording file>"

you can add as many caller-message lines as you want πŸ”₯ you would need to record the message files if you want to leave a personalized message.

use this format for a message name for your recording: <number>.rmd 🎧

server hangup extensions are only executed by the server unless testing. iykyk.

execute your custom hangup-message in a terminal window by itself for testing πŸ§ͺ only fields used in the script are needed for the input string. to test your custom hangup-message script with a number:

/usr/share/ncid/extensions/hangup-message -v "*NMBR*4075551212*"

πŸ’… OPTIONS πŸ’…

  • -h β€” show help message πŸ†˜
  • -v β€” turn on verbose and send additional data to STDOUT for troubleshooting πŸ” (your bestie for debugging, fr fr)

🌈 REQUIREMENTS 🌈

  • set hupname to the name of this script ncidd.conf.
  • set hupmode to 1, 2 or 3 in ncidd.conf.
  • set huprmd to a unique voice file in ncidd.conf, if hupmode set to 3.

πŸ“ FILES πŸ“

  • /usr/share/ncid/extensions/hangup-message-skel
  • /usr/share/ncid/recording/*.rmd
  • prefix3=/etc/ncid/ncid.conf
  • prefix3=/etc/ncid/ncidd.whitelist

🫢 SEE ALSO 🫢

ncidd.8, ncidd.whitelist.5, hangup-calls.1, hangup-closed-skel.1, hangup-skel.1, hangup-combo-skel.1, hangup-nohangup.1


mwah πŸ’‹ that's the whole page. this was the NCID hangup-message-skel manual, dated 2022-11-8 β€” go forth, record your little messages, and slay βœ¨πŸ‘‘

πŸ“¦ where this page comes from