3. Company Background
●
●
Founded in 2010 to develop rich
communications products and solutions
Based in Whiteley, Hampshire and Google
Campus, London
●
Very experienced telecom development team
●
Deep signalling expertise
●
Big users of and contributors to open source
4. Crocodile Company Structure
Managing Director
John Parr
Technical Director
Peter Dunkley
Principal Engineer
Andrew Miller
Chairman
Konstantin Levchin
Engineering Director
Paul Pankhurst
Secretary
Susan
DaCosta-Greene
Marketing Intern
Romy Roynard
Principal Engineer
Hugh Waite
Principal Engineer
Gavin Llewelyn
Developer
James Wyatt
Finance Manager
Gina Westwell
Developer
Darryl Alexander
4
5. Crocodile and WebRTC (2011 - 2012)
●
●
●
●
Became aware of WebRTC during the second
half of 2011 and started following closely
towards the end of 2011
Started prototyping, demoing, and discussing
WebRTC with customers in Q2 2012
First public demo at Rich Communications
2012 (early November 2012 in Berlin)
Demonstrated MSRP for chat and file transfer
at WebRTC Conference and Expo 2012 (late
November 2012 in San Francisco)
6. Crocodile and WebRTC (2013 – so far)
●
●
●
●
Updated demo at FOSDEM 13 (early February
2013 in Brussels)
Improved demo UX shown at Kamailio World
(mid April 2013 in Berlin)
Participated in the ITSPA WebRTC event (early
May 2013)
Crocodile Network and SDK launch event (22
May 2013)
8. The Crocodile SDK
●
●
●
The Crocodile SDK provides an easy to use
API enabling rapid development of real-time
communication applications
The only thing that limits what you can do is
your imagination
The Crocodile SDK interacts with our webservice and wraps a SIP client stack, XMPP
client stack, and MSRP client stack.
10. The Crocodile Network (Web Service)
●
●
●
●
The Web Service provides a json API for
provisioning and management.
The Crocodile SDK uses the Web Service
Third-party websites can interact directly with
the Web Service
All access is over HTTPS
11. The Crocodile Network (Network Edge)
●
SIP Edge Proxy, XMPP Connection Manager,
MSRP Relay, TURN Server
●
All traffic from the SDK uses WSS
●
WSS connections are authenticated
●
Hosted traffic is routed into the Network Core
–
●
We can host domains
Remote traffic is routed to the remote network it
belongs to
–
We are just another interconnect
12. The Crocodile Network (Network Core)
●
SIP Proxy/Registrar
●
XMPP Server
●
Pre-Pay Application Server
●
Billing Server
●
Traffic must come from the Network Edge
13. Security, scalability, and reliability
●
●
●
All traffic connecting to the network is secure
(HTTPS and WSS)
The MSRP Relay and TURN Server use
ephemeral credentials
Amazon AWS Multi A-Z Deployment
–
EC2 servers with RDS database
–
SES for email and Route 53 for DNS
–
Elastic Beanstalk for web-services
–
ElastiCache, Redshift, and DynamoDB
14. What's next?
●
John Parr and Peter Dunkley will be at
“WebRTC Conference and Expo”, Atlanta, 25 –
27 June 2013
–
●
Peter Dunkley participating in the “Making the Right
Signalling Choices” session
Peter Dunkley will be at “DevCon5”, New York,
24-25 July 2013
–
Peter Dunkley will be presenting about WebSockets
on the “Advanced HTML5” track