- sg16-avd - lists.packetizer.com

H.322 Version3
by Negar Moshiri 08 Oct '98

08 Oct '98

Does anybody know where I can get a draft copy of H.323 Version 3? Thanks, Negar Moshiri _______________________________________________________________ ========= =========== Negar Moshiri mailto:nm@salix.com ============ Staff Engineer http://www.salix.com ============ SALIX Technologies, Inc. == ==== == 904 Wind River Lane TEL: (301) 417-0017 == Suite 101 FAX: (301) 990-6400 === Gaithersburg, MD 20878 The statements contained herein are strictly those of their author, and unless otherwise specifically indicated should not be attributed to SALIX® or its management.

1 0

CFP on Internet Telephony
by Henning Schulzrinne (by way of Jim Toga <jim.toga＠intel.com>) 07 Oct '98

07 Oct '98

Jim, the attached CFP may be of interest to members of SG16. However, since I don't know the policies of the mailing list, I would appreciate if you could distribute it as you consider appropriate. I would love to have an article from somebody involved with SG16 in the issue. Thanks. Henning -- Henning Schulzrinne email: schulzrinne(a)cs.columbia.edu Dept. of Computer Science phone: +1 732 949 8344 (at Bell Labs) Columbia University fax: +1 212 666-0140 New York, NY 10027 URL: http://www.cs.columbia.edu/~hgs Call for Papers for a Joint Issue of IEEE Internet Computing (http://www.computer.org/internet) IEEE Network Magazine (http://www.comsoc.org/socstr/techcom/ntwrk/) --------------------------------------------------------------------- Special Issue on Internet Telephony (May/June 1999) --------------------------------------------------- Submission deadline: November 25, 1998 Guest Editor: Henning Schulzrinne Department of Computer Science Columbia University New York, NY Phone: 212 939 7042 Fax: 212 666 0140 WWW: http://www.cs.columbia.edu/~hgs email: hgs(a)cs.columbia.edu Internet telephony, that is, using the Internet as a communications infrastructure to replace and enhance existing telephone services, is promising to fundamentally change one of the most basic and familiar communications services. This special issue covers the technology needed to make Internet telephony a reality and the challenges that need to be addressed. This is a joint issue of the IEEE Internet Computing and IEEE Network Magazines. Topics of interest for technical papers include: * quality-of-service specific to large-scale telephony services * charging, billing and customer care * web-centric telephony service enhancements * service creation: applications, languages, tools * interworking with the global switched telephone network (GSTN): gateways, service location, directories * hybrid Internet-PSTN architectures * directory services * signaling * novel applications * embedded systems * management of QOS, services and * security and privacy issues * economic and regulatory impact We are especially interested in research papers that describe real services, software systems and experiments. Work-in-progress papers describing the state of on-going research projects in Internet telephony are also encouraged. Papers should explicate the technical issues related to Internet telephony, rather than just generic multimedia applications. Research papers should demonstrate the feasibility of the approach and describe the state of realization. Case studies and applied papers should discuss the key factors that made the system work and should also mention the pitfalls and problems encountered and how they may be overcome. Submission, Approval, Review, and Acceptance. --------------------------------------------- Authors are requested to send e-mail to the guest-editor, Henning Schulzrinne (hgs(a)cs.columbia.edu) giving a URL where the guest-editor can review the article, preferably in HTML format with GIF artwork (postscript or pdf format is also accepted). Upon approval by the guest-editor, all feature articles will then undergo a technical peer review consistent with other archival publications. Potential authors may wish to consult the sections on author information and guidelines for reviewers, which are given at http://www.comsoc.org/socstr/techcom/ntwrk. Articles for review should be in HTML or a common format easily read by reviewers. Authors will send all files to an anonymous ftp site provided by the guest editor. When an article consists of a collection of HTML and GIF files, all internal links pointing to this file should be relative. More details on the submission guidelines can be found in http://www.computer.org/internet/edguide.htm and http://www.comsoc.org/socstr/techcom/ntwrk/ Submission Deadline: November 25, 1998 Acceptance Notification: February 1, 1999 Final Manuscripts Due: March 1, 1999 Publication of Completed Special Issue: May/June 1999 http://www.comsoc.org/socstr/techcom/ntwrk/special/schulzrinne.html

1 0

Re: H.245 v5 determined - correction
by Rahul Chopra 07 Oct '98

07 Oct '98

Sakae: Have been trying to get the address for the server, if anyone can point me to it. Thanks. Rahul > -----Original Message----- > From: Sakae OKUBO [SMTP:okubo@GITI.OR.JP] > Sent: Wednesday, October 07, 1998 6:35 AM > To: ITU-SG16(a)mailbag.cps.intel.com > Subject: H.245 v5 determined - correction > > Dear Q.12-14/16 experts, > > M Nilsson> As pointed out in the attached,determined version 5 should > M Nilsson> have been created from TD39(PLEN) AND TD28(PLEN). > M Nilsson> > M Nilsson> I have now uploaded the corrected document. > M Nilsson> > M Nilsson> Mr Okubo : please remove the zip file that you created > M Nilsson> yesterday. > > This has been actioned; new file is available as follows: > > /9809_Gen/H245delga.zip > > Best regards, > > Sakae OKUBO (Mr.) > *********************************************************** > Waseda Research Center > Telecommunications Advancement Organization of Japan (TAO) > 5th Floor, Nishi-Waseda Bldg. > 1-21-1 Nishi-Waseda, Shinjuku-ku, Tokyo > 169-0051 Japan > Tel: +81 3 5286 3830 > Fax: +81 3 5287 7287 > e-mail: okubo(a)giti.or.jp > ***********************************************************

1 0

H.245 v5 determined - correction
by Sakae OKUBO 07 Oct '98

07 Oct '98

Dear Q.12-14/16 experts, M Nilsson> As pointed out in the attached,determined version 5 should M Nilsson> have been created from TD39(PLEN) AND TD28(PLEN). M Nilsson> M Nilsson> I have now uploaded the corrected document. M Nilsson> M Nilsson> Mr Okubo : please remove the zip file that you created M Nilsson> yesterday. This has been actioned; new file is available as follows: /9809_Gen/H245delga.zip Best regards, Sakae OKUBO (Mr.) *********************************************************** Waseda Research Center Telecommunications Advancement Organization of Japan (TAO) 5th Floor, Nishi-Waseda Bldg. 1-21-1 Nishi-Waseda, Shinjuku-ku, Tokyo 169-0051 Japan Tel: +81 3 5286 3830 Fax: +81 3 5287 7287 e-mail: okubo(a)giti.or.jp ***********************************************************

1 0

Re: H.245 V5 determined
by Mike Nilsson 07 Oct '98

07 Oct '98

Apologies for causing confusion. As pointed out in the attached, determined version 5 should have been created from TD39(PLEN) AND TD28(PLEN). I have now uploaded the corrected document. Mr Okubo : please remove the zip file that you created yesterday. Best regards Mike Nilsson *********************************************************************** * Mike Nilsson Tel: +44 1473 645413 * * Real Time Internet Group Fax: +44 1473 645011 * * Applications and Middleware Email: mike.nilsson(a)bt-sys.bt.co.uk * * BT Laboratories [B54 Room 94] * * Martlesham Heath * * Ipswich IP5 3RE * * UK * *********************************************************************** Dear Mr. Mike Nilsson, >I have uploaded the document H245DELG.DOC to the ftp site. This is the >delta document that was determined as version 5 of H.245. In this document, items in TD39(PLEN) are contained but other items approved as H.245 ver.5 determination described in the separate TD (TD28(PLEN)) are not included. Can I ask the status of this document? Is this to reflect all items approved as H.245 ver.5 determination? Or is this for some but not all items approved for the determination as in TD39(PLEN)? In the former case, TD28(PLEN) should be reflected in the document. In the latter case, separate document should be provided to reflect all the approved items for the H.245 determination. I can work for the items in TD28(PLEN). Would you please tell me the status for the clarify and to help the editorial work on H.245 text? Best regards, ---- Yoshihiro Kikuchi E-mail: kiku(a)eel.rdc.toshiba.co.jp Research and Development Center TEL: +81 +44 549 2151 Toshiba Corp. FAX: +81 +44 520 1308 >---------- >From: Sakae OKUBO[SMTP:okubo@GITI.OR.JP] >Sent: 07 October 1998 07:25 >To: ITU-SG16(a)MAILBAG.INTEL.COM >Subject: H.245 V5 determined > >Dear Q.12-14/16 experts, > >M Nilsson> I have uploaded the document H245DELG.DOC to the ftp site. >M Nilsson> This is the delta document that was determined as version 5 >M Nilsson> of H.245. >M Nilsson> >M Nilsson> Version 4 of H.245 was approved without any changes to COM- >M Nilsson> 59. > >This delta file has been zipped and moved to the following place: > > ftp://standard.pictel.com/avc-site/9809_Gen/H245delg.zip > > >Best regards, > >Sakae OKUBO (Mr.) >*********************************************************** >Waseda Research Center >Telecommunications Advancement Organization of Japan (TAO) >5th Floor, Nishi-Waseda Bldg. >1-21-1 Nishi-Waseda, Shinjuku-ku, Tokyo >169-0051 Japan > Tel: +81 3 5286 3830 > Fax: +81 3 5287 7287 > e-mail: okubo(a)giti.or.jp >*********************************************************** >

1 0

H.245 V5 determined
by Sakae OKUBO 07 Oct '98

07 Oct '98

Dear Q.12-14/16 experts, M Nilsson> I have uploaded the document H245DELG.DOC to the ftp site. M Nilsson> This is the delta document that was determined as version 5 M Nilsson> of H.245. M Nilsson> M Nilsson> Version 4 of H.245 was approved without any changes to COM- M Nilsson> 59. This delta file has been zipped and moved to the following place: ftp://standard.pictel.com/avc-site/9809_Gen/H245delg.zip Best regards, Sakae OKUBO (Mr.) *********************************************************** Waseda Research Center Telecommunications Advancement Organization of Japan (TAO) 5th Floor, Nishi-Waseda Bldg. 1-21-1 Nishi-Waseda, Shinjuku-ku, Tokyo 169-0051 Japan Tel: +81 3 5286 3830 Fax: +81 3 5287 7287 e-mail: okubo(a)giti.or.jp ***********************************************************

1 0

Re: Output/Input Documents of the SG16 meeting
by Mike Nilsson 06 Oct '98

06 Oct '98

I have uploaded the document H245DELG.DOC to the ftp site. This is the delta document that was determined as version 5 of H.245. Version 4 of H.245 was approved without any changes to COM-59. Best regards Mike Nilsson *********************************************************************** * Mike Nilsson Tel: +44 1473 645413 * * Real Time Internet Group Fax: +44 1473 645011 * * Applications and Middleware Email: mike.nilsson(a)bt-sys.bt.co.uk * * BT Laboratories [B54 Room 94] * * Martlesham Heath * * Ipswich IP5 3RE * * UK * *********************************************************************** >

1 0

Fwd: h341 determined on Picturetel site
by Sakae OKUBO 05 Oct '98

05 Oct '98

Dear Q.12-14/16 experts, George Kajos> I uploaded H341det.doc and H341det.zip to the Picturetel site. George Kajos> The document George Kajos> contains all changes requested at eh Study Group meeting. H341det.zip has been moved to the following place: ftp://standard.pictel.com/avc-site/9809_Gen/H341DET.ZIP Best regards, Sakae OKUBO (Mr.) *********************************************************** Waseda Research Center Telecommunications Advancement Organization of Japan (TAO) 5th Floor, Nishi-Waseda Bldg. 1-21-1 Nishi-Waseda, Shinjuku-ku, Tokyo 169-0051 Japan Tel: +81 3 5286 3830 Fax: +81 3 5287 7287 e-mail: okubo(a)giti.or.jp ***********************************************************

1 0

Re: Draft H.323 Annexes E and F uploaded
by Kaynam Hedayat 05 Oct '98

05 Oct '98

Kishore, The duplicate packet over UDP might be due to a lost response packet. In that case you must send the original response. I am not sure what you mean by dropping the Q.931 headers. All of H.225.0 is carried over UDP. Kaynam Kishore Babu Ramisetty <kish(a)TRILLIUM.COM> on 09/29/98 03:16:20 PM Please respond to Mailing list for parties associated with ITU-T Study Group 16 <ITU-SG16(a)MAILBAG.INTEL.COM> To: ITU-SG16(a)MAILBAG.INTEL.COM cc: (bcc: Kaynam Hedayat/PicTel) Subject: Re: Draft H.323 Annexes E and F uploaded Hi Folks, Annex E -- sections E.2.3 and E.5.3 are contradictory. section E.2.3 >NOTE: It is possible in the above scenario to get duplicate PDUs over TCP and >UDP. The Annex E. compliant application shall treat such an occurrence the >same way it treats duplicate UDP PDUs. section E.5.3 >If the request is a duplicate of a message formerly received via TCP, it shall >be silently ignored. If the request is a duplicate of a message formerly >received via UDP, the response given to the original request message shall be >retransmitted immediately and the currently active timer (see below) shall be restarted. Assuming section E.5.3 is correct, why should the duplicate PDUs get a different kind of treatment when received via UDP? Is there any reason why the duplicate PDU received via UDP cannot be ignored? Also, I would appreciate if someone can enlighten me of the reasons for dropping Q.931 headers from the messages sent via UDP? For eg. The rate multiplier etc. in Q.931 setup could be used for interworking with SCN. (Is it now done via h323-uu-pdu itself?) Thanks, -Kishore. > -----Original Message----- > From: Mailing list for parties associated with ITU-T Study Group 16 > [mailto:ITU-SG16@mailbag.cps.intel.com]On Behalf Of Rahul Chopra > Sent: Monday, September 28, 1998 2:51 PM > To: ITU-SG16(a)mailbag.cps.intel.com > Subject: Re: Draft H.323 Annexes E and F uploaded > > > Joerg: > Where is the avc-site? > Would apprecate a pointer > Thanks. > Rahul > > > -----Original Message----- > > From: Joerg Ott [SMTP:jo@INFORMATIK.UNI-BREMEN.DE] > > Sent: Monday, September 28, 1998 5:35 PM > > To: ITU-SG16(a)mailbag.cps.intel.com > > Subject: Draft H.323 Annexes E and F uploaded > > > > Folks, > > > > I have uploaded the determined documents H.323 Annex E and > > H.323 Annex F into the Incoming directory of the AVC ftp site. > > The file names are: > > > > H323-AnnexE-4.02.doc (equivalent to TD-47/PLEN) > > H323-AnnexF-03.doc (equivalent to TD-51/PLEN) > > > > Joerg >

1 0

Mr. Tosco report of WP2/16
by Sakae OKUBO 05 Oct '98

05 Oct '98

Dear Q.12-14/16 experts, Please be advised that Mr. Tosco's report of WP2/16 of the September SG16 meeting has been placed at the following: ftp://standard.pictel.com/avc-site/9809_Gen/Tosco_WP2_report.zip Best regards, Sakae OKUBO (Mr.) *********************************************************** Waseda Research Center Telecommunications Advancement Organization of Japan (TAO) 5th Floor, Nishi-Waseda Bldg. 1-21-1 Nishi-Waseda, Shinjuku-ku, Tokyo 169-0051 Japan Tel: +81 3 5286 3830 Fax: +81 3 5287 7287 e-mail: okubo(a)giti.or.jp ***********************************************************

1 0

Output/Input Documents of the SG16 meeting
by Sakae OKUBO 05 Oct '98

05 Oct '98

Dear Q12-14/16 experts, I have moved all the files in the Incoming directory to the following: ftp://standard.pictel.com/avc-site/9809_Gen or http://standard.pictel.com/ftp/avc-site/9809_Gen Please see /9809_Gen/9809_Gen.html for the index. Editors are requested to upload the final documents for the interested parties. Best regards, Sakae OKUBO (Mr.) *********************************************************** Waseda Research Center Telecommunications Advancement Organization of Japan (TAO) 5th Floor, Nishi-Waseda Bldg. 1-21-1 Nishi-Waseda, Shinjuku-ku, Tokyo 169-0051 Japan Tel: +81 3 5286 3830 Fax: +81 3 5287 7287 e-mail: okubo(a)giti.or.jp ***********************************************************

1 0

Re: About H.323 interoperating with ss7
by Ami Amir 02 Oct '98

02 Oct '98

Krishna Attached are the two relevant ones. Ami -----Original Message----- From: Krishna Kurapati [SMTP:kkrishna@ipcell.com] Sent: Thursday, October 01, 1998 5:28 PM To: 'Ami Amir'; Matt Holdrege Cc: Guocai Deng; iptel(a)lists.research.bell-labs.com Subject: RE: About H.323 interoperating with ss7 Dear Ami, Thanks for the information. Is there a mailing-list for participating in this ITU activity ? Thanks Krishna Kurapati IPCell Technology, Inc 2011 North Collins Blvd Suite 707 Richardson TX 75075 (972) 671 2355 -----Original Message----- From: Ami Amir [SMTP:amir@radvision.rad.co.il] Sent: Wednesday, September 30, 1998 8:23 AM To: Matt Holdrege Cc: Guocai Deng; iptel(a)lists.research.bell-labs.com Subject: Re: About H.323 interoperating with ss7 Hi At the last SG 16 H.323 meeting in Geneva - the IPDC documents were submitted - and based on those inputs and discussions during the meeting, it was agreed that a "work item" be created around the concept that gateways may be decomposed inot two elements - High Level Control, and an assembly of media gateways with "Low Level Control". The concept was driven in part by the realization that in public network, SS7 or similar non-associated signaling networks, there is a need to provide a solution where the SS7 like signaling will interface to the High Level Gateway Control, which will then - via a high level to low level protocol - control the media streams and gateway connections. The plan is to work on this work item before and during the next meeting (scheduled for November in Torino, Italy). Ami Matt Holdrege wrote: > > ---------- > > From: Matt Holdrege[SMTP:MATT@ASCEND.COM] > > Sent: Wednesday, September 30, 1998 1:01:54 PM > > To: Guocai Deng > > Cc: iptel(a)lists.research.bell-labs.com > > Subject: Re: About H.323 interoperating with ss7 > > Auto forwarded by a Rule > > > At 10:14 AM 9/30/98 +0800, Guocai Deng wrote: > > Who can tell me how H.323 network interoperating with SS7 network ? > >it maybe important to support supplementary services and one stage dial. > > We are working on this issue in various standards bodies including the > IETF, ITU-T, ETSI and other forums. IETF drafts include: > > draft-greene-ss7-arch-frame-00.txt > draft-ong-rsgp-ss7-info-00.txt > draft-huitema-sgcp-v1-02.txt > draft-taylor-ipdc-00.txt > draft-elliott-ipdc-media-00.txt > draft-dugan-ipdc-connection-00.txt > draft-bell-ipdc-signaling-00.txt > draft-pickett-ipdc-management-00.txt > > And I'm sure we will see more before the next IETF meeting. We may see some > new IETF working groups on this topic by then as well. > > --------- > This message came from the IETF IPTEL Working Group Mailing List. --------- This message came from the IETF IPTEL Working Group Mailing List. --------- This message came from the IETF IPTEL Working Group Mailing List.

1 0

Re: H.332 uploaded into the Incoming directory of the avc ftp sit e
by Kumar, Vineet 01 Oct '98

01 Oct '98

ftp://standard.pictel.com/avc-site/Incoming/ vineet > -----Original Message----- > From: Spencer Hu [SMTP:Spencer.Hu@GDC.COM] > Sent: Wednesday, September 30, 1998 4:26 AM > To: ITU-SG16(a)MAILBAG.INTEL.COM > Subject: Re: H.332 uploaded into the Incoming directory of the avc > ftp site > > Spencer Hu@GDC > 09/30/98 07:26 AM > > DO YOU HAVE A WEB ADDRESS, PLEASE? > > > SPENCER > > ------ > > > > > "Kumar, Vineet" <vineet.kumar(a)intel.com> on 09/29/98 05:53:30 PM > > Please respond to Mailing list for parties associated with ITU-T Study > Group 16 <ITU-SG16(a)mailbag.cps.intel.com> > > To: ITU-SG16(a)mailbag.cps.intel.com > cc: (bcc: Spencer Hu/Engineering/GDC/US) > Subject: H.332 uploaded into the Incoming directory of the avc ftp site > > > > > I have uploaded the decided version of H.332 (h332.doc) and the approved > version of the Implementers Gudie (h323ImplGuide.doc) into the Incoming > directory of the avc ftp site. > vineet > -------------------------------------------------------------------------- > - > - > -------------------------- > Vineet Kumar vineet.kumar(a)intel.com > Intel Corporation, JF3-212 (+1) 503-264-3439 > (phone) > Hillsboro, OR 97124-5961 (+1) 503-264-3375 > (fax) > -------------------------------------------------------------------------- > - > - > --------------------------

1 0

Re: Overlapped Sending and LRQ
by Chris Purvis WVdevmt-WS 01 Oct '98

01 Oct '98

Sarah, The overlapped send section as I understand it is predicated on the following assumptions: 1. A number that is incomplete can not also be complete! If this guideline is not followed, an endpoint in a zone separate from those of the two endpoint 1234 and 12345 (say) that attempts to dial a number one digit at a time will NEVER be able to get through to 12345! 2. Numbers are unique. 3. A gatekeeper will know from the format and first part of a number how long it should be. For example a gatekeeper might assume that if a number is not in its own zone (and therefore known by it) then to stand any chance it will have to be a full international number, whose format and length are specified in E.164. Public numbering plans do need to be covered as part of the Annex G effort, if we are going to attempt to do anything meaningful there with phone number-type addresses (as opposed to emailid-type addresses). Unfortunately the political minefield is considerable. In the meantime some sort of special knowledge on the part of each gatekeeper is assumed. Regards, Chris -- Dr Chris Purvis - Senior Development Engineer, WAVE CC Software Madge Networks Ltd, Wexham Springs, Framewood Road, Wexham, Berks. Phone:+44 1753 661359 email: cpurvis(a)madge.com

1 0

Re: H.225.0 Annex G
by William Pimentel 01 Oct '98

01 Oct '98

Glen Freundlich wrote: > I have uploaded H.225.0 Annex G into the Incoming directory of the avc > ftp site. The ziped file is annexg.zip, which expands to annexg06.doc. > This is equivalent to TD-61/PLEN plus the modifications requested during > the plenary session. > > Glen > Is this the final and approved text? -- William Pimentel w-piment(a)uniandes.edu.co

2 1

Overlapped Sending and LRQ
by Sarah Lavie 01 Oct '98

01 Oct '98

According to Overlapped Sending recommendation "If there is insufficient addressing information in the ARQ, the Gatekeeper should respond with an ARJ with the AdmissionRejectReason set to incompleteAddress" The main question is how the Overlapped Sending scheme interacts with the LRQ scheme. Here are 2 example scenarios to explain the difficulties: A) overlapped numbering scheme in 2 zones -------> GK1 GK2 dial 1234 / \ / \ T1 = 12345 T2 = 1234 A terminal dials "1234". GK1 identifies the address as incomplete and sends ARJ. However, the caller wished to call terminal 2 and therefore the address was complete and GK1 should have sent LRQ. A.1 In this case, Does the terminal should send ARQ again? Does the last ARJ terminates the call in the caller side? A.2 Should the re-sending of the ARQ (if exist) be the trigger for sending the LRQ, from the GK point of view? B) Location Request mechanism does not support overlapped sending ----> GK1 ---> GK2 dial 1234 LRQ \ \ T2 = 12345 A terminal dials "1234" as part of the digit collection. GK1 somehow recognizes that the address should be referred to GK2. However GK2 returns an LRJ because the LRQ mechanism does not support overlapped sending. It seems to me that the Overlapped Sending should be deployed in systems where the numbering scheme is unified and predefined by zones, as it is in the telephony systems. In this case, LRQ should not be deployed. Am I right in this assumption? If not, what should be the guidelines for sending LRQ when Overlapped Sending mode is on. Regards, ============================== Sarah Lavie RadVision sarah(a)radvision.rad.co.il ==============================

1 0

Re: H.332 uploaded into the Incoming directory of the avc ftp site
by Spencer Hu 30 Sep '98

30 Sep '98

Spencer Hu@GDC 09/30/98 07:26 AM DO YOU HAVE A WEB ADDRESS, PLEASE? SPENCER ------ "Kumar, Vineet" <vineet.kumar(a)intel.com> on 09/29/98 05:53:30 PM Please respond to Mailing list for parties associated with ITU-T Study Group 16 <ITU-SG16(a)mailbag.cps.intel.com> To: ITU-SG16(a)mailbag.cps.intel.com cc: (bcc: Spencer Hu/Engineering/GDC/US) Subject: H.332 uploaded into the Incoming directory of the avc ftp site I have uploaded the decided version of H.332 (h332.doc) and the approved version of the Implementers Gudie (h323ImplGuide.doc) into the Incoming directory of the avc ftp site. vineet --------------------------------------------------------------------------- - -------------------------- Vineet Kumar vineet.kumar(a)intel.com Intel Corporation, JF3-212 (+1) 503-264-3439 (phone) Hillsboro, OR 97124-5961 (+1) 503-264-3375 (fax) --------------------------------------------------------------------------- - --------------------------

1 0

H.332 uploaded into the Incoming directory of the avc ftp site
by Kumar, Vineet 29 Sep '98

29 Sep '98

I have uploaded the decided version of H.332 (h332.doc) and the approved version of the Implementers Gudie (h323ImplGuide.doc) into the Incoming directory of the avc ftp site. vineet ---------------------------------------------------------------------------- -------------------------- Vineet Kumar vineet.kumar(a)intel.com Intel Corporation, JF3-212 (+1) 503-264-3439 (phone) Hillsboro, OR 97124-5961 (+1) 503-264-3375 (fax) ---------------------------------------------------------------------------- --------------------------

1 0

Determined H.450.x documents uploaded to pictel ftp site
by Klaghofer, Karl PN VS LP3 29 Sep '98

29 Sep '98

I have uploaded the following determined documents to the Incoming directory of the pictel ftp site (ftp://standard.pictel.com/avc-site/Incoming/) - H.450.4 Call Hold Supplementary Service for H.323 - H.450.5 Call Park and Call Pickup Supplementary Services for H.323 - H.450.6 Call Waiting Supplementary Service for H.323 - H.450.7 Message Waiting Indication Supplementary Service for H.323 The file names are H4504.zip (corresponds to TD34PLEN), H4505.zip (i.e. TD35PLEN), H4506.zip (i.e. TD36PLEN) and H4507.zip (TD40PLEN) respectively. Best Regards, Karl ------------------------------------------------ Karl Klaghofer, Siemens AG, Dpmt. PN VS LP3 Hofmannstr. 51, D-81359 Munich, Germany Tel.: +49 89 722 31488, Fax.: +49 89 722 37629 e-mail: karl.klaghofer(a)vs.siemens.de

1 0

Usage guidelines for ITU-SG16
by L-Soft list server at Intel Corporation (1.8c) 29 Sep '98

29 Sep '98

Subject: Welcome to itu-sg16 (updated 1/6/97) Remember - to POST messages to the list send to: itu-sg16(a)mailbag.jf.intel.com - to interact with listserver.... send to: listserv(a)mailbag.jf.intel.com This reflector has now (as a second step) inherited the members currently registered at the h32z2-list(a)mtgbcs.lucent.com. This was done in a semi-automated fashion using the existing list as input to this one. If you do not desire to be on this list, my apologies - you may unsubscribe by sending a message to the list software at "listserv(a)mailbag.jf.intel.com" with the body set to signoff itu-g16 In addition it is requested, that contact information be provided so that the current list of correspondents on this list be provided to ITU-TSB if so requested. [Full Name] [Organization] [contact number] Please send this information in the body of a message to 'jtoga(a)ibeam.intel.com', set the "subject" of the mail to "SG16 Contact". Listed below are some hints on interacting with this mailing list: **************************************************************************** ************** mail reflector: (sent to listserv(a)mailbag.jf.intel.com) Subscribe: BODY of the text set to subscribe itu-sg16 <your email address> <your name> Unsubscribe: signoff itu-g16 You can get more information on commands by sending a message with the body of the message containing either 'help' or 'info' to: listserv(a)mailbag.jf.intel.com List Digests: If you feel like you lost some list messages or simply want to get a chronological chunk of them, you can do so. send a message to "listserv(a)mailbag.jf.intel.com" with the body of the message index itu-sg16 This will get you a list of all the digest files. After choosing which files you want, send another message to "listserv(a)mailbag.jf.intel.com" with the body of the message get itu-sg16 [filename] Finally you may always contact me (via any of the methods in my signature) with any questions. jimt. ************************************************************************* *** 503.264.8816(voice) 503.264.3485(fax) *** *** jtoga(a)ibeam.intel.com Intel - Hillsboro, OR. *** *************************************************************************

1 0

You are now subscribed to the ITU-SG16 list
by L-Soft list server at Intel Corporation (1.8c) 29 Sep '98

29 Sep '98

Tue, 29 Sep 1998 06:48:32 Your subscription to the ITU-SG16 list (Mailing list for parties associated with ITU-T Study Group 16) has been accepted. Please save this message for future reference, especially if this is the first time you subscribe to an electronic mailing list. If you ever need to leave the list, you will find the necessary instructions below. Perhaps more importantly, saving a copy of this message (and of all future subscription notices from other mailing lists) in a special mail folder will give you instant access to the list of mailing lists that you are subscribed to. This may prove very useful the next time you go on vacation and need to leave the lists temporarily so as not to fill up your mailbox while you are away! You should also save the "welcome messages" from the list owners that you will occasionally receive after subscribing to a new list. To send a message to all the people currently subscribed to the list, just send mail to ITU-SG16(a)MAILBAG.INTEL.COM. This is called "sending mail to the list", because you send mail to a single address and LISTSERV makes copies for all the people who have subscribed. This address (ITU-SG16(a)MAILBAG.INTEL.COM) is also called the "list address". You must never try to send any command to that address, as it would be distributed to all the people who have subscribed. All commands must be sent to the "LISTSERV address", LISTSERV(a)MAILBAG.INTEL.COM. It is very important to understand the difference between the two, but fortunately it is not complicated. The LISTSERV address is like a FAX number that connects you to a machine, whereas the list address is like a normal voice line connecting you to a person. If you make a mistake and dial the FAX number when you wanted to talk to someone on the phone, you will quickly realize that you used the wrong number and call again. No harm will have been done. If on the other hand you accidentally make your FAX call someone's voice line, the person receiving the call will be inconvenienced, especially if your FAX then re-dials every 5 minutes. The fact that most people will eventually connect the FAX machine to the voice line to allow the FAX to go through and make the calls stop does not mean that you should continue to send FAXes to the voice number. People would just get mad at you. It works pretty much the same way with mailing lists, with the difference that you are calling hundreds or thousands of people at the same time, and consequently you can expect a lot of people to get upset if you consistently send commands to the list address. You may leave the list at any time by sending a "SIGNOFF ITU-SG16" command to LISTSERV(a)MAILBAG.INTEL.COM. You can also tell LISTSERV how you want it to confirm the receipt of messages you send to the list. If you do not trust the system, send a "SET ITU-SG16 REPRO" command and LISTSERV will send you a copy of your own messages, so that you can see that the message was distributed and did not get damaged on the way. After a while you may find that this is getting annoying, especially if your mail program does not tell you that the message is from you when it informs you that new mail has arrived from ITU-SG16. If you send a "SET ITU-SG16 ACK NOREPRO" command, LISTSERV will mail you a short acknowledgement instead, which will look different in your mailbox directory. With most mail programs you will know immediately that this is an acknowledgement you can read later. Finally, you can turn off acknowledgements completely with "SET ITU-SG16 NOACK NOREPRO". Following instructions from the list owner, your subscription options have been set to "REPRO MIME" rather than the usual LISTSERV defaults. For more information about subscription options, send a "QUERY ITU-SG16" command to LISTSERV(a)MAILBAG.INTEL.COM. Contributions sent to this list are automatically archived. You can get a list of the available archive files by sending an "INDEX ITU-SG16" command to LISTSERV(a)MAILBAG.INTEL.COM. You can then order these files with a "GET ITU-SG16 LOGxxxx" command, or using LISTSERV's database search facilities. Send an "INFO DATABASE" command for more information on the latter. This list is available in digest form. If you wish to receive the digested version of the postings, just issue a SET ITU-SG16 DIGEST command. More information on LISTSERV commands can be found in the LISTSERV reference card, which you can retrieve by sending an "INFO REFCARD" command to LISTSERV(a)MAILBAG.INTEL.COM.

1 0

Re: decided version of H.323 Annex D is now in the Incoming direc tory of the avc-site
by Rahul Chopra 28 Sep '98

28 Sep '98

Vineet: Wanted to know where the avc-site was? Would appeciate it. Thanks. Rahul > -----Original Message----- > From: Kumar, Vineet [SMTP:vineet.kumar@INTEL.COM] > Sent: Monday, September 28, 1998 5:18 PM > To: ITU-SG16(a)mailbag.cps.intel.com > Subject: decided version of H.323 Annex D is now in the Incoming > directory of the avc-site > > The decided version of H.323 Annex D is now in the Incoming directory of > the > avc-site. Is there a new directory where all the decided and determined > documents need to be uploaded ? > > vineet > -------------------------------------------------------------------------- > -- > -------------------------- > Vineet Kumar vineet.kumar(a)intel.com > Intel Corporation, JF3-212 (+1) 503-264-3439 > (phone) > Hillsboro, OR 97124-5961 (+1) 503-264-3375 > (fax) > -------------------------------------------------------------------------- > -- > --------------------------

1 0

Re: Draft H.323 Annexes E and F uploaded
by Alexandre Chatilov 28 Sep '98

28 Sep '98

ftp://standard.pictel.com/avc-site/Incoming/ -----Original Message----- From: Rahul Chopra [mailto:rchopra@NETSPEAK.COM] Sent: Monday, September 28, 1998 2:51 PM To: ITU-SG16(a)MAILBAG.INTEL.COM Subject: Re: Draft H.323 Annexes E and F uploaded Joerg: Where is the avc-site? Would apprecate a pointer Thanks. Rahul > -----Original Message----- > From: Joerg Ott [SMTP:jo@INFORMATIK.UNI-BREMEN.DE] > Sent: Monday, September 28, 1998 5:35 PM > To: ITU-SG16(a)mailbag.cps.intel.com > Subject: Draft H.323 Annexes E and F uploaded > > Folks, > > I have uploaded the determined documents H.323 Annex E and > H.323 Annex F into the Incoming directory of the AVC ftp site. > The file names are: > > H323-AnnexE-4.02.doc (equivalent to TD-47/PLEN) > H323-AnnexF-03.doc (equivalent to TD-51/PLEN) > > Joerg

1 0

Re: Draft H.323 Annexes E and F uploaded
by Rahul Chopra 28 Sep '98

28 Sep '98

Joerg: Where is the avc-site? Would apprecate a pointer Thanks. Rahul > -----Original Message----- > From: Joerg Ott [SMTP:jo@INFORMATIK.UNI-BREMEN.DE] > Sent: Monday, September 28, 1998 5:35 PM > To: ITU-SG16(a)mailbag.cps.intel.com > Subject: Draft H.323 Annexes E and F uploaded > > Folks, > > I have uploaded the determined documents H.323 Annex E and > H.323 Annex F into the Incoming directory of the AVC ftp site. > The file names are: > > H323-AnnexE-4.02.doc (equivalent to TD-47/PLEN) > H323-AnnexF-03.doc (equivalent to TD-51/PLEN) > > Joerg

1 0

Draft H.323 Annexes E and F uploaded
by Joerg Ott 28 Sep '98

28 Sep '98

Folks, I have uploaded the determined documents H.323 Annex E and H.323 Annex F into the Incoming directory of the AVC ftp site. The file names are: H323-AnnexE-4.02.doc (equivalent to TD-47/PLEN) H323-AnnexF-03.doc (equivalent to TD-51/PLEN) Joerg

1 0