Baze Posted February 15, 2019 Report Share Posted February 15, 2019 Hey All - wondering if anyone has come across this one yet. By default, 2600 is set for **+ext to be the "call direct to voicemail" option. On older firmware versions of Yealink this worked fine. After updating to 35.83.0.50, the dial pad now does an IME style thing where it cycles through, so if you hit ** you end up getting a . instead. We've tried modifying the ime.text (language) file to no avail. Got a ticket in with Yealink because at the very least this seems poorly executed or at least should have a config option. Not sure what firmware version the hosted platform runs either. Anyone run across this or have a fix not involving downgrading firmware or manually changing that star code on all clients? Thanks in advance! Quote Link to comment Share on other sites More sharing options...
Baze Posted February 15, 2019 Author Report Share Posted February 15, 2019 Side note - did some firmware testing here, and the issue first appears in the v83 firmware, so don't go past 82.0.30 if you want to avoid this. Quote Link to comment Share on other sites More sharing options...
esoare Posted February 15, 2019 Report Share Posted February 15, 2019 FYI Hosted has the following options(Yealink T42S is what I am looking at) Inherit V82.0.30 Use own firmware (V80 or below) Use own firmware (V81 or above) V82.0.30 V83.0.10 (beta) Quote Link to comment Share on other sites More sharing options...
esoare Posted February 15, 2019 Report Share Posted February 15, 2019 FYI: I tried the **+ext on a T42S running V83.0.10 and the call transfered fine. esoare Quote Link to comment Share on other sites More sharing options...
Baze Posted February 15, 2019 Author Report Share Posted February 15, 2019 Alright, always best to answer my own questions here. - this looks to be ONLY with the T48G and T48S. Here is the config line to fix it: phone_setting.virtual_keyboard.enable = 0 Was a setting added in V83 to allow an english keyboard onscreen. Quote Link to comment Share on other sites More sharing options...
Baze Posted February 15, 2019 Author Report Share Posted February 15, 2019 2 minutes ago, esoare said: FYI: I tried the **+ext on a T42S running V83.0.10 and the call transfered fine. esoare Perfect! Thank you - that definitely reinforces that this looks to just be a T48G/S problem. Phew! Quote Link to comment Share on other sites More sharing options...
esoare Posted February 15, 2019 Report Share Posted February 15, 2019 FTI: Yealink T58v running 58.80.0.40 does NOT have the issue 58.83.0.15 does NOT have the issue The new look to the web-interface is...interesting! ' Thanks for bringing the context to the T48G/S @Baze Quote Link to comment Share on other sites More sharing options...
Baze Posted February 15, 2019 Author Report Share Posted February 15, 2019 oh boy - that is interesting, yeah. Definitely this is the 48 only - here is the line in their changelog: 21. Added the feature of English onscreen keyboard on T48G/T48S IP phone. Quote Link to comment Share on other sites More sharing options...
esoare Posted February 15, 2019 Report Share Posted February 15, 2019 Just now, Baze said: oh boy - that is interesting, yeah. Definitely this is the 48 only - here is the line in their changelog: 21. Added the feature of English onscreen keyboard on T48G/T48S IP phone. (but killed the ** function during in call transfers) Should have added the italics Quote Link to comment Share on other sites More sharing options...
Baze Posted February 15, 2019 Author Report Share Posted February 15, 2019 Ha!!! Yes, you should be a technical writer in your next life. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.