Founder and CEO Mikhail Rodionov discusses all the projects and code contributions that they have built for Kazoo over the past year.

1. PRESENTED BY:
HARD ROCKING
KAZOO
MIKHAIL RODIONOV

2. ABOUT ME
Founder and CEO of SIPLABS
Work in Telecom industry since 2003
Open source evangelist
Master of Mathematics (Novosibirsk
University)
Mikhail (Michael) Rodionov
E-mail: marod@siplabs.ru
Find me in LinkedIn, Facebook, etc…

3. @kazoocon
ABOUT SIPLABS
 Now team of 8 people (7 technical)
 Software development and
professional services/support company
 Now almost 100% focused on KAZOO
 HQ in Russia but work worldwide
 3 Erlang developers
 Own development/CI chain
 Own support/monitoring
tools/services

4. @kazoocon
ABOUT SIPLABS (Continued)
WE DEVELOP (FOR) KAZOO
• 100+ closed pull-request to KAZOO projects at github (as of Sep
29th 2015, a lot more coming right now!)
• #1 independent code contributor
• We develop apps, modules, APIs, scripts, UI, even entire
solutions
AND WE GIVE A THING
ABOUT IT!

5. @kazoocon
ABOUT SIPLABS (Continued)
Some customers we could name (the are more,
but we respect NDAs)

6. @kazoocon
IT WAS “DUDKA STYLE” LAST YEAR…
NOW IT’S “ERLANG, FREESWITCH AND
ROCK’N’ROLL”!!!

7. @kazoocon
PROJECTS
(Contact) Lists API
 Universal contact lists
 VCARD fields support
 Avatar attachments support
 Callflow module for lists matching
 Callflow module for CID Name lookup

8. @kazoocon
PROJECTS (Continued)
Frontier – Your KAZOO guard
 IP ACLs at account/device
level
 Packet rate limits
 Coming soon: temporary
bans
 Can be used with Kamailio,
API, device privisioning
apps, etc

9. @kazoocon
PROJECTS (Continued)
Smaller contributions
 CAMP-ON feature
 Eavesdrop
 ACD Call priorities
 Weighted random ring-group strategy
 Office documents/images support for FAXing
 Temporary greetings for voicemail
 Outbound flags at account level for choosing
upstream carriers
 Voicefabric TTS engine support
 Monster-UI Russian i18n files

10. @kazoocon
PROJECTS (Continued)
 Call Waiting feature
 PATCH support for most APIs
 High definition call recording
 Conference participant name announcements
 System-wide dialplan collections
 Multiple fixes to konami app
 Fixes to ACD app
 Etc...
Smaller contributions (Continued)

11. @kazoocon
(Ladies and Gentlemen, and now
the moment you’ve all been waiting
for, we proudly present for your
dedicated cluster pleasure….)
CONTRIBUTING TODAY!

12. @kazoocon
Project "Circlemaker"
 Native KAZOO implementation
 Comprehensive AAA client (authn, authz, accounting,
session times, interim updates, disconnect packets, etc.)
 RADIUS protocol support with fully customizable
dictionaries/fields
 DIAMETER support may be added (anybody interested?)
 Reseller/multi-tenant friendly architecture
 Callflow module for custom requests
AAA server/billing system
integration

13. @kazoocon
Project “FMC” – mobile for the rest of us
 “Trusting” incoming calls from mobile
networks
 Finding accounts/devices by incoming Caller
IDs
 Mobile-to-Extension calls
 Better support for on-call DTMF commands
(konami) with “cellphone”-type devices
 Can be used as base for MVNO setups

14. @kazoocon
Project “Ananke*” – call scheduler
 Originates calls from the platform
 Example app – voicemail notification calls
 Multiple tries to reach the callee
 (SOON) Timezone-enabled call scheduler
*Ananke (mythology), in Greek mythology,
Goddess of destiny, necessity, and fate

15. @kazoocon
NOW IN DEVELOPMENT
(and looking for interested ones)

16. @kazoocon
Project “Wormhole“
 Inter-connecting accounts
 Connecting PBX trunks with
cloud users
 Voice VPNs
 Inter-branch routing
 Resources-like API for
precise number/Caller-ID
manipulations
 Designed with security in
mind

17. @kazoocon
Project “Sortinghat“
 DNS server for KAZOO
serving DNS zones for
account realms
 KAZOO Zone-aware
 Active SBC aware
 SRV records support
 NAPTR records support

18. @kazoocon
Project “bluemoon”
 LUA scripting inside
callflows and API
 Real time call variable
operations
 Number/Caller-ID
manipulations
 API calls support
Just imagine instantly adding a caller to blacklist by
dialing *-code while on call. Without pivot scripting!
Or creating an EXTENSION with one single API request…

19. @kazoocon
THREE STRATEGIES FOR
WORKING WITH OPEN
SOURCE PRODUCTS

20. STRATEGY #1 - WAITING
«We'll just wait for new features to arrive. And
spend nothing. Ha-ha!»
• Leads to «clone wars»
• No innovations
• Nobody's paying for new features and they never
arrive!!!
• Open source projects die this way
• No energy

21. STRATEGY #2 – PARANOID
«We are not paying for features/bugfixes
others will use»
• Overprotecting Intellectual Property (not in the
spirit of open source)
• Leads to support for non-compatible versions
and increases costs of support and upgrades
• Breaks the natural flow of energy — the balance
of taking and giving
• Open source projects die this way as well

22. STRATEGY #3 (WIN-WIN ONE) - HYBRID
«We support open source base/core but have
private unique features as well»
• Combines open source support and proprietary/in-house
features/IP development
• Helps avoiding clone wars
• Makes competition healthier
• Drives progress
• Occasional «contributions» and «grand open sourcing» of
previously closed features raise the bar and help industry
grow
• Open source projects live long this way
• Room for developers/companies to live and earn
• WIN-WIN

23. @kazoocon
DEVELOPING (FOR) KAZOO IS
FUN… AND ART… AND
BUSINESS
LET’S ROCK!

24. Thank You!
#kazoocon14

25. @kazoocon
US site: www.siplabs.org
E-mail: info@siplabs.org