none
Skype For Business video call with federated partner's video solution RRS feed

  • Question

  • Hi,

    We are trying to connect to a virtual room of our federated partner's Video solution but every time it fails with stating that "Call failed due to Network issue" although If we do video call with any normal federated user, it works.

    I checked in UCCApi logs and found below error :

    INFO  :: MM_FP_CONFIG.PeerFederation set to 0

    INFO  :: CUccSessionParticipant::InternalSetState [1B1EA254] - state: 0x2->0x2

    ERROR :: SIP_MESSAGE::GetHeader: HRESULT API failed: 80ee0005 = hr. GetHeader

    WARN  :: header not present

    ERROR :: SIP_MESSAGE::GetHeader: HRESULT API failed: 80ee0005 = hr. GetHeader

    INFO  :: MSP.SetState[163B2770] SIP_CALL_STATE_ALERTING-

    SIP_MESSAGE::GetHeader: HRESULT API failed: 80ee0005 = hr. GetHeader

    ERROR :: Already completed receiving final response.

    ERROR :: SIP_MESSAGE::GetHeader: HRESULT API failed: 80ee0005 = hr. GetHeader

    WARN  :: we can't find SIP_HEADER_MS_ENDPOINT_LOCATION_DATA

    Please suggest if anyone has any idea on this error.

    -James

    Tuesday, January 10, 2017 5:43 PM

All replies

  • Hi James,

    Welcome to post in our forum.

    Based on your description, when you use normal video call with federation users, it works fine, so from my point of view, there may be no problem with federation.

    Did the issue only appear on the specific client ?

    If the issue only appeared on the specific client, please try to clear SFB cache files and test again.
    %userprofile%\AppData\Local\Microsoft\Office\15.0\Lync\sip_UserName@Domain.com (Lync 2013/ SFB 2015)

    You could also check the configuration of Lync room system, please refer to
    https://www.microsoft.com/en-us/download/details.aspx

    Hope this reply is helpful to you.


    Regards,

    Alice Wang


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

    Wednesday, January 11, 2017 5:19 AM
    Moderator
  • Hi,

    This issue is for every user.We again gone through th UCCApi  logs and found:

    "Attempt was made to set port range for mode that is not supported! Audio/Video/Pano/AS/Data are only supported"

    "CSipSubscription::InternalUnsubscribe CreateOutgoingUnsub failed 80004005, this 17A09AF0."

    Please suggest if we get some clue with above error.

    -James

    Thursday, January 12, 2017 12:06 PM
  • Hi,

    Please suggest what should we check here.

    -James

    Monday, January 16, 2017 10:25 AM
  • This could be because the media traffic to third party video solution should flow directly from your end.Not through the federated partner edge server.If they are routing media through partner edge server then only this will work.

    Other things may be the media port ranges allowed by your edge server may not be supporting the partner required media port ranges or not matching with both the ends.Network trace will give more information on this issue.

    Your client network trace as well as the edge server network trace.


    Jayakumar K

    Monday, January 16, 2017 1:57 PM
  • We analyzed the SFB client tracing and through Snooper we see that the following event appears 

    ERROR :: CUccOutgoingInviteOperation::Execute: HRESULT API failed: 80ee000b = hr. StartNegotiation on Media Flow failed.

    Any suggestion ?

    -James

    Tuesday, January 17, 2017 9:47 PM
  • Hi, is the Audio Call good with federated partner ?

    How about AV calls with other Federated partners ?

    Wednesday, January 18, 2017 1:33 AM
  • Hi,

    Audio and video Calls are fine with other federated partners.Not sure why but this issue is with particular federated partner only although they have open federation.They do have other federated partners who can connect them without any issue.

    -James

    Wednesday, January 18, 2017 9:23 AM
  • Hi James,

    For this issue, please check if UDP 3478 is open on the Edge server. Make sure UDP 50000-59999 are open at least from Edge to internet.

    Regards,

    Alice Wang


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

    Monday, January 23, 2017 1:57 AM
    Moderator
  • Hi Alice,

    UDP 3478 is already open from A/V Edge Server Public IP to internet. Please suggest if UDP 50000-59999 will require only from A/V Edge Server Public IP to Internet or from Web Conf Edge Server Public IP also ?

    I have read in many articles these ports are required where federated partners are still using OCS 2007, is that recommended these ports should be opened in every Lync environment ?

    -James

    Monday, January 23, 2017 6:26 PM
  • Hi Alice,

    Please suggest.

    -James

    Friday, January 27, 2017 10:21 AM
  • Does the federated partner's video solution support ICE?  If it doesn't, then it's possible that you're having issues negotiating a media session with your Edge Server.
    Wednesday, February 1, 2017 2:42 PM
  • Hi,

    Please suggest what configuration I need to do if that does not support ICE ?

    Also one more thing I noticed that Call disconnects exactly at 10 seconds every time.Please suggest if there is any known issue relates to this time span.

    -James

    Thursday, February 9, 2017 8:19 PM