[sunstate]

Got my hands on one, and am looking at deploying about 50 of them pretty quick here. There doesn't seem to be any info on them yet. No template and no guide for manual or auto provisioning. Any idea if it will take a T28 config? I've got it up and running on the system and everything works great, but it's going to suck if I have to manually provision 50 of these things.

[willow]

you could always download the template for the 28 and compare with the 38. I would make a new template and just use that. The yealinks are pretty easy to config so it really should not take that long to config 50. I always run a few tweaks on all phones so that the interface is a little better any ways.

I also come from a voice background so admining 50 phones is reasonable to me

[paul1]

I also have some T38Gs. Even though they are "based on the T28 Feature set" they do not provision the same way.

Pedro from Yealink FAE team expected to have an Auto-Provision Manual available by mid May. I have not seen any updates yet. I have found a few issues with the LDAP directory functions and VLAN operation. In spite of a few rough edges it looks like a great phone.

[mfm]

Hi,

Manually setting them all up might be the easiest way to go.

The second option and the more challenging one is to get a sample provisioning template of these new phones and use Beyondcompare to try and understand where the new values need to be placed.

[paul1]

yealink.ph.T38.zip

Working Yealink T38G Template

(8.85 KiB) Downloaded 268 times

Here is a working draft of my T38G Provisioning Template. I started with the Template for the T28P and worked from there. If you are using any of the EXP3x sidecars you will need to do some more editing in that section. I only created the first few memory buttons.

This template is functional for the features I have tested. Let me know if you find it useful.

Paul

[paul1]

It looks like this has made it to beta. Nice work!

[nbailey]

not sure what the differences are between ours Paul1, if you get time or if you want to as I know you already made your own I am looking at feedback before we add the template. It is a good phone, I like it and I think a lot of folks out there will as well.

Thanks,
Nate

[paul1]

Thanks Nate. I will check it out and give you some feedback. The T38G should be very popular.

[makios]

Thanks Nate. I will check it out and give you some feedback. The T38G should be very popular.

PAUL1, I'm not sure what I'm doing wrong but the T28 went fine. We also have a T38G here, and so i updated the XML to "C:\ProgramData\3CX\Data\Http\Templates\phones" and it sees it in the Phone Provisioning tab under phones, but it is not taking, no matter what i do. Now granted I am new to this, any help would be appreciated, we're planning a rollout of these units very soon.

[mirjam.nz]

Hi Nils

Can you use the BLF keys on the T38G to do a Blind transfer ?

Cheers
Mirjam

[paul1]

I think the T38G still has trouble getting the provisioning address from DHCP etc. If you login to the phone's web interface and go to Phone -> Auto Provision and update the Server URL. It should look something like: http://192.168.xxx.xxx:5000/provisioning/

You may also want to click the Check New Config option to "On".

Once this is done it should be able to read it's configuration file on bootup.

[paul1]

I have noticed that my template forces the phone to ignore the user's ring tone settings.

Here are some changes I would make to the template. (Nate - I think you have the same settings.)

This line is just under the Account section and should be changed as follows:
RingTone.RingType = ring1.wav ----< Change to:>---- RingTone.RingType = common

This line is in the PhoneSetting section:
PhoneSetting.Ringtype = Ring1.wav ----< Change to:>---- #PhoneSetting.Ringtype = Ring1.wav

After these changes ring tones should work as expected.

[1tb]

Been quite a few months since this phone was released and now there is another gigabit colour Yealink model- the T32G. Still no autoprovisioning from 3CX for these new phones.

Any ideas when these new phones will get auto provisioning- my client is asking why he pays for upgrade insurance if it takes such a long time for his phones to be supported by 3CX.

The template doesn't work properly for us- throws the following error when adding new extension:

3CX Interface: An exception occurred EditExtension Error: Unknown variable %%payload1%% in template.

Anyone

[nbailey]

One thing you need to consider is that we don't generally get every model of phone for testing that manufacturers produce.
with this in mind we do what we can when we have the information at hand and the device in our testing lab. Just because a supported manufacturer creates a new model phone doesn't always mean we will support it right away. In fact the T38 is not fully supported yet. There is more behind the scene work that needs to be done in cases like this and when we are confident the phone works as intended with 3CX we release a template and support the phone fully. Until then it is as it is and you will have to manually provision it.

Thanks,

Nate

[sunstate]

How come we still don't have a template for the T38G/T32G? I already did one deployment of 75 T38's and am looking at a deployment of 75 T32's right now. It would be nice if I could provision these properly via 3CX.