Shared Converged Services

StateNets / Net@Edu ConferenceFebruary 13, 2008

2

Agenda

• Voice Services at ENA– Platform Design– Service Features– We can share!

• Shared Application Development

– A possible model for collaboration and sharing

• Q&A

3

ENA Converged Services

• Brief History– 2006: ENA decides to offer Voice/VoIP services

– 2007: Offer Voice services to 6 customers (Pilot)• Install 1st Voice Platform• Intercarrier agreements with RBOCS/CLECs etc.• First 6 Pilot School Districts• Offering Focuses on Hosted PBX/IP Centrex and SIP Trunking Services

– 2008: 20+ School Districts signed up for Services• ~20K IP Centrex End points• Multiple District-wide Trunking Solutions• Able to serve both Urban and Rural Districts

4

Service Requirements• Carrier-class

– Reliability of Telecommunications solution vitally important to K-12 community and their constituents

• Future Looking– Architecture allows for integration w/ future converged services

• Open Standards Architecture• SIP vs MGCP

• Feature Rich– Features should be equivalent to what customers could get with

proprietary CPE solutions

5

Platform Architecture

• Redundancy– Every key platform component is redundant (N+1)

– Redundant IP and PSTN connectivity

– Redundant utility power + battery + generator

– Platform can experience multiple component failure without dropping a call

– UPCOMING: Geographically diverse primary and backup platforms

• We’ve tried to this right, and can share

6

Multiple Layers of Administration

• Regional/Wholesale Administration• School District/End Customer Administration• End User Configuration Control

– End User Portal

– Attendant Console

7

Administrator’s Portal

8

Model for Shared Application Development

• Swisscom Model– Open Converged Services Platform available to developers world-

wide

– Mash-ups/widgets/scheduling apps etc.

– Swisscom can deploy any developed apps/services in Switzerland

– Contributors are free to deploy same services anywhere else

9

Q&A