[cisco-voip] CUCM 10.5 and Office 365

[Nick Barnett]

I'd also add when comparing Exchange/UM to CUC with Cisco/UM, caller input
can get really complicated if you use non-DIDs inside your company
(especially since the SBC connection solutions are EOL). We have a "global"
opt out of "press 0 to speak to blah blah blah operator group", but the
actual number dialed hits CVP/ICM and routes around with non-PSTN numbers.
We also have some complex ToD routing done through CUC using the same
non-DID type numbers (hitting hunt pilots, CTI route points, etc). We'd
have to redesign our entire dial plan to accomodate ExO/UM.

On Wed, Sep 27, 2017 at 2:45 AM, Nathan Reeves <nathan.a.reeves at gmail.com>
wrote:

> In situations where a customer has gone O365 (and they've got licenses for
> Unity Connection Via CUWL Standard or Basic Messaging Licenses), I'd be
> using Unity for Voicemail and AA's, and using the Single Inbox
> functionality of Unity to get Voicemail's synced into the Users Exchange
> Mailbox.  Note that Single inbox is still available post 1 July 2018, it's
> only the SBC Functionality which is being deprecated.
>
> The only thing from memory you lose with Unity Connection Vs Exchange UM
> is missed call notifications.  Only issue I suppose is the additional tasks
> required to manage the unity mailboxes vs Checking the box in AD for
> Exchange.
>
> Nathan
>
> On Wed, Sep 27, 2017 at 2:47 PM, James Andrewartha <
> jandrewartha at ccgs.wa.edu.au> wrote:
>
>> On 27/09/17 13:12, Nathan Reeves wrote:
>> > To be honest it was the best thing to happen.  After inheriting a
>> > customer setup where they were using AA's on O365, with Cube acting as
>> > the SBC, we saw endless issues with calls being answered but no audio
>> > heard.  Wouldn't work for a varied length of time only to just start
>> > working again.  Managed to move them over to Unity Call Handlers and
>> > we've not skipped a beat since.  Like you, being in AU, we also saw
>> > latency through to the O365 tenancy, though I'm suspecting the issues we
>> > saw were not latency related.
>>
>> Hmm. AAs are less of an issue, we can leave them on the on-premises
>> Exchange server that a hybrid configuration leaves behind for
>> management. Voicemail is the main thing, at the moment it seems our
>> choices are go to Exchange 2016 on-premises or switch to Unity
>> Connection (we already have CUWL Standard for some reason) then go to
>> Exchange Online. Is there a third option?
>>
>> --
>> James Andrewartha
>> Network & Projects Engineer
>> Christ Church Grammar School
>> Claremont, Western Australia
>> Ph. (08) 9442 1757
>> Mob. 0424 160 877
>>
>
>
> _______________________________________________
> 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/20171005/fe3af7e4/attachment.html>