Srini,
This only applies to a Facility message carrying an H.450.1 Supplementary Service APDU, not to Facility messages in general. For example, H.323 does not impose this constraint on Facility/reason=startH245. If an incoming Setup message does not contain an H.245 transport address and does not indicate support for H.245 Tunneling, we immediately send Facility/reason=startH245, even before we send Alerting. This is allowed, and the recipient of this Facility is required to connect on our H.245 transport address.
Paul Long Smith Micro Software, Inc.
-----Original Message----- From: Srini Beereddy [mailto:srini@TRILLIUM.COM] Sent: Tuesday, May 23, 2000 12:28 PM To: ITU-SG16@MAILBAG.INTEL.COM Subject: Re: On TD26 - Fast TCS and M/S negotiation in H.323v4
Pete,
It was specified in section 6.3 of H.450.1 specification
- a FACILITY message shall not be sent if a SETUP message previously sent or received has not been answered.
Srini, Trillium Digital Systems, Inc.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv@mailbag.intel.com