[cisco-voip] Conductor MRG on CUCM never register and rendezvous calls don´t work

Brian Meade bmeade90 at vt.edu
Tue Jul 5 11:38:56 EDT 2016


Looks like this bug-
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCut10254

On Mon, Jul 4, 2016 at 11:19 AM, Eric Pedersen <PedersenE at bennettjones.com>
wrote:

> 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.
>
>
>
> *From:* cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] *On Behalf
> Of *Nilson Costa
> *Sent:* 01 July 2016 12:56 PM
> *To:* cisco-voip at puck.nether.net
> *Subject:* [cisco-voip] Conductor MRG on CUCM never register and
> rendezvous calls don´t work
>
>
>
> 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
>
>
> 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
>
> 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
>
> I got the trace attached from CUCM and from conductor
>
> Can someone help me on it ?
>
>
>
> --
>
> Nilson Lino da Costa Junior
>
>
> 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.
>
> If you no longer wish to receive commercial messages, you can unsubscribe
> by accessing this link: http://www.bennettjones.com/unsubscribe
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20160705/29f2c43d/attachment.html>


More information about the cisco-voip mailing list