1. 1 Creative Innovation – Customer Satisfaction – Continual Quality Improvement Accessing and Building Asterisk SCF

2. 2 Creative Innovation – Customer Satisfaction – Continual Quality Improvement Building Asterisk SCF  Required tools: git, cmake, C++ compiler  Build Ice: – Obtain and build Ice dependencies (if necessary) – Obtain and build Ice from the Asterisk SCF Ice git repository  Obtain and build Asterisk SCF: – Release and Integration Repositories – Git to know your git for contributing – gitall-asterisk-scf.sh

3. 3 Creative Innovation – Customer Satisfaction – Continual Quality Improvement Required Tools: git  Free and open source  Very popular and for good reason  Distributed version control system  Fast. Very fast.  Bit of a learning curve, but documentation exists to specifically help users switching over from subversion etc.  Documentation, tutorials and books widely available, both free and for $$$ – e.g. Pro Git (http://progit.org/book - Creative Commons)

4. 4 Creative Innovation – Customer Satisfaction – Continual Quality Improvement Required Tools: cmake  Build system generator  Asterisk SCF currently supports GNU Makefiles and Visual Studio solution files  Cross Platform (Windows, Linux, Solaris, etc)  Console and GUI tool provided  Easy to understand and use build system language  As easy as going into your build directory and typing cmake

5. 5 Creative Innovation – Customer Satisfaction – Continual Quality Improvement Required Tools: Compilers  Fairly recent versions of GNU C++, Visual Studio 10 including the “Express” version. – Asterisk SCF requires support for fairly recent C++ language features, but not c++11.. yet – No clang yet!  Python 2.6.6 required for configuration tools. – Version is tied to Ice for Python requirements, YMMV with newer versions.

6. 6 Creative Innovation – Customer Satisfaction – Continual Quality Improvement Building Ice - Dependencies  Needs to be done first!  “Third-Party-Libraries” packages and archives available on ZeroC – Pre-built for some platforms with patches already applied. – Source archives available which include the patches that need to be applied. – When stock packages are sufficient, make sure the “dev” packages are also installed. – A patched version for libmcpp is required to work around bugs in mcpp.  Problems with precompiler interfere with proper operations of the slice translators.

7. 7 Creative Innovation – Customer Satisfaction – Continual Quality Improvement Building Ice – the Ice Repository  Includes features added for Asterisk SCF – Developed in partnership with ZeroC – To be incorporated in future version of Ice  New features and why the stock version of Ice will not do: – unsliceable classes – custom code generation for visitor class support – improvements to library loading for services – code generation fixes

8. 8 Creative Innovation – Customer Satisfaction – Continual Quality Improvement Building Asterisk SCF - Boost  Boost is a collection of free, peer-reviewed C++ class libraries  The culmination of countless years of C++ experience and hard-won best practices  Wide range of platform support  Answers the “Java/C#/Python library has that” challenge  boost::test used for Asterisk SCF unit tests!

9. 9 Creative Innovation – Customer Satisfaction – Continual Quality Improvement Building Asterisk SCF – the Repositories  Integration and release repositories – asterisk-scf/integration/sip and asterisk-scf/release/sip  Repository per component – asterisk-scf/release/sip and asterisk-scf/release/bridging  Slice collections – asterisk-scf/release/slice  Non-component foundation repositories – asterisk-scf/release/ice-util-cpp  gitall-asterisk-scf.sh shell script simplifies things by cloning what you need to build

10. 10 Creative Innovation – Customer Satisfaction – Continual Quality Improvement Building Asterisk SCF – the Instructions  Instructions available for Windows and various Linux distros at http://wiki.asterisk.org/  If we can make the instructions clearer please tell us how!