[cisco-voip] CUPC presence indicators

Oleg Skomorokhov pocketapl at nm.ru
Tue Oct 20 16:13:41 EDT 2009


There's a cisco UC integration for MOC plugin available, if you want to use
MOC for the presence information and cisco-plugin for the soft/desk phone.
It works as an additional bottom toolbar in MOC, where you can access all
the telephony features. Check more info at cisco.com...

On Tue, Oct 20, 2009 at 6:49 PM, Voice Noob <voicenoob at gmail.com> wrote:

>  Exactly my point.
>
>
>
> *From:* Matt Slaga (US) [mailto:Matt.Slaga at us.didata.com]
> *Sent:* Tuesday, October 20, 2009 9:39 AM
> *To:* Voice Noob; 'Carlos Ortiz'
>
> *Cc:* cisco-voip at puck.nether.net
> *Subject:* RE: [cisco-voip] CUPC presence indicators
>
>
>
> I wouldn’t say that Cisco can’t get that part down, it’s more of what
> Microsoft allows for integration points with their apps.
>
>
>
> *From:* Voice Noob [mailto:voicenoob at gmail.com]
> *Sent:* Tuesday, October 20, 2009 9:43 AM
> *To:* Matt Slaga (US); 'Carlos Ortiz'
> *Cc:* cisco-voip at puck.nether.net
> *Subject:* RE: [cisco-voip] CUPC presence indicators
>
>
>
> From a user perspective the Microsoft platform is far more robust. From an
> technical perspective the MOC server is very immature.  Microsoft knows how
> to make their products  integrate well together where Cisco still can’t get
> that part down.
>
>
>
>
>
> *From:* Matt Slaga (US) [mailto:Matt.Slaga at us.didata.com]
> *Sent:* Tuesday, October 20, 2009 8:32 AM
> *To:* Carlos Ortiz; Voice Noob
> *Cc:* cisco-voip at puck.nether.net
> *Subject:* RE: [cisco-voip] CUPC presence indicators
>
>
>
> Robust telephony platform
>
> Call Admission Control
>
> QoS – can be accomplished with Microsoft as well, but not to the degree
> that Cisco allows.  This is because of how Microsoft handles voice and video
> traffic over the same ports so differentiation is not always possible.  Ever
> put video into a priority queue?
>
> Version 7/8 of the PBX, whereas Microsoft is on version 2.
>
>
>
> There is more, but I think you get the picture.
>
>
>
>
>
> *From:* Carlos Ortiz [mailto:COrtiz at sscincorporated.com]
> *Sent:* Tuesday, October 20, 2009 9:25 AM
> *To:* Voice Noob; Matt Slaga (US)
> *Cc:* cisco-voip at puck.nether.net
> *Subject:* RE: [cisco-voip] CUPC presence indicators
>
>
>
> I’ve just been waiting over the past couple of years to see how the
> presence battle was going to play out.  If you run Microsoft Office
> applications in house as most do what does the Cisco side offer over
> Microsoft?
>
>
>
>
>
> *From:* cisco-voip-bounces at puck.nether.net [mailto:
> cisco-voip-bounces at puck.nether.net] *On Behalf Of *Voice Noob
> *Sent:* Tuesday, October 20, 2009 9:19 AM
> *To:* 'Matt Slaga (US)'; cisco-voip at puck.nether.net
> *Subject:* Re: [cisco-voip] CUPC presence indicators
>
>
>
> I will add that to my ever growing list of the things the MOC client can do
> that the CUPC client cannot.
>
> Has anyone had a satisfied customer that has deployed CUPC?
>
>
>
> *From:* Matt Slaga (US) [mailto:Matt.Slaga at us.didata.com]
> *Sent:* Monday, October 19, 2009 6:19 PM
> *To:* Voice Noob; cisco-voip at puck.nether.net
> *Subject:* RE: [cisco-voip] CUPC presence indicators
>
>
>
> These presence jelly beans are part of the deep office integration that
> Microsoft has made with MOC.  There are currently no APIs to integrate other
> presence clients into sharepoint and outlook, so yes it is another item that
> MOC can and CUPC cannot.
>
>
>
>
>
>
>
> *From:* cisco-voip-bounces at puck.nether.net [mailto:
> cisco-voip-bounces at puck.nether.net] *On Behalf Of *Voice Noob
> *Sent:* Monday, October 19, 2009 5:53 PM
> *To:* cisco-voip at puck.nether.net
> *Subject:* [cisco-voip] CUPC presence indicators
>
>
>
> When I use the MOC client on my PC and I use a Microsoft application like
> SharePoint or outlook it puts a bubble icon indicating the presence
> information of that user. I assume this is something on the client side. Can
> this be implemented using the CUPC client or is it just another item that
> MOC can do that CUPC cannot.
>
>
>
>
>
>
>  ------------------------------
>
> *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. *
>
> CONFIDENTIALITY NOTICE: This e-mail transmission, including any attachments
> to it, may contain confidential information or protected health information
> subject to privacy regulations such as the Health Insurance Portability and
> Accountability Act of 1996 (HIPAA). This transmission is intended only for
> the use of the recipient(s) named above. If you are not the intended
> recipient, or a person responsible for delivering it to the intended
> recipient, you are hereby notified that any disclosure, copying,
> distribution or use of any of the information contained in this transmission
> is STRICTLY PROHIBITED. If you have received this transmission in error,
> please immediately notify me by reply e-mail and destroy the original
> transmission in its entirety without saving it in any manner.
>
> Warning: Although precautions have been taken to make sure no viruses are
> present in this email, the company cannot accept responsibility for any loss
> or damage that arise from the use of this email or attachments.
>  ------------------------------
>
> *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. *
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20091021/6bcad97a/attachment.html>


More information about the cisco-voip mailing list