MWI is not working CME/CUE

-
For such an issue, please make sure SIP domain IP address is correct.



Comments

Post a Comment

Popular posts from this blog

IP phone reset problem.

-
In the IPT world, IP phones are bound to reset. Sometimes, after firmware upgrade we force phones to reset and other times, due to reboot of the CM server during maintenance window. However, unexpected ip phone reset is a problem. In order to troubleshoot any issue, it is most important to isolate the problem into parts. In an issue of IP phone reset, it is important to collect evidences like-     Is there any error appear on the IP phone screen when it resets?     How many times have phone reset?     How many phones are affected with this behavior?     Is it a progressive issue?     Did we make any changes on UC which might lead to this behavior?     What firmware are affected phones running as compared to working ones?     Are all affected phones connected to the same switch? Unless its not a buggy behavior of phone's firmware, we should check the application logs under s...
Read more

Status: Local Agent is not responding. This may be due to Master or Local Agent being down.

-
If you have read my previous post , you would understand why LA and MA services are important for such a scenario and no component has backed-up, rather you get the above error message. Symptoms -   All Disaster Recovery Framework (DRF) services are down, and no new devices, schedules, or statuses can be viewed from the DRF console. Also, when you access the DRF admin pages, the above error message is received. Affected CM releases 6.1.5 and later. Resolution In order to resolve it, first, verify if the Certificate Serial Number in the keystore of Publisher is present in the Truststore of all Subscribers. Complete these steps: Log on to CUCM OS Administration page of Publisher server of the cluster setup. Choose Security > Certificate Management . The Certificate List window displays. You can use the Find controls in order to filter the certificate. Click on the ipsec.pem file and check the serial number of the certificate. Log on to CUCM OS Admin...
Read more