Best of Breed Telephony with mixed OST and proprietary code Presented by: David Mandelstam, CEO/President, Sangoma Technologies
Open Source vs. Licensed software Licensed software Open Source Produced to meet a business requirement Written to meet a user’s specific need Feature set defined by standards or business case Features added as required by the users Customers expect all published features to work! Standards define the features Implementation is pragmatic: Features are added as they are found useful Good projects are exhaustively tested before release, with quick fixes for any published features that do not work Most testing is in the field: Popular features are well tested, other features are less well tested
Compliance testing and open source <ul><li>Compliance testing is often both time consuming and expensive. Who pays for certification of an open source project? </li></ul><ul><li>Does she then give it away to the community? </li></ul><ul><li>Why? </li></ul><ul><li>The certified software is only certified to the extent that the code is not touched. Who is responsible if the code is modified and no longer complies? </li></ul>
Conclusion: Open Source may not be the best solution for compliance tested code.
Sangoma Open Source/Proprietary mixed implementation Closed source Proprietary code Open Source code
Extensions of this approach <ul><li>Used for BRI support </li></ul><ul><li>Splitting the telephony interface from the application improves scalability. </li></ul><ul><li>Protocol stack does not have to be proprietary: We may use this approach for PRI using libpri or other PRI stacks </li></ul><ul><li>Could even be used for SIP </li></ul><ul><li>From the point of view of Asterisk, every type of connection looks exactly the same: Total connection abstraction </li></ul><ul><li>It is the SMG and telephony application that is certified, without reference to the application, e.g. Asterisk. </li></ul>
Sangoma AFT Family of Cards Base PCI or PCI Express card Optional DSP module for echo cancellation and transcoding Personality Card : Quad port analog module Personality Card : Octal port T1/E1 module Personality Card: Quad port T1/E1 module Personality Card: Dual port T1/E1 module
Standards and compliance <ul><li>Adherence to standards is often a requirement in telephony applications </li></ul><ul><li>Compliance testing is often largely related to dealing with exception conditions </li></ul><ul><li>These exception conditions are by definition seldom seen in the field </li></ul><ul><li>Pragmatic solutions (solutions that “work”) do not therefore always meet the requirements of standards certification </li></ul>
What are the attributes of a good open source project? <ul><li>The application must fit a universal need </li></ul><ul><li>There needs to be a strong central organization and driving member(s) </li></ul><ul><li>The project should ideally be multifaceted so that multiple developers can work on different aspects. </li></ul><ul><li>In open source popularity=quality , as much of the quality control is in the field. </li></ul><ul><li>There must be a payoff for developers </li></ul><ul><li>Excellent examples of good open source projects are Linux® and Asterisk® </li></ul>
We are heavily standards-based There is a difference between an implementation that “works” and one that is certified!