Recent content by LiscardGP

  1. IP Phone Guides and Firmware Updates

    Thanks for the prompt reply. As I said, I followed the instructions and it would not auto-provision until DHCP option 66 was specified on the DHCP server.
  2. IP Phone Guides and Firmware Updates

    I was pleased to see that the Yealink T42G is back on the supported list. I followed all the instructions but our T42G's would not auto-provision. It took some time to find the solution which is to set DHCP option 66, on our DHCP server, to provide the provisoning URL. I suggest this step is...
  3. Unable to get FTPES backups working with Filezilla server

    HI I am attempting to implement FTPES backups. I am using a Filezilla server which has been tested using the filezilla client located on an external site. The filezilla client successfully connects to the server using both FTP and FTPES. I have confirmed that the Filezilla client FTPES...
  4. Strange PnP behaviour for Yealink T40G phone taking 4 DAYS to appear in Phones node?

    I have done further testing and it appears the problem has resolved itself, even though there has been no change to the network configuration ! However the Cisco Switch and the Draytek Router were both rebooted in the interim. So it looks like it is just a matter of waiting to see if the...
  5. Strange PnP behaviour for Yealink T40G phone taking 4 DAYS to appear in Phones node?

    Sounds like a job for wireshark installed on the Windows PC running 3CX SBC. Am I correct ? I was hoping to avoid this but your advice to look for SIP SUBSCRIBE will be very helpful. Thank you for your helpful feedback.
  6. Strange PnP behaviour for Yealink T40G phone taking 4 DAYS to appear in Phones node?

    It is a Cisco SPA502G managed PoE switch running with factory default settings. Thank you very much for this very helpful feedback. Much appreciated. I will investigate and reply when I have more information.
  7. Strange PnP behaviour for Yealink T40G phone taking 4 DAYS to appear in Phones node?

    Does anyone have any suggestions why it took 4 DAYS for a correctly configured yealink phone, set to factory defaults, to appear as a new phone in the Phones node? I am looking for a solution because I would like to prevent it occuring again. Background 3CX debian 9, latest stable version...
  8. Solved UK Timezone incorrect

    I have the same problem this morning. I am running in 3CX debian deployed Google cloud. System time is showing correct BST, but 3CX has not changed so office hours still switching status on UTC 0:00
  9. Moving 3CX backups to another provider backups not listed again

    What do you mean as I don't recognise this term? Is the file actually saved in the 3CX backup directory, or is it a link to the file? Given that your new backups are listed normally, then either the previous backup files are not present or it is a pemissions issue as suggested by Rhys. Good luck
  10. Windows 10 SBC uninstall issue - with solution

    Thank you for answering my question. Does this apply to SBC running on other platforms?
  11. Windows 10 SBC uninstall issue - with solution

    Hi During recent testing, during which SBC for windows worked perfectly, I discovered I was not able to reconfigure the SBC. I then tried to uninstall SBC through Wondows control panel and this did not work. It may be worth noting that the original SBC file I downloaded from 3CX immediately...
  12. Incorrect system time after deployment to Google cloud

    SOLVED I decide to take path of least resistance. 1) backed up PBX 2) released FQDN 3) deleted cloud instance 4) Deployed for second time to google cloud 5) restored backup System time correct and 3CX working correctly. Who knows why it happened. I just hope it does not recur!
  13. Incorrect system time after deployment to Google cloud

    OK JohnS_3CX. Try not to be quite so condesending please.:( I have used linux and windows platforms and I am fully aware of the differnce between 3CX and an OS! I have also been using 3CX for about 10 years so I think I have a resonable knowledge base and I am dissapointed by concesending...
  14. Incorrect system time after deployment to Google cloud

    OK . That's a brush off as clearly this is a 3CX issue as I have simply followed the 3CX instructions :) There was no variation from the standard 3CX instructions. Does anyone else have something helpful to add before I start learning debian? :)