MOH not working on external calls

-
You have just finished upgrading servers to 8.x and are in testing phase. While everything seems to working - phones, gateways, voicemail system, only one thing is kaput.
MOH stopped working.
On further research, you figured out, MOH is not working on only external calls both inbound and outbound.
Good that issue is isolated properly, but if you have only upgraded CUCM box then why MOH through gateways are affected. This generally happens due to compatibility issue between gateway's IOS and CM version.

However, here we are hitting a classic caveat- CSCtl21854. Though, this caveat talks about unicast MOH, this workaround works in case of multicast MOH as well.
Please note that this caveat is only observed on CM 8.x releases

Unicast MoH fails if CEF is enabled.

Symptom:
Unicast MoH audio coming from CUCM will stop working after upgrade.

Conditions:
The symptom can be observed after upgrading a Cisco router to 15.0.1M4,
15.1(2)T1 or 151-3.T.

Workaround:
Option 1:
Disable CEF by adding the no ip cef command under global
configuration mode. Beware this can affect the router's performance and
functionality of CEF dependent configurations.

Option 2:
Enable Duplex Streaming in the CallManager service parameters. This does not
carry the same performance impact as disabling CEF on the voice gateway. There
is minimal signaling difference for this and no *known* negative side effects.

Comments

Post a Comment

Popular posts from this blog

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 Administr
Read more

Understanding code yellow

-
Understanding sample code yellow alert- Oct 3 01:00:10, cms01, Error, Cisco CallManager, ccm: 147896: Oct 03 05:00:10.616 UTC : %CCM_CALLMANAGER-CALLMANAGER-3-CodeYellowEntry: CodeYellowEntry Expected Average Delay:362 Entry Latency:20 Exit Latency:8 Sample Size:10 Total Code Yellow Entry:14 High Priority Queue Depth:2 Normal Priority Queue Depth:12 Low Priority Queue Depth:70 Cluster ID:StandAloneCluster Node ID:cms01, 3652 The above alert is about code yellow entry, it shows the time when server enters code yellow state. There are no specifications to note at this alert, CM enters code yellow when it achieves the mentioned conditions for code yellow state as mentioned in service parameters. Oct 3 01:00:12, cms01, Error, Cisco CallManager, ccm: 147897: Oct 03 05:00:12.268 UTC : %CCM_CALLMANAGER-CALLMANAGER-3-CodeYellowExit: CodeYellowExit Expected Average Delay:0 Entry Latency:20 Exit Latency:8 Sample Size:10 Time Spent in Code Yellow:2 Number of Calls Rejected Due to C
Read more