signal) to indicate that this is not a new instance of the script
i.e., if there is no script executing at the present time do not
start executing a new one.
The "ir" signal is only associated with an executing script. If
none are running when a request for the event/signal is made, or
if a new script request is not included with the request, then the
"ir" signal/event will not be executed (i.e., the "ir" event with
its parameters is passed to an existing script for parsing and
execution and is considered opaque as far as MGCP as concerned.
If no such script exists, response code "800" will be returned,
indicating that the script is not executing).
The following response code is associated with this package:
Code Text Explanation
800 Script not Request for "ir" signal or event
Executing but no script is executing at the
time the request was received.
Note that package specific error codes include the package name
following the error code. For example, if error code 800 occurs
in response to a request with a transaction ID of 1001, it would
be sent as:
800 1001 /SCRIPT
3. IANA Considerations
The following packages and their versions have been registered with
IANA as per the instructions in [1].
Package Title Name Version
------------- ---- -------
Announcement A 1
DTMF D 1
Digit Map Extension DM1 0
Media Format FM 0
Generic G 1
Handset H 1
Line L 1
RTP R 1
Resource Reservation RES 0
Script SCRIPT 1
Supplementary Tones SST 0
Signal List SL 0
Trunk T 1
The following extension digit map letter has been registered with
IANA:
Package Letter
------- ------
DM1 P
The following Local Connections have been registered with IANA:
Field Name
------- -----
Media Format fmtp
Reservation Confirmation r-cnf
Reservation Direction r-dir
Resource Sharing r-sh
4. Security Considerations
The MGCP packages contained in this document do not require any
further security considerations beyond those indicated in the base
MGCP specification [1].
5. Acknowledgements
Special thanks are due to the authors of the original MGCP 1.0
specification: Mauricio Arango, Andrew Dugan, Isaac Elliott,
Christian Huitema, and Scott Picket.
Thanks also to the reviewers of this document, including but not
limited to: Jerry Kamitses, Sonus Networks; Dave Auerbach, Dan Wing,
Cisco Systems; Ed Guy, EMC Software; Martin Wakley, Nortel Networks.
6. References
6.1. Normative References
[1] Andreasen, F. and B. Foster, "Media Gateway Control Protocol
(MGCP) Version 1.0", RFC 3435, January 2003.
[2] Bellcore, "LSSGR: Switching System Generic Requirements for Call
Control Using the Integrated Services Digital Network User Part
(ISDNUP)", GR-317-CORE, Issue 2, December 1997.
[3] ITU-T, "Telephone User Part Signaling Procedures", ITU-T Q.724,
November 1988.
[4] ANSI, "OAM&P - Terminating Test Line Access and Capabilities",
T1.207-2000.
[5] Bellcore, "Notes on the Network", Special Report SR-2275, Issue
3, December 1997.
[6] Bellcore, "Call Processing" GR-505-CORE, Issue 1, December 1997.
[7] Bellcore, "LSSGR: Signaling for Analog Interfaces", GR-506-CORE,
Issue 1, June 1996.
[8] ITU-T, "Technical Characteristics of Tones for the Telephone
Service", ITU-T E.180, March 1998.
[9] ITU-T, "Various Tones Used in National Networks", ITU-T E.180,
Supplement 2, January 1994.
[10] ITU-T, "Applications of Tones and Recorded Announcements in
Telephone Services", ITU-T E.182, March 1998.
[11] Bellcore, "Call Forwarding Sub-Features FSD-01-02-1450, GR-586,
Issue 1, June 2000.
[12] Bellcore, "CPE Compatibility Considerations for the Voiceband
Data Transmission Interface", SR-TSV-002476, December 1992.
[13] Bellcore, "LSSGR: Visual Message Waiting Indicator Generic
Requirements (FSD 01-02-2000)", GR-1401, Issue 01, June 2000.
[14] Bellcore, "LSSGR Voiceband Data Transmission Interface", Section
6.6, GR-30-CORE, Issue 02, December 1998.
[15] Handley, M. and V. Jacobson, "SDP: Session Description
Protocol", RFC 2327, April 1998.
[16] Bellcore, "LSSGR: Call Waiting, FSD 01-02-1201", GR-571, Issue
01, June 2000.
[17] Bellcore, "LSSGR: Verification Connections FSD 25-05-0903", GR-
531-CORE, Issue 1, June 2000.
[18] Bellcore, " LSSGR: CLASS Feature: Calling Identity Delivery on
Call Waiting, FSD 01-02-1090, GR-575, Issue 01, June 2000.
[19] Postel, J., "Internet Control Message Protocol", STD 5, RFC 792,
September 1981.
[20] Bellcore, "Class Feature: Screen Editing (FSD 30-28-0000)", GR-
220, Issue 2, April 2002.
[21] ITU-T, "Procedure for document facsimile transmission in the
general switched telephone network", ITU-T T.30, April 1999.
[22] ITU-T, "300 bits per second duplex modem standardized for use in
the general switched telephone network", ITU-T V.21, November
1988.
[23] Telcordia Technologies, "Telcordia Technologies Specification of
Signaling System Number 7", GR-246-CORE, Issue 7, December 2002.
[24] Telcordia Technologies, "LSSGR: CLASS Feature: Calling Name
Delivery Generic Requirements (FSD 01-02-1070)", GR-1188, Issue
02, December 2000.
[25] Telcordia Technologies, "LSSGR: CLASS Feature: Calling Number
Delivery (FSD 01-02-1051)", GR-31, Issue 01, June 2000.
[26] Schulzrinne, H. and S. Casner, "RTP Profile for Audio and Video
Conferences with Minimal Control", RFC 3551, July 2003.
[27] Braden, R., Ed., Zhang, L., Berson, S., Herzog, S. and S. Jamin,
"Resource ReSerVation Protocol (RSVP) -- Version 1 Functional
Specification", RFC 2205, September 1997.
[28] Berners-Lee, T., Masinter, L. and M. McCahill, Eds., "Uniform
Resource Locators (URL)", RFC 1738, December 1994.
[29] Schulzrinne, H., Rao, A. and R. Lanphier, "Real Time Streaming
Protocol (RTSP)", RFC 2326, April 1998.
[30] Berners-Lee, T., Fielding, R. and L. Masinter, "Uniform Resource
Identifiers (URI): Generic Syntax", RFC 2396, August 1998.
[31] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119, March 1997.
6.2. Informative References
[32] Perkins, C., Kouvelas, I., Hodson, O., Hardman, V., Handley, M.,
Bolot, J.C., Vega-Garcia, A. and S. Fosse-Parisis, "RTP Payload
for Redundant Audio Data", RFC 2198, September 1997.
[33] Schulzrinne, H. and S. Petrack, "RTP Payload for DTMF Digits,
Telephony Tones and Telephony Signals", RFC 2833, May 2000.
[34] Foster, B., "MGCP CAS Packages", RFC 3064, February 2001.
[35] PacketCableTM, Dynamic Quality if Service Specification,
http://www.packetcable.com/downloads/specs/PKT-SP-DQOS-I07-
030815.pdf
[36] PacketCableTM Network-Based Call Signaling Protocol
http://www.packetcable.com/downloads/specs/PKT-SP-EC-MGCP-I08-
030728.pdf
[37] Groves, C., Pantaleo, M., Anderson, T. and T. Taylor, Eds.,
"Gateway Control Protocol Version 1", RFC 3525, June 2003.
[38] Arango, M., Dugan, A., Elliott, I., Huitema, C. and S. Pickett,
"Media Gateway Control Protocol (MGCP) Version 1.0", RFC 2705,
October 1999.
7. Authors’ Addresses
Bill Foster
Cisco Systems
Phone: +1 250 758 9418
EMail: bfoster@cisco.com
Flemming Andreasen
Cisco Systems
Edison, NJ 08837
EMail: fandreas@cisco.com
8. Full Copyright Statement
Copyright (C) The Internet Society (2003). All Rights Reserved.
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assignees.
This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.