Re: FW: Issue in H.323 robustness not addressed by SCTP/DDP

hi , Please see my comments below: -Archana
I think you are confusing the RELCOMPLETE here with the RELCOMPLETE as used in Q.93B. In H.323 there is no RELEASE message..there is only RELEASE COMPLETE. So in the above example, EP1 is the end that wants to release the call and sends a RELEASE COMPLETE (instead of RELEASE as in Q.93B)and no response is required to this RELEASE COMPLETE. So the moment EP1 's SCTP delivers the RELEASE COMPLETE message to the GK, the EP1 considers the call released. And this is exactly the problem we were trying to point out- the problem of no ACKs. Like you pointed out , if there had been a pair (RELEASE /RELEASE COMPLETE)for every message, the problem would have been sorted out by itself. There are also other H.245 messages which have no ACKs where we will have a similar problem. So we need an ACK for every message at the H.323 layer also. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv@mailbag.intel.com
participants (1)
-
Archana Nehru