integrate lync2013 with Exchange OWA2013

Hi,

can someone tell me how to perform the integration with OWA2013 via Lync topology builder? right now our company just installed 4 Exchange2013 (mbx/cas).

Do i need to add all 4 servers as trusted servers ? meaning i need to run below command 4 times with different exchange name? how about the port number, shall i assign different port number for each exchange ?

New-CsTrustedApplicationPool -Identity exchange01 -Registrar lyncpool.domain.com -Site 1 -RequiresReplication $False

New-CsTrustedApplication -ApplicationId OutlookWebApp -TrustedApplicationPoolFqdn exchange01 -Port 5199

May 19th, 2015 1:12pm

No need to add it four times. You should add Trusted Application Pool and add the Exchange servers to it. Remember, the name of the TAP (Trusted Application Pool) is... just that, a name. So, in Topology, add "New Trusted Application Pool" with "This computer has multiple servers" option and list your Exchange servers on the next screen. Then, when you create the Trusted Application, you will reference to the TAP FQDN.

Drago

Free Windows Admin Tool Kit Click here and download it now
May 19th, 2015 1:41pm

Hi Drago,

Let say if i named it that pool as 'OutlookWebApp', do i need to assign virtual IP to it ? after adding all my exchange to that pool, i still need to run below command right?

New-CsTrustedApplication -ApplicationId OutlookWebApp -TrustedApplicationPoolFqdn OutlookWebApp -Port 5199

thx.

May 19th, 2015 1:47pm

Hi!

You need certificate from Exchange and port for TrustedApplication. This is full guide:  

http://lyncdude.com/2013/06/26/integrate-lync-2013-with-exchange-2013-step-by-step-part-2/

Should be something like

New-CsTrustedApplication -ApplicationId OutlookWebApp -TrustedApplicationPoolFqdn mail.domain.com -Port 5199

where mail.domain.com points to your 4 mail servers.
  • Edited by Tuesday, May 19, 2015 2:14 PM
Free Windows Admin Tool Kit Click here and download it now
May 19th, 2015 2:07pm

While Topology is asking for "Pool FQDN", any name will be sufficient. You can name it Mickey Mouse if you want. Think of it as a "placeholder" and from this prospective, no need virtual IP. We will use the name in conjuction with the Trusted Application on the next step.

Of course, a meaningful name will be more useful. Since you are planning to use "OutlookWebApp" as application id, I would name the pool a little different - "OutlookWebAppPool" for example, to avoid confusion later.

Drago

May 19th, 2015 2:08pm

ok, thx. i have configured everything but still my OWA IM still not able to connect to Lync. While i have no issue when connecting using Lync client. my OWAPool name is same as certificate subject name which generated from internal CA. I'm able to see logging in Mailbox server OWA\Instantmessaging folder. Below is the error:

TL_WARN(TF_DIAG) [2]1DEC.90C4::06/02/2015-08:50:11.149.0006d2fa (SIPStack,SIPAdminLog::WriteDiagnosticEvent:SIPAdminLog.cpp(805))[883288899] $$begin_record
Severity: warning
Text: Routing error occurred; check Result-Code field for more information
Result-Code: 0xc3e93f13 SIPPROXY_E_CONTACT_NOT_AUTHORIZED
SIP-Start-Line: REGISTER sip:mydomain.my SIP/2.0
SIP-Call-ID: 898f13ec47a949ab83aac49fb78611d7
SIP-CSeq: 1 REGISTER
Peer: 192.168.242.12:30795
$$end_record

Free Windows Admin Tool Kit Click here and download it now
June 3rd, 2015 12:29pm

Have you configured the OwaVirtualDirectory for intergration yet? Here is a reference (it is for EX2010 but 2013 is the same) http://www.lynclog.com/2011/09/lync-exchange-2010-sp1-owa-integration.html

Drago

June 3rd, 2015 4:29pm

Hi Drago,

Below is my activity:

1. configured trusted application pool (giving pool name as my CAS server name).

2. configured certificate from internal CA

3. configured partner application.

4. i have seen event ID 112 in my exchange server, meaning integration is successful.

4. I'm able to connect to Lync server using Lync client 2013.

5. i have configured owa-virtualdirectory and owa mailbox policy.

however all i have done still failed. from Exchange mbx logging, i see below:

ERROR:InstantMessageOCSProvider.GenerateInstantMessageUnavailablePayload. Context: User=testuser@mydomain, Sip address=sip:testuser@mydomain, Lyncserver=lyncpool.mydomain. endPoint: Microsoft.Rtc.Internal.UCWeb.UCWAuthenticatedEndpoint, MethodName: InstantMessageOCSProvider.SignInCallback, InstantMessageServiceError: SipEndpointRegister, Exception: UCWEB Failure: Code=OcsRegisterFailure, SubCode=Undefined, Reason=None\r\nMicrosoft.Rtc.Internal.UCWeb.Utilities.UCWException: The endpoint was unable to register. See the ErrorCode for specific reason. ---> Microsoft.Rtc.Signaling.RegisterException: The endpoint was unable to register. See the ErrorCode for specific reason.\r\n   at Microsoft.Rtc.Signaling.SipAsyncResult`1.ThrowIfFailed()\r\n   at Microsoft.Rtc.Signaling.Helper.EndAsyncOperation[T](Object owner, IAsyncResult result)\r\n   at Microsoft.Rtc.Internal.UCWeb.UCWAuthenticatedEndpoint.OotyUserEndpointEstablish_callback(IAsyncResult asyncResult)\r\n   --- End of inner exception stack trace ---\r\n   at Microsoft.Rtc.Internal.UCWeb.Utilities.AsyncHelper.EndAsyncCall[T](IAsyncResult asyncResult, String methodName, T ucwScopeInstance)\r\n   at Microsoft.Rtc.Internal.UCWeb.UCWAuthenticatedEndpoint.EndSignIn(IAsyncResult asyncResult)\r\n   at Microsoft.Exchange.Clients.Owa2.Server.Core.InstantMessageOCSProvider.<>c__DisplayClass33.<SignInCallback>b__32(RequestDetailsLogger logger)"

While using Lync debugger, i'm getting below:

TL_WARN(TF_DIAG) [2]1DEC.90C4::06/02/2015-08:50:11.149.0006d2fa (SIPStack,SIPAdminLog::WriteDiagnosticEvent:SIPAdminLog.cpp(805))[883288899] $$begin_record
Severity: warning
Text: Routing error occurred; check Result-Code field for more information
Result-Code: 0xc3e93f13 SIPPROXY_E_CONTACT_NOT_AUTHORIZED
SIP-Start-Line: REGISTER sip:mydomain.my SIP/2.0
SIP-Call-ID: 898f13ec47a949ab83aac49fb78611d7
SIP-CSeq: 1 REGISTER
Peer: 192.168.242.12:30795
$$end_record

TL_INFO(TF_PROTOCOL) [5]1DEC.7884::06/05/2015-03:19:08.595.001176db (SIPStack,SIPAdminLog::ProtocolRecord::Flush:ProtocolRecord.cpp(265))[1287359414] $$begin_record
Trace-Correlation-Id: 1287359414
Instance-Id: 59D61
Direction: outgoing;source="local"
Peer: 172.20.242.112:40289
Message-Type: response
Start-Line: SIP/2.0 400 Invalid Contact information
FROM: <sip:testuser@mydomain>;epid=AF285D6E9D;tag=875b488dee
To: <sip:testuser@mydomain>;tag=4EBD9B54663D51475D3207CA2A7D29FB
CALL-ID: 0b33aa026f274b48a980b8f0c1844724
CSEQ: 1 REGISTER
Via: SIP/2.0/TLS 172.20.242.112:40289;branch=z9hG4bKb647b2ef;ms-received-port=40289;ms-received-cid=3C81900
Content-Length: 0
ms-diagnostics: 1018;reason="Parsing failure";source=server01@mydomain.com
$$end_record

Free Windows Admin Tool Kit Click here and download it now
June 6th, 2015 2:38am

Might be we can get together this weekend to look at your config?

Drago

June 6th, 2015 3:03am

Hi Drago, Yeah, how do i contact you ? Basically server at customer site and i did not have access via vpn. All works must performed on site. i am using latest exchange 2013 cu8 and lync 2013 on latest patch. Both services running on windows 2012 r2. On lync 2013 eventvwr, i have seen a lot of schannel error number 36888 in system log. Based on my research is due to TLS 1.2. However since no issue connecting to lync via skype/lync client 2013, i ignore this message. Do you think i should disable TLS 1.2 in order OWA IM to work? Anyway, i'm happy if you need further information. It has been almost a month this issue with me.
Free Windows Admin Tool Kit Click here and download it now
June 7th, 2015 12:27am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics