We've made it even clearer in v4. Including H.245 and H.225.0 elements.
-----Original Message-----
From: Paul Long [mailto:Plong@SMITHMICRO.COM]
Sent: Saturday, May 20, 2000 5:21 PM
To: ITU-SG16@MAILBAG.INTEL.COM
Subject: Re: On TD26 - Fast TCS and M/S negotiation in H.323v4
Pete,
This is already covered in H.323, so there is no need to say
it again or in
another way. Do you think that the text, below, is deficient
in some way?
Seems pretty clear to me.
8.2.2/H.323v3: "...intermediate entities shall ensure that
H.245 messages
encapsulated in Q.931 messages are forwarded to the other
endpoint even if
the Q.931 message in which the H.245 message is encapsulated would be
consumed and not forwarded to the other endpoint. This is
accomplished by
transferring the encapsulated H.245 message into a Facility
message with the
h323-message-body set to empty."
Paul Long
Smith Micro Software, Inc.
-----Original Message-----
From: Pete Cordell [mailto:pete@TECH-KNOW-WARE.COM]
Sent: Saturday, May 20, 2000 12:57 PM
To: ITU-SG16@MAILBAG.INTEL.COM
Subject: On TD26 - Fast TCS and M/S negotiation in H.323v4
I note that TD-26 has been accepted to show how TCS can be conveyed in
parallel with fast start.
However, the example shows the use of call proceeding for
receiving TCS
back
from the remote endpoint. This is not typically an
end-to-end message,
and
therefore how the procedure works with the gatekeeper routed
model needs
to
be addressed.
Possible solutions are:
1. Refer to the new text that says it is the responsibility of the
gatekeeper to forward any tunnelled message for which none is
available
using FACILITY. (There might be some objection from some to using a
facility message this early in the call setup process though.)
2. Restrict the tunnelling (and probably the fast start info) to
Alerting,
Connect and Facility, which generally are end-to-end. I
believe this is
compatible with the latest procedures for deciding when fast start has
been
ignored.
Which ever option is chosen, it would also be nice to have a
picture for
it
also!
Pete
=============================================
Pete Cordell
pete@tech-know-ware.com
=============================================
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
For help on this mail list, send "HELP ITU-SG16" in a message to
listserv@mailbag.intel.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
For help on this mail list, send "HELP ITU-SG16" in a message to
listserv@mailbag.intel.com
Francois Audet