rfc3050 - Network Working Group J. Lennox Request for...

Info iconThis preview shows pages 1–3. Sign up to view the full content.

View Full Document Right Arrow Icon
Network Working Group J. Lennox Request for Comments: 3050 H. Schulzrinne Category: Informational Columbia U. J. Rosenberg dynamicsoft January 2001 Common Gateway Interface for SIP Status of this Memo This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. Copyright Notice Copyright (C) The Internet Society (2001). All Rights Reserved. Abstract In Internet telephony, there must be a means by which new services are created and deployed rapidly. In the World Wide Web, the Common Gateway Interface (CGI) has served as popular means towards programming web services. Due to the similarities between the Session Initiation Protocol (SIP) and the Hyper Text Transfer Protocol (HTTP), CGI is a good candidate for service creation in a SIP environment. This document defines a SIP CGI interface for providing SIP services on a SIP server. IESG Note The IESG notes that the mechanism specified here depends on the Common Gateway Interface. Should this interface change or be enhanced changes in this specification may also be necessary or appropriate. According to the W3C, the CGI is presently maintained by the NCSA Software Development Group. See http://www.w3c.org/cgi for additional information on the current state of the CGI interface. Lennox, et al. Informational [Page 1]
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
RFC 3050 CGI for SIP January 2001 Table of Contents 1 Introduction . ...................................... 3 2 Motivations . ....................................... 4 3 Differences from HTTP CGI . ......................... 5 3.1 Basic Model . ....................................... 6 3.2 Persistence Model . ................................. 8 3.3 SIP CGI Triggers . .................................. 9 3.4 Naming . ............................................ 9 3.5 Environment Variables . ............................. 9 3.6 Timers . ............................................ 10 4 Overview of SIP CGI . ............................... 10 5 SIP CGI Specification . ............................. 12 5.1 Introduction . ...................................... 12 5.1.1 Relationship with HTTP CGI . ........................ 12 5.1.2 Conventions of This Document . ...................... 12 5.1.3 Specifications . .................................... 12 5.1.4 Terminology . ....................................... 13 5.2 Notational Conventions and Generic Grammar . ........ 13 5.3 Invoking the Script . ............................... 14 5.4 The SIP CGI Script Command Line . ................... 14 5.5 Data Input to the SIP CGI Script . .................. 14 5.5.1 Message Metadata (Metavariables) . .................. 14 5.5.1.1 AUTH_TYPE . ......................................... 16 5.5.1.2 CONTENT_LENGTH . .................................... 16 5.5.1.3 CONTENT_TYPE . ...................................... 17 5.5.1.4 GATEWAY_INTERFACE . ................................. 17 5.5.1.5 Protocol-Specific Metavariables . ................... 18 5.5.1.6
Background image of page 2
Image of page 3
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 36

rfc3050 - Network Working Group J. Lennox Request for...

This preview shows document pages 1 - 3. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online