Cisco Cisco TelePresence Video Communication Server Expressway 관리 매뉴얼
Dial plan and call processing
Cisco VCS Administrator Guide (X7.1)
Page 198 of 479
Call signaling configuration
The
Calls
page (
VCS configuration > Calls
) is used to configure the VCS's call signaling functionality.
Call routed mode
Calls are made up of two components - signaling and media. For
, the VCS always handles
both the media and the signaling. For non-traversal calls, the VCS does not handle the media, and may or
may not need to handle the signaling.
may not need to handle the signaling.
The Call routed mode setting specifies whether the VCS removes itself, where it can, from the call
signaling path after the call has been set up. The options for this setting are:
signaling path after the call has been set up. The options for this setting are:
n
Always: the VCS always handles the call signaling. The call consumes either a traversal call license or a
local (non-traversal) call license on the VCS.
local (non-traversal) call license on the VCS.
n
Optimal: the VCS handles the call signaling when the call is one of:
l
a traversal call
l
an H.323 call that has been modified by Call Policy or FindMe such that:
o
the call resolves to more than one alias
o
the source alias of the call has been modified to display the associated FindMe ID
o
the FindMe has a "no answer" or "busy" device configured
l
one of the endpoints in the call is locally registered
l
a SIP call where the incoming transport protocol (UDP, TCP, TLS) is different from the outgoing protocol
In all other cases the VCS removes itself from the call signaling path after the call has been set up. The
VCS does not consume a call license for any such calls, and the call signaling path is simplified. This
setting is useful in a
VCS does not consume a call license for any such calls, and the call signaling path is simplified. This
setting is useful in a
, when used on the directory VCS. In such deployments the
directory VCS is used to look up and locate endpoints and it does not have any endpoints registered
directly to it.
directly to it.
Call loop detection mode
Your dial plan or that of networks to which you are neighbored may be configured in such a way that there are
potential signaling loops. An example of this is a
potential signaling loops. An example of this is a
, where all systems are neighbored
together in a mesh. In such a configuration, if the
are set too high, a single search request may be
sent repeatedly around the network until the hop count reaches 0, consuming resources unnecessarily.
The VCS can be configured to detect search loops within your network and terminate such searches through
the Call loop detection mode setting, thus saving network resources. The options for this setting are:
the Call loop detection mode setting, thus saving network resources. The options for this setting are:
n
On: the VCS will fail any branch of a search that contains a loop, recording it as a level 2 "loop detected"
event. Two searches are considered to be a loop if they meet all of the following criteria:
event. Two searches are considered to be a loop if they meet all of the following criteria:
l
have same call tag
l
are for the same destination alias
l
use the same protocol
l
originate from the same zone
n
Off: the VCS will not detect and fail search loops. You are recommended to use this setting only in
advanced deployments.
advanced deployments.