Re: [cisco-voip] CUCM SU release cycle

2019-08-16 Thread Lelio Fulgenzi

This may sound silly, but in reality, it's out of my hands. I can make 
recommendations, but it all depends on the strategic decision the organization 
takes. Right now, cloud migrations are at the forefront. For a number of 
reasons.

Our on-premise deployment has a budgetary lifecycle of peaks and valleys. 
They'd rather see that flatlined. That's one thing. The other thing is that it 
takes a lot of effort to upgrade systems right now. Not because we don't know 
what we're doing, but it simply requires effort and co-ordination.  I've had to 
argue for the last 25 years that telephone services need special attention. 
Case in point, a completely isolated VM infrastructure since that's the only 
way we can build those reservations. It's been hard. I think they're sick of 
hearing it. Well, they've said they're sick of hearing it.

So if there's a cloud service that gives us 10% of the CUCM feature set and 95% 
of what we need. It might be time.


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

www.uoguelph.ca/ccs | @UofGCCS on Instagram, 
Twitter and Facebook

[University of Guelph Cornerstone with Improve Life tagline]

From: cisco-voip  On Behalf Of Pawlowski, 
Adam
Sent: Friday, August 16, 2019 12:58 PM
To: cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] CUCM SU release cycle

Regarding the SU release cycle, I believe I have heard similar claims before 
about cadence and committal to move forward and not maintain old code but I'll 
believe it when I see it.

Regarding the cloud services, we're being asked to look too like many shops. 
I'm struggling to find the real advantage to doing so, other than for the sake 
of it. Most of our customers treat our service like a utility, and if we have 
issues we are on it right away. Some don't really care, and that number grows a 
bit year over year. No one plans for continuing operations if there are 
interruptions, and if we ride over the commercial internet and lose that 
service as well people will freak out being cut off.

I'm still trying to work an angle to shift us internally towards user 
centricity a bit better. Get accounts for everyone, assign and track resources, 
one mailbox, etc. In trying to eliminate the old square/key PBX feel we built 
12 years ago out of this system (to replace so many of those ancient key 
systems), I'm hoping I can set us up to go forward into telephony applications, 
user focused services like Teams, etc which will make the pain easier. That 
would also let us get a better grasp on the classes of service that are going 
to form between the mission-critical and the yeah-it-would-be-nice-but-I-don't 
really-care, which can steer what runs prem or with fallback, and what runs 
hosted/cloud/out-of-my-hands.

Only real scare with a lot of these services is the lack of interface and 
access for someone like myself who likes APIs, who likes to tinker and build 
solutions and systems, instead of operating products.

Adam Pawlowski
SUNYAB NCS
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip


Re: [cisco-voip] CUCM SU release cycle

2019-08-16 Thread Pawlowski, Adam
Regarding the SU release cycle, I believe I have heard similar claims before 
about cadence and committal to move forward and not maintain old code but I'll 
believe it when I see it.

Regarding the cloud services, we're being asked to look too like many shops. 
I'm struggling to find the real advantage to doing so, other than for the sake 
of it. Most of our customers treat our service like a utility, and if we have 
issues we are on it right away. Some don't really care, and that number grows a 
bit year over year. No one plans for continuing operations if there are 
interruptions, and if we ride over the commercial internet and lose that 
service as well people will freak out being cut off.

I'm still trying to work an angle to shift us internally towards user 
centricity a bit better. Get accounts for everyone, assign and track resources, 
one mailbox, etc. In trying to eliminate the old square/key PBX feel we built 
12 years ago out of this system (to replace so many of those ancient key 
systems), I'm hoping I can set us up to go forward into telephony applications, 
user focused services like Teams, etc which will make the pain easier. That 
would also let us get a better grasp on the classes of service that are going 
to form between the mission-critical and the yeah-it-would-be-nice-but-I-don't 
really-care, which can steer what runs prem or with fallback, and what runs 
hosted/cloud/out-of-my-hands.

Only real scare with a lot of these services is the lack of interface and 
access for someone like myself who likes APIs, who likes to tinker and build 
solutions and systems, instead of operating products.

Adam Pawlowski
SUNYAB NCS
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip