[cisco-voip] how long to let expressway updates bake

Matt Jacobson m4ttjacobson at gmail.com
Tue Aug 1 04:16:38 EDT 2017


Hi all,

Has anyone moved to X8.10.0? I heard .1 is a little further away than
expected. I'm curious to see if anyone has taken the plunge. This
particular cluster does not run MRA, but it does have Jabber Guest and B2B
calls running across it with over 500 registrations on the Exp-C.

Thanks

On Tue, Jul 18, 2017 at 12:32 PM, Lelio Fulgenzi <lelio at uoguelph.ca> wrote:

> **phew**
>
>
>
> ---
>
> Lelio Fulgenzi, B.A.
>
> Senior Analyst, Network Infrastructure
>
> Computing and Communications Services (CCS)
>
> University of Guelph
>
>
>
> 519-824-4120 Ext 56354 <(519)%20824-4120>
>
> lelio at uoguelph.ca
>
> www.uoguelph.ca/ccs
>
> Room 037, Animal Science and Nutrition Building
>
> Guelph, Ontario, N1G 2W1
>
>
>
> *From:* Ryan Huff [mailto:ryanhuff at outlook.com]
> *Sent:* Tuesday, July 18, 2017 12:10 PM
> *To:* Lelio Fulgenzi
> *Cc:* Tim Frazee; cisco-voip at puck.nether.net
>
> *Subject:* Re: [cisco-voip] how long to let expressway updates bake
>
>
>
> I'm talking about the remote screen sharing features :).
>
> Sent from my iPhone
>
>
> On Jul 18, 2017, at 12:05 PM, Lelio Fulgenzi <lelio at uoguelph.ca> wrote:
>
> What? Jabber MRA not working in Expressway 8.8+
>
>
>
> Wasn’t that the primary reason for expressway? Eeeeeek.
>
>
>
> Is this in the release notes?
>
>
>
> ---
>
> Lelio Fulgenzi, B.A.
>
> Senior Analyst, Network Infrastructure
>
> Computing and Communications Services (CCS)
>
> University of Guelph
>
>
>
> 519-824-4120 Ext 56354 <(519)%20824-4120>
>
> lelio at uoguelph.ca
>
> www.uoguelph.ca/ccs
>
> Room 037, Animal Science and Nutrition Building
>
> Guelph, Ontario, N1G 2W1
>
>
>
> *From:* cisco-voip [mailto:cisco-voip-bounces at puck.nether.net
> <cisco-voip-bounces at puck.nether.net>] *On Behalf Of *Ryan Huff
> *Sent:* Monday, July 17, 2017 3:28 PM
> *To:* Tim Frazee
> *Cc:* cisco-voip at puck.nether.net
> *Subject:* Re: [cisco-voip] how long to let expressway updates bake
>
>
>
> I'd personally say anything 8.8+ is good 2 go and it's mostly still just
> the Jabber stuff that doesn't work over MRA (which is documented).
>
> Sent from my iPhone
>
>
> On Jul 17, 2017, at 3:20 PM, Tim Frazee <tfrazee at gmail.com> wrote:
>
> When I say "sit" would be how long do I let other Cisco customers find any
> serious issues before I would hop on. Wait for the "a" revision to drop.
> was typical back in the day. not sure if expressway had the same history.
>
>
>
> On Mon, Jul 17, 2017 at 10:25 AM, Ryan Huff <ryanhuff at outlook.com> wrote:
>
> Not sure what you're referring to by "sit"? Are you referring to a
> hardware burn-in of the host chassis the guest VM is running on?
>
> During the non-production period, is the business using it to validate its
> configuration and usability for its specified business case? Usually, once
> UAT (User Acceptance Testing) is completed and signed off on I would kick
> it in to production during a scheduled window.
>
> For chassis burn-in, I like to see a week in the production racks.
>
> Thanks,
>
> -Ryan
>
> Sent from my iPhone
>
>
> > On Jul 17, 2017, at 10:32 AM, Tim Frazee <tfrazee at gmail.com> wrote:
> >
> > Hi
> >
> > new to the expressway suite and was wondering whats the average wait
> time (if any) for new versions of expressway to sit before you consider
> them production worthy.
> >
> > for ucm/cup/cuc, I usually give it no more than a month before I would
> consider it "stable" but was interested in what this group tends to lean to.
>
> > _______________________________________________
> > 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20170801/7628f984/attachment.html>


More information about the cisco-voip mailing list