Page 83 - Asterisk™: The Future of Telephony

chkconfig command for you so Asterisk and Zaptel will be started automatically upon
system boot. The following shows their usage:

# service zaptel start
# service asterisk start
Each initialization script has several options that can be utilized to control the PBX or
the drivers. Tables 3-2 and 3-3 show the commands run by the script as if you had typed
them into the command-line interface (CLI) yourself:

Table 3-2. Asterisk initialization script options
service asterisk <option> Manual equivalent
start asterisk
stop killproc asterisk
restart stop; start
reload asterisk -rx "reload"
status ps aux | grep [a]sterisk

Table 3-3. Zaptel initialization script options
service zaptel <option> Manual equivalent
start modprobe zaptel; modprobe <module>; /sbin/ztcfg
stop rmmod ztdummy; rmmod zaptel
restart stop; start
reload /sbin/ztcfg

Loading Zaptel Modules Without Scripts

In this section, we’ll take a quick look at how to load the zaptel and ztdummy modules
without the CentOS initialization script. The zaptel module does not require any con-
figuration if it’s being used only for the ztdummy module. If you plan on loading the
ztdummy module as your timing source (and thus, you will not be running any PCI
hardware in your system), now is a good time to load both drivers.

Systems Running udevd
In the early days of Linux, the system’s /dev/ directory was populated with a list of
devices with which the system could potentially interact. At the time, nearly 18,000
devices were listed. That all changed when devfs was released, allowing dynamic cre-
ation of devices that are active within the system. Some of the recently released
distributions have incorporated the udev daemon into their systems to dynamically
populate /dev/ with device nodes.

Loading Zaptel Modules Without Scripts | 55