HTTP only - Printable Version +- Yealink Forums (http://forum.yealink.com/forum) +-- Forum: IP Phone Series (/forumdisplay.php?fid=4) +--- Forum: T4x Series (/forumdisplay.php?fid=31) +--- Thread: HTTP only (/showthread.php?tid=40738) Pages: 1 2 |
RE: HTTP only - Jazzy - 06-04-2017 10:37 AM (06-02-2017 06:41 PM)ModCraig Wrote: IT was already factory reset with no config... probably not important but you put earlier the IP address of the phone as 192.168.2.107 and then in your pic it shows 192.168.3.0 asking for credentials.. I guess your phone IP has changed and you're maybe using a 255.255.0.0 subnet or something? RE: HTTP only - CWR - 06-04-2017 07:53 PM It does not matter. We are using a /23 scheme. I gave the phone a static IP to see if it would help the situation... an IP that is not part of the DHCP scheme... it did not help... but definitely has to do with the 3cx template. RE: HTTP only - complex1 - 07-23-2017 07:47 PM (06-04-2017 07:53 PM)ModCraig Wrote: It does not matter. Hi Craig, I think this is causing the issue and can be found in the first part of the 3CX template: Code: <interfaceLink>https://admin:%%PHONE_WEB_PASSWORD%%@%%PHONE_IP%%</interfaceLink> RE: HTTP only - Johnson_Yealink - 07-24-2017 10:18 AM Dear Customer, This is Johnson from Yealink technical support team. Nice to work with you. For this issue, would you please provide issue date to us. http://support.yealink.com/faq/faqInfo?id=313 BR Johnson RE: HTTP only - Johnson_Yealink - 07-27-2017 07:51 AM Dear valued Customer, Is there any update regarding this issue? Thanks and looking forward to your reply. BR Johnson RE: HTTP only - complex1 - 07-27-2017 07:55 PM (07-27-2017 07:51 AM)Johnson_Yealink Wrote: Dear valued Customer, Hi Johnson, The issue is caused by the use of the latest 3CX templates 66694 and 66695. If you use the 3CX template 60903 then everything is OK. During the tests the phone was running on firmware version .110 and on .61 (3CX preferred) I am still examine both 3CX templates on differences. RE: HTTP only - justingoldberg - 08-05-2019 02:46 PM I checked by using Chrome's Incognito mode (bypassing local cache and cookies) and I was able to login after upgrading the firmware to newer revisions. I tried to clear out Chrome's cache (three months of cache), however it is still "clearing" as I post this. I tested Incognito on a T42S running v66.84.0.15 and a T54S running v70.84.0.15. |