Cisco Cisco TelePresence Video Communication Server Expressway 관리 매뉴얼
endpoint.
The VCS's behavior as a SIP proxy server is determined by:
■
the SIP registration proxy mode setting
■
the presence of Route Set information in the request header
■
whether the proxy server from which the request was received is a neighbor of the VCS
A Route Set specifies the path to take when requests are proxied between an endpoint and its registrar. For example,
when a REGISTER request is proxied by the VCS, it adds a path header component to the request. This signals that
calls to that endpoint should be routed through the VCS. This is usually required in situations where firewalls exist
and the signaling must follow a specified path to successfully traverse the firewall. For more information about path
headers, see
when a REGISTER request is proxied by the VCS, it adds a path header component to the request. This signals that
calls to that endpoint should be routed through the VCS. This is usually required in situations where firewalls exist
and the signaling must follow a specified path to successfully traverse the firewall. For more information about path
headers, see
.
When the VCS proxies a request that contains Route Set information, it forwards it directly to the URI specified in the
path. Any call processing rules configured on the VCS are bypassed. This may present a security risk if the
information in the Route Set cannot be trusted. For this reason, you can configure how the VCS proxies requests that
contain Route Sets by setting the SIP registration proxy mode as follows:
path. Any call processing rules configured on the VCS are bypassed. This may present a security risk if the
information in the Route Set cannot be trusted. For this reason, you can configure how the VCS proxies requests that
contain Route Sets by setting the SIP registration proxy mode as follows:
■
Off: requests containing Route Sets are rejected. This setting provides the highest level of security.
■
Proxy to known only: requests containing Route Sets are proxied only if the request was received from a
known zone.
known zone.
■
Proxy to any: requests containing Route Sets are always proxied.
In all cases, requests that do not have Route Sets are proxied as normal in accordance with existing call processing
rules. This setting only applies to dialog-forming requests, such as INVITE and SUBSCRIBE. Other requests, such as
NOTIFY, are always proxied regardless of this setting.
rules. This setting only applies to dialog-forming requests, such as INVITE and SUBSCRIBE. Other requests, such as
NOTIFY, are always proxied regardless of this setting.
Proxying Registration Requests
If the VCS receives a registration request for a domain for which it is not acting as a Registrar (the VCS does not have
that SIP domain configured), then the VCS may proxy the registration request onwards. This depends on the SIP
registration proxy mode setting, as follows:
that SIP domain configured), then the VCS may proxy the registration request onwards. This depends on the SIP
registration proxy mode setting, as follows:
■
Off: the VCS does not proxy any registration requests. They are rejected with a “403 Forbidden” message.
■
Proxy to known only: the VCS proxies the request in accordance with existing call processing rules, but only to
known neighbor, traversal client and traversal server zones.
known neighbor, traversal client and traversal server zones.
■
Proxy to any: this is the same as Proxy to known only but for all zone types i.e. it also includes ENUM and DNS
zones.
zones.
If your network is set up to proxy registration requests, we recommend that you disable GRUU on the VCS systems
that are acting as a Registrar for those proxied requests. If GRUU is left enabled, Presence may not work properly for
the proxy registered endpoints.
that are acting as a Registrar for those proxied requests. If GRUU is left enabled, Presence may not work properly for
the proxy registered endpoints.
GRUU can only be disabled via the CLI (
xConfiguration SIP GRUU Mode: Off
).
Accepting proxied registration requests
, you can also
control whether the VCS accepts the registration depending upon the zone through which the request was received.
You do this through the Accept proxied registrations setting when
You do this through the Accept proxied registrations setting when
.
Proxied registrations are classified as belonging to the zone they were last proxied from. This is different from non-
proxied registration requests which are assigned to a subzone within the VCS.
proxied registration requests which are assigned to a subzone within the VCS.
VCS as a SIP Presence Server
The VCS supports the SIP-based SIMPLE protocol. It can act as a Presence Server and Presence User Agent for any
of the SIP domains for which it is authoritative. For full information on how to enable and use the VCS as a SIP
Presence server, see the
of the SIP domains for which it is authoritative. For full information on how to enable and use the VCS as a SIP
Presence server, see the
section.
92
Cisco TelePresence Video Communication Server Administrator Guide