Charles,
Wrong in my opinion, but I would hope other experts would express their opinions too! The problem is I'm not sure whether this is a question of understanding or of detailed definition of the phrase "third party" in this context. My understanding of the phrase "third party registration" would be one H.323 entity registering at a gatekeeper on behalf of other H.323 entities. My understanding of the word "registration" of this context is that it can only apply to H.323 entities. In this context the IWF can be considered to be at the extreme edge of the H.323 network, so any "registration" it does is on its own behalf. Maybe what you actually want is some equivalent to the supportedPrefixes that arrived in version 2, for SIP gateways. Whatever we agree you want, though, I think it is worth trying to reach some consensus among experts in this group as to what the phrase "third party" means in this context - as your understanding and mine are clearly in disagreement.
Regards, Chris
"Agboh, Charles" wrote:
Chris,
There are applications where an IWF can register an EP from one domain into another. This allows automatic visibility of EP from one domain from another. In this case the IWF is registering not only itself but other EPs. For this scenario, the third-party entity is the IWF, right?
regards,
charles
-- 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