Configuring Sip Domains; Configuring Sip And H.323 Interworking; Searching By Protocol - Cisco TelePresence Video Communication Server Administrator's Manual

Field Description
Require Controls whether the VCS requires the use of the
UDP BFCP com.tandberg.udp.bfcp extension for
mode endpoints that support it.
Require Controls whether the VCS requires the use of the
Duo Video com.tandberg.sdp.duo.enable extension for
mode endpoints that support it.

Configuring SIP domains

The Domains page (VCS configuration > Protocols > SIP >
which the VCS is authoritative. The VCS will act as a SIP Registrar and Presence Server for these
domains, and will accept registration requests for any SIP endpoints attempting to register with an
alias that includes these domains.
The domain name can comprise multiple levels. Each level's name can only contain letters, digits and
hyphens, with each level separated by a period (dot). A level name cannot start or end with a hyphen,
and the final level name must start with a letter. An example valid domain name is 100.example-
name.com.

Configuring SIP and H.323 interworking

The Interworking page
whether or not the VCS acts as a gateway between SIP and H.323 calls.
The VCS is able to act as a gateway between SIP and H.323, translating calls from one protocol to the
other. This is known as "interworking".
By default, the VCS acts as a SIP-H.323 and H.323-SIP gateway but only if at least one of the
endpoints that are involved in the call is locally registered. You can change this setting so that the
VCS will act as a SIP-H.323 gateway regardless of whether the endpoints involved are locally
registered. You also have the option to disable interworking completely.
The options for the H.323 <-> SIP interworking mode are:
Off: the VCS will not act as a SIP-H.323 gateway.
n
Registered only: the VCS will act as a SIP-H.323 gateway but only if at least one of the endpoints is
n
locally registered.
On: the VCS will act as a SIP-H.323 gateway regardless of whether the endpoints are locally
n
registered.
You are recommended to leave this setting as Registered only (where calls are interworked only if at
least one of the endpoints is locally registered). Unless your network is correctly configured, setting it
to On (where all calls can be interworked) may result in unnecessary interworking, for example where
a call between two H.323 endpoints is made over SIP, or vice versa.

Searching by protocol

When searching a zone, the VCS will first perform the search using the protocol of the incoming call. If
the search was unsuccessful the VCS may then search the zone again using the alternative protocol,
depending on where the search came from and the Interworking mode.
If the request has come from a neighboring system and Interworking mode is set to Registered
n
only, the VCS will search the local zone using both protocols, and all other zones using the native
Cisco VCS Administrator Guide (X6.1)
(VCS configuration > Protocols >
Usage tips
The default settings for these
modes are not supported by
some neighbor systems so
make sure you select the
appropriate zone profile
configuring zones.
Domains) lists the SIP domains for
Interworking) lets you configure
Protocols
when
Page 62 of 401