RFC 5140: A Telephony Gateway REgistration Protocol (TGREP)
In plain English — editorial summary, not part of the RFC
This document describes the Telephony Gateway Registration Protocol (TGREP) for registration of telephony prefixes supported by telephony gateways and soft switches. The registration mechanism can also be used to export resource information. The prefix and resource information can then be passed on to a Telephony Routing over IP (TRIP) Location Server, which in turn can propagate that routing information within and between Internet Telephony Administrative Domains (ITADs). TGREP shares a lot of similarities with the TRIP protocol. It has similar procedures and finite state machine for session establishment. It also shares the same format for messages and a subset of attributes with TRIP. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5140
- Published
- March 2008
- Authors
- M. Bangalore; R. Kumar; J. Rosenberg; H. Salama; D.N. Shah
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 28
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3872Management Information Base for Telephony Routing over IP (TRIP)Current
September 2004
- RFC 3219Telephony Routing over IP (TRIP)Updated
January 2002
- RFC 2871A Framework for Telephony Routing over IPCurrent
June 2000
- RFC 9506Explicit Host-to-Network Flow Measurements TechniquesCurrent
October 2023
- RFC 5139Revised Civic Location Format for Presence Information Data Format Location Object (PIDF-LO)Current
February 2008
- RFC 5133Terminal Endpoint Identifier (TEI) Query Request Number ChangeCurrent
December 2007
- RFC 5124Extended Secure RTP Profile for Real-time Transport Control Protocol (RTCP)-Based Feedback (RTP/SAVPF)Current
February 2008
- RFC 5118Session Initiation Protocol (SIP) Torture Test Messages for Internet Protocol Version 6 (IPv6)Current
February 2008
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?