Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

CCM not sending Skinny Message of StationStartTone(on hold) to Unity

This was originally posted in the Unity area, but was suggested by someone at Cisco that I post it here...

Version Info...

Unity 3.1 Build 3.1.5

CallManager 3.3(2)spC

Unity-CM TSP 7.0(2)

OK, so Caller A logs into Unity. While Caller A is listening to his messages in Unity, Caller B calls Caller A. Caller A decides to take the call, but instead of hanging up with Unity, Caller A simply switches over to the line that Caller B is calling on. This places Unity on hold. Unity waits patiently for an input, but after 45 to 60 seconds decides to transfer the line to the default Operator. However, Unity grabs the line that Caller A is on with Caller B, puts Caller B on hold and transfers Caller A to the default Operator. The connection is established for about 5 seconds and then promptly drops confusing both the Operator and Caller A.

It only seemed to start happening after we upgraded to CCM3.3(2) a few weeks ago. After reviewing the logs, it was determined that the CallManager is not sending the Skinny Message of StationStartTone(on hold) to Unity.

Any further information would be appreciated.


Re: CCM not sending Skinny Message of StationStartTone(on hold)

I didn't find any matching caveat in these release notes.

This might be a new bug in CM. You may want to check it in the bug toolkit.

CreatePlease login to create content