Lync Federation Error Id 504 Source Id 239
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeOnline20132010Interop ProgramsLibraryForumsGalleryLync Blogs Ask a question Quick access Forums home Browse
Lync Error Id 403 Source Id 239
forums users FAQ Search related threads Remove From lync error id 503 source id 239 My Forums Answered by: Error while sending message in federation /error ID
Skype For Business
504 (source ID 239)/ Outbound TLS negotiation failed Lync Server , Lync > Lync 2010 and OCS - Planning and Deployment Question 0 Sign in to vote Hi all! I have such question now: I hve such Lync Server test zone: I set up federation between srgdomain1 and srgdomain2 But message can't be sent from one domain to anothererror ID 504 (source ID 239) I have the next situation WiredShark on Edge servers show, that packets leave one server and get to another Maybe I have problem with setting up ports? Firewall is off SRV records are created and reachable from nslookup Lync Server Logging Tool shows TL_ERROR(TF_NETWORK) [0]0600.0984::08/21/2012-14:57:24.615.00000055 (SIPStack,`CTLSLogic::ProcessOutboundTlsFailure'::`1'::catch$0:tlslogic.cpp(1437))( 0000000003295A68 ) Exit$CryptFailure - AdvanceOutboundTls() failed. Returned HRESULT=80096004 TL_ERROR(TF_NETWORK) [0]0600.0984::08/21/2012-14:57:24.615.00000056 (SIPStack,`CTLSLogic::AdvanceOutboundTls'::`1'::catch$0:tlslogic.cpp(1053))( 0000000003295A68 ) Failed. Returned HRESULT=80096004 TL_ERROR(TF_NETWORK) [0]0600.0984::08/21/2012-14:57:24.615.00000057 (SIPStack,CTLSLogic::GetRemoteCertContext:tlslogic.cpp(1492))( 0000000003295A68 ) Exit$Unexpected - invalid SSPI security context TL_ERROR(TF_CONNECTION) [0]0600.0984::08/21/2012-14:57:24.615.00000058 (SIPStack,SIPAdminLog::TraceConnectionRecord:SIPAdminLog.cpp(160))$$begin_record LogType: connection Severity: error Text: Outbound TLS negotiation failed Local-IP: 88.88.88.21:49445 Peer-IP: 99.99.99.11:5061 Peer-FQDN: srgls-edge1.srgdomain1.com Connection-ID: 0x5302 Transport: TLS Result-Code: 0x80096004 $$end_record TL_ERROR(TF_DIAG) [0]0600.0984::08/21/2012-14:57:24.615.00000059 (SIPStack,SIPAdminLog::TraceDiagRecord:SIPAdminLog.cpp(143))$$begin_record LogType: diagnostic Severity: error Text: Mes
failure. Here are a few and what they might be indicating. I hope they make your life a little easier: Instant Messages “
ID 504 (source ID 239). Issue: Unable to see presence after federation. Error: When contacting your support team, reference error ID 504 (source ID 239). Problem Statement: Recently I have done the Lync http://communicationsknowledge.blogspot.com/2013/12/when-contacting-your-support-team.html federation with another Lync in-house organization. I have added the access edge to both Lync environment. After federation we are able to find each other in Lync however unable to see presence information. When you ping http://terenceluk.blogspot.com/2013/04/unable-to-send-instant-messages-or-view.html to each other then it will share above error message. Resolution / Workaround: First you need to setup Lync federation. There are many steps involved in Lync federation. You may refer below article for federation. To error id configure a user policy for anonymous participation in meeting: http://technet.microsoft.com/en-us/library/gg398359.aspx To enable or disable federated user access for your organization: http://technet.microsoft.com/en-us/library/gg182549.aspx After configuring completing federation steps. Do the following steps- There are two reason behind above error. 1. Certificate - Order the SSL certificate which from external CA which trusted by Lync. If issue persist then do the following. 2. SRV Record - Federation SRV recods. In my case we have created SRV, source id 239 A records however we missed Federation SRV Record. _sipfederationtls._tcp. priority = 0 weight = 0 port = 5061 svr hostname = After creation of above SRV record user were able to see each other presence status. Thank you. Posted by Balu Ilag at 6:32 PM Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest Labels: presence unknown after federation, reference error ID 504 (source ID 239), unable to see presence information after federation, When contacting your support team No comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) ShareThis Search This Blog Image Total Pageviews Blog Archive ► 2016 (66) ► October (1) ► September (3) ► August (9) ► July (4) ► June (4) ► May (5) ► April (5) ► March (19) ► February (10) ► January (6) ► 2015 (109) ► December (5) ► November (10) ► October (10) ► September (12) ► August (11) ► July (10) ► June (6) ► May (11) ► April (10) ► March (7) ► February (12) ► January (5) ► 2014 (99) ► December (15) ► November (9) ► October (13) ► September (12) ► August (8) ► July (8) ► June (3) ► May (5) ► April (7) ► March (5) ► February (8) ► January (6) ▼ 2013 (
You've configured federation between two Lync Server 2013 environments and noticed that one of the organizations can send instant messages and see presence information but the other one cannot. The following is the organization that can send instant messages and see presence: While the other company displays a globe indicating that the user is a federated contact and is able to receive messages, presence information is labeled as "unknown": An attempt to send a message to this federated contact will display spinning dots: … then subsequently fail with the message: When contacting your support team, reference error ID 504 (source ID 239). Troubleshooting information is available online, including best practices for using Lync.TestWhen contacting your support team, reference error ID 1 (source ID 0). Troubleshooting information is available online, including best practices for using Lync. A quick debugging session with the logging tool on the front end server of the user who is unable to send or see presence information will show the following: TL_INFO(TF_PROTOCOL) [0]0C88.14F4::04/24/2013-22:53:16.498.0000358e (SIPStack,SIPAdminLog::ProtocolRecord::Flush:2387.idx(196))[2663723319] $$begin_record Trace-Correlation-Id: 2663723319 Instance-Id: 271E Direction: incoming Peer: svrgalyncedge01.ganet.internal:5061 Message-Type: response Start-Line: SIP/2.0 430 Flow Failed From: