I have done this in the past but now that I reinstalled it, it has become unlinked, or so it seems as I need to dial it's public IP to reach it from my ClearSea extensions.
Thank you Marek. The H235 was the key. It didn't work till I registered the MXP to a NTP server!! H.235 on Tandberg requires a time source supplied by a Network Time Protocol (NTP) as part of the authentication process.
UVC ClearSea can act as an H323 Gatekeeper and a SIP Registrar.
You need to create an account for the Team220 in the ClearSea users.
Then go to the Team220 WebUI, and use the Communications/H323 and/or SIP menus to enter the account and server details.
Marek is right, this works on Team 220 fine. Did anyone register a Tandberg MXP 95 successfully? I receive this message when I try to register H323:
H323Gatekeeper [@ status=Rejected ] Address=10.217.25.10 Port=1719 Cause=Security denial Alternates
SIP registration is OK.
H323 registration on UVC ClearSea will only work if you create a ClearSea user account on the server, and use H235 authentication in the H323 settings of the terminal.
UVC ClearSea does not support unauthenticated H323 registrations.
Works. As it turns out the info from the original registration was there but someone had disabled the Gatekeeper authentication. Now it shows up on my ClearSea directory and can be called as a ClearSea extension. Thanks!
Retrieving data ...