<html><body bgcolor="#FFFFFF"><div>The vcs-e can be a challenge if you have quirks in your environment or one-offs.</div><div><br></div><div>We only experimented with h323 though so SIP might be easier.</div><div><br></div><div>My thoughts are thst integrating the environment makes for a consistent user experience. You can register any GK compatible h323 endpoint with the vcs-e so you can migrate slowly if needed. <br><br>On Aug 15, 2012, at 8:43 AM, Lelio Fulgenzi <<a href="mailto:lelio@uoguelph.ca">lelio@uoguelph.ca</a>> wrote:<br><br></div><div></div><blockquote type="cite"><div><div style="font-family: Verdana; font-size: 10pt; color: #000000"><br>I'm trying to get my head around the benefits of deploying a Cisco telepresence solution (TMS, VCS, C60, Movi, etc) vs simply buying one off Polycom units that dial each other and bridges when necessary. I understand the centralized address book, but what else? It seems like I'm building a contained solution that needs additional equipment and licenses in order to talk to these other devices, i.e. VCS Expressway.<br><br>Anything stand out for people who have investigated this route?<br><span><br><span name="x"></span>---<br>Lelio Fulgenzi, B.A.<br>Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<br>(519) 824-4120 x56354 (519) 767-1060 FAX (ANNU)<br>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>Cooking with unix is easy. You just sed it and forget it. <br> - LFJ (with apologies to Mr. Popeil)<br><span name="x"></span><br></span><br></div></div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>cisco-voip mailing list</span><br><span><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a></span><br><span><a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a></span><br></div></blockquote></body></html>