HP-UX C SIP Stack Programmer's Guide (Novembery 2007)

412 HP-UX C SIP Stack Programmer’s Guide
Configuration Parameters
bResolveTelUrls
Indicates that tel: schemes should be resolved by the SIP Stack. Version 4.0
implements the ENUM/TEL URL scheme. If this parameter is set to RV_TRUE,
the SIP Stack will try to resolve tel URLs according to RFC 3764. If this
parameter is set to RV_FALSE, the SIP Stack will call the
RvSipXXXOtherURLAddressFoundEv() callback if the remote address
contains a tel URL scheme.
Note: If you wish the SIP Stack to resolve tel URLs, you should also compile
the SIP Stack with the RV_SIP_TEL_URI_SUPPORT compilation flag.
Default value: RV_FALSE
Remarks: Group A parameter
strDialPlanSufix
A string supplied by the user to indicate the dialing plan DNS suffix. This is the
suffix that will be added for the URI discovery NAPTR query. For example,
“e164.arpa”.
Default value: NULL
Remarks: Group A parameter
E
XTENSION SUPPORT supportedExtensionList
The list of supported option-tags, separated by commas, that are supported by
the SIP Stack. The list will be added to a Supported header for outgoing
messages.
Default Value: NULL (empty list)
Remarks: Group A parameter
rejectUnsupportedExtensions
Indicates whether the SIP Stack should reject unsupported extensions found in
the Require header of a received request. If set to RV_TRUE, such requests will
be rejected with 420 status code.
Default Value: RV_FALSE
Remarks: Group A parameter
addSupportedListToMsg
Indicates whether or not the SIP Stack advertises its supported abilities and adds
a supported header to outgoing messages with the supported list in the header.