Cisco Cisco TelePresence Video Communication Server Expressway 관리 매뉴얼
51
D14049.08
November 2010
November 2010
Grey Headline (continued)
CISCO TELEPRESENCE
VIDEO COMMUNICATION SERVER
ADMINISTRATOR GUIDE
SIP
The SIP page is used to enable and disable SIP system-wide on
the VCS, and to configure SIP-specific ports and settings.
To go to the SIP page:
the VCS, and to configure SIP-specific ports and settings.
To go to the SIP page:
•
VCS configuration > Protocols > SIP > Configuration
To configure SIP using the CLI:
Enabling SIP
SIP support is On by default.
To enable and disable SIP functionality (i.e. SIP registrar and SIP
proxy services) on the VCS, use the SIP mode setting.
To enable and disable SIP functionality (i.e. SIP registrar and SIP
proxy services) on the VCS, use the SIP mode setting.
SIP registration expiry
SIP endpoints must periodically re-register with the SIP registrar
in order to prevent their registration expiring. The Registration
expire delta setting defines the interval within which SIP
endpoints must register with the VCS. The default is 60.
in order to prevent their registration expiring. The Registration
expire delta setting defines the interval within which SIP
endpoints must register with the VCS. The default is 60.
This applies only to endpoints registered with the VCS. It
does not apply to endpoints whose registrations are
proxied through the VCS.
does not apply to endpoints whose registrations are
proxied through the VCS.
SIP registration proxy mode
This specifies how proxied registrations and requests containing
Route Sets are handled.
Off: registration requests are not proxied (but are still permitted
locally if the VCS is authoritative for that domain). Requests with
existing Route Sets are rejected.
Proxy to known only: registration requests are proxied in
accordance with existing call processing rules, but only to known
neighbor, traversal client and traversal server zones. Requests
containing Route Sets are proxied only if they were received from
a known zone.
Proxy to any: registration requests are proxied in accordance
with existing call processing rules to all known zones. Requests
containing Route Sets are always proxied.
The default is Off.
Route Sets are handled.
Off: registration requests are not proxied (but are still permitted
locally if the VCS is authoritative for that domain). Requests with
existing Route Sets are rejected.
Proxy to known only: registration requests are proxied in
accordance with existing call processing rules, but only to known
neighbor, traversal client and traversal server zones. Requests
containing Route Sets are proxied only if they were received from
a known zone.
Proxy to any: registration requests are proxied in accordance
with existing call processing rules to all known zones. Requests
containing Route Sets are always proxied.
The default is Off.
SIP protocols and ports
The VCS supports SIP over UDP, TCP and TLS transport
protocols. You can configure whether or not incoming and
outgoing connections using each protocol are supported, and if
so, the ports on which the VCS listens for such connections. This
is done using the Mode and Port settings for each protocol.
The default Mode for each protocol is On; the default ports are:
protocols. You can configure whether or not incoming and
outgoing connections using each protocol are supported, and if
so, the ports on which the VCS listens for such connections. This
is done using the Mode and Port settings for each protocol.
The default Mode for each protocol is On; the default ports are:
•
UDP port: 5060
•
TCP port: 5060
•
TLS port: 5061
At least one of the transport protocols must be set to a
Mode of On for SIP functionality to be supported.
Mode of On for SIP functionality to be supported.
You can also specify the range of ports the VCS uses when TCP
and TLS connections are established by configuring the TCP
outbound port start and TCP outbound port end settings.
The default range is 25000 to 29999. This range must be
sufficient to support all required concurrent connections.
and TLS connections are established by configuring the TCP
outbound port start and TCP outbound port end settings.
The default range is 25000 to 29999. This range must be
sufficient to support all required concurrent connections.
Session timers
You can configure SIP session expiry timers through the Session
refresh interval and Minimum session refresh interval settings.
For more information on session timers, refer to
refresh interval and Minimum session refresh interval settings.
For more information on session timers, refer to
.
SIP device interoperability
You can configure the following device interoperability settings:
Require UDP BFCP mode
Controls whether the VCS requires the use of the com.tandberg.
udp.bfcp extension for endpoints that support it.
udp.bfcp extension for endpoints that support it.
Require Duo Video mode
Controls whether the VCS requires the use of the com.tandberg.
.sdp.duo.enable extension for endpoints that support it.
.sdp.duo.enable extension for endpoints that support it.
The default settings for these modes are not supported
by some neighbor systems so make sure you select the
appropriate
by some neighbor systems so make sure you select the
appropriate
when configuring zones.
Configuring SIP
The Domains page lists the SIP domains for which the VCS
is authoritative, and allows you to add, edit and delete SIP
domains.
To go to the Domains page:
is authoritative, and allows you to add, edit and delete SIP
domains.
To go to the Domains page:
•
VCS configuration > Protocols > SIP > Domains.
To configure SIP domains using the CLI:
The VCS will act as a SIP registrar and Presence Server for all
these domains, and will accept registration requests for any SIP
endpoints attempting to register with an alias that includes any
of these domains.
these domains, and will accept registration requests for any SIP
endpoints attempting to register with an alias that includes any
of these domains.
SIP domains