RFC 3661: Media Gateway Control Protocol (MGCP) Return Code Usage

In plain English — editorial summary, not part of the RFC

This document provides implementation guidelines for the use of return codes in RFC 3435, Media Gateway Control Protocol (MGCP) Version 1.0. Return codes in RFC 3435 do not cover all possible specific situations that may ever occur in a gateway. That is not possible and not necessary. What is important is to ensure that the Call Agent that receives a return code behaves appropriately and consistently for the given situation. The purpose of this document is to provide implementation guidelines to ensure that consistency.

Document record

Document ID

RFC3661

Published

December 2003

Authors

B. Foster; C. Sivachelvan

Status

INFORMATIONAL

Stream

INDEPENDENT

Area

—

Pages

24

Also known as

—

Updates:

RFC 3435

• Read the full RFC text →
• Plain text version
• IETF Datatracker history
• DOI: 10.17487/RFC3661

Topics

• guidelines
• call agent
• implementation

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

• RFC 3624The Media Gateway Control Protocol (MGCP) Bulk Audit PackageCurrent

  November 2003

• RFC 3383Internet Assigned Numbers Authority (IANA) Considerations for the Lightweight Directory Access Protocol (LDAP)Obsoleted

  September 2002

• RFC 2350Expectations for Computer Security Incident ResponseCurrent

  June 1998

• RFC 2209Resource ReSerVation Protocol (RSVP) -- Version 1 Message Processing RulesCurrent

  September 1997

• RFC 1704On Internet AuthenticationCurrent

  October 1994

• RFC 5657Guidance on Interoperation and Implementation Reports for Advancement to Draft StandardCurrent

  September 2009

• RFC 5767User-Agent-Driven Privacy Mechanism for SIPCurrent

  April 2010

• RFC 6271Requirements for SIP-Based Session PeeringCurrent

  June 2011

Also filed under

• INFORMATIONAL
• 2003
• INDEPENDENT stream