1 / 37

voopIX

voopIX. Building the Educational VoIP Cloud in Croatia Branko Radojević , M.Sc . Deputy CEO September 20 1 4 . (v 2. 4 2 ). CARNet – Who we are & what we do?. Public Institution funded from National Budget NREN – National Research and Education Network

thimba
Download Presentation

voopIX

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. voopIX Building the Educational VoIPCloud in Croatia BrankoRadojević, M.Sc. Deputy CEO September 2014.(v 2.42)

  2. CARNet – Who we are & what we do? • Public Institution funded from National Budget • NREN – National ResearchandEducationNetwork • Over 20 years ISP for Educational Institutions in Croatia • (schools, universities, research institutes, ministry, agencies, • public hospitals, etc.) – 3000 locations in Croatia • Since 2004 adding more and more services for our members: • (National EducationalAA infrastructure, CMS for schools, LMS for schools, • National e-learning portal, National portal for schools, Content • filtering for schools, (many,many more), and voopIX ) • All our services are free for our member institutions

  3. CARNet – voopIX goals • To interconnect all our member institutions (3000 locations) to a single VoIP cloud and to provide to them: • Free telephony service between institutions • Interconnect different locations of the same institution • Let them use legacy PBXs with our system • Provide advanced telephony possibilities available only in VoIP PBXs • Provide free international calls to certain destinations for free • TRY TO BE AS TRANSPARENT TO THEM AS POSSIBLE • Open their eyes and let them discard legacy PBXs and move to VoIP

  4. How we arrived to this idea?

  5. voopIX - Evolution • It all started at the University of Dubrovnik in 2004. Telco Proprietary phones 1x ISDN PRI Legacy PBX 1x ISDN PRI

  6. voopIX – Evolution (cont’d) • In a matter of no time ... Telco DUNDi

  7. voopIX – Next Step In 2005 I’ve got married, moved to Zagreb and changed my employer to the current one .

  8. voopIX – Next Step (cont’d) • CARNet – my new employer already has ordered newVoIP PBX (normal PBX functionality + Call Center), but it’s a Cisco Call Manager • When it arrived, it took just few days to add an Asterisk to CCM (connected with SIP trunk), and to bring up DUNDi cloud and interconnect it with the Asterisks at theUniversityof Dubrovnik • It proved to be reliable solution, so why don’t expand it? • voopIX was born

  9. voopIX – Building the core • We started to buildvoopIX core, based onfive servers runningAsterisk positionedin five of our largestPOPs • Connections shown are logical DUNDI peeringconnections • No clustering at this time ZG OS RI ST DU

  10. voopIX – Legacy PBXs • Our members don’t want to throw away their working PBXs. Some of them were purchased recently  • We had to find a way to transparently connect them to our system. • Obviously, we are talking about hundreds of different combinations of PBXs, software, cards, setups, etc. • Telco connection is also non-unified: from R2/MFC, ISDN BRI, ISDN PRI and some SIP trunks (recently). • We had to put our box between PBX and the Telco connection in order to intercept calls. Our solution should be reliable.

  11. voopIX – Appliance (large) • Custom designed in CARNet • Runs Linux (debianlenny) + Asterisk • 2x or 4x ISDN PRI voice card installed • No hard drives • It has custom madefailover switch thatcan bypass the cardand connect backPBX directly to Telco. PBX Telco

  12. Interconnecting voopIX and PBX CARNet voopIX voopIX app. Telekom operator Old phones Legacy PBX BASIC

  13. Interconnecting voopIX and PBX (2) CARNet voopIX voopIX app. Telekom operator Old phones Legacy PBX BASIC HYBRID

  14. Interconnecting voopIX and PBX(3) CARNet voopIX / / voopIX app. Telekom operator Old phones Legacy PBX BASIC HYBRID ADVANCED

  15. voopIX - Appliance (cont’s)

  16. voopIX - Appliance (cont’s) FAILOVER SWITCH VOICE CARD NETWORK

  17. voopIX – Appliance (small) • Commerciallyavailable • Runs Linux + Asterisk • 1x FXS portinstalled • 2 module slotsavailable for line cards: • 4x FXO, 4xFXS, 2xBRI, 2xGSM • No hard drives, USB and SD Cardreaderincluded • It has failover switch thatcan bypass two FXO and FXSportsdirectly to Telco.

  18. voopIX – Callflows (availablenumber) DUNDi voopIX context IAX2 Lookup AVAILABLE Telco ISDN Network ISDN PRI ISDN PRI CALL Legacy PBX CDR (RADIUS)/LOG Server

  19. voopIX – Callflows (unavailablenumber) DUNDi voopIX context NOT AVAIL Lookup Telco ISDN Network ISDN PRI ISDN PRI CALL CALL Legacy PBX CDR (RADIUS)/LOG Server

  20. voopIX - Today 1 • Around 110locations (our first target were the institutions with larger phone installations and those considered most interestingones) • We expect to double thenumber until the end of2014. 1 51 12 4 2 1 7 1 1 1 9 1 1 10 6

  21. Problems we encountered - AOC • AOC = Advice Of Charge (D-During, E-End) Telco ISDN Network AOC-D ISDN PRI CALL AOC-E Legacy PBX

  22. Problems we encountered – AOC (cont’d) • AOC = Advice Of Charge (D-During, E-End) Telco ISDN Network AOC-D AOC-D ISDN PRI ISDN PRI CALL CALL AOC-E AOC-E Legacy PBX

  23. Asterisk Implementation Overview(Technical Details)

  24. Node becomes available Telco ISDN Network ZG [iax-pbx-reg] exten=> _38551400[5-7]XX OS RI IAX2 peering + registration DUNDi voopIX context ISDN PRI _38551400[5-7]XX ST Legacy PBX Numbers: (51)-400-500 to 400-799 DU

  25. Node becomes unavailable Telco ISDN Network ZG [iax-pbx-reg] exten=> _38551400[5-7]XX OS RI IAX2 peering + registration RIP DUNDi voopIX context ISDN PRI _38551400[5-7]XX ST NAGIOSServer Legacy PBX Numbers: (51)-400-500 to 400-799 DU

  26. Interconnection with TERENA NRENUM.net

  27. NRENUM.net • Since the two systems (ENUM and DUNDi) are incompatible, we had to build gateway service • Outgoing calls are easy to implement, since Asterisk has built-in ENUM support that we are using • Publishing our numbers to NRENUM tree were more difficult, since our system is highly dynamical, and DNS zones are more statical • We built on top of PowerDNS software that has ability to query not only its internal database, but also invoke script for subqueries. So, for every query that we receive through ENUM, we do subquery in DUNDi and return results.

  28. AdvancedTelephonyFunctionalityprovidedbyvoopIX

  29. Skype to PBX • We allow calls from Skype to any number in our system • Often used to place calls directly from web pages

  30. Users traveling around the World • We provide the possibility for user traveling around the World to use softphones which allows them to become extensions on their PBX • It is also useful to someone working from home • ZoIPer is a popular (and free) softphone which is beside having SIP protocol also provides IAX2 which has much lessproblems traversing NATs • Now available for Windows, MacOS, iPad/iPhone, Android, Windows Phone

  31. CentralizedServices(logging, monitoring, configuration, …)

  32. Centralized Services • Generally, we tend to use Open Source software: • Logging: Syslog NG • Fault Monitoring: Nagios • Graphs + Performance Monitoring: Munin • Accounting: FreeRADIUS + mySQL • Configuration+UserMgmt.+ … : Puppet

  33. voopIX Future ?

  34. voopIX – Future? • Scalability problem - not yet seen, but may become an issue • Web portal for members (billing, some setup, etc.) • Solution for smaller institutions (Schools on small islands) • Shown interest from other public/government institutions • Try to animate institutions in other countries to start up similar project and to peer with us - we’re ready to help • Add more advanced functions to our system

  35. OpenPlatform

  36. OpenPlatform • The idea here is to be able to create VoIP infrastructure on the Open Platform, which doesn’t rely on a single vendor, single technology or a proprietary solution • At any time, if there is a technology or protocol that shows up to be superior to currently used, we can move to them without investing in new equipment or paying additional licenses • By using central configuration, we can switch hundreds of appliances to new system in a matter of hours

  37. Thank you for your time ! voopix@carnet.hr All questions and suggestions are more then welcome.

More Related