allow semicolons to be escaped in call files (issue #5407)

git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@6742 65c4cc65-6c06-0410-ace0-fbb531ad65f3
This commit is contained in:
Russell Bryant
2005-10-11 20:52:37 +00:00
parent 1ae71d0b41
commit 460655f31c
2 changed files with 22 additions and 6 deletions

View File

@@ -1,8 +1,16 @@
#
# This is a sample file that can be dumped in /var/spool/asterisk/outgoing
# to generate a call. Obviously, you MUST specify at least a channel in
# the same format as you would for the "Dial" application. Only one
# channel name is permitted.
# to generate a call.
#
# Comments are indicated by a '#' character that begins a line, or follows
# a space or tab character. To be consistent with the configuration files
# in Asterisk, comments can also be indicated by a semicolon. However, the
# multiline comments (;-- --;) used in Asterisk configuration files are not
# supported. Semicolons can be escaped by a backslash.
#
# Obviously, you MUST specify at least a channel in the same format as you
# would for the "Dial" application. Only one channel name is permitted.
#
Channel: Zap/1
#