June 2000 - sg16-avd - lists.packetizer.com

Voice Signal Level in H323 Terminal/Gateway
by Shan Lu 03 Jul '00

03 Jul '00

Hi, I'd like to start a discussion on how to set speech signal level in an H323 environment. Speech signal level is an important part of QoS. It directly impacts end user's perception of how good the system works. It is also an integral part of interoperability testing. After the interoperability issues at the protocol level have been ironed out, the signal levels from different vendors have to "match" in order to provide true interoperability for end users. Some vendors make speech signal level a configurable parameter in their equipment and leave it to end user to decide. However, not all end users are capable of making intelligent decisions on this issue. When signal levels are set improperly, end users will complain about low volume, high volume, and/or echo. If the system consists of equipment from multiple vendors or involves interworking with PSTN/PBX, things can become complicated quickly. So a set of guidelines on how to determine speech level can benefit equipment manufacturers as well as their customers, including end users and service providers. I envision the guidelines should cover a number of topics: 1. desired end-end signal attenuation and acceptable range; 2. desired place of attenuation (tx or rx?) and how much; 3. desired level for DTMF and tones 4. desired level of echo cancellation; 5. connection scenarios: terminal-terminal, terminal-gateway, and gateway-gateway. Issues that we have to contend with include: end user acceptance, voice coder and echo cancellor optimal operation ranges, idle noise levels. For many of these issues, we can draw upon the wealth body of knowledge from the telephony world. Some of them may only take a reference to an existing standard. Others may require some serious thinking and, more importantly, agreement among multiple vendors. The discussion certainly is not restricted to voice only applications. But I am not sure if video has an interoperability issue as serious as voice. I am open to any suggestions. We may continue the discussion online or we can discuss face to face at SuperOp next week. Now here is my question #1: Is SourceInfo/DestinationInfo structure in H225 call setup messages a reliable way to distinguish end point type (terminal, gateway, gk)? What if in a GK-routed call? Does the GK modify that field? Thanks, Shan Lu NexTone Communications, Inc 9700 Great Seneca Highway Rockville, MD 20850 +1 240-453-6315 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)mailbag.intel.com

2 1

H.245 White paper uploaded to server
by Mike Nilsson 30 Jun '00

30 Jun '00

I have submitted the H.245 White Paper to the ITU and have uploaded it to ftp://standard.pictel.com/avc-site/Incoming/h245_n.zip (Mr Okubo will move this in due course). Best regards Mike -------------------- Mike Nilsson Internet and Multimedia Applications B81 Room 102 pp14 BT Advanced Communications Technology Centre Adastral Park, Martlesham Heath, Ipswich, IP5 3RE, UK Tel: +44 1473 645413 Mobile: +44 7808 635412 Fax: +44 1473 646589 Email: mike.nilsson(a)bt.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)mailbag.intel.com

2 1

H.323 URL
by Orit Levin 30 Jun '00

30 Jun '00

Hi Paul and all the others! This is my attempt to articulate the H323-URL motivation and use in the shortest way. I don't have any problem with expanding or/and tightening the definition of the H.323 URL. I think we should incorporate the real syntax corrections now. Nevertheless, I would prefer to decide a BASIC H323-URL in a way which makes it possible for later backwards compatible modifications. I addition to that, I think that comments (4) and (5) from TD-40a should appear in the decided document. Regards, Orit Levin RADVision Inc. 575 Corporate Drive Suite 420 Mahwah, NJ 07430 Tel: 1 201 529 4300 (230) Fax: 1 201 529 3516 www.radvision.com orit(a)radvision.com -----Original Message----- From: Michael Welser <michael.welser(a)AON.AT> To: ITU-SG16(a)MAILBAG.INTEL.COM <ITU-SG16(a)MAILBAG.INTEL.COM> Date: Friday, June 30, 2000 5:43 AM Subject: Re: H.323 URL Text >I propose to change the ABNF to the following: > > H323-URL = "H323:" user [ "@" hostport ] > user = 1*( unreserved / escaped ) > hostport = host [":" port] > host = hostname / IPv4address / IPv6reference > hostname = *( domainlabel "." ) toplabel [ "." ] > domainlabel = alphanum / alphanum *( alphanum / "-" ) alphanum > toplabel = ALPHA / ALPHA *( alphanum / "-" ) alphanum > IPv6reference = "[" IPv6address "]" > IPv6address = hexpart [ ":" IPv4address ] > IPv4address = 1*3DIGIT "." 1*3DIGIT "." 1*3DIGIT "." 1*3DIGIT > IPv6prefix = hexpart "/" 1*2DIGIT > hexpart = hexseq | hexseq "::" [ hexseq ] | "::" [ hexseq ] > hexseq = hex4 *( ":" hex4) > hex4 = 1*4HEXDIG > port = 1*DIGIT > unreserved = alphanum / mark > alphanum = ALPHA / DIGIT > mark = "-" / "_" / "." / "!" / "~" / "*" / "'" > / "(" / ")" / "&" / "=" / "+" / "$" / "," > escaped = "%" HEXDIG HEXDIG > >This introduces IPv6 adresses according to RFCs 2732, 2373 and 2396. The >ABNF still relies on RFC 2234. > >It also corrects the IPv4 address by limiting each segment to three >digits. > >I am not too sure about the 'port'. Although 1*DIGIT makes absolutely >sense, most schemes currently in use are more relaxed about it and just >do a DIGIT. > >I am also not too sure about the extended user definition and the >password extension which are used e.g. in SIP and HTTP: > > H323-URL = "H323:" userinfo [ "@" hostport ] > userinfo = user [ ":" password ] > user = *( unreserved / escaped > / "&" / "=" / "+" / "$" / "," ) > password = *( unreserved | escaped > / "&" / "=" / "+" / "$" / "," ) > etc. > >Could we need that? > >Cheers, > >Michael >(welser(a)acm.org) > >> -----Original Message----- >> From: Mailing list for parties associated with ITU-T Study Group 16 >> [mailto:ITU-SG16@mailbag.cps.intel.com]On Behalf Of Paul E. Jones >> Sent: Monday, June 26, 2000 12:23 PM >> To: ITU-SG16(a)mailbag.cps.intel.com >> Subject: H.323 URL Text >> >> >> Folks, >> >> I have attached the text that I propose adding to the H.323v4 document >> relating to the H.323 URL scheme. I think this text is weak, >> but I expect >> contributions to be brought to define the usage of this >> scheme-- presently, >> there really is no procedural text. >> >> I'd like to point out that I removed the telephone number >> portions of the >> URL, which should make both Orit and Bob happy :-) >> >> Please review the text and the ABNF grammar for errors. You >> will note one >> small bit of procedural text near the end where it discusses >> the fact that a >> Gatekeeper may modify the alias provided to the Gatekeeper. >> The substance >> of that existed in TD-50 (Osaka) and I thought that it was >> important to go >> ahead and include that at the very least. >> >> Please, give me feedback. Mr. Bowen and I plan to post H.323v4 and >> H.225.0v4 this week for review. A formal announcement will >> be made later >> today or tomorrow. >> >> Best Regards, >> Paul >> > >~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >For help on this mail list, send "HELP ITU-SG16" in a message to >listserv(a)mailbag.intel.com

2 1

Re: Draft versions of H.323v4, H.225.0v4, H.323v4 Annex D, and th e Implementers Guide ready for review
by <Morgan Potter> 30 Jun '00

30 Jun '00

Pete, I tried to contact you today. If you are in next week, we had better touch base with the TD 50 issues. M. > -----Original Message----- > From: Paul E. Jones [SMTP:paulej@PACKETIZER.COM] > Sent: Friday, June 30, 2000 11:42 AM > To: ITU-SG16(a)MAILBAG.INTEL.COM > Subject: Draft versions of H.323v4, H.225.0v4, H.323v4 Annex D, and > the Implementers Guide ready for review > > Folks, > > At long last, Rich Bowen and I have been able to complete the initial > editing work for the H.323v4 and H.225.0v4 documents. I believe that most > of the work is behind us, but I want everybody to review these documents > before we finish the final edits and present them to the TSB. The only > editing work that remains (at least in H.323v4 and Annex D) are minor > editorial issues. > > Please post comments to the ITU-T SG16 mailing list with the subject > prefix > "[V4]". Also, I'd like to schedule a conference call for interested > parties > on Friday, July 7 at 11AM U.S. Eastern Time (GMT - 5). If you are > interested in going through the documents, please contact me before that > date and we'll set up a conference bridge for the right number of people > and > go through an issues. > > http://www.packetizer.com/iptel/h323/drafts/h225v4h_wp_draft.zip > http://www.packetizer.com/iptel/h323/drafts/h323v4.zip > http://www.packetizer.com/iptel/h323/drafts/H323_annex_d.zip > > I have one open issue that I definitely want to resolve before the white > paper is produced, although we could wait if we absolutely had to-- it is > an > issue that affects H.323v3, too, and is detailed at the top of the H.323v4 > document. I consider it significant as H.323v3 and H.323v2 > interoperability > is currently impaired. > > If you have any questions, please feel free to contact me. Once we get > the > initial review complete, we will complete the edits and send them to the > TSB. > > I also have a complete up to date Implementers Guide for H.323v3: > http://www.packetizer.com/iptel/h323/drafts/H.323v3_ig.zip > > Comments are certainly welcome, but it is not necessary to review that > document immediately. > > Best Regards, > Paul E. Jones > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > For help on this mail list, send "HELP ITU-SG16" in a message to > listserv(a)mailbag.intel.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)mailbag.intel.com

1 0

Draft versions of H.323v4, H.225.0v4, H.323v4 Annex D, and the Implementers Guide ready for review
by Paul E. Jones 30 Jun '00

30 Jun '00

Folks, At long last, Rich Bowen and I have been able to complete the initial editing work for the H.323v4 and H.225.0v4 documents. I believe that most of the work is behind us, but I want everybody to review these documents before we finish the final edits and present them to the TSB. The only editing work that remains (at least in H.323v4 and Annex D) are minor editorial issues. Please post comments to the ITU-T SG16 mailing list with the subject prefix "[V4]". Also, I'd like to schedule a conference call for interested parties on Friday, July 7 at 11AM U.S. Eastern Time (GMT - 5). If you are interested in going through the documents, please contact me before that date and we'll set up a conference bridge for the right number of people and go through an issues. http://www.packetizer.com/iptel/h323/drafts/h225v4h_wp_draft.zip http://www.packetizer.com/iptel/h323/drafts/h323v4.zip http://www.packetizer.com/iptel/h323/drafts/H323_annex_d.zip I have one open issue that I definitely want to resolve before the white paper is produced, although we could wait if we absolutely had to-- it is an issue that affects H.323v3, too, and is detailed at the top of the H.323v4 document. I consider it significant as H.323v3 and H.323v2 interoperability is currently impaired. If you have any questions, please feel free to contact me. Once we get the initial review complete, we will complete the edits and send them to the TSB. I also have a complete up to date Implementers Guide for H.323v3: http://www.packetizer.com/iptel/h323/drafts/H.323v3_ig.zip Comments are certainly welcome, but it is not necessary to review that document immediately. Best Regards, Paul E. Jones ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)mailbag.intel.com

1 0

upload of H.235v2 white contribution
by Euchner Martin 30 Jun '00

30 Jun '00

The H.235v2 white paper has been uploaded to the incoming directory of the avc-site. After the document has been moved, you will find it in the 0011_Gen directory. Changes since the Osaka Meeting: * Figures added clarifying use of the challenge-response procedures. * Minor editorial cleanup. Kind regards Martin Euchner. ----------------------------------------------------------------------- | Dipl.-Inf. Phone: +49 89 636-46201 | Martin Euchner Fax : +49 89 636-48000 | Siemens AG | ZT IK 3 mailto:Martin.Euchner@mchp.siemens.de | mailto:martin.euchner@ties.itu.int | Otto-Hahn-Ring 6 Intranet: http://zt-security.mchp.siemens.de/de/Competence/Standardization/ITU-T_SG16/ index.html | D-81730 Muenchen Internet: http://www.siemens.de | __________________ | Germany ----------------------------------------------------------------------- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)mailbag.intel.com

1 0

H.323 URL Text
by Paul E. Jones 30 Jun '00

30 Jun '00

Folks, I have attached the text that I propose adding to the H.323v4 document relating to the H.323 URL scheme. I think this text is weak, but I expect contributions to be brought to define the usage of this scheme-- presently, there really is no procedural text. I'd like to point out that I removed the telephone number portions of the URL, which should make both Orit and Bob happy :-) Please review the text and the ABNF grammar for errors. You will note one small bit of procedural text near the end where it discusses the fact that a Gatekeeper may modify the alias provided to the Gatekeeper. The substance of that existed in TD-50 (Osaka) and I thought that it was important to go ahead and include that at the very least. Please, give me feedback. Mr. Bowen and I plan to post H.323v4 and H.225.0v4 this week for review. A formal announcement will be made later today or tomorrow. Best Regards, Paul

2 1

PV 2001
by PV2001 Secretariat 29 Jun '00

29 Jun '00

<<APOLOGIES TO THOSE WHO RECEIVE THIS EMAIL MORE THAN ONCE.>> Invitation to PV(Packet Video Workshop) 2001 : 30 April - 1 May 2001, Kyongju, Korea The 11th International Packet Video Workshop (PV 2001) will be held on 30 April - 1 May 2001 in Kyongju, Korea, which was the capital city of ancient Korea (A.D 676 - A.D 935), located in 350-kilometer southeast of Seoul. The workshop is devoted to presenting technological advancements and innovations in video transmission over packet networks, in particular, the Internet. Packet Video Workshop has been unique in providing a common ground for people from video coding and networking fields. Presentations on theory and practice, standards activities, and business and consumer applications are encouraged. In 2001, the workshop is scheduled to take place in the week following Picture Coding Symposium (PCS 2001) which will be held in Seoul, Korea on 25-27 April 2001 (http://pcs.kaist.ac.kr). We cordially invite you take part in this workshop by submitting your work. Important due date: November 15, 2000: Paper submission January 31, 2001: Notice of acceptance March 15, 2001: Final paper delivery For more information about PV 2001 and the conference city, kyongju, please check the attached file as well as the web site of http://pv2001.kaist.ac.kr. Best regards, Jae-kyoon Kim, General Chair

1 0

Re: liaisons for August Q12-14 meeting
by Sakae OKUBO 23 Jun '00

23 Jun '00

Dear Mr. Freundlich, APC numbers have been allocated as follows: >We have received two liaisons from SG11 that we should cover during the >August meeting in Portland: APC-1872 >"Liaison to SG16 On Interaction Between Intelligent Network Systems and >H.248" from Q22/11 APC-1873 >"Liaison to SG16 On Interworking Between H.323 Systems and Intelligent >Network Systems" from Q22/11 Best regards, Sakae OKUBO *********************************************************** 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 (to be transferred) +81 3 3204 8194 (direct) Fax: +81 3 5287 7287 e-mail: okubo(a)giti.or.jp *********************************************************** ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)mailbag.intel.com

1 0

upload of white draft for Annex K
by Espen Skj�ran 23 Jun '00

23 Jun '00

Hi all, I've uploaded a draft of H.323 Annex K to ftp://standard.pictel.com/avc-site/Incoming/h323-annexK-white.zip Changes since Osaka: - Removed section K.3.3 (the callto: scheme) and inserted text that h323-urls should be handled locally by the h.323 endpoint. - Removed references to WAP, XML, and CPL. All CPL descriptions are made more generic with "call processing scripts". I saw Chip's mail about the less need for justification of informative references, but this seemed the most reasonable thing to do. I intend to submit this document by July 1st. Espen ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)mailbag.intel.com

1 0