locked
PIC Lync-Skpe federation, does it works? RRS feed

  • Question

  • Hi all

    I have SFB2015 server with edge & reverse proxy.

    1 year ago i have connect PIC (Lync-Skype Federation)

    but all the time it works very unstable:

    1 month works, then 1 month not

    today its doesn't works again

    somebody have it stable?

    or this is beta function ?

    Monday, September 19, 2016 2:07 PM

Answers

  • hi

    good news

    i have fixed where is the problem:

    messages works good with old version of Skype Client ( 7.26.0.101)

    and they doesn't works in new Skype client (7.28.66.101)

    Tuesday, October 18, 2016 11:21 AM

All replies

  • Skype federation works sometime good, sometime it has problems. Be sure that you use always the new skypeids.net for the users sip address.

    regards Holger Technical Specialist UC

    Monday, September 19, 2016 3:14 PM
  • yes accounts@skypeids.net

    skype users with Microsoft acconts - works good

    old skype users (without MSA) - works very bad

    Monday, September 19, 2016 6:12 PM
  • Hi Dmitrii Baliasnikov,

    Welcome to post in our forum.

    Would you please tell us is that all non-MSA account cannot work in your environment ?

    As you have mentioned, the federation one month work and one month didn’t work, when it didn’t work, did you mean that all users (MSA& non MSA) didn’t work?

    Are there any error message when it didn’t work ?

    Please try to use remote connectivity analyzer test if there are any error about connectivity.

    And you could try to telnet port 5061 and make sure this port is open.

    You could also try to run the command line in Lync management shell to check if there is any error message :

    Test-CsFederatedPartner -domain <sistercompany> -TargetFqdn <edge>

    For details, please refer to

    https://technet.microsoft.com/en-us/library/gg398281.aspx?f=255&MSPPError=-2147217396

    Hope this reply helpful to you.


    Alice Wang
    TechNet Community Support


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    • Proposed as answer by Liinus Tuesday, September 20, 2016 6:46 AM
    • Unproposed as answer by Dmitrii Baliasnikov Thursday, September 22, 2016 8:58 PM
    Tuesday, September 20, 2016 5:55 AM
  • hi Dmitrii , 

    sort out the behaviour as Alice was suggesting to isolate the issue with specific ids in the mean time would you also lets us know about the skype for business which  you are with is that onpremise or  online, was there any attempt to register  your domain with Online  sometimes as there could also be stale entries which can cause this.   From the server level also make sure that the Edge is replicated and upto date with all the updates. check the port reach ability that is required for the federation  as well. 

    I will also list  out few steps which you can go through for troubleshooting methords

    1. On Edge Server, check if you can telnet federation.messenger.msn.com 5061.

    2. Remove and re-add the Skype provider.

    New-CsPublicProvider -Identity Skype -ProxyFqdn federation.messenger.msn.com -IconUrlhttps://images.edge.messenger.live.com/Messenger_16x16.png -NameDecorationRoutingDomain msn.com -NameDecorationExcludedDomainList "msn.com,outlook.com,live.com,hotmail.com" -Enabled $true -EnableSkypeIdRouting $true -EnableSkypeDirectorySearch $true

     

    3. Please make sure you are using a Microsoft account.  Skype users must be signed in with their Microsoft account for any Lync to Skype federation scenarios to work.

    4. Check the replication status on Edge Server.

     5. Telnet skypegraph.skype.com 443


    Linus || Please mark posts as answers/helpful if it answers your question.

    Tuesday, September 20, 2016 6:51 AM
  • Hi Alice, Linus

    I have Skype For business server 2015 on premise (march 2016 CU)

    I mean that non MSA accounts doesn't work 

    MSA Accounts always works good, but i cant tell all users in the world to use MSA Accounts

    i have no errors on edge and frontend

    Remote Connectivity Analyzer test - successful 

    I have 3 public ipv4 addresses on edge (without NAT). No firewall now, and windows firewall turned off.

    telnet from external to sip.mydomain.com 5061 - works 

    telnet from edge to federation.messenger.msn.com - 5061 works

    Test-CsFederatedPartner -domain push.lync.com with my edge - Success

    remove and re-add skype provider - done

    replication on edge - works

    telnet skypegraph.skype.com 443 - works

    no result

    Skype Users (without MSA) can see my lync status - green

    Skype Users can write me message - it works

    In Skype For Business 2015/2016 clients Skype Users without MSA - always Offline

    Skype For Business 2015/2016 clients cannot reply message to Skype users without MSA - can't receive IMs right now. Status is unavailable or offline.

    Tuesday, September 20, 2016 10:12 AM
  • Hi Dmitrii Baliasnikov,

    Thank you for your reply and thanks for sharing your result to me.

    Would you please tell us did you mean that the issue only appeared on the SFB 2015/2016 client, and there is no issue with Lync 2013 client ?

    If so, based on my understanding, it is the SFB client side issue.

    Please try to test this issue with other PC client.

    Moreover, for SFB 2015/2016 client, is that the specific user or client have this issue?

    If the specific user has the issue, please try to compare the user attribute between affected user and normal user.

    If the issue only appeared on the specific SFB client, please try to delete SFB cache files and test again.

    %userprofile%\AppData\Local\Microsoft\Office\15.0\Lync\sip_UserName@Domain.com (SFB 2015)

    %userprofile%\AppData\Local\Microsoft\Office\16.0\Lync\sip_UserName@Domain.com (SFB 2016)

    Hope this reply helpful to you.

    If you have any question, please feel free let me know.


    Alice Wang
    TechNet Community Support


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, September 23, 2016 10:00 AM
  • Hi Alice

    its not a client problem

    i have tested it on s4b 2016/2015, lync 2013 and lync 2011 mac

    i have tested it on different s4b users and computers (include mac)

    Friday, September 23, 2016 10:13 AM
  • Hi Dmitrii Baliasnikov,

    Thanks for your response.

    Since you mentioned:

    Skype Users (without MSA) can see my lync status - green

    Skype Users can write me message - it works

    I guess it works fine with Lync 2013 client.

    Thanks for your confirmation, it will help us narrow done the issue.

    In order to do further troubleshooting, please help us confirm the following questions:

    Did you have any event log/ID or any error message in your environment, would you please provide it to us for the further troubleshooting?

    What kind of non-MSA account did you use in your environment?

    You can use Lync Logging Tool on Edge server to collect trace file. You can choose S4 and SIPStack component.

    Make sure your SFB server with the latest update.

    Hope this reply helpful to you.


    Alice Wang
    TechNet Community Support


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, September 26, 2016 9:52 AM
  • Hi Alice

    Thanks for your reply

    i have found error with Logging tool:

    TL_ERROR(TF_COMPONENT) [vs-skype-edge\vs-skype-edge]04EC.0768::09/27/2016-06:57:15.022.00002367 ((Shared),ValidateCertPolicyAndChain:CertificateHelper.cpp(1779)) 
    Exit - certificate chain verification for SN=[federation.messenger.msn.com] returned a failure in CERT_CHAIN_POLICY_STATUS. Returned HRESULT=800B010F

    Tuesday, September 27, 2016 7:25 AM
  • Hi Dmitrii Baliasnikov,

    Thanks for your response.

    According to your error message, it may be something wrong your certificate.

    You could try to recreate certificate to add the SN to the certificate.

    Hope this reply helpful to you.


    Alice Wang
    TechNet Community Support


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    • Proposed as answer by Alice-Wang Monday, October 10, 2016 10:03 AM
    • Unproposed as answer by Dmitrii Baliasnikov Tuesday, October 11, 2016 12:28 PM
    Thursday, September 29, 2016 5:58 AM
  • Hi Alice

    i checked my Comodo certificate:

    sn sip.mydomain.com

    san sip.mydomain.com

    san av.mydomain.com

    san webconf.mydomain.com

    i don't think that problem with certificate, because Connectivity Analyser works good, federation with other companies and with non-MSA accounts works good

    i think the problem with only some Skype accounts (like my)

    Can anybody write me test message from skype for business? (my skype account - dbalas2)

    Monday, October 10, 2016 10:58 AM
  • hi

    good news

    i have fixed where is the problem:

    messages works good with old version of Skype Client ( 7.26.0.101)

    and they doesn't works in new Skype client (7.28.66.101)

    Tuesday, October 18, 2016 11:21 AM