<div dir="ltr"><div><div><div>Hello all,<br><br></div>There were 2 issues actually on the system, we were hitting bug <a href="https://bst.cloudapps.cisco.com/bugsearch/bug/CSCut10254" target="_blank">CSCut10254</a> this was what wasn´t allowing conference bridges to register into CUCM but even after I fixed it the system continued to present errors when we started any kind of meeting.<br><br></div><div>I reviewd the whole configuration and also found an error on the name of X509 subject name in the sip security profile. As soon as I fixed that everything worked. Thank you very much guys for the help<br></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">2016-07-05 12:38 GMT-03:00 Brian Meade <span dir="ltr"><<a href="mailto:bmeade90@vt.edu" target="_blank">bmeade90@vt.edu</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Looks like this bug- <a href="https://bst.cloudapps.cisco.com/bugsearch/bug/CSCut10254" target="_blank">https://bst.cloudapps.cisco.com/bugsearch/bug/CSCut10254</a></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="h5">On Mon, Jul 4, 2016 at 11:19 AM, Eric Pedersen <span dir="ltr"><<a href="mailto:PedersenE@bennettjones.com" target="_blank">PedersenE@bennettjones.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5">
<div link="blue" vlink="purple" lang="EN-US">
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">There is a defect in CUCM 10.5 where the Conductor won't register if CUCM is configured to use HTTPS. I don't remember the details but it's related to certificate
validation. We had to switch our CUCM configuration to use HTTP to communicate with Conductor.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> cisco-voip [mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a>]
<b>On Behalf Of </b>Nilson Costa<br>
<b>Sent:</b> 01 July 2016 12:56 PM<br>
<b>To:</b> <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<b>Subject:</b> [cisco-voip] Conductor MRG on CUCM never register and rendezvous calls don´t work<u></u><u></u></span></p><div><div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<div>
<div>
<p>I have a new implementation with CUCM 11, conductor XC4 and vTS 4.2(4.23). I create a CA to sign the certificates on CUCM and on Conductor and exchanged the certificates. and followed this document for the implementation<u></u><u></u></p>
<p><a href="http://www.cisco.com/c/dam/en/us/td/docs/telepresence/infrastructure/conductor/config_guide/xc4-0_docs/TelePresence-Conductor-Unified-CM-Deployment-Guide-XC4-0.pdf" target="_blank">http://www.cisco.com/c/dam/en/us/td/docs/telepresence/infrastructure/conductor/config_guide/xc4-0_docs/TelePresence-Conductor-Unified-CM-Deployment-Guide-XC4-0.pdf</a><u></u><u></u></p>
<p>The problem is that the media resource group never register on the system and when I try to call a rendezvous room the call fail using any endpoint or Jabber<u></u><u></u></p>
<p>I got the trace attached from CUCM and from conductor<u></u><u></u></p>
<p>Can someone help me on it ?<u></u><u></u></p>
</div>
</div>
</div>
<p class="MsoNormal"><br clear="all">
<br>
-- <u></u><u></u></p>
<div>
<div>
<p class="MsoNormal">Nilson Lino da Costa Junior<u></u><u></u></p>
</div>
</div>
</div>
</div></div></div>
<br>
<br>
The contents of this message may contain confidential and/or privileged
subject matter. If this message has been received in error, please contact
the sender and delete all copies. Like other forms of communication,
e-mail communications may be vulnerable to interception by unauthorized
parties. If you do not wish us to communicate with you by e-mail, please
notify us at your earliest convenience. In the absence of such
notification, your consent is assumed. Should you choose to allow us to
communicate by e-mail, we will not take any additional security measures
(such as encryption) unless specifically requested.
<br>
<br>
If you no longer wish to receive commercial messages, you can unsubscribe
by accessing this link: <a href="http://www.bennettjones.com/unsubscribe" target="_blank">http://www.bennettjones.com/unsubscribe</a>
</div>
<br></div></div>_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" rel="noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br></blockquote></div><br></div>
</blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">Nilson Lino da Costa Junior<br></div></div>
</div>