Alcatel-Lucent omniacces-voip gateway Manual Do Utilizador

Página de 430
  Setup and Installation
Page 4-5
Depending on the dialing scheme selected, some command entries may need to be added 
altogether, such as those required for coding profiles. Other than the minimum configura-
tion entries, there are no visual representations of the default settings in any 
vsmboot.asc
 
file unless they are specifically entered in the file.
All configuration changes must be saved to this modified 
vsmboot.asc
 file or they will not 
take effect. Changes should be made in accordance with the CLI reference instructions in 
Chapter 5, “VoIP Commands.” Optional settings should only be changed if the default 
settings do not apply. Any modifications made through the CLI directly will be lost on 
reboot, as settings contained in the 
vsmboot.asc
 file override all other settings.
 Note 
Once the card has been configured and is operational, 
it can be reconfigured later without rebooting the 
switch using the dynamic reconfiguration feature via 
the 
voice numbering plan activate 
command. See Chap-
ter 5, “VoIP Commands.”
The entries below are not necessarily listed in the order they appear in the master 
vsmboot.asc
 file; to reduce boot time for large files, lines which are commented out (
!
) may 
be removed. Depending on the number of CLI commands in the modified 
vsmboot.asc
 
file, it may take from three to 15 minutes to load depending on the complexity of the 
configuration.
Switch Settings (Required)
• IP address (unique), IP [subnet] mask and the default gateway addresses for 
the voice daughtercard.
 Notes 
A separate routing group just for the VoIP gateway(s) 
must also be created on the switch, and Spanning 
Tree for that group must be turned OFF; see the 
appropriate switch manual for further details on using 
groups and Spanning Tree.
The IP mask and default gateway addresses in the 
vsmboot.asc
 file must match the IP subnet mask and 
the IP broadcast address used in the routing group for 
the VoIP gateway(s).
Alcatel VoIP (
VSD
VSB
VSA
) modules cannot not be 
in a Virtual 
LAN
 (
VLAN
) with non-voice ports (i.e. data 
ports), 
IP
 phone ports, etc. All voice traffic must route 
in and out of the VoIP 
VLAN
.
• voice port interface type (e.g., T1, E1; *required only for digital voice daugh-
tercard)