Henri,

Check the file h225v3b at the avc-site - a set bitstring exists in the EndpointType structure, but there is no longer a set boolean in the TerminalInfo structure.

I apologize for the confusion. The file h225v3 is the white draft I sent to the ITU in June. h225v3wcm shows the differences between h225v3 and H.225.0 V2. The file h225v3b contains corrections to h225v3 (these corrections will appear as a contribution in the special September SG16 session where V3 is scheduled for decision). The file h225v3bcm highlights the changes between h225v3 and h225v3b.

Glen

henri.maenpaa@NOKIA.COM wrote:

All,

There seems to be redundant information in the endpointType IE concerning SETs. Hopefully this has just been left there accidentally from the earlier versions of H.225v3 drafts. Could someone clarify:

First, endpointType can have set "bitmask" octet string along with terminal or gateway structures. OK. Then, if terminal was chosen for endpointType, terminalInfo specifies (again) being a SET with a boolean value. I think this should be removed. If there is some reason for including it there, then shouldn't it be included into gatewayInfo struct as well?!?

-Henri Mäenpää, Nokia Wireless Business Communications

---

Part 1.2 Type: application/ms-tnef Encoding: base64

-- Glen Freundlich ggf@lucent.com Lucent Technologies office: +1 303 538 2899 11900 N. Pecos fax: +1 303 538 3907 Westminster, Colorado 80234 USA