Installing VOCAL onto a Multihost System

As Table 3-1 showed, VOCAL is scalable and, in a network with 26 hosts or more, can support many thousands of users. Our recommended method for deploying a multihost system is to get VOCAL running on one host as shown in Chapter 2. Then, using your preferred file transfer routine, copy the binaries to the other hosts, edit a configuration file, reprovision some of the servers, and then restart VOCAL. Here is an example set of instructions that uses scp to copy the binaries from host to host. If you prefer to use copy or ftp, it’s up to you.

Assume that there is a network with four hosts named Host1, Host2, Host3, and Host4. In the instructions, we have used the abbreviations for the different server types as they appear in the configuration file.

VOCAL Configuration File

Table 3-2 provides a list of abbreviations found in the /usr/local/vocal/etc/vocal.conf file and their definitions.

Table 3-2. /usr/local/vocal/etc/vocal.conf abbreviations and definitions

Abbreviation

Definition

snmptrapd

Simple Network Management Protocol trap daemon (see Chapter 17)

netMgnt

Network Management Station (see Chapter 17)

vmserver

Voicemail server (see Chapter 14)

hbs

Heartbeat server (see Chapter 17)

fsvm 5110

Voice Mail Feature server (see Chapter 14)

uavm 5170

uavm 5171

uavm 5172

uavm 5173

uavm 5174

Voice Mail User Agents (see Chapter 14)

siph323csgw 5155 5150

SIP H.323 Call Signaling gateway (see Chapter 16)

Get Practical VoIP Using VOCAL now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.