Auto Provision Alcatel Lucent Enterprise (ALE) IP Phone with Yeastar P-Series Software Edition
This topic takes Alcatel Lucent Enterprise M3 (firmware: 2.13.39.000.2217) as an example to describe how to auto provision Alcatel Lucent Enterprise (ALE) IP phone with Yeastar P-Series Software Edition in Local Area Network (LAN).
Requirements
The firmwares of ALE IP phone and Yeastar PBX meet the following requirements.
Model | Phone Requirement | PBX Requirement | Supported Auto Provisioning Method |
---|---|---|---|
H2 | 2.10.00.0001083 or later |
83.6.0.24 or later |
|
H2P | 2.10.00.0001083 or later |
83.6.0.24 or later |
|
H3P | 2.12.43.010.2272 or later |
83.5.0.9 or later |
|
H3G | 2.12.43.010.2272 or later |
83.5.0.9 or later |
|
H6 | 2.12.43.010.2272 or later |
83.5.0.9 or later |
|
M3 | 2.13.37.000.2202 or later |
83.5.0.9 or later |
|
M5 |
2.13.37.000.2202 or later |
83.5.0.9 or later |
|
M7 | 2.13.37.000.2202 or later |
83.5.0.9 or later |
|
M8 | 2.13.32.000.1535 or later |
83.6.0.24 or later |
|
Scenarios
The provisioning methods and operations vary depending on the network environment of ALE IP phone and Yeastar PBX, as the following table shows.
Scenario | Description |
---|---|
IP Phone and PBX are in the SAME subnet | In this scenario, you can provision the ALE IP phone with the
PBX via PnP method. For more information, see Auto provision an ALE IP phone in the same subnet (PnP). |
IP Phone and PBX are in DIFFERENT subnets | In this scenario, you can provision the ALE IP phone with the
PBX via DHCP method. For more information, see Auto provision an ALE IP phone in different subnets (DHCP). |
Auto provision an ALE IP phone in the same subnet (PnP)
In this example, the ALE IP phone (IP: 192.168.28.205
) and the
Yeastar PBX (IP: 192.168.28.39
) are both deployed in subnet 28.
- Prerequisites
-
- Make sure that you have downloaded the template for the desired phone model (Path: ).
- If the IP phone is previously used, you need to RESET the IP phone, then re-configure the network settings for the phone.
- Procedure
-
- Log in to PBX web portal, go to
The IP phones detected by the PBX via PnP are displayed in the phone list.
. - Click beside the ALE IP phone.
- Optional: In the Options section,
select a desired template from the Template
drop-down list.Note: You can select the default template corresponding to the phone model, or customize your own template. For more information, see Create a Custom Auto Provisioning Template.
- In the Assign Extension
section, assign an extension to the IP phone.Note: If your desired extension is not listed in the drop-down list, it indicates that the extension has been associated with an IP phone or gateway.
- To release the extension from the associated IP phone or gateway, see Release an Extension from a Provisioned IP Phone/Gateway.
- To assign the extension to the phone without releasing it from the previously associated device, you can configure the concurrent registration setting for the extension, as the PBX only allows an extension to register with one SIP endpoint by default.
- Click Save.
- Log in to PBX web portal, go to
- Result
-
Note: Some IP phones will reboot automatically. If not, you need to manually reboot the phone to make the configurations take effect.
Auto provision an ALE IP phone in different subnets (DHCP)
In this example, the ALE IP phone and DHCP server are deployed in subnet 20, while
the Yeastar PBX (IP: 192.168.28.110
) is deployed in subnet 28.
- Prerequisites
-
- Make sure that there is only one DHCP server running in the subnet where the IP phone is deployed, or the IP phone would fail to obtain an IP address.
- Make sure that the IP phone and PBX can communicate with each other over the subnets.
- Make sure that you have downloaded the template for the desired phone model (Path: ).
- RESET the IP phone if it is previously used.
- Gather information of IP phone, including Vendor, Model, and MAC address.
- Procedure
- Step 1. Enable Remote Registration feature for the extension on PBX
- Enable the Remote Registration feature for the extension to be assigned to the phone, so that the extension can be registered in a different subnet.
- Step 2. Add the ALE IP phone on the PBX
-
Add the IP phone on PBX. The PBX will generate a configuration file based on the phone's MAC address.
- On PBX web portal, go to .
- Click .
- In the IP Phone section, configure phone
information as follows:
- Vendor: Select Alcatel-Lucent Enterprise.
- Model: Select a phone model. In this example, select M3.
- MAC Address: Enter the MAC address of the IP phone.
- In the Options section, configure the
following settings.
- Template: Select a desired
template from the drop-down list.Note: You can select the default template corresponding to the phone model, or customize your own template. For more information, see Create a Custom Auto Provisioning Template.
- Provisioning Method: Select
DHCP (In the Office).
A provisioning link is automatically generated and displayed in the Provisioning Link field. This provisioning link points to the location where the phone's configuration file is stored.
- Template: Select a desired
template from the drop-down list.
- In the Assign Extension
section, assign an extension to the IP phone.Note: If your desired extension is not listed in the drop-down list, it indicates that the extension has been associated with an IP phone or gateway.
- To release the extension from the associated IP phone or gateway, see Release an Extension from a Provisioned IP Phone/Gateway.
- To assign the extension to the phone without releasing it from the previously associated device, you can configure the concurrent registration setting for the extension, as the PBX only allows an extension to register with one SIP endpoint by default.
- Click Save.
- Step 3. Configure DHCP option 66 on DHCP server
-
In the subnet where the IP phone is deployed, use the generated provisioning link to configure option 66 on the DHCP Server.
- On PBX web portal, copy the provisioning link from the phone's detail page.
- On the DHCP server, set up option 66 with the provisioning
link.
In this example, the configuration is shown below.
- Result
-
Note: Some IP phones will reboot automatically. If not, you need to manually reboot the phone to make the configurations take effect.
- After the IP phone is rebooted, it gets an IP address from the DHCP server, downloads the configurations from the PBX via the provisioning link, and applies the settings automatically.
- The extension is successfully registered on the IP phone. You can check the registration status on on the PBX web portal.