SIP's Role in Open Source

1
SIP's Role in Open Source

• Alan D. Percy
• Director of Business Development
• AudioCodes, Inc.
• Alan.percy_at_audiocodes.com
• 1-716-662-2769

2
Who is AudioCodes?

• OEM Manufacturer of Enabling VoIP equipment
• Gateways
• Media Servers
• Chips and Modules
• Key IPR holder for G.723.1
• 11th Year in Business
• 82.8M Revenue for FY04
• Over 440 Employees
• HQ in Israel
• Six offices in US

3
Perspective on Market
4
What Makes Open Source Work?

• Need or market opportunity that is widely
  understood
• Easily available standard hardware
• Standard development environment
• Access to test environment

5
Need or Market Opportunity

• Well understood
• Applications that most developers can grasp
• Broad horizontal applications
• Applies to many different businesses
• Broad appeal
• Opportunities for creativity
• A bit of Wouldnt it be great if to spur
  creativity
• Impact on every day life on the job

6
IP-PBX Application
FXS Gateway
FXS Gateway
WAN
SIP Phone
IP-PBX Application
Local Trunks (E911) FXO Gateway
T1/E1
Gateway
7
Standard PC Hardware

• Standard PC Platforms
• Wide range of choices
• White box simple servers
• Name Brand and High-end
• Linux Drivers Support
• Driver availability
• Full support for Linux
• Availability via Channel

IBM BladeCenter
8
VoIP Hardware

• Phones
• Simple one-line display phones
• Sophisticated Executive Phones
• Gateways
• Analog FXO Trunking
• Analog FXS Stations (POTS phones and FAX)
• Digital Trunking
• Media Servers
• Announcements, Transcoding and Conferencing

9
Standard Software Components

• Soft-phones
• Simple embedded-ready
• Full featured operator consoles
• Branding-enabled
• Operating Systems
• Linux

10
Standard Development Tools

• C
• Java
• Perl
• GNU
• Apache

11
Access to Test Environment

• To contribute, every developer needs access to a
  test environment
• No expensive equipment required!

12
What ties it all together?

• SIP

13
Where does SIP fit in?

• Call control to the phone
• Control of the gateways
• Control of the media server
• Message Indications
• Instant Messaging
• what else?

14
Why SIP?

• Driven by IETF RFC process
• Inherently open
• Despite all of the challenges
• Very Verbose
• Slow time to market
• Wait for consensus
• Rethink the terminal responsibilities
• Moving target

15
SIP - Results

• Community of Investment has formed
• Created open development environment
• Base of reusable knowledge
• Lowered Bar of Entry
• Now almost any developer could contribute
• Expandable
• Not just telephone calls anymore

16
SIP A Case Study

• Pingtel
• IP-PBX Application
• Needed TDM Trunking Interfaces
• AudioCodes TP260/SIP
• PC-card Gateway
• SIP controlled
• Available through trained channel partners
• Interoperability and Certification
• One month

17
Other Existing Tools

• Linux (Redhat etc.)
• Turned the first earth
• Showed a working model
• Provided an application platform
• Development environment
• Ethereal (www.ethereal.com)
• Packet capture and decoding
• Selective tracing
• Makes diagnosis easier

18
Impact on Closed-source vendors?

• The closed-source vendors are
• Saying Who ya gonna call?
• Focusing on packaged solutions, service and
  support
• Opening portions of the applications
• Especially the IVR/ACD components
• VoiceXML, Plug-ins etc.
• Supporting name-brand phones and gateways

19
Closing Thoughts

• Is the real value proposition of an open-source
  PBX the initial cost of the software?
• Is an open-source PBX for everyone?
• What is the ideal open-source end-user?
• How will end-customers get long-term support?
• Will a network of support specialists evolve?
• What applications are next?

20
Thanks!