Group PJLIB_UTIL_CONFIG¶

group PJLIB_UTIL_CONFIG

Defines

PJ_DNS_MAX_IP_IN_A_REC¶: Maximum number of IP addresses in DNS A response.

PJ_DNS_SRV_MAX_ADDR¶: Maximum server address entries per one SRV record

PJ_DNS_MAX_NAMES_IN_NAMETABLE¶

This constant specifies the maximum names to keep in the temporary name table when performing name compression scheme when duplicating DNS packet (the pj_dns_packet_dup() function).

Generally name compression is desired, since it saves some memory (see PJ_DNS_RESOLVER_RES_BUF_SIZE setting). However it comes at the expense of a little processing overhead to perform name scanning and also a little bit more stack usage (8 bytes per entry on 32bit platform).

Default: 16

PJ_DNS_RESOLVER_MAX_NS¶: Maximum numbers of DNS nameservers that can be configured in resolver.

PJ_DNS_RESOLVER_QUERY_RETRANSMIT_DELAY¶

Default retransmission delay, in miliseconds. The combination of retransmission delay and count determines the query timeout.

Default: 2000 (2 seconds, according to RFC 1035)

PJ_DNS_RESOLVER_QUERY_RETRANSMIT_COUNT¶

Maximum number of transmissions before timeout is declared for the query.

Default: 5

PJ_DNS_RESOLVER_MAX_TTL¶

Maximum life-time of DNS response in the resolver response cache, in seconds. If the value is zero, then DNS response caching will be disabled.

Default is 300 seconds (5 minutes).

See: PJ_DNS_RESOLVER_INVALID_TTL

PJ_DNS_RESOLVER_INVALID_TTL¶

The life-time of invalid DNS response in the resolver response cache. An invalid DNS response is a response which RCODE is non-zero and response without any answer section. These responses can be put in the cache too to minimize message round-trip.

Default: 60 (one minute).

See: PJ_DNS_RESOLVER_MAX_TTL

PJ_DNS_RESOLVER_GOOD_NS_TTL¶

The interval on which nameservers which are known to be good to be probed again to determine whether they are still good. Note that this applies to both active nameserver (the one currently being used) and idle nameservers (good nameservers that are not currently selected). The probing to query the “goodness” of nameservers involves sending the same query to multiple servers, so it’s probably not a good idea to send this probing too often.

Default: 600 (ten minutes)

See: PJ_DNS_RESOLVER_BAD_NS_TTL

PJ_DNS_RESOLVER_BAD_NS_TTL¶

The interval on which nameservers which known to be bad to be probed again to determine whether it is still bad.

Default: 60 (one minute)

See: PJ_DNS_RESOLVER_GOOD_NS_TTL

PJ_DNS_RESOLVER_MAX_UDP_SIZE¶

Maximum size of UDP packet. RFC 1035 states that maximum size of DNS packet carried over UDP is 512 bytes.

Default: 512 byes

PJ_DNS_RESOLVER_RES_BUF_SIZE¶

Size of memory pool allocated for each individual DNS response cache. This value here should be more or less the same as maximum UDP packet size (PJ_DNS_RESOLVER_MAX_UDP_SIZE), since the DNS replicator function (pj_dns_packet_dup()) is also capable of performing name compressions.

Default: 512

PJ_DNS_RESOLVER_TMP_BUF_SIZE¶

Size of temporary pool buffer for parsing DNS packets in resolver.

default: 4000

PJ_SCANNER_USE_BITWISE¶: Macro PJ_SCANNER_USE_BITWISE is defined and non-zero (by default yes) will enable the use of bitwise for character input specification (cis). This would save several kilobytes of .bss memory in the SIP parser.

PJSTUN_MAX_ATTR¶

Maximum number of attributes in the STUN packet (for the old STUN library).

Default: 16

PJ_STUN_MAX_ATTR¶

Maximum number of attributes in the STUN packet (for the new STUN library).

Default: 16

PJ_CRC32_HAS_TABLES¶

Specifies whether CRC32 algorithm should use the table based lookup table for faster calculation, at the expense of about 1KB table size on the executable. If zero, the CRC32 will use non-table based which is more than an order of magnitude slower.

Default: 1

PJ_HTTP_DEFAULT_TIMEOUT¶: Timeout value for HTTP request operation. The value is in ms. Default: 60000ms