Alcatel-Lucent omniacces-voip gateway Manuel D’Utilisation

Page 5-2

To use this chapter, refer to the command task list below to find the page number for a 
specific task. The commands use a simple, line-at-a-time prompt and response scheme. The 
CLI interface presents a single prompt character at the beginning of each command line; 
however, this does not apply to the 

file in which there is no response. For details 

on the 

 file and other similar type files, see Chapter 4, “Setup and Installation,” 

which contains an example of a partial VoIP boot file.

♦ Note ♦

Do not use any CLI 

 or 

commands from 

within the aforementioned VSM boot files at any time.

The CLI text-based commands used in VoIP are intended for use by Network Administrators 
and technical staff to configure Alcatel switches for VoIP. Commands are not case sensitive 
unless otherwise stated; however, if a name or string is used in a command it will be case 
sensitive. Commands which may apply to either E1, E1 ISDN PRI, or BRI Euro, are in general, 
collectively referenced in command names under E1.

Typically, command tasks which begin with “specify” have more than two parameters from 
which to choose, whereas command tasks beginning with “set” are generally an either/or type 
command, e.g. 

 or 

.

When entering certain values such as slot, port and channel numbers in the command syntax, 
refer to the configuration table on the following page for valid entries.

VoIP configuration parameters include system-wide configuration as well as per channel, per 
port, and per daughtercard configuration. System-wide configuration includes voice signaling 
interfaces, coding profiles, and the VoIP network interface (including H.323 gateway and 
gatekeeper configuration). Per channel configuration includes general channel and channel-
level telephony signaling configuration.

Coding profiles, in particular, are important parameters that define the way a device such as a 
VoIP H.323 gateway card acts. Once a coding profile is available to a channel in the network, 
it remains in effect until or unless it is made unavailable to the channel. If any individual 
parameter of the profile is modified, it will take effect on all entities to which it had been 
defined until the next time the profile is requested from the voice switching daughtercard. 
Coding profiles are not assigned to a physical entity because the coding profile to be used is 
determined at runtime. If coding profile parameters are changed, the next time a modified 
coding profile is requested by the voice switching daughtercard, the new information will be 
obtained. Coding profiles are also used to associate specific entities (daughtercard with 
channels) on a voice switching daughtercard.

Other voice switching daughtercard parameters may also be applied in a manner similar to 
coding profiles, such as phone groups and numbering plans.

Phone groups and voice numbering plans are used as containers for VoIP gateway operations 
to group parameters so that all related parameters can be referenced (by other commands) 
using a single name, e.g., “topbx”. The phone group or numbering plans must be created 
before parameters can be added to them.

Many other parameters available for configuring VoIP networks are typically used in 
conjunction with Alcatel’s patent-pending Alcatel VoIP Network Dialing Schemes (AVNDS). 
See Chapter 3, “Network Dialing Schemes,” for more information.