TANDBERG MSE 8510, MCU 4500 manual use Gateway Cisco GK compatible, which case use MCU compatible

	having specific problems
	using the Cisco Gatekeeper (with or
	without a service prefix), in which case
	use Gateway (Cisco GK compatible)
	using the VCON MXM Gatekeeper
	(with or without a service prefix), in
	which case use MCU (compatible)
	Refer to the list of Frequently Asked Questions
	(FAQ) in the Support section of the web site for
	more details about interoperability with
	gatekeepers.
Whether a call involves consultation with the
configured gatekeeper also depends on the Port A
and Port B settings. For all incoming calls, and
outgoing calls dialed by address rather than by
E.164 phone number, the gatekeeper will be used
to validate the connection only if the network
port over which the connection is made is
selected here.
Specifies an identifier that the MCU can use to	Before the MCU can register any IDs with the
register itself with the H.323 gatekeeper.	H.323 gatekeeper, it must make a unit-wide
	registration.
	This field is required for the gatekeeper
	registration.
	This will have no effect if H.323 gatekeeper usage is
	disabled.
If the configured gatekeeper required password	Note that where password authentication is used,
authentication from registrants, check the Use	the (Mandatory) H.323 ID to register will be used as
password box and type the password.	the username.
Specifies an optional group of digits that are	Conferences and auto attendants registered with a
added to the beginning of each conference or auto	gatekeeper have a Numeric identifier. The numeric
attendant's numeric identifier before registering it	identifier is a unique sequence of digits entered
with the H.323 gatekeeper.	from a video-conferencing endpoint to connect
	directly to the conference or auto attendant. This
	eliminates the need for users to navigate
	additional menus or to know the IP address of the
	MCU.
	To usefully partition the dialing space, you might
	need to ensure that all registrations from a single
	MCU start with the same sequence of digits.
	Using registration prefixes also can benefit large-
	scale dial plan changes. For example, you can
	change all MCU registrations to begin with "121"
	instead of "11" by changing a single MCU
	configuration field rather than individually
	amending every conference or auto attendant's
	120