Hi Jan,

Annex M.2 does not seem to provide any standard mechanism for specifying the variant of ISUP that is being tunneled. Therefore ISUP tunneling as currently defined in Annex M.2 will only work properly if both H.323 endpoints are connected to ISUP equipment using the exact same type and version of ISUP. Do you agree?

Assuming that I didn't miss something and this is a valid concern, the addition of type and version fields would solve this problem. I believe Protocol type and version information would be universally useful for all tunneled protocols, so I propose that the tunneledSignallingMessage construct be enhanced to provide fields for protocolType (or maybe it should be called protocolVariant?) and protocolVersion; exact format TBD.

Any comments?

Thanks,

-- Daniel Eskenazi .|. .|. dve@cisco.com OR deskenaz@cisco.com Cisco Systems ..::|::..::|::.. 919-472-3891

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv@mailbag.intel.com