Once this chain is established it promises the remote client to send its media connection to the internal network client. This will establish a chain of connection between the external client and the client inside the network.By using this edge servers will create a chain and will offer ports on UDP and TCP for the media path. This will allow the SFB client to discover the available public IP for the SFB media path inorder to establish the connectivity. The new name for this acronym is Session Traversal Utilities for NAT. All Lync/SFB clients are ICE clients and use ICE to try and establish connectivity between itself and another ICE client.Remember this is the main protocol which functions as the core and wraps the other 2 to establish a path. The stands for Interactive Connectivity Establishment protocol for communications. SFB/Lync uses all these 3 protocols to establish a media connectivity: Now this is the time for me to dig into the analysis of in which protocol fashion the SFB clients establishes the connection.So started to explore on STUN,TURN & ICE since ever i was having a glossy look on these topics. Getting error as call failed due to media connectivity failure when both the end points are remote. Please try again later)ġ)Did a telnet to on port 80 and 443 – ( This was done just to make sure the clients when logging in gets all the updated info of the pool,SFB config etc.,)Ģ)Did a telnet to on port 443 – successfulģ)Did a telnet to on port 443 – successfulĤ)Did a telnet to av. on 443 successfulġ)The edges were in DNSLB and were in scaled consolidated topology using NAT.Ĥ)Port 50k was blocked in my case since no legacy OCS clients.ĥ)No edge hair pin traffic is allowed for Audio and Video Public Ips.ĭid a Snooper trace from the affected remote client and got the following info on the snooper logs Please try again later)Ģnd test – from remote users n/w to my office n/w – received error (we couldn’t connect to the presentation because of n/w issues. This a new deployment and users were unable to present desktop.ġst test – from remote users n/w to my home n/w – received error (we couldn’t connect to the presentation because of n/w issues. All Skype for Business Clients from remote locations were unable to present the screen sharing through meet now ,peer to peer and conference.
0 kommentar(er)
