Lync 2013 Front End SIP/2.0 500 Compression algorithm refused

I've deployed a brand new Lync 2013 environment hosted on Windows Server 2012 R2 that is currently in co-existence mode with my Lync 2010 environment. 
I have SCOM 2012 monitoring the environment and it recently started reporting that one or more of my front end servers
was in a critical state.  Diving into it revealed the following perf counter threshold was being tripped:
Time Sampled: 3/26/2014 2:33:30 PM
Object Name: LS:SIP - Responses
Counter Name: SIP - Local 500 Responses
Instance Name: 
First Value: 14287
Last Value: 14340
Delta Value: 53
Using OCSLOGGER.exe on the front end to capture logs, i trapped the following:
TL_INFO(TF_PROTOCOL) [11]9138.1C58::03/26/2014-19:12:39.098.0022c780 (SIPStack,SIPAdminLog::ProtocolRecord::Flush:ProtocolRecord.cpp(265))[120713120] $$begin_record
Trace-Correlation-Id: 120713120
Instance-Id: 7D80EB
Direction: outgoing;source="local"
Peer: poolA.contoso.com:63820
Message-Type: response
Start-Line: SIP/2.0 500 Compression algorithm refused
FROM: <sip:poolA.contoso.com>;ms-fe=FEserver1.contoso.com
To: <sip:poolA.contoso.com>;tag=F8B88CAB38613EB380773027C56D94AF
CALL-ID: 986f9f568c794ce39d33d7158376157b
CSEQ: 1 NEGOTIATE
Via: SIP/2.0/TLS 10.154.228.225:63820;ms-received-port=63820;ms-received-cid=C3D7C00
Content-Length: 0
ms-diagnostics: 2;reason="See response code and reason phrase";HRESULT="0xC3E93C0F(SIP_E_REACHED_CONFIGURED_LIMIT)";source="FEserver1.contoso.com"
Server: RTC/5.0
$$end_record
The only recent change made to the front end servers was making the registry change outlined in this article: 
http://support.microsoft.com/kb/2901554/en-us so i'm wondering if that has something to do with it.

The MSFT support person said to re-apply CU5 to the Director servers and reboot.  Since this is impactful to the environment and I would have to do reboots anyway, I opted to go the route of installing the more recent update so....
Last weekend I updated my Lync environment with what I think is considered CU6, the September 2014 updates for Lync 2013 Server (https://support.microsoft.com/kb/2809243) and still no luck. The front
end servers are fine; no excess SIP 500 errors occurring there but within 30 minutes of removing the SCOM override on the Director servers the alerts started firing again.
I reinstated the override in SCOM for the Directors and had my case with Premier support un-archived.  The MSFT support person said if the alerts didn't go away she was going to have to engage the Lync product group for help.  We'll see where it
goes from here.
JKuta

Similar Messages

  • Lync 2013 Front-End HA

    We are currently in a co-existence environment with both Lync 2010 and 2013 running side-by-side. 
    There are 2 FE pools with pool pairing setup for Lync 2013. We have been carrying out some testing before migrating all of our users over.
    We have an issue where when we take out one of the 2013 front end servers the client does not automatically reconnect to one of the other servers in the pool, occasionally it will but can take 10-15 mins to do this. If we simulate a similar test on the 2010
    front ends the client reconnects in seconds. 
    I am using the Lync 2013 client 

    Thanks for your replies. 
    I have setup DNS LB for the pool name (this is working correctly) and I am using a kemp load balancer for the internal web services FQDN
    I checked the EndPointConfiguration.Cache file and it just had the name of the front end server I was connected to. I deleted it and restarted my client now the EndPointConfiguration.Cache file has the name of the pool, the front end server that I am connected
    to and the IP addresses of the servers in the pool, is that correct?
    I tested the failure of the server I was connected to by removing the network adapter in VMware. 
    It took 44 seconds for my client to sign out and 1:15 after that to sign back in. My LPE took 2:18 to sign out and 1:22 after that to sign back in. Surely this cant be right? 
    During the time the failure happens and the client signs out, it is unusable. 
    I have had a look in the snooper logs but it is difficult to see the wood for the trees. 
    Thanks for your help. 

  • 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

  • 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 Server 2013 Front End Pool Mediation Service only works on one node

    Hello, I'm currently experiencing an interesting issue with a Lync 2013 Front End Pool implementation on a customer, and I don't know if this is by design or am I missing something.
    We implemented 3 Enterprise Front End Servers in a Pool with a hardware load balancer and we have them configured also as a mediation Pool.
    We have a SIP trunk to an Avaya PBX which was perfectly working before on a Lync 2010 Implementation that we migrated to these new 2013 Front End Pools.
    Now the SIP traffic is only working when configured directly to one node of the pool. If we configure it to any other node the calls fail. We also tried configuring the HLB for port 5060 for the pool and pointed the PBX to that IP but the calls also fail.
    Searching around I read something about that the PBX has to be Lync certified in order to use DNS load balancing to send SIP traffic to the mediation pool, however, I don't think DNS load balancing will work because the other nodes doesn't connect the calls
    from the PBX, only one node appears to be listening for the SIP Trunk.
    I also restarted the mediation service on one  non-working mediation server node and the event viewer on the working mediation server node showed events that it restarted the service, Not the non-working one, it's like only one server from the pool
    is doing as mediation server. 
    So even if I get a Lync Certified PBX/Media Gateway, the mediation service doesn't appear to be load balanced, or how does it work in order to do that?
    Thanks.
    Eduardo Rojas

    Just a few things about what should be happening.  Each front-end server should be listening on the port configured in topology builder for the mediation service. So if that is port 5060, verify that you see that port listening on all front-end servers
    by running a netstat -ano.  From a local workstation, also make sure you can connect to that port via a telnet IPAddress 5060.  As you say, you should be able to send any of the three mediation servers an inbound call.
    Outbound calls will round robin out of the enterprise pool.  So you shouldn't see all of the calls coming out of a single server.
    A few other items I would look into:
    - Make sure your ports are right.  Ensure that you are matching ports on the Avaya and Lync.  It's not a hard requirement but makes life easier to troubleshoot.  So if the Avaya is 5060, just make sure TCP/5060 enabled in your mediation pools
    and that your gateways/trunks are also set to TCP/5060.
    - Look outside the Lync Event Viewer and see if anything strange (.net errors) are being tossed anywhere else during startup of the mediation service.  I once had to remove the mediation server installer (Program and Features | Remove) and rebootstrap
    the server because something went sideways during an install.
    Thanks,
    Richard
    Richard Brynteson, Lync MVP | http://masteringlync.com | http://lyncvalidator.com

  • Lync 2013 Logon Failing (HTTP status code 500) No valid security token

    Hello there,
    I'm in the process of deploying Lync 2013.  I have the pool deployed and everything is at least running.  I can access the control panel and provision users.  However when I try to logon to the Lync Client I get a DNS error.  The DNS
    error appears to be misleading and is a result of the earlier auto-detection methods failing.
    However using the Lync Connectivity Analyzer I get a "No valid security token." error.  This doesnt matter if I use auto-detection or manual pointing the Connectivity Analyzer to the pool servers.
    [3/2/2015 9:34:15 AM] [ERROR] Reason: Internal server error (HTTP status code 500)
    [3/2/2015 9:34:15 AM] [ERROR] Ms-Diagnostics-Fault ErrorId: 28020, Reason: No valid security token.
    [3/2/2015 9:34:15 AM] [CRITICAL] The credentials were not authorized by the server. Please verify your login credentials and try again.
    [3/2/2015 9:34:15 AM] [DEBUG] System.Exception: Exception of type 'System.Exception' was thrown.
    at Microsoft.LyncServer.WebServices.WebTicketManager.WTExceptions(String exText)
    at Microsoft.LyncServer.WebServices.WebTicketManager.<AcquireTicketAsync>d__19.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    at Microsoft.LyncServer.WebServices.WebTicketManager.<AcquireOpaqueTicketAsync>d__14.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
    at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<AuthenticationRequired>d__2a.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<SendRequest>d__d.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
    at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<TryNextUrl>d__3.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<ParseResponse>d__16.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<TryNextUrl>d__3.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<StartDiscoveryJourney>d__0.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    at LyncConnectivityAnalyzerCore.Utilities.<RetrieveUserLocation>d__3e.MoveNext()
    Im a bit stumped where to go next.
    Thanks.

    Manually entering the server also fails and does not provide much to help "We're having trouble connecting to the server. If this continues, please contact your support team."
    I found that each time I try to logon it generates a Schannel Error on the server.  "A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection. The TLS protocol defined fatal error code is 51.
    The Windows SChannel error state is 1106."
    There seems to be a lot more information on that than the previous "Internal Error" message I was trying to deal with.
    https://social.technet.microsoft.com/Forums/office/en-US/41718327-203f-445f-8657-87b0a8545ead/lync-2013-client-signin-issue-with-lync-2013-server?forum=lyncprofile
    Actually I just found the Lync Server Front-End is stuck "starting" so that would explain why I cannot login.  However I re-issued my certificate to make sure the primary CN matched "lync.domain.tld" and it still wont start.
    https://expertslab.wordpress.com/2014/04/23/lync-server-2013-front-end-service-stuck-on-starting/
    I think my problem is the certificate.  I have been trying to use selfSSL7 to generate the certificate for testing but it does not support creating SAN entries so I have entered all the FQDNs as CN entries.
    Im going to get another method to generate the self-signed certificate for testing.

  • The Lync Server Front-End service terminated with service-specific error %%-1008124893.

    Hello, everyone
    I've installed Lync Server 2010. There was no error during installation. But when i start Lync Server Front End Server, i'm getting following error:
    The Lync Server Front-End service terminated with service-specific error %%-1008124893.
    In event viewer:
    The evaluation period for Microsoft Lync Server 2010  has expired. Please upgrade from the evaluation version to the fully licensed version of the product. Look at help for Setup.exe to learn how to upgrade from evaluation version to the licensed version.
    Cause: The evaluation period for Microsoft Lync Server 2010  has expired.
    I've upgraded Lync Server according to http://technet.microsoft.com/en-us/library/gg521005.aspx?ppud=4
    Also I've installed all Lync Server updates.
    But I still could not start Lync Front End Sever. How can I solve this problem?
    Thanks

    Hi,
    Can you try to run
    start-cswindowsservice -report c:\report.html
    and post the report so we can have more information about your problem ?
    Regards,
    Adrian TUPPER - ABC Systemes - http://thelyncexperience.blog.com/ If answer is helpful, please hit the green arrow on the left, or mark as answer Thank you

  • Lync Server Front End 2 Hardware Load Balancer IP

    I currently have the following Setup.
    I only have 1 Hardware Load Balanced IP for my Front End Pool. 
    After running the Lync Planning Tool it actually states that i need 2 Hardware Load Balanced IP, 1 for internal and 1 for external. 
    My question would be would i be able to configure for mobility and external access with just using 1 Hardware Load Balanced IP? 
    Because i seem to have problem with connecting to the front end server based on the following scenario.
    Without Reverse Proxy Mapping (port 80/443 internet to port 80/443 reverse proxy to port 80/443 lyncpool frontend) 
    Internal Access (No Issue)
    Lync Mobile 2013 App (Can Connect and chat but intermittent connection) *gets disconnected if i access video/audio
    Lync Client 2013 Externally (Cannot Connect to Server) 
    https://meet.domain.com (working)
    With Reverse Proxy Mapping (Port 80/443 internet to port 8080/4443 reverse proxy to port 8080/4443 lyncpool frontend)
    Internal Access (No Issue)
    Lync Mobile 2013 App (Cannot connect)
    Lync Client 2013 Externally (Cannot connect)
    https://meet.domain.com (Not working)
    Would i actually need to have a additional front end pool IP for external access? or can i maintain it as it is? 
    I do not understand why without the mapping it can work whereas if i do the mapping according to technet article it won't work.
    Everything is running windows server 2012 R2 and Lync 2013, Loadbalancer / Reverse Proxy is the same F5 Appliance
    Any assistance on this is greatly appreciated.

    Hi Greg,
    I have been making use of it (https://testconnectivity.microsoft.com/) to test my autodiscover and remote
    access.
    Like i mentioned it is weird that without doing port mapping from 80/443 to 8080/4443 i was able to pass
    the autodiscovery and all but once i changed to the proper steps to do port mapping it stopped working. 
    and im not using TMG but using a F5 Hardware Reverse Proxy which also happen to be my Load Balancing Appliance. 
    Is there anyone who can help give me more details if i need 2 VIP for the front end ? 

  • Lync 2013 Multi Tenant - SIP/2.0 401 Unauthorized

    New Lync 2013 Multi Tenant install. Can provision users in the Primary OU. Users in primary OU login without error.
    Users provisioned in a sub OU can not login to Lync. Provisioning process completes successfully.
    Client prompts for password. Attempts login and fails with:
    You didn't get signed in. It might be your sign-in address or logon credentials. (SIP address and UPN are identical)
    FE logging:
    SIP/2.0 401 Unauthorized
    TL_INFO(TF_PROTOCOL) [0]128C.2E1C::04/15/2014-22:28:42.421.00004ea3 (SIPStack,SIPAdminLog::ProtocolRecord::Flush:ProtocolRecord.cpp(265))[212989229] $$begin_recordTrace-Correlation-Id: 212989229
    Instance-Id:
    3A4
    Direction:
    outgoing;source="local"
    Peer:
    edge1.domain.corp:56094
    Message-Type:
    response
    Start-Line:
    SIP/2.0 401 Unauthorized
    From:
    <sip:[email protected]>;tag=57e75cd85f;epid=f7a8f50c07
    To:
    <sip:[email protected]>;tag=10A7EC7396D5F1EDCEA8D35A0C49F3CB
    Call-ID:
    8654248b0dd64d519f42617b862e75bc
    CSeq:
    2 REGISTER
    Via:
    SIP/2.0/TLS 10.200.10.210:56094;branch=z9hG4bK4B6654F6.FADCC8B2E74B96BA;branched=FALSE;ms-received-port=56094;ms-received-cid=20C00
    Via:
    SIP/2.0/TLS 172.16.232.59:60361;received=10.200.250.206;ms-received-port=43233;ms-received-cid=1E9D00
    Content-Length:
    0
    Failed to validate user credentials
    $$end_record
    TL_ERROR(TF_SECURITY) [0]128C.2E1C::04/15/2014-22:28:42.468.0000542a (SIPStack,SIPAdminLog::WriteSecurityEvent:SIPAdminLog.cpp(319))[212989229] $$begin_recordText: Failed to validate user credentials
    Result-Code:
    0x8009030c SEC_E_LOGON_DENIED
    Source:
    edge1.domain.internal:56094
    SIP-Start-Line:
    REGISTER sip:domain.com SIP/2.0
    SIP-Call-ID:
    8654248b0dd64d519f42617b862e75bc
    SIP-CSeq:
    3 REGISTER
    Data:
    gssapi-data="NTLMSSP\x00\x03\x00\x00\x00\x18\x00\x18\x00\xB4\x00\x00\x00D\x01D\x01\xCC\x00\x00\x00 \x00 \x00X\x00\x00\x000\x000\x00x\x00\x00\x00\x0C\x00\x0C\x00\xA8\x00\x00\x00\x10\x00\x10\x00\x10\x02\x00\x00U\x82\x90b\x06\x03\x80%\x00\x00\x00\x0FQ\[email protected]\x1E\x1F\xD2\xF9w\x0C!\xF8Y\x84\x84\x06PM\x00i\x00c\x00r\x00o\x00s\x00o\x00f\x00t\x00A\x00c\x00c\x00o\x00u\x00n\x00t\x00r\x00i\x00c\x00h\x00.\x00l\x00i\x00b\x00e\x00r\x00t\x00y\[email protected]\x00h\x00o\x00t\x00m\x00a\x00i\x00l\x00.\x00c\x00o\x00m\x00L\x00A\x00P\x00T\x00O\x00P\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00+\xD8\x1CE\xFB\\x9E7\xACbc\x17e\xDE\xAC\xFD\x01\x01\x00\x00\x00\x00\x00\x00R\n\x0E\xFAX\xCF\x01\xF2h\xA4\xBE\x8B\xC3w=\x00\x00\x00\x00\x02\x00\x06\x00P\x00P\x00C\x00\x01\x00\x1A\x00P\x00P\x00C\x001\x00L\x00Y\x00N\x00C\x00F\x00E\x000\x000\x001\x00\x04\x00\x10\x00p\x00p\x00c\x00.\x00c\x00o\x00r\x00p\x00\x03\x00,\x00P\x00P\x00C\x001\x00L\x00Y\x00N\x00C\x00F\x00E\x000\x000\x001\x00.\x00p\x00p\x00"
    $$end_record

    Hi,
    Please double check the port between FE server and Edge server.
    Please also check if you add the SAN of sub domain in the Edge external certificate with the help of the link below:
    http://technet.microsoft.com/en-us/library/gg398409.aspx
    Best Regards,
    Eason Huang
    Eason Huang
    TechNet Community Support

  • Lync 2013 Error 31055 ,31059 LS Call Park Service, The database being used by Group Pickup is not the appropriate version and There was a problem communicating with the Group Pickup backend database.

    Hello
    I have Lync 2013 and 2010  , still i didn't finish my migration completely from 2010 to 2013 .this  is  coexistence environment that contains both Lync Server 2010 and Lync Server 2013 .
    There was no error's in my lync 2013 front end and back end server's and every thing was fine, yesterday I installed windows updated AND CU for my lync 2013  front end and backend server's .
    later on after restarting both the front end and the back end server's i start having hundred's of  these error's related to "LS Call Park Service".
    so any advice for these issue ? and what is the effect for these error .
    below is the error I got .
    The database being used by Group Pickup is not the appropriate version.
    The database is not the correct version:
    Connection: Data Source=HQ-LYNC2013-BE.aaaaaaaaaaaaaaaaaaaaaaaaaaa\rtc;Initial Catalog=cpsdyn;Integrated Security=True
    Expected... SchemaVersion: 1, SprocVersion: 1, UpgradeVersion: 2
    Actual...   SchemaVersion: 0, SprocVersion: 0, UpgradeVersion: 0
    Cause: The database has not been upgraded.
    Resolution:
    Upgrade the database to CU1.
    ==============================================================
    There was a problem communicating with the Group Pickup backend database.
    There were problems accessing SQL server:
    Connection: Data Source=HQ-LYNC2013-BE.aaaaaaaaaaaaaaaaaaaaaaaaaa\rtc;Initial Catalog=cpsdyn;Integrated Security=True
    Message: The EXECUTE permission was denied on the object 'DbpGetVersionSchema', database 'cpsdyn', schema 'dbo'.
    Error code: -2146232060
    Error number: 229
    Cause: This may be caused by connectivity issues with the backend database.
    Resolution:
    Check if SQL backend is running and accepts connections from Group Pickup.
    =============================================================================
    Kind Regards
    MK

    Hello
    thanks Holger for u r replay .
    due to the Microsoft article about the cu :
    I run only :
    Install-CsDatabase -ConfiguredDatabases -SqlServerFqdn FEBE.FQDN -Verbose
    Note In a coexistence environment that contains both Lync Server 2010 and Lync Server 2013 and in which the Central Management Service is located on a Lync Server 2010 pool, do not run the
    Install-CsDatabase -CentralManagementDatabase command. If you later move the Central Management Service to a Lync Server 2013 pool, you have to run the
    Install-CsDatabase -CentralManagementDatabase command to apply the changes.
    here is what I get on my power shell after i run the command : "WARNING: Warning: Failed to execute batch --"
    PS C:\Users\MK> Install-CsDatabase -ConfiguredDatabases -SqlServerFqdn HQ-LYNC2013-BE.MyDomain -Verbose
    VERBOSE: Creating new log file
    "C:\Users\MK\AppData\Local\Temp\2\Install-CsDatabase-82d6613c-f2e3-47e6-8fc4-8f75d2efe6e4.xml".
    VERBOSE: Install databases required by Lync Server role(s).
    ****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.BlobStore'****
    Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\rtc. using windows authentication...
    Sql version: Major: 11, Minor: 0, Build 5058.
    Sql version is acceptable.
    Checking state for database rtcxds.
    ****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.AbsDatabase'****
    Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\rtc. using windows authentication...
    Sql version: Major: 11, Minor: 0, Build 5058.
    Sql version is acceptable.
    Checking state for database rtcab.
    ****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.RgsConfigDatabase'****
    Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\rtc. using windows authentication...
    Sql version: Major: 11, Minor: 0, Build 5058.
    Sql version is acceptable.
    Checking state for database rgsconfig.
    ****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.RgsDynDatabase'****
    Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\rtc. using windows authentication...
    Sql version: Major: 11, Minor: 0, Build 5058.
    Sql version is acceptable.
    Checking state for database rgsdyn.
    ****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.CpsDynDatabase'****
    Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\rtc. using windows authentication...
    Sql version: Major: 11, Minor: 0, Build 5058.
    Sql version is acceptable.
    Checking state for database cpsdyn.
    ****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.ArchivingDatabase'****
    Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\arc. using windows authentication...
    Sql version: Major: 11, Minor: 0, Build 5058.
    Sql version is acceptable.
    Checking state for database LcsLog.
    ****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.MonitoringDatabase'****
    Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\mon. using windows authentication...
    Sql version: Major: 11, Minor: 0, Build 5058.
    Sql version is acceptable.
    Checking state for database LcsCDR.
    VERBOSE: Assigning "BackendStore:BlobStore:LogPath" to F:\CsData
    VERBOSE: Assigning "BackendStore:RtcSharedDatabase:LogPath" to F:\CsData
    VERBOSE: Assigning "ArchivingStore:ArchivingDatabase:LogPath" to F:\CsData
    VERBOSE: Assigning "MonitoringStore:MonitoringDatabase:LogPath" to F:\CsData
    VERBOSE: Assigning "MonitoringStore:QoEMetricsDatabase:LogPath" to F:\CsData
    VERBOSE: Assigning "ArchivingStore:ArchivingDatabase:DbPath" to F:\CsData
    VERBOSE: Assigning "MonitoringStore:MonitoringDatabase:DbPath" to F:\CsData
    VERBOSE: Assigning "MonitoringStore:QoEMetricsDatabase:DbPath" to F:\CsData
    VERBOSE: Assigning "ABSStore:AbsDatabase:LogPath" to F:\CsData
    VERBOSE: Assigning "ApplicationStore:RgsConfigDatabase:LogPath" to F:\CsData
    VERBOSE: Assigning "ApplicationStore:RgsDynDatabase:LogPath" to F:\CsData
    VERBOSE: Assigning "ApplicationStore:CpsDynDatabase:LogPath" to F:\CsData
    VERBOSE: Assigning "BackendStore:BlobStore:DbPath" to F:\CsData
    VERBOSE: Assigning "BackendStore:RtcSharedDatabase:DbPath" to F:\CsData
    VERBOSE: Assigning "ABSStore:AbsDatabase:DbPath" to F:\CsData
    VERBOSE: Assigning "ApplicationStore:RgsConfigDatabase:DbPath" to F:\CsData
    VERBOSE: Assigning "ApplicationStore:RgsDynDatabase:DbPath" to F:\CsData
    VERBOSE: Assigning "ApplicationStore:CpsDynDatabase:DbPath" to F:\CsData
    VERBOSE: Installing "BackendStore" on HQ-LYNC2013-BE.MyDomain\rtc, collocated: False
    ****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.BlobStore'****
    Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\rtc. using windows authentication...
    Sql version: Major: 11, Minor: 0, Build 5058.
    Sql version is acceptable.
    Checking state for database rtcxds.
    Checking state for database rtcxds.
    State of database rtcxds is DbState_RequiresMinorUpgrade.
    Database rtcxds set to mode Restricted.
    Dropping all procedures, functions and views from database rtcxds.
    Executing RtcDb.sql...
    Adding master role...
    Setting owner for database rtcxds to sa.
    Creating login MyDomain\RTCHSUniversalServices.
    Creating user MyDomain\RTCHSUniversalServices.
    Creating Schema MyDomain\RTCHSUniversalServices.
    Creating login MyDomain\RTCUniversalReadOnlyAdmins.
    Creating user MyDomain\RTCUniversalReadOnlyAdmins.
    Creating Schema MyDomain\RTCUniversalReadOnlyAdmins.
    Creating login MyDomain\RTCUniversalServerAdmins.
    Creating user MyDomain\RTCUniversalServerAdmins.
    Creating Schema MyDomain\RTCUniversalServerAdmins.
    Adding account MyDomain\RTCHSUniversalServices to role ConsumerRole.
    Adding account MyDomain\RTCUniversalReadOnlyAdmins to role ConsumerRole.
    Adding account MyDomain\RTCHSUniversalServices to role ReplicatorRole.
    Adding account MyDomain\RTCHSUniversalServices to role PublisherRole.
    Adding account MyDomain\RTCUniversalServerAdmins to role PublisherRole.
    Setting database version: Schema Version 15, Sproc Version 13, Update Version 2.
    Setting the database rtcxds to multi user mode.
    Database rtcxds is set to multi user mode.
    ****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.RtcSharedDatabase'****
    Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\rtc. using windows authentication...
    Sql version: Major: 11, Minor: 0, Build 5058.
    Sql version is acceptable.
    Checking state for database rtcshared.
    Database created by script "RtcSharedDatabase" already exists and is current.
    VERBOSE: Successfully installed the database. For details, see the following log:
    "C:\Users\MK\AppData\Local\Temp\2\Create-BackendStore-HQ-LYNC2013-BE.MyDomain_rtc-[2014_11_13][14_35_01].log"
    VERBOSE: Installing "ABSStore" on HQ-LYNC2013-BE.MyDomain\rtc, collocated: False
    ****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.AbsDatabase'****
    Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\rtc. using windows authentication...
    Sql version: Major: 11, Minor: 0, Build 5058.
    Sql version is acceptable.
    Checking state for database rtcab.
    Checking state for database rtcab.
    State of database rtcab is DbState_RequiresMinorUpgrade.
    Database rtcab set to mode Restricted.
    Dropping all procedures, functions and views from database rtcab.
    Executing RtcAbTypes.sql...
    WARNING: Warning: Failed to execute batch --
    -- Copyright (c) Microsoft Corporation. All rights reserved.
    exec sp_addrole N'ServerRole'.
    Executing RtcAbDb.sql...
    Setting owner for database rtcab to sa.
    Creating login MyDomain\RTCComponentUniversalServices.
    Creating user MyDomain\RTCComponentUniversalServices.
    Creating Schema MyDomain\RTCComponentUniversalServices.
    Adding account MyDomain\RTCComponentUniversalServices to role ServerRole.
    Setting database version: Schema Version 62, Sproc Version 42, Update Version 3.
    Setting the database rtcab to multi user mode.
    Database rtcab is set to multi user mode.
    VERBOSE: Successfully installed the database. For details, see the following log:
    "C:\Users\MK\AppData\Local\Temp\2\Create-ABSStore-HQ-LYNC2013-BE.MyDomain_rtc-[2014_11_13][14_35_20].log"
    VERBOSE: Installing "ApplicationStore" on HQ-LYNC2013-BE.MyDomain\rtc, collocated: False
    ****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.RgsConfigDatabase'****
    Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\rtc. using windows authentication...
    Sql version: Major: 11, Minor: 0, Build 5058.
    Sql version is acceptable.
    Checking state for database rgsconfig.
    Database created by script "RgsConfigDatabase" already exists and is current.
    ****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.RgsDynDatabase'****
    Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\rtc. using windows authentication...
    Sql version: Major: 11, Minor: 0, Build 5058.
    Sql version is acceptable.
    Checking state for database rgsdyn.
    Database created by script "RgsDynDatabase" already exists and is current.
    ****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.CpsDynDatabase'****
    Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\rtc. using windows authentication...
    Sql version: Major: 11, Minor: 0, Build 5058.
    Sql version is acceptable.
    Checking state for database cpsdyn.
    Checking state for database cpsdyn.
    State of database cpsdyn is DbState_RequiresMinorUpgrade.
    Database cpsdyn set to mode Restricted.
    Dropping all procedures, functions and views from database cpsdyn.
    Executing CpsDyn.sql...
    Setting owner for database cpsdyn to sa.
    Creating login MyDomain\RTCComponentUniversalServices.
    Creating user MyDomain\RTCComponentUniversalServices.
    Creating Schema MyDomain\RTCComponentUniversalServices.
    Creating login MyDomain\RTCUniversalReadOnlyAdmins.
    Creating user MyDomain\RTCUniversalReadOnlyAdmins.
    Creating Schema MyDomain\RTCUniversalReadOnlyAdmins.
    Creating login MyDomain\RTCUniversalServerAdmins.
    Creating user MyDomain\RTCUniversalServerAdmins.
    Creating Schema MyDomain\RTCUniversalServerAdmins.
    Adding account MyDomain\RTCComponentUniversalServices to role ReadWriteRole.
    Adding account MyDomain\RTCUniversalServerAdmins to role ReadWriteRole.
    Adding account MyDomain\RTCUniversalReadOnlyAdmins to role ReadOnlyRole.
    Setting database version: Schema Version 1, Sproc Version 1, Update Version 2.
    Setting the database cpsdyn to multi user mode.
    Database cpsdyn is set to multi user mode.
    VERBOSE: Successfully installed the database. For details, see the following log:
    "C:\Users\MK\AppData\Local\Temp\2\Create-ApplicationStore-HQ-LYNC2013-BE.MyDomain_rtc-[2014_11_13][14_35_37].log"
    VERBOSE: Installing "ArchivingStore" on HQ-LYNC2013-BE.MyDomain\arc, collocated: False
    ****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.ArchivingDatabase'****
    Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\arc. using windows authentication...
    Sql version: Major: 11, Minor: 0, Build 5058.
    Sql version is acceptable.
    Checking state for database LcsLog.
    Database created by script "ArchivingDatabase" already exists and is current.
    VERBOSE: Successfully installed the database. For details, see the following log:
    "C:\Users\MK\AppData\Local\Temp\2\Create-ArchivingStore-HQ-LYNC2013-BE.MyDomain_arc-[2014_11_13][14_35_51].log"
    VERBOSE: Installing "MonitoringStore" on HQ-LYNC2013-BE.MyDomain\mon, collocated: False
    ****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.MonitoringDatabase'****
    Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\mon. using windows authentication...
    Sql version: Major: 11, Minor: 0, Build 5058.
    Sql version is acceptable.
    Checking state for database LcsCDR.
    Checking state for database LcsCDR.
    Checking state for database LcsCDR.
    State of database LcsCDR is DbState_RequiresMinorUpgrade.
    WARNING: The database LcsCDR being updated has data file path at
    \\HQ-LYNC2013-BE.MyDomain\C$\CsData\MonitoringStore\mon\DbPath\LcsCDR.mdf and supplied data file path is
    \\HQ-LYNC2013-BE.MyDomain\F$\CsData\MonitoringStore\mon\DbPath\LcsCDR.mdf. Supplied path will be ignored.
    WARNING: The database LcsCDR being updated has log file path at
    \\HQ-LYNC2013-BE.MyDomain\C$\CsData\MonitoringStore\mon\LogPath\LcsCDR.ldf and supplied data file path is
    \\HQ-LYNC2013-BE.MyDomain\F$\CsData\MonitoringStore\mon\LogPath\LcsCDR.ldf. Supplied path will be ignored.
    Database LcsCDR set to mode Restricted.
    Dropping all procedures, functions and views from database LcsCDR.
    Executing CdrDb.sql...
    Setting owner for database LcsCDR to sa.
    Creating login MyDomain\CSAdministrator.
    Creating user MyDomain\CSAdministrator.
    Creating Schema MyDomain\CSAdministrator.
    Creating login MyDomain\RTCComponentUniversalServices.
    Creating user MyDomain\RTCComponentUniversalServices.
    Creating Schema MyDomain\RTCComponentUniversalServices.
    Adding account MyDomain\RTCComponentUniversalServices to role ServerRole.
    Adding account MyDomain\RTCComponentUniversalServices to role ReportsReadOnlyRole.
    Adding account MyDomain\CSAdministrator to role ReportsReadOnlyRole.
    Setting database version: Schema Version 39, Sproc Version 82, Update Version 2.
    Setting the database LcsCDR to multi user mode.
    Database LcsCDR is set to multi user mode.
    SQL Server Agent is running and its start mode was detected as Auto.
    Executing CdrJobs.sql...
    ****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.QoEMetricsDatabase'****
    Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\mon. using windows authentication...
    Sql version: Major: 11, Minor: 0, Build 5058.
    Sql version is acceptable.
    Checking state for database QoEMetrics.
    Checking state for database QoEMetrics.
    Checking state for database QoEMetrics.
    State of database QoEMetrics is DbState_RequiresMinorUpgrade.
    WARNING: The database QoEMetrics being updated has data file path at
    \\HQ-LYNC2013-BE.MyDomain\C$\CsData\MonitoringStore\mon\DbPath\QoEMetrics.mdf and supplied data file path is
    \\HQ-LYNC2013-BE.MyDomain\F$\CsData\MonitoringStore\mon\DbPath\QoEMetrics.mdf. Supplied path will be ignored.
    WARNING: The database QoEMetrics being updated has log file path at
    \\HQ-LYNC2013-BE.MyDomain\C$\CsData\MonitoringStore\mon\LogPath\QoEMetrics.ldf and supplied data file path is
    \\HQ-LYNC2013-BE.MyDomain\F$\CsData\MonitoringStore\mon\LogPath\QoEMetrics.ldf. Supplied path will be ignored.
    Database QoEMetrics set to mode Restricted.
    Dropping all procedures, functions and views from database QoEMetrics.
    Executing QoEDb.sql...
    Setting owner for database QoEMetrics to sa.
    Creating login MyDomain\RTCComponentUniversalServices.
    Creating user MyDomain\RTCComponentUniversalServices.
    Creating Schema MyDomain\RTCComponentUniversalServices.
    Adding account MyDomain\RTCComponentUniversalServices to role ServerRole.
    Setting database version: Schema Version 62, Sproc Version 90, Update Version 1.
    Setting the database QoEMetrics to multi user mode.
    Database QoEMetrics is set to multi user mode.
    SQL Server Agent is running and its start mode was detected as Auto.
    Executing QoEJobs.sql...
    VERBOSE: Successfully installed the database. For details, see the following log:
    "C:\Users\MK\AppData\Local\Temp\2\Create-MonitoringStore-HQ-LYNC2013-BE.MyDomain_mon-[2014_11_13][14_35_51].log"
    VERBOSE: No changes were made to the Central Management Store.
    VERBOSE: Creating new log file
    "C:\Users\MK\AppData\Local\Temp\2\Install-CsDatabase-82d6613c-f2e3-47e6-8fc4-8f75d2efe6e4.html".
    WARNING: "Install-CsDatabase" processing has completed with warnings. "5" warnings were recorded during this run.
    WARNING: Detailed results can be found at
    "C:\Users\MK\AppData\Local\Temp\2\Install-CsDatabase-82d6613c-f2e3-47e6-8fc4-8f75d2efe6e4.html".
    PS C:\Users\MK>
    I hope some one can confirm no issue with what I did ??
    Kind Regards
    MK

  • Best path to Lync 2013

    I've been running Lync 2010 Standard with a single edge server and a single front-end server. Recently I lost two of the four drives in my edge server simultaneously, and - of course - there is no backup. I've already got a virtual server started for Lync
    2013 front-end. My current question is whether I need to rebuild the Lync 2010 Edge server, or just build a Lync 2013 edge server instead and not worry about the 2010 edge server loss. I wasn't sure if the 2010 edge server was required for the migration to
    2013.
    It seems that I should be able to get my topology built on the Lync 2013 front-end server, then use that topology to import into the 2013 edge server, and, finally, move my users to the 2013 front-end environment. Any guidance would be appreciated before
    I begin the work. Thank you.
    David

    If it was just the edge, then don't worry about the loss and don't rebuild it. Deploy a new 2013 edge and move forward. If you see the 2010 edge in the topology builder just remove it from there and there's nothing left to do if everything is associated
    with the 2013 replacement.
    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.

  • Issues with Hosted Exchange, UM and Lync 2013.

    Hello everyone!
    I am trying to deploy UM with Office 365 Hosted Exchange. We are using one Lync 2013 Standard Edition FE and have deployed one edge server. We have set up our firewall to host the Reverse Proxy.
    We do not use wildcard certs. External DNS resolves the _sipfederation and sip._tls SRV records to the external face of the edge server. The edge server functions as it should for remote users and mobility.
    I have tried to follow these instructions to the letter three times over to no avail.
    http://y0av.me/2014/01/07/lyncum365/
    Neither Snooper or Event Viewer show any particular issue, though when I try to dial out to voice mail I will get one to two rings and then 5 seconds of silence a fast busy, and finally "Call Unsuccessful".
    When checking the firewall logs I notice a seemingly random 10.x.x.x address being sent to the firewall by the external leg of the edge server. Wireshark captures it as STUN packets on port 3478 being sent to port 3478. These are being dropped by our firewall.
    I believe them to be RTP packets but I do not know if this is normal behavior. Has anyone any ideas?

    My mistake. Here is the snooper result.
    TL_INFO(TF_PROTOCOL) [edge\edge]0C4C.05E4::06/18/2014-15:43:34.153.0000000C (SIPStack,SIPAdminLog::ProtocolRecord::Flush:ProtocolRecord.cpp(265)) [3770767507]
    Trace-Correlation-Id: 3770767507
    Instance-Id: 2E5A
    Direction: incoming;source="external edge";destination="internal edge"
    Peer: exap.um.outlook.com:5061
    Message-Type: response
    Start-Line: SIP/2.0 488 Compression algorithm refused
    From: sip:sip.domain.net;tag=08FB9ED133BA396696FE6546EA6F3031
    To: sip:exap.um.outlook.com;tag=B8FFE4E9267ED6ECB78ADCC60126B53F
    Call-ID: 66602CE1F9980BFA94AD
    CSeq: 1 NEGOTIATE
    Via: SIP/2.0/TLS 10.11.11.23:50752;branch=z9hG4bK2132316E.5B3AF52DE2753A36;branched=FALSE;received=207.46.5.9;ms-received-port=50752;ms-received-cid=60172700
    Content-Length: 0
    Server: RTC/5.0
    TL_INFO(TF_NETWORK) [edge\edge]0C4C.05E4: :06/18/2014-15:43:34.153.0000000D (SIPStack,NegotiateLogic::SetCompressionType:NegotiateLogic.cpp(2701)) [559249495]( 00000079B1274FB8 ) Compression type is now CompOff
    TL_INFO(TF_NETWORK) [edge\edge]0C4C.05E4: :06/18/2014-15:43:34.153.0000000E (SIPStack,NegotiateLogic::ProcessCompressionResponse:NegotiateLogic.cpp(2217)) [559249495]( 00000079B1274FB8 ) Peer refused [488] our request for compression
    TL_INFO(TF_NETWORK) [edge\edge]0C4C.05E4: :06/18/2014-15:43:34.153.0000000F (SIPStack,NegotiateLogic::AdvanceOutboundNegotiation:NegotiateLogic.cpp(910)) [559249495]( 00000079B1274FB8 ) Outbound negotiation sequence is complete
    $$end_record
    And finally..
    TL_INFO(TF_PROTOCOL) [edge\edge0C4C.05E4::06/18/2014-15:43:49.379.0000002E (SIPStack,SIPAdminLog::ProtocolRecord::Flush:ProtocolRecord.cpp(265)) [962697980]
    Trace-Correlation-Id: 962697980
    Instance-Id: 2E61
    Direction: incoming;source="internal edge";destination="external edge"
    Peer: fe1.domain.net:61254
    Message-Type: request
    Start-Line: BYE sip:uminternal.um.prod.outlook.com:5066;transport=Tls;ms-fe=CO1PR02MB111.namprd02.prod.outlook.com SIP/2.0
    From: <sip:[email protected]>;tag=b736386270;epid=9bcee72318
    To: <sip:[email protected];opaque=app:voicemail>;tag=eced411395;epid=07C3F2A933
    Call-ID: 4266a095bdef8280d67c7e7df58446fc
    CSeq: 2 BYE
    Via: SIP/2.0/TLS 10.10.10.25:61254;branch=z9hG4bKC848F11A.A88BCA6858661A50;branched=FALSE
    Via: SIP/2.0/TLS 10.10.10.125:49156;ms-received-port=49156;ms-received-cid=401200
    Route: <sip:edge.domain.net:5061;transport=tls;opaque=state:Si;lr>
    Route: <sip:exap.um.outlook.com:5061;transport=tls;epid=07C3F2A933;lr;ms-key-info=AAEAARc45bIQE6UJAYvPAR8eV4QTvCH3EE2Kxtie7I2PMCSj-2aArKHP8dStYlJe-9jphIkz_mDEkCD_v8hY-mghQEHD6-F12E7E14YG-TJ2gEcQE0Bx2r_rDB3LrzRZzgQ0WVvxreLPWGI80elWF-xfbc_X3JE8mOR2OB9KQM8-e9WOjfq2kj6CnDGeL0yzgz4OB8zm-ao03Yo4gMZ-BpwaxC3BNuvvVDJo9wqrYftq_Z3MIVewWrqcDt5Td4vxCsMiXdwEqtEIRKVvQoqboleBJAyQl-C3qGgfEoSkUnApFuTSnQYRa4kbZ1iPaACpdKT-VTQGjc9HXfps48YJCsIXW0Ab_NSM2uvhUyw900men1ukXSmoZoWZbwqe5siuWVUcFoQl1h1Jcy4lCyZUfDZoqPzDioLqTk9iUmS8fa-PAJjsq72yGjVB_y1aJSxtHVsw7MiDqOGOPqT3dmF-sINkeyuokCy8UCf_cQHmEHwVzZLUJqaVccr3QNCLsBzhcWSypnC60ZZphOKuwl6RvUXWICPf0ubLTL2ppC3tWEgFdUUWOPVd84uGlMcqRLKGb1qrmpj8Nu6Lte7t5n2pMEBCfgAe79t4GO0C5KScdKT_XBM1iIBRXdNkPKHfSgC-wPQgRikdw7vRD-hOWlN5Lay7-zkQ4Ag6rauszFTAwbft99OieAOxKIsgYcxXxcG6;ms-route-sig=fiEMuzbN4_PyEz_I5gG3g8FtqNAonwgZCoRnOq-ByfYEtywTZp-Hk_eAAA>
    Max-Forwards: 69
    Content-Length: 0
    ms-client-diagnostics: 22; reason="Call failed to establish due to a media connectivity failure when both endpoints are internal";CallerMediaDebug="audio:ICEWarn=0x40003a0,LocalSite=10.10.10.125:6735,LocalMR=10.11.11.23:51430,RemoteSite=10.27.46.15:5286,RemoteMR=207.46.5.80:54106,PortRange=1025:65000,LocalMRTCPPort=51430,RemoteMRTCPPort=54106,LocalLocation=2,RemoteLocation=2,FederationType=0"
    $$end_record

  • 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 Edge server compatibility with Lyn 2010 Front end Pool

    Hi All,
    Technet article (http://technet.microsoft.com/en-us/library/jj688121.aspx) says the following:
    If your legacy Lync Server 2010 Edge Server is configured to use the same FQDN for the Access Edge service, Web Conferencing Edge service, and the A/V Edge service, the procedures in this section are not supported. If the
    legacy Edge services are configured to use the same FQDN, you must first migrate all your users from Lync Server 2010 to Lync Server 2013, then decommission the Lync Server 2010 Edge Server before enabling federation on the Lync Server 2013 Edge Server.
    Can you tell me why it is you have to change the External Lync Web services URL during a migration to Lync 2013 from Lync 2010. What purpose does this serve?
    Also can you clarify this and explain why this is required, why would you have to migrate all of your users, would a Lync 2013 Edge not talk to a Lync 2010 front-end?
    Any help would be much appreciated. MANY THANKS.

    Thank you very much for all your inputs.
    We still have few questions:
    Questions:
    Can you tell me if Lync 2010 users will be able to login using mobility if we repoint the reverse proxy (TMG) web services publishing rule to the Lync 2013 server? Remember both systems Lync 2010 and 2013 are using the same web
    services URL so they will both end up at the Lync 2013 server. Alternatively if not we will migrate all users to 2013, this is not a problem
    In addition to this I cannot find anything that states how Exchange UM will operate when you are running from a backup pool and the exchange UM contacts are not available because they are homed on the server that is down. This
    configuration is 2 x standard edition servers pool paired. How can we make sure Exchange voice mail works during a pool failover?
    Call Park is not clear to me I read the following:
    Lync Server 2013 provides new disaster recovery mechanisms in the form of failover and failback processes. These failover and failback processes support recovery of Call Park functionality by allowing
    users who are homed in the primary pool to leverage the Call Park application of the backup pool when an outage occurs in the primary pool. Support for disaster recovery of the Call Park application is enabled as part of the configuration and deployment of
    paired Front End pools.
     Is this saying we need to deploy Call Park in the DR pool and use a different range of orbit numbers, or can we use the same range in the DR pool?
    Further, I can see that Common Area Phones will be fine as they will log into the DR pool automatically. Response Groups need to be exported and imported to the DR pool. Incidentally these did not migrate well at all and have
    caused us a big headache!
    Any inputs will be greatly appreciated. Thanks again for all of your time.

  • LYNC 2010 Enterprise Pool Front End Servers

    Can we mix Windows 2008 R2 Enterprise Edition and Standard Edition virtual servers in same LYNC 2010 Front End Pool?
    Tek-Nerd

    Agree with Lisa,Lync Server virtualization supports a mix of operating systems. For example, a host server running Windows Server 2012 R2 that runs virtual servers that run Windows Server 2008 R2 is supported.
    You cannot mix different types of servers within the same pool. All servers within the same pool must either be physical or virtual
    Also you can refer below link
    http://technet.microsoft.com/en-us/library/gg399035.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"

Maybe you are looking for

  • IPod won't restore...error message saying "Can't mount iPod"...

    I have determined that I need to restore my iPod based on my problem (I manually update playlists and cannot add a playlist because I get an error message saying "The disk cannot be read from or written to.") So I open iPod updater 11-17-2005 to try

  • XP Pro, Service Packs 1,2,3, and sound card problems

    I recently purchased a white macbook. So far it has been a very good experience, however I am having some trouble with XP Pro and its service packs. I've installed XP and it works fine for the most part however the sound card does not work. I tried t

  • Reservation of iPhone 5

    Why hasn't iphone 5 reservation started? It says that we can reserve iphone 5 between 7am to 3pm. It is 7:22an now!!!! The reservation has not opened yet!!!!!!!!! I have been waiting it for so long.......................

  • Unable to customize the af:REGION tag

    Hi I am using <af:region> tag for search contents, its working fine but its overlapping on header portion I unable to customize it (unable to change the position of the component) please if you allready use the region tag advice me how to use it. tha

  • How to trace AAE mappings (UDF)

    Hi, i have a PI 7.1 and some scenarios use the advanced adapter engine (AAE). However, i have some UDF in my mappings which seem to work different when in test mode (test tab in Integration Builder) and during runtime. So i need to write information