Cisco Cisco TelePresence Video Communication Server Expressway 관리 매뉴얼
4.
Click Save.
The VCS should connect to the policy service server and start using the service for Call Policy decisions.
Any connection problems will be reported on this page. Check the Status area at the bottom of the page and
check for additional information messages against the Server address fields.
check for additional information messages against the Server address fields.
Supported Address Formats
The destination address that is entered using the caller’s endpoint can take a number of different formats, and this
affects the specific process that the VCS follows when attempting to locate the destination endpoint. The address
formats supported by the VCS are:
affects the specific process that the VCS follows when attempting to locate the destination endpoint. The address
formats supported by the VCS are:
■
IP address, for example
10.44.10.1
or
3ffe:80ee:3706::10:35
■
H.323 ID, for example
john.smith
or
john.smith@example.com
(note that an H.323 ID can be in the form of a URI)
■
E.164 alias, for example
441189876432
or
6432
■
URI, for example
john.smith@example.com
■
ENUM, for example
441189876432
or
6432
Each of these address formats may require some configuration of the VCS in order for them to be supported. These
configuration requirements are described below.
configuration requirements are described below.
Dialing by IP Address
Dialing by IP address is necessary when the destination endpoint is not registered with any system (such as a VCS or
other gatekeeper). See the
other gatekeeper). See the
section for more information.
Endpoints registered to a VCS Expressway
Calls made by dialing the IP address of an H.323 endpoint registered directly with a VCS Expressway are forced to
route through the VCS Expressway. The call will therefore be subject to any restrictions configured on that system.
route through the VCS Expressway. The call will therefore be subject to any restrictions configured on that system.
Dialing by H.323 ID or E.164 Alias
No special configuration is required to place a call using an H.323 ID or E.164 alias.
, applying any transforms and then searching the Local Zone and
external zones for the alias, according to the search rules.
Note that SIP endpoints always register using an AOR in the form of a URI. You are recommended to ensure that
H.323 endpoints also register with an H.323 ID in the form of a URI to facilitate interworking.
H.323 endpoints also register with an H.323 ID in the form of a URI to facilitate interworking.
Dialing by H.323 or SIP URI
When a user places a call using URI dialing, they will typically dial
name@example.com
.
If the destination endpoint is locally registered or registered to a neighbor system, no special configuration is required
for the call to be placed. The VCS follows the usual
for the call to be placed. The VCS follows the usual
, applying any transforms and then searching the
Local Zone and external zones for the alias, according to the search rules.
If the destination endpoint is not locally registered, URI dialing may make use of DNS to locate the destination
endpoint. To support URI dialing via DNS, you must configure the VCS with at least one DNS server and at least one
DNS zone.
endpoint. To support URI dialing via DNS, you must configure the VCS with at least one DNS server and at least one
DNS zone.
Full instructions on how to configure the VCS to support URI dialing via DNS (both outbound and inbound) are given in
the
the
section.
Dialing by ENUM
ENUM dialing allows an endpoint to be contacted by a caller dialing an E.164 number - a telephone number - even if
that endpoint has registered using a different format of alias. The E.164 number is converted into a URI by the DNS
that endpoint has registered using a different format of alias. The E.164 number is converted into a URI by the DNS
207
Cisco TelePresence Video Communication Server Administrator Guide