[cisco-voip] Cisco CUP to OCS federation/integration

[Lelio Fulgenzi]

hmmm, I guess these are all things that will come out during a pilot. i'm also hearing that CUPS v8 will require CUCM v8 as well. *sigh* we're stuck with suite v7 for now. 

--- 
Lelio Fulgenzi, B.A. 
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1 
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN) 
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
"Bad grammar makes me [sic]" - Tshirt 


----- Original Message ----- 
From: "Matt Slaga (US)" <Matt.Slaga at us.didata.com> 
To: "Lelio Fulgenzi" <lelio at uoguelph.ca>, "Mike Wilusz" <mikewilusz at pricechopper.com> 
Cc: cisco-voip at puck.nether.net 
Sent: Tuesday, December 22, 2009 11:48:24 AM GMT -05:00 US/Canada Eastern 
Subject: RE: [cisco-voip] Cisco CUP to OCS federation/integration 

Re: [cisco-voip] Cisco CUP to OCS federation/integration 


With OCS RCC integration with Cisco, you will not have the conference click. Microsoft removed that functionality as a means of pushing their own SIP server. It existed and worked great in LCS, but removed it in OCS. 





From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Lelio Fulgenzi 
Sent: Tuesday, December 22, 2009 11:45 AM 
To: Mike Wilusz 
Cc: cisco-voip at puck.nether.net 
Subject: Re: [cisco-voip] Cisco CUP to OCS federation/integration 




Our thinking was that we would only license OCS for faculty/staff (and then, only those that need it). Faculty/staff could use the full feature set of OCS to communicate to one another (we have several campuses) and use a subset of features to communicate to students via MSN. I like the idea of the tie in to the phone system to do all those fancy things like, "oh, just a sec, let me conference us all in to a conversation" click. or, "just a sec, let me start up a desktop sharing session". click. 



--- 
Lelio Fulgenzi, B.A. 
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1 
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN) 
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
"Bad grammar makes me [sic]" - Tshirt 


----- Original Message ----- 
From: "Mike Wilusz" <mikewilusz at pricechopper.com> 
To: "Lelio Fulgenzi" <lelio at uoguelph.ca> 
Cc: "Philip Walenta" <pwalenta at wi.rr.com>, cisco-voip at puck.nether.net 
Sent: Tuesday, December 22, 2009 10:30:30 AM GMT -05:00 US/Canada Eastern 
Subject: Re: [cisco-voip] Cisco CUP to OCS federation/integration 

Lelio, 

You have more options than CUPS and OCS, especially if you’re looking at extending this to your student populations. Licensing OCS or CUPS for all those users would be $$$$$! You may be better off offering a cheap/no-cost IM solution to the students that allows open federation to other networks. Students use this and it federates to whatever they needs to talk to (AIM, Gtalk, MSN...), and with CUPS 8.0 you’ll be able to federate between the student IM server and the CUPS server for the teachers. No sense using OCS or CUPS with all the tie-ins to the phone system for all those students who don’t operate IP phones. 

Mike Wilusz, CCNA 
Telecommunications & Networking Supervisor 
Price Chopper Supermarkets / The Golub Corporation 





From: Lelio Fulgenzi < lelio at uoguelph.ca > 
Date: Mon, 21 Dec 2009 21:53:08 -0500 
To: Michael Wilusz < mikewilusz at pricechopper.com > 
Cc: Philip Walenta < pwalenta at wi.rr.com >, < cisco-voip at puck.nether.net > 
Subject: Re: [cisco-voip] Cisco CUP to OCS federation/integration 


I'm interested in hearing about the nightmare. We are considering CUPS vs OCS as a future project, but from what I heard, CUPS can not federate with MSN (yet). Since 99% of our first year students use MSN, I'm leaning towards an OCS implementation with whatever integration we can do with CUCM (+CUPS). We might have fewer features with OCS w/ CUCM than with CUPS w/ CUCM, but if the strategic goal is to allow our students access to faculty/staff via IM, then i'm not sure we have too much of an option. 
--- 
Lelio Fulgenzi, B.A. 
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1 
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN) 
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
"Bad grammar makes me [sic]" - Tshirt 


----- Original Message ----- 
From: "Mike Wilusz" < mikewilusz at pricechopper.com > 
To: "Philip Walenta" < pwalenta at wi.rr.com >, cisco-voip at puck.nether.net 
Sent: Monday, December 21, 2009 9:24:30 PM GMT -05:00 US/Canada Eastern 
Subject: Re: [cisco-voip] Cisco CUP to OCS federation/integration 

Re: [cisco-voip] Cisco CUP to OCS federation/integration I did a CUPS to OCS federation setup. You definitely do not need to use an ASA. Follow the CUPS doc and you’ll be fine from that side. OCS is a nightmare but it will work. We ditched OCS and are going with a total CUPS implementation. 

Mike Wilusz, CCNA 
Telecommunications & Networking Supervisor 
Price Chopper Supermarkets / The Golub Corporation 



From: Philip Walenta < pwalenta at wi.rr.com > 
Date: Tue, 22 Dec 2009 05:04:31 -0600 
To: < cisco-voip at puck.nether.net > 
Subject: [cisco-voip] Cisco CUP to OCS federation/integration 

Has anyone done a CUP to OCS federation/integration? 

I’m looking for good documentation because Cisco’s doc wiki just keeps running me in circles? 

It says I need an ASA to do this and I can’t believe I need an ASA to link OCS to CUP in the same company. 



_______________________________________________ 
cisco-voip mailing list 
cisco-voip at puck.nether.net 
https://puck.nether.net/mailman/listinfo/cisco-voip 

_______________________________________________ cisco-voip mailing list cisco-voip at puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip 






Disclaimer: This e-mail communication and any attachments may contain confidential and privileged information and is for use by the designated addressee(s) named above only. If you are not the intended addressee, you are hereby notified that you have received this communication in error and that any use or reproduction of this email or its contents is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and deleting it from your computer. Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20091222/34518a1a/attachment.html>