View Full Version : TB GW registration
We have a TB GK in the US and a GW in Trinidad. Every so often the GW will become unresisted to the TB GK and register itself to a GK in Melbourne (non Tandberg). I reboot fixes the problem but I am curious on how to prevent this. I have increased the time to live to 720 seconds do to the distance between the devises. The endpoints and the MCU do not seem to be effected. Does anybody have any ideas what would cause this?
Sean Lessman
01-19-2008, 07:55 AM
We have a TB GK in the US and a GW in Trinidad. Every so often the GW will become unresisted to the TB GK and register itself to a GK in Melbourne (non Tandberg). I reboot fixes the problem but I am curious on how to prevent this. I have increased the time to live to 720 seconds do to the distance between the devises. The endpoints and the MCU do not seem to be effected. Does anybody have any ideas what would cause this?
do you have the gatekeeper settings in the gateway setup for 'auto' or 'manual'?
Sean
Sean Lessman
01-21-2008, 11:00 AM
Do you have an alternate GK address set up in the TANDBERG?
Sean
No. I assume you mean in the GK config. I don't see anyplace in the GW to to add an alternate GK address.
Sean Lessman
01-21-2008, 04:10 PM
No. I assume you mean in the GK config. I don't see anyplace in the GW to to add an alternate GK address.
You don't add it to the GW. You add alternates to the GK config, and the GK gives the alternate addresses to the device upon registration. Check your GK config to see if you have alternates.
Sean
No alternates in the GW config
Sean Lessman
01-21-2008, 05:04 PM
No alternates in the GW config
Understood. How about the Gatekeeper?
Sean Lessman
01-22-2008, 02:29 PM
The only way for the gateway to know there is a 2nd gatekeeper somewhere else to register to is one of two ways:
1. Autodiscovery is turned on (gatekeeper = auto) and the 2nd gatekeeper is reachable through that protocol (multicast).
2. The primary gatekeeper communicates to the gateway that there are alternate gatekeepers available and then the primary gatekeeper fails (even if just for a split second).
You have indicated that neither are true. There is no possible way for the gateway to know about the other gatekeeper unless you tell the gateway about it.
Maybe you should approach the services team at TANDBERG to see if they can look at your configs for you. Right now you seem to have the 'impossible' issue -- which usually means something is being overlooked.
Sean
vBulletin® v3.7.2, Copyright ©2000-2009, Jelsoft Enterprises Ltd.