Forum Discussion

Icon for Microsoft rank

Microsoft

Jul 18, 2017

Discontinuation of support for Session Border Controllers in Exchange Online Unified Messaging

In July 2018, we will no longer support the use of Session Border Controllers (SBC) to connect 3 rd Party PBX systems to Exchange Online Unified Messaging (UM). We're making this change to provide ...

exchange online

Copper Contributor

Sep 25, 2017

We have a hybrid cisco/Lync/SfB environment with Hybrid Exchange and we have managed to retarget the Cisco UM through the Lync/SfB infrastructure to Exchange UM online using Sip Dial Plans with managed sip code on the FE's. Cisco environment dials an allocated pilot number which is a simple ExUMContact entry.

Eric Stevens
Copper Contributor
Sep 26, 2017
Are you willing to share the managed code?
- Lee Holland
  Copper Contributor
  Sep 26, 2017
  The version i have at the moment is customer specific, i'll generalise it and then publish it.
  
  Effectively what i am doing is taking the diversion header where the to header contains the pilot number, I then take the diversion number and look up the number in a generic list held in memory for the users sip address associated with UM, I then remove the to and diversion headers. I then re-create the to header as <sip:user@domain.com;opaque=app;voicemail;local-resource-path=voicemail>, then recreate the diversion header as <sip:user@domain.com>;reason=unknown. I then retarget the request to sip:user@domain.com;opaque=app;voicemail;local-resource-path=voicemail, this method doesn't matter whether is user has EV or AV but it is dependant on the user being Lync/SfB enabled and having the hostedvoicemail policy for o365.
  
  The server application has to be put in above the ExUmRouting service for two reasons,
  1 ExUMRouting strips the diversion header
  2 ExUMRouteing redirects the voicemail to the relevant service.
  
  I've found about 3 different ways to bounce it through so far, was only given the task last Friday.

Resources