- sg16-avd - lists.packetizer.com

Informations for the attendees to the Torino meeting
by Tosco Federico 12 Nov '98

12 Nov '98

ÐÏà¡±á>þÿ 02þÿÿÿ/ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿì¥ÁY¿bjbjóWóW*,==ÿÿÿÿÿÿ]úúúúúúú$oîRRRRR---4666666$]ôQŒZú-----Z_úúRRÛR___-úRúR4úúúú-4_Þ_=þH Ôúú4R>à.¶YŸC ITU Meeting Turin, November 17th- 20th, 1998 GENERAL INFORMATION ABOUT THE MEETING CSELT is pleased to welcome you to the Experts Meeting on Questions 11-14/16. This document contains logistic information about the meetings set-up and some general information about our site and the facilities that we will be providing throughout the meeting. THE MEETING VENUE The meeting will take place in 3 places: The Auditorium (Level -1, Building A) The Manzoni Room (2nd Floor, Building A) The MR Room (3rd Floor, Building I) All Plenary sessions will take place in the Auditorium. Participants dealing with Questions 12, 13 and 14 will mainly be working in the Auditorium. The Manzoni room will be a breakout room and participants dealing with Question 11 will meet in the MR room. These details may of course vary according to the agenda. Details shall be posted outside the meeting rooms. II. MEETING SUPPORT When you enter the CSELT premises from the Via G. Reiss Romoli n. 274 entrance, you will find signs to the Auditorium. CSELT staff will be in the Auditorium foyer area to register you and give you a participants badge (from 8:30 AM to 9:30 AM). For security reasons, we would be extremely grateful if you could kindly keep this badge with you at all times, and exhibit it to security personnel upon request. The registration desk will be staffed during the hours mentioned above. However, assistance is only a phone-call away as we have set up a meeting helpline that will be active during the entire course of the meeting. Should you require any kind of information or assistance, whether technical or logistical, please call 0335462567 and we will be pleased to do our best to help. The number will be active from 8:30 AM to 6:30 PM. The telephones you can call from are located in the following areas: Auditorium: at the reception desk Manzoni: in the reception area outside the meeting room MR Room: please refer to the office opposite the meeting room (office number I4226). N.B. Please dial 0 before dialling the number. SERVICES The cloakroom is located in the Auditorium foyer. Staff will direct you to it when you register. Coffee breaks will take place at the bar in the Auditorium foyer. Lunch will take place at 1:15 PM in the CSELT canteen. Each participant will be issued with lunch tickets for all 4 days upon registration on Tuesday morning. CSELT staff will be waiting in the Auditorium foyer at 1:00 PM to show you the way to the canteen. It is self-service, and serves a wide range of hot and cold food. Once you have chosen your meal please go to the tills and give the attendant your voucher. The water fountains are located opposite the tills. You may take a seat at any of the tables. The canteen stops serving food at 1:30 PM. It is therefore important that participants get there by 1:15. TECHNICAL FACILITIES LAN: A local network will be at your disposal throughout the duration of the meeting, both in the Manzoni room and the Auditorium. Technical assistants will be present and detailed instructions will be provided upon request. Printers: Printing facilities will be available in both the Manzoni room and the Auditorium. In the MR room, please refer to office number I4226 (opposite the meeting room). Copiers A copier will be at your disposal in the Auditorium foyer. If you need a large number of copies, please contact the helpline. Additional information: We would like to draw your attention to the Auditoriums seating set-up. This applies exclusively to those participants who will be using their laptop there. Although the seats are mobile, we have alternately fixed seats so that documents, laptops and other items can be left without them closing. Therefore we kindly advise you to sit in the mobile seats. Another reason for this is that there is one LAN attachment for every two seats. VI. GENERAL INFORMATION ABOUT CSELTS VIA REISS ROMOLI SITE How to get here We are located in northern Turin, about a 15-minute drive from Turins Caselle Airport. A taxi from the airport to this site costs around 45.000 Lire. There are no direct public transport services from the airport. However, there is a bus service from the airport terminal to the City Centre that terminates in Corso Inghilterra. The journey takes about 40 minutes (the fare is 6000 Lire). There are public transport services to this site from both of Turins main railway stations (Torino Porta Nuova and Torino Porta Susa). The number 52 bus takes 45-50 minutes from Porta Nuova railway station. The same bus takes 30-40 minutes to reach this site from Porta Susa Railway Station. The bus stops right outside CSELT. Please note that from 9 AM to 2:30 PM the 52 bus does not stop on Via Reiss Romoli because it takes a different route. During these hours we advise you to ask the bus driver to let you know when to get off (the bus will stop in an adjacent street and to get to our site you will need to turn left into Via Reiss Romoli). Alternatively you are advised to take a taxi. The 52 bus runs until 9 PM. A taxi ride from the City Centre takes approximately 20 minutes and should cost around 25.000 Lire. Tickets cannot be purchased onboard buses or trams. You can find them at tobacconists and newsagents or vending machines at certain bus/tram stops at a cost of 1400 Lire. Please note that you cannot buy them near our Via Reiss Romoli site and we therefore advise you to purchase them beforehand. Opening Hours: The Meeting Rooms are open from 8:30 AM to 6:30 PM. The Via Reiss Romoli entrance closes at 6:30 PM. If you need to stay beyond that time please contact the helpline. After 6:30 PM you will need to use the Via Olivetti entrance. Please ask staff for directions to this entrance. !#')YcdvÚÜþ!6acrtýýúöýýööôôñCJ5>*mH mH H*0WXY©abcdvw ¡Çð3 üüõüüüüüòòððüîììüçççüåìììì &F$$Ð$0WXY©abcdvw ¡Çð3 4 á &HÕrµT² !67<=ýýýý÷ôñîèàØÕÓËÈÂŒŽ±®«š¥¢äÿÿÿåÿÿÿ êÿÿÿ ëÿÿÿ çüÿÿèüÿÿéüÿÿêüÿÿëüÿÿUýÿÿ³ýÿÿRÿÿÿ ÿÿÿ öÿÿÿ ÷ÿÿÿ Pÿÿÿtÿÿÿ ÿÿÿ Ãÿÿÿ Äÿÿÿíÿÿÿîÿÿÿ 43 4 á &HÕrµT² !67<=ýýýýýýýýýøýóîîêêýýýýýøýåêã &Fh &F &F &F&'ËÌÍÕÖTUmn$%&bcstÌú12ß\]^mnûóðëæáÙÖÑÎÈÅÂ¿Œ¹¶°ª¥ ôÿÿ³õÿÿŽõÿÿ Ãõÿÿ ÄõÿÿÅõÿÿBöÿÿïöÿÿðöÿÿ'úÿÿUûÿÿûÿÿ®ûÿÿ Ÿûÿÿ ¿ûÿÿûûÿÿüûÿÿýûÿÿ³ýÿÿŽýÿÿ Ìýÿÿ ÍýÿÿKþÿÿLþÿÿTþÿÿ UþÿÿVþÿÿúþÿÿûþÿÿÿÿÿ ÿÿÿ&'ËÌÍÕÖTUmn$%&bcstÌú12ß\]ýøöýýýøöýòíòòòöêêãêêááêêêê$ &F $ &Fh &F]^mnüõüóð$$ &F $(&P °. °ÂA!°"°# $ %°°Â°Â [6@ñÿ6NormaleB*CJOJQJmH :`:Titolo 1$ &F@&>*mHNA@òÿ¡NCarattere predefinito paragrafoHU`¢ñHCollegamento ipertestuale>*B*:B`:Corpo del testo$mH:P`:Corpo del testo 2$FC`"FRientro corpo del testoh ,ÿÿÿÿ3 ]ð8ð@ñÿÿÿ÷ððð0ð( ðÀ ððB ðSð¿Ëÿ ?ðqspqÿÿ **********+C:\temp\AutoRecovery save of ITUHelpDoc.asd **********%C:\WINDOWS\DESKTOP\ITU\ITUHelpDoc.doc **********%C:\WINDOWS\DESKTOP\ITU\ITUHelpDoc.doc **********%C:\WINDOWS\DESKTOP\ITU\ITUHelpDoc.doc **********%C:\WINDOWS\DESKTOP\ITU\ITUHelpDoc.doc **********%C:\WINDOWS\DESKTOP\ITU\ITUHelpDoc.doc **********%C:\WINDOWS\DESKTOP\ITU\ITUHelpDoc.doc **********%C:\WINDOWS\DESKTOP\ITU\ITUHelpDoc.doc **********%C:\WINDOWS\DESKTOP\ITU\ITUHelpDoc.docDonatella BertolottiD:\itu-t\ITUHelpDoc.doc ³Y: ÿ_z~& ÿpv. ÿ7j7¢}ÞùÿÿÿÿÿÿÿÿI*À^ ÿZ f ÿ£yÈl ÿk¹r ÿŽu«| ÿhþÆhOJQJo(·ðhþÆhOJQJo(·ðhþÆhOJQJo(·ðÐ0ýÆÐo(.hþÆhOJQJo(·ðhþÆhOJQJo(·ðhþÆhOJQJo(·ðhþÆhOJQJo(·ðhþÆhOJQJo(·ð Žu«|7j77j74â÷³Y:Z f_z~&k¹r£yÈlpv.I*À^ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ ÿ@qqtî÷qp @GTimes New Roman5Symbol3&Arial7Optimum"1ÐhVd+^d+Vd+B '$¥ÀŽŽ0dÎpÿÿ C:\MSOffice\Templates\Normal.dotITU Meeting **********Donatella BertolottiþÿàòùOh«+'³Ù0 ŽÀÔàì , HT` lxäITU MeetingTU ****************Normal.dotDonatella Bertolotti83naMicrosoft Word 8.0i@ @ XŸ@ XŸ@Ž'±YŸBþÿÕÍÕ.+,ù®DÕÍÕ.+,ù®T px š°žÀÈÐ Øðä CSELT S.p.A.\' ÎjITU MeetingTitle 6> _PID_GUIDäAN{7252F5C0-A912-11D1-8790-0000E81EF7E5} þÿÿÿþÿÿÿ !"#$%&þÿÿÿ()*+,-.þÿÿÿýÿÿÿ1þÿÿÿþÿÿÿþÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿRoot Entryÿÿÿÿÿÿÿÿ ÀF`á\©XŸÀÍ>¶YŸ3nate1TableO6ð+2]â$Wr Budget_1998.lnkBUDGET~1.LNKÿÿÿÿÿÿÿÿÿÿÿÿâ$] Riprev_1998.lnkRIPREV~1.LNKÌô'WordDocumentARIC-1~1.LNKäO*ð 2jM%Mr prÿÿÿÿÿÿÿÿos! Ìô'€LU%;x Lucidi (E).lnk*,1.LNSummaryInformationÀF(ÿÿÿÿÁ`,+0DocumentSummaryInformationoft Netw8ÿÿÿÿÿÿÿÿÿÿÿÿficazioneHPI0994 - Viviani Fabio (S'anifCompObjIANIFICAZIONE\Riprev_1998NoneHÿÿÿÿ\\PIAkObjectPoolÿÿÿÿÿÿÿÿÿÿÿÿÀÍ>¶YŸÀÍ>¶YŸÿÿÿÿÿÿÿÿÿÿÿÿþÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿþÿ ÿÿÿÿ ÀFDocumento Microsoft Word MSWordDocWord.Document.8ô9²q

1 0

Req clarification of H.245 SessionID
by Pete Cordell 12 Nov '98

12 Nov '98

Dear All, Please could some one clarify the use of the H.245 sessionID in communicationModeCommand and OLC. For example, H.245 says: "The sessionID is a unique RTP or T.120 Session Identifier in the conference. It is used by the transmitter to refer to the session to which the logical channel applies. <BOLD>Only the master can create the session identification.</BOLD> " Q: does this mean that the master defines the sessionID in a communications mode command message, or in the OLC procedure. e.g. is it: My endpoint(slave) Remote endpoint(master) ---------> OLC (no SessID) -------------> <--------- OLC ACK (SessID=1) ----------- OR: My endpoint(slave) Remote endpoint(master) <-----ComModeComm (SessID 1 = xyz)<------ ----------> OLC (SessID 1) -------------> <--------OLC ACK (no SessID) <----------- If it is the second case, what happens if the remote endpoint becomes the master, but is not an MC. Do you do: My endpoint(slave) Remote endpoint(master) ---------> OLC (no SessID) -------------> <--------- OLC ACK (SessID=1) ----------- OR: My endpoint(slave) Remote endpoint(master) ----------> OLC (SessID 1) -------------> <--------OLC ACK (no SessID) <----------- If you want to open a second audio session with an associated second video session in a point-to-point non-MC case, do you do: My endpoint(slave) Remote endpoint(master) ----------> OLC (SessID=0) -------------> <--------OLC ACK (SessID=4) <------------ ----> OLC (SessID=0, AssocSessID=4) ----> <--------OLC ACK (SessID=5) <------------ OR is there a way to open the two channels at the same time? Thanks for any pointers, Pete P.S. I'm sure Mark Reid wrote down some examples on these sorts of things, but I can't seem to find them. ================================= Pete Cordell BT Labs E-Mail: pete.cordell(a)bt-sys.bt.co.uk Tel: +44 1473 646436 Fax: +44 1473 645499 =================================

1 0

APC-1445 Uploaded
by Klaghofer Karl PN VS LP3 11 Nov '98

11 Nov '98

Dear Mr. Okubo, APC-1445 "Conference out of Consultation Supplementary Service for H.323" has been uploaded to the pictel Incoming directory. Karl Klaghofer ------------------------------------------------ Karl Klaghofer, Siemens AG, Dpmt. ICN IB NL IP 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

APC-1471.doc
by Bryan Hill 11 Nov '98

11 Nov '98

Dear Mr. Okubo: Please be advised that I have loaded APC-1471 'ISUP and FAS/NFAS Call Signaling for H.323 Gateways' onto the ptel incoming directory. Regards, Bryan Hill _________________________________________________________ Bryan Hill VideoServer Inc. bhill(a)videoserver.com <mailto:bhill@videoserver.com>

1 0

APC-1472, 1473, 1474 on ftp site
by Glen Freundlich 11 Nov '98

11 Nov '98

Dear Mr. Okubo, I have placed APCs 1472, 1473, and 1474 into the Incoming directory of the avc ftp site. Please note that this APC-1474 in the Incoming directory should replace the APC-1474 that exists in the 9811_Tor (I'm not sure where the version in 9811_Tor came from). Best Regards, Glen -- 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: H.245 alphanumeric support required?
by Paul Long 11 Nov '98

11 Nov '98

> From: Rich Bowen[SMTP:rkbowen@CISCO.COM] > H.323 v2 section 6.8.2.1 says, "Transmitters shall limit the content > of their transmitted information to that which the receiver has > indicated it is capable of receiving." > This was written back when "transmitted information" did not include H.245 messages. It referred only to the streams of video, audio, and data. That's why it seems to contradict the following, which was added much later: > H.245 v3 > section 7.12.6 says, "Endpoints shall use the alphanumeric indication > to convey DTMF user input if the other endpoint has not indicated > the ability to receive DTMF using UserInputCapability." > > o Every endpoint is required to indicate capability of > receiving alphanumeric user input (not likely), or -- > > o Every endpoint is assumed to have the capability to > accept alphanumeric user input; i.e., each endpoint > *implicitly* indicates that it has this capability. Or -- > > o I'm interpreting H.245 v3 too strictly. What it really > means is that endpoints shall use alphanumeric if the > remote endpoint did not indicate DTMF capability but it did > indicate alphanumeric capability; otherwise don't send user > input at all. > > Is any of these interpretations correct? > The second one. > Can someone please clarify the requirements here? > First, the intent was that all H.323 terminals have at least a basic ability to signal "DTMF." In fact, this is a requirement. 6.2.8/H.323v2: "An H.245 indication, userInputIndication, is available for transport of user input alphanumeric characters from a keypad or keyboard, equivalent to the DTMF signals used in analogue telephony... H.323 terminals shall support the transmission of user input characters 0-9, "*", and "#". Transmission of other characters is optional." All endpoints must be able to receive all of the H.245 messages, including userInputIndication (6.2.8/H.245v3: "H.323 terminals shall be capable of parsing all H.245 MultimediaSystemControlMessage messages..."); however, note that there is no requirement to do anything with this information on the receive side. Just like with the PSTN, it is up to special-purpose terminals to decide whether and how to interpret these signals, but all terminals are required to send them. Paul Long Smith Micro Software, Inc.

2 1

Re: q11h17, apc1457
by Robert Webber 11 Nov '98

11 Nov '98

Dear Yoshihiro Kikuchi: Your documents in the Q.11 dropbox have been scanned for viruses and moved to the Q.11 Torino meeting directory. Bob Webber At 03:50 PM 11/11/98 +0900, Yoshihiro Kikuchi wrote: >Dear Q.11 and Q.14 experts, > >Ihave place the following document to the dropbox q11-site/dropbox >(avc-site/incoming) directory: > >Q11-H-17 (APC-1457) Proposed Changes on H.245 Codepoints for MPEG-4 >Visual Support (Proposal) > >Best regards, >Yoshihiro > >---- > 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 >

1 0

APC-1470 - IVR Requirements - on FTP site
by Pete Cordell 11 Nov '98

11 Nov '98

Dear Mr. Okubo and SG16 members, Please be advised that I have placed APC-1470 "Requirements for IVR Control in VoIP" from BT into the PictureTel Incoming directory. (Mr. Okubo - Please delete AVC-1470.doc. I forgot that the prefix had changed for a while!) Regards, 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

What aliases is a Gateway to use ?
by Alexander Rovny 11 Nov '98

11 Nov '98

Dear experts, There seems to be an ambiguity in H.323 / H.225.0 concerning alias addresses exposed by a Gateway (not MC / MP) to a Gatekeeper. The question is : What aliases is a Gateway to use during Gatekeeper-related messaging to be able to appear as several H.323 terminals later ? May the alias addresses used as sourceAddress during Discovery/Registration Requests and during Admission Request differ ? H.323 Section 3.16 says : >> An H.323 Gateway (GW) is an endpoint This inspires the idea of a Gateway having it's own aliases; but they CANNOT be a composition of a all possible E164 numbers. H.225.0 Section 7.8.1 says : >> GRQ is sent per logical endpoint; thus ... a Gateway might send many. Does that mean that a Gateway can be considered as a composition of multiple logical Endpoins ? Then, should each of them use separate Discovery/Registration process ? There are 3.5 possible ways to interpret this : a) Gateway pretends to be a composition of multiple logical Endpoins, each of them use separate Discovery/Registration/Admission process with different aliases b1) Gateway's own unique aliases are used for GK Discovery/Registration process which happens only once, but when making a call, the sourceAddress field of AdmissionRequest is filled with appropriate SCN Terminal's E164 number b2) Same as b1), but both Gateway's and SCN Terminal's aliases are used for Admission Request. c) Gateway always uses it's own unique aliases and does not tell the source E164 number to the Gatekeeper What is the common practice here ? Which way do existing GK / GW implementations act ? Please, answer, if you have ideas. Thank you. A.S.Rovny ------------------------------- Alexander S. Rovny MD Information Systems rovny(a)mdis.ru

1 0

APC 1462 uploaded to PicTel's site
by Simao Campos 11 Nov '98

11 Nov '98

Dear colleagues Please accept my apologies for my delay in uploading APC 1462 ("Guidelines for support of non-ITU voice codecs in ITU-T Recommendations") to the PIctureTel FTP incoming AVC directory. I was absent from office most of yesterday, when the internal clearance of the document was concluded. The file can be retrieved from: ftp://standards.pictel.com/avc-site/Incoming/apc1462.doc (before it is moved to the 9811_Tor directory). The summary of the document is attached for your reference. Best regards, Simao Campos-Neto COMSAT ---------------- Summary: This contribution addresses the recent requests for added support of non-ITU voice codecs in ITU-T H-series of Recommendations, H.245 in particular. As the most recent event, ISO/IEF JTC1/SC29/WG11 (a.k.a. MPEG) has requested support for the full MPEG4/Audio for transport in H.324 (N2509, October 1998). The automatic adoption of this and other requests may have important technical implications. This contribution proposes that careful assessment of the implication of such adoptions should be performed by SG 16 as a whole prior to acceptance, with input from other SGs (e.g. SG 12) when necessary. In particular, this contribution proposes that the normative support for MPEG4/Audio is premature without very careful study within the ITU.

1 0