Hi folks, I think I may have found some incorrect text in H.323 8.1 The same text appears in both V3 and V4 so I suspect nobody has commented before. In the paragraph beginning: "An endpoint shall be capable of sending the Alerting message. ..." it goes on to say: "If an endpoint can respond to a Setup message with a Connect, Call Proceeding, or Release Complete within 4 seconds, it is not required to send the Alerting message. An endpoint sending the Setup message can expect to receive either an Alerting, Connect, Call Proceeding, or Release Complete message within 4 seconds after successful transmission." I believe the first sentence here should really be discussing the requirement to send a Call Proceeding (not Alerting) message. The period of 4 seconds in the last sentence is related to T303 which is specifically terminated by a Call Proceeding message in order to extend the timeout for the sending endpoint. I think the sentence should read: "If an endpoint can respond to a Setup message with a Connect, Alerting, or Release Complete within 4 seconds, it is not required to send the Call Proceeding message." This is then consistent with the use of Call Proceeding described in 8.1.8.2 (second para). Peter Price ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv@mailbag.intel.com
Hi folks,
I think I may have found some incorrect text in H.323 8.1
The same text appears in both V3 and V4 so I suspect nobody has commented before.
In the paragraph beginning: "An endpoint shall be capable of sending the Alerting message. ..."
it goes on to say: "If an endpoint can respond to a Setup message with a Connect, Call Proceeding, or Release Complete within 4 seconds, it is not required to send the Alerting message. An endpoint sending the Setup message can expect to receive either an Alerting, Connect, Call Proceeding, or Release Complete message within 4 seconds after successful transmission."
I believe the first sentence here should really be discussing the requirement to send a Call Proceeding (not Alerting) message. The period of 4 seconds in the last sentence is related to T303 which is specifically terminated by a Call Proceeding message in order to extend
Peter, Alerting was the intent. Call Proceeding not produce a ringing sound in the caller's ear. H.323 devices have to be able to send an Alerting, though they're not required to do so if they can send a Connect within 4 second. The 4 seconds is the T303 timeout and the T303 timer is disabled when receiving Alerting, too... not just Call Proceeding. The ideas are related, but independent. What we have seen some folks do is send a Call Proceeding to the caller and then nothing else until the connect. The result is that the calling party hears silence for a very long time: that's not good. Paul ----- Original Message ----- From: "Peter Price" <PeterP@VEGASTREAM.COM> To: <ITU-SG16@mailbag.cps.INTEL.COM> Sent: Friday, July 20, 2001 6:54 AM Subject: H.323 (8.1) Phase A - Call Setup the
timeout for the sending endpoint.
I think the sentence should read: "If an endpoint can respond to a Setup message with a Connect, Alerting, or Release Complete within 4 seconds, it is not required to send the Call Proceeding message."
This is then consistent with the use of Call Proceeding described in 8.1.8.2 (second para).
Peter Price
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 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
Ah! The reasoning becomes clear - thanks Paul! Nevertheless, Pete is right. Given that the term "endpoints" can include answering machines this needs some careful rewording! Regards, Chris Paul E. Jones wrote:
Peter,
Alerting was the intent. Call Proceeding not produce a ringing sound in the caller's ear. H.323 devices have to be able to send an Alerting, though they're not required to do so if they can send a Connect within 4 second. The 4 seconds is the T303 timeout and the T303 timer is disabled when receiving Alerting, too... not just Call Proceeding.
The ideas are related, but independent. What we have seen some folks do is send a Call Proceeding to the caller and then nothing else until the connect. The result is that the calling party hears silence for a very long time: that's not good.
Paul
----- Original Message ----- From: "Peter Price" <PeterP@VEGASTREAM.COM> To: <ITU-SG16@mailbag.cps.INTEL.COM> Sent: Friday, July 20, 2001 6:54 AM Subject: H.323 (8.1) Phase A - Call Setup
Hi folks,
I think I may have found some incorrect text in H.323 8.1
The same text appears in both V3 and V4 so I suspect nobody has commented before.
In the paragraph beginning: "An endpoint shall be capable of sending the Alerting message. ..."
it goes on to say: "If an endpoint can respond to a Setup message with a Connect, Call Proceeding, or Release Complete within 4 seconds, it is not required to
send
the Alerting message. An endpoint sending the Setup message can expect to receive either an Alerting, Connect, Call Proceeding, or Release Complete message within 4 seconds after successful transmission."
I believe the first sentence here should really be discussing the requirement to send a Call Proceeding (not Alerting) message. The period of 4 seconds in the last sentence is related to T303 which is specifically terminated by a Call Proceeding message in order to extend
the
timeout for the sending endpoint.
I think the sentence should read: "If an endpoint can respond to a Setup message with a Connect, Alerting,
or
Release Complete within 4 seconds, it is not required to send the Call Proceeding message."
This is then consistent with the use of Call Proceeding described in
8.1.8.2
(second para).
Peter Price
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 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
-- Dr Chris Purvis -- Development Manager ISDN Communications Ltd, The Stable Block, Ronans, Chavey Down Road Winkfield Row, Berkshire. RG42 6LY ENGLAND Phone: +44 1344 899 007 Fax: +44 1344 899 001 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv@mailbag.intel.com
Paul- Based on your argument (with which I agree), we should include the Progress message in the list, along with Alerting. That assures some feedback to the user within the 4 seconds. -Bob ---------------------------------------------------- Bob Gilman rrg@avaya.com +1 303 538 3868 "Paul E. Jones" wrote:
Peter,
Alerting was the intent. Call Proceeding not produce a ringing sound in the caller's ear. H.323 devices have to be able to send an Alerting, though they're not required to do so if they can send a Connect within 4 second. The 4 seconds is the T303 timeout and the T303 timer is disabled when receiving Alerting, too... not just Call Proceeding.
The ideas are related, but independent. What we have seen some folks do is send a Call Proceeding to the caller and then nothing else until the connect. The result is that the calling party hears silence for a very long time: that's not good.
Paul
----- Original Message ----- From: "Peter Price" <PeterP@VEGASTREAM.COM> To: <ITU-SG16@mailbag.cps.INTEL.COM> Sent: Friday, July 20, 2001 6:54 AM Subject: H.323 (8.1) Phase A - Call Setup
Hi folks,
I think I may have found some incorrect text in H.323 8.1
The same text appears in both V3 and V4 so I suspect nobody has commented before.
In the paragraph beginning: "An endpoint shall be capable of sending the Alerting message. ..."
it goes on to say: "If an endpoint can respond to a Setup message with a Connect, Call Proceeding, or Release Complete within 4 seconds, it is not required to send the Alerting message. An endpoint sending the Setup message can expect to receive either an Alerting, Connect, Call Proceeding, or Release Complete message within 4 seconds after successful transmission."
I believe the first sentence here should really be discussing the requirement to send a Call Proceeding (not Alerting) message. The period of 4 seconds in the last sentence is related to T303 which is specifically terminated by a Call Proceeding message in order to extend the timeout for the sending endpoint.
I think the sentence should read: "If an endpoint can respond to a Setup message with a Connect, Alerting, or Release Complete within 4 seconds, it is not required to send the Call Proceeding message."
This is then consistent with the use of Call Proceeding described in 8.1.8.2 (second para).
Peter Price
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 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
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv@mailbag.intel.com
Hi Pete (long time, no see!), The sentence "An endpoint shall be capable of sending the Alerting message" is surely bogus. For example in the case of an answering machine there can be no requirement to be capable of sending Alerting - it must be acceptable to make the decision on receipt of the setup message either to accept the call (Connect) or not (ReleaseComplete). Similarly there is no absolute requirement to be able to send CallProceeding. I suggest you formally propose the removal of the offending sentence as an item for the Implementor's Guide. Regards, Chris Peter Price wrote:
Hi folks,
I think I may have found some incorrect text in H.323 8.1
The same text appears in both V3 and V4 so I suspect nobody has commented before.
In the paragraph beginning: "An endpoint shall be capable of sending the Alerting message. ..."
it goes on to say: "If an endpoint can respond to a Setup message with a Connect, Call Proceeding, or Release Complete within 4 seconds, it is not required to send the Alerting message. An endpoint sending the Setup message can expect to receive either an Alerting, Connect, Call Proceeding, or Release Complete message within 4 seconds after successful transmission."
I believe the first sentence here should really be discussing the requirement to send a Call Proceeding (not Alerting) message. The period of 4 seconds in the last sentence is related to T303 which is specifically terminated by a Call Proceeding message in order to extend the timeout for the sending endpoint.
I think the sentence should read: "If an endpoint can respond to a Setup message with a Connect, Alerting, or Release Complete within 4 seconds, it is not required to send the Call Proceeding message."
This is then consistent with the use of Call Proceeding described in 8.1.8.2 (second para).
Peter Price
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv@mailbag.intel.com
-- Dr Chris Purvis -- Development Manager ISDN Communications Ltd, The Stable Block, Ronans, Chavey Down Road Winkfield Row, Berkshire. RG42 6LY ENGLAND Phone: +44 1344 899 007 Fax: +44 1344 899 001 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv@mailbag.intel.com
participants (4)
-
Bob Gilman -
Chris Wayman Purvis -
Paul E. Jones -
Peter Price