nonstandardmessage see fig7 for an asn 1 syntax description of the encoded data the nonstandardidentifier of the non standard response message will have the same object identifier as the nonstandard capability which identifies this method note that the called terminal does not include any additional or nonstandard capabilities into the tcs it sends to the calling terminal even if it supports this method the calling terminal must wait to receive either a tcsack or the nonstandardmessage before proceeding the process of setting up an h 324 call between two terminals which support this embodiment of the method of using custom h 245 messages is illustrated in fig3 this embodiment offers one and a half less round trip exchanges than the embodiment of the method of concatenated h 245 capability expressed in the terminalcapabilityset request message this ensures that the called terminal would not malfunction or hang up as it is required to be able to handle the case of a non standard capability being communicated to it the second key aspect is that the encapsulation of the custom message in the terminalcapabilityset request message allows the terminal to transmit the custom message in the first h 245 message after the mobile level determination is done and hence it does not have to wait the third aspect is that the terminalcapabilityset request containing the type ii message embedded as a non standard capability can be transmitted using the type i mode together with one or more h 245 messages the fourth aspect is that the called terminal responds with an ack message that informs the calling terminal of the preferred modes of the called terminal and.