Hello All,
I’m using Skype for Business online and logged on with a directory synced user. We have a Exchange Hybrid and we use the same UPN for SFB Online as well. (SFB is not a hybrid).
We’ve set up the DNS records correctly and have given access to see external (personal skype) users as well. It works fine where the users can add external skype users/ can see presence/ can send and receive IMs, Audio and Video.
SFB Online to SFB Online file transfer works OK. However SFB Online to Personal Skype file transfer gives the error – Error in Transfer and Transfer Failed.
Tried sending doc files, txt files but still the same error.
Any help would be appreaciated to sort this issue.
Many thanks.
This is our external communication on Admin Portal (below)
And the user options (below)
This is our Global Conference policy
And all the users have assigned to the below policy by default
The event viewer always logs 2 events when it fails to transfer. Please refer below.
Event 1 -
A SIP request made by Lync failed in an unexpected manner (status code 80ef01e8). More information is contained in the following technical data:
RequestUri: sip:xxxxxx@skypeids.net
From: sip:xxxxxx@xxxxxx.com.xx;tag=fd6a51967c
To: sip:xxxxxx85@skypeids.net;tag=(null)
Call-ID: 8a8a0bef1c374cfcb2d95899bf515ad7
Content-type: multipart/mixed;boundary="----=_NextPart_000_005C_01D305F8.81DE8AB0";call-type=datasharing
------=_NextPart_000_005C_01D305F8.81DE8AB0
Content-Type: application/sdp
Content-Transfer-Encoding: 7bit
Content-ID: <3f4cc40cb90df06cfbc7bd3d86e421b9@sealink.com.au>
Content-Disposition: session; handling=optional; ms-proxy-2007fallback
v=0
o=- 0 0 IN IP4 52.113.5.29
s=session
c=IN IP4 52.113.5.29
b=CT:99980
t=0 0
m=data 54083 TCP/RTP/SAVP 127
a=ice-ufrag:5lMR
a=ice-pwd:FNJRfT4bUaOgKeaE0ivn64Ei
a=candidate:1 1 TCP-PASS 2120613887 My_Internal_IP 50051 typ host
a=candidate:1 2 TCP-PASS 2120613374 My_Internal_IP 50051 typ host
a=candidate:2 1 TCP-ACT 2121006591 My_Internal_IP 50040 typ host
a=candidate:2 2 TCP-ACT 2121006078 My_Internal_IP 50040 typ host
a=candidate:3 1 TCP-PASS 174455807 52.113.5.29 54083 typ relay raddr 52.113.5.126 rport 50046
a=candidate:3 2 TCP-PASS 174455294 52.113.5.29 54083 typ relay raddr 52.113.5.126 rport 50046
a=candidate:4 1 TCP-ACT 174848511 52.113.5.29 54083 typ relay raddr 52.113.5.126 rport 50046
a=candidate:4 2 TCP-ACT 174847998 52.113.5.29 54083 typ relay raddr 52.113.5.126 rport 50046
a=x-candidate-ipv6:5 1 TCP-PASS 174454783 2603:1047:0:8a::22 55546 typ relay raddr 52.113.5.126 rport 50046
a=x-candidate-ipv6:5 2 TCP-PASS 174454270 2603:1047:0:8a::22 55546 typ relay raddr 52.113.5.126 rport 50046
a=x-candidate-ipv6:6 1 TCP-ACT 174847487 2603:1047:0:8a::22 55546 typ relay raddr 52.113.5.126 rport 50046
a=x-candidate-ipv6:6 2 TCP-ACT 174846974 2603:1047:0:8a::22 55546 typ relay raddr 52.113.5.126 rport 50046
a=candidate:7 1 TCP-ACT 1684796415 52.113.5.126 50046 typ srflx raddr My_Internal_IP rport 50046
a=candidate:7 2 TCP-ACT 1684795902 52.113.5.126 50046 typ srflx raddr My_Internal_IP rport 50046
a=cryptoscale:1 client AES_CM_128_HMAC_SHA1_80 inline:55WK23PiQ0ImP5q3utV2MIBIVBoFaeRUClx2fxzZ|2^31|1:1
a=crypto:2 AES_CM_128_HMAC_SHA1_80 inline:55WK23PiQ0ImP5q3utV2MIBIVBoFaeRUClx2fxzZ|2^31|1:1
a=crypto:3 AES_CM_128_HMAC_SHA1_80 inline:55WK23PiQ0ImP5q3utV2MIBIVBoFaeRUClx2fxzZ|2^31
a=fingerprint:sha-256 5C:F4:D1:BD:06:3B:7B:4E:FB:1C:81:84:2C:59:3C:A2:F7:CD:FD:15:91:04:52:9E:CC:59:42:58:87:14:1D:86
a=setup:passive
a=connection:new
a=rtcp:54083
a=mid:1
a=sendonly
a=rtpmap:127 x-data/90000
a=rtcp-mux
a=extmap:1 http:\\www.webrtc.org\experiments\rtp-hdrext\abs-send-time
a=extmap:3 http:\\skype.com\experiments\rtp-hdrext\fast_bandwidth_feedback
a=x-bwealgorithm:packetpair
------=_NextPart_000_005C_01D305F8.81DE8AB0
Content-Type: application/ms-filetransfer+xml
Content-Transfer-Encoding: quoted-printable
Content-ID: <10ff32ea63c042faae3d341fc2aff8e3@3efe0ee83648417da2f87ea78fb00743>
Content-Disposition: render; handling=optional
<request xmlns=3D"http://schemas.microsoft.com/rtc/2009/05/filetransfer" =
requestId=3D"9">
<publishFile>
<fileInfo embedded=3D"false">
<id>{FA715A9B-5F74-4DB9-A118-EBCB7515F83E}</id>
<name>fileName.docx</name>
<size>75114</size>
</fileInfo>
</publishFile>
</request>
------=_NextPart_000_005C_01D305F8.81DE8AB0--
Response Data:
488 Unsupported media line in SDP
ms-diagnostics: 1033;reason="Previous hop server component did not report diagnostic information";Domain="skypeids.net";PeerServer="lync.bridge.messenger.live.com";source="federation.messenger.msn.com";OriginalPresenceState="0";CurrentPresenceState="0";MeInsideUser="No";ConversationInitiatedBy="0";SourceNetwork="0";RemotePartyCanDoIM="No"
Resolution:
If this error continues to occur, please contact your network administrator. The network administrator can use a tool like winerror.exe from the Windows Resource Kit or lcserror.exe from the Office Communications Server Resource Kit in order to interpret any error codes listed above.
Event 2
A SIP request made by Lync failed in an unexpected manner (status code 80ef019f). More information is contained in the following technical data:
RequestUri: sip:xxxxxx@skypeids.net
From: sip:xxxx@sealink.com.xx;tag=718d486548
To: sip:xxxxx@skypeids.net;tag=15_140_wtw9ymb9
Call-ID: 998f13040e4d4cc1b341bd9b31738f48
Content-type: application/sdp;call-type=im
v=0
o=- 0 0 IN IP4 my_Internal_IP
s=session
c=IN IP4 192.168.0.179
t=0 0
m=message 5060 sip null
a=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:
415 Unsupported Media Type
ms-diagnostics: 1033;reason="Previous hop server component did not report diagnostic information";Domain="skypeids.net";PeerServer="lync.bridge.messenger.live.com";source="federation.messenger.msn.com";OriginalPresenceState="3000";CurrentPresenceState="3000";MeInsideUser="No";ConversationInitiatedBy="6";SourceNetwork="4";RemotePartyCanDoIM="Yes"
Resolution:
If this error continues to occur, please contact your network administrator. The network administrator can use a tool like winerror.exe from the Windows Resource Kit or lcserror.exe from the Office Communications Server Resource Kit in order to interpret any error codes listed above.
Accepted Solutions