Configuring H.323; Enabling H.323; Configuring H.323 Ports; Registration Conflict Mode - Cisco TelePresence Administrator's Manual

Grey Headline (continued)
H.323
The H.323 page allows you to enable and disable H.323 system-
wide on the VCS, and configure H.323-specific ports and settings.
To go to the H.323 page:
•
VCS configuration > Protocols > H.323
To configure H.323 using the CLI:
xConfiguration H323
•

Enabling H.323

H.323 support is On by default.
To enable or disable H.323 on the VCS, use the H.323 Mode
setting.

Configuring H.323 ports

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.
You can configure the following H.323 ports:
Registration UDP port
The listening port for H.323 UDP registrations. Default is 1719.
Call signaling TCP port
The listening port for H.323 call signaling. Default is 1720.
Call signaling port range start
Specifies the lower port in the range used by H.323 calls after
they are established. Default is 15000.
Call signaling port range end
Specifies the upper port in the range used by H.323 calls after
they are established. Default is 19999.
The call signalling port range must be great enough to
!
support all the required concurrent calls.
Overview and System
Introduction
status configuration
D14049.08
November 2010

Configuring H.323

Registration conflict mode

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
register using the same alias.
•
A single endpoint has previously registered using a particular
alias. The IP address allocated to the endpoint then changes,
and the endpoint attempts to re-register using the same alias.
You can determine how the VCS will behave in this situation by
configuring the Registration conflict mode. The options are:
Reject: denies the new registration.
Overwrite: deletes the original registration and replaces it with
the new registration.
The default is Reject.

Time to live

H.323 endpoints must periodically re-register with the VCS in
order to confirm that they are still functioning. The VCS allows
you to configure the interval (in seconds) between these re-
registrations, known as the Time to live. The default is 1800.
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.

Call time to live

When the endpoint is in a call, the VCS will periodically poll it
to confirm whether it is still in the call. If the endpoint does not
respond, the call will be disconnected.
The VCS allows you to configure the interval (in seconds) at which
the endpoints are polled, known as the Call time to live. The
default is 120.
The system will poll endpoints in a call regardless of
whether the call type is traversal or non-traversal.
Cisco VCS Zones and Clustering and
configuration neighbors peers

Auto discover

The VCS has an Auto discover setting which determines whether
it will respond to
endpoints. The default is On.
To prevent H.323 endpoints being able to register automatically
with the VCS, set Auto discover to Off. This will mean that
endpoints will be able to register with the VCS only if they have
been configured with the VCS's IP address.

Caller ID

You can specify whether the Caller ID displayed on the
destination endpoint includes or excludes the prefix of the ISDN
gateway when displaying the caller's E.164 number.
Call Bandwidth
processing control
49
CISCO TELEPRESENCE VIDEO COMMUNICATION SERVER
Gatekeeper Discovery Requests
Including the prefix allows the recipient to directly return
the call.
Firewall
Applications Maintenance
traversal
ADMINISTRATOR GUIDE
sent out by
Appendices