Lync 2013 integration with OWA

Hi,
I am integrating Lync 2013 ( with SBAs as branches) with OWA 2010.
The IM and presence works fine for users homed in the front end pool. However for users in the branch pool it does not work as the certificate is rejected by the CAS server.
SBA uses same server authentication certificate ( OAuth) as the front end. ( which I believe is expected)
Below is the error msg im seeing :
brief error logs:
================
TL_WARN(TF_PROTOCOL) [<SBA>\<SBA>]0704.11F0::06/04/2014-04:45:05.129.00001662 (UserServices,CRegister::OnClientDisconnected:register.cpp(1130)) ( 0000000002AACC20 ) Disconnecting client [[email protected]]/EndpointId
[a9cf0cb1-b611-50ae-8652-3cab8a0c8056] as it has crashed
TL_ERROR(TF_CONNECTION) [<SBA>\<SBA>]0704.11F0::06/04/2014-04:45:05.129.00001663 (SIPStack,SIPAdminLog::WriteConnectionEvent:SIPAdminLog.cpp(460)) [4230621814] $$begin_record
Severity: error
Text: The connection was closed before TLS negotiation completed. Did the remote peer accept our certificate?
Local-IP: <SBA ip>:62858
Peer-IP: <CAS server ip>:5075
Connection-ID: 0x1FEB401
Transport: TLS
$$end_record

Similar issue here...users homed on the SBAs can only see each other in OWA...users homed in other pools show gray presence indicators.

Similar Messages

Lync 2013 integration with Avaya Aura Session Manager 6.3

Dear All,
we are planning to integrate Lync 2013 with Avaya Aura Session Manager 6.3 and Avaya
Communication Server 6.3.1 for one of our client.
As per the technical documentation from MS, it shows the integration with lync 2013 with Avaya aura session manager
6.3 and Communication Server 1000 (CS1K).
Please let me know is there any difference between Communication Server
1000 (CS1K) and Avaya Communication Server 6.3.1.

Hi,
From the link below of “Infrastructure qualified for Microsoft Lync”: Aura Session Manager 6.3 is supported with Lync Server 2013.
https://technet.microsoft.com/en-us/office/dn788945
Configuration Notes:
1.Media Bypass, RTCP, and History-Info were set to Enabled.
2.REFER and Session Timer were set to Disabled.
Known Limitations:
1.With Media bypass enabled in Lync, for an incoming call to Lync client that has simultaneous ring to a number with early media enabled, caller will hear ring back instead of the early media.
2.Avaya Aura communication manager does not send disconnect to PSTN via ISDN trunk while receiving SIP 603 response from Mediation server for incoming call to Lync client. Caller will hear overflow tone and call will not disconnect until caller drops the
call.
What’s more, it is better to contact IP-PBX vendor for the installation and set up as they have the complete documentation.
Best Regards,
Eason Huang
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Eason Huang
TechNet Community Support

Lync 2013 integration with Avaya Communication Manager Version 5.2 and Avaya Session Manager 6.3

Hi Team,
I have a situation, We have done integration between Avaya Communication Manager Version 5.2, Avaya Session Manager 6.3 and Lync 2013.
I’m able to make lync to lync call via extension number but not lync to avaya extension vice versa and lync to mobile calls. Will appreciate your help.
A PBX gateway has been marked as less-preferred.
Gateway name: sm.contoso.com
Response Code: 400
Consecutive Failure occurrences: 29
Cause: The gateway responded with the same failure response multiple consecutive times and is being marked as less-preferred.
Resolution:
Verify that the gateway is functioning correctly.

Did you add Avaya Session Manager as a PSTN gateway in Lync Topology?
Did you create dial plan and related normalization rule for extension in Avaya telephone system.
Which guide did you use to integrate Avaya Aura Session Manager with Lync Server?
You can check the following deployment guide:
http://www.microsoft.com/en-hk/download/details.aspx?id=41152
Lisa Zheng
TechNet Community Support

Biztalk 2013 integration with CRM 2015

Hi,
I am working on a BizTalk 2013 integration with CRM 2015 on premise server and currently developing a POC to see how it works. There are quite a few good articles on BizTalk-CRM integration and I am referring them while building this POC. However I thought
of taking expet’s advice for this. Here are my requirements as of now.
Search CRM contacts by Fname, Lname etc.. And definitely not by Contact ID which is GUID. In this case BizTalk can expect responses like Single contact, Multiple contacts, Contact Not found or soap fault.
Create a single contact record in CRM from BizTalk.
Update Contact details in CRM like multiple addresses for a single contact.
So we have 2 approaches to integrate CRM, using untyped soap endpoint or CRM SDK.
I did an orchestration today with soap endpoint for “Retrieve” operation bypassing a GUID and can see the response returned. But how to pass the fname, lname etc. instead of GUID as there are no fields to populate in the soap Retrieve schema?
Is it wise decision to use untyped soap UI instead of CRM SDK proxy by keeping the above 3 requirements in mind?
Using SOAP endpoint, how can achieve the requirement 1 that returns multiple contacts?
I have seen articles using Query and Fetch to get multiple contacts and I really don’t understand it. Is it the only way to get multiple contacts?
Thanks!
JB

Hi Abhishek,
While exploring the CRM REST capabilities i found the below content on MSDN that says the REST endpoint works only for getting the contact by uniqueID and not by firstname and lastname etc...
https://msdn.microsoft.com/en-us/library/gg328090.aspx#BKMK_RetrievingRecords
Retrieving records
HTTP GET is used when you are retrieving records. When a unique identifier for
a specific record is provided, only that record will be retrieved. Otherwise, any system query options that are defined will be applied and up to 50 records will be retrieved that match any system query option filters.
We can't use a GUID as it is name search from customer website and GUID available at that stage.
So if it works only with GUID then we have to use either CRM SDK or SOAP enpoint right?
Cheers
JB

Lync 2013\Exchange 2010 OWA Integration Problem

Hi there,
I've got a vexing issue that I haven't had much luck in researching. I am running Lync 2013 on Server 2008 R2 and Exchange 2010 SP3 on Server 2008 R2. I followed Jeff Schertz's instructions (http://blog.schertz.name/2010/11/lync-and-exchange-im-integration/)
and Lync\OWA integration is working--sort of.
We currently have a central pool (we'll call it lyncpool.contoso.com) and three pools housed on SBAs-- lyncsba-loc1, lyncsba-loc2,lyncsba-loc3. Users in our main location are housed on the central pool, whereas users in our remote locations are housed
on their respective SBA.
Following the instructions, I pointed my OWA virtual directories at lyncpool.contoso.com, and everything seemed fine at first. I could see presence in OWA, initiate an instant message...the works. However, when I asked a user homed on one of the SBAs,
he said that he could only see presence for other users in his pool\location. Everyone else had a white "unknown" presence chiclet. To verify, I temporarily moved my lync account to that branch pool, and sure enough--I saw the same thing. As
a troubleshooting measure, I re-ran the OWA configuration portion and instead of using the central pool as the instantmessagingserver value, I pointed it directly at that branch pool. At that point, he and I, being homed in that branch pool, could see
presence for EVERYONE. Problem solved, right? Well, no...because now, the central pool users could only see presence for other central pool users, and the other branches could still only see presence for their poolmates.
I've run Wireshark, CLS logging, you name it--I haven't seen anything fishy, and I'm starting to wonder if this perhaps a bug or an unsupported use-case(I hope not, since Microsoft otherwise endorses such a configuration). I've been beating my head
against this wall for almost two weeks with no change...someone, help! :)

This is the only thing that seems of interest in the CLS Log:
TL_WARN(TF_DIAG) [lyncpool01\VGTLYNCFE-01]1B70.4184::06/17/2014-20:47:03.028.00001F75 (SIPStack,SIPAdminLog::WriteDiagnosticEvent:SIPAdminLog.cpp(805))
[1781536493] $$begin_record
Severity: warning
Text: Cannot process Route headers from a non-trusted source, or with first Route field in the set not matching the connection on which the request arrived
Result-Code: 0xc3e93c5e SIPPROXY_E_ROUTING
SIP-Start-Line: SUBSCRIBE sip:LyncPool01.xxx.net:5061;transport=tls;ms-fe=VGTLYNCFE-01.xxx.net SIP/2.0
SIP-Call-ID: 45c62e9edaee4252908914b37ca5ef23
SIP-CSeq: 1895 SUBSCRIBE
Source: mail.xxx.net:47892
$$end_record
The "source" here is our OWA server. I have issued a certificate from our local CA(the same one that issued the Lync certs), making sure the CN of the certificate matches the OWA url. Any ideas?

EXC13 cu7, Lync 2013 last updates OWA integration error

Hello,
we have 3 cas and 3 mbx exc13 cu7 environment
when a user from a specified database tries to log on OWA IM through OWA he can't
if we move mount the database to another mbx server it works fine
all users (where their databases are mounted at mbx2) are getting this error
I used this article
http://blogs.technet.com/b/jenstr/archive/2012/10/31/troubleshooting-tips-for-exchange-2013-owa-im-integration-to-lync-2013.aspx
and we got nothing new
always the same error on IM logging at mbx \ v15\logging\owa\ logs
2015-04-13T14:48:18.774Z,102,5,,,,0,DEBUG:Globals.Initialize: Initialization failed.,
Thiago Beier Se foi útil marca como resposta! Don´t forget to mark as answer!

Hi,
Please confirm if there is an event 103 on the Exchange Even Viewer when the user logs in OWA IM. If there is the event, please provide the detailed event log here for further analysis.
Please run the following command to check the certificate information in your Exchange server:
Get-ExchangeCertificate | fl
We need to collect the certificate thumbprint which is added in OWA web.config file and compare it with Exchange certificate results.
Generally, the certificate which is added in OWA web.config file on the MBX server(s) should be trusted by both Lync Server and Exchange. It is generally created by using your internal certificate authority on the mailbox server, making sure
that the server FQDN is used for the subject name and that this FQDN appears in the certificate alternate name field.
If it is not match, please create a new certificate from your
internal certificate authority on the mailbox server. Then add the certificate thumbprint in the right section of the OWA web.config file (<appSettings>), restart IIS service and check whether the issue persists.
Regards,
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Winnie Liang
TechNet Community Support

Lync Server Integration with Exchange 2013

Hello,
I have Exchange 2013 standard edition server installed and running successfully on a Windows 2012 machine. Now, I would like to have a Lync 2013 server integrated with it. I came across some links telling that its not possible to integrate Unified Messaging
in the Exchange standard edition and would need an Enterprise edition license. But, when I checked my ECP, I could see that UM is already there and its enabled.
So, Is it possible to integrate Lync 2013 with Exchange 2013 standard edition? What all things I need to take care of while Integrating? If someone could shed some light on this, that would be greatly appreciated.
Thanks and Regards,
Nash Burns

Yes you can integrate Lync 2013 with Exchange 2013 Standard, the only big difference between Exchange 2013 Standard vs Enterprise is the number of mailbox databases (5 vs 50).
Follow this link for information on integrating the two: http://technet.microsoft.com/en-us/library/jj688098.aspx (specifically integrating Lync with Exchange for Voicemail http://technet.microsoft.com/en-us/library/jj687983.aspx)
Having said that, the confusion may be related to User CALs. You need Exchange Enterprise User CALs to use the Unified Messaging components. (I believe they still work regardless, but
to be properly licensed and compliant you need to have the correct number of Enterprise CALs for the number of users that use UM)
If this helped you please click "Vote As Helpful" if it answered your question please click "Mark As Answer" | Blog
www.lynced.com.au | Twitter
@imlynced

Lync 2013 Intergration with Siemens HiPath 4000 and HiPath 3500

Dear All,
We have implemented Lync 2013 with 2 FE , 1 PChat , 1 OWA and 2 Edge Server (DNS Load Balancing with NAT) , we are now in the next phase where we need to provide complete voice integration,
The customer is currently using Siemens HiPath 4000 at main office and Siemens HiPath 3800 and HiPath 3500 at the Branch offices,
Our scope is as under,
1) As first part intergrade the we have to integrate it with Siemens HiPath 4000 , with below features,
a) Lync User ability to dial via the PRI Lines
b) Lync User to receive Calls made to their Siemens extension on Lync Client ( Simultaneous ringing or enabling mobility (Similar to Cisco Mobility- When DID calls come they ring both on physical phone and Lync Client)
c) Features Such as Call forwarding , Hunt Groups , Integrated Exchange 2010 UM support ,
Finally Since we need to phase out Siemens we would have SBC 2000 gateway
We have 5 PRI lines going to Siemens HiPath , post this we would transfer one of the lesser used PRI to SBC 2000 , while maintaining complete functionality,
A similar setup would also be done at the Branch Office , except that we would be having SBC 1000 at one of the branch offices and Sangoma Lync Express at the other Branch Offices,
What we need ,
1) Design related suggestions
2) Implementation related challenges and hurdles
3) Dos and Donts , we do not want to over commit the client and then regret,
4) Any kind of Guide and similar scenarios implemented by other , step by step documents,
5) Best Practices , limitations and things to avoid, Suggestions
Thanks and Regards,
Hasan Reza

Dear All ,
I am sure all you guys who have advised me are much more experienced and have a better understanding of Voice,
I would like to rest my solution based on below design , before I submit the same to the customer, Need one final check list , Pls advise / confirm ,
Also please help me with the pre-requisites that I need to go to client with ? If there is something missing pls highlight
Looking at the changed design ,
Here is call flow
1) Calls comes via ---> PRI to Siemens HiPath
2) Hipath locally routes the call if the Extension is present in the Local System
3) If not then call is sent to Sip Trunk that would be accepted by the Sonus 2000
4) Sonus would then forward to the call to Lync 2013
5) Lync 2013 establishes the call with Lync Client
In this scenario , what would be the impact on below
0) Can we have same series of extension , for example (4001, 4002 , 4003 on traditional PABX , and have 4101,4102,4103 on Lync 2013)
1) Conference calls between Lync and Traditional PABX Systems
2) Currently all the Extension are configured with DID nos , any out going calls has the users DID no , after a user is moved to Lync 2013 , then the DID number associated with user , how would that behave ?
3) Can from a I transfer a user and his/her PRI to Sonus, or I should transfer the entire PRI Bunch,
4) Will there be an impact on caller ID , MOH (Music on Hold) , Hunt groups,
5) Will the same concept be used for Branch Offices as well ?
Please pardon my queries but if the above are made clear I am sure many people would benefit from this blog.
Thanks and Regards,
Hasan Reza

Cisco VCS/Codian MCU and Lync 2013 integration

Hi,
I would like to know if Lync 2013 is supported to work with:
- Cisco Tandberg VCS version x6.1
- Cisco Codian 4.1 (comp. 6.16)
Is it necessary to update both devices to be supported/homologated/qualified?
Thanks

Hi, Kent ... From what I'm seeing so far the challenges of integrating Cisco/Tandberg equipment and Lync 2013 are the same as what you may have already encountered with Lync 2010. Since the Cisco endpoints and MCU cannot register directly to Lync 2010
or 2013, you will need to leverage the VCS systems as your SIP gateway between them and Lync clients. In Lync 2010 there were limitations as to the interoperability of the H.263/264 codec used by Cisco gear and the RTV codec that Lync was restricted
to, and we often experienced frozen video feeds from Lync clients or an inability to connect to individual Cisco endpoints or conferences hosted by the Codian MCU. Even though Lync 2013 will use H.264 as a codec for the video stream, I anticipate there
will still be challenges interconnecting through the VCS as well as providing content between Lync and Cisco endpoints. However, I expect an increase in the video quality since Lync 2013 supports higher resolutions and also uses a non-proprietary codec.
I expect content to still be unreliable for the Lync participant, even when using a Codian MCU.
You will still need to setup your VCS with a separate Neighbor zone for the Lync 2013 server just as you did for Lync 2010. I wouldn't hold my breath for Cisco to update the VCS software to accomodate the specific needs of Lync 2013, but at least the
VCS will get the correct video codec and connect your call. I don't know about you but I had to put my Cisco units and MCU into a separate SIP domain from the Lync pool, and then create a static route for the Cisco SIP domain on the Lync 2010 front-end
server. I expect to do the same in Lync 2013.
Ideally, Microsoft and Cisco would agree that SIP is SIP, and whether an endpoint registers with VCS, UCM or Lync shouldn't be relevant. Alas, it'll be a long, long time before that is true, certainly not as long as Microsoft and Polycom have
such a tight bond. I plan on implementing Lync 2013 in the next few months and will gladly post any progress here. At this point my plan is to simply mirror the static route and configuration I have with Lync 2010. My VCS and Codian units
are running software versions just a little ahead of yours and work fine.
Good luck!

Lync 2013 problem with interaction in Hyper-V

Hello,
during the conference in Lync 2013 does
not work the guest interaction service,
which has been referred to the control
(display the
desktop). The
guest can move the
cursor, but
can't click or
write in Hyper-V virtual
machine. In
a virtual machine running Windows Server 2012R2. Enhanced VM Interaction is
on.
What to do to give away full
control for the guest?

I may be confused, but it looks like you're trying to control a server VM with this capability. Do the actions require elevated or administrator access? If so, by security design this won't work.
"It is worthwhile mentioning that people who you gave control to in a desktop sharing session will not be able to interact with elevated prompts."
The article below mentions this, and suggests running as Lync as administrator which we've not had great success with.
http://blogs.technet.com/b/lync/archive/2012/11/02/presenting-your-screen-in-lync-2013.aspx
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer".
SWC Unified Communications

How to connect Lync 2013 client with OCS 2007 R2 Edge server

Hi,
We have OCS 2007 R2 Edge server for external & OCS 2007 R2 FE Server for internal access in our environment.
We able to access internally Lync2013 clients with OCS 2007R2 server, however from external we cannot access Lync2013 client with OCS2007 R2 server.
Is there any patch or registry key trick to access OCS from lync2013 client externally? We cannot immediately migrate to Lync2013 server from OCS.
Any help
MD

Hi,
I suggest you still use OCS 2007 R2 client to login OCS 2007 R2 Server untill finishing migration to Lync Server 2013, as using Lync client with OCS 2007 R2 Server will offer a pretty limited experience.
Here is a great blog about Lync 2010 Client unsupported with OCS, it is for Lync 2010 client but similar for Lync 2013 client:
http://blog.schertz.name/2010/09/lync-client-unsupported-ocs/
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there.
Please make sure that you completely understand the risk before retrieving any suggestions from the above link.
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Lync 2013 design with minimum resources

Let me give one example and ask.
For 1000 users , Lync 2013, only IM/presence, Audio/Video etc., High availability needed, DR needed.
Plan to have 2 FE servers in DC and 1 FE in DR, all 3 FE are part of one pool. How is this idea? Will FE server in DR require license as it is in passive mode?
OR
2 FE servers in DC and 1 FE in DR , both are in different pool, I understand MS does not recommend to have 2 FE , it should be at least 3 but there are cases where it can be done. Hows this idea?
Which option is better and cost effective?
1 SQL , 1 SQL witness in DC and 1 SQL in DR , these are mirrored , is there any drawback of this?
2 Edge in DC , 1 Edge in DR in different pool OR 1 Edge in DC and 1 Edge in DR in same pool. Which one is better and possible way?

1) Stretching a pool across geographic areas isn't supported anymore. You'd need 20ms latency and a 1 Gbps connection in the Lync 2010 days.
http://technet.microsoft.com/en-us/library/gg679096(v=ocs.14).aspx
Yes the DR server would require a license, there is no passive in the pool.
The second option with separate pools (configured as paired pools) is the best option.
1) The drawback is that if your DC is down, your SQL won't automatically fail over because your primary and witness are both down. You need to make sure you'd have a sufficient pipe for this mirroring.
2) The edges in the same pool but geo-dispersed would be OK, but without intelligent DNS LB or HLB you'd get traffic coming in/out of both pipes which might be an inefficient or expensive route. The separate pools from DC and DR are fine
too, but would require a bit of manual intervention in a failure. The answer depends on what you need to accomplish and what kind of uptime you're promising.
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer".
SWC Unified Communications

Lync 2013 Authenticating with Windows Account Every Minute

Seeing a strange issue with Lync 2013 client logging into my Windows Account about every 1-2 minutes. We are using Lync Server 2013 (on-premise) so it makes no sense that it is logging into and authenticating against Windows Account. This was causing major
issues as my Windows Account password was different than my company domain login. This was causing Lync to use the "wrong" password to login into Windows Account. I changed the passwords to match and now still seeing Lync logging in constantly
into Windows Account.
This is adding up to a LOT of data traffic. Lync should NOT be authenticating every 1-2 minutes into my Windows (Live) Account. Help please!

Hi,
Did the issue happen only for you or for multiple users?
Please exist Lync client, delete user profile on local computer with the following path, then restart Lync client:
%UserProfile%\AppData\Local\Microsoft\Office\15.0\Lync
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Lync 2013 federation with Skype error: 'Reference error id 504 (Source ID 239)

I have setup lync 2013, configured skype federation (http://www.techtroubleshoot.com/federate-lync-server-with-skype/) and also done Lync provisioning. Skype federation worked for a few days (2weeks) and then stopped. Currently I am getting the following
error 'Reference error id 504 (Source ID 239)'.
Ports are open on the firewall. I however still get the error.
KimaniBob

Verify from following:
you can telnet to your sip domain on port 5061 and 443 from external and resolve of nslookup to srv record of sipfederation is correct.
Certificate on Edge Server not expire or damaged.
This link had similar issue, you can check it.
http://terenceluk.blogspot.com/2013/04/unable-to-send-instant-messages-or-view.html
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"

Lync 2013 compatibility with Application sharing

Just upgraded to Lync 2013, and I found a compatibility issue with StarTech Stream capture software when attepting to share the application in a meeting.
The Hardware device that Stream Capture uses is:
www.startech.com/AV/Converters/Video/PCI-Express-HD-Video-Capture-Card-1080p-HDMI-DVI-VGA-Component~PEXHDCAP
The software can be downloaded: http://sgcdn.startech.com/005329/media/sets/Stream_Catcher/Capture_Software.zip
The issue I notice is when streaming just the program through Lync 2013. The mouse pointer will disappear over any Lync screen.
To duplicate the issue start a lync meeting, share the stream capture software.   Minimize the software, and wait 30 seconds so the app doesn't detect activity.   Then when you try to click on the "Stop Presenting" button within
Lync   The mouse will disappear.   Also, noticed similar behavior with other parts of Lync.
The program works as expected when sharing the full desktop.
Upon contacting Startech support they said that the issue may be related to how Lync 2013 uses "Active Video Content".   Problem didn't occur in Lync 2010.
I also tried updating to most recent video driver, disabled hardware acceleration but this did not help.
Any configuration settings I can change in Lync 2013 to get around this behavior?

Hi rainmakers,
I suggest you consult Microsoft for dedicated support.
You can click the “Give Feedback” button in the bottom-right of Lync 2013 to report the issue.
Best regards,
Eric

Lync 2013 integration with OWA

Similar Messages

Maybe you are looking for