
Setup and Installation
Page 4-4
General Installation Procedures
These instructions apply to all voice daughtercards being installed in either the
OmniAccess 512 and Omni Switch/Router, unless otherwise specified, but are geared toward
setting up an OA 512 voice network using a T1 VSD card as an example configuration. At
least two communicating devices, e.g, two VoIP switches, or a VoIP switch and an OmniPCX
4400, must be configured to provide VoIP. Components required to implement VoIP in the
switch, as described above, must be set up and configured as follows.
1.
Start HyperTerminal or some other terminal emulation program on a workstation
connected to the switch via the console port.
2.
Apply power to switch and watch for switch IP address to be displayed on HyperTermi-
nal. When a message similar to the following appears, write down the displayed IP
address as it will be required for downloading switch files in the next step:
“Configuring default VLAN hostname no-name at addr 127.0.0.0”
3.
Using TELNET or FTP, download all required VoIP files to the switch flash as per the
component table above. Contact customer service if these files cannot be located.
4.
Locate the master
vsmboot.asc
file, and the file for the selected dialing scheme
vsmboot##.asc
[
01-24
] to use as per Chapter 3, “Network Dialing Schemes,” and then copy
the files to a Network Administrator’s workstation connected to the VoIP switch. A dial-
ing scheme must be selected as there is no default dialing scheme in place. Contact
customer service if these files cannot be located.
5.
Insert contents of selected dialing scheme file
vsmboot##.asc
[
01-24
] into master
vsmboot.asc
file above the
“voice daughtercard activate”
line, and then save the master
vsmboot.asc
file by the same name in a different directory so as not to overwrite the origi-
nal master
vsmboot.asc
file. Do not change the name of the filenames, and keep them
lowercase as they are case sensitive. Do not use any type of
view
commands in any VSM
boot files at any time as they may cause the switch to time-out or hang. Refer to Appen-
dix A, “VSM Boot Files,” to see complete boot file examples.
The last two lines of the
vsmboot.asc
file must always be the
“voice daughtercard activate”
line followed by a comment mark (
!
) only on the next line, otherwise the file will not load
properly later. It is important that all entries be kept in the same order in which they appear
in the master
vsmboot.asc
file, as the incorrect order will negatively impact boot time.
For a visual reference, see the example dialing scheme file following these instructions.
Dialing Scheme Example 1 has been selected and used to demonstrate portions of a dial
scheme (
vsmboot01.asc)
merged with the master
vsmboot.asc
file, which was then modi-
fied and saved to create a modified
vsmboot.asc
file.
Multiple dialing schemes can be merged into the master
vsmboot.asc
file, but only the
master boot file (or a modified copy of it) on the flash can be used to configure and boot a
VoIP network. Note that there is no default dialing scheme. A standard text editor may be
used to merge and modify the files (Step 6).
Most CLI configuration data required by the switch to run VoIP are pre-installed as default
settings on the voice daughtercard when the VoIP image file is downloaded to the switch;
as a result, the master
vsmboot.asc
file contains only the minimum configuration data,
namely, commands which must be modified to be enterprise-specific.
6.
Modify the following entries in the merged
vsmboot.asc
file to be enterprise-specific, and
then save the file again; also, be sure to make adjustments relative to standard switch
settings (e.g., slot, port) in any CLI commands in which they are necessary. The default
settings can be changed by entering the appropriate CLI command(s) in the
vsmboot.asc
file
as per Chapter 5, “VoIP Commands.” For assistance when entering certain values such as
slot, port and channel numbers in the command syntax, refer to the configuration table at
the beginning of that chapter.
Summary of Contents for 060170-10
Page 1: ...Part No 060170 10 Rev C April 2004 VoIP User Manual Release 4 5...
Page 4: ...page iv...
Page 14: ...Table of Contents page xiv...
Page 34: ...VoIP and VLANs Page 1 20...
Page 64: ...VoIP Daughtercard Port Numbering Schemes Page 2 30...
Page 424: ...VoIP Commands Page 5 282...
Page 430: ...Page I 6 Index...