Error Id 400 Source Id 239
Contents |
a PBX I've been called a few times in the past to look at the issue where Lync Server 2010 or lync diagnostic id 25 2013 IM (Instant Messaging) conference no longer works when RCC (Remote Call
Error Id 504 Source Id 239
Control) is configured with a PBX and as simple as the root cause is for administrators who have lync error id 403 source id 239 configured RCC before, it may not be the same for ones who are doing it the first time so this post serves to list the symptoms and the solution to
Reference Error Id 504 Source Id 239 Lync
the issue. Problem You attempt to start a IM conference between 3 participants: The IM window above has 2 participants (both Terence Luk accounts). You attempt to invite the 3rd person into the IM chat window: You see the 3rd participant briefly displayed in the chat windows: … but quickly disappear leaving the IM: There are times when you are error id 504 source id 239 lync online able to bring the 3rd participant in but you receive the following error when you send a message: When contacting your support team, reference ID 400 (source ID 239). Troubleshooting information is available online, including best practices for using Lync. No one receives the instant message. Reviewing the application logs on the workstation's event logs show the following event ID 11 warning logged: The description for Event ID 11 from source Lync cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.If the event originated on another computer, the display information had to be saved with the event.The following information was included with the event: Lync80ef0190RequestUri: sip:tluk@contoso.com;gruu;opaque=app:conf:chat:id:FS500B1GFrom: sip:tluk@contoso.com;tag=582b69a2deTo: sip:tluk@contoso.com;gruu;opaque=app:conf:chat:id:FS500B1G;tag=(null)Call-ID: a5902bd56aa54dbab02f70021f05257fContent-type: application/sdp;call-type=imv=0o=- 0 0 IN IP4 10.40.2.10s=sessionc=IN IP4 10.40.2.10t=0 0m=message 5060 sip nulla=accept-types:text/plain multipart/alternative image/gif text/rtf text/html application/x-ms-ink application/ms-imdn+xml text/x-msmsgsinvite Response Data:400 Bad request: TR87 protocol violation; required application/csta+xml content missing or invalidms-diagnostics-public: 1033;reason="Previous hop server component did not report diagnostic information";Domain="contoso.com";PeerServer="aes.contoso.internal";OriginalPresenceState="0";CurrentPresenceState="0";MeInsideUser="Yes";ConversationInitiatedBy="0";SourceNetwork="0";RemotePartyCanDoIM="No" You proceed to lo
failure. Here are a few and what they might be indicating. I hope they make your life a little easier: Instant Messages “
Lync 2013 Error Id 403 Source Id 239
is no such user at the recipient’s domain. There's an instance of OCS/Lync there, they
Lync Reference Error Id 403 Source Id 239
have an Edge, but you've simply nominated an invalid user - or guessed their e-mail naming format wrong. 2) There *is* lync error id 504 (source id 239) such a user at the recipient’s domain – but they’re not enabled for Federation. There's an instance of OCS/Lync there & they have an Edge. [TBC] 3) There *may be* such a user at the recipient’s http://terenceluk.blogspot.com/2013/03/lync-server-2010-or-2013-im-instant.html domain – but they don’t have open Federation and THEY don’t trust YOUR domain. [In this example, my lab domain is not Federated with Microsoft]. “
client error which I hadn’t seen before “Call was not transferred because [user name] does not have an audio device set up to accept calls.” In this case, the error was a little http://tomtalks.uk/2011/07/lync-client-error-codes/ misleading. The endpoint the customer was transferring to was fine, and it was http://communicationsknowledge.blogspot.com/2013/12/when-contacting-your-support-team.html happening to more than one user. In actual fact this was a SIP Refer issue. As soon as we disabled SIP refer on the PSTN trunk, transfers were successful. In my troubleshooting I came across this useful reference list of SIP errors in the Microsoft protocol documentation, and thought it might error id come in useful. http://msdn.microsoft.com/en-us/library/gg132389(v=office.12).aspx Mode Error Id Error Message Additional Information Conference 400 [user name] cannot be reached. This person is using an application that does not support this type of meeting. Conference 404 [user name] cannot be found. Please check the address and try again. Conference 404 The meeting you are trying to join has ended. The meeting you are trying to join source id 239 has ended or does not exist. Contact your support team with this information. Conference 408 The conferencing service did not respond. Please wait and try again. Conference 408 The invitation to [user name] expired. Conference 410 [user name] cannot be found. Please check the address and try again. Conference 413 This online meeting cannot be found. This online meeting cannot be found on the server. Please check the meeting ID and try again. Conference 415 [user name] cannot be reached. This person is using an application that does not support this type of meeting. Conference 480 [user name] cannot be reached and may be offline. Conference 482 [user name] cannot be reached because of conferencing service issues. Conference 483 [user name] cannot be reached because of conferencing service issues. Conference 486 Cannot reach [user name]. Try again later. Conference 488 [user name] cannot be reached. This person is using an application that does not support this type of meeting. Conference 488 The meeting you are trying to join has ended. The meeting you are trying to join has ended or does not exist. Contact your support team with this information. Conferenc
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 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 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 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, 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 (105) ▼ December (9) Antivirus scanning exclusion l