Another contribution talked about the gatekeeper using FACILITY whenever a CALL PROCEEDING was received but not available because already sent. We also added some missing fields present in CALL PROCEEDING but not in FACILITY to FACILITY. We could add a reference.
-----Original Message----- From: Pete Cordell [mailto:pete@TECH-KNOW-WARE.COM] Sent: Saturday, May 20, 2000 10:57 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