Does your company allow Skype in network? What are reasons to forbid it, and how it is enforced? Is it done for security concerns?
closed as primarily opinion-based by kce, Ward♦, mdpc, Michael Hampton♦ Aug 28 '13 at 0:59
Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise. If this question can be reworded to fit the rules in the help center, please edit the question.
locked by Michael Hampton♦ Aug 28 '13 at 0:59
This question exists because it has historical significance, but it is not considered a good, on-topic question for this site so please do not use it as evidence that you can ask similar questions here. This question and its answers are frozen and cannot be changed. See the help center for guidance on writing a good question.
Read more about locked posts here.
Skype is P2P so it eats up bandwidth. Also nominates users with good connection to serve as hubs, forwarding connection between other users. That eats up lot more bandwidth and CPU. You have absolutely no control over it. Other problem with Skype, that being P2P it uses firewall punch-trough, which of course admins don't like.
No. It is actively removed from managed systems. It is forbidden for bandwidth & security reasons as well as the fact that voice services and other forms of IM are provided.
Skype is the voip solution for the office; when you have a small office (<10 people) it suffices.
Yes we do.
For small offices it is a great tool for communicating. It can use lots of bandwidth but if the company does lots of traveling, the cost savings from international long distance can be great.
We actually use it more for chat than voice, but since it does both we don't need another IM client on the desktop.
For business or personal purposes? We used to use it for business, but dropped it for a proper voip system.
I wouldn't allow it for personal use, just like I wouldn't allow IM.
We allow and use it, although less than we used to. It used to be our main solution for inter-office communication internationally, but we now have a wider VoIP network that takes its place. We still use it to communicate between folks working at home and folks in the office on occasion, but even that's falling away as Office Communicator takes its place.
That said, we've seen no reason to block it (or external IM, for that matter)
No for one of several reasons:
- Not SOX compliant
- No Central logging
- Resource and network bandwidth hogger
It's my department's preferred medium for 'working' remote conferences (like doing an after-hours release with the people involved at home).
No, it's in competition with our parent company products - we are owned by a large telco. Their product is VOIP and allows logging and monitoring of calls not just by team leaders but also by Human Resources. Control of access is what it all boils down to really.
We do not allow Skype behind the firewall. We provide a good phone system, with lots of good features and excellent rates. The primary reason is to control network performance, secondary reasons are to control what gets through the firewall and to reduce opportunities for non-work activities.
We do allow the "road warriors" to have it on their laptops, but don't support it. Several of them use it to communicate with the home front.
We block it using a web filter product from Websense.
My co does not install it, but they did allow it as they understood some of our clients will reply faster via skype than say email.