In the config file, I could see the below: <deviceSecurityMode>1</deviceSecurityMode> Is this a secure cluster ? If so the phone needs to get CTL file. From whatever we could see in your attached captures , it seems like the phone requests for CTL file but not getting it and only getting an ITL. COuld you confirm whether this cluster is indeed secure and the phone got CTL file ? IF not try resetting security settings on the phone once. HTH Rajan Pls rate all useful posts by clicking the star below ... View more

I believe that is needed to get any support for licenses and to contact Global licensing team for any issues. HTH Rajan Pls rate all useful posts by clicking the star below ... View more

Hi Tony, "a=sendonly" usually will be sent for MOH during transfer and since you have the same codec specified throughout the call path, I think this is negotiated for the call leg involving MOH device and not for the actual call. you can check these configuration. HTH Rajan Pls rate all useful posts by clicking the star below ... View more

Hi Giuseppe, Please press the settings button on any phone and see whether the phones has got the required configuration (Primary, secondary CallManager). If not, check the status messages on the phone and if you see any errors related to ITL file once. HTH Rajan Pls rate all useful posts by clicking the star below ... View more

Hi Carl, It actually depends on how the configuration is. If you want to use the local route group first and then use the other ISDN gateway as the secondary option, you can create a Route list with the route group "Standard Local Route Group" as the first option and RG containing the other gateway as the second option in the list. If you have 9.@ route pattern pointed to this RL, then it will use the local RG pointed in the site's DP for all outbound calls. But if you have 9.@ route directly pointed to your ISDN gateways, then that will be used and not the local RG pointed in the DP. HTH Rajan Pls rate all useful posts by clicking the star below ... View more

Hi Amir, You can refer the below document to get info reg the certificates : https://www.cisco.com/c/en/us/support/docs/unified-communications/unified-presence/116917-technote-certificate-00.html#anc3 HTH Rajan Pls rate all useful posts by clicking the star below ... View more

Hi Mohamed, Can you confirm with provider that all parameters used are correct (username, password and other config) and also to check on their end what is the error they are getting. HTH Rajan Pls rate all useful posts ... View more

In any case, you need to rerun the CTL after renewing the expired certificates so that the CTL file will have signatures of all new certs. Since you dont have the CTL token, you can regenerate all expired certs without any issues if you are ready to run the cluster in nonsecure mode. If you are ok with that, you can disable security for the CUCM cluster and use the "Prepare cluster for pre CM-8.0 rollback" Enterprise Parameter so that all phones will get a blank ITL file and trust everything. YOu can regenerate all expired certs and restart required services. Once you complete this for all servers, you can change the enterprise parameter back for the phones to get new ITL file to trust and register. HTH Rajan Pls rate all useful posts by clicking the star below ... View more

Hi Noa,   You can find this option by navigating to System --> Service Parameters --> Select the server --> Select "Cisco CallManager service and searching for "Drop Ad Hoc Conference" parameter.   HTH Rajan Pls rate all useful posts by clicking the star below     ... View more

Hi Cristian, You need to check the status of all activated services on that subscriber. Also you could pull the below logs for that server from RTMT to check for any other alarms: Event viewer - application logs Event viewer - system logs HTH Rajan Pls rate all useful posts by clicking the star below ... View more

Hi Abdul, I dont think this delay is due to the TFTP server failover but the actual registration to secondary server when the primary is down. IP Phone usually sends keepalive messages to both the primary and secondary servers at the specified time interval as configured and failover happens if three such keepalives are missed. Please check the below link which explains this in detail: https://www.cisco.com/c/en/us/support/docs/collaboration-endpoints/unified-ip-phone-7900-series/200410-Troubleshoot-IP-Phone-Unregistration-A.html you can play with these timers based on the requirement and keep it at an optimum value. Keeping a very low value could result in unnecessary failover/fallback as the phones will register back and forth, HTH Rajan Pls rate all useful posts by clicking the star below ... View more

Hi Hari, If the two nodes are completely removed from production, then could you confirm whether you have deleted those server entries in System --> Server and rebooted the cluster once. HTH Rajan Pls rate all useful posts by clicking the star below ... View more

Hi Jonathan, Pub reboot is not required for changing cluster ID and not mentioned as mandatory in any of the Cisco documents. After changing the cluster id, you could verify by downloading a CDR report. HTH Rajan Pls rate all useful posts ... View more