The PINT Service Protocol: Extensions to SIP and SDP for IP Access to Telephone Call Services
RFC 2848

 
Document Type RFC - Proposed Standard (June 2000; No errata)
Last updated 2013-03-02
Stream IETF
Formats plain text pdf html
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state RFC 2848 (Proposed Standard)
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                        S. Petrack
Request for Comments: 2848                                      MetaTel
Category: Standards Track                                     L. Conroy
                                            Siemens Roke Manor Research
                                                              June 2000

                       The PINT Service Protocol:
   Extensions to SIP and SDP for IP Access to Telephone Call Services

Status of this Memo

   This document specifies an Internet standards track protocol for the
   Internet community, and requests discussion and suggestions for
   improvements.  Please refer to the current edition of the "Internet
   Official Protocol Standards" (STD 1) for the standardization state
   and status of this protocol.  Distribution of this memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (2000).  All Rights Reserved.

Abstract

   This document contains the specification of the PINT Service Protocol
   1.0, which defines a protocol for invoking certain telephone services
   from an IP network. These services include placing basic calls,
   sending and receiving faxes, and receiving content over the
   telephone. The protocol is specified as a set of enhancements and
   additions to the SIP 2.0 and SDP protocols.

Table of Contents

   1. Introduction .................................................  4
   1.1 Glossary ....................................................  6
   2. PINT Milestone Services ......................................  6
   2.1 Request to Call .............................................  7
   2.2 Request to Fax Content ......................................  7
   2.3 Request to Speak/Send/Play Content ..........................  7
   2.4 Relation between PINT milestone services and traditional
       telephone services ..........................................  7
   3. PINT Functional and Protocol Architecture ....................  8
   3.1. PINT Functional Architecture ...............................  8
   3.2. PINT Protocol Architecture .................................  9
   3.2.1. SDP operation in PINT .................................... 10
   3.2.2. SIP Operation in PINT .................................... 11
   3.3. REQUIRED and OPTIONAL elements for PINT compliance ......... 11
   3.4. PINT Extensions to SDP 2.0 ................................. 12

Petrack & Conroy            Standards Track                     [Page 1]
RFC 2848               The PINT Service Protocol               June 2000

   3.4.1. Network Type "TN" and Address Type "RFC2543" ............. 12
   3.4.2. Support for Data Objects within PINT ..................... 13
   3.4.2.1. Use of fmtp attributes in PINT requests ................ 15
   3.4.2.2. Support for Remote Data Object References in PINT ...... 16
   3.4.2.3. Support for GSTN-based Data Objects in PINT ............ 17
   3.4.2.4. Session Description support for included Data Objects .. 18
   3.4.3. Attribute Tags to pass information into the Telephone
          Network .................................................. 19
   3.4.3.1. The phone-context attribute ............................ 20
   3.4.3.2. Presentation Restriction attribute ..................... 22
   3.4.3.3. ITU-T CalledPartyAddress attributes parameters ......... 23
   3.4.4. The "require" attribute .................................. 24
   3.5. PINT Extensions to SIP 2.0 ................................. 25
   3.5.1. Multi-part MIME (sending data along with SIP request) .... 25
   3.5.2. Warning header ........................................... 27
   3.5.3. Mechanism to register interest in the disposition of a PINT
          service, and to receive indications on that disposition .. 27
   3.5.3.1. Opening a monitoring session with a SUBSCRIBE request .. 28
   3.5.3.2. Sending Status Indications with a NOTIFY request ....... 30
   3.5.3.3. Closing a monitoring session with an UNSUBSCRIBE request 30
   3.5.3.4. Timing of SUBSCRIBE requests ........................... 31
   3.5.4. The "Require:" header for PINT ........................... 32
   3.5.5. PINT URLs within PINT requests ........................... 32
   3.5.5.1. PINT URLS within Request-URIs .......................... 33
   3.5.6. Telephony Network Parameters within PINT URLs ............ 33
   3.5.7. REGISTER requests within PINT ............................ 34
   3.5.8. BYE Requests in PINT ..................................... 35
   4. Examples of PINT Requests and Responses ...................... 37
   4.1. A request to a call center from an anonymous user to receive
        a phone call ............................................... 37
   4.2. A request from a non anonymous customer (John Jones) to
Show full document text