- sg16-avd - lists.packetizer.com

Addressing information in H.450.1
by Pete Cordell 24 Feb '98

24 Feb '98

Dear Karl (or anybody else who can answer), Please can you assure me that the majority of the partyNumber fields in Table 6/H.450.1 (white) should indeed refer PartyNumber and not to EndpointAddress as I would have first expected!!! Many thanks, Pete ================================= Pete Cordell BT Labs E-Mail: pete.cordell(a)bt-sys.bt.co.uk Tel: +44 1473 646436 Fax: +44 1473 645499 =================================

1 0

Re: User Information or Information in H.225.0
by Callaghan, Robert 23 Feb '98

23 Feb '98

Pete, Just a minor adjustment. H.450.1 specifies the use of call-independent signaling. Bob -------------------------------------- Robert Callaghan Siemens Business Communication Systems Email: Robert.Callaghan(a)Siemenscom.com Tel: +1.561.997.3756 FAX: +1.561.997.3403 >-----Original Message----- >From: Pete Cordell [SMTP:pete.cordell@BT-SYS.BT.CO.UK] >Sent: Friday, February 20, 1998 8:44 AM >To: ITU-SG16(a)MAILBAG.INTEL.COM >Subject: Re: User Information or Information in H.225.0 > >Glen, > >On closer examination there seem to be a few errors in Table 4/H.225.0. >The 6th paragraph of section 7.1/H.225.0 (white paper at least) says >that the "The procedures of Q.931/Section 3.1 for circuit mode >connection setup are followed." According to this section the messages >"User Information" and "Congestion Control" do not apply. They are used >in the call-independent signalling part that we are not using. > >Also "Status Inquiry" is spelt "Status Enquiry" in Q.931 (not that I >would know what is the right form!!!). > >We need to go with option 1 of your suggestions. The Information >message is what we need for overlap sending. The description part of >7.3.6 is correct for the "Information" message (including the reference >to the table in Q.931). > >If we can silently remove "Congestion Control" at the same time so much >the better!!!!! > >Regards, > >Pete >================================= >Pete Cordell >BT Labs >E-Mail: pete.cordell(a)bt-sys.bt.co.uk >Tel: +44 1473 646436 >Fax: +44 1473 645499 >================================= > > >>---------- >>From: Glen Freundlich[SMTP:ggf@LUCENT.COM] >>Sent: 19 February 1998 16:09 >>To: ITU-SG16(a)MAILBAG.INTEL.COM >>Subject: User Information or Information in H.225.0 >> >>In H.225.0 V1, section 7.3.6 describes the User Information message. >>The >>related ASN.1 definition is named UI-UUIE, but the table and caption >>(Table 9) describe the Q.931 Information message. >> >>H.323 V2 describes the use of the Information message (for example, to >>support overlap sending), but H.225.0 V2 contains no section describing >>the Information message and no ASN.1 has been defined specifically for >>use with the Information message. >> >>Possible fixes seem to be: >> >>1 - rename section 7.3.6 from "User Information" to "Information" and >>add some text stating that the Information message is used to support >>overlap sending >> >>2 - correct section 7.3.6 to align with the User Information message >>(correct the table, correct the reference to Q.931) and add a new >>section (and associated ASN.1) for the Information message >> >>3 - other suggestions? >> >>As backward compatibility is a concern, the best approach depends on >>existing implementations and the use of User Information or Information >>messages. So, a vendor that decides to implement might interpret this >>to >>be a User Information message with a different set of information >>elements (not as described in table 9/H225) or an Information message >>with the set of information elements as defined in table 9. >> >>Please comment. >> >>Regards, >>Glen Freundlich (editor H.225.0) >> >> >>-- >>Glen Freundlich ggf(a)lucent.com >>Lucent Technologies office: +1 303 538 2899 >>11900 N. Pecos fax: +1 303 538 3907 >>Westminster, Colorado 80234 USA >>

1 0

unsubscribe/subscribe
by isabelle haignere 23 Feb '98

23 Feb '98

Please, would it be possible to be unregistered with the Email address "isabelle.haignere(a)issy.cnet.fr" ? and to be registered with the new Email address "isabelle.haignere(a)cnet.francetelecom.fr ? I thank you very much. Isabelle Haignere FT/BD - CNET/DSE/SGV 38-40 rue du general Leclerc 92131 Issy-Moulineaux Tel : 33 1 45 29 40 08 Fax : 33 1 45 29 52 94 Email : isabelle.haignere(a)cnet.francetelecom.fr --------------------------------------------------- --------------------------------------------------- Isabelle HAIGNERE FT/BD - CNET/DSE/SGV 38-40 rue du general Leclerc 92131 Issy-Moulineaux Tel : 33 1 45 29 40 08 Fax : 33 1 45 29 52 94 Email : isabelle.haignere(a)cnet.francetelecom.fr ---------------------------------------------------

1 0

Request of uploading
by Sakae Okubo 20 Feb '98

20 Feb '98

Dear Editors, Please upload your decided and determined draft Recommendations at the Incoming directory if not yet done. Best regards, Sakae OKUBO (Mr.) ******************************************************************** Graphics Communication Laboratories Phone: +81 3 5351 0181 6F ANNEX TOSHIN BLDG. Fax: +81 3 5351 0184 4-36-19 Yoyogi, Shibuya-ku, Tokyo e-mail: okubo(a)gctech.co.jp 151-0053 Japan ********************************************************************

1 0

Treatment of Q.931 Shifted Code Sets in H.225.0v2
by Tom Taylor 20 Feb '98

20 Feb '98

In Sec. 7.1 of H.225.0 the following paragraph appears shortly before the table: "Endpoints not supporting Q.931 shifted code sets shall ignore all Q.931 messages using such methods." Was this not supposed to read: "Endpoints not supporting Q.931 shifted code sets shall ignore all IEs using such methods." Background: the latter is the practice in ISDN land. The typical use of shifted code sets in North America is for the end-to-end transport of display information (e.g. caller's name and number). Code set 5 (national information) is used for the purpose.

1 0

Re: Request of uploading
by Kiyoshi SAKAI 20 Feb '98

20 Feb '98

Dear Mr.Okubo, As requested, I have uploaded the determined version of H.310v2 document to the Incoming directory of the GCL ftp site. The file name is; TD66PL_R.ZIP (Word95 document "h310v2DR.doc" is zipped in it) Regards, ********************************************************************** Kiyoshi Sakai Media Processing Laboratory Multimedia Systems Labs. FUJITSU LABORATORIES LTD. Tel. : +81 44 754 2679 Fax. : +81 44 754 2347 E-mail : sakai(a)flab.fujitsu.co.jp **********************************************************************

1 0

Re: User Information or Information in H.225.0
by Pete Cordell 20 Feb '98

20 Feb '98

Glen, On closer examination there seem to be a few errors in Table 4/H.225.0. The 6th paragraph of section 7.1/H.225.0 (white paper at least) says that the "The procedures of Q.931/Section 3.1 for circuit mode connection setup are followed." According to this section the messages "User Information" and "Congestion Control" do not apply. They are used in the call-independent signalling part that we are not using. Also "Status Inquiry" is spelt "Status Enquiry" in Q.931 (not that I would know what is the right form!!!). We need to go with option 1 of your suggestions. The Information message is what we need for overlap sending. The description part of 7.3.6 is correct for the "Information" message (including the reference to the table in Q.931). If we can silently remove "Congestion Control" at the same time so much the better!!!!! Regards, Pete ================================= Pete Cordell BT Labs E-Mail: pete.cordell(a)bt-sys.bt.co.uk Tel: +44 1473 646436 Fax: +44 1473 645499 ================================= >---------- >From: Glen Freundlich[SMTP:ggf@LUCENT.COM] >Sent: 19 February 1998 16:09 >To: ITU-SG16(a)MAILBAG.INTEL.COM >Subject: User Information or Information in H.225.0 > >In H.225.0 V1, section 7.3.6 describes the User Information message. >The >related ASN.1 definition is named UI-UUIE, but the table and caption >(Table 9) describe the Q.931 Information message. > >H.323 V2 describes the use of the Information message (for example, to >support overlap sending), but H.225.0 V2 contains no section describing >the Information message and no ASN.1 has been defined specifically for >use with the Information message. > >Possible fixes seem to be: > >1 - rename section 7.3.6 from "User Information" to "Information" and >add some text stating that the Information message is used to support >overlap sending > >2 - correct section 7.3.6 to align with the User Information message >(correct the table, correct the reference to Q.931) and add a new >section (and associated ASN.1) for the Information message > >3 - other suggestions? > >As backward compatibility is a concern, the best approach depends on >existing implementations and the use of User Information or Information >messages. So, a vendor that decides to implement might interpret this >to >be a User Information message with a different set of information >elements (not as described in table 9/H225) or an Information message >with the set of information elements as defined in table 9. > >Please comment. > >Regards, >Glen Freundlich (editor H.225.0) > > >-- >Glen Freundlich ggf(a)lucent.com >Lucent Technologies office: +1 303 538 2899 >11900 N. Pecos fax: +1 303 538 3907 >Westminster, Colorado 80234 USA >

1 0

User Information or Information in H.225.0
by Glen Freundlich 19 Feb '98

19 Feb '98

In H.225.0 V1, section 7.3.6 describes the User Information message. The related ASN.1 definition is named UI-UUIE, but the table and caption (Table 9) describe the Q.931 Information message. H.323 V2 describes the use of the Information message (for example, to support overlap sending), but H.225.0 V2 contains no section describing the Information message and no ASN.1 has been defined specifically for use with the Information message. Possible fixes seem to be: 1 - rename section 7.3.6 from "User Information" to "Information" and add some text stating that the Information message is used to support overlap sending 2 - correct section 7.3.6 to align with the User Information message (correct the table, correct the reference to Q.931) and add a new section (and associated ASN.1) for the Information message 3 - other suggestions? As backward compatibility is a concern, the best approach depends on existing implementations and the use of User Information or Information messages. So, a vendor that decides to implement might interpret this to be a User Information message with a different set of information elements (not as described in table 9/H225) or an Information message with the set of information elements as defined in table 9. Please comment. Regards, Glen Freundlich (editor H.225.0) -- Glen Freundlich ggf(a)lucent.com Lucent Technologies office: +1 303 538 2899 11900 N. Pecos fax: +1 303 538 3907 Westminster, Colorado 80234 USA

1 0

Re: [Help] Who can anyone tell me email address of Mr. Matsumoto..
by Istvan Sebestyen 19 Feb '98

19 Feb '98

At 10:52 19.02.1998 +0900, Yongmin Choi wrote: >I have questions about holding an ITU meeting. >Please let me know the email address of Dr. Matsumoto. > >Thank you in advance.. > >============================================================= >Yong-Min Choi >Technical Evaluation Center >Korea Telecom R & D Group >e-mail: himrchoi(a)rcunix.kotel.co.kr >============================================================= > > Yes, here it is.... matumoto(a)tom.comm.waseda.ac.jp Sincerely, Istvan SEbestyen ------------------------------------------------------------------ Istvan Sebestyen Siemens AG Standardization, Large Networks PN GS 94, Private Communications Systems Group, Mch H/1760/255 Tel: +49-89-722 47230 Hofmannstr. 51 Fax: +49-89-722 47713 D-81359 Munich, GERMANY Internet: istvan.sebestyen(a)mch.pn.siemens.de (preferred) istvan.sebestyen(a)pn.siemens.de (Fall back only) X.400: c=de;a=dbp;p=scn;o=siemens;ou1=mch;ou2=PN-msmail; s=Sebestyen;g=Istvan Note: Unfortunately - in practice - e-mails sent to me occasionally may get lost or stay unread for a long time due to business trips. So, for very important communication pls. send a "back-up" in fax. ------------------------------------------------------------------

1 0

[Help] Who can anyone tell me email address of Mr. Matsumoto..
by Yongmin Choi 18 Feb '98

18 Feb '98

I have questions about holding an ITU meeting. Please let me know the email address of Dr. Matsumoto. Thank you in advance.. ============================================================= Yong-Min Choi Technical Evaluation Center Korea Telecom R & D Group e-mail: himrchoi(a)rcunix.kotel.co.kr =============================================================

1 0