EasyManua.ls Logo

Alcatel-Lucent 7360 - Sources of SIP Configuration Data; Process for Country-Specific POTS Configuration Files

Alcatel-Lucent 7360
1073 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
5 — VoIP overview
5-20 November 2013 Alcatel-Lucent 7302 ISAM | 7330 ISAM FTTN | 7360 ISAM FX ONT R04.06.02
Edition 01 3FE 55873 AAAA TCZZA
ONT Product Information Guide
Table 5-5 Sources of SIP configuration data
VoIP service configuration is described in subsequent sections as follows:
process for country-specific POTS configuration files
service and protocol configuration
configuration profile (embedded in the software load or FTP download)
iConfig (Sipping) configuration for SIP
VoIP service provisioning parameters
Process for country-specific POTS configuration files
In order for SIP configuration to work correctly in different countries, XML
download files are used. These XML files contain:
CDE data, related to hardware settings specific to a country, such as tone values
and ringing cadences.
SIP provisioning data, related to SIP-specific configuration parameters, allowing
for per-ONT and per-POTS line configurations.
The CDE data is gathered by Alcatel-Lucent and used to generate the XML
download files. The XML download files are shipped with the ONT software. The
XML download files are downloaded to the ONTs, and when the ONT initializes and
the VoIP client is activated, the XML content containing SIP configurations is
loaded into system. Alternately, on OMCIv2 systems, some SIP configurations can
be done using TL1.
Source Description
OMCI OMCI communication is used to conduct service and protocol provisioning. OMCI data
is used to configure the overall VOIP service and individual POTS lines from the OLT.
A limited set of provisioning options for SIP are also provided using OMCI. When using
OMCIv2, additional TL1 provisioning options can be sued. OMCI data is established
using TL1 or SNMP commands at the OLT.
OMCIv1 allows configuration of proprietary options using TL1. OMCIv2 allows
configuration of standards-based VoIP service, POTS line, and SIP commands. Those
SIP commands that cannot be configured using OMCIv2 are listed in Tables 5-10 to
5-14.
OMCIv2 configuration support is available for Release 04.02.02 and later.
DHCP IP addresses that are used for the voice service can be manually selected and
entered or automatically obtained. As an option to manual IP address provisioning,
a DHCP server can be used to automatically obtain IP addresses.
Configuration
profile file
Country-specific parameters are stored in a configuration profile file (XML file) to
allow the VoIP services to be configured for individual countries. Configuration
profile files can be embedded in the software load or obtained by FTP download.
When the configuration profile is downloaded using FTP, it may contain SIP-specific
provisioning parameters.
When using an OLT system that supported OMCIv2, many SIP-specific provisioning
parameters can be configured using standards-based TL1 commands.
iConfig iConfig is an alternative to the configuration profile method of provisioning
SIP-specific parameters at the ONT. The iConfig external server communicates SIP
Provisioning data to ONTs. This process is intended to allow centralized control and
dissemination of provisioning data to multiple SIP devices, such as ONTs. Not
supported on package D or I-240W-S ONTs.

Table of Contents

Related product manuals