Search results

  1. Fanvil X7 Key tone feedback

    John, thanks for looking. I was not sure if I missed it. Problem is when I misdial....or miss a number. its all good....just learning the new interface. Cheers, Mark

  2. Fanvil X7 Key tone feedback

    I find that when I enter a phone number, there is no audio feedback that I actually touched the key, so I have to stare at the screen to see that I actually pressed the key. Is there anyway to make the number keys give a click or tone sound when you touch them? My old Yealink did.... 18.0...

  3. Solved BLF Function quit with V18 on Yealink

    So, they added Google's servers to the Debian DNS lookup, and then were able to get the license page to work. Several update license selections and I re-provisioned one phone, and it is all working now. Wild times!!! Thanks everyone for your help! Mark

  4. Solved BLF Function quit with V18 on Yealink

    I have the firewall team looking. but doesn't the firewall checker take care of that?

  5. Solved BLF Function quit with V18 on Yealink

    I think that is it. It will not reach activation.3cx.com. I have pinged it from the debian instance that the management console is on, and that works just fine. but the console can not connect.

  6. Solved BLF Function quit with V18 on Yealink

    from the local phone web UI, it shows the phones remain configured for UDP. I don't believe 3CX changed to TLS on me....

  7. Solved BLF Function quit with V18 on Yealink

    Yes, I can pull it using the *20*ext method.

  8. Solved BLF Function quit with V18 on Yealink

    Very interesting! I will check that in a little while....I wonder if V18 turned that on.... I did not change anything other than upgrade to 18 from 16. Thanks! Mark

  9. Solved BLF Function quit with V18 on Yealink

    The extensions all worked with V16 just fine. The new fanvil phones should be here tomorrow, I can try them. The web client, windows app, and I think my android app all work fine for the BLF function. For now my secretary is using the web app to pick up my line when I am out of the office...

  10. Solved BLF Function quit with V18 on Yealink

    updated internal DNS to add FQDN pointing to internal address. should make provisioning easier...but no joy...

  11. Solved BLF Function quit with V18 on Yealink

    Well, got my phone to work. Needed to use the internal address, not the FQDN -- duh... But still have the problem with the BLF keys not working. No lights and can't pick up a call. Can press them to call the assigned extension though.

  12. Solved BLF Function quit with V18 on Yealink

    I am frustrated. so... I ordered Fanvil phones. Your site suggests them. I would love to have my desk phone back. maybe something else is going on. I tried to reset the phone several times, and now I have a phone that can't get service and I cant log into it, since it stays stuck on the bold...

  13. Solved BLF Function quit with V18 on Yealink

    I followed the 3CX info to reload the certs in the Management console only. I just added NTP to Debian. Yes it is a Hyper V server, the normal Network adapter is used, not the Legacy version. The phone time looks exactly like the server time via the Date command. Reset my phone. BLF on 3CX...

  14. Solved BLF Function quit with V18 on Yealink

    Sorry, I should have completed all the info in the format you wanted. I hope this works better for you now. 3CX Version, Professional Annual 18.0 update 1 (build 237) Server OS, Debian 10 Is the 3CX Server Hosted and where? .Virtual server in house on internal network IP Phone...

  15. Solved BLF Function quit with V18 on Yealink

    Upgraded from V16 to 18 (Debian 9 to 10 -upgrade as well....very smooth!) Sunday on my virtual server in house. I have two T27Gs and three T23G phones. Ever since the upgrade the BLF lamps do not work, and we can not use them to pick up another line like we used to. The new windows app works...
3CX Logo Footer Copyright © Sitemap Privacy
Top Bottom