Experts,

8.1.7.3/H.323 states that when Fast Connect is used to establish a call and no initiation of the H.245 procedures took place, the call _may_ be terminated by sending a RELEASE COMPLETE message.

First of all, there is no reference to 8.1.7.3/H.323 in section 8.5/H.323, which describes the call termination procedure. This may lead the reader to believe that the procedures from 8.5/H.323 always apply and that the H.245 procedures must be initiated first (I.e. at a minimum the exchange of the terminal capability sets) to be able to send an EndSessionCommand message.

Secondly, by stating that the call _may_ be terminated by sending a RELEASE COMPLETE message the reader may think that there are other ways of terminating the call. Obviously, there are (as described above, for example), but this would not seem the logical thing to do. Why not state that the call SHALL be terminated by sending a RELEASE COMPLETE message?

Regards,

Frank