Cisco Cisco TelePresence Video Communication Server Expressway 관리 매뉴얼
For H.323, the hop count only applies to search requests. For SIP, the hop count applies to all requests sent to a zone
(affecting the Max-Forwards field in the request).
(affecting the Max-Forwards field in the request).
The hop count value can be between 1 and 255. The default is 15.
Note:
if your hop counts are set higher than necessary, you may risk introducing loops into your network. In these
situations a search request will be sent around the network until the hop count reaches 0, consuming resources
unnecessarily. This can be prevented by setting the
unnecessarily. This can be prevented by setting the
to On.
When dialing by URI or ENUM, the hop count used is that for the associated DNS or ENUM zone via which the
destination endpoint (or intermediary SIP proxy or gatekeeper) was found.
destination endpoint (or intermediary SIP proxy or gatekeeper) was found.
Configuring hop counts for a zone
Hop counts are configured on a zone basis. To configure the hop count for a zone:
1.
Go to the Zones page (Configuration > Zones > Zones).
2.
Click on the name of the zone you want to configure. You are taken to the Edit zone page.
3.
In the Configuration section, in the Hop count field, enter the hop count value you want to use for this zone.
section.
Configuring Dial Plan Settings
The Dial plan configuration page (Configuration > Dial plan > Configuration) is used to configure how the VCS
routes calls in specific call scenarios.
routes calls in specific call scenarios.
The configurable options are:
Field
Description
Usage tips
Calls to
unknown IP
addresses
unknown IP
addresses
Determines the way in which the VCS attempts to call systems
which are not registered with it or one of its neighbors.
which are not registered with it or one of its neighbors.
Direct: allows an endpoint to make a call to an unknown IP
address without the VCS querying any neighbors. The call
setup would occur just as it would if the far end were
registered directly to the local system.
address without the VCS querying any neighbors. The call
setup would occur just as it would if the far end were
registered directly to the local system.
Indirect: upon receiving a call to an unknown IP address, the
VCS will query its neighbors for the remote address and if
permitted will route the call through the neighbor.
VCS will query its neighbors for the remote address and if
permitted will route the call through the neighbor.
Off: endpoints registered directly to the VCS may only call an
IP address of a system also registered directly to that VCS.
IP address of a system also registered directly to that VCS.
The default is Indirect.
This setting applies to the call's
destination address prior to any
zone transforms, but after any
pre-search transforms, Call
Policy or User Policy rules have
been applied.
destination address prior to any
zone transforms, but after any
pre-search transforms, Call
Policy or User Policy rules have
been applied.
In addition to controlling calls,
this setting also determines the
behavior of provisioning and
presence messages to SIP
devices, as these messages are
routed to IP addresses.
this setting also determines the
behavior of provisioning and
presence messages to SIP
devices, as these messages are
routed to IP addresses.
for more information.
Fallback alias
The alias to which incoming calls are placed for calls where
the IP address or domain name of the VCS has been given but
no callee alias has been specified.
the IP address or domain name of the VCS has been given but
no callee alias has been specified.
If no fallback alias is configured,
calls that do not specify an alias
will be disconnected. See below
for more information.
calls that do not specify an alias
will be disconnected. See below
for more information.
About the Fallback Alias
The VCS could receive a call that is destined for it but which does not specify an alias. This could be for one of the
following reasons:
following reasons:
185
Cisco TelePresence Video Communication Server Administrator Guide