- sg16-avd - lists.packetizer.com

Contributions for the Yokosuka meeting
by Sakae OKUBO 11 Apr '98

11 Apr '98

Dear Q.112-14 colleagues, So far I have listed from APC-1328 to 1366 as contributions to the Yokosuka meeting as attached. The following are yet to be uploaded. APC-1338 APC-1344 APC-1345 APC-1350 APC-1351 APC-1359 APC-1365 As we lost another incoming mails during 16:00 Thursay - 10:00 Friday (Tokyo time) without advising the sender, I may have missed your important messages. Please send them again to me if any. Many apologies about this. To those who are coming to Yokosuka, I wish you safe … [View More]trips. See you next week. 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 or okubo(a)mxz.meshnet.or.jp ******************************************************************** ----------------------------------------------------------------------- APC- Source Provisional Title ----------------------------------------------------------------------- 1328 Siemens Proposal for Call Hold Supplementary service in H.323 (H.450.Hold) 1329 Siemens Proposal for Call Park/Call Pickup supplementary service in H.323 (H.450.Park+Pickup) 1330 Siemens Proposal for Call Waiting Supplementary Service H.323 (H.450.CallWaiting) 1331 RADVision A proposal for RTP/RTCP addresses use during the Fast Connect Procedure 1332 RADVision Remarks on H.225.0 1333 Editor Drat Amendment 5 to H.222.0 1334 Editor Draft Annex I to H.225.0 1335 Editor Darft H.245 V4 1336 Editor Darft H.310 V2 1337 Editor Draft H.bmultipoint 1338 Editor Draft Annex D to H.323 1339 PictureTel Proposals and General Comments for H.323 Annex C 1340 Mitel Message Waiting Indication Supplementary Service in H.323 1341 3Com, Ascend, Deutsche Telecom, France Telecom, GPT, Hewlett-Packard, Intel, Lucent Technologies, Post & Telecom Austria (PTA), Siements, VocalTec Inter-Gatekeeper Communication Requirements (H.323 Annex G) 1342 ETSI Communication from EP TIPHON to ITU SG16 on Codec support for H.323 1343 MPEG Liaison response regarding DMIF 1344 Editor H.246 Work Plan and Discussion 1345 VideoServer/Intel Proposal for H.MediaMIB 1346 VideoServer Proposal for H.225 Call Signalling MIB 1347 VideoServer Proposal for H.225 RAS MIB 1348 VideoServer Proposal for H.245 MIB 1349 Cisco Proposal for H.323 Gatekeeper MIB 1350 VideoServer Proposal for H.323 Terminal MIB 1351 multiple Faster connect for H.323 terminals 1352 Editor Draft H.323 v2 Implementers Guide 1353 Intel Proposals and general comments for Inter-Gatekeeper Communications 1354 IBM Comment to the current H.323 endpoint registration procedure 1355 IBM Coding of the MultipointCapabilitys within the H2250Capability data structure 1356 Intel Proposal for Real Time Device Control in H.323 1357 NTT DoCoMo The support of MPEG-4 video in H.324 terminals 1358 Secretary of Meeting Host Organization Network configuration of Yokosuka Rapporteur Meeting 1359 Fujitsu Proposed addition to H.245 for the AAL1/5 conversion gateway capabilities 1360 RADVision Comments on H.235: H.323 Procedures 1361 RADVision GK's role in up-to-date H.323 architecture 1362 Editor Corrections to Decided H.225.0 V2 1363 Lucent H.225 Signaling Enhancements 1364 Madge Networks Comment on the current limitations in H.225.0 v2 for signalling call setup parameters for an outgoing SCN call 1365 VTEL A MIB for audiovisual communication terminals 1366 Accord Real Time Device Control in H.323 ----------------------------------------------------------------------- [View Less]

3 2

address for subscription
by David Bukovinsky 10 Apr '98

10 Apr '98

Sorry for sending this out on this list - can someone send me the email address of the server, and the appropriate message body, to subscribe to the ITU list? thanks, and apologies for sending this out in this forum. --dave ---------------------------------------------------------------------------- ---------------------------------------------- Dave Bukovinsky d.bukovinsky(a)cablelabs.com Project Director, Software Architectures (303) 661-3862 CableLabs, Inc.

1 0

uploaded documents
by George Kajos 10 Apr '98

10 Apr '98

Hello folks, I have uploaded apc1345a.zip, apc-1346.zip, apc-1347.zip, apc-1348.zip, and apc-1349.zip. Mr. Webber please delete apc-1345.zip from the incoming directory in favor of apc1345a.zip. Thank you, George Kajos

1 0

APC-1330 uploaded
by Markku Korpi 10 Apr '98

10 Apr '98

All, I have uploaded the contribution APC-1330 on Call Waiting supplementary service to the PictureTel incoming site (It is in Word 8.0/'97 format) Regards Markku Korpi ------------ Markku Korpi Siemens, 4900 Old Ironsides Dr., P.O.Box 58075, Santa Clara CA 95054 Phone: +1 408 492 7328, E-mail: korpim(a)sbs.de

1 0

APCs 1331, 1332, 1360, 1361
by Orit Levin 09 Apr '98

09 Apr '98

Dear Mr. Okubo! I have uploaded the following APCs to the Incoming Directory: 1331 RADVision A proposal for RTP/RTCP addresses use during the Fast Connect Procedure 1332 RADVision Remarks on H.225.0 1360 RADVision H.235: Comments on H.323 Procedures 1361 RADVision GK's role in up-to-date H.323 architecture Best Regards, Orit Levin RADVision Inc., Mahwah, NJ Tel: 201-529-4300 ext. 230 Fax: 201-529-3516 E Mail: orit(a)radvision.com

1 0

APC-1340 MWI Supplementary Service for H.323
by Dave Walker 09 Apr '98

09 Apr '98

Dear Colleagues, I have uploaded APC-1340, Message Waiting Indication Supplementary Service in H.323, to standard.pictel.com/avc-site/Incoming. Regards, Dave Walker. -- D. R. Walker Mitel Corp, Kanata, ON, CANADA email: dave_walker(a)mitel.com phone: (613) 592-2122 x1613

1 0

APC-1364 uploaded
by Michele Bozier WVdevmt-WS 09 Apr '98

09 Apr '98

All, I have uploaded APC-1364 - " Comment on the current limitations in H.225.0 v2 for signalling call setup parameters for an outgoing SCN call" to the ftp server. Regards Michele Bozier ---------------------------------------- Michele Bozier Principal Development Engineer Madge Networks, Wexham Springs, Framewood Rd, Wexham, Slough SL3 6PJ, England Tel: +44(0)1753 661331 Fax: +44(0)1753 661011 email:mbozier@madge.com

1 0

Re: request for apc number
by Sakae OKUBO 09 Apr '98

09 Apr '98

Dear Roni Even, In response to your requests, APC-1366 has been allocated to your contribution as attached. 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 or okubo(a)mxz.meshnet.or.jp **************… [View More]****************************************************** ----------------------------------------------------------------------- APC- Source Provisional Title ----------------------------------------------------------------------- 1328 Siemens Proposal for Call Hold Supplementary service in H.323 (H.450.Hold) 1329 Siemens Proposal for Call Park/Call Pickup supplementary service in H.323 (H.450.Park+Pickup) 1330 Siemens Proposal for Call Waiting Supplementary Service H.323 (H.450.CallWaiting) 1331 RADVision A proposal for RTP/RTCP addresses use during the Fast Connect Procedure 1332 RADVision Remarks on H.225.0 1333 Editor Drat Amendment 5 to H.222.0 1334 Editor Draft Annex I to H.225.0 1335 Editor Darft H.245 V4 1336 Editor Darft H.310 V2 1337 Editor Draft H.bmultipoint 1338 Editor Draft Annex D to H.323 1339 PictureTel Proposals and General Comments for H.323 Annex C 1340 Mitel Message Waiting Indication Supplementary Service in H.323 1341 3Com, Ascend, Deutsche Telecom, France Telecom, GPT, Hewlett-Packard, Intel, Lucent Technologies, Post & Telecom Austria (PTA), Siements, VocalTec Inter-Gatekeeper Communication Requirements (H.323 Annex G) 1342 ETSI Communication from EP TIPHON to ITU SG16 on Codec support for H.323 1343 MPEG Liaison response regarding DMIF 1344 Editor H.246 Work Plan and Discussion 1345 VideoServer/Intel Proposal for H.MediaMIB 1346 VideoServer Proposal for H.225 Call Signalling MIB 1347 VideoServer Proposal for H.225 RAS MIB 1348 VideoServer Proposal for H.245 MIB 1349 Cisco Proposal for H.323 Gatekeeper MIB 1350 VideoServer Proposal for H.323 Terminal MIB 1351 multiple Faster connect for H.323 terminals 1352 Editor Draft H.323 v2 Implementers Guide 1353 Intel Proposals and general comments for Inter-Gatekeeper Communications 1354 IBM Comment to the current H.323 endpoint registration procedure 1355 IBM Coding of the MultipointCapabilitys within the H2250Capability data structure 1356 Intel Proposal for Real Time Device Control in H.323 1357 NTT DoCoMo The support of MPEG-4 video in H.324 terminals 1358 Secretary of Meeting Host Organization Network configuration of Yokosuka Rapporteur Meeting 1359 Fujitsu Proposed addition to H.245 for the AAL1/5 conversion gateway capabilities 1360 RADVision Comments on H.235: H.323 Procedures 1361 RADVision GK's role in up-to-date H.323 architecture 1362 Editor Corrections to Decided H.225.0 V2 1363 Lucent H.225 Signaling Enhancements 1364 Madge Networks Comment on the current limitations in H.225.0 v2 for signalling call setup parameters for an outgoing SCN call 1365 VTEL A MIB for audiovisual communication terminals 1366 Accord Real Time Device Control in H.323 ----------------------------------------------------------------------- [View Less]

1 0

APC-1336
by Kiyoshi SAKAI 09 Apr '98

09 Apr '98

Dear Mr. Okubo and Q.12-14 colleagues, I have uploaded the following file to the "avc-site/Incoming" directory; apc1336.zip: Draft H.310 version 2 The zip-file contains a Word95/6.0(US version) compatible document. If you have any problems to read the file, please let me know. Regards, ********************************************************************** Kiyoshi Sakai Media Processing Laboratory … [View More]

1 0

Multiple RAS messages per PDU?
by Paul Long 09 Apr '98

09 Apr '98

6.1/H.225.0v2 says, "When messages are sent on the reliable H.245 control channel, more than one message may be sent within the boundaries defined by the reliable transport PDU as long as whole messages are sent;" However, nothing is said about whether more than one _RAS_ message may be sent "within the boundaries defined by the _un_reliable transport PDU as long as whole messages are sent." Are we allowed or prohibited from packing RAS messages, or is this just not addressed in the … [View More]

2 1