Lync Error Id 503 Source Id 239
Contents |
Lync 2010 Unable to Transfer Calls in A Response Group with a PSTN connected through Call ManagerExpress/UC500 Jul 17 Posted by James Botham Another small integration issue when connecting Call Manager Express with Lync 2010, users in a response group were getting thrown an error lync reference error id 403 source id 239 when the call arrived from the PSTN via our CME SIP trunk. The Lync error this
Lync Error Id 504 (source Id 239)
time was slightly less informative “Cannot complete the transfer, when contacting your support team, reference error ID 503 (source ID 239)” or see below
When Contacting Your Support Team Reference Error Id 1 Source Id 0
for the graphical version. After a bit of digging this was related to our trunk configuration being misconfigured when it came to how SIP refer messages were being handled. This was caused because in essence the Lync server had
Error Id 430 (source Id 239)
picked up the call to play our messages, music whilst waiting etc. before transferring it to a real human which is where the problem starts, the real human cannot now transfer the call to another person. After doing some digging I found a TechNet article describing my exact symptoms (http://support.microsoft.com/kb/2506083), the problem occurs when you have “enable refer support” switched on. To resolve you need to go in to your trunk configuration and remove the “enable refer support” check box lync error codes as below, the GUI will also fail to save you configuration unless you also remove “enable media bypass” so un-tick that as well. This will leave you with a trunk configured similar to the below. Once completed press OK and then select commit all in the next screen to save and activate your changes within Lync. Again as with any changes grab a cup of coffee and leave Lync for 5 minutes so that it processes your changes. That is it, your response group transfer issues should now be sorted. Posted in Lync 2010 Leave a comment Lync 2010 hold issue with Cisco Call ManagerExpress/UC500 Jul 16 Posted by James Botham Well we went live with Lync 2010 on our customer support desk and as per any go live there were a couple of teething issues so I thought I would blog one of the biggies I got that didn’t show up in testing, but was a nasty on go live. This seems to apply to CME as well as the UC500 platform but from what I have seen it will most likely apply to Cisco Call Manager as well (I don’t have a CM to play with and test though). The issue is that when you place somebody on hold after what seemed like a random amount of times the call would get cut off (it normally seemed to cut you off between 30 and 40
Address LookupWhat's My IP AddressContact Tag Archives: error ID 403 (source ID 239) Lync On-Premise with Office 365 Federation - error ID 403 Leave a reply When communicating to hosted companies in Office 365 from an On-Premise Lync environment, I lync call was not completed or has ended had begun seeing the following symptoms: Presence defaulted to Unknown for federated contacts: When joining someone's lync reference error id 102 source id 238 meeting or sending them an IM, I would see the following: "When contacting your support team, reference error ID lync response group agent anonymity 403 (source ID 239)." Inside of event viewer, I saw: 403 Forbidden ms-diagnostics-public: 1034;reason="Previous hop federated peer did not report diagnostic information";Domain="othercompanydomainon.com";PeerServer="sipfed.online.lync.com" Solution: Interestingly enough, even though you have an On-Premise https://jamesbotham.wordpress.com/category/lync-2010/ Lync environment, it appears that Office 365 will tie back to your account for some settings. In my case, I had not enabled federation to other PIC providers on Office 365. To resolve the issue, please follow the steps below: Login to the Office 365 Admin Portal Click on Manage Lync Click on the External communications tab and ensure the following settings: Domain federation http://jackstromberg.com/tag/error-id-403-source-id-239/ mode: Turned on for all domains except blocked domains (you can switch to the other mode, just keep in mind you will have to whitelist every domain you are enabling communication with) Public IM connectivity mode: Enabled Next, head over to the Lync Online Control Panel for your on-premise Lync deployment. Select the Federation nand External Access tab and then select SIP Federated Providers Ensure you have created a rule for the provider LyncOnline that is federated to sipfed.online.lync.com
To create the provider via the Lync Server 2013 Control Panel Select New… and then click Hosted Provider Enable communications with this provider: Checked Provider Name: LyncOnline Access Edge Service (FQDN): sipfed.online.lync.com Click Commit To create the provider via PowerShell, execute the following command: New-CSHostingProvider -identity LyncOnline -ProxyFqdn sipfed.online.lync.com -Enabled $True Wait a few minutes for the changes to take effect, exit out of your Lync client on your workstation, reopen and you should now be able to communicate to your federated partner. Bookmark on Delicious Digg this post Recommend on Facebook share via Reddit Share with Stumblers Tweet about it Subscribe to the comments on this post Print for later Bookmafor Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help https://www.experts-exchange.com/questions/28205839/Lync-Server-2013-An-error-ocurred-during-the-lync-meeting-Error-ID-403-Source-ID-239.html Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > Lync Server 2013- An error ocurred during the lync meeting. Error ID:403 (Source ID:239) Want to Advertise Here? Solved Lync Server 2013- An error ocurred during the lync meeting. Error ID:403 (Source ID:239) Posted on 2013-08-06 Exchange MS Applications Conferencing Software 1 Verified Solution 4 Comments 8,393 error id Views Last Modified: 2015-02-27 Hi We are receiving the following error when we try to join to external lync meeting . The error showed is this: "An error occurred during the lync meeting . When contacting your support team, reference error ID:403 (Source ID:239)..." The federation is enabled at lync server and all the port opened. In the other direction when we created the meeting the external domain is able to join source id 239 but they are no able to see the whiteboard, PowerPoint or we can not send attachment the error code trying is 141. Let me know if you have any suggestion Thanks LL 0 Question by:CGNET-TE Facebook Twitter LinkedIn Google LVL 12 Best Solution byImtiaz Hasham Please advise what events are logged on the Lync Server at the time of the call Go to Solution 4 Comments LVL 12 Overall: Level 12 Exchange 7 MS Applications 1 Message Accepted Solution by:Imtiaz Hasham2013-08-31 Please advise what events are logged on the Lync Server at the time of the call 0 Message Author Comment by:CGNET-TE2013-11-01 thanks it was a firewall issue 0 LVL 12 Overall: Level 12 Exchange 7 MS Applications 1 Message Expert Comment by:Imtiaz Hasham2013-11-02 noted! 0 LVL 17 Overall: Level 17 Exchange 4 MS Applications 2 Message Active today Expert Comment by:LesterClayton2015-02-27 I just ran into this issue myself - at least with the same error message and code described, and the solution for me was to change the global External Access Policy (or create a site or user policy), and permit External chatting. I'm pasting the solution for me here since EE comes up very high on the results when searching for the error message. 0 Write Comment Firs