Network Working Group T. Taylor
Request for Comments: 2886 Nortel Networks
Category: Standards Track August 2000
Network Working Group T. Taylor
Request for Comments: 2886 Nortel Networks
Category: Standards Track August 2000
Megaco Errata
Megaco勘误表
Status of this Memo
本备忘录的状况
This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.
本文件规定了互联网社区的互联网标准跟踪协议，并要求进行讨论和提出改进建议。有关本协议的标准化状态和状态，请参考当前版本的“互联网官方协议标准”（STD 1）。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The Internet Society (2000). All Rights Reserved.
版权所有（C）互联网协会（2000年）。版权所有。
This document records the errors found in the Megaco/H.248 protocol document [2], along with the changes proposed in the text of that document to resolve them.
本文件记录了Megaco/H.248协议文件[2]中发现的错误，以及该文件文本中建议的解决错误的更改。
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC-2119 [1].
本文件中的关键词“必须”、“不得”、“要求”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照RFC-2119[1]中所述进行解释。
All section numbers are those of the relevant text of [2].
所有章节编号均为[2]相关文本的编号。
Section: 2 "References"
----------
Editorial: Add missing references to I.363.5 (AAL5) and RFC 1661
(PPP).
Section: 2 "References"
----------
Editorial: Add missing references to I.363.5 (AAL5) and RFC 1661
(PPP).
Editorial: delete unused reference to Q.724.
社论：删除未使用的Q.724参考。
Editorial: Leave Recommendations referred to in Annex C undated, implying latest issue.
社论：将附件C中提到的建议保留为未注明日期，暗示最新版本。
Editorial: add reference to RFC 2805, the Megaco requirements document.
编辑：添加对RFC 2805的参考，即Megaco要求文件。
Section: 4 "Abbreviations"
----------
Editorial: delete unused abbreviation BRI.
Section: 4 "Abbreviations"
----------
Editorial: delete unused abbreviation BRI.
Editorial: add explanations for GSM and IVR.
社论：添加GSM和IVR的解释。
Section: 6.2.2 "TerminationIDs"
----------
Issue: Not clear what wildcard union responses look like.
Section: 6.2.2 "TerminationIDs"
----------
Issue: Not clear what wildcard union responses look like.
Resolution: Add the following text:
"ie. Given termination Ta with properties p1=a, p2=b, and
termination Tb with properties p2=c, p3=d a UNION
response would be T* p1=a, p2=b,c, p3=d."
Resolution: Add the following text:
"ie. Given termination Ta with properties p1=a, p2=b, and
termination Tb with properties p2=c, p3=d a UNION
response would be T* p1=a, p2=b,c, p3=d."
Section: 6.2.4 "Termination Properties and descriptors"
----------
Issue: Says that property values set in Null context are remembered
and reinstated when termination returns to Null. Contradicts latest
text in 7.2.3.
Section: 6.2.4 "Termination Properties and descriptors"
----------
Issue: Says that property values set in Null context are remembered
and reinstated when termination returns to Null. Contradicts latest
text in 7.2.3.
Resolution: Rewrite the first paragraph from the third sentence onward, to read: "Most properties have default values, which are explicitly defined in this standard or in a package (see Section 12) or set by provisioning. If not provisioned otherwise, all descriptors except for TerminationState and LocalControl default to empty/"no value" when a termination is first created or is returned to the null context. The default contents of the two exceptions are described in sections 7.1.5 and 7.1.7."
解决方案：从第三句开始重写第一段，内容如下：“大多数属性都有默认值，这些默认值在本标准或包（见第12节）中明确定义，或通过设置进行设置。如果未另行设置，则除TerminationState和LocalControl外的所有描述符默认为空/”无值“当终止第一次创建或返回到空上下文时。第7.1.5节和第7.1.7节描述了两种例外情况的默认内容。”
Issue: DigitMap entry in table makes explicit reference to DTMF tones, but is also intended to apply to other in-band signalling systems.
问题：表中的DigitMap条目明确提及DTMF音调，但也适用于其他带内信令系统。
Resolution: Change existing text to new one as follows: "Defines patterns against which sequences of a specified set of events are to be matched so they can be reported as a group rather than singly."
解决方案：将现有文本更改为新文本，如下所示：“定义匹配指定事件集序列的模式，以便将它们作为一个组而不是单独报告。”
Section: 6.2.5 "Root Termination"
----------
Issue: Root can have statistics as well as properties and events.
Section: 6.2.5 "Root Termination"
----------
Issue: Root can have statistics as well as properties and events.
Resolution: add "statistics" to the fourth sentence of the first paragraph, listing what is valid for Root. Add "statistics" to what AuditValue can return for Root.
解决方案：在第一段的第四句中添加“统计”，列出对Root有效的内容。将“统计信息”添加到AuditValue可以为Root返回的内容中。
Section: 7.1 "Descriptors"
----------
Issue: it is unclear how to express empty descriptors in responses to
the MGC.
Section: 7.1 "Descriptors"
----------
Issue: it is unclear how to express empty descriptors in responses to
the MGC.
Proposed resolution: In section 7.1, add the following text after the sentence: "Descriptors may be returned as output from a command.": "In any such return of descriptor contents, an empty descriptor is represented by its name unaccompanied by any list."
建议的解决方案：在第7.1节中，在句子后面添加以下文本：“描述符可以作为命令的输出返回。”：“在任何此类描述符内容的返回中，空描述符由其名称表示，不附带任何列表。”
In the ASN.1, add the following choice to the AuditReturnParameter production:
在ASN.1中，将以下选项添加到AuditReturnParameter production：
"emptyDescriptors AuditDescriptor,"
emptyDescriptors审核描述符
In the ABNF, add the choice auditItem to the production auditReturnParameter.
在ABNF中，将选项auditItem添加到production AuditReturn参数中。
Section: 7.1.1 "Specifying Parameters"
----------
Issue: Third paragraph (discussing unspecified parameters): not clear
which parameters are mandatory.
Section: 7.1.1 "Specifying Parameters"
----------
Issue: Third paragraph (discussing unspecified parameters): not clear
which parameters are mandatory.
Resolution: Replace the first two sentences (each beginning with the word "unspecified") with the following text: "If a required descriptor other than the Audit descriptor is unspecified (i.e. entirely absent) from a command, the previous values set in that descriptor for that termination, if any, are retained. A missing Audit descriptor is equivalent to an empty Audit descriptor. The behaviour of the MG with respect to unspecified parameters within a descriptor varies with the descriptor concerned, as indicated in succeeding sections."
解决方案：将前两句（每句以“未指定”一词开头）替换为以下文字：“如果审计描述符以外的所需描述符未指定（即完全缺失）从命令中，保留该描述符中为该终止设置的先前值（如果有）。缺失的审计描述符相当于空的审计描述符。MG对于描述符中未指定参数的行为因相关描述符而异，如后续章节所示。”
Section: 7.1.6 "Stream Descriptor", ABNF (Annex B.2)
----------
Issue: Text indicates use of "true" and "false" values while ABNF
uses "on" and "off"
Section: 7.1.6 "Stream Descriptor", ABNF (Annex B.2)
----------
Issue: Text indicates use of "true" and "false" values while ABNF
uses "on" and "off"
Resolution: Add comment in B.2 that "true" in text corresponds to "on" in ABNF, and "false" corresponds to "off".
解决方案：在B.2中添加注释，文本中的“真”对应于ABNF中的“开”，而“假”对应于“关”。
Section: 7.1.8 "Local and Remote Descriptors"
----------
Issue: case where reserveGroup or reserveValue is true, last bulleted
item beginning: "If the Mode property of the LocalControl descriptor
is RecvOnly or SendRecv,...", could also have DSP involvement in the
case of loopback mode.
Section: 7.1.8 "Local and Remote Descriptors"
----------
Issue: case where reserveGroup or reserveValue is true, last bulleted
item beginning: "If the Mode property of the LocalControl descriptor
is RecvOnly or SendRecv,...", could also have DSP involvement in the
case of loopback mode.
Resolution: Add "loopback".
解决方案：添加“环回”。
Section: 7.1.9 "Events Descriptor"
----------
Issue: EventDM is part of syntax but not mentioned in section.
Section: 7.1.9 "Events Descriptor"
----------
Issue: EventDM is part of syntax but not mentioned in section.
Resolution: Add text: "If a digit map completion event is present or implied in the EventsDescriptor, EventDM is used to carry either the name or the value of the associated digit map. See section 7.1.14."
解决方案：添加文本：“如果EventsDescriptor中存在或暗示数字映射完成事件，则使用EventDM携带相关数字映射的名称或值。请参阅第7.1.14节。”
Issue: Not clear whether events trigger side effects (e.g. signal termination) at time of detection, at time of processing (whether or not in active Events Descriptor) or at time of notification. Also, the third paragraph of the section fails to mention these side effects and limits MG action to notification.
问题：不清楚事件是否在检测时、处理时（无论是否在活动事件描述符中）或通知时触发副作用（例如信号终止）。此外，该节第三段未提及这些副作用，并将MG行动限制在通知范围内。
Resolution: Modify the third paragraph of the section, so that it reads: "When an event (either newly detected or buffered) is processed against the contents of an active Events descriptor and found to be present in that descriptor ("recognized"), the default action of the MG is to send a Notify command to the MG. Notification may be deferred if the event is absorbed into the current dial string of an active digit map (see section 7.1.14). Any other action is for further study. Moreover, event recognition may cause currently active signals to stop, or may cause the current Events and/or Signals descriptor to be replaced, as described at the end of this section."
解决方案：修改本节第三段，使其内容为：“当针对活动事件描述符的内容处理事件（新检测到的或缓冲的）并发现该描述符中存在（“已识别”）时”，MG的默认操作是向MG发送Notify命令。如果事件被吸收到活动数字映射的当前拨号字符串中，则通知可能会延迟（见第7.1.14节）。任何其他操作都有待进一步研究。此外，事件识别可能会导致当前活动信号停止，或导致当前事件和/或信号描述符被替换，如本节末尾所述。”
Replace "detection" with "recognition" in the fourth paragraph from the end, so that it reads: "Normally, recognition of an event shall cause any active signals to stop. When KeepActive is specified in the event, the MG shall not interrupt any signals active on the Termination on which the event is detected."
将第四段结尾处的“检测”替换为“识别”，以便其内容如下：“通常，事件识别应导致任何活动信号停止。当事件中规定了Keepacitive时，MG不得中断检测到事件的终端上的任何活动信号。”
In the third-last paragraph, replace all three instances of "detected" with "recognized".
在最后第三段中，将“检测到”的所有三个实例替换为“已识别”。
Leave the word "detected" as is in the final paragraph.
保留最后一段中的“检测到”一词。
Issue: Case 1, step 2(a) is incorrectly formulated. Existing logic may result in an infinite loop. Also, the step excludes side effect actions such as signal termination.
问题：案例1，步骤2（a）的表述不正确。现有逻辑可能导致无限循环。此外，该步骤还排除了诸如信号终止之类的副作用。
Resolution: Modify step 2(a) to read: "If the event in the queue is in the events listed in the new EventsDescriptor, the MG acts on the event and removes it from the EventBuffer. The time stamp of the Notify shall be the time the event was actually detected. The MG then waits for a new EventsDescriptor. While waiting for a new EventsDescriptor, any events detected which appear in the current EventsBufferDescriptor will be placed in the EventBuffer. When a new EventDescriptor is received, event processing repeats from step 1."
解决方案：将步骤2（a）修改为：“如果队列中的事件在新EventsDescriptor中列出的事件中，MG将对该事件执行操作并将其从EventBuffer中删除。”。通知的时间戳应为实际检测到事件的时间。MG然后等待新的EventsDescriptor。在等待新的EventsDescriptor时，在当前EventsBufferDescriptor中出现的任何检测到的事件都将放置在EventBuffer中。当接收到新的EventDescriptor时，事件处理将从步骤1开始重复。“
Section: 7.1.11 "Signals Descriptor"
----------
Issue: There is a need for the MGC to be aware of signalling
failures. It is not possible to use the signal completion event to
monitor for signalling failures only, without also having to process
successes.
Section: 7.1.11 "Signals Descriptor"
----------
Issue: There is a need for the MGC to be aware of signalling
failures. It is not possible to use the signal completion event to
monitor for signalling failures only, without also having to process
successes.
Proposed Resolution: In section 7.1.11, replace the current text on completion notification, beginning: "Finally, the optional parameter "notifyCompletion" ..." and continuing to the end of the paragraph with the following text:
提议的解决方案：在第7.1.11节中，将完成通知的当前文本替换为：“最后，可选参数“notifyCompletion”…，并继续使用以下文本至本段末尾：
"Finally, the optional parameter "notifyCompletion" allows a MGC to indicate the circumstances under which it wishes to be notified when the signal finishes playout. The possible cases are that the signal timed out, that it was interrupted by an event, that it was halted when a Signals descriptor was replaced, or that it stopped or never started for other reasons. If "notifyCompletion" is absent, notification is generated in the "other reasons" case only. For reporting to occur the signal completion event (see section E.1.2) must be enabled in the currently active Events descriptor."
最后，可选参数“notifyCompletion”“允许MGC指示信号播放结束时希望得到通知的情况。可能的情况是信号超时、被事件中断、在替换信号描述符时停止、或由于其他原因停止或从未启动。如果没有“notifyCompletion”，则仅在“其他原因”情况下生成通知。为了报告事件的发生，必须在当前活动事件描述符中启用信号完成事件（见第E.1.2节）。”
In Annex A.2, make notifyCompletion a BIT STRING with the four cases. In B.2, make it a parameter consisting of a name and a list of values representing the possible completion methods.
在附录A.2中，使用四种情况制作一个位字符串。在B.2中，将其作为一个参数，由一个名称和一个表示可能的完成方法的值列表组成。
Section: 7.1.13 "ServiceChange Descriptor"
----------
Issue: Missing "extension" component in the API.
Section: 7.1.13 "ServiceChange Descriptor"
----------
Issue: Missing "extension" component in the API.
Resolution: Add missing component.
解决方案：添加缺少的组件。
Section: 7.1.14 "DigitMap Descriptor"
----------
Editorial: add the following subsections.
Section: 7.1.14 "DigitMap Descriptor"
----------
Editorial: add the following subsections.
7.1.14.1 DigitMap definition, creation, modification and termination (before first paragraph)
7.1.14.1 数字地图的定义、创建、修改和终止（第一段之前）
7.1.14.2 DigitMap Timers (after the first bullet list)
7.1.14.2 DigitMap计时器（在第一个项目符号列表之后）
7.1.14.3 DigitMap syntax (before the long paragraph starting "The formal syntax of the digit map [...]")
7.1.14.3 DigitMap语法（在“digit map[…]的形式语法”开头的长段落之前）
7.1.14.4 DigitMap completion event (before the paragraph starting "A digit map is active while the events descriptor [...]")
7.1.14.4 DigitMap完成事件（在“当事件描述符[…]处于活动状态时，数字映射处于活动状态”开头的段落之前）
7.1.14.5 DigitMap procedures (before the sentence "Pending completion, successive events shall be processed [...]", preceding the numbered list)
7.1.14.5 DigitMap程序（在“待完成，应处理连续事件[…]”一句之前，在编号列表之前）
7.1.14.6 DigitMap activation (after the numbered list)
7.1.14.6 数字地图激活（编号列表后）
7.1.14.7 Interaction of DigitMap and event processing (before the next paragraph, starting "While the digit map is activated, [...]")
7.1.14.7 数字地图和事件处理的交互（在下一段之前，从“激活数字地图时，[…]”开始）
7.1.14.8 Wildcards (before the the next paragraph, starting "Note that if a package contains [...]")
7.1.14.8 通配符（在下一段之前，以“注意如果包包含[…]”开头）
7.1.14.9 Example (before the example)
7.1.14.9 示例（在示例之前）
Issue: incorrect statements regarding the interaction of the dot symbol with default timing rules.
问题：有关点符号与默认计时规则交互的错误陈述。
Resolution: last sentence of the paragraph beginning "The letter "x" is used as a wildcard, ..." should be modified to read: "As a consequence of the third timing rule above, inter-event timing while matching a terminal dot symbol uses the short timer by default." In the next paragraph, the third sentence, which begins: "A timer specifier following a dot ...", should be deleted.
解决方案：以“字母“x”作为通配符，…”开头的段落的最后一句应修改为：“根据上述第三个计时规则，在匹配终端点符号时，事件间计时默认使用短计时器。”在下一段中，第三句开始：应删除“点后面的计时器说明符…”。
Issue: Step 5 in second numbered list understates conditions for digit map completion when single candidate remains.
问题：第二个编号列表中的第5步低估了单个候选人留下时数字地图完成的条件。
Resolution: Add the words "and it has been fully matched" to the existing sentence. Also remove the parenthetical remark: "... (because the candidate set still contains more than one alternative event sequence)" from step 6.
解决方案：在现有句子中添加“且已完全匹配”字样。同时删除步骤6中的附加注释：“…（因为候选集仍然包含多个备选事件序列）”。
Issue: Not clear when unmatched events are recognized and trigger side effects (e.g. signal termination).
问题：不清楚何时识别不匹配事件并触发副作用（例如信号终止）。
Resolution: Modify the final sentence of the paragraph following procedural step 6 to read as follows: "Normal event behaviour (e.g. stopping of signals unless the digit completion event has the KeepActive flag enabled) continues to apply for each such event detected, except that
解决方案：将程序步骤6之后段落的最后一句修改为：“正常事件行为（例如，除非数字完成事件启用了KeepActive标志，否则停止信号）继续适用于检测到的每个此类事件，但以下情况除外：
. the events in the package containing the specified digit map completion event other than the completion event itself are not individually notified, and . an event which triggers a "partial match" completion is not recognized and therefore has no side effects until reprocessed following the recognition of the digit map completion event."
. 不单独通知包中包含指定数字映射完成事件（完成事件本身除外）的事件，以及。触发“部分匹配”完成的事件不被识别，因此在识别数字映射完成事件后重新处理之前没有副作用。”
Issue: the last paragraph before the example is misleading if the package containing the digit map completion event is different from the package containing the actual digits.
问题：如果包含数字映射完成事件的包与包含实际数字的包不同，则示例前的最后一段会产生误导。
Resolution: qualify the second sentence of the paragraph as follows: "Regardless of whether a digit map is activated, if the package also contains the digit events themselves, this form of event specification ...".
解决方案：将段落的第二句限定如下：“无论是否激活数字映射，如果包中也包含数字事件本身，则此形式的事件规范……”。
Section: 7.1.18 "Topology Descriptor"
----------
Issue: Third bullet attached to third para: says loopback achieved by
manipulating TerminationMode, which no longer has that name.
Section: 7.1.18 "Topology Descriptor"
----------
Issue: Third bullet attached to third para: says loopback achieved by
manipulating TerminationMode, which no longer has that name.
Resolution: Delete the clause "; loopbacks are created by setting the TerminationMode"
解决方案：删除“通过设置TerminationMode创建环回”子句
Section: 7.2
----------
Issue: The order in which descriptors are processed within a command
matters, but is not clear. Moreover, it is fixed in the ASN.1 but
variable in the ABNF.
Section: 7.2
----------
Issue: The order in which descriptors are processed within a command
matters, but is not clear. Moreover, it is fixed in the ASN.1 but
variable in the ABNF.
Resolution: Add text stating that descriptors are processed in the order in which they are provided. Change ASN.1 in Annex A.2 to allow the MGC to specify ordering:
解决方案：添加文本，说明按照提供描述符的顺序处理描述符。更改附录A.2中的ASN.1，以允许MGC规定订购：
AmmRequest ::= SEQUENCE
{
terminationID TerminationIDList,
descriptors SEQUENCE OF AmmDescriptor,
-- At most one descriptor of each type (see AmmDescriptor)
-- allowed in the sequence
...
}
AmmRequest ::= SEQUENCE
{
terminationID TerminationIDList,
descriptors SEQUENCE OF AmmDescriptor,
-- At most one descriptor of each type (see AmmDescriptor)
-- allowed in the sequence
...
}
AmmDescriptor ::= CHOICE
{
mediaDescriptor MediaDescriptor,
modemDescriptor ModemDescriptor,
muxDescriptor MuxDescriptor,
eventsDescriptor EventsDescriptor,
eventBufferDescriptor EventBufferDescriptor,
signalsDescriptor SignalsDescriptor,
digitMapDescriptor DigitMapDescriptor,
auditDescriptor AuditDescriptor,
...
}
AmmDescriptor ::= CHOICE
{
mediaDescriptor MediaDescriptor,
modemDescriptor ModemDescriptor,
muxDescriptor MuxDescriptor,
eventsDescriptor EventsDescriptor,
eventBufferDescriptor EventBufferDescriptor,
signalsDescriptor SignalsDescriptor,
digitMapDescriptor DigitMapDescriptor,
auditDescriptor AuditDescriptor,
...
}
Section: 7.2.3 "Subtract"
----------
Issue: cannot use the CHOOSE wildcard for terminationId of a Subtract
command.
Section: 7.2.3 "Subtract"
----------
Issue: cannot use the CHOOSE wildcard for terminationId of a Subtract
command.
Resolution: add this qualification to the second sentence, which indicates that terminationId may be wildcarded.
解决方案：将此限定添加到第二句，这表明terminationId可能是通配符。
Section: 7.2.4 "Move"
----------
Issue: cannot use the CHOOSE wildcard for terminationId of a Move
command.
Section: 7.2.4 "Move"
----------
Issue: cannot use the CHOOSE wildcard for terminationId of a Move
command.
Resolution: add this qualification to the second sentence, which indicates that terminationId may be wildcarded.
解决方案：将此限定添加到第二句，这表明terminationId可能是通配符。
Section: 7.2.5 "AuditValue"
----------
Issue: Not clear whether AuditValue of ObservedEventsDescriptor
reports events captured in current dial string of active digit map.
Section: 7.2.5 "AuditValue"
----------
Issue: Not clear whether AuditValue of ObservedEventsDescriptor
reports events captured in current dial string of active digit map.
Resolution: Add text to indicate that if a digit map is active and ObservedEventsDescriptor is specified the response to an AuditValue includes a digit map completion event which shows the current dial string but does not show a termination method.
解决方案：添加文本以指示如果数字映射处于活动状态并且指定了ObservedEventsDescriptor，则对AuditValue的响应包括数字映射完成事件，该事件显示当前拨号字符串，但不显示终止方法。
Issue: Fails to indicate what AuditValue for EventBufferDescriptor returns
问题：无法指示EventBufferDescriptor返回的AuditValue
Resolution: Add the following text: "EventBuffer returns the set of events and associated parameter values currently enabled in the EventBufferDescriptor."
解决方案：添加以下文本：“EventBuffer返回EventBufferDescriptor中当前启用的事件集和相关参数值。”
Issue: not clear whether wildcarded context includes the null context.
问题：不清楚通配符上下文是否包含空上下文。
Resolution: add statement that ALL as a contextID does not include the null context.
解决方案：添加语句，使ALL作为contextID不包含空上下文。
Issue: the text of 7.2.5 allows retrieval of multiple digit maps with one AuditValue command if the terminationId is ALL. Moreover, earlier text in the Annex anticipates that multiple instances of a descriptor may be returned. The comment in front of production auditReturnParameter in Annex B.2 contradicts this text. Note that Annex A has no restriction on the number of instances of any descriptor in either a command or a response.
问题：如果terminationId为ALL，7.2.5的文本允许使用一个AuditValue命令检索多个数字映射。此外，附件中较早的文本预期可能返回描述符的多个实例。附录B.2中生产参数前面的注释与本文相矛盾。注意，附录A对命令或响应中任何描述符的实例数没有限制。
Proposed Resolution: delete the"at-most-once" comment preceding ABNF production auditReturnParameter.
建议的解决方案：删除ABNF production AuditReturn参数前面的“最多一次”注释。
Issue: Does not indicate how an audit of digit maps returns unnamed digit maps.
问题：不指示数字地图审核如何返回未命名的数字地图。
Resolution: Change syntax of DigitMapDescriptor to allow return of unnamed digit maps as follows:
解决方案：更改DigitMapDescriptor的语法以允许返回未命名的数字映射，如下所示：
digitMapDescriptor = DigitMapToken EQUAL ( (LBRKT digitMapValue RBRKT) / (digitMapname [ LBRKT digitMapValue RBRKT ]) ) and
digitMapDescriptor=DigitMapToken等于（（LBRKT digitMapValue RBRKT）/（digitMapname[LBRKT digitMapValue RBRKT]），并且
DigitMapDescriptor ::= SEQUENCE {
digitMapName DigitMapName OPTIONAL,
digitMapValue DigitMapValue OPTIONAL }
DigitMapDescriptor ::= SEQUENCE {
digitMapName DigitMapName OPTIONAL,
digitMapValue DigitMapValue OPTIONAL }
Issue: the text in section 7.2.5 mentions that using an empty Audit descriptor with a wildcarded terminationId is a way to get a list of the terminations in the context. Annex A provides the possibility that the auditReply may be a contextAuditResult of type terminationIdList, and Annex B allows for an auditReply containing a contextTerminationAudit which in turn presents a terminationIdList. The connection between the text in 7.2.5 and these special forms of audit result is not clear. Moreover, a note at the beginning of Annex A section A.2 limits terminationIdList to one terminationId.
问题：第7.2.5节中的文本提到，使用带有通配符terminationId的空审核描述符是在上下文中获取终止列表的一种方法。附录A提供了auditReply可能是terminationIdList类型的contextAuditResult的可能性，附录B允许包含contextTerminationAudit的auditReply，该contextTerminationAudit反过来表示terminationIdList。7.2.5中的文本与这些特殊形式的审计结果之间的联系不明确。此外，附录a第a.2节开头的注释将terminationIdList限制为一个terminationId。
Proposed Resolution: add the following text in section 7.2.5 after the sentence "This may be useful to get a list of TerminationIDs when used with wildcard.": "Annexes A and B provide a special syntax for presenting such a list in condensed form, such that the AuditValue command tag does not have to be repeated for each terminationId." Also, in the Note at the beginning of section A.2 of Annex A, provide an exception on the length of type TerminationIdList when used in contextAuditResult.
建议的解决方案：在第7.2.5节中的“当与通配符一起使用时，这可能有助于获取终止ID列表”一句之后添加以下文本：“附录a和B提供了一种特殊语法，用于以压缩形式呈现此类列表，以便不必为每个终止ID重复AuditValue命令标记。”，在附录A第A.2节开头的注释中，提供在contextAuditResult中使用时类型TerminationIdList长度的例外情况。
Section: 7.2.6 "AuditCapabilities"
----------
Issue: Fails to indicate what AuditCapabilities for
EventBufferDescriptor returns
Section: 7.2.6 "AuditCapabilities"
----------
Issue: Fails to indicate what AuditCapabilities for
EventBufferDescriptor returns
Resolution: Add the following text: "EventBuffer returns the same information as Events."
解决方案：添加以下文本：“EventBuffer返回与事件相同的信息。”
Issue: Inconsistency regarding permissibility of DigitMap or Packages as capability audit items.
问题：DigitMap或包作为能力审核项目的许可不一致。
Resolution: Add comment to B.2 "auditItem" production indicating that DigitMap and Packages are not allowed in the AuditCapabilities command.
解决方案：在B.2“auditItem”产品中添加注释，指出AuditCapabilities命令中不允许使用DigitMap和包。
Section: 7.2.8 "ServiceChange"
----------
Issue: In point 1) describing the Graceful ServiceChange method, the
scope of the recommendation against new connections is unclear.
Section: 7.2.8 "ServiceChange"
----------
Issue: In point 1) describing the Graceful ServiceChange method, the
scope of the recommendation against new connections is unclear.
Resolution: at the end of the first sentence, add the phrase "on the termination(s) affected by the ServiceChange command".
解决方案：在第一句末尾添加短语“受ServiceChange命令影响的终止”。
Issue: the explanatory string associated with ServiceChangeReason is optional in the syntax, but not in the text.
问题：与ServiceChangeReason关联的解释性字符串在语法中是可选的，但在文本中不是。
Resolution: add "optional" before "explanatory string" in the explanation of the ServiceChangeReason" parameter.
解决方案：在ServiceChangeReason“参数的说明中，在“解释性字符串”之前添加“可选”。
Issue: Paragraph beginning "A ServiceChange Command specifying the Root..." immediately following the description of ServiceChange Descriptor parameters erroneously states that the response to the ServiceChange command terminates the registration process. This is so only if the response does not specify an alternate MGC.
问题：紧接着ServiceChange描述符参数描述之后的“指定根目录的ServiceChange命令…”开头的段落错误地表示对ServiceChange命令的响应终止了注册过程。仅当响应未指定备用MGC时，才会出现这种情况。
Resolution: Add text to the offending sentence, so that it reads: "Acknowledgement of the ServiceChange Command completes the registration process, except when the MGC has returned an alternative ServiceChangeMgcId as described in the next paragraph."
解决方案：将文本添加到有问题的句子中，这样它就会显示：“ServiceChange命令的确认完成注册过程，除非MGC已返回下一段中所述的备选ServiceChangeMgcId。”
Section: 7.3 "Command Error Codes"
----------
Issue: Text for error code 403 should be consistent with that for 404
and 405.
Section: 7.3 "Command Error Codes"
----------
Issue: Text for error code 403 should be consistent with that for 404
and 405.
Resolution: Change text to "Syntax error in TransactionRequest"
解决方案：将文本更改为“TransactionRequest中的语法错误”
Issue: There should be no error responses to TransactionReply or TransactionPending, lest they create response loops.
问题：TransactionReply或TransactionPending不应该有错误响应，以免它们创建响应循环。
Resolution: Delete codes 404, 405, 461-467
解决方案：删除代码404405461-467
Section: 8 "Transactions", A.2
----------
Issue: state is unclear if a command fails.
Section: 8 "Transactions", A.2
----------
Issue: state is unclear if a command fails.
Resolution: add the following text: "If a command fails, the MG shall as far as possible restore the state which prevailed prior to the attempted execution of the command before continuing with transaction processing."
解决方案：添加以下文字：“如果命令失败，MG应尽可能恢复尝试执行命令之前的状态，然后再继续事务处理。”
Section: 8.1.1 "Transaction Identifiers"
----------
Issue: need a transaction identifier to use when reporting a syntax
error such that the identifier is unavailable.
Section: 8.1.1 "Transaction Identifiers"
----------
Issue: need a transaction identifier to use when reporting a syntax
error such that the identifier is unavailable.
Resolution: add text reserving transionId = 0 for this purpose.
解决方案：为此目的，添加保留transionId=0的文本。
Section: 8.1.2 "Context Identifiers"
----------
Issue: ALL as a context identifier does not include the null context.
Section: 8.1.2 "Context Identifiers"
----------
Issue: ALL as a context identifier does not include the null context.
Resolution: add text to indicate that exclusion in the final sentence of the section.
解决方案：在本节最后一句中添加文本以表明排除。
Section: 8.2.2 "TransactionReply"
----------
Issue: Final para has wrong text for error code 442.
Section: 8.2.2 "TransactionReply"
----------
Issue: Final para has wrong text for error code 442.
Resolution: Change to "Syntax Error in Command"
解决方案：更改为“命令中的语法错误”
Section: 10.2 "Interim AH Scheme", B.2
----------
Issue: The interim AH header can actually be as short as 24 hex
digits (per RFCs 2403, 2404 which are indirectly referenced). It is
also unclear whether it is the source or destination UDP port which
is prepended in the calculation.
Section: 10.2 "Interim AH Scheme", B.2
----------
Issue: The interim AH header can actually be as short as 24 hex
digits (per RFCs 2403, 2404 which are indirectly referenced). It is
also unclear whether it is the source or destination UDP port which
is prepended in the calculation.
Resolution: Change 10.2 second para, second-last sentence to specify the destination port, in consistency with IPSEC. In Annex B.2, change lower count for production AuthData to 24 from 32.
解决方案：将10.2第二段最后一句更改为指定目标端口，与IPSEC保持一致。在附录B.2中，将生产验证数据的下限计数从32更改为24。
Section: 11.2 "Cold Start"
----------
Issue: First paragraph last sentence inadvertently modified --
duplicates material in 11.3.
Section: 11.2 "Cold Start"
----------
Issue: First paragraph last sentence inadvertently modified --
duplicates material in 11.3.
Resolution: Restore original sentence: "If the MG is unable to establish a control relationship with any MGC, it shall wait a random amount of time as described in Section 9.2 and then start contacting its primary, and if necessary, its secondary MGCs again."
解决方案：恢复原来的句子：“如果MG无法与任何MGC建立控制关系，则应按照第9.2节所述随机等待一段时间，然后开始再次联系其主要MGC，如有必要，联系其次要MGC。”
Section: 11.4 "Failure Of an MG"
----------
Issue: Second para: wrong MG is specified as the one to be used after
failover.
Section: 11.4 "Failure Of an MG"
----------
Issue: Second para: wrong MG is specified as the one to be used after
failover.
Resolution: Change fourth sentence to refer to "secondary MG" rather than "primary MG".
决议：将第四句改为“次要MG”，而不是“主要MG”。
Section: 12.1.2 "Properties"
----------
Issue: As indicated in 6.2.4, Properties occur in other descriptors
besides LocalControl and TerminationState.
Section: 12.1.2 "Properties"
----------
Issue: As indicated in 6.2.4, Properties occur in other descriptors
besides LocalControl and TerminationState.
Resolution: after the sentence mentioning TerminationState, add another sentence: "Although these are the most common cases, it is also possible for a property to be defined for other descriptors."
解决方案：在提到TerminationState的句子后，添加另一句话：“虽然这是最常见的情况，但也可以为其他描述符定义属性。”
Section: 12.1.4 "Signals"
----------
Issue: Note says that default duration should be specified for BR
signals. This also applies to TO signals.
Section: 12.1.4 "Signals"
----------
Issue: Note says that default duration should be specified for BR
signals. This also applies to TO signals.
Resolution: Add TO signals to note.
分辨率：添加到要注释的信号。
Section: 12.2 "Guidelines to defining Properties, Statistics and
Parameters to Events and Signals", B.2
----------
Issue: Text indicates that statistics can have the sub-list data
type, but ABNF does not support that.
Section: 12.2 "Guidelines to defining Properties, Statistics and
Parameters to Events and Signals", B.2
----------
Issue: Text indicates that statistics can have the sub-list data
type, but ABNF does not support that.
Resolution: qualify the sublist type by adding the note: "(not supported for statistics)".
解决方案：通过添加注释来限定子列表类型：“（统计信息不支持）”。
Section: Annex A.1, ASN.1 Syntax
----------
Issue: the ASN.1 uses the values 0x0, 0xFFFFFFFE, and 0xFFFFFFFF for
the NULL context, a wildcard CHOOSE of context, and a wildcard ALL of
context respectively. Because of the possibility of a switch between
binary and text encoding for messages relating to the same context,
these values should be reserved in the text encoded syntax.
Section: Annex A.1, ASN.1 Syntax
----------
Issue: the ASN.1 uses the values 0x0, 0xFFFFFFFE, and 0xFFFFFFFF for
the NULL context, a wildcard CHOOSE of context, and a wildcard ALL of
context respectively. Because of the possibility of a switch between
binary and text encoding for messages relating to the same context,
these values should be reserved in the text encoded syntax.
Resolution: Add a comment preceding the ContextID production in Annex B.2 indicating that these values are reserved.
解决方案：在附录B.2中的ContextID生成之前添加注释，表明保留这些值。
Section: Annex A.2, ASN.1 Syntax
----------
Issue: sloppy ASN.1 -- in production EventBufferControl the values
"off" and "lockstep" should not be capitalized, and IA5STRING in
production NonStandardIdentifier should be IA5String. Both
TransactionID and TransactionId are used. A number of productions
need ellipses to express extensibility.
Section: Annex A.2, ASN.1 Syntax
----------
Issue: sloppy ASN.1 -- in production EventBufferControl the values
"off" and "lockstep" should not be capitalized, and IA5STRING in
production NonStandardIdentifier should be IA5String. Both
TransactionID and TransactionId are used. A number of productions
need ellipses to express extensibility.
Resolution: fix them.
解决方法：修复它们。
Issue: syntax for PropertyParm does not support sub-lists (i.e. parameters supporting multiple values simultaneously)
问题：PropertyPart的语法不支持子列表（即同时支持多个值的参数）
Resolution: add a third choice to extrainfo in PropertyParm as follows:
解决方案：在PropertyPart中的extrainfo中添加第三个选项，如下所示：
extraInfo CHOICE { relation Relation, range BOOLEAN, sublist BOOLEAN } OPTIONAL
extraInfo选项{关系，范围布尔，子列表布尔}可选
and add an appropriate note to the preceding comments.
并在前面的评论中添加适当的注释。
Issue: LocalControlDescriptor still contains reserve rather than reserveValue and reserveGroup.
问题：LocalControlDescriptor仍然包含reserve而不是reserveValue和reserveGroup。
Resolution: Replace reserve with separate reserveValue and reserveGroup Booleans.
解决方案：用单独的reserveValue和reserveGroup布尔值替换reserve。
Issue: EventBufferDescriptor is incorrectly portrayed as a SEQUENCE OF ObservedEvent.
问题：EventBufferDescriptor被错误地描述为ObservedEvent序列。
Resolution: replace with the following productions:
解决方案：替换为以下产品：
EventBufferDescriptor ::= SEQUENCE OF EventSpec
EventBufferDescriptor ::= SEQUENCE OF EventSpec
EventSpec ::= SEQUENCE {
pkgdName PkgdName,
streamID StreamID OPTIONAL,
evParList SEQUENCE OF EventParameter }
EventSpec ::= SEQUENCE {
pkgdName PkgdName,
streamID StreamID OPTIONAL,
evParList SEQUENCE OF EventParameter }
Issue: Assigned object identifier missing. It is usually present as a matter of convention.
问题：缺少分配的对象标识符。它通常作为惯例出现。
Resolution: Add object identifier line in the message header with content: "itu-t recommendation h 248 media-gateway-control(0)" Delete the version field, which this makes redundant.
解决方案：在消息头中添加对象标识符行，内容为：“itu-t建议h 248媒体网关控制（0）”删除版本字段，这将使其变得冗余。
Issue: the T.35 country code in the H221NonStandard production does not have the right structure.
问题：H221非标准产品中的T.35国家代码没有正确的结构。
Resolution: fix it.
解决方案：修复它。
Section: Annex B.2, ABNF Syntax
----------
Issue: Syntax for parmValue and VALUE together make parsing of range
ambiguous. Furthermore, sub-lists and sets of alternative values
have the same syntax, introducing possible ambiguity
Section: Annex B.2, ABNF Syntax
----------
Issue: Syntax for parmValue and VALUE together make parsing of range
ambiguous. Furthermore, sub-lists and sets of alternative values
have the same syntax, introducing possible ambiguity
Resolution: Replace production alternativeValue by the following:
"alternativeValue = ( VALUE
/ LSBRKT VALUE *(COMMA VALUE) RSBRKT ; sub-list
/ LBRKT VALUE *(COMMA VALUE) RBRKT ; alternatives
/ LSBRKT VALUE COLON VALUE RSBRKT ) ; range"
Resolution: Replace production alternativeValue by the following:
"alternativeValue = ( VALUE
/ LSBRKT VALUE *(COMMA VALUE) RSBRKT ; sub-list
/ LBRKT VALUE *(COMMA VALUE) RBRKT ; alternatives
/ LSBRKT VALUE COLON VALUE RSBRKT ) ; range"
Issue: EventBufferDescriptor content mistakenly shown as a sequence of observedEvent.
问题：EventBufferDescriptor内容错误地显示为observedEvent序列。
Resolution: replace the production for eventBufferDescriptor with the following productions:
解决方案：将eventBufferDescriptor的产品替换为以下产品：
eventBufferDescriptor = EventBufferToken LBRKT [ eventSpec *( COMMA eventSpec ) ] RBRKT
eventBufferDescriptor=EventBufferToken LBRKT[eventSpec*（逗号eventSpec）]RBRKT
eventSpec = pkgdName [ LBRKT eventSpecParameter *( COMMA eventSpecParameter ) RBRKT ]
eventSpec=pkgdName[LBRKT eventSpecParameter*（逗号eventSpecParameter）RBRKT]
eventSpecParameter = ( eventStream / eventOther )
eventSpecParameter = ( eventStream / eventOther )
Issue: Error in syntax for digitMapDescriptor: value meant to be optional.
问题：digitMapDescriptor的语法错误：值是可选的。
Resolution: Change production: digitMapDescriptor = DigitMapToken EQUAL digitMapName [ LBRKT digitMapValue RBRKT ]
解决方案：更改产品：digitMapDescriptor=DigitMapToken等于digitMapName[LBRKT digitMapValue RBRKT]
Issue: VersionToken not defined.
问题：未定义VersionToken。
Resolution: Add ABNF: VersionToken = ("Version" / "V")
Resolution: Add ABNF: VersionToken = ("Version" / "V")
Issue: DiscardToken not used.
问题：未使用丢弃令牌。
Resolution: Delete production.
解决方案：删除生产。
Section: Annex C
----------
Issue: alignment of sub-octet fields within the octet is not
indicated.
Section: Annex C
----------
Issue: alignment of sub-octet fields within the octet is not
indicated.
Resolution: add note that fields of sub-octet length are placed in the low-order bits of the octet.
分辨率：请注意，子八位字节长度的字段位于八位字节的低位。
Section: Annex C, ATM-related sections C.4, C.7, C.8, C.10
----------
Issue: direction of flow is segregated by outgoing (Remote
descriptor) and incoming (Local descriptor). Since forward and
backward properties will not both reside in the same descriptor, need
only the one set of properties applicable to both directions.
Section: Annex C, ATM-related sections C.4, C.7, C.8, C.10
----------
Issue: direction of flow is segregated by outgoing (Remote
descriptor) and incoming (Local descriptor). Since forward and
backward properties will not both reside in the same descriptor, need
only the one set of properties applicable to both directions.
Resolution: replace with a single set of properties.
解决方案：替换为单个属性集。
Issue: miscellaneous problems of parameter specifications inconsistent with the relevant standards, unused parameters, distinction between ATM Forum and ITU-T usages, missing references.
问题：参数规格与相关标准不一致的杂项问题，未使用的参数，ATM论坛和ITU-T使用之间的区别，缺少参考资料。
Resolution: fix them.
解决方法：修复它们。
Section: Annex C.8 "ATM AAL1"
----------
Issue: Length of GIT is wrong.
Section: Annex C.8 "ATM AAL1"
----------
Issue: Length of GIT is wrong.
Resolution: ITU-T procedural problem, to be resolved by SG 16. Probable solution is to allow 29 octets, event though the relevant form requires only four octets.
解决方案：ITU-T程序问题，由SG 16解决。可能的解决方案是允许29个八位字节，尽管相关形式只需要四个八位字节。
Section: Annex C.9 "Bearer Capabilities"
----------
Issue: ITC has reference to missing note 2
Section: Annex C.9 "Bearer Capabilities"
----------
Issue: ITC has reference to missing note 2
Resolution: Delete reference.
解决方案：删除引用。
Issue: Not clear that Q.931 Bearer Capability IE rather than Low Layer Compatibility IE is being used.
问题：不清楚使用的是Q.931承载能力IE，而不是低层兼容性IE。
Resolution: Specify that values are those valid for Bearer Capability IE
解决方案：指定值为对承载能力有效的值
Section: Annex D.1 "Transport over IP/UDP using Application Level
Framing"
----------
Issue: Even in the case of handoff or failover, the originating MGC
needs confirmation that its command was received.
Section: Annex D.1 "Transport over IP/UDP using Application Level
Framing"
----------
Issue: Even in the case of handoff or failover, the originating MGC
needs confirmation that its command was received.
Resolution: In the last sentence of the first paragraph, delete the excepting clause, so that the sentence reads: "Responses must be sent to the address and port from which the corresponding commands were sent."
解决方案：在第一段的最后一句中，删除例外条款，这样的句子是：“响应必须发送到发送相应命令的地址和端口。”
Section: Annex D.1.1 "Providing At-Most-Once Functionality"
----------
Issue: Second para last sentence provides a procedural reference to
8.2.3. Should refer to UDP-specific procedures.
Section: Annex D.1.1 "Providing At-Most-Once Functionality"
----------
Issue: Second para last sentence provides a procedural reference to
8.2.3. Should refer to UDP-specific procedures.
Resolution: Add reference to D.1.4.
决议：增加对D.1.4的参考。
Section: Annex D.1.3 "Repeating Requests, Responses and
Acknowledgements"
----------
Issue: Make exponential backoff in the face of congestion mandatory.
Section: Annex D.1.3 "Repeating Requests, Responses and
Acknowledgements"
----------
Issue: Make exponential backoff in the face of congestion mandatory.
Resolution: To the paragraph just before the note, which begins "The specification purposely avoids specifying any value for the retransmission timers...", add the following sentence:
解决方案：在注释前面的段落中，该段落以“规范有意避免指定重传计时器的任何值…”开头，添加以下句子：
"Implementations SHALL ensure that the algorithm used to calculate retransmission timing performs an exponentially increasing backoff of the retransmission timeout for each retransmission or repetition after the first one."
“实施应确保用于计算重传定时的算法对第一次重传或重复后的每次重传超时进行指数级递增退避。”
In the paragraph in the middle of the note beginning "After any retransmission ...", capitalize the word SHOULD to emphasize the importance of the steps which follow.
在“开始任何重发”的音符的中间段落中，大写单词应该强调后续步骤的重要性。
Issue: Last paragraph is equivocal about what ServiceChangeReason to use when recovering from loss of contact; it must always be "Disconnected".
问题：最后一段对于从失去联系中恢复时使用什么ServiceChangeReason含糊不清；它必须始终处于“断开”状态。
Resolution: Change the two sentences following the phrase "_ and it begins its recovery process" to read as follows: "The MG shall use a ServiceChange with ServiceChangeMethod set to disconnected so that the new MGC will be aware that the MG lost one or more transactions."
解决方案：将短语“并开始其恢复过程”后的两句话改为：“MG应使用ServiceChangeMethod设置为disconnected的ServiceChange，以便新MGC意识到MG丢失了一个或多个交易。”
Section: Annex D.1.4 "Provisional responses"
----------
Issue: First paragraph, last sentence talks about when to send the
Transaction Pending response. When UDP/ALF is in use, the originator
of a transaction may repeat it because it has not received an
acknowledgement that the transaction was received. An appropriate
response to a duplicate transaction which is still being processed is
to return Transaction Pending.
Section: Annex D.1.4 "Provisional responses"
----------
Issue: First paragraph, last sentence talks about when to send the
Transaction Pending response. When UDP/ALF is in use, the originator
of a transaction may repeat it because it has not received an
acknowledgement that the transaction was received. An appropriate
response to a duplicate transaction which is still being processed is
to return Transaction Pending.
Resolution: Add the sentence: "They SHOULD send this response if they receive a repetition of a transaction that is still being executed."
解决方案：添加一句话：“如果他们收到仍在执行的事务的重复，他们应该发送此响应。”
Issue: Second para: transaction originator may not have received TransactionPending response(s) because they were lost, and may therefore not know that responder is expecting immediate acknowledgement of the TransactionReply.
问题：第二段：交易发起人可能没有收到TransactionPending响应，因为它们丢失了，因此可能不知道响应者希望立即收到TransactionReply。
Resolution: add an optional field to TransactionReply allowing the responder to indicate if an immediate ACK is required. Add text in the section indicating that when the responder has sent a provisional response, it shall also set the indicator in the final transaction reply to indicate that an immediate acknowledgement is required.
解决方案：向TransactionReply添加可选字段，允许响应者指示是否需要立即确认。在部分中添加文本，表明当响应者发送临时响应时，还应在最终交易回复中设置指示器，以表明需要立即确认。
Section: Annex E "Basic Packages"
----------
Issue: package numbering does not follow order of presentation.
Section: Annex E "Basic Packages"
----------
Issue: package numbering does not follow order of presentation.
Resolution: renumber packages to follow order of numbering.
解决方案：按照编号顺序重新编号包裹。
Section: Annex E.2.1 "Base Root Package -- Properties"
----------
Issue: the descriptor in which these properties occur is not
specified.
Section: Annex E.2.1 "Base Root Package -- Properties"
----------
Issue: the descriptor in which these properties occur is not
specified.
Resolution: in each case, indicate that the property is defined in the TerminationState descriptor.
解析：在每种情况下，指示属性在TerminationState描述符中定义。
Section: Annex E.6.2 "DTMF detection Package -- Events"
----------
Issue: "Long duration event modifier" is shown as "L" in parameter
DigitString -- should be "Z".
Section: Annex E.6.2 "DTMF detection Package -- Events"
----------
Issue: "Long duration event modifier" is shown as "L" in parameter
DigitString -- should be "Z".
Resolution: Replace with "Z".
分辨率：替换为“Z”。
Section: Annex E.9.2 "Analog Line Supervision Package -- Events"
----------
Issue: Stated hook state reporting behaviour has race condition where
same transition could be reported twice.
Section: Annex E.9.2 "Analog Line Supervision Package -- Events"
----------
Issue: Stated hook state reporting behaviour has race condition where
same transition could be reported twice.
Resolution: add an optional EventsDescriptor parameter and an optional ObservedEvents parameter to each of the on-hook and off-hook events. Delete the second sentence of the existing event description (which indicates that the event is always reported if the hook state has already been achieved).
解决方案：将可选的EventsDescriptor参数和可选的ObservedEvents参数添加到每个挂接和挂接事件中。删除现有事件描述的第二句话（这表示如果已达到挂钩状态，则始终报告事件）。
The EventsDescriptor parameter is described as follows:
EventsDescriptor参数描述如下：
Strict Transition ParameterID: strict (0x0001) Type: enumeration Possible values: "exact" means that only an actual hook state transition to on-hook (off-hook) is to be recognized
Strict Transition ParameterID:Strict（0x0001）Type:枚举可能的值：“exact”表示只识别到实际的钩子状态转换为on hook（off hook）
"state" means that the event is to be recognized either if the hook state transition is detected or if the hook state is already on-hook (off-hook). This is the default value if "strict" is unspecified.
“状态”意味着，如果检测到钩子状态转换，或者钩子状态已经处于钩子上（脱离钩子），则将识别事件。如果未指定“strict”，则这是默认值。
"failWrong" means that if the hook state is already what the transition would imply, the command fails and an error is reported [error code to be defined in the package].
“FailError”意味着，如果钩子状态已经是转换所暗示的状态，则命令失败并报告错误[错误代码将在包中定义]。
The ObservedEvents parameter is described as follows:
ObservedEvents参数描述如下：
Initial State ParameterID: init (0x0002) Type: Boolean Possible values: true/"ON" means that the event was reported because the line was already on-hook (off-hook) when the events descriptor containing this event was activated
初始状态参数id:init（0x0002）Type:Boolean可能值：true/“ON”表示报告该事件，因为在激活包含该事件的事件描述符时，该行已挂起（脱离挂起）
false/"OFF" means that the event represents an actual state transition to on-hook (off-hook)
false/“OFF”表示事件表示实际状态转换为on-hook（OFF-hook）
Section: Annex E.10.3 "Basic Continuity Package -- Signals"
----------
Issue: The rsp signal should continue until the MGC tells the MG to
stop applying it.
Section: Annex E.10.3 "Basic Continuity Package -- Signals"
----------
Issue: The rsp signal should continue until the MGC tells the MG to
stop applying it.
Resolution: change the type of signal from Timeout to ON/OFF.
解决方案：将信号类型从超时更改为开/关。
Section: Annex E.10.5 "Basic Continuity Package -- Procedures"
----------
Issue: Wording of condition for generating cmp event with "success"
does not cover case where test also requires successful removal of
tone.
Section: Annex E.10.5 "Basic Continuity Package -- Procedures"
----------
Issue: Wording of condition for generating cmp event with "success"
does not cover case where test also requires successful removal of
tone.
Resolution: In the second paragraph of E.10.5 (dealing with test initiation), add the words "and any other required conditions are satisfied" in the second sentence, as part of the condition upon which success is reported. Replace the third paragraph (dealing with test response) with the following text:
解决方案：在E.10.5第二段（涉及试验启动）中，在第二句中添加“以及满足任何其他要求的条件”，作为报告成功的条件的一部分。将第三段（涉及测试响应）替换为以下文本：
"When a MGC wants the MG to respond to a continuity test, it sends a command to the MG containing a signals descriptor with the rsp signal. Upon reception of a command with the rsp signal, the MG either applies a loop-back or (for 2-wire circuits) awaits reception of a continuity test tone. In the loop-back case, any incoming information shall be reflected back as outgoing information. In the 2-wire case, any time the appropriate test tone is received, the appropriate response tone should be sent. The MGC will determine when to remove the rsp signal."
“当MGC希望MG响应连续性测试时，它向MG发送一个命令，其中包含一个带有rsp信号的信号描述符。当接收到带有rsp信号的命令时，MG应用环回或（对于双线电路）等待连续性测试音的接收。在环回情况下，任何传入信息应作为传出信息反射回来。在双线情况下，任何时候收到适当的测试音，都应发送适当的响应音。MGC将确定何时删除rsp信号。”
Section: Appendix A.1.2 "Example -- Collecting Originator Digits and
Initiating Termination"
----------
Issue: Step 3 uses a now-obsolete package DS0 for echo cancellation.
Section: Appendix A.1.2 "Example -- Collecting Originator Digits and
Initiating Termination"
----------
Issue: Step 3 uses a now-obsolete package DS0 for echo cancellation.
Resolution: replace with echo cancellation via package TDM.
解决方案：替换为通过包TDM的回声消除。
Issue: Step 20 fails to show a returned TerminationStateDescriptor. It also contains the erroneous statement that an RTP termination does not support events and signals and fails to show a number of other descriptors.
问题：步骤20未能显示返回的TerminationStateDescriptor。它还包含一条错误的语句，即RTP终端不支持事件和信号，并且无法显示许多其他描述符。
Resolution: Delete the sentence containing the erroneous statement. Add the following to the Media Descriptor preceding the line "Stream = 1_": "TerminationState { ServiceStates = InService, EventBufferControl = OFF },"
决议：删除包含错误陈述的句子。将以下内容添加到“Stream=1”行前面的媒体描述符中：“TerminationState{ServiceStates=InService，EventBufferControl=OFF}”
Add lines showing Events, Signals, and DigitMap descriptors following the Media descriptor.
在媒体描述符后面添加显示事件、信号和DigitMap描述符的行。
"Events, Signals, DigitMap,"
事件、信号、数字地图
This memo is a supplement to [2], which contains the required security section.
本备忘录是[2]的补充，其中包含所需的安全部分。
[1] Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, RFC 2026, October 1996.
[1] Bradner，S.，“互联网标准过程——第3版”，BCP 9，RFC 2026，1996年10月。
[2] Cuervo, F., Greene, N., Huitema, C., Rayhan, A., Rosen, B. and J. Segeret, "Megaco Protocol", RFC 2885, August 2000.
[2] Cuervo，F.，Greene，N.，Huitema，C.，Rayhan，A.，Rosen，B.和J.Segeret，“Megaco协议”，RFC 28852000年8月。
[3] Bradner, S., "Key Words For Use In RFCs To Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[3] Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
This memo records the contributions of a number of people on the Megaco list and the H.248 faithful in ITU-T Study Group 16 who took the time to read the Megaco/H.248 document with care and attention. Thanks to all of them.
本备忘录记录了Megaco名单上的许多人以及ITU-T研究组16中的H.248信徒的贡献，他们花时间仔细阅读了Megaco/H.248文件。感谢他们所有人。
Tom Taylor Nortel Networks P.O. Box 3511, Station C Ottawa, Ontario, Canada K1Y 4P7
Tom Taylor Nortel Networks加拿大安大略省渥太华C站3511信箱K1Y 4P7
Phone: +1 613 736 0961
EMail: taylor@nortelnetworks.com
Phone: +1 613 736 0961
EMail: taylor@nortelnetworks.com
Copyright (C) The Internet Society (2000). All Rights Reserved.
版权所有（C）互联网协会（2000年）。版权所有。
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 assigns.
上述授予的有限许可是永久性的，互联网协会或其继承人或受让人不会撤销。
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.
RFC编辑功能的资金目前由互联网协会提供。