Jump to content

Recommended Posts

Posted
Hello,
Yealink has just released some new products.  We are looking forward to using them and wanted to point them out so they can be added to the advanced provisioner.

We are VERY excited about OPUS support with Yealink and look forward to using it.

With a new firmware update. the WF40 now supports the T46G as well as the T29G. Please note you will need to be on firmware revision xx.81.0.15 for this functionality to work.  It also works with the T48G with firmware 35.80.0.95 or higher.  I believe the WF40 also works on all the new T4S series phones, but I need to double check.

--- begin copy paste ---

The T4S series includes the entry-level T41S and T42S phones, the gigabit color phone T46S, and the gigabit touch screen phone T48S. The series maintains the elegant appearance of the Yealink T4 series and further ensures users a lifelike communication experience, thanks to Yealink Optima HD voice technologies and the addition of Opus -a totally open, highly versatile audio codec. Moreover, the T4S provides enhanced performance and extended hardware functionalities for business customers.

The upgraded T4S series incorporates the latest advanced components for excellent stability and performance. The phone series delivers a remarkable phone experience with an optimized smartphone-like interface. Integrated cutting-edge features, like Wi-Fi and Bluetooth connectivity and rich one-touch soft keys, brings additional convenience and increased productivity for customers. 

Posted
Be advised that the new firmware [81] uses a radically different approach to provisioning than previous versions. It claims to be backward compatible, but (at least for me) I'm having difficulty making it work. I mean, it should simply work as usual, and it's not. I've looked at syslog output and the firmware never checks for the legacy config files.  

However, I setup a sandbox tftp server and been successful in using the new provisioning method, but the configuration restructure is forcing a complete re-write of my scripts. I'm guessing if the backward compatibility is really broken, 2600hz will have to re-write the config templates accordingly.    
Posted
It appears all they really did was introduce a new codec processor to support Opus and minor tweaks to speaker audio quality. I'm sure if they could have gotten away with supporting the entire Opus codec in software there wouldn't be an "S" series. I do hope they provide the limited version of Opus on the T29G.
Posted
I found out today that my distributor is no longer selling T46G's.  I can only get the T46S series as they are no longer manufacturing them.

Can we get some kind of update on whether or not these will be supported in provisioner and when?
  • Administrators
Posted
I'm trying to get ahold of one of the new phones so we can figure out our action plan here. If they've changed the format of the files, it will take us a while to re-test and re-certify the new firmware + config file format. We have to test that ALL functions on the phone work as expect, such as BLF, parking, NAPTR/SRV failover, provisioning via SmartPBX, provisioning via advanced provisioner, network settings, VLAN, line keys, presence/speed dial/BLF programming, etc.

I would expect this will take some time.

There are still a bunch of vendors who are selling T46G's though so I don't think this problem is quite as acute as you're describing. I suspect we have a month or two here before this becomes a huge problem.
Posted
Out of the 3 distributors I called yesterday, 1 is out completely, one had 366, and the other had 50.  

I talked to another one today and they have 22.

I am not sure how quickly these phones sell, but my primary distributor was sold out the first day.  Like you said, we may be able to find some distributors that still have stock, but I am already having to call people we would normally not do business with.
  • Administrators
Posted
Can you tell me where you're getting your information that vendors are running out of the T46s? I just contacted four different vendors and they have a total collectively of over 200 in stock. What am I missing here, where is the urgency coming from?

The announcement originally pasted in this thread is from 5 days ago... I can't imagine all the old inventory just vanishes in 5 days time and we are expected to support the new firmware and configs with 5 days notice.

I can't tell if this is a "we really want this ASAP because we love OPUS" or a "we actually are screwed and can no longer continue selling phones" issue (there's a difference).
Posted
I'm using a T29G for testing with the updated v81 firmware, and although it states to be backwardly compatible with provisioning, it's not working. I've moved to the new process as described in the documentation and that appears to be working. 
Posted
We have a deal for 75 phones coming up right now. To get it done, we are going to have to pull onto two separate vendors to get all t46g. And we are definitely going to get sub optimal pricing because of it. I'm not sure that this is a crisis right now. But, it sure isn't going to be long before it is.

EDIT: to be clear, I am excited about OPUS. But, I certainly don't think it's going to sell any deals.
  • Administrators
Posted
Great, thanks Yealink for all the advance notice.

*grumble grumble*

Let me think about a way to not just fix this problem but avoid it from ever happening again. We really want a firmware selector tool so you can manage which firmware you push to phones. Perhaps we pair that finally with the ability to just edit flat files and upload them. Then you guys can do whatever you want, but of course it means increased support costs if you screw something up. But since we're moving to 100% per-hour support strategy anyway, I think the risk is minimized to us for exposing that level of functionality, so it would make sense to me to just do it at this point.

Last thing I want to do is make it hard to sell our service so it seems like that may be the best path forward.
Posted
I just provisioning a few phones with the new FW,  it's very simple you create one file MACADDRESS.boot  that tells the phone to look for the global and the Mac file,  it looks like this

#!version:1.0.0.1## 
     
include:config <y000000000069.cfg>
include:config "00156xxxxxxx.cfg"
     
overwrite_mode = 1



so each phone has 3 files one is the MACADDRESS.boot   y000000000069.cfg     00156xxxxxxx.cfg

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...