This sessoin is led by Kevin Han, Senior Vice President with VoEx, Inc. I'm keenly interested in communities of interest and how they interact, so this session is particularly interesting to me.

This is not a terribly techinical presentation. This is about how to egt solutions to market, have impact...and make money naturally.

Looking at opportunities and critical componnts for success using VoIP for e-Communities. It's really a question of what we can do as a development community.

VoIP disruption has occurred. Ties to the vertically integrated Class 5 switch isn't what it was a few yeas ago. This disruption has been accepted as the trend to the future of telecommunications.

IP evolution is replacing monolithic, proprietary solutions. Innovation is increasing at a faster, dynamic and competitive environment.

What will be the celerant for VoIP? Cost reduction vs. Enhanced utility. "More of the same" or "me too" solutions limit the ability to advance. The VoIP community has been providing equivalent features to the telco environment. A more subtle challenge is the integraion between the walled gardens.

If applications will fuel the future growth and demand, does that integration point need to be inside the wall. Can it be at an integration layer to reach a broader market.

E-Communities are early adopters, Markets emerge over time through an established pipe. We don't know at the beginning of the journey what the killer app is. Communities are the early adopters and innovators that create that future. Multi-media, relime telephony experience exists, but it's just taking off.

Expect voice to no longer be driven by the telephone, but by the context of the business application.

The PC centric group of innovators and early adopters provides only a limited market. It's an application and integration proving ground. Apps ened to move to the web with any time anywhere access integrated withcommon infrastructure.

Kevin presented an eCommunities Managed Services "Stack". I can't replicate the visual here, but here's how the layers break out -
End Users Applications APIs Registries and Peering Transact Platform

It's not an architecture, but a conceptual service stack for providing an effective user experience across the community for all users. They;re things an apop devloper can't build from top to bottom.

What's missing? The core shared infrastructure of calling, registrationg, presencem provisioning and billing isn't really there. That's needed to support an integration layer across the walled gardens.

What to do? Wecan wait for evolution or we can band together as developers to dewfine the architecture,boundaies, requirements and interfaces to create an infrastructure we can share and support.

Lessons 1) Focus on your core application development and competency. Partner for the rest. 2) The core network is the place to integrate a cross walled garden set of applications. Note: This isn't enterprise apps, but carrier and service provider apps. 3) Broaden reach and distribution. Look for ways to reach multiple communities. Economy of scale.

Kevin did a nice job. The session just wasn't quite what I'd wanted myself. I'll have some more wrap-up thoughts after I can review my notes and post some cogen thoughts in the next few days.