AdhearsionConf 2013 Keynote

The Last

The Last?!?

The Last?!?Hold your horses, I’m getting to it.

AdhearsionConf - A History

AdhearsionConf - A History

2010

AdhearsionConf - A History

2010

AdhearsionConf - A History

2010 2011

AdhearsionConf - A History

2010 2011

AdhearsionConf - A History

2010 2011 2012

AdhearsionConf - A History

2010 2011 2012

AdhearsionConf - Themes

AdhearsionConf - Themes

AdhearsionConf - Themes

2

AdhearsionConf - Themes

2

The Reboot of Real-Time Communications

The Reboot of Real-Time Communications

The Reboot of Real-Time Communications• Talk about Security and Privacy

The Reboot of Real-Time Communications• Talk about Security and Privacy• Talk about WebRTC and the future of RTC Apps

The Reboot of Real-Time Communications• Talk about Security and Privacy• Talk about WebRTC and the future of RTC Apps• Talk about Load Testing and Web Scale

The Reboot of Real-Time Communications• Talk about Security and Privacy• Talk about WebRTC and the future of RTC Apps• Talk about Load Testing and Web Scale• Talk about High Availability on the Internet

Rebooting Real-Time CommunicationsLet’s Talk About The Apps

We have the best toys

We have the best toys

We have the best toys

We have the best toys

We have the best toys

We have the best toys

We have the best toys

We have the best toys

We have the best toys

We have the best toys

We have the best toys

We have the best toys

But we still build this…

But we still build this…

But we still build this…

What should we build?

“Communicating isn’t going to be what you’re doing -

it’s what you’ll be doing while you’re doing something else”

- Geoff Hollingworth Ericsson Head of AT&T Foundry

RTC App Ideas3 Ideas

1. Incident Response

Incident Response•Timely, Contextual Information •Adapt for mobile vs. desktop users •Group-based communication •Inherit from existing organizational groups •Allow ad-hoc participants (“guest” parties) •Federate with external services

•Incident recording/logging •“Lessons learned” and process improvement •Links from/to issue tracking systems

2. Medical Records Management

Medical Records Management•Automate Medical Claims •Secure Caller Authentication •Reuse primary auth via website •Verify with voice biometrics •Cross-check against caller location

•Call recording/transcription •Medical advice given to patient automatically added to patient file •Auditing/Service Quality Assurance

3. Live, Anonymous Matchmaking

http://funnydate.com/have-a-chat

FunnyDate

FunnyDate

SHErlock22FemaleMaleOakdale

Books, Moustaches, Puzzles

Captain Beard 23

MaleFemale

Springfield

Books, Moustaches, Puzzles

USERNAMEAGE

GENDERSEEKINGCITY

MATCHINGINTERESTS

Live, Anonymous Matchmaking•Safe Introductions •Strict anonymity •No need to exchangephone numbers •Low friction interface enables users to connect in real-time •Silly video tricks used to break the ice •...or even add more anonymity

•Negligible operating costs relative to traditional telephony

FunnyDate

We have the best toystools!

Stop building this…

Build this!

The Last

The End?

The End?NOT

Adhearsion - The Framework for RTC

Adhearsion - The Framework for RTC• Adhearsion Roadmap

Adhearsion - The Framework for RTC• Adhearsion Roadmap• Ahn1: Framework for Asterisk

Adhearsion - The Framework for RTC• Adhearsion Roadmap• Ahn1: Framework for Asterisk• Ahn2: Framework for Voice

Adhearsion - The Framework for RTC• Adhearsion Roadmap• Ahn1: Framework for Asterisk• Ahn2: Framework for Voice• Ahn3: Framework for Real Time Communications

Adhearsion - The Framework for RTC• Adhearsion Roadmap• Ahn1: Framework for Asterisk• Ahn2: Framework for Voice• Ahn3: Framework for Real Time Communications• Includes Voice/Telephony

Adhearsion - The Framework for RTC• Adhearsion Roadmap• Ahn1: Framework for Asterisk• Ahn2: Framework for Voice• Ahn3: Framework for Real Time Communications• Includes Voice/Telephony• Goes into Text/Video

Powerful New Apps

Powerful New Apps

Powerful New Apps

Powerful New Apps

Powerful New Apps

Powerful New Apps

Bridging The Two Worlds

Bridging The Two Worlds

Bridging The Two Worlds

Telephones in Web Browsers!

Telephones in Web Browsers!

Telephones in Web Browsers!Telephones in Web Browsers!

http://

Get m

e Bob

ple

ase!

SDP:

v=0

o=al

ice 2

0518 0

IN IP

4 0.0

.0.0

s=-

t=0 0

m

=audio

54609 R

TP/SAVPF 1

09

SDP:v=0 o=bob 19915 0 IN IP4 0.0.0.0

s=- t=0 0 m=audio 61001 RTP/SAVPF 109

Alice Bob

SRTP

SRTP

http://

Get m

e Bob

ple

ase!

SDP:

v=0

o=al

ice 2

0518 0

IN IP

4 0.0

.0.0

s=-

t=0 0

m

=audio

54609 R

TP/SAVPF 1

09

SDP:v=0 o=bob 19915 0 IN IP4 0.0.0.0

s=- t=0 0 m=audio 61001 RTP/SAVPF 109

Alice Bob

SRTP

SRTP

http://

Get m

e Bob

ple

ase!

SDP:

v=0

o=al

ice 2

0518 0

IN IP

4 0.0

.0.0

s=-

t=0 0

m

=audio

54609 R

TP/SAVPF 1

09

SDP:v=0 o=bob 19915 0 IN IP4 0.0.0.0

s=- t=0 0 m=audio 61001 RTP/SAVPF 109

Alice Bob

SRTP

SRTP

X

Hallmarks of Future RTC Apps

Hallmarks of Future RTC Apps• User-centric Identities

Hallmarks of Future RTC Apps• User-centric Identities• Facebook, Twitter, LinkedIn (see: Twelephone)

Hallmarks of Future RTC Apps• User-centric Identities• Facebook, Twitter, LinkedIn (see: Twelephone)• Corporate Identities (Active Directory/Lync)

Hallmarks of Future RTC Apps• User-centric Identities• Facebook, Twitter, LinkedIn (see: Twelephone)• Corporate Identities (Active Directory/Lync)

• Peer-to-Peer when appropriate (ICE! STUN! TURN!)

Hallmarks of Future RTC Apps• User-centric Identities• Facebook, Twitter, LinkedIn (see: Twelephone)• Corporate Identities (Active Directory/Lync)

• Peer-to-Peer when appropriate (ICE! STUN! TURN!)• Secure By Default (HTTPS for signaling, SRTP for media)

Hallmarks of Future RTC Apps• User-centric Identities• Facebook, Twitter, LinkedIn (see: Twelephone)• Corporate Identities (Active Directory/Lync)

• Peer-to-Peer when appropriate (ICE! STUN! TURN!)• Secure By Default (HTTPS for signaling, SRTP for media)• Nothing to Download (HTML5 FTW!)

Hallmarks of Future RTC Apps• User-centric Identities• Facebook, Twitter, LinkedIn (see: Twelephone)• Corporate Identities (Active Directory/Lync)

• Peer-to-Peer when appropriate (ICE! STUN! TURN!)• Secure By Default (HTTPS for signaling, SRTP for media)• Nothing to Download (HTML5 FTW!)• Communicate by URL (and come back to it later)

Hallmarks of Future RTC Apps• User-centric Identities• Facebook, Twitter, LinkedIn (see: Twelephone)• Corporate Identities (Active Directory/Lync)

• Peer-to-Peer when appropriate (ICE! STUN! TURN!)• Secure By Default (HTTPS for signaling, SRTP for media)• Nothing to Download (HTML5 FTW!)• Communicate by URL (and come back to it later)• Embedded in some larger task

Hallmarks of Future RTC Apps• User-centric Identities• Facebook, Twitter, LinkedIn (see: Twelephone)• Corporate Identities (Active Directory/Lync)

• Peer-to-Peer when appropriate (ICE! STUN! TURN!)• Secure By Default (HTTPS for signaling, SRTP for media)• Nothing to Download (HTML5 FTW!)• Communicate by URL (and come back to it later)• Embedded in some larger task• Contextual