Mobicents Summit 2012 - Thomas Quintana - The Future Of PBX With RestComm
Upcoming SlideShare
Loading in...5

Mobicents Summit 2012 - Thomas Quintana - The Future Of PBX With RestComm






Total Views
Views on SlideShare
Embed Views



1 Embed 28 28



Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment

Mobicents Summit 2012 - Thomas Quintana - The Future Of PBX With RestComm Mobicents Summit 2012 - Thomas Quintana - The Future Of PBX With RestComm Presentation Transcript

  • The Future of the PBX with RestComm Presented By: Thomas Quintana RestComm Project LeadDirector of Engineering @ TeleStax, Inc.
  • Target Audience● Carriers● Service Providers● Implementors of PBX-es
  • Requirements● Back to Back User Agent (ex. SipXecs)● Session Border Controller (ex. Acme Packet, OpenSIPs, etc.)
  • Network Address Translation● Breaks the SIP and Media paths● Most SIP UAs will require help with NAT traversal● STUN and ICE require SIP UA support● Using SBCs for NAT traversal is transparent and doesnt require SIP UA support
  • Clients Restful APIResource URI: 2012-04-24/Accounts/{AccountSid}/Clients/{ClientSid}A Client instance resource represents aRestComm user agent client. The Client listresource represents an accounts user agentclients.
  • Client Properties Property Description Sid The unique id of this client. ApiVersion The date that this resource was created. FriendlyName The human readable description for this client. AccountSid The unique id of the Account that created this client. Login The client user name. Password The client password. Status The status of this client. Possible values are VoiceUrl The URL RestComm will request when this client makes a call. VoiceMethod The HTTP method RestComm will use when requesting the VoiceUrl. Either GET or POST. VoiceFallbackUrl The URL RestComm will request in case there is an error executing or retrieving the RCML requested by the VoiceUrl.VoiceFallbackMethod The HTTP method RestComm will use when requesting the VoiceFallbackUrl. Either GET or POST.
  • Client PropertiesVoiceApplicationSid The Sid of the application that RestComm should use to handle outbound calls made by this client. If a VoiceApplicationSid is present RestComm will ignore the above set of urls and methods and use the one provided by the corresponding application. Uri The URI for this resource.
  • Client Resource Methods● DELETE – Delete a client resource.● GET – Retrieves an instance of the client resource.● POST/PUT – Creates a new client resource if it doesnt exist and otherwise updates the existing client resource.
  • Basic Extension with voice mail in RCML<Dial><Client>tom</Client></Dial><Say> You have reached the voice mail of ThomasQuintana. Please leave a message after thebeep and press pound or hangup to finishrecording.</Say><Record action=”voicemail”/>
  • Java Wrapper● Provides a domain specific language in Java for building communications applications using RestComm
  • Other Wrappers● Empower users to get started quickly with their favorite platform● Enable rapid application development and prototyping using RestComm● Enable non-Java shops to innovate with RestComm
  • Other Wrappers Status● There are ongoing community efforts to extend and port the remainder of the Twilio wrappers to RestComm. Current efforts are working on Ruby, PHP, and Scala
  • Questions & Answers Thank You! Thomas Quintana @thomasquintana