EasyManua.ls Logo

Polycom 1725-11530-310 - Page 169

Polycom 1725-11530-310
373 pages
Print Icon
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
Configuration Files
A - 15
Alert Information <alertInfo/>
This configuration attribute is defined as follows:
Request Validation <requestValidation/>
This configuration attribute is defined as follows:
Attribute
Permitted
Values Default Interpretation
voIpProt.SIP.alertInfo.x.value string to
compare
against the
value of
Alert-Info
headers in
INVITE
requests
Null Alert-Info fields from INVITE requests will be
compared against as many of these
parameters as are specified (x=1, 2, ..., N)
and if a match is found, the behavior
described in the corresponding ring class
(refer to Ring type <rt/> on page A-36) will
be applied.
voIpProt.SIP.alertInfo.x.class positive
integer
Null
Attribute
Permitted
Values Default Interpretation
voIpProt.SIP.requestValidation.x.
request
One of:
“INVITE”, “ACK”
, “BYE”
“REGISTER”,
“CANCEL”,
“OPTIONS”,
“INFO”,
“MESSAGE”,
“SUBSCRIBE”
“NOTIFY”,
“REFER”,
“PRACK”, or
“UPDATE”
Null Sets the name of the method for which
validation will be applied.
WARNING: Intensive request validation
may have a negative performance impact
due to the additional signaling required in
some cases, therefore, use it wisely.
voIpProt.SIP.requestValidation.x.
method
Null or
one of: “source”,
“digest” or
“both”/”all”
Null If Null, no validation is done. Otherwise this
sets the type of validation performed for the
request:
source: ensure request is received from an
IP address of a server belonging to the set
of target registration servers;
digest: challenge requests with digest
authentication using the local credentials
for the associated registration (line);
both or all: apply both of the above methods

Table of Contents

Related product manuals