Refs #2809 - upgraded chan-sccp package as old stuff doesn't build on bionic

ubuntu/asterisk/chan-sccp-4.3.1/.github/CONTRIBUTING.md

+## How to contribute to Chan-SCCP
+
+#### **Did you find a bug?**
+
+* **Ensure the bug was not already reported** by searching on GitHub under [Issues](https://github.com/chan-sccp/chan-sccp/issues).
+
+* If you're unable to find an open issue addressing the problem, [open a new one](https://github.com/chan-sccp/chan-sccp/issues/new). 
+Be sure to include 
+   * a **title and clear description**
+   * as much relevant information as possible, like:
+      * platform (cpu / 32/64 bit / endianness)
+      * operating system + version
+      * **asterisk version** (includeing revision if relevant)
+      * **chan-sccp version** (including revision if relevant)
+   * and a **code sample** or an **reproducable test case** demonstrating the expected behavior that is not occurring.
+   * when refering to the mailinglist, please include the subject title and date of the first mail in that thread.
+   
+Note: How more information is provided upfront, the easier it is to get into the debugging phase. And the sooner the issue is resolved.
+
+* If possible, use the relevant bug report templates to create the issue. Simply copy the content of the appropriate template into a .txt file, make the necessary changes to demonstrate the issue, and **paste the content into the issue description**:
+  * [**Generic template** for issues](https://github.com/chan-sccp/chan-sccp/blob/master/.github/ISSUE_TEMPLATE.md)
+
+* For more detailed information on submitting a bug report and creating an issue, visit our [reporting bugs guideline](https://github.com/chan-sccp/chan-sccp/wiki/Reporting%20Bugs).
+
+#### **Did you write a patch that fixes a bug?**
+
+* Open a new GitHub pull request with the patch.
+
+* Ensure the Pull Request description clearly describes the problem and solution. Include the relevant issue number if applicable.
+
+* Before submitting, please read the [Contributing to Chan-SCCP](https://github.com/chan-sccp/chan-sccp/wiki/Contributing) guide to know more about coding conventions and benchmarks.
+
+BTW: Thanks for being a team player and helping out, this is really appreciated !
+
+#### **Do you intend to add a new feature or change an existing one?**
+
+* Suggest your change in the [chan-sccp mailing list](https://sourceforge.net/p/chan-sccp-b/mailman/chan-sccp-b-discussion/) and start writing code.
+
+* Do not open an issue on GitHub until you have collected positive feedback about the change. GitHub issues are primarily intended for bug reports and fixes.
+
+#### **Do you have questions about the source code?**
+
+* Ask any question about how to use Chan-SCCP in the [chan-sccp mailing list](https://sourceforge.net/p/chan-sccp-b/mailman/chan-sccp-b-discussion/).
+
+#### **Do you want to contribute to the Chan-SCCP WIKI documentation?**
+
+* Open a new GitHub pull request with the patch against [wiki](https://github.com/chan-sccp/chan-sccp.wiki.git). We will review the change and post it as soon as possible.
+
+</br>
+Chan-SCCP is a volunteer effort. We encourage you to pitch in and [join the team](http://github.com/chan-sccp/)!
+
+Thanks!
+
+The Chan-SCCP Team

ubuntu/asterisk/chan-sccp-4.3.1/.github/ISSUE_TEMPLATE.md

+[Short description of problem here]
+
+**Reproduction Steps:**
+
+1. [First Step]
+2. [Second Step]
+3. [Other Steps...]
+
+**Expected behavior:**
+
+[Describe expected behavior here]
+
+**Observed behavior:**
+
+[Describe observed behavior here]
+
+**Screenshots**
+
+(Screenshots which show reproduction steps and/or demonstrate the problem)
+[url]
+
+**chan-sccp version:** (include revision and/or branch if relevant)
+
+**asterisk version:** (include revision and/or branch if relevant)
+
+**Addition / Optional Information:**
+- Problem started happening recently, didn't happen in an older version of Chan-SCCP: [Yes/No]
+- Problem can be reliably reproduced, doesn't happen randomly: [Yes/No]
+- Platform:
+  - [CPU]
+  - [32/64 Bit]
+  - [Big/Small Endian]
+  - [Operating System]
+  - [Operating System Version]
+- Direct Contact information: [You can contact me here]
+- Log Files (attach .txt / [pastbin](http://pastebin.com/) / [gist](http://gist.github.com/)): [url]
+- Comments: [Other Information]
+
+
+
+

ubuntu/asterisk/chan-sccp-4.3.1/.github/PULL_REQUEST_TEMPLATE.md

+Fixes Issue: #.
+
+Changes proposed by this Pull Request:
+- 
+- 
+- 
+- 
+
+Inform: @Developers

ubuntu/asterisk/chan-sccp-4.3.1/.gitignore

+/.tmp
+/.hgignore
+/.hgtags
+/.project
+/.cproject
+/config.h
+Makefile
+/config.log
+/config.status
+/config.cache
+/autom4te.cache
+/changes.patch
+/ChangeLog
+/doxygen.warn
+/libtool
+.libs
+.deps
+*.lo
+*.la
+*.o
+contrib/gen_sccpconf/.deps/
+contrib/gen_sccpconf/Makefile
+contrib/gen_sccpconf/gen_sccpconf
+src/config.h.bak
+src/config.h.in.bak
+.*~
+*~
+.revision
+src/revision.h
+src/sccp_enum.?
+*.bak
+*.diff
+coverage/
+chan_sccp-en_US.xml

ubuntu/asterisk/chan-sccp-4.3.1/.travis.yml

+language: c
+
+# Setup Build Matrix
+compiler: 
+ - clang
+ - gcc
+
+env:
+  global:
+    - COVERITY_SCAN_PROJECT_NAME="chan-sccp/chan-sccp"
+    - COVERITY_SCAN_PROJECT_DESCRIPTION="SCCP Channel Addon for Asterisk"
+    - COVERITY_SCAN_NOTIFICATION_EMAIL="info@talon.nl"
+    # COVERITY_SCAN_BRANCH_PATTERN="master"
+    - COVERITY_SCAN_BRANCH_PATTERN="develop"
+    - COVERITY_SCAN_BUILD_URL="https://scan.coverity.com/scripts/travisci_build_coverity_scan.sh"
+    - COVERITY_SCAN_BUILD="curl -s $COVERITY_SCAN_BUILD_URL | bash"
+    - COVERITY_SCAN_BUILD_COMMAND_PREPEND="./configure --enable-video --enable-conference --enable-distributed-devicestate --enable-advanced-functions && make clean"
+    - COVERITY_SCAN_BUILD_COMMAND="make -j2"
+    # The next declaration is the encrypted COVERITY_SCAN_TOKEN, created using: travis encrypt COVERITY_SCAN_TOKEN="xxxxxxx-xxxxxxx" -r dkgroot/chan-sccp-b
+    - secure: "VJIQBkTBxuMqUEk872yPrbPq3MAFqB0EnjElxjTk+BWEHIKmheKIHyrlqJgnql/tqyeLSa6D8epV0cJ47adVbedCPAG/l1tk4AzErrQdnw9VVFANUFrJXxlaH/yfm39XiwwumuAJ2RF3OaYGHlyurW+lb91y2HHw8vQHNPu+uHI="
+  matrix:
+    - REPOS=precise
+    - REPOS=trusty
+    - REPOS=trusty13
+    - REPOS=utopic
+
+matrix:
+  allow_failures:
+    - compiler: clang
+      env: REPOS=trusty13
+
+# Install Required Devel Packages
+before_install:
+ - if [ "${REPOS}" != "trusty13" ]; 
+   then
+     echo "deb http://archive.ubuntu.com/ubuntu ${REPOS} main restricted universe multiverse"            | sudo tee -a /etc/apt/sources.list.d/trusty.list;
+     echo "deb http://archive.ubuntu.com/ubuntu ${REPOS}-updates main restricted universe multiverse"    | sudo tee -a /etc/apt/sources.list.d/trusty.list;
+     echo "deb http://security.ubuntu.com/ubuntu/ ${REPOS}-security main restricted universe multiverse" | sudo tee -a /etc/apt/sources.list.d/trusty.list;
+     echo "deb http://archive.canonical.com/ubuntu/ ${REPOS} partner"                                    | sudo tee -a /etc/apt/sources.list.d/trusty.list;
+     sudo apt-get update -qq;
+     sudo apt-get install -qq libblocksruntime0 libblocksruntime-dev asterisk asterisk-dev asterisk-config asterisk-modules binutils.dev libc6-dev gettext;
+   else
+     echo "deb http://archive.ubuntu.com/ubuntu trusty main restricted universe multiverse"              | sudo tee -a /etc/apt/sources.list.d/trusty.list;
+     echo "deb http://archive.ubuntu.com/ubuntu trusty-updates main restricted universe multiverse"      | sudo tee -a /etc/apt/sources.list.d/trusty.list;
+     echo "deb http://security.ubuntu.com/ubuntu/ trusty-security main restricted universe multiverse"   | sudo tee -a /etc/apt/sources.list.d/trusty.list;
+     echo "deb http://archive.canonical.com/ubuntu/ trusty partner"                                      | sudo tee -a /etc/apt/sources.list.d/trusty.list;
+     sudo apt-key adv --recv-keys --keyserver keyserver.ubuntu.com 9C245DE2;
+     echo "deb http://ppa.launchpad.net/jan-hoffmann/asterisk13/ubuntu trusty main"                      | sudo tee -a /etc/apt/sources.list.d/asterisk13.list;
+     echo "deb-src http://ppa.launchpad.net/jan-hoffmann/asterisk13/ubuntu trusty main"			 | sudo tee -a /etc/apt/sources.list.d/asterisk13.list;
+     sudo apt-get update -qq;
+     sudo apt-get install -qq libblocksruntime0 libblocksruntime-dev libpj2 libpjmedia2 libpjnath2 libpjproject-dev libpjsip2 libpjsua2 libpjsua2-2 asterisk asterisk-dev asterisk-config asterisk-modules asterisk-dbg binutils.dev libc6-dev gettext;
+     if [ "x${CC}" == "xclang" ] && [ "x${TRAVIS_BRANCH}" == "xdevelop" ]; then eval "$COVERITY_SCAN_BUILD"; fi;
+   fi
+
+# Prepare Configure Script
+before_script:
+ - autoreconf -fi
+
+# Report Results
+notifications:
+  slack: chan-sccp:yfQzKYTnTf4cD1iHElnTYsXD
+  email:
+    recipients:
+      - ddegroot@talon.nl
+      - marcelloceschia@users.sourceforge.net
+  webhooks:
+    urls:
+      - https://webhooks.gitter.im/e/2d18f92f8374e4e15fbc
+    on_success: change  # options: [always|never|change] default: always
+    on_failure: always  # options: [always|never|change] default: always
+    on_start: never     # options: [always|never|change] default: always

ubuntu/asterisk/chan-sccp-4.3.1/.version

+4.3.1

ubuntu/asterisk/chan-sccp-4.3.1/AUTHORS

+/**
+ * 
+ * \file
+ * Contains the list of Chan-SCCP-b Authors
+ *
+ * To report Bugs, Issues and Featuren Request, please do not contact the
+ * developers directly, but always use the Tracker System on Sourceforge:
+ * http://sourceforge.net/tracker/?words=tracker_browse&group_id=186378&atid=917045
+ *
+ * \note        Reworked, but based on chan_sccp code.
+ *              The original chan_sccp driver that was made by Zozo which
+ * 		itself was derived from the chan_skinny driver.
+ *              Modified by Jan Czmok and Julien Goodwin
+ *
+ * \page authors Chan-SCCP-b Authors
+ *
+ * Name              | Username        | Role                             | E-mail                       | GPG        | Active
+ * ------------------|-----------------|----------------------------------|------------------------------|------------|----------
+ * Marcello Ceschia  | marcelloceschia | Project Admin/Developer (Trunk)  | marcelloceschia@users.sf.net | 0xE6F16AD3 | YES
+ * Diederik de Groot | ddegroot        | Project Admin/Developer (Trunk)  | ddegroot@users.sf.net        | 0x0A1BECD6 | YES
+ * David Dederscheck | davidded        | Project Admin/Developer (Stable) | davidded@users.sf.net        |            | NO
+ * Anthony Shaw      | anthonyshaw     | Project Admin/Developer          | anthonyshaw@users.sf.net     |            | NO
+ * Scotchy           | scotchy         | Project Admin/Developer          | scotchy@users.sf.net         |            | NO
+ * Andrew Lee        | andrewylee      | Developer                        | andrewylee@users.sf.net      |            | NO
+ * Federico Santulli | fsantulli       | Developer                        | fsantulli@users.sf.net       |            | NO
+ * Geoff Thornton    | gthornton       | Developer                        | gthornton@users.sf.net       |            | NO
+ * macdiver          | macdiver        | Developer                        | macdiver@users.sf.net        |            | NO
+ * Sebastian Vetter  | sebbbl          | Doc Writer                       | sebbbl@users.sf.net          |            | NO
+ * Romain Bignon     | progs           | Developer                        | progs@users.sf.net           |            | NO
+ */
+
+/**
+ * GPG are embedded in this repository, you can import these gpg keys using:
+ *
+ * > git cat-file blob <username>.gpg_pub_key | gpg --import
+ *
+ * for example:
+ * > git cat-file blob dkgroot.gpg_pub_key | gpg --import
+ *
+ */
+
+/**
+ * Developers:
+ *
+ * To Add your gpg to the repository:
+ *
+ * > gpg --armor --export <email@address.to> >pubkey.txt
+ * > git hash-object -w pubkey.txt
+ * > git tag -s username.gpg_pub_key <HASH-VALUE-GOTTEN_FROM-PREVIOUS-COMMAND>
+ *
+ * See more info: http://365git.tumblr.com/post/2813251228/adding-a-gpg-public-key-to-a-repository
+ */
+

ubuntu/asterisk/chan-sccp-4.3.1/COPYING

+
+                    GNU GENERAL PUBLIC LICENSE
+                     Version 1, February 1989
+
+ Copyright (C) 1989 Free Software Foundation, Inc.
+                    51 Franklin St, Fifth Floor, Boston, MA  02110-1301  USA
+
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+                            Preamble
+
+  The license agreements of most software companies try to keep users
+at the mercy of those companies.  By contrast, our General Public
+License is intended to guarantee your freedom to share and change free
+software--to make sure the software is free for all its users.  The
+General Public License applies to the Free Software Foundation's
+software and to any other program whose authors commit to using it.
+You can use it for your programs, too.
+
+  When we speak of free software, we are referring to freedom, not
+price.  Specifically, the General Public License is designed to make
+sure that you have the freedom to give away or sell copies of free
+software, that you receive source code or can get it if you want it,
+that you can change the software or use pieces of it in new free
+programs; and that you know you can do these things.
+
+  To protect your rights, we need to make restrictions that forbid
+anyone to deny you these rights or to ask you to surrender the rights.
+These restrictions translate to certain responsibilities for you if you
+distribute copies of the software, or if you modify it.
+
+  For example, if you distribute copies of a such a program, whether
+gratis or for a fee, you must give the recipients all the rights that
+you have.  You must make sure that they, too, receive or can get the
+source code.  And you must tell them their rights.
+
+  We protect your rights with two steps: (1) copyright the software, and
+(2) offer you this license which gives you legal permission to copy,
+distribute and/or modify the software.
+
+  Also, for each author's protection and ours, we want to make certain
+that everyone understands that there is no warranty for this free
+software.  If the software is modified by someone else and passed on, we
+want its recipients to know that what they have is not the original, so
+that any problems introduced by others will not reflect on the original
+authors' reputations.
+
+  The precise terms and conditions for copying, distribution and
+modification follow.
+
+                    GNU GENERAL PUBLIC LICENSE
+   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+  0. This License Agreement applies to any program or other work which
+contains a notice placed by the copyright holder saying it may be
+distributed under the terms of this General Public License.  The
+"Program", below, refers to any such program or work, and a "work based
+on the Program" means either the Program or any work containing the
+Program or a portion of it, either verbatim or with modifications.  Each
+licensee is addressed as "you".
+
+  1. You may copy and distribute verbatim copies of the Program's source
+code as you receive it, in any medium, provided that you conspicuously and
+appropriately publish on each copy an appropriate copyright notice and
+disclaimer of warranty; keep intact all the notices that refer to this
+General Public License and to the absence of any warranty; and give any
+other recipients of the Program a copy of this General Public License
+along with the Program.  You may charge a fee for the physical act of
+transferring a copy.
+
+  2. You may modify your copy or copies of the Program or any portion of
+it, and copy and distribute such modifications under the terms of Paragraph
+1 above, provided that you also do the following:
+
+    a) cause the modified files to carry prominent notices stating that
+    you changed the files and the date of any change; and
+
+    b) cause the whole of any work that you distribute or publish, that
+    in whole or in part contains the Program or any part thereof, either
+    with or without modifications, to be licensed at no charge to all
+    third parties under the terms of this General Public License (except
+    that you may choose to grant warranty protection to some or all
+    third parties, at your option).
+
+    c) If the modified program normally reads commands interactively when
+    run, you must cause it, when started running for such interactive use
+    in the simplest and most usual way, to print or display an
+    announcement including an appropriate copyright notice and a notice
+    that there is no warranty (or else, saying that you provide a
+    warranty) and that users may redistribute the program under these
+    conditions, and telling the user how to view a copy of this General
+    Public License.
+
+    d) You may charge a fee for the physical act of transferring a
+    copy, and you may at your option offer warranty protection in
+    exchange for a fee.
+
+Mere aggregation of another independent work with the Program (or its
+derivative) on a volume of a storage or distribution medium does not bring
+the other work under the scope of these terms.
+
+  3. You may copy and distribute the Program (or a portion or derivative of
+it, under Paragraph 2) in object code or executable form under the terms of
+Paragraphs 1 and 2 above provided that you also do one of the following:
+
+    a) accompany it with the complete corresponding machine-readable
+    source code, which must be distributed under the terms of
+    Paragraphs 1 and 2 above; or,
+
+    b) accompany it with a written offer, valid for at least three
+    years, to give any third party free (except for a nominal charge
+    for the cost of distribution) a complete machine-readable copy of the
+    corresponding source code, to be distributed under the terms of
+    Paragraphs 1 and 2 above; or,
+
+    c) accompany it with the information you received as to where the
+    corresponding source code may be obtained.  (This alternative is
+    allowed only for noncommercial distribution and only if you
+    received the program in object code or executable form alone.)
+
+Source code for a work means the preferred form of the work for making
+modifications to it.  For an executable file, complete source code means
+all the source code for all modules it contains; but, as a special
+exception, it need not include source code for modules which are standard
+libraries that accompany the operating system on which the executable
+file runs, or for standard header files or definitions files that
+accompany that operating system.
+
+  4. You may not copy, modify, sublicense, distribute or transfer the
+Program except as expressly provided under this General Public License.
+Any attempt otherwise to copy, modify, sublicense, distribute or transfer
+the Program is void, and will automatically terminate your rights to use
+the Program under this License.  However, parties who have received
+copies, or rights to use copies, from you under this General Public
+License will not have their licenses terminated so long as such parties
+remain in full compliance.
+
+  5. By copying, distributing or modifying the Program (or any work based
+on the Program) you indicate your acceptance of this license to do so,
+and all its terms and conditions.
+
+  6. Each time you redistribute the Program (or any work based on the
+Program), the recipient automatically receives a license from the original
+licensor to copy, distribute or modify the Program subject to these
+terms and conditions.  You may not impose any further restrictions on the
+recipients' exercise of the rights granted herein.
+
+  7. The Free Software Foundation may publish revised and/or new versions
+of the General Public License from time to time.  Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+Each version is given a distinguishing version number.  If the Program
+specifies a version number of the license which applies to it and "any
+later version", you have the option of following the terms and conditions
+either of that version or of any later version published by the Free
+Software Foundation.  If the Program does not specify a version number of
+the license, you may choose any version ever published by the Free Software
+Foundation.
+
+  8. If you wish to incorporate parts of the Program into other free
+programs whose distribution conditions are different, write to the author
+to ask for permission.  For software which is copyrighted by the Free
+Software Foundation, write to the Free Software Foundation; we sometimes
+make exceptions for this.  Our decision will be guided by the two goals
+of preserving the free status of all derivatives of our free software and
+of promoting the sharing and reuse of software generally.
+
+                            NO WARRANTY
+
+  9. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
+FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.  EXCEPT WHEN
+OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
+PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
+OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  THE ENTIRE RISK AS
+TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.  SHOULD THE
+PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
+REPAIR OR CORRECTION.
+
+  10. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
+REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
+INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
+OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
+TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
+YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
+PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGES.
+
+                     END OF TERMS AND CONDITIONS
+
+        Appendix: How to Apply These Terms to Your New Programs
+
+  If you develop a new program, and you want it to be of the greatest
+possible use to humanity, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these
+terms.
+
+  To do so, attach the following notices to the program.  It is safest to
+attach them to the start of each source file to most effectively convey
+the exclusion of warranty; and each file should have at least the
+"copyright" line and a pointer to where the full notice is found.
+
+    <one line to give the program's name and a brief idea of what it does.>
+    Copyright (C) 19yy  <name of author>
+
+    This program is free software; you can redistribute it and/or modify
+    it under the terms of the GNU General Public License as published by
+    the Free Software Foundation; either version 1, or (at your option)
+    any later version.
+
+    This program is distributed in the hope that it will be useful,
+    but WITHOUT ANY WARRANTY; without even the implied warranty of
+    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+    GNU General Public License for more details.
+
+    You should have received a copy of the GNU General Public License
+    along with this program; if not, write to the Free Software
+    Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston MA  02110-1301 USA
+
+
+Also add information on how to contact you by electronic and paper mail.
+
+If the program is interactive, make it output a short notice like this
+when it starts in an interactive mode:
+
+    Gnomovision version 69, Copyright (C) 19xx name of author
+    Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+    This is free software, and you are welcome to redistribute it
+    under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the
+appropriate parts of the General Public License.  Of course, the
+commands you use may be called something other than `show w' and `show
+c'; they could even be mouse-clicks or menu items--whatever suits your
+program.
+
+You should also get your employer (if you work as a programmer) or your
+school, if any, to sign a "copyright disclaimer" for the program, if
+necessary.  Here a sample; alter the names:
+
+  Yoyodyne, Inc., hereby disclaims all copyright interest in the
+  program `Gnomovision' (a program to direct compilers to make passes
+  at assemblers) written by James Hacker.
+
+  <signature of Ty Coon>, 1 April 1989
+  Ty Coon, President of Vice
+
+That's all there is to it!

ubuntu/asterisk/chan-sccp-4.3.1/INSTALL

+Installation Instructions
+*************************
+
+Copyright (C) 1994-1996, 1999-2002, 2004-2013 Free Software Foundation,
+Inc.
+
+   Copying and distribution of this file, with or without modification,
+are permitted in any medium without royalty provided the copyright
+notice and this notice are preserved.  This file is offered as-is,
+without warranty of any kind.
+
+Basic Installation
+==================
+
+   Briefly, the shell command `./configure && make && make install'
+should configure, build, and install this package.  The following
+more-detailed instructions are generic; see the `README' file for
+instructions specific to this package.  Some packages provide this
+`INSTALL' file but do not implement all of the features documented
+below.  The lack of an optional feature in a given package is not
+necessarily a bug.  More recommendations for GNU packages can be found
+in *note Makefile Conventions: (standards)Makefile Conventions.
+
+   The `configure' shell script attempts to guess correct values for
+various system-dependent variables used during compilation.  It uses
+those values to create a `Makefile' in each directory of the package.
+It may also create one or more `.h' files containing system-dependent
+definitions.  Finally, it creates a shell script `config.status' that
+you can run in the future to recreate the current configuration, and a
+file `config.log' containing compiler output (useful mainly for
+debugging `configure').
+
+   It can also use an optional file (typically called `config.cache'
+and enabled with `--cache-file=config.cache' or simply `-C') that saves
+the results of its tests to speed up reconfiguring.  Caching is
+disabled by default to prevent problems with accidental use of stale
+cache files.
+
+   If you need to do unusual things to compile the package, please try
+to figure out how `configure' could check whether to do them, and mail
+diffs or instructions to the address given in the `README' so they can
+be considered for the next release.  If you are using the cache, and at
+some point `config.cache' contains results you don't want to keep, you
+may remove or edit it.
+
+   The file `configure.ac' (or `configure.in') is used to create
+`configure' by a program called `autoconf'.  You need `configure.ac' if
+you want to change it or regenerate `configure' using a newer version
+of `autoconf'.
+
+   The simplest way to compile this package is:
+
+  1. `cd' to the directory containing the package's source code and type
+     `./configure' to configure the package for your system.
+
+     Running `configure' might take a while.  While running, it prints
+     some messages telling which features it is checking for.
+
+  2. Type `make' to compile the package.
+
+  3. Optionally, type `make check' to run any self-tests that come with
+     the package, generally using the just-built uninstalled binaries.
+
+  4. Type `make install' to install the programs and any data files and
+     documentation.  When installing into a prefix owned by root, it is
+     recommended that the package be configured and built as a regular
+     user, and only the `make install' phase executed with root
+     privileges.
+
+  5. Optionally, type `make installcheck' to repeat any self-tests, but
+     this time using the binaries in their final installed location.
+     This target does not install anything.  Running this target as a
+     regular user, particularly if the prior `make install' required
+     root privileges, verifies that the installation completed
+     correctly.
+
+  6. You can remove the program binaries and object files from the
+     source code directory by typing `make clean'.  To also remove the
+     files that `configure' created (so you can compile the package for
+     a different kind of computer), type `make distclean'.  There is
+     also a `make maintainer-clean' target, but that is intended mainly
+     for the package's developers.  If you use it, you may have to get
+     all sorts of other programs in order to regenerate files that came
+     with the distribution.
+
+  7. Often, you can also type `make uninstall' to remove the installed
+     files again.  In practice, not all packages have tested that
+     uninstallation works correctly, even though it is required by the
+     GNU Coding Standards.
+
+  8. Some packages, particularly those that use Automake, provide `make