Using Exchange Connector with Exchange Online / o365.

You can locate the EWS URL with the Test E-Mail Autoconfiguration in Outlook. To do it,

--Start Outlook client.

--Hold down the CTRL key, right-click the Outlook icon in the notification area, and then click Test E-mail AutoConfiguration.

--Verify that the correct email address is in the E-mail Address box.

--Click to clear the Use Guessmart check box and the Secure Guessmart Authentication check box.

--On the Test E-mail AutoConfiguration page, click to select the Use AutoDiscover check.

--From the Results tab locate the Availability Service URL.


From there you will configure impersonation.  Use the following 

Phantom Park Issues

There is a rare condition wherein calls will remain visible in the Parking lot after they have been either retrieved or hung up. The counter will count down to zero, the call with briefly disappear, the call will reappear and the process starts over again.

It appears that it can affect all versions of CallManager prior to version 10.x.

In essence, after the call is no longer in the Parking slot, we are not getting an UnPark Event from CallManager


There is a fix available by contacting Cisco TAC. Reference the following numbers.


CSCty67720 - CTI handler leak in Callpark manager
CSCty04584 - Idle event not reported in hunt list RNA race scenario

Call transfer issues

If you are having trouble transferring calls it may be a result of an improperly set prepend digit.
Verify both the client settings and the server side setting.

Client

Server

However, if the prepend digit is not the issue, it may be a gateway configuration issue.
Especially if you are trying to transfer a call you put on hold.
When handling a held call, we don't actually transfer the call.  We do a redirect.  This allows the call to retain all of the original call information and not be stamped with the operator's information.
The trouble is in that original call did not have all of the correct information to begin with.
Confusion arises because you cannot actually recreate it with a physical phone since you cannot actually perform a redirect on phone.

You can test this by performing the the same Call->Answer->Place on Hold -> Transfer process with a call that originates from another internal extension.  It should complete as expected.

This problem and fix resides on the gateway configuration.  The fix is phrased somewhat differently depending upon the gateway type (MGCP, ISDN, H.323,SIP etc) but its the same logic.

Select the box for Redirecting Number or Redirecting Diversion Header Inbound/Outbound.
This change will require a Gateway reset, so you may need a maintenance window.

More information can be found here.
https://supportforums.cisco.com/discussion/10926046/call-forwarding-retain-redirecting-device-information

Launch issues

If you experience issues at launch time that appear to be a freeze or stuck screen, there may be an issue with .NET framework.

• .NET Framework 4.5 depends on the Windows Performance Counters..You can reinitialize them by typing the following at a Command Prompt.
       lodctr /R
  You must run this command as a local administrator.
  
  If you receive an Error 5, you are not an admin.
  If you receive an Error 2, make sure you are running from the C: drive.
  
  This should repair the condition and allow BOC to launch.
  
  
• A second issue is with .NET Framework 4.7.
  If you see a Windows Application Event log with the following Warning message.
  
     An unhanded exception just occurred.  The type initializer for 'MS.Win32.Penimc.UnsafeNativeMethods' threw an exception.
  
  Uninstall .NET Framework 4.7 and install .NET 4.6.2 instead.
  
  This should repair the condition and allow BOC to launch.