Cisco Cisco TelePresence Video Communication Server Expressway 관리 매뉴얼
Call Signaling Optimization
, 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.
handle the signaling.
The Call signaling optimization 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:
path after the call has been set up. The options for this setting are:
■
Off: 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.
■
On: the VCS handles the call signaling when the call is one of:
—
a traversal call
—
an H.323 call that has been modified by Call Policy or FindMe such that:
•
the call resolves to more than one alias
•
the source alias of the call has been modified to display the associated FindMe ID
•
the FindMe has a "no answer" or "busy" device configured
—
one of the endpoints in the call is locally registered
—
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
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.
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
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:
loop detection mode setting, thus saving network resources. The options for this setting are:
■
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:
—
have same call tag
—
are for the same destination alias
—
use the same protocol
—
originate from the same zone
■
Off: the VCS will not detect and fail search loops. You are recommended to use this setting only in advanced
deployments.
deployments.
Identifying Calls
Each call that passes through the VCS is assigned a Call ID and a Call Serial Number. Calls also have a Call Tag
assigned if one does not already exist.
assigned if one does not already exist.
Call ID
The 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.
maximum number of calls allowed on that system.
233
Cisco TelePresence Video Communication Server Administrator Guide
Dial Plan and Call Processing