Configuring H.323 - Cisco TelePresence Administrator's Manual

Protocols

Configuring H.323

The H.323 page (Configuration > Protocols >
including:
whether H.323 is enabled or not
n
H.323 gatekeeper settings
n
whether to insert the prefix of the ISDN gateway into the caller's E.164 number presented on the
n
destination endpoint
The configurable options are:
Field Description
H.323 mode Enables or disables H.323 on
the VCS. H.323 support is On
by default.
Registration The listening port for H.323
UDP port UDP registrations. Default is
1719.
Call The listening port for H.323 call
signaling signaling. Default is 1720.
TCP port
Call Specifies the lower port in the
signaling range used by H.323 calls after
port range they are established. Default is
start and 15000.
end
Registration Determines how the system
conflict behaves if an endpoint
mode attempts to register an alias
currently registered from
another IP address.
Reject: denies the new
registration. This is the default.
Overwrite: deletes the original
registration and replaces it
with the new registration.
Time to live The interval (in seconds) at
which an H.323 endpoint must
re-register with the VCS in
order to confirm that it is still
functioning. Default is 1800.
Cisco VCS Administrator Guide (X8.1.1)
H.323) is used to configure the
Usage tips
The default VCS configuration uses standard port numbers so
you can use H.323 services out of the box without having to first
set these up.
The call signaling port range must be great enough to support all
the required concurrent calls.
An H.323 endpoint may attempt to register with the VCS using
an alias that has already been registered on the VCS from
another IP address. The reasons for this could include:
Two endpoints at different IP addresses are attempting to
n
register using the same alias.
A single endpoint has previously registered using a particular
n
alias. The IP address allocated to the endpoint then changes,
and the endpoint attempts to re-register using the same alias.
Reject is useful if your priority is to prevent two users registering
with the same alias. Overwrite is useful if your network is such
that endpoints are often allocated new IP addresses, because it
will prevent unwanted registration rejections.
Note that in a cluster a registration conflict is only detected if the
registration requests are received by the same peer.
Some older endpoints do not support the ability to periodically re-
register with the system. In this case, and in any other situation
where the system has not had a confirmation from the endpoint
within the specified period, it will send an IRQ to the endpoint to
verify that it is still functioning.
Configuring H.323
H.323 settings on the VCS,
Page 79 of 507