n
Off
: requests containing Route Sets are rejected. This setting provides the highest level of security.
n
Proxy to known only
: requests containing Route Sets are proxied only if the request was received from a
known zone.
n
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.
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:
n
Off
: the VCS does not proxy any registration requests. They are rejected with a “403 Forbidden” message.
n
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.
n
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.
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.
GRUU can only be disabled via the CLI (
xConfiguration SIP GRUU Mode: Off
).
Accepting proxied registration requests
If the VCS receives a proxied registration request, in addition to the VCS's standard
registration controls
, 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
configuring a
zone
.
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.
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
Presence
section.
Cisco VCS Administrator Guide (X8.1.1)
Page 83 of 507
Protocols
About SIP