Terry,
Following that logic, I believe it makes sense to have the desired/needed features in the GRQ. That way, if the GK does not support the needed features, it could chose to not respond or send a GRJ message. The idea, of course, would to put the endpoint into a zone with a GK that supports the needed features.
Paul
----- Original Message ----- From: "Terry L Anderson" tla@LUCENT.COM To: ITU-SG16@mailbag.cps.intel.com Sent: Monday, July 31, 2000 11:21 AM Subject: Re: H.225 white draft - more
as a follow on to my previous question -
It would seem useful to have featureSet in RRQ rather than only in ARQ. This would allow desired and needed Features to be indicated at
registration
time. If the features are needed for all calls and not available this
would
allow determining this before the first call.
And it should be in RCF so that the gatekeeper can indicate to the GW features that it desires or needs. For example, a GW might indicate in
RRQ
that is supports feature "A" and GK might indicate in RCF that feature "A" is needed (thereby indicating that feature-A-specific GenericData should
be
included in ARQs).
featureSet is not currently in either RRQ or RCF, so currently such negotiation can only occur in ARQ/ACF. The later is useful for
negotiating
per-call features, but cannot indicate all-call needs or affect
genericData
to be included in ARQ's.
Terry L Anderson wrote:
I am looking over the "GenericData" related fields in the ASN.1 and saw one asymmetry. Several commands (e.g., Alerting, ARQ, etc) contain featureSet FeatureSet OPTIONAL while Setup contains neededFeatures SEQUENCE OF FeatureDescriptor OPTIONAL, desiredFeatures SEQUENCE OF FeatureDescriptor OPTIONAL, supportededFeatures SEQUENCE OF FeatureDescriptor OPTIONAL, which with the exception of the replacementFeatureSet BOOLEAN is exactly the contents of FeatureSet. Is there a reason for having these separately in Setup rather than having featureSet in Setup?
--
Terry L Anderson mailto:tla@lucent.com Tel:908.582.7013 Fax:908.582.6729 Pager:800.759.8352 pin 1704572 1704572@skytel.com Lucent Technologies/ Voice Over IP Access Networks/ Applications Grp Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974 http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla
--
Terry L Anderson mailto:tla@lucent.com Tel:908.582.7013 Fax:908.582.6729 Pager:800.759.8352 pin 1704572 1704572@skytel.com Lucent Technologies/ Voice Over IP Access Networks/ Applications Grp Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974 http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv@mailbag.intel.com