[svn-commits] russell: branch group/addons-merge r204399 - /team/group/addons-merge/configs/
SVN commits to the Digium repositories
svn-commits at lists.digium.com
Tue Jun 30 09:51:05 CDT 2009
Author: russell
Date: Tue Jun 30 09:51:02 2009
New Revision: 204399
URL: http://svn.asterisk.org/svn-view/asterisk?view=rev&rev=204399
Log:
add configs for modules that were merged in
Added:
team/group/addons-merge/configs/cdr_mysql.conf.sample (with props)
team/group/addons-merge/configs/mobile.conf.sample (with props)
team/group/addons-merge/configs/mysql.conf.sample (with props)
team/group/addons-merge/configs/res_mysql.conf.sample (with props)
Added: team/group/addons-merge/configs/cdr_mysql.conf.sample
URL: http://svn.asterisk.org/svn-view/asterisk/team/group/addons-merge/configs/cdr_mysql.conf.sample?view=auto&rev=204399
==============================================================================
--- team/group/addons-merge/configs/cdr_mysql.conf.sample (added)
+++ team/group/addons-merge/configs/cdr_mysql.conf.sample Tue Jun 30 09:51:02 2009
@@ -1,0 +1,58 @@
+;
+; Note - if the database server is hosted on the same machine as the
+; asterisk server, you can achieve a local Unix socket connection by
+; setting hostname=localhost
+;
+; port and sock are both optional parameters. If hostname is specified
+; and is not "localhost" (you can use address 127.0.0.1 instead), then
+; cdr_mysql will attempt to connect to the port specified or use the
+; default port. If hostname is not specified or if hostname is
+; "localhost", then cdr_mysql will attempt to connect to the socket file
+; specified by sock or otherwise use the default socket file.
+;
+;[global]
+;hostname=database.host.name
+;dbname=asteriskcdrdb
+;table=cdr
+;password=password
+;user=asteriskcdruser
+;port=3306
+;sock=/tmp/mysql.sock
+;
+; If your system's locale differs from mysql database character set,
+; cdr_mysql can damage non-latin characters in CDR variables. Use this
+; option to protect your data.
+;charset=koi8r
+;
+; Older versions of cdr_mysql set the calldate field to whenever the
+; record was posted, rather than the start date of the call. This flag
+; reverts to the old (incorrect) behavior. Note that you'll also need
+; to comment out the "start=calldate" alias, below, to use this.
+;compat=no
+;
+; ssl connections (optional)
+;ssl_ca=<path to CA cert>
+;ssl_cert=<path to cert>
+;ssl_key=<path to keyfile>
+;
+; You may also configure the field names used in the CDR table.
+;
+[columns]
+;static "<value>" => <column>
+;alias <cdrvar> => <column>
+alias start => calldate
+alias callerid => clid
+;alias src => src
+;alias dst => dst
+;alias dcontext => dcontext
+;alias channel => channel
+;alias dstchannel => dstchannel
+;alias lastapp => lastapp
+;alias lastdata => lastdata
+;alias duration => duration
+;alias billsec => billsec
+;alias disposition => disposition
+;alias amaflags => amaflags
+;alias accountcode => accountcode
+;alias userfield => userfield
+;alias uniqueid => uniqueid
Propchange: team/group/addons-merge/configs/cdr_mysql.conf.sample
------------------------------------------------------------------------------
svn:eol-style = native
Propchange: team/group/addons-merge/configs/cdr_mysql.conf.sample
------------------------------------------------------------------------------
svn:keywords = Author Date Id Revision
Propchange: team/group/addons-merge/configs/cdr_mysql.conf.sample
------------------------------------------------------------------------------
svn:mime-type = text/plain
Added: team/group/addons-merge/configs/mobile.conf.sample
URL: http://svn.asterisk.org/svn-view/asterisk/team/group/addons-merge/configs/mobile.conf.sample?view=auto&rev=204399
==============================================================================
--- team/group/addons-merge/configs/mobile.conf.sample (added)
+++ team/group/addons-merge/configs/mobile.conf.sample Tue Jun 30 09:51:02 2009
@@ -1,0 +1,68 @@
+;
+; mobile.conf
+; configuration file for chan_mobile
+;
+
+[general]
+interval=30 ; Number of seconds between trying to connect to devices.
+
+; The following is a list of adapters we use.
+; id must be unique and address is the bdaddr of the adapter from hciconfig.
+; Each adapter may only have one device (headset or phone) connected at a time.
+; Add an [adapter] entry for each adapter you have.
+
+[adapter]
+id=blue
+address=00:09:DD:60:01:A3
+;forcemaster=yes ; attempt to force adapter into master mode. default is no.
+;alignmentdetection=yes ; enable this if you sometimes get 'white noise' on asterisk side of the call
+ ; its a bug in the bluetooth adapter firmware, enabling this will compensate for it.
+ ; default is no.
+
+[adapter]
+id=dlink
+address=00:80:C8:35:52:78
+
+; The following is a list of the devices we deal with.
+; Every device listed below will be available for calls in and out of Asterisk.
+; Each device needs an adapter=xxxx entry which determines which bluetooth adapter is used.
+; Use the CLI command 'mobile search' to discover devices.
+; Use the CLI command 'mobile show devices' to see device status.
+;
+; To place a call out through a mobile phone use Dial(Mobile/[device]/NNN.....) or Dial(Mobile/gn/NNN......) in your dialplan.
+; To call a headset use Dial(Mobile/[device]).
+
+[LGTU550]
+address=00:E0:91:7F:46:44 ; the address of the phone
+port=4 ; the rfcomm port number (from mobile search)
+context=incoming-mobile ; dialplan context for incoming calls
+adapter=dlink ; adapter to use
+group=1 ; this phone is in channel group 1
+;nocallsetup=yes ; set this only if your phone reports that it supports call progress notification, but does not do it. Motorola L6 for example.
+
+[blackberry]
+address=00:60:57:32:7E:B2
+port=2
+context=incoming-mobile
+adapter=dlink
+group=1
+;blackberry=yes ; set this if you are using a blackberry device
+
+[6310i]
+address=00:60:57:32:7E:B1
+port=13
+context=incoming-mobile
+adapter=dlink
+group=1 ; this phone is in channel group 1 also.
+
+[headset]
+address=00:0B:9E:11:AE:C6
+port=1
+type=headset ; This is a headset, not a Phone !
+adapter=blue
+
+[headset1]
+address=00:0B:9E:11:74:A5
+port=1
+type=headset
+adapter=dlink
Propchange: team/group/addons-merge/configs/mobile.conf.sample
------------------------------------------------------------------------------
svn:eol-style = native
Propchange: team/group/addons-merge/configs/mobile.conf.sample
------------------------------------------------------------------------------
svn:keywords = Author Date Id Revision
Propchange: team/group/addons-merge/configs/mobile.conf.sample
------------------------------------------------------------------------------
svn:mime-type = text/plain
Added: team/group/addons-merge/configs/mysql.conf.sample
URL: http://svn.asterisk.org/svn-view/asterisk/team/group/addons-merge/configs/mysql.conf.sample?view=auto&rev=204399
==============================================================================
--- team/group/addons-merge/configs/mysql.conf.sample (added)
+++ team/group/addons-merge/configs/mysql.conf.sample Tue Jun 30 09:51:02 2009
@@ -1,0 +1,24 @@
+; Configuration file for the MYSQL app addon
+
+[general]
+;
+; Nullvalue governs how NULL values are returned from the database. In
+; previous versions, the special NULL value was returned as the "NULL"
+; string. We now provide an option for the behavior, configured globally.
+; nullstring - the string "NULL"
+; emptystring - the string ""
+; null - unset the variable
+;
+; WARNING: setting nullvalue=null may have undesireable consequences, in
+; particular if you use subroutines in AEL or the LOCAL() variable construct.
+; You have been warned. Don't complain if you use that setting in combination
+; with Gosub or AEL and get buggy behavior.
+;
+nullvalue = nullstring
+
+; If set, autoclear will destroy allocated statement and connection resources
+; when the channel ends. For most usage of the MYSQL app, this is what you
+; want, but it's conceivable that somebody is sharing MYSQL connections across
+; multiple channels, in which case, this should be set to 'no'. Defaults to
+; 'no', as this was the original behavior.
+autoclear=yes
Propchange: team/group/addons-merge/configs/mysql.conf.sample
------------------------------------------------------------------------------
svn:eol-style = native
Propchange: team/group/addons-merge/configs/mysql.conf.sample
------------------------------------------------------------------------------
svn:keywords = Author Date Id Revision
Propchange: team/group/addons-merge/configs/mysql.conf.sample
------------------------------------------------------------------------------
svn:mime-type = text/plain
Added: team/group/addons-merge/configs/res_mysql.conf.sample
URL: http://svn.asterisk.org/svn-view/asterisk/team/group/addons-merge/configs/res_mysql.conf.sample?view=auto&rev=204399
==============================================================================
--- team/group/addons-merge/configs/res_mysql.conf.sample (added)
+++ team/group/addons-merge/configs/res_mysql.conf.sample Tue Jun 30 09:51:02 2009
@@ -1,0 +1,40 @@
+;
+; Sample configuration for res_config_mysql.c
+;
+; The value of dbhost may be either a hostname or an IP address.
+; If dbhost is commented out or the string "localhost", a connection
+; to the local host is assumed and dbsock is used instead of TCP/IP
+; to connect to the server.
+;
+; Multiple database contexts may be configured, with the caveat that
+; all context names should be unique and must not contain the slash ('/')
+; character. If you wish to separate reads from writes in your database
+; configuration, you specify the database (NOT HERE, in other files)
+; separated by a slash, read database first. If your database
+; specification does not contain a slash, the implication is that reads
+; and writes should be performed to the same database.
+;
+; For example, in extconfig.conf, you could specify a line like:
+; sippeers => mysql,readhost.asterisk/writehost.asterisk,sipfriends
+; and then define the contexts [readhost.asterisk] and [writehost.asterisk]
+; below.
+;
+; The requirements parameter is available only in Asterisk 1.6.1 and
+; later and must be present in all contexts. It specifies the behavior
+; when a column name is required by the system. The default behavior is
+; "warn" and simply sends a warning to the logger that the column does
+; not exist (or is of the wrong type or precision). The other two
+; possibilities are "createclose", which adds the column with the right
+; type and length, and "createchar", which adds the column as a char
+; type, with the appropriate length to accept the data. Note that with
+; the MySQL driver, both "createclose" and "createchar" will, on occasion,
+; widen a table column width to meet the requirements specified.
+;
+[general]
+;dbhost = 127.0.0.1
+;dbname = asterisk
+;dbuser = myuser
+;dbpass = mypass
+;dbport = 3306
+;dbsock = /tmp/mysql.sock
+;requirements=warn ; or createclose or createchar
Propchange: team/group/addons-merge/configs/res_mysql.conf.sample
------------------------------------------------------------------------------
svn:eol-style = native
Propchange: team/group/addons-merge/configs/res_mysql.conf.sample
------------------------------------------------------------------------------
svn:keywords = Author Date Id Revision
Propchange: team/group/addons-merge/configs/res_mysql.conf.sample
------------------------------------------------------------------------------
svn:mime-type = text/plain
More information about the svn-commits
mailing list