It sounds as though your Lync install requires some serious post-installation best practice guidelines following. Please allow me (as an avid supporter, consultant and v.heavy user of Lync) to retort, as constructively as possible.īest practice guidelines recommend you should not run Lync via VPN’s, due to the complexities of double encrypting traffic and various NAT concerns. A split-tunnel VPN solution (directing Lync traffic outside of your VPN tunnel) is recommended. To address a host of your other concerns i would be checking exact scenarios with your Lync monitoring server. Usually, it is due to the nature of one participants Internet connection (3g stick on a train anyone?), VPN issues (see above), or other. Your monitoring server will be able to reveal more on this. Microphone and audio issues the same, i have never experienced any of the issues you speak of above. ![]() However, i do always attempt to use a wired connection where possible, or my own personal home wi-fi, ie not contested 3g data networks or public hotspots. Lync is an excellent product, but it can’t work miracles digging your traffic through the crowded Starbucks wi-fi. If you’re forced onto these connections, stick with IM&P only, or use the intelligent feedback the Lync client provides. If it’s reporting “poor network quality”, it’s unreasonable to expect a perfect HD call. In which case, switch modality to a gsm call, or, as above, stick with IM&P. With reference to your comparison to the mobility clients vs Skype. Consider this… Skype can do it, we all know this. But Skype is free, and Lync is an enterprise grade product. ![]() Your company paid good money in licensing, hardware and implementation costs for Lync, so there should be no compromise. In short, if we cant guarantee a top quality call or at least report back on why it was poor quality, it wont be enabled.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |