Table Of Contents

Appendix L: Server Directives

Appendix L: Server Directives

---

Table 19 Server Directives 

Directive Name	Directive Definition	Valid Directive Values
<ServerRoot>	Directory in which Cisco SPS scripts and executables (bin/), configuration (conf/), and error-log (logs/) files reside. Do not add a forward slash (/) to the end of the directory path.	Default is as follows: Linux: /usr/local/sip Solaris: /opt/sip
LockFile	Path to the lockfile used when Cisco SPS is compiled with either USE_FCNTL_SERIALIZED_ACCEPT or USE_FLOCK_SERIALIZED_ACCEPT. (A lockfile is a type of file that Apache uses to let multiple processes access the same network socket.) You should normally leave this directive at its default value. Change the value, though, if the logs directory is NFS mounted, because the lockfile must be stored on a local disk. For more information on lockfile location, refer to Apache's documentation on this directive at http://www.apache.org/docs/mod/core.html#lockfile. The protocol identifier (PID) of the main server process is automatically appended to the filename.	Default is logs/accept.lock.
PidFile	Path and file where Cisco SPS records its process ID upon startup. A filename that does not begin with a forward slash (/) is assumed to be relative to <ServerRoot>.	Default is logs/sipd.pid.
ScoreBoardFile	Memory-mapped file in which internal server process information is stored. This file is automatically created if your architecture requires it. If the file is automatically created, ensure that no two servers share the same file.	Default is logs/apache_runtime_status.
preforkMPMmodule	Module that implements a nonthreaded, preforking web server for handling requests. This field parameter causes Cisco SPS to monitor child processes and, when necessary, spawn additional child processes to handle incoming SIP requests and responses. If too few requests and responses are being created, Cisco SPS tears down some idle child processes.	Maximum and minimum values for the following prefork MPM module directives depend on your available platform resources. Cisco SPS ignores prefork module directives if the server is run in single-process mode (/sipd -DONE_PROCESS) for debugging purposes. •StartServers—Number of child processes that Cisco SPS creates upon startup. Default is 5. •MinSpareServers—Minimum number of idle child processes (that is, processes that do not handle requests). Default is 5. •MaxSpareServers—Maximum number of idle child processes. Such processes that exceed this number are torn down. Do not set this parameter to a large number. Default is 10.
preforkMPMmodule (continued)		•MaxClients—Number of simultaneous requests that Cisco SPS can support; this number must be no greater than the number of child processes to be created. Default is 20. •MaxRequestsPerChild—Maximum number of requests that an individual child process (process that handles UDP traffic, IPC traffic, and timeouts) can handle during its life. If this number is exceeded, the child process is torn down and replaced by a new child process. This directive limits the amount of memory that processes can consume by accidental memory leakage. Timeouts occur every 50 milliseconds even in the absence of SIP traffic, and the counter is updated. Commonly used value is on the order of hours or days, (100000) or days (1000000). Default is 0 (child process is never torn down).
Listen	List of ports or port and IP address combinations that the server listens to. This directive binds the server to specific IP addresses and specifies whether the server should listen to more than one IP address or port. If you specify only a port, the server responds to requests on all IP interfaces on that port. Valid entries include port and IP:port, but not IP only.	Default is all requests on all IP interfaces. The following are examples of proper syntax: Listen 3000 Listen 10.23.56.78:5060