Cisco Cisco TelePresence Video Communication Server Expressway 관리 매뉴얼
Field
Description
Usage tips
Registration
conflict
mode
conflict
mode
Determines how the system
behaves if an endpoint
attempts to register an alias
currently registered from
another IP address.
behaves if an endpoint
attempts to register an alias
currently registered from
another IP address.
Reject: denies the new
registration. This is the
default.
registration. This is the
default.
Overwrite: deletes the original
registration and replaces it
with the new registration.
registration and replaces it
with the new registration.
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:
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.
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.
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.
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.
registration requests are received by the same peer.
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.
which an H.323 endpoint
must re-register with the VCS
in order to confirm that it is
still functioning. 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.
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.
Note:
By reducing the registration time to live too much, you risk
flooding the VCS with registration requests, which will severely
impact performance. This impact is proportional to the number of
endpoints, so you should balance the need for occasional quick
failover against the need for continuous good performance.
impact performance. This impact is proportional to the number of
endpoints, so you should balance the need for occasional quick
failover against the need for continuous good performance.
Call time to
live
live
The interval (in seconds) at
which the VCS polls the
endpoints in a call to verify
that they are still in the call.
Default is 120.
which the VCS polls the
endpoints in a call to verify
that they are still in the call.
Default is 120.
If the endpoint does not respond, the call will be disconnected.
The system polls endpoints in a call regardless of whether the call
type is traversal or non-traversal.
type is traversal or non-traversal.
Auto
discover
discover
by endpoints. The default is
On.
On.
To prevent H.323 endpoints being able to register automatically with
the VCS, set Auto discover to Off. This means that endpoints can
the VCS, set Auto discover to Off. This means that endpoints can
only register with the VCS if their Gatekeeper Discovery setting is
Manual and they have been configured with the VCS’s IP address.
Caller ID
Specifies whether the prefix
of the ISDN gateway is
inserted into the caller's
E.164 number presented on
the destination endpoint.
of the ISDN gateway is
inserted into the caller's
E.164 number presented on
the destination endpoint.
Including the prefix allows the recipient to directly return the call.
About SIP
The VCS supports the SIP protocol. It can act as a SIP registrar, SIP proxy and as a SIP Presence Server.
The VCS can provide interworking between SIP and H.323, translating between the two protocols to enable
endpoints that only support one of these protocols to call each other.
endpoints that only support one of these protocols to call each other.
To support SIP:
101
Cisco TelePresence Video Communication Server Administrator Guide
Protocols