I ran into a problem where unity generated hundreds of ciscounity_tsp (ID 128) information alerts in the event viewer. Specifically, the notifications were that MWI was running into collisions when trying to update MWI. Has anyone ever encountered this problem?
The specific error is...
Event Type: Information
Event Source: CiscoUnity_TSP
Event Category: None
Event ID: 128
Time: 3:17:39 PM
Cisco Unity-CM TSP device 17 (Cisco Unity port 13): An attempt to turn OFF the message waiting indicator (MWI) for extension 2264 failed because a collision occurred with an incoming call on the same port.
The MWI request will be retried. But to prevent collisions, we recommend that ports setting MWIs be isolated from ports handling incoming calls. If the MWI status remains unchanged for an extended period of time or if there are many of these warnings from Cisco Unity in a short period of time, there may be an MWI misconfiguration or another problem.
For more information, refer to the "Message Waiting Indicators" chapter in the Cisco Unity Troubleshooting Guide.
The usual fix for this is allow MWI only on a couple of ports and not allow calls on the MWI ports. ie:
Suppose there are ports 1-16
On Unity side, configure only ports 15,16 for MWI. Take these ports out of the hunt group for inbound/outbound calls.
I am not sure which version of Unity or if you are integrating with CallManager, but the following URL that tells how to plan the port usage.
Hope this helps!