- sg16-avd - lists.packetizer.com

Re: H.323 mobility first draft
by Roy, Radhika R, ALARC 24 Aug '99

24 Aug '99

Ed: Thank you so much for clarifcations! I appreciate. Regards, Radhika > -----Original Message----- > From: Edgar Martinez [1] [SMTP:martinze@CIG.MOT.COM] > Sent: Tuesday, August 24, 1999 10:26 AM > To: ITU-SG16(a)MAILBAG.INTEL.COM > Subject: Re: H.323 mobility first draft > Importance: High > > Dear All, > > Roy statements are correct. The official work of Annex-H has not > been started. There is no official Annex-H document at the present. > > The Terms of reference for H.323 Mobility (TD-34) was included > with the Motorola contribution to provide a check list for other > contributors and comments. Basically, does the Motorola > (Annex-H - User and Service Mobility in H.323) > contribution meet the terms of reference? > > Now, as the editor of the upcoming Annex H. I hope on that in the > upcoming SG16 Q.13 meeting in New Jersey. We can get started > on the official Annex-H, so contributions are needed. > Looking forward for your contributions and comments. > > As for the style of the contribution. I have other editorial > duties in other standards and habits are hard to break. > > > Best Regards, > Ed > > > "Roy, Radhika R, ALARC" wrote: > > > Hi Everyone: > > > > We have received two documents from Edgar Martinez with the following > > titles: > > > > 1. Terms of reference for H.323 Mobility > > 2. Annex-H (User and Service Mobility in H.323) > > > > Let me make very clear that the mobility ad hoc group agreed with the > first > > document (Terms of reference for H.323 Mobility). > > > > Th second document (Annex-H - User and Service Mobility in H.323) had > NOT > > been considered at all. Therefore, this document does NOT reference any > > reference with respect to any agreement in the last Berlin meeting. > > > > It is very confusing because Edgar Martinez has been assigned to play > the > > role of "Editor" of H.323 Annex-H. As such, any document produced as an > > editor should reflect the consensus of the delegates. > > > > I suppose that the second document (Annex-H - User and Service Mobility > in > > H.323) is a contribution from Motorola (NOT as an editor of Annex H) > that > > may be discussed in the upcoming SG16 Q.13 meeting ( New Jersey, USA - > > October 18-22, 1999). > > > > I hope that Edgar will clarify the confusion to all of us. > > > > Best Regards, > > > > Radhika R. Roy > > AT&T > > + 1 732 420 1580 > > > > > -----Original Message----- > > > From: Edgar Martinez [1] [SMTP:martinze@CIG.MOT.COM] > > > Sent: Monday, August 23, 1999 3:19 AM > > > To: ITU-SG16(a)MAILBAG.INTEL.COM > > > Subject: H.323 mobility first darft > > > > > > Dear All > > > > > > I have uploaded the first H.323 draft, for user > > > and service mobility based on the terms of reference > > > agreed in the SG16 meeting in Berlin. > > > > > > The focus of the document at the moment is to provide full > > > mobility regards of terminal types, that is either fixed or wireless > > > h.323 terminals. Only using H.323 messages with additional > > > extensions to provide seamless wireless handover and > > > terminal roaming. > > > > > > Anyone can pick-up a copy in following wed sites. > > > > > > http://people.itu.int/~emartine/temp/ > > > or > > > ftp://standard.pictel.com/avc-site/Incoming/ > > > > > > The Filename is h323mob01.zip > > > > > > Comments are welcome. > > > > > > Best Regards, > > > -- > > > Edgar Martinez - Principal Staff Engineer > > > Email mailto:martinze@cig.mot.com > > > FAX 1-847-632-3145 - - Voice 1-847-632-5278 > > > 1501 West Shure Drive, Arlington Hgts. IL 60004 > > > Public: TIPHON & Other Stds - http://people.itu.int/~emartine/ > > > Private:TIPHON & Other Stds - http://www.cig.mot.com/~martinze/ > > -- > Edgar Martinez - Principal Staff Engineer > Email mailto:martinze@cig.mot.com > FAX 1-847-632-3145 - - Voice 1-847-632-5278 > 1501 West Shure Drive, Arlington Hgts. IL 60004 > Public: TIPHON & Other Stds - http://people.itu.int/~emartine/ > Private:TIPHON & Other Stds - http://www.cig.mot.com/~martinze/

1 0

Re: H.323 mobility first draft
by Edgar Martinez [1] 24 Aug '99

24 Aug '99

Dear All, Roy statements are correct. The official work of Annex-H has not been started. There is no official Annex-H document at the present. The Terms of reference for H.323 Mobility (TD-34) was included with the Motorola contribution to provide a check list for other contributors and comments. Basically, does the Motorola (Annex-H - User and Service Mobility in H.323) contribution meet the terms of reference? Now, as the editor of the upcoming Annex H. I hope on that in the upcoming SG16 Q.13 meeting in New Jersey. We can get started on the official Annex-H, so contributions are needed. Looking forward for your contributions and comments. As for the style of the contribution. I have other editorial duties in other standards and habits are hard to break. Best Regards, Ed "Roy, Radhika R, ALARC" wrote: > Hi Everyone: > > We have received two documents from Edgar Martinez with the following > titles: > > 1. Terms of reference for H.323 Mobility > 2. Annex-H (User and Service Mobility in H.323) > > Let me make very clear that the mobility ad hoc group agreed with the first > document (Terms of reference for H.323 Mobility). > > Th second document (Annex-H - User and Service Mobility in H.323) had NOT > been considered at all. Therefore, this document does NOT reference any > reference with respect to any agreement in the last Berlin meeting. > > It is very confusing because Edgar Martinez has been assigned to play the > role of "Editor" of H.323 Annex-H. As such, any document produced as an > editor should reflect the consensus of the delegates. > > I suppose that the second document (Annex-H - User and Service Mobility in > H.323) is a contribution from Motorola (NOT as an editor of Annex H) that > may be discussed in the upcoming SG16 Q.13 meeting ( New Jersey, USA - > October 18-22, 1999). > > I hope that Edgar will clarify the confusion to all of us. > > Best Regards, > > Radhika R. Roy > AT&T > + 1 732 420 1580 > > > -----Original Message----- > > From: Edgar Martinez [1] [SMTP:martinze@CIG.MOT.COM] > > Sent: Monday, August 23, 1999 3:19 AM > > To: ITU-SG16(a)MAILBAG.INTEL.COM > > Subject: H.323 mobility first darft > > > > Dear All > > > > I have uploaded the first H.323 draft, for user > > and service mobility based on the terms of reference > > agreed in the SG16 meeting in Berlin. > > > > The focus of the document at the moment is to provide full > > mobility regards of terminal types, that is either fixed or wireless > > h.323 terminals. Only using H.323 messages with additional > > extensions to provide seamless wireless handover and > > terminal roaming. > > > > Anyone can pick-up a copy in following wed sites. > > > > http://people.itu.int/~emartine/temp/ > > or > > ftp://standard.pictel.com/avc-site/Incoming/ > > > > The Filename is h323mob01.zip > > > > Comments are welcome. > > > > Best Regards, > > -- > > Edgar Martinez - Principal Staff Engineer > > Email mailto:martinze@cig.mot.com > > FAX 1-847-632-3145 - - Voice 1-847-632-5278 > > 1501 West Shure Drive, Arlington Hgts. IL 60004 > > Public: TIPHON & Other Stds - http://people.itu.int/~emartine/ > > Private:TIPHON & Other Stds - http://www.cig.mot.com/~martinze/ -- Edgar Martinez - Principal Staff Engineer Email mailto:martinze@cig.mot.com FAX 1-847-632-3145 - - Voice 1-847-632-5278 1501 West Shure Drive, Arlington Hgts. IL 60004 Public: TIPHON & Other Stds - http://people.itu.int/~emartine/ Private:TIPHON & Other Stds - http://www.cig.mot.com/~martinze/

1 0

Re: H.323 mobility first draft
by Roy, Radhika R, ALARC 24 Aug '99

24 Aug '99

Hi Everyone: We have received two documents from Edgar Martinez with the following titles: 1. Terms of reference for H.323 Mobility 2. Annex-H (User and Service Mobility in H.323) Let me make very clear that the mobility ad hoc group agreed with the first document (Terms of reference for H.323 Mobility). Th second document (Annex-H - User and Service Mobility in H.323) had NOT been considered at all. Therefore, this document does NOT reference any reference with respect to any agreement in the last Berlin meeting. It is very confusing because Edgar Martinez has been assigned to play the role of "Editor" of H.323 Annex-H. As such, any document produced as an editor should reflect the consensus of the delegates. I suppose that the second document (Annex-H - User and Service Mobility in H.323) is a contribution from Motorola (NOT as an editor of Annex H) that may be discussed in the upcoming SG16 Q.13 meeting ( New Jersey, USA - October 18-22, 1999). I hope that Edgar will clarify the confusion to all of us. Best Regards, Radhika R. Roy AT&T + 1 732 420 1580 > -----Original Message----- > From: Edgar Martinez [1] [SMTP:martinze@CIG.MOT.COM] > Sent: Monday, August 23, 1999 3:19 AM > To: ITU-SG16(a)MAILBAG.INTEL.COM > Subject: H.323 mobility first darft > > Dear All > > I have uploaded the first H.323 draft, for user > and service mobility based on the terms of reference > agreed in the SG16 meeting in Berlin. > > The focus of the document at the moment is to provide full > mobility regards of terminal types, that is either fixed or wireless > h.323 terminals. Only using H.323 messages with additional > extensions to provide seamless wireless handover and > terminal roaming. > > Anyone can pick-up a copy in following wed sites. > > http://people.itu.int/~emartine/temp/ > or > ftp://standard.pictel.com/avc-site/Incoming/ > > The Filename is h323mob01.zip > > Comments are welcome. > > Best Regards, > -- > Edgar Martinez - Principal Staff Engineer > Email mailto:martinze@cig.mot.com > FAX 1-847-632-3145 - - Voice 1-847-632-5278 > 1501 West Shure Drive, Arlington Hgts. IL 60004 > Public: TIPHON & Other Stds - http://people.itu.int/~emartine/ > Private:TIPHON & Other Stds - http://www.cig.mot.com/~martinze/

1 0

interpretation of the callSignalAddress parameter
by Wolfgang Bandow 24 Aug '99

24 Aug '99

Dear Sir or Madam, let me please put a question concerning the H.323/H.225 call signalling and RAS parameters. Going on the assumption that the gatekeeper routed call model is chosen, we would like to know how to interpret "destCallSignalAddress" and "srcCallSignalAddress". We focus on following configuration: endpoint A <-> gatekeeper <-> endpoint B, where endpoint A is the initiator of a call. 1. Is it correct that the CallSignalAddress of the gatekeeper is to be used as the destCallSignalAddress for messages sent from endpoint A or endpoint B? 2. Is it correct that the CallSignalAddress of the gatekeeper is to be used as the srcCallSignalAddress for messages sent from the gatekeeper to endpoint A or endpoint B? 3. Is it correct that the CallSignalAddress of endpoint B is to be used as the srcCallSignalAddress for messages sent from endpoint B to the gatekeeper (e.g. ARQ message) although endpoint B is the called party and not the calling one? Maybe there is a generic definition for "source" and "destination" for multi-station-calls. Thanks a lot in advance for your help. Regards, Wolfgang Bandow

1 0

APC-1644 - Report of the Berlin meeting
by Sakae OKUBO 24 Aug '99

24 Aug '99

Dear Q12-14/16 experts, I have uploaded the followin two files at the ftp site: ftp://standard.pictel.com/avc-site/Incoming/APC-1644a.zip ftp://standard.pictel.com/avc-site/Incoming/APC-1644a_wcm.zip or http://standard.pictel.com/ftp/avc-site/Incoming/APC-1644a.zip http://standard.pictel.com/ftp/avc-site/Incoming/APC-1644a_wcm.zip These update the APC-1644.doc with minor editorial improvements. An exception, though it is still of editorial nature, is addition of Annex 9 (communication to Megaco regarding commenting on the requirements for the MGC protocol). APC-1644a_wcm.zip marks the changes relative to APC-1644.doc. APC-1644a.zip will soon be moved to /9908_Ber directory. APC-1644.zip and APC-1644a_wcm.zip will be removed at that time. You see also APC-1645.zip at the /Incoming directory. This is a liaison from TIPHON to be reviewed at the October Rapporteur meeting. It will be moved to /9910_??? directory (??? will be "New" or something else depending on the meeting place). 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

None
by Sherlock, Stuart 23 Aug '99

23 Aug '99

Same here. Thanks Stuart -----Original Message----- From: Mordy Rothberg [mailto:mordy@NET2PHONE.COM] Sent: Sunday, August 22, 1999 11:36 AM To: ITU-SG16(a)MAILBAG.INTEL.COM Subject: how do you unsubscribe? > -----Original Message----- > From: Mailing list for parties associated with ITU-T Study Group 16 > [mailto:ITU-SG16@mailbag.cps.intel.com]On Behalf Of Roy, Radhika R, > ALARC > Sent: Thursday, August 19, 1999 8:31 AM > To: ITU-SG16(a)mailbag.cps.intel.com > Subject: > > > Thanks, > Radhika > > > -----Original Message----- > > From: Jangi, Shrirang [SMTP:sjangi@SONUSNET.COM] > > Sent: Wednesday, August 18, 1999 7:47 PM > > To: ITU-SG16(a)MAILBAG.INTEL.COM > > Subject: > > > > "subscribe" >

1 0

H.450.3 call forwarding supplementary services
by vjaiswal＠HSS.HNS.COM 23 Aug '99

23 Aug '99

Hi In H.450.3, call forwarding supplementary services, the response to interrogateDiversionQ.Invoke APDU is defined as follows IntResultList ::= SET SIZE (0..29) OF IntResult IntResult ::= SEQUENCE { servedUserNr EndpointAddress, basicService BasicService, procedure Procedure, divertedToAddress EndpointAddress, remoteEnabled BOOLEAN DEFAULT FALSE, extension CHOICE {extensionSeq ExtensionSeq, nonStandardData NonStandardParameter } OPTIONAL, ? } I would like to know, why the result has been kept a list of maximum 29 nodes. As far as my understanding goes, a list of 3 nodes would suffice, one node for each service type (CFU/CFB/CFNR). Ane help would be appreciated. Thanks Regards Vivek Jaiswal, Hughes Software Systems

1 0

H.323 mobility first darft
by Edgar Martinez [1] 23 Aug '99

23 Aug '99

Dear All I have uploaded the first H.323 draft, for user and service mobility based on the terms of reference agreed in the SG16 meeting in Berlin. The focus of the document at the moment is to provide full mobility regards of terminal types, that is either fixed or wireless h.323 terminals. Only using H.323 messages with additional extensions to provide seamless wireless handover and terminal roaming. Anyone can pick-up a copy in following wed sites. http://people.itu.int/~emartine/temp/ or ftp://standard.pictel.com/avc-site/Incoming/ The Filename is h323mob01.zip Comments are welcome. Best Regards, -- Edgar Martinez - Principal Staff Engineer Email mailto:martinze@cig.mot.com FAX 1-847-632-3145 - - Voice 1-847-632-5278 1501 West Shure Drive, Arlington Hgts. IL 60004 Public: TIPHON & Other Stds - http://people.itu.int/~emartine/ Private:TIPHON & Other Stds - http://www.cig.mot.com/~martinze/

1 0

Looking for H.332 products
by Annika Kilegran 23 Aug '99

23 Aug '99

Hello, I'm looking for H.332 products (also Beta versions) to be used for example for internal seminars. Thanks, Annika Kilegran Telia -------------------------------------------------- Annika Kilegran Telia Research AB Phone: +46-8-71382926 Vitsandsgatan 9 B211 Fax: +46-8-7138199 S-12386 Farsta Mobile: +46-70-5904032 Sweden E-mail: Annika.W.Kilegran(a)telia.se --------------------------------------------------

1 0

H.225.0 V3 documents
by Glen Freundlich 22 Aug '99

22 Aug '99

Dear colleagues, I've placed 4 files in the Incoming directory of the ftp site: h225v3.zip - H.225.0 V3 white draft h225v3wcm.zip - V3 white draft showing changes from V2 h225v3b.zip - H.225.0 V3 with changes from Berlin meeting and corrections h225v3bcm.zip - h225v3b showing differences from h225v3 Please let me know as soon as possible if you find any errors. 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

2 1