November 1998 - sg16-avd - lists.packetizer.com

APC 1436 was uploaded
by Sasha Ruditsky 17 Nov '98

17 Nov '98

Dear Mr. Okubo, I have uploaded APC-1436 to the Incoming directory. Best regards. Sasha *********************************************** Alexander(Sasha) Ruditsky RADVision Ltd. 24 Raul Wallenberg St. Tel Aviv 69719 Israel Tel: +972-3-645-5220 Fax: +972-3-647-6669 Direct: +972-3-645-5273 sasha(a)radvision.rad.co.il ***********************************************

1 0

H.225 Status Enquiry CRV length
by Srinivasa Reddy 16 Nov '98

16 Nov '98

H.225 V2 & V3 "Section 7.3.13 Status Enquiry" says the call reference IE length is 3 bytes. I guess it should be 2 bytes. thanks, Srinivasa Beereddy, Trillium Digital Systems, Inc.

1 0

APC-1455
by Naomi Frid 16 Nov '98

16 Nov '98

> Dear Mr. Okubo, > > I have uploaded APC-1455 to the Incoming directory. > > Best regards. > > Naomi > -------------------------------------------- > Naomi Frid Ruppin > Gatekeeper Project Manager > RadVision > Tel. 972-3-7657505 > Fax. 972-3-6476669 > frid(a)radvision.rad.co.il > > >

1 0

Re: Mailing List Archive.
by Jim Toga 16 Nov '98

16 Nov '98

There are two places to get the archive from: When the list was hosted at Intel (about 5mos ago) it was archived to ftp://ftp.intel.com/pub/H.323/mailing-list/ After moving to the IMTC, it has taken a while to start the archives but they can be found at: http://www.imtc.org/mail/h323implementors/1998/ Regards, jimt. At 09:03 AM 11/13/98 +0900, you wrote: > >Please let me know the site address of this mailinig list archive. > >Thanks. > >------------------------------------------------------------------------- >for list subscription instructions, >send email to h323implementors-request(a)imtc.org with text "info" > ***************************************************** *** +1-503-264-8816(voice) Intel - Hillsboro, OR. *** *** mailto:jim.toga@intel.com mailto:james.toga@ties.itu.int *** *** PGP keyID 36 07 86 49 7D 74 DF 57 50 CB BA 32 08 9C 7C 41 *** *****************************************************

1 0

IMTC Liaison
by Sebestyen Istvan ICN WN ES SP 4 16 Nov '98

16 Nov '98

Dear Mr. Okubo, unfortunately this time I can not be present at the Joint Rapp. Meeting due to collisions with other meetings. <<IMTC-lias>> However, please find attached a short Liason from IMTC in my capacity as IMTC BOD Member and SG16 Associated Rapp. I have promised to help Deepak Kamlani in organizing the February 1999 SG16 rapp. meeting that IMTC is planning to host. I have asked Bernard Hammer to present that paper at the ITU-T Sg16 rapp. meeting, who is going to attend at your meeting. Regards, Istvan Sebestyen -------------------------------------------------------------------------- Dr. Istvan Sebestyen Siemens AG, ICN WN ES SP 4, Hofmannstr. 51 D-81359 Munich Tel:+49-89-722-47230 Fax:+49-89-722-47713 E-Mail: istvan.sebestyen(a)icn.siemens.de Intranet: http://www.pn.siemens.de/pngs/people/pngs9/ ---------------------------------------------------------------------------- ----------------

1 0

AW: Usage of CallID in H.323v2 for rerouted (diverted, transferre d,.. .) calls
by Klaghofer Karl PN VS LP3 16 Nov '98

16 Nov '98

Chris, Thanks for your comment. CRV is unique just at one signalling link of a call (e.g. between EP A and GK; and may be different between GK and EP2 of the same call) . Since CallID may be preserved when calls are redirected (incl. transfer, forward,...), the CallID actually identifies the call scenario and not exactly one call. I think this is fine. A CallLegID would be a new identifier that is somehow in between CallID and CRV by identifying exactly one call (or call attempt) between two endpoints. We might think about for H.225.0v3. Regards, Karl > -----Ursprüngliche Nachricht----- > Von: Chris Purvis [SMTP:CPurvis@MADGE.COM] > Gesendet am: Montag, 16. November 1998 12:52 > An: ITU-SG16(a)mailbag.cps.intel.com > Betreff: Re: Usage of CallID in H.323v2 for rerouted (diverted, > transferre d,.. .) calls > > Karl, > > I agree with your comments on CallID being preserved when calls are > transferred. However... > > > >As an alternative, we might add a new multilevel CallID (e.g. > >to H.225.0 v3) > >that consists of an identifier that indicates the "overal > >call" and a second > >identifier that indicates the call leg. > Isn't this the CRV, that's always been there? > 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: Usage of CallID in H.323v2 for rerouted (diverted, transferre d,.. .) calls
by Chris Purvis 16 Nov '98

16 Nov '98

Karl, I agree with your comments on CallID being preserved when calls are transferred. However... >As an alternative, we might add a new multilevel CallID (e.g. >to H.225.0 v3) >that consists of an identifier that indicates the "overal >call" and a second >identifier that indicates the call leg. Isn't this the CRV, that's always been there? 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

Usage of CallID in H.323v2 for rerouted (diverted, transferred,.. .) calls
by Klaghofer Karl PN VS LP3 16 Nov '98

16 Nov '98

H.225.0v2 CallID identifies the call with which the message is associated (all RAS and Call Signalling messages related to the same call). Is it allowed that the CallID value for a rerouted call (second Setup) may be the same as the CallID value used in the first call Setup message ? According to H.323v2 clause 7.5 second last sentence it is even recommended (e.g. reference to Fig. 19/H.323 where all messages shown in the figure shall use the same CallID) ? However, I would like this to be confirmed, since somebody might interpret this as contradicting with the definition of the call identifier. If we can confirm this, then I propose that such a usage of the CallID is also possible for H.450.x related call redirections (e.g. Call Diversion, Call Transfer). This would allow the calls (e.g. first call setup and diverted call) to be associated for applications. As an alternative, we might add a new multilevel CallID (e.g. to H.225.0 v3) that consists of an identifier that indicates the "overal call" and a second identifier that indicates the call leg. Thanks, Karl ------------------------------------------------ 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-1456.
by Yair Miranda 15 Nov '98

15 Nov '98

Dear Mr. Okubo, I have uploaded an updated version of APC-1456 to the Incoming directory. Best regards. Yair Miranda yair(a)radvision.rad.co.il Tel : +972-3-6455271 Fax : +972-3-6476669 Video : +972-3-6489010 http://www.radvision.com

1 0

Re: APC No for Contribution to Q14/SG16
by Sakae OKUBO 14 Nov '98

14 Nov '98

Dear Mike Buckley, Your request is very late. Let me consult with the meeting how to handle your contribution (APC numbered document or TD or other way). In the meantime please upload your document at the /Incoming directory with an appropriate file name and announce your uploading on the reflector for the interest of the group members. 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 *********************************************************** At 23:26 +0900 98/11/13, Mike Buckley wrote: > Mr Okubo, > > We would like to submit a contribution to next weeks Q11, Q12, Q13, Q14 > meeting in Turin. I realise that the deadline for submissions is now past, >and I > apologise for the lateness. The contribution relates to the Media Gateway > Control Protocol and will probably contain a number of companies names > including Lucent Technologies. > > I would be very grateful if you could allocate an APC number. > > Many Thanks, > > Mike Buckley > Lucent Technologies > +44-145-877718 (T) > +44-145-877721 (F) > mikebuckley(a)lucent.com

1 0