⭐ 欢迎来到虫虫下载站! | 📦 资源下载 📁 资源专辑 ℹ️ 关于我们
⭐ 虫虫下载站

📄 config.h

📁 基于sip协议的网络电话源码
💻 H
字号:
/* $Id: config.h 1033 2007-03-02 14:51:03Z bennylp $ *//*  * Copyright (C) 2003-2007 Benny Prijono <benny@prijono.org> * * This program is free software; you can redistribute it and/or modify * it under the terms of the GNU General Public License as published by * the Free Software Foundation; either version 2 of the License, or * (at your option) any later version. * * This program is distributed in the hope that it will be useful, * but WITHOUT ANY WARRANTY; without even the implied warranty of * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the * GNU General Public License for more details. * * You should have received a copy of the GNU General Public License * along with this program; if not, write to the Free Software * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA  */#ifndef __PJLIB_UTIL_CONFIG_H__#define __PJLIB_UTIL_CONFIG_H__/** * @file config.h * @brief Compile time settings *//** * @defgroup PJLIB_UTIL_CONFIG PJLIB-UTIL Configuration * @ingroup PJLIB_UTIL * @{ *//* ************************************************************************** * DNS CONFIGURATION *//** * 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 */#ifndef PJ_DNS_MAX_NAMES_IN_NAMETABLE#   define PJ_DNS_MAX_NAMES_IN_NAMETABLE	    16#endif/* ************************************************************************** * RESOLVER CONFIGURATION *//** * Maximum numbers of DNS nameservers that can be configured in resolver. */#ifndef PJ_DNS_RESOLVER_MAX_NS#   define PJ_DNS_RESOLVER_MAX_NS		    16#endif/** * Default retransmission delay, in miliseconds. The combination of  * retransmission delay and count determines the query timeout. * * Default: 2000 (2 seconds, according to RFC 1035) */#ifndef PJ_DNS_RESOLVER_QUERY_RETRANSMIT_DELAY#   define PJ_DNS_RESOLVER_QUERY_RETRANSMIT_DELAY   2000#endif/** * Maximum number of transmissions before timeout is declared for * the query. * * Default: 5 */#ifndef PJ_DNS_RESOLVER_QUERY_RETRANSMIT_COUNT#   define PJ_DNS_RESOLVER_QUERY_RETRANSMIT_COUNT   5#endif/** * 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 */#ifndef PJ_DNS_RESOLVER_MAX_TTL#   define PJ_DNS_RESOLVER_MAX_TTL		    (5*60)#endif/** * 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 */#ifndef PJ_DNS_RESOLVER_INVALID_TTL#   define PJ_DNS_RESOLVER_INVALID_TTL		    60#endif/** * 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 */#ifndef PJ_DNS_RESOLVER_GOOD_NS_TTL#   define PJ_DNS_RESOLVER_GOOD_NS_TTL		    (10*60)#endif/** * 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 */#ifndef PJ_DNS_RESOLVER_BAD_NS_TTL#   define PJ_DNS_RESOLVER_BAD_NS_TTL		    (1*60)#endif/** * Maximum size of UDP packet. RFC 1035 states that maximum size of * DNS packet carried over UDP is 512 bytes. * * Default: 512 byes */#ifndef PJ_DNS_RESOLVER_MAX_UDP_SIZE#   define PJ_DNS_RESOLVER_MAX_UDP_SIZE		    512#endif/** * 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 (as a broad guidance, 400 is good for 4 SRV entries). */#ifndef PJ_DNS_RESOLVER_RES_BUF_SIZE#   define PJ_DNS_RESOLVER_RES_BUF_SIZE		    512#endif/** * Size of temporary pool buffer for parsing DNS packets in resolver. * * default: 4000 */#ifndef PJ_DNS_RESOLVER_TMP_BUF_SIZE#   define PJ_DNS_RESOLVER_TMP_BUF_SIZE		    4000#endif/* ************************************************************************** * SCANNER CONFIGURATION *//** * 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. */#ifndef PJ_SCANNER_USE_BITWISE#  define PJ_SCANNER_USE_BITWISE		    1#endif/* ************************************************************************** * STUN CLIENT CONFIGURATION *//** * Maximum number of attributes in the STUN packet. * * Default: 16 */#ifndef PJ_STUN_MAX_ATTR#   define PJ_STUN_MAX_ATTR			    16#endif/** * @} */#endif	/* __PJLIB_UTIL_CONFIG_H__ */

⌨️ 快捷键说明

复制代码 Ctrl + C
搜索代码 Ctrl + F
全屏模式 F11
切换主题 Ctrl + Shift + D
显示快捷键 ?
增大字号 Ctrl + =
减小字号 Ctrl + -