Charles, All,
Is third party registration supported in H.323 V2, V3, V4?
What's your application?
According to "original intent", the answer is "yes". However this will surprise a lot of people and I doubt you'll find many gatekeepers to support it. It all comes down to a couple of strange-looking "sequence of"s in RRQ. I was reliably informed some time ago that the original intent was that IF RRQ gives more than one callSignalAddresses, it should give the same number of rasAddresses and either none or the same number of terminalAliases. Similarly if giving more than one rasAddress there should be the same number of callSignalAddresses Then the first element in each list maps to the first element of the others, the second to the second etc. My assumption is that RCF or RRJ ought to be sent only to the first rasAddress in the list. However, as I said before, this is an undocumented "original intent", and the ASN.1 that came out of it is far from the best way to achieve it. I don't know if anybody actually handles multiple entries in these fields (apart from terminalAlias) or, if they do, HOW they handle them.
Does anyone out there with a gatekeeper have any input on whether or how they handle this?
Charles,
I'm cross-posting this to the H.323 implementors list - you may get more idea of what's actually implemented from there.
Regards, Chris -- Dr Chris Purvis -- Development Manager ISDN Communications Ltd, The Stable Block, Ronans, Chavey Down Road Winkfield Row, Berkshire. RG42 6LY ENGLAND Phone: +44 1344 899 007 Fax: +44 1344 899 001
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv@mailbag.intel.com