11-07-2012 08:05 AM - edited 03-19-2019 05:50 AM
Hi,
We have a CUCM/CUC Cluster since 2009 and we never had problems with accessing Voicemail. We configured a Secure Siptrunk between the CUCM Cluster and the CUC-Server.
CUCM 8.5.1SU4/CUC8.5.1SU1
2 weeks ago we upgraded CUC from 8.5.1SU1 to 8.5.1SU5
Since this upgrade we had at 2 times no voicemail access from the IP-Phones registered on CUCM-Cluster (reorder tone) - in the log of CUC we saw that all 144 ports become busy !!
History:
Update CUC from 8.5.1SU1 to 8.5.1SU5 on Saturday 10/26
- first outage on wed. 10/31 ; 1:48 pm
- second outage on tue 11/6 10:26 am
After restart of the CUC-Server the system works normally - I think stopping and starting Connection Manager coiuld also be a workaround, but i did not verified this :
here the log from wed 10/31
Oct 31 13:48:37 CUC1 local7 4 : 4298: CUC1.sprachdienst.fraunhofer.de: Oct 31 2012 12:48:37 PM.862 UTC : %UC_UCEVNT-4-EvtMiuBusyHere: %[AppID=CuCsMgr][ClusterID=][NodeID=CUC1]: Miu SIP Integration, All lines are busy on redirector 10.37.239.21:5061. An incoming call will not be answered.
Oct 31 13:48:44 CUC1 local7 4 : 4299: CUC1.sprachdienst.fraunhofer.de: Oct 31 2012 12:48:44 PM.931 UTC : %UC_UCEVNT-4-EvtMiuBusyHere: %[AppID=CuCsMgr][ClusterID=][NodeID=CUC1]: Miu SIP Integration, All lines are busy on redirector 10.37.239.21:5061. An incoming call will not be answered.
Oct 31 13:48:47 CUC1 local7 4 : 4300: CUC1.sprachdienst.fraunhofer.de: Oct 31 2012 12:48:47 PM.508 UTC : %UC_UCEVNT-4-EvtMiuBusyHere: %[AppID=CuCsMgr][ClusterID=][NodeID=CUC1]: Miu SIP Integration, All lines are busy on redirector 10.37.239.21:5061. An incoming call will not be answered....
the log from yesterday
Nov 6 10:26:43 CUC1 local7 4 : 14264: CUC1.sprachdienst.fraunhofer.de: Nov 06 2012 09:26:43 AM.732 UTC : %UC_UCEVNT-4-EvtMiuBusyHere: %[AppID=CuCsMgr][ClusterID=][NodeID=CUC1]: Miu SIP Integration, All lines are busy on redirector 10.37.239.21:5061. An incoming call will not be answered.
Nov 6 10:26:56 CUC1 local7 4 : 14265: CUC1.sprachdienst.fraunhofer.de: Nov 06 2012 09:26:56 AM.942 UTC : %UC_UCEVNT-4-EvtMiuBusyHere: %[AppID=CuCsMgr][ClusterID=][NodeID=CUC1]: Miu SIP Integration, All lines are busy on redirector 10.37.239.21:5061. An incoming call will not be answered.
Nov 6 10:27:03 CUC1 local7 4 : 14266: CUC1.sprachdienst.fraunhofer.de: Nov 06 2012 09:27:03 AM.147 UTC : %UC_UCEVNT-4-EvtMiuBusyHere: %[AppID=CuCsMgr][ClusterID=][NodeID=CUC1]: Miu SIP Integration, All lines are busy on redirector 10.37.239.21:5061. An incoming call will not be answered.
Nov 6 10:27:11 CUC1 local7 4 : 14267: CUC1.sprachdienst.fraunhofer.de: Nov 06 2012 09:27:11 AM.359 UTC : %UC_UCEVNT-4-EvtMiuBusyHere: %[AppID=CuCsMgr][ClusterID=][NodeID=CUC1]: Miu SIP Integration, All lines are busy on redirector 10.37.239.21:5061. An incoming call will not be answered.
Nov 6 10:27:59 CUC1 local7 4 : 14268: CUC1.sprachdienst.fraunhofer.de: Nov 06 2012 09:27:59 AM.155 UTC : %UC_UCEVNT-4-EvtMiuBusyHere: %[AppID=CuCsMgr][ClusterID=][NodeID=CUC1]: Miu SIP Integration, All lines are busy on redirector 10.37.239.21:5061. An incoming call will not be answered.
Nov 6 10:27:59 CUC1 local7 4 : 14269: CUC1.sprachdienst.fraunhofer.de: Nov 06 2012 09:27:59 AM.177 UTC : %UC_UCEVNT-4-EvtMiuBusyHere: %[AppID=CuCsMgr][ClusterID=][NodeID=CUC1]: Miu SIP Integration, All lines are busy on redirector 10.37.239.21:5061. An incoming call will not be answered.
Nov 6 10:29:33 CUC1 local7 4 : 14270: CUC1.sprachdienst.fraunhofer.de: Nov 06 2012 09:29:33 AM.475 UTC : %UC_UCEVNT-4-EvtMiuBusyHere: %[AppID=CuCsMgr][ClusterID=][NodeID=CUC1]: Miu SIP Integration, All lines are busy on redirector 10.37.239.21:5061. An incoming call will not be answered.
Nov 6 10:29:48 CUC1 local7 4 : 14271: CUC1.sprachdienst.fraunhofer.de: Nov 06 2012 09:29:48 AM.770 UTC : %UC_UCEVNT-4-EvtMiuBusyHere: %[AppID=CuCsMgr][ClusterID=][NodeID=CUC1]: Miu SIP Integration, All lines are busy on redirector 10.37.239.21:5061. An incoming call will not be answered.
Question:
do we have a bug in the software CUC 8.5.1SU5 or is there another problem ?
Any Ideas ?
regards
alex
Solved! Go to Solution.
11-28-2012 12:47 AM
Hi,
we opened a tac case and it seems we run into a bug which is known in Version 8.6. (We run 8.5.1SU5)
Cisco already have the fix available for version 8.6.2 ES52.
Cause we can not upgrade to 8.6 (Server Hardware not supported) we will wait for the Version 8.5 Fix.
Meanwhile I will change the SIP-Trunk between the Unity Connection Server and the Call Manager Server from TLS to non-TLS (described in CSCuc22800 as a workaround)
regards
Alex
11-07-2012 09:52 AM
Hi Alex,
First of all check the capability matrix of CUCM and Unity Connection. If everything is okay
Try to recreate the sip integration with CUCM and Unity.
In the case of the problem continue, open a tac case.
best regards,
Daniel
11-28-2012 12:47 AM
Hi,
we opened a tac case and it seems we run into a bug which is known in Version 8.6. (We run 8.5.1SU5)
Cisco already have the fix available for version 8.6.2 ES52.
Cause we can not upgrade to 8.6 (Server Hardware not supported) we will wait for the Version 8.5 Fix.
Meanwhile I will change the SIP-Trunk between the Unity Connection Server and the Call Manager Server from TLS to non-TLS (described in CSCuc22800 as a workaround)
regards
Alex
11-28-2012 07:05 AM
Hi Alex,
Thanks for this kind follow-up with your resolution +5
This type of thread completion really helps others here @ CSC!
Cheers!
Rob
"And if I should fall behind
Wait for me" - Springsteen
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide