[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

BCP 76, RFC 3666 on Session Initiation Protocol (SIP) Public Switched Telephone Network (PSTN) Call Flows




A new Request for Comments is now available in online RFC libraries.


        BCP 76
        RFC 3666

        Title:      Session Initiation Protocol (SIP)
                    Public Switched Telephone Network (PSTN) Call Flows
        Author(s):  A. Johnston, S. Donovan, R. Sparks, C. Cunningham,
                    K. Summers
        Status:     Best Current Practice
        Date:       December 2003
        Mailbox:    alan.johnston@mci.com, sdonovan@dynamicsoft.com,
                    rsparks@dynamicsoft.com,
                    ccunningham@dynamicsoft.com,
                    kevin.summers@sonusnet.com
        Pages:      118
        Characters: 200478
        SeeAlso:    BCP 76

        I-D Tag:    draft-ietf-sipping-pstn-call-flows-02.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3666.txt


This document contains best current practice examples of Session
Initiation Protocol (SIP) call flows showing interworking with the
Public Switched Telephone Network (PSTN).  Elements in these call
flows include SIP User Agents, SIP Proxy Servers, and PSTN
Gateways.  Scenarios include SIP to PSTN, PSTN to SIP, and PSTN to
PSTN via SIP.  PSTN telephony protocols are illustrated using ISDN
(Integrated Services Digital Network), ISUP (ISDN User Part), and FGB
(Feature Group B) circuit associated signaling.  PSTN calls are
illustrated using global telephone numbers from the PSTN and private
extensions served on by a PBX (Private Branch Exchange).  Call flow
diagrams and message details are shown.

This document is a product of the Session Initiation Proposal
Investigation Working Group of the IETF.

This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements.  Distribution of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
<ftp://ftp.isi.edu/in-notes/rfc3666.txt>