How to configure T3 Series for 3CX
This guide applies to v15 only.
On this topic
Supported Models Yealink T3 series (End Of Life)
- Yealink T32G - final firmware version 188.8.131.52
- Yealink T38G - final firmware version 184.108.40.206
Step 1: Upgrade to Minimum required firmware
Check that the phone is running the minimum required firmware described above. Read how to check what firmware the phones are running and how to upgrade them in this guide: How to manual upgrade Yealink IP phones.
Step 2: Factory Reset the IP Phone
Before provisioning the IP phone, the phone must be brought back to factory defaults in case the device has residual settings of a previous configuration. To reset the device read our how to factory Reset Yealink Phones document.
Step 3: Provision the phone
There are several methods to provision a phone:
- Plug & Play - For phones on the local LAN or behind the 3CX SBC.
- Manual Provisioning - For phones on remote networks that will connect directly to 3CX and use STUN.
For more information, see “When can I use which provisioning method?”
Local LAN or SBC: Provision via Plug’n’Play
- Connect the phone to the network. A PnP request will be sent automatically to 3CX.
- Go to the 3CX Management Console ⇒ “Phones” page. The new phone will be marked in Bold.
- Click on the BOLD entry and choose between “Assign Ext” or “Add Ext”, depending on whether you want to assign the phone to an existing extension or create a new one.
- All major provisioning settings are pre-populated. If your PBX has multiple network cards, select to which network this IP phone is connected.
- Click “OK”. The phone will configure automatically and will reboot to finalize the setup.
Remote phones: Provision with the Manual Provisioning Link
In order to provision the device for STUN (Teleworker) usage, the device must be provisioned using the Manual Link Provisioning method outlined here.
Important note about BLF Layout
All Yealink phone devices’ BLF keys are mapped to allocate the first two keys (wherever they are) as the line keys. The rest of them can be configured from the 3CX Management Console as desired.
- End Of Life models:
- No support for CTI via uaCSTA
- No direct UI login
- No support for “Let’s encrypt”
(certificate check needs to be disabled manually if used as remote extension)
- No RPS Support