Alcatel-Lucent omniacces-voip gateway User Manual
Setup and Installation
Page 4-7
10. Connect VoIP switch to external components, e.g., OmniPCX 4400, and then set these
devices so that no calls can be processed until setup and installation is complete.
For analog daughtercard (with FXO, FXS module) only; confirm the analog (VSA) daugh-
tercard (North American or European version) being installed is the correct board for the
location in which it will be used, and that the ring cadence is appropriately set for that
location (if necessary, contact Customer Support for further assistance); also, confirm that
all phones/fax machines are connected to the switch (VSA) are on hook. For information
on the ring cadence CLI command, see Chapter 5, “VoIP Commands.”
tercard (North American or European version) being installed is the correct board for the
location in which it will be used, and that the ring cadence is appropriately set for that
location (if necessary, contact Customer Support for further assistance); also, confirm that
all phones/fax machines are connected to the switch (VSA) are on hook. For information
on the ring cadence CLI command, see Chapter 5, “VoIP Commands.”
11. Reapply power to switch to load all contents of the master
vsmboot.asc
file. Watch console
for VoIP error conditions as not all errors display in the error file. For an OA 512, when
the file has completely loaded, the following screen message appears:
the file has completely loaded, the following screen message appears:
“Configuration complete for voice daughtercard in slot 4, submodule 1.”
♦ Notes ♦
The screen message will be different for OSRs depend-
ing on the slot number entered in the modified
vsmboot.asc
file.
The Reboot command is not applicable to VoIP in the
switch. The switch must be powered ON/OFF instead.
switch. The switch must be powered ON/OFF instead.
12. From the console screen, type
ls
at the prompt. Look for any “
vsmboot.asc.[01-99].err
”
files. The list of files that would typically display for the OA 512 are shown below:
oa5.cmd
oa5.cnf
oa5.cfg
mpm.log
oa5isdn.img
oa5diag.img
t1e1drv.img
oa5drv.img
oa5.img
oa5_text_cfg.img
vsoa.img
vsmboot.asc
oa5.cnf
oa5.cfg
mpm.log
oa5isdn.img
oa5diag.img
t1e1drv.img
oa5drv.img
oa5.img
oa5_text_cfg.img
vsoa.img
vsmboot.asc
13. If the error file is listed in addition to the above files, correct the offending CLI
command(s) in the modified master
vsmboot.asc
file, save the file and download it again
to the flash.
14. Turn OFF power to the switch, and then repeat Steps 10 and 11, and if necessary,
Steps 12 and 13.
15. Set VoIP switch, including other digital devices, e.g., OmniPCX 4400, connected to VoIP
switch to route calls to VoIP network. Analog devices should already be set as per Step 9.
Assuming the entire VoIP network and the network dialing scheme (AVNDS) were prop-
erly configured, the VoIP switch is now ready to receive and route calls.
erly configured, the VoIP switch is now ready to receive and route calls.
Instructions for Additional VoIP Installations
VoIP should be setup and installed in another switch in the same manner as described above
with the following main exceptions:
with the following main exceptions:
• Do not download the modified master
vsmboot.asc
file to the next VoIP switch installa-
tion. A copy of that modified boot file should first be created, saved to a different direc-
tory, and then modified to be specific to the next installation.
tory, and then modified to be specific to the next installation.
• All modifications to the master
vsmboot.asc
file must be done before downloading it to the