RFC 4904: Representing Trunk Groups in tel/sip Uniform Resource Identifiers (URIs)
In plain English — editorial summary, not part of the RFC
This document describes a standardized mechanism to convey trunk group parameters in sip and tel Uniform Resource Identifiers (URIs). An extension to the tel URI is defined for this purpose. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4904
- Published
- June 2007
- Authors
- V. Gurbani; C. Jennings
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 19
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3807V5.2-User Adaptation Layer (V5UA)Current
June 2004
- RFC 3578Mapping of Integrated Services Digital Network (ISDN) User Part (ISUP) Overlap Signalling to the Session Initiation Protocol (SIP)Current
August 2003
- RFC 3398Integrated Services Digital Network (ISDN) User Part (ISUP) to Session Initiation Protocol (SIP) MappingCurrent
December 2002
- RFC 3372Session Initiation Protocol for Telephones (SIP-T): Context and ArchitecturesCurrent
September 2002
- RFC 5009Private Header (P-Header) Extension to the Session Initiation Protocol (SIP) for Authorization of Early MediaCurrent
September 2007
- RFC 3910The SPIRITS (Services in PSTN requesting Internet Services) ProtocolCurrent
October 2004
- RFC 3573Signalling of Modem-On-Hold status in Layer 2 Tunneling Protocol (L2TP)Current
July 2003
- RFC 3136The SPIRITS ArchitectureCurrent
June 2001
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?