Move Asterisk-addons modules into the main Asterisk source tree.

Someone asked yesterday, "is there a good reason why we can't just put these
modules in Asterisk?".  After a brief discussion, as long as the modules are
clearly set aside in their own directory and not enabled by default, it is
perfectly fine.

For more information about why a module goes in addons, see README-addons.txt.

chan_ooh323 does not currently compile as it is behind some trunk API updates.
However, it will not build by default, so it should be okay for now.


git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@204413 65c4cc65-6c06-0410-ace0-fbb531ad65f3

5 files changed, 363 insertions, 0 deletions

diff --git a/configs/cdr_mysql.conf.sample b/configs/cdr_mysql.conf.sample
new file mode 100644
index 000000000..c0c4a5fc4
--- /dev/null
+++ b/configs/cdr_mysql.conf.sample
@@ -0,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
diff --git a/configs/mobile.conf.sample b/configs/mobile.conf.sample
new file mode 100644
index 000000000..7555a17e5
--- /dev/null
+++ b/configs/mobile.conf.sample
@@ -0,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
diff --git a/configs/mysql.conf.sample b/configs/mysql.conf.sample
new file mode 100644
index 000000000..fafd4f7a2
--- /dev/null
+++ b/configs/mysql.conf.sample
@@ -0,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
diff --git a/configs/ooh323.conf.sample b/configs/ooh323.conf.sample
new file mode 100644
index 000000000..6d14bcbc5
--- /dev/null
+++ b/configs/ooh323.conf.sample
@@ -0,0 +1,173 @@
+; ---------------------------------------------------------------------------------
+; ---  ******* IMPORTANT NOTE ***********
+; ---
+; ---  This module is currently unsupported.  Use it at your own risk.
+; ---
+; ---------------------------------------------------------------------------------
+
+; Objective System's H323 Configuration example for Asterisk
+; ooh323c driver configuration
+;
+; [general] section defines global parameters
+;
+; This is followed by profiles which can be of three types - user/peer/friend
+; Name of the user profile should match with the h323id of the user device.
+; For peer/friend profiles, host ip address must be provided as "dynamic" is
+; not supported as of now.
+;
+; Syntax for specifying a H323 device in extensions.conf is
+; For Registered peers/friends profiles:
+;        OOH323/name where name is the name of the peer/friend profile.
+;
+; For unregistered H.323 phones:
+;        OOH323/ip[:port] OR if gk is used OOH323/alias where alias can be any H323
+;                          alias
+;
+; For dialing into another asterisk peer at a specific exten
+;       OOH323/exten/peer OR OOH323/exten@ip
+;
+; Domain name resolution is not yet supported.
+; 
+; When a H.323 user calls into asterisk, his H323ID is matched with the profile
+; name and context is determined to route the call
+;
+; The channel driver will register all global aliases and aliases defined in 
+; peer profiles with the gatekeeper, if one exists. So, that when someone
+; outside our pbx (non-user) calls an extension, gatekeeper will route that 
+; call to our asterisk box, from where it will be routed as per dial plan.
+
+
+[general]
+;Define the asetrisk server h323 endpoint
+
+;The port asterisk should listen for incoming H323 connections.
+;Default - 1720
+;port=1720
+
+;The dotted IP address asterisk should listen on for incoming H323
+;connections
+;Default - tries to find out local ip address on it's own
+bindaddr=0.0.0.0    
+
+;This parameter indicates whether channel driver should register with 
+;gatekeeper as a gateway or an endpoint.
+;Default - no
+;gateway=no
+
+;Whether asterisk should use fast-start and tunneling for H323 connections.
+;Default - yes
+;faststart=no
+;h245tunneling=no
+
+;Whether media wait for connect
+;Default - No
+;mediawaitforconnect=yes
+
+;H323-ID to be used for asterisk server
+;Default - Asterisk PBX
+h323id=ObjSysAsterisk 
+e164=100
+
+;CallerID to use for calls
+;Default - Same as h323id
+callerid=asterisk
+
+;Whether this asterisk server will use gatekeeper.
+;Default - DISABLE
+;gatekeeper = DISCOVER
+;gatekeeper = a.b.c.d
+gatekeeper = DISABLE
+
+;Location for H323 log file
+;Default - /var/log/asterisk/h323_log
+;logfile=/var/log/asterisk/h323_log
+
+
+;Following values apply to all users/peers/friends defined below, unless
+;overridden within their client definition
+
+;Sets default context all clients will be placed in.
+;Default - default
+context=default
+
+;Sets rtptimeout for all clients, unless overridden
+;Default - 60 seconds
+;rtptimeout=60	    ; Terminate call if 60 seconds of no RTP activity
+                    ; when we're not on hold
+
+;Type of Service
+;Default - none (lowdelay, thoughput, reliability, mincost, none)
+;tos=lowdelay
+
+;amaflags = default
+
+;The account code used by default for all clients.
+;accountcode=h3230101
+
+;The codecs to be used for all clients.Only ulaw and gsm supported as of now.
+;Default - ulaw
+; ONLY ulaw, gsm, g729 and g7231 supported as of now
+disallow=all     ;Note order of disallow/allow is important.
+allow=gsm
+allow=ulaw
+
+
+; dtmf mode to be used by default for all clients. Supports rfc2833, q931keypad
+; h245alphanumeric, h245signal.
+;Default - rfc 2833
+dtmfmode=rfc2833
+
+; User/peer/friend definitions:
+; User config options                    Peer config options
+; ------------------                     -------------------
+; context                            
+; disallow                               disallow
+; allow                                  allow
+; accountcode                            accountcode
+; amaflags                               amaflags
+; dtmfmode                               dtmfmode
+; rtptimeout                             ip
+;                                        port
+;                                        h323id
+;                                        email
+;                                        url
+;                                        e164
+;                                        rtptimeout
+
+;
+
+;Define users here
+;Section header is extension
+[myuser1]
+type=user
+context=context1
+disallow=all
+allow=gsm
+allow=ulaw    
+
+
+
+[mypeer1]
+type=peer
+context=context2
+ip=a.b.c.d   ; UPDATE with appropriate ip address
+port=1720    ; UPDATE with appropriate port
+e164=101
+
+
+
+[myfriend1]
+type=friend
+context=default
+ip=10.0.0.82   ; UPDATE with appropriate ip address
+port=1820    ; UPDATE with appropriate port
+disallow=all
+allow=ulaw
+e164=12345
+rtptimeout=60
+dtmfmode=rfc2833
+
+
+
+
+
diff --git a/configs/res_mysql.conf.sample b/configs/res_mysql.conf.sample
new file mode 100644
index 000000000..dfbbf49a8
--- /dev/null
+++ b/configs/res_mysql.conf.sample
@@ -0,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