RFC 3601: Text String Notation for Dial Sequences and Global Switched Telephone Network (GSTN) / E.164 Addresses
In plain English — editorial summary, not part of the RFC
This memo describes the full set of notations needed to represent a text string in a Dial Sequence. A Dial Sequence is normally composed of Dual Tone Multi Frequency (DTMF) elements, plus separators and additional "actions" (such as "wait for dialtone", "pause for N secs", etc.) which could be needed to successfully establish the connection with the target service: this includes the cases where subaddresses or DTMF menu navigation apply.
Document record
- Document ID
- RFC3601
- Published
- September 2003
- Authors
- C. Allocchio
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 10
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3660Basic Media Gateway Control Protocol (MGCP) PackagesCurrent
December 2003
- RFC 3666Session Initiation Protocol (SIP) Public Switched Telephone Network (PSTN) Call FlowsCurrent
January 2004
- RFC 3327Session Initiation Protocol (SIP) Extension Header Field for Registering Non-Adjacent ContactsUpdated
December 2002
- RFC 3286An Introduction to the Stream Control Transmission Protocol (SCTP)Current
May 2002
- RFC 4186Extensible Authentication Protocol Method for Global System for Mobile Communications (GSM) Subscriber Identity Modules (EAP-SIM)Current
January 2006
- RFC 4187Extensible Authentication Protocol Method for 3rd Generation Authentication and Key Agreement (EAP-AKA)Updated
January 2006
- RFC 4281The Codecs Parameter for "Bucket" Media TypesObsoleted
December 2005
- RFC 2833RTP Payload for DTMF Digits, Telephony Tones and Telephony SignalsObsoleted
May 2000
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?