Min-Size; Allow-Strict - Yamaha CS-700 Series Integrators Reference Manual

min-size

Description: Use compact SIP message format. The SIP protocol specifies that header field names can be
in the full name form or in the abbreviated form. Abbreviated form is useful when
messages might be too large to be carried on the available transport, for example when
exceeding UDP's Maximum Transmission Unit (MTU). Enable this option to encode SIP
headers in their short forms to reduce size. By default, the option is not enabled and SIP
headers in outgoing messages will be encoded in their full names. (See SIP protocol
standard, IETF RFC 3261.)
Property Actions: set, get, notify
Default Value: 0
Command Definition:
Action Definition
get
get min-size
response val min-size <0|1>
set set min-size <0|1>
notify notify voip.min-size <0|1>
Parameters:
Parameter Description
0
Do not use compact format
1
Use compact format.
CLI Format Examples:
get min-size
val min-size 0
set min-size 0
notify voip.min-size 0
Supported Products: CS700-SP
Available in API Version: 1.1

allow-strict

Description: Allow strict routing for SIP registration proxies. By default, proxies specified for SIP
registration will be configured as loose-routing proxies. The loose-routing designation will
be automatically appended to each proxy address when the proxy is added to the SIP Route
header. Older proxies may be strict-routing (see IETF RFC 2543), not supporting loose
routing (see IETF RFC 3261). Enable this option if you are using strict-routing proxies. If this
option is enabled and you are specifying one or more loose-routing proxies in the Proxy
field, then you must manually add the suffix to each loose-routing proxy address. For
example, "10.134.123.101;lr".
Property Actions: set, get, notify
Yamaha CS-700 Integrators Reference Guide 115