![]() (StoreContext ctx, StoreRequest request, AsyncCallback asyncCallback, Object state) (StoreContext ctx, ExStoreRequest exStoreRequest, StoreAsyncResult`1 asyncResult) (StoreContext ctx, String sipAddress, CreateItemType createItem, Boolean autoCreateParentFolder, StoreAsyncResult`1 asyncResult, Boolean reAuthorize) ![]() ![]() (StoreContext ctx, String sipUri, CacheMode cacheMode) (StoreContext ctx, String sipUri, Guid& tenantId, String& smtpAddress, String&userSid,String& userUpn) VERBOSE: Processing web storage response for ExCreateItem Failure., result=ErrorUserSmtpMissing, activityId=2a173b88-ecb5-43ca-a0be-09f3fdb7bb2e, reason=StoreException: code=ErrorUserSmtpMissing, reason=Found user but SmtpAddress is null/empty, ensure mailbox is enabled. VERBOSE: Execute Exchange Storage Command. However, at the end of the configuration, when the Test-CsExStorageConnectivity cmdlet it throws an error : VERBOSE: Successfully opened a connection to storage service at localhost using binding: NetNamedPipe. So again, another blog post from Cloud Exchangers about OAuth is very useful to implement this. This command means that Oauth (Server to Server authentication) between SfB on prem and Exchange online should be OK. Test-CsExStorageConnectivity –SipUri -Verbose I understood that for the Server Side Conversation History to work the cmdlet So, I used some useful blog posts from Cloud Exchangers for the whole process understanding of Server Side Conversation History. These two days I struggled to implement the new (well it dates from 2015) Server Side Conversation History for a customer who has a Skype for Business 2015 on-site (from Enterprise Voice and Telephony) and Exchange Online through Office 365.
0 Comments
Leave a Reply. |