Cisco TelePresence Administrator's Manual page 83

Field Description
Standard The minimum allowed value for a SIP registration
registration refresh period for standard registrations. Requests for a
refresh value lower than this will result in the registration being
minimum rejected with a 423 Interval Too Brief response. The
default is 45 seconds.
Standard The maximum allowed value for a SIP registration
registration refresh period for standard registrations. Requests for a
refresh value greater than this will result in a lower value being
maximum returned (calculated according to the Standard
registration refresh strategy). The default is 60
seconds.
Outbound The method used to generate the SIP registration
registration expiry period for Outbound registrations.
refresh
Maximum: uses the lesser of the configured Maximum
strategy
refresh value and the value requested in the
registration.
Variable: generates a random value between the
configured Minimum refresh value and the lesser of
the configured Maximum refresh value and the value
requested in the registration.
The default is Variable.
Outbound The minimum allowed value for a SIP registration
registration refresh period for Outbound registrations. Requests for
refresh a value lower than this will result in the registration
minimum being rejected with a 423 Interval Too Brief response.
The default is 600 seconds.
Outbound The maximum allowed value for a SIP registration
registration refresh period for Outbound. Requests for a value
refresh greater than this will result in a lower value being
maximum returned (calculated according to the Outbound
registration refresh strategy). The default is 3600
seconds.
Cisco VCS Administrator Guide (X7.1)
Usage tips
These options work in the same
manner as for the Standard
registration refresh strategy.
However, Outbound registrations
allow a much higher maximum value
than standard registrations. This is
because standard registrations use
the re-registration mechanism to
keep their connection to the server
alive. With Outbound registrations the
keep-alive process is handled by a
separate, less resource-intensive
process, meaning that re-
registrations (which are more
resource-intensive) can be less
frequent.
Page 83 of 479
Protocols