Error Id 504 Source Id 239 Lync
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) Home20132010Other VersionsLibraryForumsGallery Ask a question Quick access Forums home Browse forums users FAQ Search lync 2013 error id 504 related threads Remove From My Forums Answered by:
Microsoft Lync Error Id 504 (source Id 239)
when contacting your support team, reference error ID 504 (ssource ID 239) Lync lync reference error id 504 (source id 239) Server > Lync Server 2013 - Sign-In, Presence, IM, and Contacts Question 0 Sign in to vote Hi, The certificate
Reference Error Id 504 (source Id 239) Lync 2013
and the CA server was changed Got some issues: - External Lync user cannot change lync status from offline to online - Even if the external Lync user status is offline, the user can still see the status of his contacts when contacting your support team reference error id 504 (source id 239) - External Lync user can IM the internal Lync user but the internal Lync usercannot reply to IM with error message when contacting your support team, reference error ID 504 (ssource ID 239) Any known issues and fix? Thanks Tuesday, March 03, 2015 3:46 AM Reply | Quote Answers 0 Sign in to vote Hi, Please make sure that Edge can resolve the user's front end. Please check the old posts similar issue that has been resolved. https://social.technet.microsoft.com/Forums/en-US/071b373b-6851-45fc-96c2-6f8f60eb32de/internal-user-got-error-id-504-source-id-239-when-reply-the-message-to-external-user?forum=lyncprofile https://social.technet.microsoft.com/Forums/en-US/eff520ae-826e-441e-98aa-9bc6b47aed6b/unable-to-message-external-user?forum=ocsedge check this https://greiginsydney.com/decoding-lyncs-client-side-error-messages/ Whenever you see a helpful reply, click on Vote As Helpful & click on Mark As Answer if a post answers your question. Edited by Raju_rajuMVP Tuesday, March 03, 2015 6:49 AM Marked as answer by Eric_YangKMicrosoft contingent staff, Moderato
ID 504 (source ID 239). Issue: Unable to see presence after federation. Error: When contacting your support team, reference error
Lync Error Id 403 Source Id 239
ID 504 (source ID 239). Problem Statement: Recently I have done the
Lync Error Id 503 Source Id 239
Lync federation with another Lync in-house organization. I have added the access edge to both Lync environment. After skype for business federation we are able to find each other in Lync however unable to see presence information. When you ping to each other then it will share above error message. https://social.technet.microsoft.com/Forums/office/en-US/8baa6e80-8b7a-453d-910a-b99c4751155c/when-contacting-your-support-team-reference-error-id-504-ssource-id-239?forum=lyncprofile 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 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 http://communicationsknowledge.blogspot.com/2013/12/when-contacting-your-support-team.html 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, 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
to be inconsistent. Even though an organization was configured for "open federation", I couldn't necessarily federate with them. The error received when attempting to send a message was "reference error ID 504 (source http://www.itworkedinthelab.com/2011/11/lync-2010-federation-fails-reference-error-id-504-source-id-239/ ID 239)"; most who have worked with OCS 2007 or Lync 2010 will recognize as http://terenceluk.blogspot.com/2013/04/unable-to-send-instant-messages-or-view.html being a fairly generic communication error. After reviewing the logs on my edge server with "Snooper", I could see where TLS failures were causing the error; this had me thinking I was probably looking at a certificate issue. Fortunately, with one prospective federated organization, I was able to look at their edge server and check the installed root certificates. error id Despite my certificate authority (StartCom) being on the "Windows Root Certificate Program Members" list, it was not listed in the trusted root CAs on the other organization's edge server. The list of installed trusted root CAs in Windows 2008 is significantly less than in previous versions of Windows; this is because Windows 2008 utilizes the "Automatic Root Certificates Update" feature which downloads approved root certificates on an as-needed basis. This "as-needed basis", however, does not source id 239 apply to communication from Lync. Thus, even when configured for open federation, your edge server will only successfully federate with organizations using certificates from one of the base install root CAs or the same CA as you (since you'd have that root certificate). If you want to have the least compatibility problems with other organizations federating with you, it may be worth your time to install the root certificates for some of the more common CAs (i.e. VeriSign, GoDaddy, Thawte, DigiCert, Comodo, etc). This can be done quite easily in most cases by just hitting up the vendor's website with https:// using Internet Explorer on your edge server and "Automatic Root Certificates Update" will handle installing the certificate. Otherwise, if you have a specific partner for whom you need to install their certificate chain, it can be done relatively easy as well. First, you'll want to look up their edge server, this can be done via the following command (where "iwitl.com" is your partner's domain name): nslookup -type=SRV _sipfederationtls._tcp.iwitl.com The response should look something like below: _sipfederationtls._tcp.iwitl.com SRV service location: priority = 5 weight = 0 port = 5061 svr hostname = sip.iwitl.com From your edge server, you can now open Internet Explorer and type "https://sip.iwitl.com:5061" into the address bar. While you'll get a "Page Cannot Be Displayed" error within Inter
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: