- sg16-avd - lists.packetizer.com

several gatekeepers
by Wolfgang Bandow 04 Jul '00

04 Jul '00

Hello H.323-Experts, in connection with H.323 based IP-telephony in a PISN environment we came across the question whether it is permitted to have more than two Gatekeepers involved in a point to point H.323 connection. Is this in line with H.323 conventions? >From my point of view this situation also occurs in case of a call transfer, if the endpoints are located in different zones and the gatekeeper routed model is used. Is this correct? Thanks a lot in advance for your answer. Regards, Wolfgang Bandow CT-B / Berlin ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)mailbag.intel.com

2 1

Re: several gatekeepers
by Agboh, Charles 04 Jul '00

04 Jul '00

I was just kidding... Let me elaborate Both endpoints could be registered to different gatekeepers (different zones)each using the GRC model. Note that either gatekeeper could choose to use the DRC model. In this case, the gatekeeper using the DRC model would not be involved in the call signaling (Q.931 of H.225) and call control signaling (H.245) but would be receiving/sending service control signaling (RAS: IRR/IRG, ARQ/ACF, RRQ/RCF,DRQ/DCF...). In the DRC case it is a little difficult to provide some supplementary services independant of H.450.X. In the case of call transfer, the called party transfers the call to another endpoint sitting behind a GRC gatekeeper. In short, your assumption is correct. charles -----Original Message----- From: Wolfgang Bandow [mailto:wolfgang.bandow@DETEWE.DE] Sent: Tuesday, July 04, 2000 11:02 AM To: ITU-SG16(a)MAILBAG.INTEL.COM Subject: several gatekeepers Hello H.323-Experts, in connection with H.323 based IP-telephony in a PISN environment we came across the question whether it is permitted to have more than two Gatekeepers involved in a point to point H.323 connection. Is this in line with H.323 conventions? >From my point of view this situation also occurs in case of a call transfer, if the endpoints are located in different zones and the gatekeeper routed model is used. Is this correct? Thanks a lot in advance for your answer. Regards, Wolfgang Bandow CT-B / Berlin ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 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

Re: several gatekeepers
by Agboh, Charles 04 Jul '00

04 Jul '00

yes -----Original Message----- From: Wolfgang Bandow [mailto:wolfgang.bandow@DETEWE.DE] Sent: Tuesday, July 04, 2000 11:02 AM To: ITU-SG16(a)MAILBAG.INTEL.COM Subject: several gatekeepers Hello H.323-Experts, in connection with H.323 based IP-telephony in a PISN environment we came across the question whether it is permitted to have more than two Gatekeepers involved in a point to point H.323 connection. Is this in line with H.323 conventions? >From my point of view this situation also occurs in case of a call transfer, if the endpoints are located in different zones and the gatekeeper routed model is used. Is this correct? Thanks a lot in advance for your answer. Regards, Wolfgang Bandow CT-B / Berlin ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 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

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

Re: next revision of H.323 Annex H ?
by Jaakko Sundquist 03 Jul '00

03 Jul '00

Vineet et al, I'll try to work on it this week and maybe get it available by Friday. Sorry about the delay, but I had a couple of weeks of holiday and didn't feel like working on Annex H during that time. Furthermore, the mobility discussion seems to have been quite non-existent since Osaka, so I would really appreciate any contributions and/or discussions on the email reflector. -Jaakko > -----Original Message----- > From: EXT Kumar, Vineet [mailto:vineet.kumar@intel.com] > Sent: 21. June 2000 20:04 > To: Jaakko Sundquist (E-mail) > Cc: 'ITU-SG16(a)MAILBAG.INTEL.COM' > Subject: next revision of H.323 Annex H ? > > > Jaakko, > > When is the next revision of H.323 Annex H draft scheduled to > be out ? > > Regards, > vineet > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)mailbag.intel.com

1 0

Deadlines
by Sakae OKUBO 03 Jul '00

03 Jul '00

Dear Q12-14/16 experts, I forgot to mention one thing regarding the meeting notice I just posted at the reflector. This time the deadlines for document registration and uploading are precisely specified as follows: /// Registration of the document: by 23:59 UTC, 11 August /// /// Distribution of the document: by 23:59 UTC, 14 August /// I am not a robot, but will basically manage the documents according to the meeting notice. 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

Notice of the Portland meeting in August 2000
by Sakae OKUBO 03 Jul '00

03 Jul '00

Dear Q12-14/16 experts, Please find attached the notice of the Portland meeting during 21-25 August 2000 as well as the logistic information from the host, Intel. The two files are also placed at the PictureTel ftp site: http://standard.pictel.com/ftp/avc-site/0008_Por/Notice_ITU-T_Portland.txt http://standard.pictel.com/ftp/avc-site/0008_Por/PortlandInfoPack.zip Please note that you are required to send your participation registration and hotel room reservation by 7 August 2000. 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 *********************************************************** To Experts of ITU-T SG16 Q.12/16, Q.13/16 and Q.14/16 Cc Mr. P-A. Probst, Chairman of SG16 Mr. G. Helder, Vice-Chairman of SG16 Mr. F. Tosco, Chairman of WP2/16 Mr. F. Bigi, ITU-TSB Mr. T. Geary, Rapporteur for Q.11/16 Mr. G. Sullivan, Rapporteur for Q.15/16 Mr. G. Meyer, Intel De Sakae OKUBO Rapporteur for Q.12/16 in ITU-T SG16 TAO Waseda Research Center 5th Floor, Nishi-Waseda Bldg. 1-21-1 Nishi-Waseda, Shinjuku-ku, Tokyo 169-0051 Japan Tel: +81 3 3204 8194 Fax: +81 3 5287 7287 E-mail: okubo(a)giti.or.jp Dale SKRAN Rapporteur for Q.13/16 in ITU-T SG16 Sonus Networks 4400 Route 9 South Suite 1000 Freehold, NJ 07748 USA Tel: +1 732 409 5107 Fax: +1 732 409 5172 E-mail: dskran(a)sonusnet.com Glen FREUNDLICH Rapporteur for Q.14/16 in ITU-T SG16 Lucent Technologies 11900 N. Pecos Westminster, Colorado 80234 USA Tel: +1 303 538 2899 Fax: +1 303 538 3907 E-mail: ggf(a)lucent.com ------------------------------------------------------------ Subject: Notice of Q.12-14/16 Rapporteur Meeting in Portland Date: 3 July 2000 ------------------------------------------------------------ Dear Q.12-14/16 experts, The subject meeting of ITU-T SG16 experts will be held in Portland, USA at the kind invitation of Intel Corporation. Please note that Q.11/16 and Q.15/16 will meet concurrently at the same place and have joint session(s) with Q.12-14/16. 1. Date ^^^^^^^ 21 (Monday) - 25 (Friday) August 2000 starting at 9:00 on the first day closing at 18:00 on the final day 2. Venue ^^^^^^^^ The Resort At The Mountain 68010 East Fairway Welches, OR 97067 Tel: +1-503-662-3101 (for messages) 3. Topics (tentative) ^^^^^^^^^^^^^^^^^^^^^ 1) Review of the relevant group meetings 2) Q.12/16 B-ISDN multimedia systems and terminals - Work with Q.13 on high quality video transmission over IP - Future AV communication systems 3) Q.13/16 Packet switched multimedia systems and terminals - Toward determination in November: * H.323 Annex H (User, Service, and Terminal Mobility in H.323) * H.323 Annex I (Packet based MM Telephony over Error Prone Channels) * H.450.10 (Call Offer Supplementary Services) * H.450.11 (Call Intrusion) * H.450.12 (Common Information Additional Network) * H.225.0 Annex G V2 (Inter-domain) * H.323 Annex R (Robustness) * H.323 Annex M.3 (DSS1 Tunneling) * H.323 Annex E V2 (UDP call signaling) - Progress work for: * H.323 Annex N (QoS) * H.323 Annex O (Internet protocols and technologies complementary to H.323) * Other new items that may arise 4) Q.14/16 Common protocols, MCUs and protocols for interworking with H.300-series terminals - Toward determination in November: * H.248 Annex L * H.248 Annex M * H.235 V8 - Progress work for: * H.246 Annex D * H.248 V2 * H.341 V2 * other new items that may arise (e.g., new packages for H.248) 5) Coordination with Q.11/16 and Q.15/16 - System aspects - Video coding aspects 6) Interaction with other groups 7) Future work plan 4. Documents ^^^^^^^^^^^^ /// Registration of the document: by 23:59 UTC, 11 August /// /// Distribution of the document: by 23:59 UTC, 14 August /// /// Use the ftp site (or e-mail reflector) for distribution /// 1) When you are going to submit a document, please notify S. Okubo as soon as possible, by 23:59 UTC, Friday 11 August at the latest. Document number (APC-nnnn) will be allocated. Early indication of your submission plan is welcome and encouraged. Note - Prefix "APC" comes from Atm (Q.12/16), Packet based (Q.13/16) and Common protocols (Q.14/16) based on the coordination with Q.1 ("Q1City"), Q.3 ("T120"), Q.11 ("Q11"), Q.15 ("Q15") groups. 2) You are advised to include a header as follows: ------------------------------------------------------------------ | | | ITU Telecommunication Standardization Sector Document APC-{nnnn}| | Study Group 16 {Version m if relevant}| | Q.12-14/16 Rapporteur Meeting {Date}| | Portland, 21-25 August 2000 | | | | SOURCE*: { } | | TITLE : { } | | PURPOSE: {Proposal, Discussion, Information, Report, etc.} | | | | _________________________ | | | | | | | | *Contact: Name, e-mail | ------------------------------------------------------------------ 3) All the contributors are requested to distribute their documents as early as possible, at least 7 calendar days in advance of the meeting (23:59 UTC, Monday 14 August or before) by posting them at either of the following: - PictureTel ftp site (please advise S. Okubo of your posting) Site: standard.pictel.com/avc-site Login name: anonymous Directory: Incoming - Q.12-14/16 experts reflector e-mail address: itu-sg16(a)mailbag.intel.com Please avoid the use of reflector when your document is voluminous. 4) Input documents can be retrieved from /0008_Por directory of the ftp site. 5) The document distribution / presentation at the meeting will be all electronic. Participants must bring along their laptop, 10BASE-T card and cord, and optionally wireless LAN card (please follow the host's advice). 6) The copying service is very limited and expensive at the meeting site. 5. Logistic information ^^^^^^^^^^^^^^^^^^^^^^^ Please see the attached document provided by the meeting host (http://standard.pictel.com/ftp/avc-site/0008_Por/PortlandInfoPack.zip). 6. Registration ^^^^^^^^^^^^^^^ To register your meeting attendance, please send the attached form to the meeting secretariat by 7 August 2000: Intel Meeting Service ATTN: Valerie Nester Fax: +1 480 554 7775 AND advise Rapporteurs of your attendance by e-mail: To: okubo(a)giti.or.jp, dskran(a)sonusnet.com, ggf(a)lucent.com, tom.geary(a)conexant.com, garysull(a)microsoft.com Subject: Portland meeting registration Name: Company: Arrival: Departure: 7. Hotel Room Reservation ^^^^^^^^^^^^^^^^^^^^^^^^^ Please send the attached form to the meeting secretariat together with the meeting registration. Special package room rate is $149.18 (single or double occupancy) per night including breakfast, tax and gratuity. The block reservation is held until 7 August. We are looking forward to meeting with you in Portland. Sincerely yours, Sakae OKUBO Dale SKRAN Glen FREUNDLICH ----------

1 0

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