locked
Skype for Business Skype federarton RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi ,

    Since a few weeks it not possible to set up a video call between a Skype for Business 2015 client (office 2013) and a public Skype user. With the  Skype for Business client 2016 ( office 2016 ) there's no problem.

    Is there a change in the requirements for a Skype f B, Skype public federation ?

    Any ideas or suggestions?

    Monday, September 18, 2017 1:34 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hey,

    just checked it within our deployment. Videocall is working without any problem between SfB 2015 Client and Consumer Skype. I am not aware of any changes beeing made regarding SfB 2015 and Skype Consumer compatibility.

    Few questions:

    - Does this problem occur on multiple systems?
    - What Client version of 2015 do you use?
    - When you install SfB 2016 on a system where this was not working with 2015 - is it working?
    - Did you take a look into the client logs to see what happens during the media negotiation
    - How is the error looking like? Signaling is ok, but after accepting the call drops?
    - Only audio is working fine?

    Greets,
    Markus

    Monday, September 18, 2017 8:07 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Frank,

     

    1.Do all SFB 2015 clients have this problem?

    If not all SFB 2015 clients have this problem,please compare the clients’ version.

     

    2.when you could not set up a video call ,did the client have some error messages?

    if any, please send us a screenshot for the error message.

     

    You can update the skype for business 2015 client to the latest version and make a test,the following document is for your reference.

    https://blogs.technet.microsoft.com/uclobby/2016/10/19/lync-2013-skype-for-business-2015-client-update-list/

    Best Regards,

    Leon-Lu
    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

    Tuesday, September 19, 2017 5:58 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi ,

    All clients have the problem. I've tested it with 2 customers both have  skype for business onprem . I'm trying to test this week with a fully updates client. The problem is with starting a video call from Skype to Skype for Business. Skype for Business to Skype works fine ( audio and video )

    chat from skype to SFB works with any problem.

    Thursday, September 21, 2017 9:56 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Frank2601,

    Have you tested fully updates client?Was the issues existed?

    Best Regards,

    Leon-Lu
    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 25, 2017 9:33 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Are there any update for this issue, if the reply is helpful to you, please try to mark it as an answer, it will help others who has similar issue.

    Best Regards,

    Leon-Lu
    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

    Wednesday, September 27, 2017 9:14 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi ,

    I've tested with an fully updated client. The problem stil exist. What i've noticed is that when I make an call to my mobile ( android with Skype client (Not SfB)). evety things works. When I try the Skype client on my laptop ( same network as my mobile ) there's no video.

    In the logs I find a time out message

    Authentication-Info: TLS-DSK qop="auth", opaque="F56A9C03", srand="7E9124BC", snum="30", rspauth="db823cb97b74d471a1433c5f9a8dcda760391823", targetname="frontend.BASIS.LAN", realm="SIP Communications Service", version=4

    Via: SIP/2.0/TLS 10.13.22.193:49657;ms-received-port=49657;ms-received-cid=47C5B00

    CONTENT-LENGTH: 0

    From: "xxxx, xx"<sip:x.xxxx@yxxx.xx>;tag=294f9b77e7;epid=787a5fbc19

    To: <sip:xxx_xxxx@hotmail.com>;tag=d84ae0c8be;epid=4B14175EFD

    CSeq: 1 INVITE

    Call-ID: ce77fae0315240e38d01d67bbf25c771

    Priority: Normal

    Supported: replaces

    P-Asserted-Identity: ""<sip:xxx_xxxx@hotmail.com;maddr=sip.lgw.skype.com;transport=tls>

    X-Microsoft-Skype-Chain-ID: 367add81-90a5-4083-828b-30ddc52dce23

    ngc-diagnostics: 930010004;reason="Call cancelled on timeout";ngcCode="487";LgwProcessingInstance="a-lgw-euno-01.lgw.skype.com:IN_1"

    Ms-Conversation-ID: AdM4WWXapx3q2Lo6QIubHz0CgweGLA==

    ms-lync-skype-gw-2: true

    ms-telemetry-id: 566F2BC5-A500-5D01-BFD1-F8B8E9541A3A

    ms-diagnostics: 1033;reason="Previous hop server component did not report diagnostic information";Domain="hotmail.com";PeerServer="b-lgw-euwe-01.lgw.skype.com";source="federation.messenger.msn.com"

    ms-edge-proxy-message-trust: ms-source-type=AuthorizedServer;ms-ep-fqdn=edgepool.basis.lan;ms-source-network=publiccloud;ms-source-verified-user=verified;ms-remote-fqdn=federation.messenger.msn.com

    Thursday, September 28, 2017 6:43 PM