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

None
by Samuel Kallner 19 Oct '98

19 Oct '98

Please allocate a port for IBM Haifa Research Lab (Sam Kallner and Zvi Mizrahy) Thanks. Sam.

1 0

Re: Gateway decomposition
by Michele Bozier 19 Oct '98

19 Oct '98

Mark, I would also like to be included on the call. Regards, Michele Bozier ---------------------------------------- Michele Bozier Principal Development Engineer Madge Networks, Wexham Springs, Framewood Rd, Wexham, Slough SL3 6PJ, England Tel: +44(0)1753 661331 Fax: +44(0)1753 661011 email:mbozier@madge.com -----Original Message----- From: Mark Reid [mailto:mreid@VIDEOSERVER.COM] Sent: Friday, October 16, 1998 9:53 PM To: ITU-SG16(a)MAILBAG.INTEL.COM Subject: Dear Colleagues, I would like to invite you to participate in an audio call, Tuesday October 20th from 11AM to 1PM EST to discuss our work plan for the study of gateway decomposition as outlined in TD 89 (WP2). The goals of the audio call will be to identify what work items we need to completed and in what order should we attack them. Once we have an agreed to work plan, we can talk about building an architecture document and the specific requirements of each interface. As a place to start the discussions, I think we need the following (referenced to TD 89): New Protocols: ***************** Interface A - Device Control Interface New H.246 Annexes: ************************ 1) H.323 to Voice/Voiceband Terminals = The breakdown of the media. How DTMF is converted to/from UserInputIndication messages, etc. (There is a draft of this in the current H.246 Annex B) 2) H.323 to SS7 (Similar to Q.699 - a Q.931 to ISUP conversion spec) 3) H.323 to Q.931 (Similar to the section in Annex A for H.320) Interface B, C, D ******************** For the Proposed Interfaces B, C, and D. Given that the messages passing across these interfaces must reflect all of the content of the signaling that the respective signaling functions receive from and send to extern entities, aren't these protocols modified or extended ISUP for Interface D, modified or extended Q.931 for Interface C, and modified or extended H.225 for Interface B? For C & D, can they be the real protocols if carried on a T1 and some derivation of them if running over TCP/IP? Please try and get all attendee requests in by Monday the 19th at 12:00 Noon EST so that I can make the proper arrangements. I will send port assignments later that day. Here is a summary of attendees so far: 1) G. Thom 2) S. Nayak 3) R. Badri 4) P Kallur 5) K. Hedayat 6) R Spitzer 7) R Chopra 8) A Amir 9) R Even 10) H Liu 11) J Yeh 12) R Radhika 13) B Bell 14) T Taylor 15) G Freundlich 16) M Reid/B Hill/G Kajos All comments welcome, Mark Reid 1-781-505-2368 mreid(a)videoserver.com Bryan Hill 1-781-505-2159 bhill(a)videoserver.com

1 0

Re: conference call on GW decompostion
by Nancy-M Greene 18 Oct '98

18 Oct '98

I would also like to attend this call. Nancy -------------------------------------------------------------------------- Nancy Greene (internally Nancy-M Greene) Internet & Service Provider Networks, Nortel NOTE NEW #'s: T:514-271-7221 (internally ESN853-1077) E:ngreene@nortel.com > > -----Original Message----- > > From: Mark Reid [SMTP:mreid@VIDEOSERVER.COM] > > Sent: Friday, October 16, 1998 1:53 PM > > To: ITU-SG16(a)MAILBAG.INTEL.COM > > Subject: > > > > Dear Colleagues, > > > > I would like to invite you to participate in an audio call, Tuesday > > October > > 20th from 11AM to 1PM EST to discuss our work plan for the study of > > gateway > > decomposition as outlined in TD 89 (WP2). > > > > The goals of the audio call will be to identify what work items we need > to > > completed and in what order should we attack them. Once we have an > agreed > > to > > work plan, we can talk about building an architecture document and the > > specific requirements of each interface. > > > > As a place to start the discussions, I think we need the following > > (referenced to TD 89): > > > > New Protocols: > > ***************** > > Interface A - Device Control Interface > > > > New H.246 Annexes: > > ************************ > > 1) H.323 to Voice/Voiceband Terminals = The breakdown of the media. How > > DTMF > > is converted to/from UserInputIndication messages, etc. (There is a > draft > > of > > this in the current H.246 Annex B) > > 2) H.323 to SS7 (Similar to Q.699 - a Q.931 to ISUP conversion spec) > > 3) H.323 to Q.931 (Similar to the section in Annex A for H.320) > > > > Interface B, C, D > > ******************** > > For the Proposed Interfaces B, C, and D. Given that the messages passing > > across these interfaces must reflect all of the content of the signaling > > that the respective signaling functions receive from and send to extern > > entities, aren't these protocols modified or extended ISUP for Interface > > D, > > modified or extended Q.931 for Interface C, and modified or extended > H.225 > > for Interface B? For C & D, can they be the real protocols if carried on > a > > T1 and some derivation of them if running over TCP/IP? > > > > Please try and get all attendee requests in by Monday the 19th at 12:00 > > Noon > > EST so that I can make the proper arrangements. I will send port > > assignments > > later that day. Here is a summary of attendees so far: > > > > 1) G. Thom > > 2) S. Nayak > > 3) R. Badri > > 4) P Kallur > > 5) K. Hedayat > > 6) R Spitzer > > 7) R Chopra > > 8) A Amir > > 9) R Even > > 10) H Liu > > 11) J Yeh > > 12) R Radhika > > 13) B Bell > > 14) T Taylor > > 15) G Freundlich > > 16) M Reid/B Hill/G Kajos > > > > All comments welcome, > > > > Mark Reid > > 1-781-505-2368 > > mreid(a)videoserver.com > > > > Bryan Hill > > 1-781-505-2159 > > bhill(a)videoserver.com >

1 0

Re: GW Decomp Conf Call
by Bhasker, Narjala 18 Oct '98

18 Oct '98

Mark - Pls allocate a port for Intel (Bhasker, Toga, Kumar). Thanks Bhasker -----Original Message----- From: Joerg Ott [mailto:jo@INFORMATIK.UNI-BREMEN.DE] Sent: Saturday, October 17, 1998 12:57 AM To: ITU-SG16(a)MAILBAG.INTEL.COM Subject: Re: your mail Hi Mark, please add me to the list of participants... Joerg ---------------------------------------------------------------------------- --- Joerg Ott jo(a)tzi.uni-bremen.de Universitaet Bremen, Germany fax + 49 421 218-2085 TELES AG voice + 49 421 218-7000

1 0

None
by Markku Korpi 18 Oct '98

18 Oct '98

Mark, Please include me. --Markku Korpi Siemens Information & Communication Networks Tel: +1(408)4927328 Fax: +(408)4924666 Email: korpim(a)scn.de At 04:52 PM 10/16/98 -0400, you wrote: >Dear Colleagues, > >I would like to invite you to participate in an audio call, Tuesday October >20th from 11AM to 1PM EST to discuss our work plan for the study of gateway >decomposition as outlined in TD 89 (WP2). > >The goals of the audio call will be to identify what work items we need to >completed and in what order should we attack them. Once we have an agreed to >work plan, we can talk about building an architecture document and the >specific requirements of each interface. > >As a place to start the discussions, I think we need the following >(referenced to TD 89): > >New Protocols: >***************** >Interface A - Device Control Interface > >New H.246 Annexes: >************************ >1) H.323 to Voice/Voiceband Terminals = The breakdown of the media. How DTMF >is converted to/from UserInputIndication messages, etc. (There is a draft of >this in the current H.246 Annex B) >2) H.323 to SS7 (Similar to Q.699 - a Q.931 to ISUP conversion spec) >3) H.323 to Q.931 (Similar to the section in Annex A for H.320) > >Interface B, C, D >******************** >For the Proposed Interfaces B, C, and D. Given that the messages passing >across these interfaces must reflect all of the content of the signaling >that the respective signaling functions receive from and send to extern >entities, aren't these protocols modified or extended ISUP for Interface D, >modified or extended Q.931 for Interface C, and modified or extended H.225 >for Interface B? For C & D, can they be the real protocols if carried on a >T1 and some derivation of them if running over TCP/IP? > >Please try and get all attendee requests in by Monday the 19th at 12:00 Noon >EST so that I can make the proper arrangements. I will send port assignments >later that day. Here is a summary of attendees so far: > >1) G. Thom >2) S. Nayak >3) R. Badri >4) P Kallur >5) K. Hedayat >6) R Spitzer >7) R Chopra >8) A Amir >9) R Even >10) H Liu >11) J Yeh >12) R Radhika >13) B Bell >14) T Taylor >15) G Freundlich >16) M Reid/B Hill/G Kajos > >All comments welcome, > >Mark Reid >1-781-505-2368 >mreid(a)videoserver.com > >Bryan Hill >1-781-505-2159 >bhill(a)videoserver.com > > Markku Korpi Siemens Information & Communication Networks Tel: +1(408)4927328 Fax: +(408)4924666 Email: korpim(a)scn.de

1 0

None
by Mark Reid 17 Oct '98

17 Oct '98

Dear Colleagues, I would like to invite you to participate in an audio call, Tuesday October 20th from 11AM to 1PM EST to discuss our work plan for the study of gateway decomposition as outlined in TD 89 (WP2). The goals of the audio call will be to identify what work items we need to completed and in what order should we attack them. Once we have an agreed to work plan, we can talk about building an architecture document and the specific requirements of each interface. As a place to start the discussions, I think we need the following (referenced to TD 89): New Protocols: ***************** Interface A - Device Control Interface New H.246 Annexes: ************************ 1) H.323 to Voice/Voiceband Terminals = The breakdown of the media. How DTMF is converted to/from UserInputIndication messages, etc. (There is a draft of this in the current H.246 Annex B) 2) H.323 to SS7 (Similar to Q.699 - a Q.931 to ISUP conversion spec) 3) H.323 to Q.931 (Similar to the section in Annex A for H.320) Interface B, C, D ******************** For the Proposed Interfaces B, C, and D. Given that the messages passing across these interfaces must reflect all of the content of the signaling that the respective signaling functions receive from and send to extern entities, aren't these protocols modified or extended ISUP for Interface D, modified or extended Q.931 for Interface C, and modified or extended H.225 for Interface B? For C & D, can they be the real protocols if carried on a T1 and some derivation of them if running over TCP/IP? Please try and get all attendee requests in by Monday the 19th at 12:00 Noon EST so that I can make the proper arrangements. I will send port assignments later that day. Here is a summary of attendees so far: 1) G. Thom 2) S. Nayak 3) R. Badri 4) P Kallur 5) K. Hedayat 6) R Spitzer 7) R Chopra 8) A Amir 9) R Even 10) H Liu 11) J Yeh 12) R Radhika 13) B Bell 14) T Taylor 15) G Freundlich 16) M Reid/B Hill/G Kajos All comments welcome, Mark Reid 1-781-505-2368 mreid(a)videoserver.com Bryan Hill 1-781-505-2159 bhill(a)videoserver.com

5 4

Re: Gateway Decomposition
by Ami Amir 17 Oct '98

17 Oct '98

Hi All Small "European/Middle Eastern" request -try not to schedule evening calls so that we can join. Anothe request - can someone pots again the "GAteway Decomposition" document? I only have a hard copy somewhere. Thanks Ami Gary A. Thom wrote: > > ---------- > > From: Gary A. Thom[SMTP:GTHOM@DELTA-INFO.COM] > > Sent: Friday, October 16, 1998 10:27:22 AM > > To: ITU-SG16(a)mailbag.cps.intel.com > > Subject: Re: Contact Info requested > > Auto forwarded by a Rule > > > Tom, > > Please include me also. > > Gary > ------------------------------------------------------ > Name : Gary A. Thom > Company: Delta Information Systems, Inc. > Address: 300 Welsh Rd., Bldg 3 > Horsham, PA 19044 USA > Phone : +1-215-657-5270 Fax : +1-215-657-5273 > E-mail : gthom(a)delta-info.com > ------------------------------------------------------

1 0

[Q] Differences between 'ad hoc multipoint conf' and 'multipoint conf'.
by Lee Hyoung soo 16 Oct '98

16 Oct '98

Hi, Can you tell me the differences between 'ad hoc multipoint conference' and 'multipoint conference'? According to the recommendation of H.323 V2, ad hoc multipoint conference : An Ad Hoc Multipoint conference was a point-to-point conference that had been expanded into a multipoint conference at some time during the call. multipoint conference : A Multipoint conference is a conference between three or more terminals. Any multipoint conference can begin with three or more terminals without expansion from point-to-point conference? Best wishes, soo Nada Research Co., Ltd. Korea.

1 0

Re: conference call on GW decompostion
by Kumar, Vineet 16 Oct '98

16 Oct '98

Please include me in the conference call. Thanks. vineet ---------------------------------------------------------------------------- -------------------------- Vineet Kumar vineet.kumar(a)intel.com Intel Corporation, JF3-212 (+1) 503-264-3439 (phone) Hillsboro, OR 97124-5961 (+1) 503-264-3375 (fax) ---------------------------------------------------------------------------- -------------------------- > -----Original Message----- > From: Mark Reid [SMTP:mreid@VIDEOSERVER.COM] > Sent: Friday, October 16, 1998 1:53 PM > To: ITU-SG16(a)MAILBAG.INTEL.COM > Subject: > > Dear Colleagues, > > I would like to invite you to participate in an audio call, Tuesday > October > 20th from 11AM to 1PM EST to discuss our work plan for the study of > gateway > decomposition as outlined in TD 89 (WP2). > > The goals of the audio call will be to identify what work items we need to > completed and in what order should we attack them. Once we have an agreed > to > work plan, we can talk about building an architecture document and the > specific requirements of each interface. > > As a place to start the discussions, I think we need the following > (referenced to TD 89): > > New Protocols: > ***************** > Interface A - Device Control Interface > > New H.246 Annexes: > ************************ > 1) H.323 to Voice/Voiceband Terminals = The breakdown of the media. How > DTMF > is converted to/from UserInputIndication messages, etc. (There is a draft > of > this in the current H.246 Annex B) > 2) H.323 to SS7 (Similar to Q.699 - a Q.931 to ISUP conversion spec) > 3) H.323 to Q.931 (Similar to the section in Annex A for H.320) > > Interface B, C, D > ******************** > For the Proposed Interfaces B, C, and D. Given that the messages passing > across these interfaces must reflect all of the content of the signaling > that the respective signaling functions receive from and send to extern > entities, aren't these protocols modified or extended ISUP for Interface > D, > modified or extended Q.931 for Interface C, and modified or extended H.225 > for Interface B? For C & D, can they be the real protocols if carried on a > T1 and some derivation of them if running over TCP/IP? > > Please try and get all attendee requests in by Monday the 19th at 12:00 > Noon > EST so that I can make the proper arrangements. I will send port > assignments > later that day. Here is a summary of attendees so far: > > 1) G. Thom > 2) S. Nayak > 3) R. Badri > 4) P Kallur > 5) K. Hedayat > 6) R Spitzer > 7) R Chopra > 8) A Amir > 9) R Even > 10) H Liu > 11) J Yeh > 12) R Radhika > 13) B Bell > 14) T Taylor > 15) G Freundlich > 16) M Reid/B Hill/G Kajos > > All comments welcome, > > Mark Reid > 1-781-505-2368 > mreid(a)videoserver.com > > Bryan Hill > 1-781-505-2159 > bhill(a)videoserver.com

1 0

None
by Roy Spitzer 16 Oct '98

16 Oct '98

Mark, Where can I find a copy of TD 89 and any other draft documents that will be discussed in this meeting. Regards, Roy Roy Spitzer Telogy Networks Phone (301) 515-6531 20250 Century Boulevard Fax: (301) 515-7954 Germantown, Maryland 20874 email: rspitzer(a)telogy.com -----Original Message----- From: Mark Reid [mailto:mreid@VIDEOSERVER.COM] Sent: Friday, October 16, 1998 4:53 PM To: ITU-SG16(a)mailbag.cps.INTEL.com Subject: Dear Colleagues, I would like to invite you to participate in an audio call, Tuesday October 20th from 11AM to 1PM EST to discuss our work plan for the study of gateway decomposition as outlined in TD 89 (WP2). The goals of the audio call will be to identify what work items we need to completed and in what order should we attack them. Once we have an agreed to work plan, we can talk about building an architecture document and the specific requirements of each interface. As a place to start the discussions, I think we need the following (referenced to TD 89): New Protocols: ***************** Interface A - Device Control Interface New H.246 Annexes: ************************ 1) H.323 to Voice/Voiceband Terminals = The breakdown of the media. How DTMF is converted to/from UserInputIndication messages, etc. (There is a draft of this in the current H.246 Annex B) 2) H.323 to SS7 (Similar to Q.699 - a Q.931 to ISUP conversion spec) 3) H.323 to Q.931 (Similar to the section in Annex A for H.320) Interface B, C, D ******************** For the Proposed Interfaces B, C, and D. Given that the messages passing across these interfaces must reflect all of the content of the signaling that the respective signaling functions receive from and send to extern entities, aren't these protocols modified or extended ISUP for Interface D, modified or extended Q.931 for Interface C, and modified or extended H.225 for Interface B? For C & D, can they be the real protocols if carried on a T1 and some derivation of them if running over TCP/IP? Please try and get all attendee requests in by Monday the 19th at 12:00 Noon EST so that I can make the proper arrangements. I will send port assignments later that day. Here is a summary of attendees so far: 1) G. Thom 2) S. Nayak 3) R. Badri 4) P Kallur 5) K. Hedayat 6) R Spitzer 7) R Chopra 8) A Amir 9) R Even 10) H Liu 11) J Yeh 12) R Radhika 13) B Bell 14) T Taylor 15) G Freundlich 16) M Reid/B Hill/G Kajos All comments welcome, Mark Reid 1-781-505-2368 mreid(a)videoserver.com Bryan Hill 1-781-505-2159 bhill(a)videoserver.com

1 0