Praneeth, Refer to section 8.2.2 of H.323 Version 4. The last paragraph states that the reason should be set to "forwardedElements" as you indicated in your mail. -Manoj -----Original Message----- From: pmreddy@HSS.HNS.COM [mailto:pmreddy@HSS.HNS.COM] Sent: Wednesday, March 14, 2001 9:42 PM To: ITU-SG16@mailbag.cps.INTEL.COM Subject: A problem involving sending fast-start element in a facility message. Hi, I'm stuck with a particular problem, in the implementation of fast-start in the h323v2 implementation. The following are the details. If anybody is certain about the solution please do respond. Consider the scenario in which both calling end-point(A) and called end-point(B) support and prefer fast-start. Calls are gk-routed. A sends Setup message containing a fast-start element, to the Gatekeeper, which fowards it to B. Gatekeeper sends Call-Proceeding to A. B responds to the Setup sent by A, with a Call-Proceeding containing a fast-start element. Now, the Gatekeeper maps the fast-start element to a faststart element in the facility message. NOW, WHAT REASON SHOULD THE FACILITY MESSAGE HAVE?? I feel it should be "forwarded elements". But I am not very sure. If anybody knows about this, please respond immediately. Thanks Praneeth ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 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