idnits 2.17.1 draft-pickett-ipdc-management-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-20) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard == It seems as if not all pages are separated by form feeds - found 0 form feeds but 28 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 189 instances of weird spacing in the document. Is it really formatted ragged-right, rather than justified? ** There is 1 instance of lines with control characters in the document. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 148: '... MUST This word, or the adjecti...' RFC 2119 keyword, line 151: '... MUST NOT This phrase means tha...' RFC 2119 keyword, line 154: '... SHOULD This word, or the adjective ...' RFC 2119 keyword, line 159: '... MAY This word, or the adjective "...' RFC 2119 keyword, line 161: '...lude this option MUST be prepared to i...' (97 more instances...) Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 14 has weird spacing: '... This docum...' == Line 15 has weird spacing: '...), its areas...' == Line 16 has weird spacing: '... and its w...' == Line 20 has weird spacing: '... and may be...' == Line 21 has weird spacing: '...me. It is i...' == (184 more instances...) == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: The flag field MUST have bit one (Mandatory Support) set. The flag field MUST not have bit four (Vendor Specific AVP) set. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: The flag field MUST have bit one (Mandatory Support) set. The flag field MUST not have bit four (Vendor Specific AVP) set. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: The flag field MUST have bit one (Mandatory Support) set. The flag field MUST not have bit four (Vendor Specific AVP) set. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: The flag field MUST have bit one (Mandatory Support) set. The flag field MUST not have bit four (Vendor Specific AVP) set. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: The flag field MUST have bit one (Mandatory Support) set. The flag field MUST not have bit four (Vendor Specific AVP) set. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: The flag field MUST have bit one (Mandatory Support) set. The flag field MUST not have bit four (Vendor Specific AVP) set. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: The flag field MUST have bit one (Mandatory Support) set. The flag field MUST not have bit four (Vendor Specific AVP) set. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: The flag field MUST have bit one (Mandatory Support) set. The flag field MUST not have bit four (Vendor Specific AVP) set. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: The flag field MUST have bit one (Mandatory Support) set. The flag field MUST not have bit four (Vendor Specific AVP) set. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: The flag field MUST have bit one (Mandatory Support) set. The flag field MUST not have bit four (Vendor Specific AVP) set. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: The flag field MUST have bit one (Mandatory Support) set. The flag field MUST not have bit four (Vendor Specific AVP) set. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: The flag field MUST have bit one (Mandatory Support) set. The flag field MUST not have bit four (Vendor Specific AVP) set. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: The flag field MUST have bit one (Mandatory Support) set. The flag field MUST not have bit four (Vendor Specific AVP) set. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: The flag field MUST have bit one (Mandatory Support) set. The flag field MUST not have bit four (Vendor Specific AVP) set. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: The flag field MUST have bit one (Mandatory Support) set. The flag field MUST not have bit four (Vendor Specific AVP) set. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: The flag field MUST have bit one (Mandatory Support) set. The flag field MUST not have bit four (Vendor Specific AVP) set. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: AVP Flags The flag field MUST have bit one (Mandatory Support) set. The flag field MUST not have bit four (Vendor Specific AVP) set. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: The flag field MUST have bit one (Mandatory Support) set. The flag field MUST not have bit four (Vendor Specific AVP) set. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: The flag field MUST have bit one (Mandatory Support) set. The flag field MUST not have bit four (Vendor Specific AVP) set. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: The flag field MUST have bit one (Mandatory Support) set The flag field MUST not have bit four (Vendor Specific AVP) set. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: The flag field MUST have bit one (Mandatory Support) set. The flag field MUST not have bit four (Vendor Specific AVP) set. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: The flag field MUST have bit one (Mandatory Support) set. The flag field MUST not have bit four (Vendor Specific AVP) set. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: The flag field MUST have bit one (Mandatory Support) set. The flag field MUST not have bit four (Vendor Specific AVP) set. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: The flag field MUST have bit one (Mandatory Support) set. The flag field MUST not have bit four (Vendor Specific AVP) set. -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (August 1998) is 9380 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: '3' is mentioned on line 1281, but not defined == Missing Reference: '2' is mentioned on line 1279, but not defined == Missing Reference: '4' is mentioned on line 1281, but not defined == Missing Reference: '5' is mentioned on line 1282, but not defined == Missing Reference: '6' is mentioned on line 1283, but not defined == Missing Reference: '7' is mentioned on line 1283, but not defined == Unused Reference: '1' is defined on line 1278, but no explicit reference was found in the text -- No information found for - is the name correct? -- Possible downref: Normative reference to a draft: ref. '1' Summary: 11 errors (**), 0 flaws (~~), 39 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 INTERNET DRAFT IPDC Device Management Protocol August 1998 3 INTERNET DRAFT Scott Pickett 4 Vertical Networks 5 Title: draft-pickett-ipdc-management-00.txt Alan Mikhak 6 Date: August 1998 Vertical Networks 8 IPDC 9 Device Management Protocol 10 12 Status of this Memo 14 This document is an Internet-Draft. Internet-Drafts are working 15 documents of the Internet Engineering Task Force (IETF), its areas, 16 and its working groups. Note that other groups may also distribute 17 working documents as Internet-Drafts. 19 Internet-Drafts are draft documents valid for a maximum of six months 20 and may be updated, replaced, or obsoleted by other documents at any 21 time. It is inappropriate to use Internet-Drafts as reference 22 material or to cite them other than as ``work in progress.'' 24 To learn the current status of any Internet-Draft, please check the 25 ``1id-abstracts.txt'' listing contained in the Internet-Drafts Shadow 26 Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe), 27 munnari.oz.au (Pacific Rim), ftp.ietf.org (US East Coast), or 28 ftp.isi.edu (US West Coast). 30 Abstract 32 The protocol described in this document is a member of the IP Device 33 Control (IPDC) family of protocols. The IPDC protocols are proposed 34 as a protocol suite, components of which can be used individually or 35 together to perform connection control, media control, and signaling 36 transport for environments where the service control logic is 37 separated from the network access server. Please see the references 38 section for other IPDC documents. 40 The protocol specification presented here is intended for use between 41 a media gateway controller and a media gateway. The media gateway 42 may be capable of acting as a voice over IP gateway, voice over ATM 43 gateway, dialup modem media gateway, circuit switch, or cross- 44 connect. Using the IP Device Management protocol presented here, the 45 media gateway controller can obtain status and receive notification 46 of management events from the Media Gateway or between Media 47 Gateways. 49 Table of Contents 51 1.0 Introduction 52 1.1 Background 53 2.0 Protocol Definition 54 2.1 Specification of Requirements 55 2.2 Messages 56 2.3 Restart 57 2.3.1 RSIP - Restart In Progress 58 2.4 Configuration and Status 59 2.4.1 NINF - Notify Information 60 2.4.2 RINF - Request Information 61 2.4.3 SINF - Set Information 62 3.0 AVP Values 63 3.1 Media Gateway Type AVP 64 3.2 Maximum Modules AVP 65 3.3 Media Gateway Controller In Use AVP 66 3.4 Number of Lines AVP 67 3.5 Module Type AVP 68 3.6 Module Capabilities AVP 69 3.7 Module Status AVP 70 3.8 Number of Channels AVP 71 3.9 Resource ID AVP 72 3.10 Line Coding AVP 73 3.11 Line Framing AVP 74 3.12 Line Signaling Details AVP 75 3.13 Line In-Band Signaling Details AVP 76 3.14 Line Status AVP 77 3.15 Channel Status AVP 78 3.16 Channel Status Change TimeStamp AVP 79 3.17 List of Media Gateway Controllers AVP 80 3.18 Number of Lines in Line Status Array AVP 81 3.19 Line Status Array AVP 82 3.20 Number of channels in the Channel Status Array AVP 83 3.21 Channel Status Array AVP 84 3.22 Number of Failed Lines AVP 85 3.23 T1 Front End Type AVP 86 3.24 T1 CSU Build-out AVP 87 3.25 T1 DSX Line Length AVP 88 3.26 Forward Signaling Events to the Media Gateway Controller AVP 89 4.0 Security Considerations 90 5.0 Rights and Permissions 91 6.0 References 92 7.0 Acknowledgments 93 8.0 Author's Address 95 1.0 Introduction 97 The protocol specification presented here is intended for use between 98 centralized switch control logic or Media Gateway Controller and a 99 Media Gateway. The Media Gateway may be capable of acting as a 100 circuit switch, voice over IP gateway, dialup modem access server, or 101 other messaging/conference server functions. Using the IP Device 102 Management protocol within this document, the Media Gateway 103 Controller can obtain status and receive notification of management 104 events from the Media Gateway or between Media Gateways. 106 1.1 Background 108 This protocol is part of the IP Device Control (IPDC) family of 109 protocols. The IPDC protocols have been proposed as a protocol suite 110 that can be used individually or together to perform connection 111 control, media control, status and signaling transport for 112 environments where the service control logic is separated from the 113 network Media Gateway. Please see the references section for other 114 IPDC documents. 116 This document describes the commands and attribute value pairs that 117 are necessary within the IPDC protocol to allow the Media Gateway 118 Controller to be notified of status and management functions on the 119 Media Gateway. The intent of the protocol is to leverage and be 120 aware of the functions and service that other management facilities 121 provide. By assuming that there are other management facilities, the 122 protocol can be streamlined and be used for only basic management 123 functions that may impact the Media Gateway Controller functionality. 124 It is also assumed that configuration of the Media Gateway is done 125 through separate means. Although notification of some configuration 126 changes are enabled, full provisioning and configuration requires a 127 separate set of functions and are not a part of this protocol. 129 This basic management protocol provides the Media Gateway Controller 130 with start-up, configuration notification, status and basic testing 131 facilities. Startup notifications to the Media Gateway Controller 132 include system reboot, initialization and restarting of Media Gateway 133 subsystems. Configuration notifications allow Media Gateway 134 Controller to be notified if any configuration event occurs including 135 those utilizing proprietary means. These configurations can be 136 through SNMP transactions or other configuration methods. The 137 protocol also allows for indication of testing procedures and tools 138 that can be in operation on the Media Gateway. These tests could 139 have an impact on the Media Gateway Controller core functions and are 140 thus taken into account in the protocol. 142 2 Protocol Definition 143 2.1 Specification of Requirements 145 In this document, several words are used to signify the requirements 146 of the specification. These words are often capitalized. 148 MUST This word, or the adjective "required", means that the 149 definition is an absolute requirement of the specification. 151 MUST NOT This phrase means that the definition is an absolute 152 prohibition of the specification. 154 SHOULD This word, or the adjective "recommended", means there may 155 exist valid reasons in particular circumstances to ignore this item, 156 but the full implications must be understood and carefully weighed 157 before choosing a different course. 159 MAY This word, or the adjective "optional", means that this item is 160 one of an allowed set of alternatives. An implementation which does 161 not include this option MUST be prepared to interoperate with another 162 implementation which does include the option. 164 2.2 Messages 166 This section describes the IP Device Management (IPDM) commands that 167 are described within this document. 169 2.3 Restart 171 The media gateway sends a RSIP message to the media gateway 172 controller when a management system directs it to restart. The RSIP 173 message initiates a transaction identified per IPDC base document. 174 The transaction completes when the media gateway controller returns 175 an Acknowledgement message to the media gateway. 177 On a forced restart, the media gateway controller immediately sends 178 the Acknowledgement message to the media gateway. 180 On a graceful restart, the media gateway controller releases all 181 resources it is using on the media gateway before responding with the 182 Acknowledgment message. 184 The media gateway can unilaterally complete the restart transaction 185 if it does not receive an Acknowledgement within the specified time. 187 2.3.1 RSIP - Restart In Progress 188 0 1 2 3 189 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 190 +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 191 | | 192 | Message Header | 193 | | 194 +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 195 | Diameter Command AVP Code | 196 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 197 | AVP Length | AVP Flags | Reserved | 198 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 199 | Restart In Progress Command Code | 200 +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 201 | | 202 | Transaction Originator Host-Name AVP | 203 | | 204 +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 205 | | 206 | Restart Method AVP | 207 | | 208 +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 209 | | 210 | Restart Time AVP | 211 | | 212 +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 214 AVP Code 216 256 DIAMETER-Command 218 AVP Length 220 The length of this attribute MUST be at exactly 12. 222 AVP Flags 224 The flag field MUST have bit one (Mandatory Support) set. Bit two 225 (SS-Encrypted-Data), Bit three (PK-Encrypted-Data) and Bit four 226 (Vendor-Specific-AVP) SHOULD NOT be set. 228 Reserved 230 The Reserved field MUST be set to zero (0). 232 Command Code 234 1600 Device Management Restart In Progress 236 Transaction Originator Host Name AVP 238 The host name of the initiator of the transaction. This is a 239 required parameter for all IPDC protocol messages. 241 Restart Method AVP 243 This field MUST specify one of the following values: 244 00000001 Forced Restart 245 00000002 Graceful Restart 247 This is a required parameter. 249 Restart Time AVP 251 This field specifies number of seconds the media gateway waits for 252 an Acknowledgement from the media gateway controller before 253 restarting. This is a required parameter. 255 2.4 Configuration and Status 257 The media gateway controller may send a Request Information (RINF) 258 message to a media gateway, which instructs the media gateway to 259 respond with a Notify Information (NINF) message containing the 260 requested information. The RINF begins a transaction, and the 261 corresponding NINF ends the transaction. The media gateway MUST 262 respond to a RINF message with a NINF or Message Reject message. 264 The media gateway controller may send a Set Information (SINF) 265 message to the media gateway, which instructs the media gateway to 266 set some limited configuration values. The media gateway MUST 267 respond to a SINF message with an NINF or Message Reject message. 268 The NINF or Message Reject message completes the transaction. 270 The media gateway can send unsolicited NINF messages to the media 271 gateway controller to inform it of changes made to its system 272 information by other management systems. An unsolicited NINF message 273 initiates a transaction, and the transaction is completed when the 274 media gateway controller returns either a Command Acknowledgement or 275 a Message Reject. 277 2.4.1 NINF - Notify Information 279 0 1 2 3 280 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 281 +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 282 | | 283 | Message Header | 284 | | 285 +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 286 | Diameter Command AVP Code | 287 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 288 | AVP Length | AVP Flags | Reserved | 289 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 290 | Restart In Progress Command Code | 291 +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 292 | | 293 | Transaction Originator Host-Name AVP | 294 | | 295 +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 296 | | 297 | Resource Identifier AVP | 298 | | 299 +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 300 | | 301 | Forward Signaling Events AVP | 302 | | 303 +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 305 AVP Code 307 256 DIAMETER-Command 309 AVP Length 311 The length of this attribute MUST be at exactly 12. 313 AVP Flags 315 The flag field MUST have bit one (Mandatory Support) set. Bit two 316 (SS-Encrypted-Data), Bit three (PK-Encrypted-Data) and Bit four 317 (Vendor-Specific-AVP) SHOULD NOT be set. 319 Reserved 321 The Reserved field MUST be set to zero (0). 323 Command Code 325 1601 Device Management Notify Information 327 Transaction Originator Host Name AVP 329 The host name of the initiator of the transaction. This is a 330 required parameter for all IPDC protocol messages. 332 Resource Identifier AVP 333 The Resource Identifier is the unique identifier for the resource 334 or group of resources on a media gateway to which the NINF command 335 applies. The Resource Identifier is of type IPDC Reference, 336 defined in [3]. 338 Forward Signaling Events AVP 340 Indicates whether the media gateway should forward signaling 341 events to the media gateway controller 343 Conditional AVPs when IPDC-Reference specifies gateway 344 +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 345 | | 346 | Maximum Number of Modules AVP | 347 | | 348 +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 349 | | 350 | Media Gateway Controller In Use AVP | 351 | | 352 +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 353 | | 354 | List of Media Gateway Controllers AVP | 355 | | 356 +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 357 | | 358 | Media Gateway Type AVP | 359 | | 360 +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 362 Conditional AVPs when IPDC-Reference specifies equip-holder 363 +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 364 | | 365 | Module Capapbilites AVP | 366 | | 367 +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 368 | | 369 | Number of Lines AVP | 370 | | 371 +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 372 | | 373 | Number of Failed Lines AVP | 374 | | 375 +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 376 | | 377 | External Name AVP | 378 | | 379 +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 380 | | 381 | Line Status Array AVP | 382 | | 383 +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 385 Conditional AVPs when IPDC-Reference specifies trunk-term or access- 386 term 387 +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 388 | | 389 | Bearer Capapbilites AVP | 390 | | 391 +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 392 | | 393 | Calling Party Number AVP | 394 | | 395 +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 396 | | 397 | Dialed Phone Number AVP | 398 | | 399 +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 400 | | 401 | Timestamp of last channel status transition AVP | 402 | | 403 +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 404 | | 405 | Media Gateway Call Identifier AVP | 406 | | 407 +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 409 Conditional AVPs when IPDC-Reference specifies trans-term 410 +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 411 | | 412 | Number of Channels AVP | 413 | | 414 +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 415 | | 416 | External Name AVP | 417 | | 418 +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 419 | | 420 | Line Coding AVP | 421 | | 422 +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 423 | | 424 | Framing AVP | 425 | | 426 +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 427 | | 428 | Signaling AVP | 429 | | 430 +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 431 | | 432 | In-Band Signaling Details AVP | 433 | | 434 +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 435 | | 436 | T1 front end type AVP | 437 | | 438 +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 439 | | 440 | T1 CSU build out AVP | 441 | | 442 +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 443 | | 444 | T1 DSX-1 line length AVP | 445 | | 446 +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 447 | | 448 | Channel Status Array AVP | 449 | | 450 +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 452 2.4.2 RINF - Request Information 454 0 1 2 3 455 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 456 +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 457 | | 458 | Message Header | 459 | | 460 +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 461 | Diameter Command AVP Code | 462 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 463 | AVP Length | AVP Flags | Reserved | 464 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 465 | Restart In Progress Command Code | 466 +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 467 | | 468 | Transaction Originator Host-Name AVP | 469 | | 470 +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 471 | | 472 | Resource Identifier AVP | 473 | | 474 +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 476 AVP Code 478 256 DIAMETER-Command 480 AVP Length 482 The length of this attribute MUST be at exactly 12. 484 AVP Flags 486 The flag field MUST have bit one (Mandatory Support) set. Bit two 487 (SS-Encrypted-Data), Bit three (PK-Encrypted-Data) and Bit four 488 (Vendor-Specific-AVP) SHOULD NOT be set. 490 Reserved 492 The Reserved field MUST be set to zero (0). 494 Command Code 496 1602 Device Management Request Information 498 Transaction Originator Host Name AVP 500 The host name of the initiator of the transaction. This is a 501 required parameter for all IPDC protocol messages. 503 Resource Identifier AVP 505 The Resource Identifier is the unique identifier for the resource 506 or group of resources on a media gateway to which the NINF command 507 applies. The Resource Identifier is of type IPDC Reference, 508 defined in [3]. 510 2.4.3 SINF - Set Information 512 0 1 2 3 513 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 514 +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 515 | | 516 | Message Header | 517 | | 518 +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 519 | Diameter Command AVP Code | 520 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 521 | AVP Length | AVP Flags | Reserved | 522 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 523 | Restart In Progress Command Code | 524 +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 525 | | 526 | Transaction Originator Host-Name AVP | 527 | | 528 +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 529 | | 530 | Forward Signaling Events AVP | 531 | | 532 +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 533 | | 534 | Resource Identifier AVP | 535 | | 536 +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 537 | | 538 | Maximum Number of Modules AVP | 539 | | 540 +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 541 | | 542 | Media Gateway Controller In Use AVP | 543 | | 544 +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 545 | | 546 | List of Media Gateway Controllers AVP | 547 | | 548 +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 550 AVP Code 552 256 DIAMETER-Command 554 AVP Length 556 The length of this attribute MUST be at exactly 12. 558 AVP Flags 560 The flag field MUST have bit one (Mandatory Support) set. Bit two 561 (SS-Encrypted-Data), Bit three (PK-Encrypted-Data) and Bit four 562 (Vendor-Specific-AVP) SHOULD NOT be set. 564 Reserved 566 The Reserved field MUST be set to zero (0). 568 Command Code 570 1603 Device Management Set Information 572 Transaction Originator Host Name AVP 574 The host name of the initiator of the transaction. This is a 575 required parameter for all IPDC protocol messages. 577 Resource Identifier AVP 579 The Resource Identifier is the unique identifier for the resource 580 or group of resources on a media gateway to which the NINF command 581 applies. The Resource Identifier is of type IPDC Reference, 582 defined in [3]. 584 3 AVP Values 586 This section will define the new AVP that are applicable to the 587 commands described within this document. Some of the base AVPs such 588 as Message Code, Transaction ID, Endpoint Address and Connection 589 Type are defined in the IPDC base specification document. 591 3.1 Media Gateway Type AVP 593 AVP Code 595 1700 Media Gateway Type 597 AVP Length 599 The length of this attribute MUST be at least 12 to accommodate 600 the AVP header plus 4 bytes of data. 602 AVP Flags 604 The flag field MUST have bit one (Mandatory Support) set. The 605 flag field MUST not have bit four (Vendor Specific AVP) set. 607 Media Gateway Type 609 The Media Gateway Type field is of type String. 611 3.2 Maximum Modules AVP 613 AVP Code 615 1701 Maximum Modules 617 AVP Length 618 The length of this attribute MUST be 0x000C (12). The maximum 619 modules field is a 4 byte value. 621 AVP Flags 623 The flag field MUST have bit one (Mandatory Support) set. The 624 flag field MUST not have bit four (Vendor Specific AVP) set. 626 Maximum Modules 628 Maximum modules specifies the maximum number of modules (slot 629 cards) supported. 631 3.3 Media Gateway Controller In Use AVP 633 AVP Code 635 1702 Media Gateway Controller In Use 637 AVP Length 639 The length of this attribute MUST be 0x000C (12) to accommodate 8 640 bytes of AVP header information plus a 4 byte data for the index 641 of the Media Gateway Controller currently in use. 643 AVP Flags 645 The flag field MUST have bit one (Mandatory Support) set. The 646 flag field MUST not have bit four (Vendor Specific AVP) set. 648 Media Gateway Controller In Use 650 The integer32 Index of the Media Gateway Controller In Use as 651 primary. 653 3.4 Number of Lines AVP 655 AVP Code 657 1703 Number of Lines 659 AVP Length 661 The length of this attribute MUST be 0x000C (12) to accommodate 8 662 bytes of AVP header information plus a 4 byte data for number of 663 lines. 665 AVP Flags 667 The flag field MUST have bit one (Mandatory Support) set. The 668 flag field MUST not have bit four (Vendor Specific AVP) set. 670 Number of Lines 672 The Number of Lines field specifies the number of physical line 673 interfaces within a module. 675 3.5 Module Type AVP 677 AVP Code 679 1705 Module type 681 AVP Length 683 The length of this attribute MUST be 0x000C(12) to accommodate 8 684 bytes of AVP header information plus 4 byte indication of Module 685 Type. 687 AVP Flags 689 The flag field MUST have bit one (Mandatory Support) set. The 690 flag field MUST not have bit four (Vendor Specific AVP) set. 692 Module Type 694 Presently only the following module type values are specified: 695 0x00000000 not present 696 0x00000001 unknown Other values are to be defined. 698 3.6 Module Capabilities AVP 700 AVP Code 702 1706 Module Capabilities 704 AVP Length 706 The length of this attribute MUST be 0x0012(18) to accommodate 8 707 bytes of AVP header information plus 4 byte indication of Module 708 Capabilities. 710 AVP Flags 712 The flag field MUST have bit one (Mandatory Support) set. The 713 flag field MUST not have bit four (Vendor Specific AVP) set. 715 Module Capabilities 717 The Module Capabilities value is a Logical OR of any of the 718 following flags: 719 0x00000001 Capable of continuity testing 720 0x00000002 Network Interface module 722 3.7 Module Status AVP 724 AVP Code 726 1707 Module Status 728 AVP Length 730 The length of this attribute MUST be 0x0012(18) to accommodate 8 731 bytes of AVP header information plus 4 byte indication of Module 732 Status. 734 AVP Flags 736 The flag field MUST have bit one (Mandatory Support) set. The 737 flag field MUST not have bit four (Vendor Specific AVP) set. 739 Module Status 741 Describes the status of the module. The following values may 742 apply: 743 0x00000000 not present (empty) 744 0x00000001 out of service (down) 745 0x00000002 up 746 0x00000003 error 748 3.8 Number of Channels AVP 750 AVP Code 752 1709 Number of Channels 754 AVP Length 756 The length of this attribute MUST be at least 0x0012(18) to 757 accommodate 8 bytes of AVP header information plus 4 byte 758 indication of the number of channels within the line. 760 AVP Flags 762 The flag field MUST have bit one (Mandatory Support) set. The 763 flag field MUST not have bit four (Vendor Specific AVP) set. 765 Number of Channels 767 Specifies the number of channels within a channelized line 768 interface. 770 3.9 Resource ID AVP 772 AVP Code 774 1710 Resource ID 776 AVP Length 778 The length of this attribute MUST be at least 12 to accommodate 8 779 bytes of AVP header information plus a minimum 4 bytes for the 780 Resource ID. 782 AVP Flags 784 The flag field MUST have bit one (Mandatory Support) set. The 785 flag field MAY have bit four (Vendor Specific AVP) set. 787 Resource ID 789 The Resource ID field is of type IPDC Reference as defined in [3]. 790 . The Resource ID AVP identifies the resource or resources to 791 which an IPDM command applies. 793 3.10 Line Coding AVP 795 AVP Code 797 1711 Line Coding 799 AVP Length 800 The length of this attribute MUST be 0x000C(12) to accommodate 8 801 bytes of AVP header information plus 4 byte Line Coding Data. 803 AVP Flags 805 The flag field MUST have bit one (Mandatory Support) set. The 806 flag field MUST not have bit four (Vendor Specific AVP) set. 808 Line Coding 810 The following values apply to the Line Coding field: 811 0x00000000 Unknown 812 0x00000001 AMI 813 0x00000002 B8ZS 815 3.11 Line Framing AVP 817 AVP Code 819 1712 Line Framing 821 AVP Length 823 The length of this attribute MUST be 0x000C(12) to accommodate 8 824 bytes of AVP header information plus a 4 byte Line Framing data 825 field 827 AVP Flags 829 The flag field MUST have bit one (Mandatory Support) set. The 830 flag field MUST not have bit four (Vendor Specific AVP) set. 832 Line Framing 834 Describes the framing used for the line. Valid values are: 835 0x00000000 Unknown 836 0x00000001 D4 837 0x00000002 ESF 839 3.12 Line Signaling Details AVP 841 AVP Code 843 1713 Line Signaling Details 845 AVP Length 846 The length of this attribute MUST be 0x000C(12) to accommodate 8 847 bytes of AVP header information plus a 4 byte data. 849 AVP Flags 851 The flag field MUST have bit one (Mandatory Support) set. The 852 flag field MUST not have bit four (Vendor Specific AVP) set. 854 Line Signaling Details 856 The following values apply to the Line Signaling Details field: 857 0x00000000 Unknown 858 0x00000001 In-band 859 0x00000002 ISDN PRI 860 0x00000003 NFAS 861 0x00000004 SS7 gateway 863 3.13 Line In-Band Signaling Details AVP 865 AVP Code 867 1714 Line In-Band Signaling Details 869 AVP Length 871 The length of this attribute MUST be 0x000C(12) to accommodate 8 872 bytes of AVP header information plus 4 byte indication of data. 874 AVP Flags 876 The flag field MUST have bit one (Mandatory Support) set. The 877 flag field MUST not have bit four (Vendor Specific AVP) set. 879 Line In-Band Signaling Details 881 The following values apply to the Line Signaling Details field: 882 0x00000000 Unknown 883 0x00000001 Wink Start 884 0x00000002 Idle Start 885 0x00000003 wink-wink with 200msec wink 886 0x00000004 wink-wink with 400msec wink 887 0x00000005 loop start CPE 888 0x00000006 ground start CPE 890 3.14 Line Status AVP 892 AVP Code 893 1715 Line Status 895 AVP Length 897 The length of this attribute MUST be exactly 0x000C(12) to 898 accommodate 8 bytes of AVP header information plus 4 byte Line 899 Status Data. 901 AVP Flags 903 The flag field MUST have bit one (Mandatory Support) set. The 904 flag field MUST not have bit four (Vendor Specific AVP) set. 906 Line Status 908 Describes the Line State. The following Line States apply: 909 0x00000000 not present 910 0x00000001 disabled 911 0x00000002 red alarm (loss of sync) 912 0x00000003 yellow alarm 913 0x00000004 other alarms or errors 914 0x00000005 up 915 0x00000006 loopback 917 3.15 Channel Status AVP 919 AVP Code 921 1716 Latency Threshold 923 AVP Length 925 The length of this attribute MUST be at exactly 0x000C(12) to 926 accommodate 8 bytes of AVP header information plus a 4 byte 927 indication of the latency threshold. 929 AVP Flags 931 The flag field MUST have bit one (Mandatory Support) set. The 932 flag field MUST not have bit four (Vendor Specific AVP) set. 934 Channel Status 936 The following are valid values for the channel status field: 937 0x00000000 not present 938 0x00000001 out of service 939 0x00000002 signaling channel (i.e. D Channel on an ISDN PRI 940 line) 941 0x00000003 maintenance (continuity test pending or in 942 progress) 943 0x00000004 blocked 944 0x00000005 loopback 945 0x00000006 idle 946 0x00000007 in use (dialing, ringing, etc) 947 0x00000008 connected 948 0x00000009 in use/DSP output 949 0x0000000A in use/DSP input 950 0x0000000B in use/DSP input + output 951 0x0000000C off hook/idle 953 3.16 Channel Status Change TimeStamp AVP 955 AVP Code 957 1717 Channel Status Changed Timestamp 959 AVP Length 961 The length of this attribute MUST be 0x000C(12) to accommodate 8 962 bytes of AVP header information plus a 4 byte data value. 964 AVP Flags 966 The flag field MUST have bit one (Mandatory Support) set. The 967 flag field MUST not have bit four (Vendor Specific AVP) set. 969 Channel Status Changed Timestamp 971 The Channel Status Changed Timestamp field is of type Time. 973 3.17 List of Media Gateway Controllers AVP 975 AVP Code 977 1718 List of Media Gateway Controllers 979 AVP Length 981 The length of this attribute MUST be at least 0x000C(12) to 982 accommodate 8 bytes of AVP header information plus a 4 byte data 983 value. 985 AVP Flags 986 The flag field MUST have bit one (Mandatory Support) set. The 987 flag field MAY have bit four (Vendor Specific AVP) set. 989 List of Media Gateway Controllers 991 The list of media gateway controllers is an ordered list of 32-bit 992 IP addresses for the media gateway controllers which can control 993 the media gateway. The number of media gateway controllers in the 994 list is (AVP Length - 8) / 4. 996 3.18 Number of Lines in Line Status Array AVP 998 AVP Code 1000 1719 Number of Lines in Line Status Array 1002 AVP Length 1004 The length of this attribute MUST be at exactly 0x000C(12) to 1005 accommodate 8 bytes of AVP header information plus a 4 byte value 1006 indicating the number of lines specified in a Line Status Array 1007 AVP. 1009 AVP Flags 1011 The flag field MUST have bit one (Mandatory Support) set. The 1012 flag field MUST not have bit four (Vendor Specific AVP) set. 1014 Number of Lines in Line Status Array 1016 The Number of Lines in Line Status Array AVP is used to indicate 1017 the number of entries in a following Line Status Array AVP. 1019 3.19 Line Status Array AVP 1021 AVP Code 1023 1720 Line Status Array 1025 AVP Length 1027 The length of this attribute MUST be at least 0x000C(12) to 1028 accommodate 8 bytes of AVP header information plus a minimum 4 1029 byte value (indicating Line Status for at least one line). 1031 AVP Flags 1032 The flag field MUST have bit one (Mandatory Support) set. The 1033 flag field MUST not have bit four (Vendor Specific AVP) set. 1035 Line Status Array 1037 Describes an array of Line State values. Each Line State value 1038 can be one of the following: 1039 0x00000000 not present 1040 0x00000001 disabled 1041 0x00000002 red alarm (loss of sync) 1042 0x00000003 yellow alarm 1043 0x00000004 other alarms or errors 1044 0x00000005 up 1045 0x00000006 loopback 1047 The Number of entries in this array is reported by the Number 1048 of Lines in the Line Status Array AVP. 1050 3.20 Number of channels in the Channel Status Array AVP 1052 AVP Code 1054 1721 Number of channels in the channel status array 1056 AVP Length 1058 The length of this attribute MUST be 0x000C(12) to accommodate 8 1059 bytes of AVP header information plus a 4 byte value indicating the 1060 number of entries in the channel status array. 1062 AVP Flags 1064 The flag field MUST have bit one (Mandatory Support) set. The 1065 flag field MUST not have bit four (Vendor Specific AVP) set. 1067 Number of channels in the channel status array 1069 The Number of channels in the channel status array AVP is used to 1070 indicate the number of channel state entries in the Channel State 1071 Array AVP 1073 The Number of channels in the channel status array field is of 1074 type Integer32. 1076 3.21 Channel Status Array AVP 1077 AVP Code 1079 1722 Channel Status Array 1081 AVP Length 1083 The length of this attribute MUST be at least 0x000C(12) to 1084 accommodate 8 bytes of AVP header information plus a minimum 4 1085 byte value indicating at least one channel state . 1087 AVP Flags 1089 The flag field MUST have bit one (Mandatory Support) set. The 1090 flag field MUST not have bit four (Vendor Specific AVP) set. 1092 Channel Status Array 1094 Describes an array of channel state values. Each channel state 1095 value can be one of the following: 1096 0x00000000 not present 1097 0x00000001 out of service 1098 0x00000002 signaling channel (i.e. D Channel on an ISDN PRI 1099 line) 1100 0x00000003 maintenance (continuity test pending or in 1101 progress) 1102 0x00000004 blocked 1103 0x00000005 loopback 1104 0x00000006 idle 1105 0x00000007 in use (dialing, ringing, etc) 1106 0x00000008 connected 1107 0x00000009 in use/DSP output 1108 0x0000000A in use/DSP input 1109 0x0000000B in use/DSP input + output 1110 0x0000000C off hook/idle 1112 The number of entries in the channel state array is specified 1113 by the Number of channels in the channel status array AVP 1115 3.22 Number of Failed Lines AVP 1117 AVP Code 1119 1723 Number of Failed Lines 1121 AVP Length 1123 The length of this attribute MUST be 0x000C(12) to accommodate 8 1124 bytes of AVP header information plus a 4 byte data field. 1126 AVP Flags 1128 The flag field MUST have bit one (Mandatory Support) set The flag 1129 field MUST not have bit four (Vendor Specific AVP) set. 1131 Number of Failed Lines 1133 The Number of Failed Lines AVP is used in a Notify Module 1134 information message sent by an Media Gateway 1136 The Number of Failed Lines field is of type Integer32. 1138 3.23 T1 Front End Type AVP 1140 AVP Code 1142 1724 T1 Front End Type 1144 AVP Length 1146 The length of this attribute MUST be 0x000C(12) to accommodate 8 1147 bytes of AVP header information plus a 4 byte data field. 1149 AVP Flags 1151 The flag field MUST have bit one (Mandatory Support) set. The 1152 flag field MUST not have bit four (Vendor Specific AVP) set. 1154 T1 Front End Type 1156 The following are the valid values for T1 Front End Type: 1157 0x00000000 Unknown 1158 0x00000001 CSU (T1 long haul) 1159 0x00000002 DSX-1 (T1 Short Haul) 1161 3.24 T1 CSU Build-out AVP 1163 AVP Code 1165 1725 T1 CSU Build-out 1167 AVP Length 1169 The length of this attribute MUST be 0x000C(12) to accommodate 8 1170 bytes of AVP header information plus a 4 byte data field. 1172 AVP Flags 1174 The flag field MUST have bit one (Mandatory Support) set. The 1175 flag field MUST not have bit four (Vendor Specific AVP) set. 1177 T1 CSU Build-out 1179 The following are the valid values for T1 CSU Build-out: 1180 0x00000000 0 dB 1181 0x00000001 7.5 dB 1182 0x00000002 15 dB 1183 0x00000003 22.5 dB 1185 3.25 T1 DSX Line Length AVP 1187 AVP Code 1189 1726 T1 DSX Line Length 1191 AVP Length 1193 The length of this attribute MUST be 0x000C(12) to accommodate 8 1194 bytes of AVP header information plus a 4 byte data field. 1196 AVP Flags 1198 The flag field MUST have bit one (Mandatory Support) set. The 1199 flag field MUST not have bit four (Vendor Specific AVP) set. 1201 T1 DSX Line Length 1203 The following are the valid values for T1 DSX Line Length: 1204 0x00000000 1-133 ft 1205 0x00000001 134-266 ft 1206 0x00000002 267-399 ft 1207 0x00000003 400-533 ft 1208 0x00000003 534-655 ft 1210 3.26 Forward Signaling Events to the Media Gateway Controller AVP 1212 AVP Code 1214 1727 Forward Signaling Events to the Media Gateway Controller 1216 AVP Length 1217 The length of this attribute MUST be 0x000C(12) to accommodate 8 1218 bytes of AVP header information plus a 4 byte data field. 1220 AVP Flags 1222 The flag field MUST have bit one (Mandatory Support) set. The 1223 flag field MUST not have bit four (Vendor Specific AVP) set. 1225 Forward Signaling Events to the Media Gateway Controller 1227 Indicates whether the Media Gateway should send signaling events 1228 to the Media Gateway Controller. The following are valid values: 1229 0x00000000 Do not send signaling events 1230 0x00000001 Send signaling events IPDC type 1231 0x00000002 Q.931 type 1232 0x00000003 Tunnel type 1234 4 Security Considerations 1236 Security issues are not discussed in this memo. The security 1237 mechanisms recommended are those specified in [3]. 1239 5 Rights and Permissions 1241 The contributors to this document are listed in the author's address 1242 and acknowledgement sections of the document. All contributors to 1243 this document and the organizations we represent grant an unlimited 1244 perpetual, non-exclusive, royalty-free, world-wide right and license 1245 to any party under the copyrights in the contribution. This license 1246 includes the right to copy, publish and distribute the contribution 1247 in any way, and to prepare derivative works that are based on or 1248 incorporate all or part of the contribution, the license to such 1249 derivative works to be of the same scope as the license of the 1250 original contribution. The contributors grant permission to reference 1251 the names and addresses of the contributors and of the organizations 1252 we represent. We agree that no information in the contribution is 1253 confidential and that the any party may freely disclose any 1254 information in the contribution. 1256 The contributors to this document believe that the organizations we 1257 represent have the authority to grant the rights stated herein. The 1258 contributors to this document will grant any party a perpetual, non- 1259 exclusive, royalty-free, world-wide right to implement, use and 1260 distribute the technology or works when implementing, using or 1261 distributing technology based upon the specific specification. 1263 The contributors represent that we have disclosed the existence of 1264 any proprietary or intellectual property rights in the contribution 1265 that are reasonably and personally known to the contributors. The 1266 contributors do not represent that we personally know of all 1267 potentially pertinent proprietary and intellectual property rights 1268 owned or claimed by the organization he represents (if any) or third 1269 parties. 1271 The contributors represent that there are no limits to the 1272 contributors' ability to make the grants, acknowledgments and 1273 agreements above that are reasonably and personally known to the 1274 contributors. 1276 6 References 1278 [1] Calhoun, Rubens, "DIAMETER Base Protocol", Internet-Draft, draft- 1279 calhoun-diameter-03.txt, May 1998 [2] Calhoun, Zorn, Pan, "DIAMETER 1280 Framework", Internet-Draft, draft-calhoun-diameter-framework-00.txt, 1281 May 1998 [3] Taylor, "IP Device Control Base Protocol", [4] Dugan, 1282 "IP Connection Control Protocol", [5] Skran, "IP Device Control 1283 Framework" [6] Elliott, "IP Media Control Protocol" [7] Bell, "IP 1284 Signaling Protocol" 1286 7 Acknowledgments 1288 The author wishes to acknowledge the following individuals for their 1289 contribution to the IP Media Control protocol: 1291 Ilya Akramovich, Bob Bell, Dan Brendes, Peter Chung, Russ Dehlinger, 1292 Andrew Dugan, Ike Elliott, Cary FitzGerald, Jan Gronski, Tom Hess, 1293 Geoff Jordan, Tony Lam, Shawn Lewis, Dave Mazik, Pete O'Connell, 1294 Shyamal Prasad, Paul Richards, Dale Skran, Louise Spergel, Raj 1295 Srinivasan, Tom Taylor, Michael Thomas. 1297 8 Author's Addresses 1299 Questions about this memo can be directed to: 1301 Scott Pickett 1302 Vertical Networks 1303 1148 East Arques Ave 1304 Sunnyvale, CA 94086 1306 Phone: (408) 523-9700 extension 200 1307 Fax: (408) 523-9701 1308 Email: ScottP@vertical.com 1309 Alan Mikhak 1310 Vertical Networks 1311 1148 East Arques Ave 1312 Sunnyvale, CA 94086 1314 Phone: (408) 523-9700 extension 292 1315 Fax: (408) 523-9701 1316 Email: AlanM@vertical.com