Paul,
Let me phrase it another way. Are you saying that a v3 EP _must_ support Annex E? Even though an EP indicates that it does not support it in its RRQ, can a GK force it to use Annex E?
Paul Long Smith Micro Software, Inc.
-----Original Message----- From: Paul E. Jones [mailto:paul.jones@TIES.ITU.INT] Sent: Thursday, July 29, 1999 10:59 PM To: ITU-SG16@MAILBAG.INTEL.COM Subject: Re: H.323 Annex E optional?
Paul,
The endpoint does not indicate a preference-- it is to indicate capability.
The gatekeeper may force an endpoint to use Annex E by setting the flag in the RCF.
Paul
Paul,
v3 endpoint do not have to support Annex E-- it is optional.
It would be illegal for the GK to specify the usage of Annex E in the RCF or ACF if the endpoint did not indicate support in the ARQ. Perhaps that needs clarification in the Implementers Guide for v3.
Paul
----- Original Message ----- From: Paul Long Plong@SMITHMICRO.COM To: ITU-SG16@mailbag.cps.intel.com Sent: Friday, July 30, 1999 8:25 PM Subject: Re: H.323 Annex E optional?
Paul,
Let me phrase it another way. Are you saying that a v3 EP _must_ support Annex E? Even though an EP indicates that it does not support it in its
RRQ,
can a GK force it to use Annex E?
Paul Long Smith Micro Software, Inc.
-----Original Message----- From: Paul E. Jones [mailto:paul.jones@TIES.ITU.INT] Sent: Thursday, July 29, 1999 10:59 PM To: ITU-SG16@MAILBAG.INTEL.COM Subject: Re: H.323 Annex E optional?
Paul,
The endpoint does not indicate a preference-- it is to indicate
capability.
The gatekeeper may force an endpoint to use Annex E by setting the flag in the RCF.
Paul
participants (2)
-
Paul E. Jones -
Paul Long