Lync 2013 Enterprise Edition Pool Pairing

Hello
I am trying to understand Lync pool pairing, my question is:
I have two geographically dispersed locations, Site1 and Site2. If I were to do pool pairing, would I create two sites in the topology builder with a separate FE pool for each site or do you create one site with more than one FE pool (or can you only put
one FE pool per site?)
Another part of the question, if I have two sites would they both be active/active where user's would register to both locations and each site would act as a failover for the other, or would all users register to Site1 and if Site1 were to go down, they
would re-register to Site2?
Thanks,

Hi,
Agree with Michael, what’s more, when the failed pool is once more up and running, administrators can then run the Invoke-CsPoolFailBack cmdlet in order to "fail back" users of that pool. If a user is currently logged on to the backup pool then he or she
will be redirected back to their home pool after service has been restored.
You can refer to the link of “Managing Lync Server 2013 Disaster Recovery, High Availability, and Backup Service”:
http://technet.microsoft.com/en-us/library/jj721939.aspx
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Similar Messages

Rename lync server 2013 enterprise edition pool name

Im working in testing environment ,my domain controller fqdn name and my lync server 2013 enterprise pool name was same.i have to change my pool name .please give some suggestion

once a Topology has been published you can not change the FQDN.
Also you can refer shah-Khan answer, it will be helpful for you
http://social.technet.microsoft.com/Forums/lync/en-US/47d4e101-4f7b-4115-8f44-897eb5410acb/need-to-change-a-published-fqdn-lync-pool-for-lync-enterprise-2010?forum=ocsplanningdeployment
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"
Mai Ali | My blog: Technical | Twitter:
Mai Ali

How to achieve Multi-Tenant in Lync Server 2013 Enterprise Edition

Hi,
As LHPv2 is discontinued, is anyone has idea how to achieve Multi-Tenant in Lync Server 2013 Enterprise Edition?
e.g users from different tenants should not be able to communicate unless it is allowed either by federation or any other form.
J.B.Patnaik

once a Topology has been published you can not change the FQDN.
Also you can refer shah-Khan answer, it will be helpful for you
http://social.technet.microsoft.com/Forums/lync/en-US/47d4e101-4f7b-4115-8f44-897eb5410acb/need-to-change-a-published-fqdn-lync-pool-for-lync-enterprise-2010?forum=ocsplanningdeployment
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"
Mai Ali | My blog: Technical | Twitter:
Mai Ali

Lync 2013 Enterprise load balancing on the front end and edge pool

Hi,
I am setting up a Lync 2013 Enterprise deployment consisting of a Front End pool (x2 FE servers) and an Edge pool (x2 Edge servers). I'm seeing some conflicting advice regarding load balancing using hardware or DNS for the front end and the edge.
On the front end I have 2 internal DNS records 'lyncfepool1.contoso.local' each of which map to one of the IPs of the FE servers. I've used my details to populate the Detailed Design Planner excel spreadsheet and am told that I require a HLB to load
balance my front end pool. I'm aware of the need to load balance HTTPS traffic internally (which will be done by TMG) however other traffic to the front end (SIP, etc) can be balanced by DNS only, and not require a HLB?
Can someone clarify the front end requirement?
Also - looking now at the edge pool - this site again have two edge servers in a pool. We are using a total of six private IP addresses, two per edge service (2 x av.contoso.com, 2 x sip.contoso.com and 2 x webcon.contoso.com). These will be
NAT'ed by the external firewall and directed to the respective external (DMZ) IP addresses on the Edge servers on port 443. I know this isn't true roundrobin due to the intelligence of the Lync client when connecting (in that the Lync client will connect
to one of the public IPs and if it can't connect, it will know to connect to the other service IP), however I want to clarify this set up, particularly the need to direct the external public IP traffic at the DMZ Edge IP specified in the topology builder.
I've attached a basic diagram of the external/DMZ/Edge side which hopefully helps with this question
Persevere, Persevere, Per..

That is because you will always need HLB for a front-end server since it hosts the Lync webservices which use HTTP/HTTPS traffic.
The description on the calculation tool also describes this correctly:
Supports Standard and Enterprise pools (up to 12 nodes), with pure device-based load balancing or a combination of DNS load balancing and device-based load balancing (for
Lync web services)
You can use either Hardware or DNS loadbalancing for SIP traffic only, but you will always need a HLB for the webservices. Both are applicable for the Front-End so you have either
full HLB for both SIP and HTTP(S) traffic
DNS LB for SIP traffic and HLB for HTTP(S) traffic
Hope this is more clear :-)
Lync Server MVP | MCITP Lync Server 2010 | If you think my post is the answer to your question, please mark it as answer so future visitors can easily find it.

Lync 2013 standard edition server disadvantages

I have 3000 users, client is so cost effective , wanna insisting on Lync 2013 standard edition server. no enterprise voice
Feature required :- IM.presence, A/V conf, persistence chat, external access.
planned servers :- 1 Standard server in DC, 1 in DR. 1 edge server in DC and 1 in DR
1. if i make a pool of standard servers, then will it serve as HA, if yes how much time wil take for failover and what would be the impact on users?
2. If complete DC is down how mch time would take for fail-over and what is the procedure, impact on users?
3. can i collocate persistence chat role on standard edition? any limitation? how backend sizing would be for persistence chat as sql express would be there
4. can i suggest any better solution with standard servers where HA in DC .

For 3000 users Standard Edition will be fine. Use the capacity planner to size out your environment. http://www.microsoft.com/en-us/download/details.aspx?id=36828
1. It won't really serve as HA, as pool pairing is the only option it's more of a DR solution. The RTO for a pool failover is 30mins. So it could take anywhere up to 30mins. http://technet.microsoft.com/en-us/library/jj205079.aspx
2. Same as above. Here is how you failover http://technet.microsoft.com/en-us/library/jj204678.aspx
3. Yes, you can co-locate Persistent Chat on the Front End with Standard Edition. If sized correctly, there should be no performance issues.
4. The only option with Standard is Pool Pairing, so no better suggestions.
If this helped you please click "Vote As Helpful" if it answered your question please click "Mark As Answer"
Georg Thomas | Lync MVP
Blog www.lynced.com.au | Twitter
@georgathomas
Lync Edge Port Check (Beta)
This forum post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Lync 2013 Standard Edition on Cisco UCS E-Series

Hello,
We have a working Lync 2013 deployment:
- Front-End Enterprise Pool consisting of 3 FE servers
- one Edge Server
- one Back-End server
- one Mediation Server
- one IP PBX gateway, where ITSP's SIP trunks end.
Because we have geographically distributed offices, we are considering deploying of branch offices deployments.
Technet recommends to use SBA for branch offices where there are less than 1000 users. But in case of WAN outage, no conferencing will be available for branch users.
Lync 2013 Standard edition branch deployment would offer all Lync features in case of WAN outage.
In every branch, we consider deploying a Cisco ISR G2 router for terminating branch SIP trunks. This equipment have option to add Cisco UCS E-Series blade that supports CPU with hardware virtualization and supports decent amount of RAM (up to 16GB and up
to 48GB).
Have anyone experience with deploying Lync Standard Edition on this equipment - Cisco UCS E-Series blades? In every branch office there are up to 50 - 500 users that will use Lync.
Thanks,
Andrei Moraru Endava

Hi,
I don’t think you can deploy Lync server 2013 on Cisco UCS E-Series blades.
Here is a link below of “System Requirements for Servers Running Lync Server 2013” may help you:
http://technet.microsoft.com/en-us/library/gg398588.aspx
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Certificate Requirement for Lync 2013 Standard Edition

I have successfully run the setup of lync 2013 standard edition now I am stuck due to certificates required for lync 2013. when I generate a csr. it show the subjected urls for that.
hostname.domain.com
sip.domain.com
diali.domain.com
meet.domain.com
admin.domain.com
lyncdiscover.domain.com
lyncdiscoverinternal.domain.com
im.domain.com (External URL)
so if I go for 3 party CA then I need 8 certicate only for internal lync. As I also need to connected federated partner and external user so I need Edge for again I need 3 more certificates
web.domain.com
a/v.domain.com
sip.domain.com
now when I go for these certificate it quit costly and I didn't understand why such certifcates required. can anyone help me to fix such requirement.
Or, what are the necessary url to which I buy 3 party CA rest leave as it is.
I also want to deploy Edge with single adopter as we have only one network so can anyone assist me to proceed it further.
Talha Faraz Malik

To save on the cost of your third party certificates, I would deploy an internal certificate authority to sign certificates for your internal front end. For your third party certificate, you would only need the SANs for the edge and for your
reverse proxy and as Edwin said, this can be a single cert with multiple SANs.
For example, for your edge you would need:
sip.domain.com
web.domain.com
You would not need A/V as this role does not require a SAN on your certificate. On the same certificate, which you could also use on your reverse proxy, you'd likely want the following FQDNs.
lyncdiscover.domain.com
im.domain.com (your external web services FQDN)
meet.domain.com
dialin.domain.com
You may also want to consider your internal web services FQDN and include the following so third party mobile devices can connect without needing a certificate installed:
im_internal.domain.com (your internal web services FQDN)
lyncdiscoverinternal.domain.com
I'm sure that's not entirely clear yet, so feel free to ask more questions or what the purpose of each is.
When you say Edge with a single adapter, you mean a single adapter in a DMZ or internal? You definably want two NICS, both in separate DMZs, but I've managed to get the edge working with a single adapter in a DMZ before. What you don't want is
the edge in your internal network.
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
This forum post is based upon my personal experience and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Lync 2013- Standard Edition - Persistent Chat

What is the capacity of the Persistent Chat if it is collocated on Lync 2013 Standard edition front end ?
ie, number of chat rooms /usage?
In a Lync 2013 standard edition deployment if Persistent Chat is on separate server, can the SQL be offloaded to central SQL cluster enviornment or it will be held on the local server?

I haven't seen a chart that really defines the capacity, and it's difficult to measure because it's difficult to say how active the rooms will be or how much content you'll generate. That much is different from organization to organization.
There are some guidelines in general here:
https://technet.microsoft.com/en-us/library/gg615006(v=ocs.15).aspx but they don't really touch the standard model.
The pChat database can be offloaded to a central SQL cluster if you'd prefer, there are no requirements to collocate it with the local Lync databases.
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
This forum post is based upon my personal experience and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Unable to search GAL on Lync 2013 Front End Pool through Lync 2013 client

I'm in the beginning of a 2010 to 2013 migration and I'm currently testing co-existence functionality between pools. I've noticed that users cannot search the GAL from their Lync client after being moved to the 2013 pool.
When trying to access the internal URL https://fepool13.domain.com/abs/handler the user is prompted to login and after three failed attempts, receives "401 - Unauthorized: Access is denied due to invalid credentials. You do not have permission
to view this directory or page using the credentials that you supplied".
Searching withing a Lync 2010 or Lync 2013 client returns no results, but there are no errors as well as nothing in the event logs or tracing folder regarding not being able to search.
The 2010 pool has been in production for a few years now and when accessing its internal ABS URL https://fepool10.domain.com/abs/handler the user is granted access after a successful login.
In the IIS logs there are slightly more detailed 401 error codes, but I’m not sure what to make of them.
The rtcab database appears to have user information and all three front end servers appear to be syncing with active directory. I say the rtcab database appears to have user info because the AbUserEntry table is filled with User ID'd, GUID's and a
bunch of other stuff.
The authentication on 2013 front end servers “internal lync website/abs/handler” is set to 1. Negotiate, 2. Ntlm - which is the same as the 2010 front end servers.
Any ideas?

Hi,
Which step did you do among migration from Lync Server 2010 to Lync Server 2013?
Did you already move CMS from Lync Server 2010 to Lync Server 2013?
Please create a new Lync account on Lync Server 2013 pool and test the issue again.
Please check if User Replication has completed with the help of the link below:
http://technet.microsoft.com/en-us/library/jj204680.aspx
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Move cms from Lync 2010 enterprise pool to Lync 2013 enterprise pool

Hi!
We recently moved all our users from our 2010 ent pool to our new 2013 ent pool.
we have read the http://technet.microsoft.com/en-us/library/jj688013%28OCS.15%29.aspx
In step 7, it says that we should run the deployment wizard. Do we have to do this on all servers in the pool?
regards,
Uc

Hi,
yes you should run it on all front-End servers in the pool
Regards,
Charbel Hanna
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread

Strange issue with Lync 2013 Front end pool and UC Endpoints.

I have two servers in a Lync Pool.
S1 and S2. I also have an ACD server that has Trusted endpoints within Lync.
With both servers running, if a call is answered by S2 there are a bunch of weird delays in transfers. IF I shut down S2, everything works right. If I just run S2, the endpoints just ring forever and never pick up.
Additionally, with just the S1 server running, in and out calls are fine. With just the S2 server, outbound is delays and no inbound work.
It seems like there is something wrong with the S2 server, but what could it be?
Alex.

Hi,
Agree with Edwin.
Did you receive any error message from FE S2 when the issue happen?
Please double check the network status between FE S2 and ACD Server, on Lync Server Control Panel, check if FE S2 replication status normally.
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Lync 2013 enterprise voice

I have lync server and a voip gateway .
by calling 803 from lync i get access to free external line for calling outside
but for every number i have to call 803,how can i define rule and what should i do
if someone call a number with a condition like digit number lync directly call to that number with no need for your to call 803
also with lync mobile version how can i use phone contact for calling
S.Sanadi

I have lync server and a voip gateway .
by calling 803 from lync i get access to free external line for calling outside
but for every number i have to call 803,how can i define rule and what should i do
if someone call a number with a condition like digit number lync directly call to that number with no need for your to call 803
also with lync mobile version how can i use phone contact for calling
S.Sanadi

Pool pairing : lync client doesn't reconnect to backup pool

Hi
I'm currently testing lync 2013 failover via pool pairing. (IM only)
Once I stop the Frontend service however on the pool01 server, I get a notification on the lync client : "connection was lost. Reconnecting.."
However the lync client doesn't connect again (while it should reconnect with limited functionality)
Before simulating (shutting down the service)
> Get-CsBackupServiceStatus shows "final state" - "normal state"
> pool2 is configured as backup of pool1 and visa versa
> cms is hosted on pool1 server
> 2 std servers (one with pool1, other with pool2)
SRV records
1 with priority 0 and value _sipinternaltls._tcp.customer.com, which points to hostname pool1.customer.com
1 with priority 10 and value _sipinternaltls._tcp.customer.com, which points to hostname pool2.customer.com
I've upgraded the lync client to the latest build to be sure.
Anyone knows where to look? Settings seem to be correct.

I've left all defaults regarding failover.
something to add :
* the servers are installed in the domain a.prod.customer.com
* the sip addresses of all users are @customer.com
* the users can be situated in the domain a.prod.customer.com, b.prod.customer.com or c.prod.customer.com
I've just tested and when I start a Lync client, I can see both SRV records popping up, so discovery of these records seem to work correctly.
When I stop the frontend server of the pool the user is on however, I don't see any redirect in the logs.
1 Login: PASS
2 Lync-autodiscovery: FAIL (hr = 0x80004005)
Lync autodiscovery completed with hr: 0X80004005 sipint: sipext: authint: authext: wts: retry: 0
3 DNSAutoDiscovery: PASS
4 Lync-autodiscovery: FAIL (hr = 0x80004005)
Lync autodiscovery completed with hr: 0X80004005 sipint: sipext: authint: authext: wts: retry: 0
5 DNSAutoDiscovery: PASS
6 Lync-autodiscovery: FAIL (hr = 0x80004005)
Lync autodiscovery completed with hr: 0X80004005 sipint: sipext: authint: authext: wts: retry: 0
7 DNSAutoDiscovery: PASS
8 Lync-autodiscovery: FAIL (hr = 0x80004005)
Lync autodiscovery completed with hr: 0X80004005 sipint: sipext: authint: authext: wts: retry: 0
9 DNSAutoDiscovery: PASS
*edit*
When I logon the first time with a user who's primary pool is down, I can see this in the lync client log :
1 Login: FAIL (hr = 0x1)
2 server(s) returned
Server: server1.a.b.customer.com:5061, internal, discoveredadded to list of auto-discovered servers
Server: server2.a.b.customer.com:5061, internal, discoveredadded to list of auto-discovered servers
signin to server=server1.a.b.customer.com.int:5061, internal, discovered
redirectedServersList=
1.1 Lync-autodiscovery: FAIL (hr = 0x80004005)
Lync autodiscovery completed with hr: 0X80004005 sipint: sipext: authint: authext: wts: retry: 0
1.2 DNSAutoDiscovery: PASS

Lync 2013 PSTN calling not working with Sonus SBC 1000 over TLS and SRTP

Dear All,
We have recently installed Lync 2013 Enterprise Edition with a Pool of 3 FE Servers (MEDIATION COLLOCATED).
We need to implement TLS and SRTP with Sonus SBC 1000. However calls are not routing b/w SBC and Lync.
We are using wild card certificate with multiple SIP Domains as SAN(s), for internal FE servers as well SBC.
Also i would like to mentioned here that inbound and outbound calls are routing properly when we tested it over TCP.
When I move to TLS Only calls from Lync to SBC (outgoing) are working without encryption.
Here are the OCS Logger traces for incoming calls which are not landing on lync:
TL_INFO(TF_PROTOCOL) [1]2C5C.0D30::04/30/2014-14:35:18.020.00026518.020.00026518.020.00026518.020.00026518.020.00026518.020.00026518.020.00026518.020.000265d2
(S4,SipMessage.DataLoggingHelper:sipmessage.cs(774))[3491463749]
>>>>>>>>>>>>Outgoing SipMessage c=[<SipTlsConnection_AE0419>], 10.10.0.11:5067->10.10.7.50:25678
SIP/2.0 400 Bad Request
FROM: "3158222726"<sip:[email protected]>;tag=ac3201ce-4d7
TO: <sip:[email protected]:5067>;epid=D2091CF753;tag=f373543c
CSEQ: 2 INVITE
CALL-ID: [email protected]
VIA: SIP/2.0/TLS 10.10.7.50:5067;branch=z9hG4bK-UX-ac32-01ce-0b14
CONTENT-LENGTH: 0
SERVER: RTCC/5.0.0.0 MediationServer
------------EndOfOutgoing SipMessage
TL_INFO(TF_PROTOCOL) [1]2C5C.0D30::04/30/2014-14:35:18.027.00026518.027.00026518.027.00026518.027.00026518.027.00026518.027.00026518.027.00026518.027.000265d7
(S4,SipMessage.DataLoggingHelper:sipmessage.cs(774))[2666394843]
>>>>>>>>>>>>Outgoing SipMessage c=[<SipTlsConnection_370F030>], 10.10.0.11:58059->10.10.0.13:5061
SERVICE sip:2138797082;[email protected];user=phone SIP/2.0
FROM: <sip:2138797082;[email protected];user=phone>;epid=DCFDB95F4C;tag=17d286a93
TO: <sip:2138797082;[email protected];user=phone>
CSEQ: 3 SERVICE
CALL-ID: de750f98bdd94e908be5f2f975228ff7
MAX-FORWARDS: 70
VIA: SIP/2.0/TLS 10.10.0.11:58059;branch=z9hG4bKd47f1d3c
CONTACT: <sip:[email protected];gruu;opaque=srvr:MediationServer:CiGdW3iH5FiI3Qvr3PIKGQAA>
CONTENT-LENGTH: 630
SUPPORTED: gruu-10
USER-AGENT: RTCC/5.0.0.0 MediationServer
CONTENT-TYPE: application/msrtc-reporterror+xml
<?xml version="1.0" encoding="us-ascii"?>
<reportError xmlns="http://schemas.microsoft.com/2006/09/sip/error-reporting">
<error callId="[email protected]" fromUri="sip:3158222726;[email protected];user=phone" toUri="sip:2138797082;[email protected];user=phone" fromTag="ac3201ce-4d7"
toTag="" requestType="INVITE" contentType="application/sdp;call-type=audio" responseCode="400"><diagHeader>10013;reason="Gateway peer in inbound call is not found in topology document or does not depend
on this Mediation Server"</diagHeader><progressReports /></error></reportError>------------EndOfOutgoing SipMessage
Call
Send SMS
Add to Skype
You'll need Skype CreditFree via Skype

@Paul, Thanks for you response.
All ports / IP Add / DNS are defined properly. Telenet on listening port is working.
We are using Public Certificate for 3 Domains (wild card) and same is loaded and verified in SBC
I've not reviewed the OCS logs properly posted above.
What i've found or seems to me is that in a TLS Calls:
After receiving SIP Invite from SBC, mediation server started TLS Negotiation Process b/w Lync 2013 Server Pool and it fails.
SIP Domains:
contoso.com (default)
fabrikam.com
Lync FE Pool (lync.contoso.com
Here are the some more logs.
TL_INFO(TF_PROTOCOL) [0]2DF8.2930::05/01/2014-11:50:31.612.00025e49 (S4,SipMessage.DataLoggingHelper:sipmessage.cs(774))[2716989131]
<<<<<<<<<<<<Incoming SipMessage c=[<SipTlsConnection_103DFE0>], 10.10.0.11:5067<-10.10.7.50:24591
INVITE sip:[email protected]:5067 SIP/2.0
FROM: "3158222726" <sip:[email protected]>;tag=ac3201ce-ae
TO: <sip:[email protected]:5067>
CSEQ: 2 INVITE
CALL-ID: [email protected]
MAX-FORWARDS: 70
VIA: SIP/2.0/TLS 10.10.7.50:5067;branch=z9hG4bK-UX-ac32-01ce-010c
CONTACT: <sip:[email protected]:5067;transport=TLS>
CONTENT-LENGTH: 406
SUPPORTED: replaces,update,100rel
USER-AGENT: SONUS SBC1000 3.1.2v293 Sonus SBC
CONTENT-TYPE: application/sdp
ALLOW: INVITE, ACK, CANCEL, BYE, NOTIFY, OPTIONS, REFER, REGISTER, UPDATE, PRACK
P-ASSERTED-IDENTITY: "3158222726" <sip:[email protected]>
v=0
o=SBC 9 1001 IN IP4 10.10.7.50
s=VoipCall
c=IN IP4 10.10.7.50
t=0 0
m=audio 16418 RTP/AVP 8 0 101 13
c=IN IP4 10.10.7.50
a=rtpmap:8 PCMA/8000/1
a=rtpmap:0 PCMU/8000/1
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=rtpmap:13 CN/8000
a=ptime:20
a=tcap:1 RTP/SAVP
a=pcfg:1 t=1
a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:pqL6Tke8pVmXPuplJ1G3+Sr9jM97H8R7iBagWzzh|2^31|1:1
a=sendrecv
------------EndOfIncoming SipMessage
TL_INFO(TF_PROTOCOL) [1]2DF8.0E04::05/01/2014-11:50:31.665.00025e8e (S4,SipMessage.DataLoggingHelper:sipmessage.cs(774))[2716989131]
>>>>>>>>>>>>Outgoing SipMessage c=[<SipTlsConnection_103DFE0>], 10.10.0.11:5067->10.10.7.50:24591
SIP/2.0 100 Trying
FROM: "3158222726"<sip:[email protected]>;tag=ac3201ce-ae
TO: <sip:[email protected]:5067>
CSEQ: 2 INVITE
CALL-ID: [email protected]
VIA: SIP/2.0/TLS 10.10.7.50:5067;branch=z9hG4bK-UX-ac32-01ce-010c
CONTENT-LENGTH: 0
------------EndOfOutgoing SipMessage
TL_INFO(TF_CONNECTION) [1]184C.0EFC::05/01/2014-11:50:32.652.00025f32 (SIPStack,SIPAdminLog::WriteConnectionEvent:SIPAdminLog.cpp(454))[946832530] $$begin_record
Severity: information
Text: TLS negotiation started
Local-IP: 10.10.0.11:5061
Peer-IP: 10.10.0.11:52529
Connection-ID: 0x10BE00
Transport: TLS
$$end_record
TL_INFO(TF_PROTOCOL) [1]184C.0EFC::05/01/2014-11:50:32.669.00026236 (SIPStack,SIPAdminLog::ProtocolRecord::Flush:ProtocolRecord.cpp(265))[1853494582] $$begin_record
Trace-Correlation-Id: 1853494582
Instance-Id: 425D
Direction: incoming
Peer: 10.10.0.11:52529
Message-Type: request
Start-Line: NEGOTIATE sip:127.0.0.1:5061 SIP/2.0
FROM: <sip:contoso.com>;ms-fe=LYNCFE1.fabrikam.com
TO: <sip:contoso.com>
CALL-ID: aa53739ef9b34b93ba9c97d3ee56cb99
CSEQ: 1 NEGOTIATE
VIA: SIP/2.0/TLS 10.10.0.11:52529
MAX-FORWARDS: 0
CONTENT-LENGTH: 0
SUPPORTED: NewNegotiate
SUPPORTED: ECC
REQUIRE: ms-feature-info
SERVER: RTC/5.0
$$end_record
TL_INFO(TF_CONNECTION) [1]184C.0EFC::05/01/2014-11:50:32.669.0002636e (SIPStack,SIPAdminLog::WriteConnectionEvent:SIPAdminLog.cpp(383))[946832530] $$begin_record
Severity: information
Text: Connection established
Peer-IP: 10.10.0.11:52529
Peer: lync.contoso.com:52529;ms-fe=LYNCFE1.fabrikam.com
Peer-Cert: contoso.com(LYNCFE1.fabrikam.com)
Transport: M-TLS
Data: alertable="yes"
$$end_record
TL_WARN(TF_CONNECTION) [1]184C.0EFC::05/01/2014-11:50:32.669.00026387 (SIPStack,SIPAdminLog::WriteConnectionEvent:SIPAdminLog.cpp(386))[946832530] $$begin_record
Severity: warning
Text: The pool FQDN provided by the peer in its NEGOTIATE feature information does not match the pool configured in CMS for the server FQDN that it provided
Peer-IP: 10.10.0.11:52529
Peer: lync.contoso.com:52529;ms-fe=LYNCFE1.fabrikam.com
Peer-Cert: contoso.com(LYNCFE1.fabrikam.com)
Transport: M-TLS
Data: fqdn="LYNCFE1.fabrikam.com";pool="contoso.com";expected-fqdn="lync.contoso.com";info="Possible server configuration issue"
$$end_record
TL_INFO(TF_DIAG) [1]184C.0EFC::05/01/2014-11:50:32.670.000265be (SIPStack,SIPAdminLog::WriteDiagnosticEvent:SIPAdminLog.cpp(802))[1853494582] $$begin_record
Severity: information
Text: Routed a locally generated response
SIP-Start-Line: SIP/2.0 200 OK
SIP-Call-ID: aa53739ef9b34b93ba9c97d3ee56cb99
SIP-CSeq: 1 NEGOTIATE
Peer: lync.contoso.com:52529;ms-fe=LYNCFE1.fabrikam.com
$$end_record
TL_INFO(TF_PROTOCOL) [1]184C.0EFC::05/01/2014-11:50:32.670.00026615 (SIPStack,SIPAdminLog::ProtocolRecord::Flush:ProtocolRecord.cpp(265))[1853494582] $$begin_record
Trace-Correlation-Id: 1853494582
Instance-Id: 425E
Direction: outgoing;source="local"
Peer: lync.contoso.com:52529;ms-fe=LYNCFE1.fabrikam.com
Message-Type: response
Start-Line: SIP/2.0 200 OK
FROM: <sip:contoso.com>;ms-fe=LYNCFE1.fabrikam.com
To: <sip:contoso.com>;tag=C3A751556F332F7265E9BA2517C878D4
CALL-ID: aa53739ef9b34b93ba9c97d3ee56cb99
CSEQ: 1 NEGOTIATE
Via: SIP/2.0/TLS 10.10.0.11:52529;ms-received-port=52529;ms-received-cid=10BE00
Content-Length: 0
Require: ms-feature-info
Supported: NewNegotiate,OCSNative,ECC,IPv6,TlsRecordSplit
Server: RTC/5.0
$$end_record
TL_INFO(TF_PROTOCOL) [1]2DF8.1078::05/01/2014-11:50:32.671.000266da (S4,SipMessage.DataLoggingHelper:sipmessage.cs(774))[720988281]
>>>>>>>>>>>>Outgoing SipMessage c=[<SipTlsConnection_F8A09B>], 10.10.0.11:52529->10.10.0.11:5061
SERVICE sip:2138797082;[email protected];user=phone SIP/2.0
FROM: <sip:2138797082;[email protected];user=phone>;epid=16FEE4A02E;tag=22fd877f3a
TO: <sip:2138797082;[email protected];user=phone>
CSEQ: 3 SERVICE
CALL-ID: ac0f7bc4cdc94c1dbd0bb51c7c02c890
MAX-FORWARDS: 70
VIA: SIP/2.0/TLS 10.10.0.11:52529;branch=z9hG4bK67a4c9d1
CONTACT: <sip:[email protected];gruu;opaque=srvr:MediationServer:CiGdW3iH5FiI3Qvr3PIKGQAA>
CONTENT-LENGTH: 628
SUPPORTED: gruu-10
USER-AGENT: RTCC/5.0.0.0 MediationServer
CONTENT-TYPE: application/msrtc-reporterror+xml
- <reportError xmlns="http://schemas.microsoft.com/2006/09/sip/error-reporting">
- <error callId="[email protected]"
fromUri="sip:3158222726;[email protected];user=phone"
toUri="sip:2138797082;[email protected];user=phone"
fromTag="ac3201ce-ae"
toTag=""
requestType="INVITE"
contentType="application/sdp;call-type=audio"
responseCode="400">
<diagHeader>10013;reason="Gateway peer in inbound call is not found in topology document or does not depend on this Mediation Server"</diagHeader>
<progressReports/>
- </error>
------------EndOfOutgoing SipMessage

Error When Share PowerPoint Presentation. "This slide couldn't be downloaded. Error reason : name not resolved lync 2013"

Hi Partner,
I got an error as per title above when I'm sharing the powerpoint presentation within Internal.
Below are the detail of our new deployment :
- 3 SQL Servers, 3 Front End Servers, 2 Web App Servers.
- Lync 2013 Enterprise Edition
Below are the steps that i did for web app servers :
1. owapp01
- install pre-requisite
- install Microsoft Office Web Application
- install WAC Language Pack
- run command New-OfficeWebAppsFarm -InternalURL “https://LyncWAC.YourDomain.Local” -ExternalURL "https://WACsrv.domain.com" –CertificateName “My WAC Server” -EditingEnabled
2. owapp02
- installpre-requisite
- install Microsoft Office Web Application
- install WAC Language Pack
- run Command New-OfficeWebAppsMachine -MachineToJoin owapp01.yourdomain.local
3. Configure NLB follow http://blogs.technet.com/b/meamcs/archive/2013/03/27/office-web-apps-2013-multi-servers-nlb-installation-and-deployment-for-sharepoint-2013-step-by-step-guide.aspx
I can open the https://lyncwac.yourdomain.local/hosting/discovery from Web app server, Front end, Client Machines.
When I try to share the powerPoint Presentation, it shows below error on atendee
From Presenter side the error is : Some Presenting Features are unavailable due to server connectivity issues.
Below is what i got from event viewer log :
Log Name:      Lync Server
Source:        LS Data MCU
Date:          12/19/2013 4:04:26 PM
Event ID:      41033
Task Category: (1018)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      lyncfe01.domain.local
Description:
Office Web Apps Server (WAC) discovery failed, PowerPoint content is disabled.
Attempted Office Web Apps Server discovery Url: https://OfficeWebAppInt.domain.local/hosting/discovery/
Received error message: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
The number of retries: 29, since 12/19/2013 3:46:26 PM.
Cause: Office Web Apps Server may be unavailable or network connectivity may have been compromised.
Resolution:
Check HTTPS connectivity from this box to the Office Web Apps Server deployment using the discovery Url.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="LS Data MCU" />
    <EventID Qualifiers="50170">41033</EventID>
    <Level>2</Level>
    <Task>1018</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2013-12-19T09:04:26.000000000Z" />
    <EventRecordID>2013</EventRecordID>
    <Channel>Lync Server</Channel>
    <Computer> LYNCFE01.domain.local</Computer>
    <Security />
</System>
<EventData>
    <Data>https://OfficeWebAppInt.domain.local/hosting/discovery/</Data>
    <Data>Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.</Data>
    <Data>29</Data>
    <Data>12/19/2013 3:46:26 PM</Data>
</EventData>
</Event>
Thank you.
Assraf Kamaruddin Suria Business Solutions Sdn. Bhd.

Hi Lisa,
the Office Web Apps Server discovery URL defined in Lync Topology is https://officewebappint.domain.local/hosting/discovery.
the issue still persist. I hope there is any other solutions.
THank you for your feedback.
Assraf Kamaruddin Suria Business Solutions Sdn. Bhd.

Lync 2013 Enterprise Edition Pool Pairing

Similar Messages

Maybe you are looking for