Re: [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 
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 <
> jandrewar...@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@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] CUCM 10.5 and Office 365

[Nathan Reeves]

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 <
jandrewar...@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@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] CUCM 10.5 and Office 365

[James Andrewartha]

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@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] CUCM 10.5 and Office 365

[Nathan Reeves]

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.

Nathan

On Wed, Sep 27, 2017 at 1:01 PM, James Andrewartha <
jandrewar...@ccgs.wa.edu.au> wrote:

> So it turns out Microsoft is killing SBC integration with Exchange
> Online UM on 1 July 2018, needless to say their customers are not happy:
>
> https://techcommunity.microsoft.com/t5/Exchange/
> Discontinuation-of-support-for-Session-Border-Controllers-in/m-p/88228
>
> There are some options like
> https://tsoorad.blogspot.com.au/2017/09/audiocodes-x-um.html but they
> may require CloudPBX licensing? Not sure.
>
> Anyway, this has just killed our Exchange Online migration.
>
> On 07/07/17 11:40, James Andrewartha wrote:
> > On 06/07/17 16:13, Gary Parker wrote:
> >> Hi Terry, our setup is very similar to yours (except we’re on 11.5, as
> opposed to 10.5) with the addition of a Cisco Unity Connection server for
> voicemail. CUCM is configured with voicemail ports pointing to the CUC
> server which holds the voicemail, sets MWI state, and duplicates the
> messages to our O365 mailboxes. The O365 integration is configured as a
> “Unified Messaging Service” within CUC and obviously relies on proper LDAP
> integration to ensure your Directory Numbers match up properly with users
> you configure to have unified voicemail boxes.
> >
> > We've been stuck with on-premises Exchange because we use it for
> > voicemail, and I've been put off by the fact our voicemail is directly
> > in Exchange UM. That and S4B in 365 is clearly not a solution for us in
> > Australia as they don't do PSTN integration without local SBCs.
> > http://forums.whirlpool.net.au/archive/2578229
> >
> > But at least now I know there are options if we stick with CUCM (which
> > is fairly likely given our reliance on Informacast). I'm still a bit
> > hesitant as there's 50+ms of latency to our 365 tenancy.
> >
> >> It appears you can do this without CUC, and connect directly to
> Exchange from CUCM via a SIP trunk (http://www.wavecoreit.com/
> blog/exchange/how-to-setup-cucm-10-5-for-exchange-2013-
> unified-messaging-voicemail/) but I don’t know if this will work with a
> hybrid O365 deployment and you get a *lot* more functionality from CUC (the
> main one being IVRs).
> >
> > Exchange UM can do IVRs, although they call them auto attendants. S4B
> > 365 only just got AAs in its Cloud PBX product. Either way I'm not
> > really interested in using CUC
> >
> >> Also, this from Cisco support communities (https://communities.cisco.
> com/thread/31729):
> >> If you are talking about using CUCM on premise and Exchange UM in the
> cloud then Cisco doesn't endorse or support it. MSFT has had an app note
> for it but it uses third party border controllers and you will have to work
> with two vendors support.
> >
> > https://blogs.technet.microsoft.com/nexthop/2016/04/
> 16/how-to-integrate-a-pbxip-pbx-phone-system-with-o365-exchange-um-online/
> > is from last year and notes the ASR 1000 is a supported SBC, along with
> > AcmePacket, AudioCodes, Ingate, NET and Sonus.
> >
> > I wonder if it would be possible to use ExpressRoute to talk directly to
> > the Exchange UM SBC from CUCM without having to use your own SBC, like
> > you can do with on-premises Exchange
> --
> 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@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] CUCM 10.5 and Office 365

[James Andrewartha]

So it turns out Microsoft is killing SBC integration with Exchange
Online UM on 1 July 2018, needless to say their customers are not happy:

https://techcommunity.microsoft.com/t5/Exchange/Discontinuation-of-support-for-Session-Border-Controllers-in/m-p/88228

There are some options like
https://tsoorad.blogspot.com.au/2017/09/audiocodes-x-um.html but they
may require CloudPBX licensing? Not sure.

Anyway, this has just killed our Exchange Online migration.

On 07/07/17 11:40, James Andrewartha wrote:
> On 06/07/17 16:13, Gary Parker wrote:
>> Hi Terry, our setup is very similar to yours (except we’re on 11.5, as 
>> opposed to 10.5) with the addition of a Cisco Unity Connection server for 
>> voicemail. CUCM is configured with voicemail ports pointing to the CUC 
>> server which holds the voicemail, sets MWI state, and duplicates the 
>> messages to our O365 mailboxes. The O365 integration is configured as a 
>> “Unified Messaging Service” within CUC and obviously relies on proper LDAP 
>> integration to ensure your Directory Numbers match up properly with users 
>> you configure to have unified voicemail boxes.
> 
> We've been stuck with on-premises Exchange because we use it for
> voicemail, and I've been put off by the fact our voicemail is directly
> in Exchange UM. That and S4B in 365 is clearly not a solution for us in
> Australia as they don't do PSTN integration without local SBCs.
> http://forums.whirlpool.net.au/archive/2578229
> 
> But at least now I know there are options if we stick with CUCM (which
> is fairly likely given our reliance on Informacast). I'm still a bit
> hesitant as there's 50+ms of latency to our 365 tenancy.
> 
>> It appears you can do this without CUC, and connect directly to Exchange 
>> from CUCM via a SIP trunk 
>> (http://www.wavecoreit.com/blog/exchange/how-to-setup-cucm-10-5-for-exchange-2013-unified-messaging-voicemail/)
>>  but I don’t know if this will work with a hybrid O365 deployment and you 
>> get a *lot* more functionality from CUC (the main one being IVRs).
> 
> Exchange UM can do IVRs, although they call them auto attendants. S4B
> 365 only just got AAs in its Cloud PBX product. Either way I'm not
> really interested in using CUC
> 
>> Also, this from Cisco support communities 
>> (https://communities.cisco.com/thread/31729):
>> If you are talking about using CUCM on premise and Exchange UM in the cloud 
>> then Cisco doesn't endorse or support it. MSFT has had an app note for it 
>> but it uses third party border controllers and you will have to work with 
>> two vendors support.
> 
> https://blogs.technet.microsoft.com/nexthop/2016/04/16/how-to-integrate-a-pbxip-pbx-phone-system-with-o365-exchange-um-online/
> is from last year and notes the ASR 1000 is a supported SBC, along with
> AcmePacket, AudioCodes, Ingate, NET and Sonus.
> 
> I wonder if it would be possible to use ExpressRoute to talk directly to
> the Exchange UM SBC from CUCM without having to use your own SBC, like
> you can do with on-premises Exchange
-- 
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@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] CUCM 10.5 and Office 365

[James Andrewartha]

Hi Gary,

On 06/07/17 16:13, Gary Parker wrote:
> Hi Terry, our setup is very similar to yours (except we’re on 11.5, as 
> opposed to 10.5) with the addition of a Cisco Unity Connection server for 
> voicemail. CUCM is configured with voicemail ports pointing to the CUC server 
> which holds the voicemail, sets MWI state, and duplicates the messages to our 
> O365 mailboxes. The O365 integration is configured as a “Unified Messaging 
> Service” within CUC and obviously relies on proper LDAP integration to ensure 
> your Directory Numbers match up properly with users you configure to have 
> unified voicemail boxes.

We've been stuck with on-premises Exchange because we use it for
voicemail, and I've been put off by the fact our voicemail is directly
in Exchange UM. That and S4B in 365 is clearly not a solution for us in
Australia as they don't do PSTN integration without local SBCs.
http://forums.whirlpool.net.au/archive/2578229

But at least now I know there are options if we stick with CUCM (which
is fairly likely given our reliance on Informacast). I'm still a bit
hesitant as there's 50+ms of latency to our 365 tenancy.

> It appears you can do this without CUC, and connect directly to Exchange from 
> CUCM via a SIP trunk 
> (http://www.wavecoreit.com/blog/exchange/how-to-setup-cucm-10-5-for-exchange-2013-unified-messaging-voicemail/)
>  but I don’t know if this will work with a hybrid O365 deployment and you get 
> a *lot* more functionality from CUC (the main one being IVRs).

Exchange UM can do IVRs, although they call them auto attendants. S4B
365 only just got AAs in its Cloud PBX product. Either way I'm not
really interested in using CUC

> Also, this from Cisco support communities 
> (https://communities.cisco.com/thread/31729):
> If you are talking about using CUCM on premise and Exchange UM in the cloud 
> then Cisco doesn't endorse or support it. MSFT has had an app note for it but 
> it uses third party border controllers and you will have to work with two 
> vendors support.

https://blogs.technet.microsoft.com/nexthop/2016/04/16/how-to-integrate-a-pbxip-pbx-phone-system-with-o365-exchange-um-online/
is from last year and notes the ASR 1000 is a supported SBC, along with
AcmePacket, AudioCodes, Ingate, NET and Sonus.

I wonder if it would be possible to use ExpressRoute to talk directly to
the Exchange UM SBC from CUCM without having to use your own SBC, like
you can do with on-premises Exchange.

Thanks,

-- 
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@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] CUCM 10.5 and Office 365

[Gary Parker]

> On 6 Jul 2017, at 00:53, Terry Oakley  wrote:
> 
> We are currently working towards moving our MS office products to Office 365. 
>   We have currently a hybrid 2013 Exchange server that is routing emails etc 
> to either our legacy system or the new Office 365 cloud.   The part I am 
> working on is unified messaging and how to get the UM portion to function so 
> that voice mail is handled and the message waiting indicator is on or off.
> Anyone had experience with this configuration?
>  
> CUCM 10.5
> Exchange 2007 inhouse
> Exchange 2013 hybrid
> Office 365 hosted in the cloud
> Expressway C
> Expressway E

Hi Terry, our setup is very similar to yours (except we’re on 11.5, as opposed 
to 10.5) with the addition of a Cisco Unity Connection server for voicemail. 
CUCM is configured with voicemail ports pointing to the CUC server which holds 
the voicemail, sets MWI state, and duplicates the messages to our O365 
mailboxes. The O365 integration is configured as a “Unified Messaging Service” 
within CUC and obviously relies on proper LDAP integration to ensure your 
Directory Numbers match up properly with users you configure to have unified 
voicemail boxes.

It appears you can do this without CUC, and connect directly to Exchange from 
CUCM via a SIP trunk 
(http://www.wavecoreit.com/blog/exchange/how-to-setup-cucm-10-5-for-exchange-2013-unified-messaging-voicemail/)
 but I don’t know if this will work with a hybrid O365 deployment and you get a 
*lot* more functionality from CUC (the main one being IVRs).

Also, this from Cisco support communities 
(https://communities.cisco.com/thread/31729):
If you are talking about using CUCM on premise and Exchange UM in the cloud 
then Cisco doesn't endorse or support it. MSFT has had an app note for it but 
it uses third party border controllers and you will have to work with two 
vendors support.


---
/-Gary Parker--f--\
| Unified Communications Service Manager  |
n  Loughborough University, IT Services   |
| tel:+441509635635 sip:g...@lboro.ac.uk  o
| http://delphium.lboro.ac.uk/pubkey.txt  |
\r--d-/

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

[cisco-voip] CUCM 10.5 and Office 365

[Terry Oakley]

We are currently working towards moving our MS office products to Office 365.   
We have currently a hybrid 2013 Exchange server that is routing emails etc to 
either our legacy system or the new Office 365 cloud.   The part I am working 
on is unified messaging and how to get the UM portion to function so that voice 
mail is handled and the message waiting indicator is on or off.Anyone had 
experience with this configuration?

CUCM 10.5
Exchange 2007 inhouse
Exchange 2013 hybrid
Office 365 hosted in the cloud
Expressway C
Expressway E

Thanks

Terry

Sent from Mail for Windows 10

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