audiocodes – a voip leader 13 years of operation focusing on voip media gateway & media...

Post on 29-Dec-2015

215 Views

Category:

Documents

0 Downloads

Preview:

Click to see full reader

TRANSCRIPT

Background

Listening Reading Observation:

Two approaches on carrier VoIP

Improve your business strategy

A Tale of Two Engineers

Doug and Hank

Hank – An Introduction

Career Home life Personal win

Who’s Hank working for?

What’s Hank working on?

New applications. Both Wireline and

Wireless Adding pictures, music,

video

What’s Hank working on?

Fixed Mobile Convergence

Leveraging existing carrier’s network

Leveraging VoIP Standards based

(mostly) IP Multimedia

Subsystem

IMS Architecture

IMS Architecture

Business Model

Create greater value Up-sell customer

SMS Photo-mail Video-mail

Create new customers Family plan Prepaid

Create “stick” Avoid commoditization

Challenges

Staying compatible “Five-Nines” Reliability Financial limitations of existing carriers

Can’t build all of it “like we used to do”

Standard hardware platforms (cPCI and ATCA) Development time – “IMS is a five year project” Regulation hurdles

E911 CALEA

Doug – An Introduction

Career Home life Personal win

Who’s Doug working for?

What’s Doug working on?

Peer to Peer converged communications

Desktop based client Integrates

eMail Instant Messaging Presence Voice and video Collaboration

What’s Doug working on?

Applications leverage COTS equipment

Supports external dedicated devices (new!)

Standards based (mostly)

Open source tools and components

Business Model

Build a community of users Parasitic network application Charge for “off network communications”

Calls to PSTN IM

Optional Advanced Applications Messaging, IVR, Conferencing Spam, Spim and Do-not-call protection

Advertising? Business Edition

Challenges

Operating on a network you don’t control NAT, Firewalls, Packet filters Building a brand name Turning “cool” into “cash” Fickle user base Desktop crowding Support Regulation?

Conflict

Can these two very different approaches

co-exist?

Yes

They need to co-exist

Neither will fit every customer

Each will find their “purpose”

Consumers will drive adoption

Standards (like SIP) will allow interoperability

What are we doing? Working “both sides”

Products for both markets

HA Systems equipment PCI-based equipment CPE equipment Best of Breed Based on common software base

Our biggest challenge?

Being agile enough to address both:

Large NEPs and OEMs and

Smaller more agile ISVs and .com software companies

What can you do?

Standards are everything Put an end to the “download

my client to talk” thinking

Be responsive to market needs What ever happened to KISS approach?

Don’t make client/devices so complicated they’re useless

Is IMS KISS?

Participate in developing the regulation strategy

Proprietary

Thanks

Graphics by Brian Gocher

Alan PercyDirector of Business

DevelopmentAudioCodes, Inc.Alan.percy@audiocodes.comBooth #822

top related