Cisco Cisco TelePresence Video Communication Server Expressway 관리 매뉴얼
Dial plan and call processing
handle the media, and may or may not need to handle the signaling.
The Call routed mode setting specifies whether the Cisco VCS removes itself, where it can, from
the call signaling path after the call has been set up. The options for this setting are:
the call signaling path after the call has been set up. The options for this setting are:
n
Always: the Cisco VCS always handles the call signaling. The call consumes either a traversal call
license (if it is a traversal call) or a local (non-traversal) call license (if it is not a traversal call) on the
Cisco VCS.
license (if it is a traversal call) or a local (non-traversal) call license (if it is not a traversal call) on the
Cisco VCS.
n
Optimal: the Cisco 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 it resolves to more than
one alias, or has a "no answer" or "busy" device configured
one alias, or has a "no answer" or "busy" device configured
l
one of the endpoints in the call is locally registered
In all other cases the Cisco VCS removes itself from the call signaling path after the call has been
set up. The Cisco VCS does not consume a call license for any such calls, and the call signaling
path is simplified. This setting is useful in a
set up. The Cisco 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 central Cisco
VCS. In such deployments the central Cisco VCS is used to look up and locate endpoints and it
does not have any endpoints registered directly to it.
does not have any endpoints registered 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
there are 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.
resources unnecessarily.
The Cisco VCS can be configured to detect search loops within your network and terminate such
searches through the Call loop detection mode setting. The options for this setting are:
searches through the Call loop detection mode setting. The options for this setting are:
n
On: the Cisco 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:
"loop detected" event. Two searches are considered to be a loop if they:
l
have same call tag
l
are for the same destination alias
l
use the same protocol, and
l
originate from the same zone
Using this setting allows you to save on network resources and fail call branches early where loops
have been detected.
have been detected.
n
Off: the Cisco VCS will not detect and fail search loops. You are recommended to use this setting
only in advanced deployments.
only in advanced deployments.
Note: the loop detection feature was introduced in Cisco VCS version X4. It is only supported in
deployments where all Cisco VCSs are running on X4 software or later.
deployments where all Cisco VCSs are running on X4 software or later.
Identifying calls
Each call that passes through the Cisco VCS is assigned a Call ID and a Call Serial Number. Calls
also have a Call Tag assigned if one does not already exist.
also have a Call Tag assigned if one does not already exist.
Call ID
The Cisco VCS assigns each call currently in progress a different Call ID. The Call ID numbers start
at 1 and go up to the maximum number of calls allowed on that system.
at 1 and go up to the maximum number of calls allowed on that system.
Cisco VCS Administrator Guide (X6)
Page 152 of 295