Hello, First time poster. Newb on 3CX and SIP telephony in general, but highly experienced techie. Wondering if someone can suggest ideas for the following issues experienced after a 12.5 to 14 to 15 upgrade (quite rapidly). 12.5 was supplied by a vendor (before my time), and the company had been dissatisfied with it when I joined (on many levels). I was asked if I can tighten up the installation, and get it to do what they wanted -- chiefly, enable softphones (and smartphone clients) to be able to make and receive calls remotely. Well, solved that fairly quickly through the upgrade to V15, and by utilizing V15's free FQDN, and managing all the respective network requirements (NATing, port forwarding, firewall rules, etc.) However, here are the two issues being confronted now: 1. Our installation is currently V15.0.0, and its license (8SC) is active - with maintenance valid until Nov 2017 - however, there appears no way in the GUI to update to SP1. The updates notifications shows many available updates, one of which is NOT the update to SP1. I've tried clearing the browser cache, etc... but to no avail. I am not having any trouble updating phone firmwares - that works well - I am just unable to have the system present SP1 as an available update... 2. After the move to V15, phones no longer show caller ID properly - meaning, Caller ID DOES work from extension to extension, but when calls originate from an external source, and come through a Patton 4112 (2 port FXO) - then Caller ID DOES NOT show on the terminating extensions... Here's what's going on within 3CX Call Log, the number shows correctly like this... (for example - the 'x' are used by me to masquerade the number) In other words, in the call log - the number appears correctly -- meanwhile, at an extension: If it's a soft-phone (such as the iOS 3CX client) it shows as - (without the number, but with correct date, timestamp below) whereas, if it's a SIP handset (that has either answered or missed a call from an external number) it shows no corresponding call in its Call History -- confirmed across Fanvil and Cisco handsets that are up to date with firmware, and provisioned by the 3CX system successfully. Any solutions, help or suggestions tremendously appreciated. Gratitude in advance.