LSC Failed. Mic work fine. Need use LSC 7941 and 7961

Unanswered Question
Jan 8th, 2010

I have a CUCM cluster

System version: 7.1.2.10000-16 and The security is working fine using the MIC on 7941 and 7961, following the cisco recomendation using LSC instead MIC. but when I tried install/upgrade it the phone show LSC error and LSC failed. I have captured traces showed below any ideas:
Unable to parse AT_SERIAL_NUMBER from Subject Name AVA of cert
Message does not contain a SUDI certificate
<LVL::Error><MASK::0003>
SSL3 alert write warning close notify
unable to find name AVA
Certificate hash generation failed
specific detailed below:
, fd = 15
|<CLID::StandAloneCluster><NID::172.22.180.1><LVL::Error><MASK::0003>
01/08/2010 14:29:52.627 CAPF|   debug 4628:SEP0023043564DE:Retrieved cert from message.|<CLID::StandAloneCluster><NID::172.22.180.1><LVL::Error><MASK::0003>
01/08/2010 14:29:52.627 CAPF|   debug 4628:SEP0023043564DE:Message does not contain a SUDI certificate.|<CLID::StandAloneCluster><NID::172.22.180.1><LVL::Error><MASK::0003>
01/08/2010 14:29:52.663 CAPF|   debug 4628:SEP0023043564DE:In capf_ui_set_ph_opStatus_id()|<CLID::StandAloneCluster><NID::172.22.180.1><LVL::Error><MASK::0003>
01/08/2010 14:29:52.736 CAPF|   debug ERROR:172.22.181.154: SSL3 alert write warning close notify|<CLID::StandAloneCluster><NID::172.22.180.1><LVL::Error><MASK::0003>
01/08/2010 14:29:52.742 CAPF|   debug ERROR:172.22.181.154: SSL3 alert read warning close notify|<CLID::StandAloneCluster><NID::172.22.180.1><LVL::Error><MASK::0003>
01/08/2010 14:32:18.331 CAPF|   debug FD_ISSET i=0, SockServ=13
|<CLID::StandAloneCluster><NID::172.22.180.1><LVL::Error><MASK::0003>
01/08/2010 14:32:18.332 CAPF|   debug Accepted TCP connection from socket 0x00000013
, fd = 15
|<CLID::StandAloneCluster><NID::172.22.180.1><LVL::Error><MASK::0003>
01/08/2010 14:32:18.609 CAPF|   debug 4629:SEP0023043564DE:Retrieved cert from message.|<CLID::StandAloneCluster><NID::172.22.180.1><LVL::Error><MASK::0003>
01/08/2010 14:32:18.609 CAPF|   debug 4629:SEP0023043564DE:Message does not contain a SUDI certificate.|<CLID::StandAloneCluster><NID::172.22.180.1><LVL::Error><MASK::0003>
01/08/2010 14:32:18.609 CAPF|   debug In function capfSUDIParseSubjectNameObj()|<CLID::StandAloneCluster><NID::172.22.180.1><LVL::Error><MASK::0003>
01/08/2010 14:32:18.609 CAPF|   debug Exiting function capfSUDIParseSubjectNameObj()|<CLID::StandAloneCluster><NID::172.22.180.1><LVL::Error><MASK::0003>
01/08/2010 14:32:18.609 CAPF|   debug In function capfParseNameAVA()|<CLID::StandAloneCluster><NID::172.22.180.1><LVL::Error><MASK::0003>
01/08/2010 14:32:18.610 CAPF|   debug ERROR:capfParseNameAVA(): unable to find name AVA|<CLID::StandAloneCluster><NID::172.22.180.1><LVL::Error><MASK::0003>
01/08/2010 14:32:18.610 CAPF|   debug Exiting function capfParseNameAVA() with error|<CLID::StandAloneCluster><NID::172.22.180.1><LVL::Error><MASK::0003>
01/08/2010 14:32:18.610 CAPF|   debug ERROR:Unable to parse AT_SERIAL_NUMBER from Subject Name AVA of cert|<CLID::StandAloneCluster><NID::172.22.180.1><LVL::Error><MASK::0003>
01/08/2010 14:32:30.326 CAPF|   debug 4629:SEP0023043564DE:In capfIsDevCTI()|<CLID::StandAloneCluster><NID::172.22.180.1><LVL::Error><MASK::0003>
01/08/2010 14:32:30.326 CAPF|   debug ERROR:capfGetInputToCertObject 1809|<CLID::StandAloneCluster><NID::172.22.180.1><LVL::Error><MASK::0003>
01/08/2010 14:32:30.326 CAPF|   debug In capfGenerateHashFromCert()|<CLID::StandAloneCluster><NID::172.22.180.1><LVL::Error><MASK::0003>
01/08/2010 14:32:30.326 CAPF|   debug Null cert passed to capfGenerateHashFromCert()|<CLID::StandAloneCluster><NID::172.22.180.1><LVL::Error><MASK::0003>
01/08/2010 14:32:30.333 CAPF|   debug 4629:SEP0023043564DE:Certificate hash generation failed|<CLID::StandAloneCluster><NID::172.22.180.1><LVL::Error><MASK::0003>
01/08/2010 14:32:30.333 CAPF|   debug 4629:SEP0023043564DE:In capf_ui_set_ph_cert_hash()|<CLID::StandAloneCluster><NID::172.22.180.1><LVL::Error><MASK::0003>
01/08/2010 14:32:30.338 CAPF|   debug 4629:SEP0023043564DE:Setting device hash to NULL|<CLID::StandAloneCluster><NID::172.22.180.1><LVL::Error><MASK::0003>
01/08/2010 14:32:30.398 CAPF|   debug 4629:SEP0023043564DE:In capf_ui_set_ph_opStatus_id()|<CLID::StandAloneCluster><NID::172.22.180.1><LVL::Error><MASK::0003>
01/08/2010 14:32:30.460 CAPF|   debug ERROR:172.22.181.154: SSL3 alert write warning close notify|<CLID::StandAloneCluster><NID::172.22.180.1><LVL::Error><MASK::0003>
01/08/2010 14:32:30.466 CAPF|   debug ERROR:172.22.181.154: SSL3 alert read warning close notify|<CLID::StandAloneCluster><NID::172.22.180.1><LVL::Error><MASK::0003>
01/08/2010 15:05:00.520 CAPF|   debug FD_ISSET i=0, SockServ=13
|<CLID::StandAloneCluster><NID::172.22.180.1><LVL::Error><MASK::0003>
01/08/2010 15:05:00.521 CAPF|   debug Accepted TCP connection from socket 0x00000013
I have this problem too.
1 vote
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.

Actions

This Discussion