voice.conf

embedded xLinux root 5.4

# Program specific initializations
# --------------------------------
#

#
# Default values for vgetty
# -------------------------
#

program vgetty

#
# Default number of rings to wait before picking up the phone.
#
# Instead of a number, you can also give a file name, that contains
# a single number with the desired number of rings. Vgetty will
# automatically append the name of the modem device to the file name.
# The file name must be an absolut path starting with a leading "/".
# E.g. "rings /etc/rings" and the modem device is ttyS0, will
# lead to the file name "/etc/rings.ttyS0". If this file doesn't
# exist, vgetty will check for a file without the modem device name
# appended. In this example, vgetty would check for /etc/rings.
#
# Please note, that vgetty forces the number of rings to be at least 2.
# This is, because the caller ID information (if available from your
# provider) is sent between the first and the second ring. Since we don't
# know in advance, if you get CID or not, we stay on the save side.
#
# If you have compiled mgetty/vgetty with CNDFILE defined in policy.h
# then you must use the comandline option -n explained in `man mgetty`
# The default is 3
#

rings 3

#
# Default answer mode when vgetty picks up the phone after incoming
# rings.
#
# Instead of an answer mode, you can also give a file name, that
# contains a single line with the desired answer mode. Vgetty will
# automatically append the name of the modem device to the file name.
# The file name must be an absolut path starting with a leading "/".
# E.g. "answer_mode /etc/answer" and the modem device is ttyS0, will
# lead to the file name "/etc/answer.ttyS0". If this file doesn't
# exist, vgetty will check for a file without the modem device name
# appended. In this example, vgetty would check for /etc/answer.
#
# The default is "voice:fax:data".
#

answer_mode voice:fax:data

#
# When switching to data or fax mode, always switch to fax mode and
# enable autodetection of data/fax. Some modems report wrong DLE codes
# and so the predetection with DLE codes does not work.
#

force_autodetect false

#
# If vgetty knows that there are new messages (the flag file exists),
# it will turn on the AA lamp on an external modem and enable the toll
# saver - it will answer the phone TOLL_SAVER_RINGS earlier than the
# default. This feature is turned off by default.
#

toll_saver_rings 0

#
# Should the recorded voice message file be kept even if data, fax or
# DTMF codes were detected? If this is set, vgetty never deletes
# a recording, if it is not set it will delete the recording, if an
# incoming data or fax call is detected or if DTMF codes were send. Also
# this should work in nearly every situation, it makes you loose the
# recording, if the caller "plays" with DTMF codes to make the message
# even more beautiful. This feature is enabled by default.
#

rec_always_keep true

#
# The programs defined below get called by vgetty.
#
# Define an empty program name, if you want to disabled one of those
# programs.
#

#
# There are two separate uses for the Data/Voice button on a ZyXEL:
#
# - If a RING was detected recently, answer the phone with the
#   answer mode set for this case.
# - Otherwise, call an external program to play back messages
#
# If you don't define button_prgogram, vgetty will always pick up
# the phone if Data/Voice is pressed.
#
# The default value is "".
#

button_program

#
# Program called when the phone is answered, this is instead
# of the normal behaviour. Don't define this unless you want
# to e.g. set up a voice mailbox where the normal answering
# machine behaviour would be inappropiate. The C code is probably
# more stable and uses less resources.
#
# The default value is "".
#

call_program

#
# Program called when a DTMF command in the form '*digits#' is received.
# The argument is the string of digits received (without '*' and '#').
# The default value is "dtmf.sh".
#

dtmf_program dtmf.sh

#
# Program called when a voice message has been received.
# The argument is the filename of the recorded message.
# The default value is "".
#

message_program

#
# Should vgetty use the AA LED on some modems to indicate that new
# messages have arrived? This is done by setting the modem register
# S0 to a value of 255. Some modems have a maximum number of rings
# allowed and autoanswer after this, so they can not use this feature.
# This option is by default off.
#

do_message_light false

#
# * ring_report_delay:
# * This value determines the delay in /10 seconds between the falling edge
# * of the ring-signal (DRON response) and the RING response.
# * This value should be greater than the expected off-time within a distinctive
# * ring (DROF response). So says the ITU V.253, but it seems that
# * ring_report_delay should be greater than the mentioned DROF AND the following
# * DRON, and shorter than the long DROF!
#Example with ring_report_delay = 10 (2/10 sec per char):
#           ^
#ring-pulse | ...____###__##_______###__##_______###__##______....
#                      | | |    | |  | | |    | |  | | |
#                      DRON=6        DRON=6        DRON=6
#                        DROF=4        DROF=4        DROF=4
#                          DRON=4        DRON=4        DRON=4
#                               RING          RING
#                                 DROF=14       DROF=14
#                                                    time --->
#
# Default is 15 (1.5 sec)
#
ring_report_delay 15



#
# Default values for vm
# ---------------------
#

program vm

#
# Voice devices that vm can use e.g. "voice_devices ttyS0:ttyS1". Since
# I don't know to which ports your modems are connected, the default is ""
#

voice_devices

#
# Timeout for a dialout operation in seconds. The default is 90 seconds.
#

dialout_timeout 90

#
# Timeout for deciding that a dialout call has been answered; if more
# than this many 1/10ths of a second have passed since the last ringback,
# the modem assumes the call has been answered.  Default is 70 (7 sec).
#

ringback_goes_away 70

#
# Timeout for deciding that a dialout call has been answered; if more
# than this many 1/10ths of a second have passed without any ringback
# the modem assumes the call has been answered.  Default is 100 (10 sec).
#

ringback_never_came 100

#
# Default values for the pvf tools
# --------------------------------
#

program pvf

#
# There are currently no defaults.
#

#
# Port specific configuration
# ---------------------------
#

#
# Here you can optionally set some of the previously set values to different
# ones for specific ports.
#
# E.g. we have a modem on port ttyS0
#

port ttyS0

#
# And we want it to answer after the first ring and only in data mode.
# So we would define:
#
#  rings 1
#  answer_mode data
#
# The commands are commented out, because I don't want to set some port
# specific defaults in this sample configuration file. I just want to
# show you how to do it.
#
# Now we set the values for the next port e.g. ttyS5
#

port ttyS5

#
# And so on for all ports in the system, that need special treatment.
#

#
# Ring type specific configuration
# --------------------------------
#

#
# Here you can optionally set some of the previously set values to different
# ones for specific ring types. The following ring types are possible:
#
# ring     - for a normal ring
# ring1    - for distinctive ring number 1
# ring2    - for distinctive ring number 2
# ring3    - for distinctive ring number 3
# ring4    - for distinctive ring number 4
# ring5    - for distinctive ring number 5
# virtual  - for a virtual ring (kill -USR1 <mgetty pid>)
# button   - if someone pressed the data/voice button on the modem
#
# Note: The current mgetty implementation maps the data/voice button
# event to a virtual ring event.
#
# Note: ISDN MSNs will be mapped to distinctive rings in the future.
#
# E.g. we want to answer the modem on a virtual ring with answer
# mode "fax:data".
#

ring_type virtual

answer_mode fax:data

#
# Or e.g. we have one modem and want to answer with voice on a normal
# ring and with fax:data on distinctive ring1.
#

ring_type ring

# rings 6
# answer_mode voice

ring_type ring1

# rings 1
# answer_mode fax:data
#
# The commands are commented out, because I don't want to set some ring
# specific defaults in this sample configuration file. I just want to
# show you how to do it.
#
# Note: Setting the number of rings will have no effect until the mgetty
# to vgetty interface is changed.
#
# Note: If you have one modem and distinctive ring, you can simply define
# the answer mode directly in this file for the different rings. If you
# have more than one modem and you want them to react different on the same
# type of ring, you have to define rings and answer_mode as pointers to
# files. E.g.
#
# ring_type ring
#
# rings /etc/rings/ring
# answer_mode /etc/answer/ring
#
# ring_type ring1
#
# rings /etc/rings/ring1
# answer_mode /etc/answer/ring1
# for setting a different set of message files:
# message_list Index1
#
# and so on. Now you can set up a different number of rings and answer modes
# by creating the files:
#
# /etc/rings/ring       - for the default value
# /etc/rings/ring.ttyS0 - for the value for device ttyS0
# /etc/rings/ring.ttyS1 - for the value for device ttyS1
#
# And the same way you can set the answer modes.
#