Invitation via Gatekeeper
Roy, Radhika R, ALCOO
rrroy at ATT.COM
Fri Mar 5 09:08:05 EST 1999
This was my understanding as well.
Does anyone disagree with Gary?
Regards,
Radhika
-------------------------------------------
Radhika R. Roy
AT&T Labs
Room C1-2B03
200 Laurel Avenue S.
Middletwon, NJ 07748
USA
+ 1 732 420 1580 Tel
rrroy at att.com
> -----Original Message-----
> From: Gary A. Thom [SMTP:gthom at DELTA-INFO.COM]
> Sent: Friday, March 05, 1999 11:18 AM
> To: ITU-SG16 at MAILBAG.INTEL.COM
> Subject: Re: Invitation via Gatekeeper
>
> I have this minor semantic clarification:
>
> > 2. I disagree with Linh's assertion that "an MC never sends ARQ". If I
> am
> > administering an MCU which can initiate conferences by calling up a list
> of
> > participants at a given time, I will certainly require that MCU to apply
> to
> > its gatekeeper for permission to make these calls.
> > In the particular case under discussion, E2/its MC certainly has to send
> > ARQ. It is going to make a call, which will result in data flowing its
> > gatekeeper's zone, and which may end up costing money.
>
> The original idea was that only endpoints send ARQ. An MC is not an
> endpoint, however, it is a
> functional element which can be contained in an endpoint (such is the case
> of an MCU or a terminal
> which contains an MC). So even though the endpoint contains an MC, it is
> the endpoint which is
> sending the ARQ not the MC functional element.
>
> If an MC exists in the Gatekeeper, I do not beleive that that MC will ever
> send ARQ for any of the
> connections in the conference. Only the endpoints in that conference will
> send ARQ to their
> Gatekeepers.
>
>
> 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 at delta-info.com
> ------------------------------------------------------
More information about the sg16-avd
mailing list