Andy, I do Telepresence frequently so I know where you're coming from. Licensing should've been in the conversation from the beginning. Neither VCS or CUCM will provide that call control without some sort of license. You'll need TP Room Licensing for those endpoints registering to CUCM.
Did you get a Be6k or simply have UC on UCS? The reason I ask is you have VCS of you bought a Be6k and need call control. While this isn't a recommendation it would be a band aid until you get CUCM licensing. Do you have any CUWL Professional licensing? If so we should see about getting your personal multiparty licensing for vTS and Conductor. What are you planning to do with that MCU? I'm recommending that those are replaced with Telepresence Server software but you'll need Conductor in the middle. The direction the program is heading is virtual Telepresence server so I find it odd you just received and MCU 5320 when a vTS van get better capacity now. The next release of vTS is providing a 30% better performance in most vTS cases. The validated design includes CUCM, Expressway, Conductor, and Telepresence server. You can keep MCU software on there behind conductor but you cannot cascade from MCU and TS if you ever expand. If you have any other questions feel free to reach out. Thanks Sent from my Windows Phone ________________________________ From: Andy<mailto:[email protected]> Sent: 11/26/2014 4:27 PM To: Cisco VOIP<mailto:[email protected]> Subject: [cisco-voip] Off Topic -Telepresence issue Hi, I have had some Telepresence devices landed on my lap and a comment about “it only takes 15 mins” to get this going….. They have been shown the youtube video….. What that doesn’t show is the days of pulling hair and shrugging’ shoulders before it was taken out of the box. So I have 1x MX300 G2 4x SX10 1x UCS c220 1x MCU5310 TMS software. Its for internal Conferences between 3 sites I have installed ESXi on the C220 and a Win 2008 OS with Sql Express, then installed TMS and then hit a brick wall on what to do next. I did think about registering them with CCM (9.1.2.11900-12) that requires a device pack to get the MX and SX devices on it, and thats ready to go next week. It also blows out the licensing but thats another issue. The docs that I’ve found seem to assume that the Video system is already setup… Any pointers will be welcomed Andy [email protected] _______________________________________________ cisco-voip mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________ cisco-voip mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-voip
