[prev in list] [next in list] [prev in thread] [next in thread] 

List:       cisco-voip
Subject:    Re: [cisco-voip] cucm ocs integration
From:       "Matt Slaga (US)" <Matt.Slaga () us ! didata ! com>
Date:       2010-12-24 15:24:14
Message-ID: 5FE225375F6E3F4493474B90BC1B94EFC33FDF78D5 () USISPCLEXDB01 ! na ! didata ! local
[Download RAW message or body]

I should probably have explained better, and in less 'rushed' English.

If you have one user with CUCIMOC, they will have phone presence enabled.  If another \
user does not have CUCIMOC, then phone presence will not show for that user unless \
you have CUPS installed.  The problem with having phone presence for some users and \
not for others is end user's trusting the presence icon next to users.  If someone \
shows green and they attempt to IM or call, the other user may respond with 'I'm on \
the phone'.  So users will begin to trust less the presence indicators which will in \
time reduce the success of the implementation.  Just from personal experience in \
deploying Cisco/OCS integrations over the past several years.

Thanks!
Matt

From: Dew Swen [mailto:dew.swen@gmail.com]
Sent: Friday, December 24, 2010 10:14 AM
To: Matt Slaga (US)
Cc: cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] cucm ocs integration

Himm ok Matt, thanks again.

Warm regards,

--
Dew Swen




On Fri, Dec 24, 2010 at 4:45 PM, Matt Slaga (US) \
<Matt.Slaga@us.didata.com<mailto:Matt.Slaga@us.didata.com>> wrote: You will not need \
CUPS unless you need the functions that Erik explains.  Also, keep in mind that \
CUCIMOC is good as an all or nothing deployment.  If you have some users who will not \
have CUCIMOC installed, then phone presence will not show for the users without \
unless you use CUPS for those users.



From: Dew Swen [mailto:dew.swen@gmail.com<mailto:dew.swen@gmail.com>]
Sent: Friday, December 24, 2010 9:00 AM
To: Matt Slaga (US)
Cc: cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
Subject: Re: [cisco-voip] cucm ocs integration

Hi Erik & Matt,

I am trying to do "click to call, phone presence & control hardphone from MOC" \
feature. As Erik said, I want to use CUCIMOC software on the clients.

My concern about the system is: "Do I really need CUPS for presence or can CUCIMOC \
get the presence information directly from OCS server?".

Any docs/guides will be appriciated.

Kind regards,

--
Dew Swen



On Fri, Dec 24, 2010 at 3:11 PM, Matt Slaga (US) \
<Matt.Slaga@us.didata.com<mailto:Matt.Slaga@us.didata.com>> wrote: Dew,

It depends on what you are trying to accomplish with OCS/Cisco integration.  Are you \
looking for just 'click to call' and 'phone presence"?  Are you looking for OCS to \
provide audio/video between endpoints?  Are you looking to utilize OCS' dial-in \
conferencing features?

Thanks!
Matt

From: cisco-voip-bounces@puck.nether.net<mailto:cisco-voip-bounces@puck.nether.net> \
[mailto:cisco-voip-bounces@puck.nether.net<mailto:cisco-voip-bounces@puck.nether.net>] \
                On Behalf Of Dew Swen
Sent: Friday, December 24, 2010 3:20 AM
To: cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
Subject: [cisco-voip] cucm ocs integration

Merry Christmas to everyone,

I will be doing an integration between cucm and ocs. I found this doc about the \
integration: http://www.cisco.com/en/US/docs/voice_ip_comm/cucimoc/7_1/english/integrat/guide/cucimoc_integrate.html


Just CUCIMOC solves it?

Any help will be appriciated,
Kind regards,

--
Dew Swen
________________________________

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.

________________________________

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.



-----------------------------------------
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.


[Attachment #3 (text/html)]

<html xmlns:v="urn:schemas-microsoft-com:vml" \
xmlns:o="urn:schemas-microsoft-com:office:office" \
xmlns:w="urn:schemas-microsoft-com:office:word" \
xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" \
xmlns="http://www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV="Content-Type" \
CONTENT="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 \
(filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);} o\:* \
{behavior:url(#default#VML);} w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div \
class=WordSection1><p class=MsoNormal><span \
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I should \
probably have explained better, and in less &#8216;rushed&#8217; \
English.<o:p></o:p></span></p><p class=MsoNormal><span \
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p \
class=MsoNormal><span \
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>If you have \
one user with CUCIMOC, they will have phone presence enabled.&nbsp; If another user \
does not have CUCIMOC, then phone presence will not show for that user unless you \
have CUPS installed.&nbsp; The problem with having phone presence for some users and \
not for others is end user&#8217;s trusting the presence icon next to users.&nbsp; If \
someone shows green and they attempt to IM or call, the other user may respond with \
&#8216;I&#8217;m on the phone&#8217;.&nbsp; So users will begin to trust less the \
presence indicators which will in time reduce the success of the \
implementation.&nbsp; Just from personal experience in deploying Cisco/OCS \
integrations over the past several years.<o:p></o:p></span></p><p \
class=MsoNormal><span \
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p \
class=MsoNormal><span \
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Thanks!<o:p></o:p></span></p><p \
class=MsoNormal><span \
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Matt<o:p></o:p></span></p><p \
class=MsoNormal><span \
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p \
class=MsoNormal><b><span \
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span \
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Dew Swen \
[mailto:dew.swen@gmail.com] <br><b>Sent:</b> Friday, December 24, 2010 10:14 \
AM<br><b>To:</b> Matt Slaga (US)<br><b>Cc:</b> \
cisco-voip@puck.nether.net<br><b>Subject:</b> Re: [cisco-voip] cucm ocs \
integration<o:p></o:p></span></p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p \
class=MsoNormal style='margin-bottom:12.0pt'>Himm ok Matt, thanks again.<br><br>Warm \
regards,<br><br clear=all><b>--</b><br><b>Dew \
Swen<br><br><br></b><br><br><o:p></o:p></p><div><p class=MsoNormal>On Fri, Dec 24, \
2010 at 4:45 PM, Matt Slaga (US) &lt;<a \
href="mailto:Matt.Slaga@us.didata.com">Matt.Slaga@us.didata.com</a>&gt; \
wrote:<o:p></o:p></p><div><div><p class=MsoNormal \
style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span \
style='font-size:11.0pt;color:#1F497D'>You will not need CUPS unless you need the \
functions that Erik explains.&nbsp; Also, keep in mind that CUCIMOC is good as an all \
or nothing deployment.&nbsp; If you have some users who will not have CUCIMOC \
installed, then phone presence will not show for the users without unless you use \
CUPS for those users.</span><o:p></o:p></p><p class=MsoNormal \
style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span \
style='font-size:11.0pt;color:#1F497D'>&nbsp;</span><o:p></o:p></p><p class=MsoNormal \
style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span \
style='font-size:11.0pt;color:#1F497D'>&nbsp;</span><o:p></o:p></p><p class=MsoNormal \
style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span \
style='font-size:11.0pt;color:#1F497D'>&nbsp;</span><o:p></o:p></p><p class=MsoNormal \
style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span \
style='font-size:10.0pt'>From:</span></b><span style='font-size:10.0pt'> Dew Swen \
[mailto:<a href="mailto:dew.swen@gmail.com" target="_blank">dew.swen@gmail.com</a>] \
<br><b>Sent:</b> Friday, December 24, 2010 9:00 AM<br><b>To:</b> Matt Slaga \
(US)<br><b>Cc:</b> <a href="mailto:cisco-voip@puck.nether.net" \
target="_blank">cisco-voip@puck.nether.net</a><br><b>Subject:</b> Re: [cisco-voip] \
cucm ocs integration</span><o:p></o:p></p><div><div><p class=MsoNormal \
style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p></o:p></p><p \
class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:12.0pt'>Hi Erik &amp; \
Matt,<br><br>I am trying to do &quot;click to call, phone presence &amp; control \
hardphone from MOC&quot; feature. As Erik said, I want to use CUCIMOC software on the \
clients.<br><br>My concern about the system is: &quot;Do I really need CUPS for \
presence or can CUCIMOC get the presence information directly from OCS \
server?&quot;.<br><br>Any docs/guides will be appriciated.<br><br>Kind \
regards,<br><br clear=all><b>--</b><br><b>Dew \
Swen<br><br><br><br></b><o:p></o:p></p><div><p class=MsoNormal \
style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>On Fri, Dec 24, 2010 at \
3:11 PM, Matt Slaga (US) &lt;<a href="mailto:Matt.Slaga@us.didata.com" \
target="_blank">Matt.Slaga@us.didata.com</a>&gt; wrote:<o:p></o:p></p><div><div><p \
class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span \
style='font-size:11.0pt;color:#1F497D'>Dew,</span><o:p></o:p></p><p class=MsoNormal \
style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span \
style='font-size:11.0pt;color:#1F497D'>&nbsp;</span><o:p></o:p></p><p class=MsoNormal \
style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span \
style='font-size:11.0pt;color:#1F497D'>It depends on what you are trying to \
accomplish with OCS/Cisco integration.&nbsp; Are you looking for just &#8216;click to \
call&#8217; and &#8216;phone presence&#8221;?&nbsp; Are you looking for OCS to \
provide audio/video between endpoints?&nbsp; Are you looking to utilize OCS&#8217; \
dial-in conferencing features?&nbsp; </span><o:p></o:p></p><p class=MsoNormal \
style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span \
style='font-size:11.0pt;color:#1F497D'>&nbsp;</span><o:p></o:p></p><p class=MsoNormal \
style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span \
style='font-size:11.0pt;color:#1F497D'>Thanks!</span><o:p></o:p></p><p \
class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span \
style='font-size:11.0pt;color:#1F497D'>Matt</span><o:p></o:p></p><p class=MsoNormal \
style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span \
style='font-size:11.0pt;color:#1F497D'>&nbsp;</span><o:p></o:p></p><p class=MsoNormal \
style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span \
style='font-size:10.0pt'>From:</span></b><span style='font-size:10.0pt'> <a \
href="mailto:cisco-voip-bounces@puck.nether.net" \
target="_blank">cisco-voip-bounces@puck.nether.net</a> [mailto:<a \
href="mailto:cisco-voip-bounces@puck.nether.net" \
target="_blank">cisco-voip-bounces@puck.nether.net</a>] <b>On Behalf Of </b>Dew \
Swen<br><b>Sent:</b> Friday, December 24, 2010 3:20 AM<br><b>To:</b> <a \
href="mailto:cisco-voip@puck.nether.net" \
target="_blank">cisco-voip@puck.nether.net</a><br><b>Subject:</b> [cisco-voip] cucm \
ocs integration</span><o:p></o:p></p><div><div><p class=MsoNormal \
style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p></o:p></p><p \
class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:12.0pt'>Merry Christmas \
to everyone,<br><br>I will be doing an integration between cucm and ocs. I found this \
doc about the integration:<br><a \
href="http://www.cisco.com/en/US/docs/voice_ip_comm/cucimoc/7_1/english/integrat/guide/cucimoc_integrate.html" \
target="_blank">http://www.cisco.com/en/US/docs/voice_ip_comm/cucimoc/7_1/english/integrat/guide/cucimoc_integrate.html</a><br><br>Just \
CUCIMOC solves it?<br><br>Any help will be appriciated,<br>Kind regards,<br><br \
clear=all><b>--</b><br><b>Dew \
Swen</b><o:p></o:p></p></div></div></div></div><div><div class=MsoNormal align=center \
style='text-align:center'><hr size=1 width="100%" \
align=center></div><p><b>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. </b><o:p></o:p></p></div></div><p class=MsoNormal \
style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p></o:p></p></div></div></div></div><div><div><div><div \
class=MsoNormal align=center style='text-align:center'><hr size=1 width="100%" \
align=center></div><p><b>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. </b><o:p></o:p></p></div></div></div></div><p \
class=MsoNormal><o:p>&nbsp;</o:p></p></div></body></html> <HTML><BODY><P><hr \
size=1></P> <P><STRONG>

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. </STRONG></P></BODY></HTML>



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

--===============1674308490==--


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic