cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1731
Views
5
Helpful
2
Replies

Cisco Presence Gateway pointing to Exchange for hybrid presence from O365

brown3wab
Level 1
Level 1

CUCM 11.5(1)SU6

IM&P 11.5(1)SU6

Echange 2013 / O365 hybrid environment - We have some users in both environments

 

The "Microsoft Outlook Calendar Integration for the IM and Presence Service, Release 11.5(x)"...

https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/im_presence/exchange_integration/11_5_1_SU3/cup0_b_ms-outlook-calendar-integration-1151su3/cup0_b_ms-outlook-calendar-integration-1151su3_chapter_01010.html

 

...states that "You cannot configure both an Exchange server and an Office 365 server as a Presence Gateway. If you want to integrate your IM and Presence Service deployment with both types of Microsoft deployments, you must configure an Exchange server as the Presence Gateway and configure integration between Microsoft Exchange and Office 365 from your Microsoft deployment."

 

Has anybody gotten this to work?  TAC seems to be pretty stand off when requesting details on how this works. 

 

In our environment, this does not work. The Cisco gateway config doc gives no reference on the specific configuration required on the Microsoft side. 

 

The Presence engine logs display "POST 499 ErrorNonExistentMailbox" for all O365 users, when Exchange is queried for their presence.  This gives the appearance that IM&P is looking for a mailbox in Exchange, which really lives in O365.  Cisco's documentation is basically stating it's up to Exchange to forward that request to O365.

 

Per Microsoft, this level of functionality does not exist in their hybrid environment.  The IM&P server should be using AutoDiscovery to locate the user living in either Exchange or O365.  Cisco's document states "This release of the IM and Presence Service does not support the Exchange autodiscover service. The autodiscover service assumes that a load-balancing mechanism is already in place across the Client Access Server (CAS) or servers"

 

Alternatively, IM&P can provide a crossforest user availability "free/busy" request. It doesn't appear that's what IM&p is doing, however. 

 

 

2 Replies 2

Reece
Level 1
Level 1

This doesn't really answer your question, but Microsoft are deprecating Basic Auth access for EWS to O365/EXO on Oct 13, 2020.

https://developer.microsoft.com/en-us/graph/blogs/upcoming-changes-to-exchange-web-services-ews-api-for-office-365/

 

 

Thanks!  Cisco's going to need to get some fixes out.

 

Bill