<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Verdana; font-size: 10pt; color: #000000'>We haven't plunged into production yet, but all in all the products are very similar. There have been a few changes which you will probably like, others might irk you. For example, you cannot make a distribution list the owner of a call handler. This was an integral part of our business process. We will be moving to generic userIDs and passwords in order to accommodate this. Otherwise, we would have to update a number of call handlers every so often.<br><br>There are some bugs with the GUI which I've caught and filed, hopefully they will be fixed soon.<br><br>We've decided that the savings in maintenance and upkeep comparing an W2K/AD/Exchange based system far outweigh any potential issues we might come up against. As long as the system delivers voicemail and triggers MWI, we're ok. ;)<br><br><br>---<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 (JNHN)<br>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>"Bad grammar makes me [sic]" - Tshirt<br><br><br>----- Original Message -----<br>From: "Lisa Notarianni" <notariannil1@scranton.edu><br>Cc: cisco-voip@puck.nether.net<br>Sent: Tuesday, March 17, 2009 8:31:52 AM GMT -05:00 US/Canada Eastern<br>Subject: [cisco-voip] Unity vs. Unity Connect<br><br>
We are considering switching from Unity to Unity Connect. I see many
threads on Unity Connect. Any lessons learned that we should be aware
of or end user issues that change when switching from one to the other?<br>
<br>
Thanks in advance...Lisa<br>
<div class="moz-signature">-- <br>
<img src="cid:part1.04010903.07070408@scranton.edu" border="0"></div>
<br>_______________________________________________
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
</div></body></html>