[cisco-voip] Cisco moth-balling CUE - Is Connection SRSV the answer?

[Pawlowski, Adam]

I use UCXN , the “Cisco” part I guess implied. Feels like one too many letters though.

As for cluster downtime, the only time we really had the system completely down had been for Unity -> Unity Connection migration, and if we have to grow the cluster again to support more Jabber clients and rebuild, that would also do it. COBRAS took about a billion years.

Adam

From: cisco-voip <cisco-voip-bounces at puck.nether.net> On Behalf Of Anthony Holloway
Sent: Monday, May 4, 2020 1:59 PM
To: Eric Pedersen <PedersenE at bennettjones.com>
Cc: voyp list, cisco-voip (cisco-voip at puck.nether.net) <cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] Cisco moth-balling CUE - Is Connection SRSV the answer?

"CUCX"

I find it interesting the different ways we Engineers write that.  I have also seen CUXN, CUCXN and CUC.  I'm team CUC, but I think we can all agree that simply "Unity" is wrong.

On Mon, May 4, 2020 at 12:45 PM Eric Pedersen <PedersenE at bennettjones.com<mailto:PedersenE at bennettjones.com>> wrote:
Yes, from what I remember it can operate while CUCM and CUCX are both up.

From: cisco-voip <cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net>> On Behalf Of Lelio Fulgenzi
Sent: Monday, May 4, 2020 9:37 AM
To: voyp list, cisco-voip (cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>) <cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
Subject: Re: [cisco-voip] Cisco moth-balling CUE - Is Connection SRSV the answer?

Do you know if SRSV can operate while CUCM is up?

The great thing about CUE, is that it operated while CUCM was up. Completely independent of Unity Connection.

This means, I could schedule downtime for Connection and have an almost fully operational AA working.

From: Eric Pedersen <PedersenE at bennettjones.com<mailto:PedersenE at bennettjones.com>>
Sent: Monday, May 4, 2020 11:35 AM
To: Lelio Fulgenzi <lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>>; voyp list, cisco-voip (cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>) <cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
Subject: RE: Cisco moth-balling CUE - Is Connection SRSV the answer?

CAUTION: This email originated from outside of the University of Guelph. Do not click links or open attachments unless you recognize the sender and know the content is safe. If in doubt, forward suspicious emails to IThelp at uoguelph.ca<mailto:IThelp at uoguelph.ca>

I used SRSV a while ago for one of our remote sites. I found it much simpler to get up and running than CUE and you can use your centralized Exchange.  IIRC you can send your voicemail pilot back to the gateway SRSV is registered to so all calls go to it. But it's been a really long time…

From: cisco-voip <cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net>> On Behalf Of Lelio Fulgenzi
Sent: Sunday, May 3, 2020 11:38 AM
To: voyp list, cisco-voip (cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>) <cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
Subject: [cisco-voip] Cisco moth-balling CUE - Is Connection SRSV the answer?


Looks like Cisco is moth-balling CUE. I liked that product. I’ll miss it.

It looks like Connection SRSV is the answer. Although I’m not sure it will offer everything we used (and planned to use) CUE for. For example, our voicemail ports forwarded to CUE which was always registered to CUCM. This way, calls would continue to work. It’s looking like SRSV will only work if the router is in SRST mode and all phones are registered to SRST.

Has anyone successfully deployed SRSV? How about using it during voicemail maintenance?

Lelio



Bennett Jones is committed to mitigating the spread of COVID-19. We have transitioned to a remote work environment and continue to provide complete and uninterrupted service to our clients. Visit our COVID-19 Resource Centre (https://www.bennettjones.com/COVID-19) for timely legal updates.

The contents of this message may contain confidential and/or privileged subject matter. If this message has been received in error, please contact the sender and delete all copies. Like other forms of communication, e-mail communications may be vulnerable to interception by unauthorized parties. If you do not wish us to communicate with you by e-mail, please notify us at your earliest convenience. In the absence of such notification, your consent is assumed. Should you choose to allow us to communicate by e-mail, we will not take any additional security measures (such as encryption) unless specifically requested.

If you no longer wish to receive commercial messages, you can unsubscribe by accessing this link: http://www.bennettjones.com/unsubscribe


Bennett Jones is committed to mitigating the spread of COVID-19. We have transitioned to a remote work environment and continue to provide complete and uninterrupted service to our clients. Visit our COVID-19 Resource Centre (https://www.bennettjones.com/COVID-19) for timely legal updates.

The contents of this message may contain confidential and/or privileged subject matter. If this message has been received in error, please contact the sender and delete all copies. Like other forms of communication, e-mail communications may be vulnerable to interception by unauthorized parties. If you do not wish us to communicate with you by e-mail, please notify us at your earliest convenience. In the absence of such notification, your consent is assumed. Should you choose to allow us to communicate by e-mail, we will not take any additional security measures (such as encryption) unless specifically requested.

If you no longer wish to receive commercial messages, you can unsubscribe by accessing this link: http://www.bennettjones.com/unsubscribe
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto: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/20200504/4ec67a6f/attachment.htm>