Technically it’s quite tricky to get MWI status from a UCM endpoint, the hybrid
integration with spark leverages CTI for the SNR functionality, however Cisco’s
CTI implementation does not include querying MWI status. So I guess that
further complicates feature alignment for a hybrid system.

Advertising

Kind regards
Stephen Welsh
CTO
UnifiedFX
On 13 Feb 2018, at 20:52, Lelio Fulgenzi
<le...@uoguelph.ca<mailto:le...@uoguelph.ca>> wrote:
Fair enough. And interesting news about the push away from IPC!
Here’s my counter argument.
Cisco Spark _has_ MWI. But for the Spark cloud calling service. What it doesn’t
have is hybrid MWI.
So the feature exists to light a lamp per se and it’s being done by one system
currently.
Technical restrictions aside, and I’m sure there are plenty, they’ve decided
not to implement hybrid MWI.
---
Lelio Fulgenzi, B.A. | Senior Analyst
Computing and Communications Services | University of Guelph
Room 037 Animal Science & Nutrition Bldg | 50 Stone Rd E | Guelph, ON | N1G 2W1
519-824-4120 Ext. 56354 | le...@uoguelph.ca<mailto:le...@uoguelph.ca>
www.uoguelph.ca/ccs<http://www.uoguelph.ca/ccs> | @UofGCCS on Instagram,
Twitter and Facebook
<image001.png>
From: Stephen Welsh [mailto:stephen.we...@unifiedfx.com]
Sent: Tuesday, February 13, 2018 3:05 PM
To: Lelio Fulgenzi <le...@uoguelph.ca<mailto:le...@uoguelph.ca>>
Cc: Brian Meade <bmead...@vt.edu<mailto:bmead...@vt.edu>>; cisco-voip voyp list
<cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>>
Subject: Re: [cisco-voip] Spark Hybrid and MWI/Voicemail
My 2 cents…
From an Cisco Spark API perspective it’s a meeting room system as that is the
model the User Experience is aligned for, so a long way to go for more
traditional telephony features that are out of context for a meeting i.e. MWI.
Cisco Spark reminds me of the Windows 8 fiasco of making a desktop OS fit a
tablet interface at the expense of normal desktop interactions, hence the swing
back to normal desktop with Windows 10 etc. For me Cisco Spark is a "soft
meeting" client that needs be extended to sensibly incorporate more traditional
"soft phone" functionality/interactions.
That’s not to say Cisco Spark is not great at what it does, just that there
needs to be more of a choice/overlap between Spark/Jabber, until then Spark
will be more of a niche solution.
Also, it would appear all the marketing push for Cisco Spark has given Jabber a
boost, and given Cisco have finally committed to port all relevant IP
Communicator functionality to Jabber so IPC can be EOS that will keep Jabber at
the primary soft phone solution for most larger organisations until Cisco can
find a way forward with a unified soft phone solution.
Anyway, just my personal opinion, I’m sure others with disagree ;)
Kind Regards
Stephen Welsh
CTO
UnifiedFX
On 13 Feb 2018, at 17:20, Lelio Fulgenzi
<le...@uoguelph.ca<mailto:le...@uoguelph.ca>> wrote:
I could almost get away with “if you need uccx, use jabber; else, use spark”
But to say, “if you need MWI use jabber; else, use spark” – ugh.
I guess I don’t mind having two deployments, if the Jabber deployment is small
and manageable.
It’s a shame, really. ☹
---
Lelio Fulgenzi, B.A. | Senior Analyst
Computing and Communications Services | University of Guelph
Room 037 Animal Science & Nutrition Bldg | 50 Stone Rd E | Guelph, ON | N1G 2W1
519-824-4120 Ext. 56354 | le...@uoguelph.ca<mailto:le...@uoguelph.ca>
www.uoguelph.ca/ccs<http://www.uoguelph.ca/ccs> | @UofGCCS on Instagram,
Twitter and Facebook
<image001.png>
From: bmead...@gmail.com<mailto:bmead...@gmail.com> [mailto:bmead...@gmail.com]
On Behalf Of Brian Meade
Sent: Tuesday, February 13, 2018 10:37 AM
To: Lelio Fulgenzi <le...@uoguelph.ca<mailto:le...@uoguelph.ca>>
Cc: cisco-voip voyp list
<cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>>
Subject: Re: [cisco-voip] Spark Hybrid and MWI/Voicemail
No UCCX support has been the big killer for us suggesting it more as a Jabber
replacement.
On Tue, Feb 13, 2018 at 10:34 AM, Lelio Fulgenzi
<le...@uoguelph.ca<mailto:le...@uoguelph.ca>> wrote:
Well, that is certainly disappointing. Spark makes a softphone deployment much
easier, but not without key features like MWI.
I hate the fact that we’re going to have to deploy both to get all the features
we want/need.
---
Lelio Fulgenzi, B.A. | Senior Analyst
Computing and Communications Services | University of Guelph
Room 037 Animal Science & Nutrition Bldg | 50 Stone Rd E | Guelph, ON | N1G 2W1
519-824-4120 Ext. 56354<tel:(519)%20824-4120> |
le...@uoguelph.ca<mailto:le...@uoguelph.ca>
www.uoguelph.ca/ccs<http://www.uoguelph.ca/ccs> | @UofGCCS on Instagram,
Twitter and Facebook
<image001.png>
From: bmead...@gmail.com<mailto:bmead...@gmail.com>
[mailto:bmead...@gmail.com<mailto:bmead...@gmail.com>] On Behalf Of Brian Meade
Sent: Tuesday, February 13, 2018 10:31 AM
To: Lelio Fulgenzi <le...@uoguelph.ca<mailto:le...@uoguelph.ca>>
Cc: cisco-voip voyp list
<cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>>
Subject: Re: [cisco-voip] Spark Hybrid and MWI/Voicemail
Nothing I'm aware of. Just completed one of these. Basically just glorified
SNR with URIs and some calendar integration.
On Thu, Feb 8, 2018 at 7:38 PM, Lelio Fulgenzi
<le...@uoguelph.ca<mailto:le...@uoguelph.ca>> wrote:
Am I missing something?
Is there no voicemail integration with Connection? No MWI?
https://www.cisco.com/c/en/us/solutions/collaboration/spark-hybrid-services/index.html
Sent from my iPhone
_______________________________________________
cisco-voip mailing list
cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
cisco-voip mailing list
cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
cisco-voip mailing list
cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip