Glen, One thing mentioned on the reflector was moving the CallIdentifier to the H323-UU-PDU part of the message rather than including it separately in each constituent part of the message. This moves it to the highest layer of commonality and also means that it is in the same place for all messages. This is important as the module that decides which call the message belongs to should not really have to know large amounts about the format of each message. Below should show the change I mean: H323-UU-PDU ::= SEQUENCE { h323-message-body CHOICE { setup Setup-UUIE, callProceeding CallProceeding-UUIE, connect Connect-UUIE, alerting Alerting-UUIE, userInformation UI-UUIE, releaseComplete ReleaseComplete-UUIE, facility Facility-UUIE, ..., progress Progress-UUIE, empty NULL -- used when a FACILITY message is sent, -- but the Facility-UUIE is not to be invoked -- (possible when transporting supplementary -- services messages) }, nonStandardData NonStandardParameter OPTIONAL, ..., h4501SupplementaryService SEQUENCE OF OCTET STRING OPTIONAL, -- each sequence of octet string is defined as one -- H4501SupplementaryService APDU as defined in -- Table 3/H.450.1 callIdentifier CallIdentifier } Regards, Pete ================================= Pete Cordell BT Labs E-Mail: pete.cordell@bt-sys.bt.co.uk Tel: +44 1473 646436 Fax: +44 1473 645499 =================================

---------- From: Glen Freundlich[SMTP:ggf@LUCENT.COM] Sent: 07 January 1998 22:54 To: ITU-SG16@MAILBAG.INTEL.COM Subject: corrections to H.225.0 V2

<<File: h2250v2x.doc>> Dear colleagues,

Attached is a document describing changes to the H.225.0 V2 white draft to address various issues I've seen through email. The intent is for this change document to be submitted to the SG16 meeting. Please review the document as soon as possible and let me know if I've missed anything or made some other error. I have not yet addressed issues regarding the pointer to RFC2190 for H263.

In addition, I've compiled the ASN.1 but would appreciate if someone else could also compile it to be sure it is sane.

Thank you, Glen

-- Glen Freundlich ggf@lucent.com Lucent Technologies office: +1 303 538 2899 11900 N. Pecos fax: +1 303 538 3907 Westminster, Colorado 80234 USA