1 / 10

SIP for VoIP Applications March 2004

SIP for VoIP Applications March 2004. Agenda. SIP Overview Why SIP? SIP for VoIP Applications The Future of SIP. SIP Overview. Session Initiation Protocol (SIP) is a HTTP-like, text-based, client-server-based signaling protocol (Created by IETF).

ghazi
Download Presentation

SIP for VoIP Applications March 2004

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SIP for VoIP ApplicationsMarch 2004

  2. Agenda • SIP Overview • Why SIP? • SIP for VoIP Applications • The Future of SIP

  3. SIP Overview • Session Initiation Protocol (SIP) is a HTTP-like, text-based, client-server-based signaling protocol (Created by IETF). • It’s intended to create, modify and terminate multimedia sessions. • It can be used on the integrated voice, video and other interactive communication services. • It provides the extensive flexibility for future new applications.

  4. SIP Overview • SIP V1.0: RFC 2543 (1999). • SIP V2.0: RFC 3261 (2002). • RFC 3261: Session Initiation Protocol. • RFC 3262: Reliability of Provisional Responses in SIP. • RFC 3263: Locating SIP Servers. • RFC 3264: An Offer/Answer Model with the Session Description Protocol (SDP). • RFC 3265: SIP - Specific Event Notification.

  5. Why SIP? • Text-Based Protocol: Very easy for debugging and interoperability. • HTTP-like Protocol: Reuse the well-proven authentication (Digest) and encryption (SSL) mechanism used by HTTP. • Internet Standardized Protocol: Easy to integrate with other internet standard protocols to generate comprehensive services.

  6. Why SIP? • Relative shorter call setup time. • Flexibility for future extensions. • Easier to create new applications and services.

  7. SIP for VoIP Applications • Class 4/5 Soft-Switch: Fulfill current telecom services requirements for CLEC. • IP-PBX: Fulfill the current requirements for enterprises. • SIP-T: RFC 3372. Translation between PSTN domain and SIP domain. • 3G: SIP has been adopted by 3GPP for session signaling.

  8. SIP for VoIP Applications • Instant Messaging: RFC 3428. Exchange of short messages between parties in real time. • Presence: Allow users to do subscription and notify the users the change of state of individual user. • Walkie-Talkie: Real time voice communication among the members of a group.

  9. The Future of SIP • SIP will gradually dominate the IP telephony market. • SIP is not just for VoIP. It could be for V2oIP and other applications. • SIPPING (SIP Project INvestiGation) • PSTN and/or 3G telephony-equivalent applications that need a standardized approach. • Messaging-like applications of SIP. • Multi-party applications of SIP. • SIP calling to media servers.

  10. The Future of SIP • SIMPLE (SIP for Instant Messaging and Presence Leveraging Extensions) • IPTEL (IP Telephony) • Naming and Routing for VoIP Protocol (including SIP). • MMUSIC (Multiparty Multimedia Session Control) • SDP • RTP, RTCP, RTSP.

More Related