Recommended Posts

Hi everyone. My job is looking into switching to VOIP and they want my involvement, but I don't really know much about VOIP so I figured I would ask. They're of course talking to some people that say that it is, but of course they're going to say that... They want to sell us equipment... But I figured the Neowin members are pretty knowledgeable so I could trust their information.

So, is VOIP ready for adoption in a corporate environment? Of course up-time, call clarity, call forwarding, call transferring, and reliability is all very important. A company can't really afford to miss a phone call. We would also have several lines as well, as we do now.

I really don't know a heck of a lot about VOIP. I've been reading up a bit on it of course, but I don't know anyone who's actually rolled out a VOIP system. I'm not sure what I should know going into this, what issues may be involved which I wouldn't think of, etc. So I'm asking everyone their opinion. Any and all information is greatly appreciated.

Thanks Again, I'm very curious to hear what everyone has to say.

-Matt-

Link to comment
https://www.neowin.net/forum/topic/841818-is-voip-ready-for-prime-time/
Share on other sites

I have not read everything that u wrote but bottom line is that yes it is ready for a corp inv.

Vonage is based off of voip. The comcase tripple play is based off of voip, verizon fios phone service is based off of voip. So it would be safe to say a corp phone system can be voip based.

I said it years ago when it really was in its infancy before vonage came out that it was the future of phone service.

Thank you both very much for your responses. I really appreciate it. What if there is some slow down on the DSL line, or one or several users are downloading large files, or something? The fact that this uses the internet line for the conversations is a concern for me. I don't know much about this. They did say that we could use our current phones, so that's a plus. Do you think DSL is fast enough? Or do we need something faster? How much bandwidth should we have?

Thanks Again,

Nothing is going to be fast enough. But what you should be primarily looking at is QoS. Well designed QoS policy will make sure that you will always have required bandwidth for your voice/video traffic. Do some home work on these technologies and how they best work together, before you go ahead with a solution.

From your post its not clear whether you are going for single site or multiple sites implementation. However, a voice call will take somewhere between 8Kbps to 64Kbps depending on sampling and quality you are looking for. You also have ability to setup a quota for simultanious voice call, this can help in avoiding the overloading of the WAN links.

Another important point you should consider is whether to go for industry standard VoIP solution or proprietary VoIP solution. Propriety solution allow vendors to add more features & functions into their devices but locking you into a specific vendor. With industry standarized solution you have the ability of going across different vendors but you will be getting only basic features and functionality.

Hi everyone. My job is looking into switching to VOIP and they want my involvement, but I don't really know much about VOIP so I figured I would ask. They're of course talking to some people that say that it is, but of course they're going to say that... They want to sell us equipment... But I figured the Neowin members are pretty knowledgeable so I could trust their information.

So, is VOIP ready for adoption in a corporate environment? Of course up-time, call clarity, call forwarding, call transferring, and reliability is all very important. A company can't really afford to miss a phone call. We would also have several lines as well, as we do now.

I really don't know a heck of a lot about VOIP. I've been reading up a bit on it of course, but I don't know anyone who's actually rolled out a VOIP system. I'm not sure what I should know going into this, what issues may be involved which I wouldn't think of, etc. So I'm asking everyone their opinion. Any and all information is greatly appreciated.

Thanks Again, I'm very curious to hear what everyone has to say.

-Matt-

We mainly use mobile wifi phones in our office, like the SC-6060S from www.yippz.com. They work great anywhere in the office. can be taken on the road, and sound much better than our old phone lines and cell phones (with no monthly massive cell bills). We also have several office Voip phones that do pretty much anything you would want an office phone do to. Most features are dependent on which voip provider you choose. Voip service is SO cheap now that any company can save hundreds in the first month.

Unlike Voip several years ago, sound and reliability are nearly perfect these days.

Nothing is going to be fast enough. But what you should be primarily looking at is QoS. Well designed QoS policy will make sure that you will always have required bandwidth for your voice/video traffic. Do some home work on these technologies and how they best work together, before you go ahead with a solution.

From your post its not clear whether you are going for single site or multiple sites implementation. However, a voice call will take somewhere between 8Kbps to 64Kbps depending on sampling and quality you are looking for. You also have ability to setup a quota for simultanious voice call, this can help in avoiding the overloading of the WAN links.

Another important point you should consider is whether to go for industry standard VoIP solution or proprietary VoIP solution. Propriety solution allow vendors to add more features & functions into their devices but locking you into a specific vendor. With industry standarized solution you have the ability of going across different vendors but you will be getting only basic features and functionality.

Wow, thank you VERY much for your great response. That was really very helpful. I wasn't even aware that I had to decide between a proprietary solution and a standard solution... I guess a standard solution probably makes the most sense really, doesn't it? We've been locked into systems in the past, and that just never seems to work out in the end.

When I spoke to the one VOIP company the other day on the phone they said that they did 16 kb's a phone call, but they didn't seem to be very confident about their explanations of things, so I'm not sure. We would be looking at a single site implementation I would imagine, as we only have the main office. But they told us that if we took the phone to our home and connected it to our router there that we would be able to use that phone then as if we were at the office.

I am going to research those technologies you mentioned as well. I've never heard of them before. This is all new to me, and I don't want to make any noobish mistakes...

We mainly use mobile wifi phones in our office, like the SC-6060S from www.yippz.com. They work great anywhere in the office. can be taken on the road, and sound much better than our old phone lines and cell phones (with no monthly massive cell bills). We also have several office Voip phones that do pretty much anything you would want an office phone do to. Most features are dependent on which voip provider you choose. Voip service is SO cheap now that any company can save hundreds in the first month.

Unlike Voip several years ago, sound and reliability are nearly perfect these days.

Thank you very much for that suggestion. I am DEFINITELY going to consider that. That sounds like a really good idea. Then we just tell the VOIP company that that's the phone we have and they set them up? I really like that idea. The time and expense it saves in laying phone lines (And connecting them to the router) seems to be well worth it. Does that phone support encryption? Our network at the office is security enabled. It sounds like you can set it up with different profiles, so if you were at the office it would connect, at home it would connect, etc. without any setup. That is a very nice feature (If I'm understanding it correctly).

Thanks Again everyone for all of your help. It's been invaluable really. I've learned a lot.

It depends on the size of the company, If a plain DSL connection is enough to handle everybody then the company just wouldn't be that large. Of course, you could get multiple DSL connections, one for VOIP and one for everything else.

Thanks for your suggestion too. Getting a second DSL line is definitely cheaper than upgrading to T1 or something.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Not even an OLED display on the laptops. Also it seems that the laptop design isn't the same as the Surface Ultra model. Looks like bargain bin at high prices.
    • make your own notch - it's not that hard
    • VirtualBox 7.2.10 by Razvan Serea VirtualBox is a powerful x86 and AMD64/Intel64 virtualization product for enterprise as well as home use. Targeted at server, desktop and embedded use, it is now the only professional-quality virtualization solution that is also Open Source Software. Presently, VirtualBox runs on Windows, Linux, macOS, and Solaris hosts and supports a large number of guest operating systems including but not limited to Windows (NT 4.0, 2000, XP, Server 2003, Vista, 7, 8, Windows 10 and Windows 11), DOS/Windows 3.x, Linux (2.4, 2.6, 3.x, 4.x, 5.x and 6.x), Solaris and OpenSolaris, OS/2, OpenBSD, NetBSD and FreeBSD. Some of the features of VirtualBox are: Modularity. VirtualBox has an extremely modular design with well-defined internal programming interfaces and a client/server design. This makes it easy to control it from several interfaces at once: for example, you can start a virtual machine in a typical virtual machine GUI and then control that machine from the command line, or possibly remotely. VirtualBox also comes with a full Software Development Kit: even though it is Open Source Software, you don't have to hack the source to write a new interface for VirtualBox. Virtual machine descriptions in XML. The configuration settings of virtual machines are stored entirely in XML and are independent of the local machines. Virtual machine definitions can therefore easily be ported to other computers. VirtualBox 7.2.10 changelog: VMM: Fixed issue when CentOS 10 VM was not booting due to the message "Fatal glibc error: CPU does not support x86-64-v3" (​github:gh-642) Devices/EFI: Fixed booting issue when ARM VM had less than 1024 MiB of RAM assigned (​github:gh-679) USB: Fixed issue when it was not possible to attach USB device to headless VM on Apple Silicon/macOS 26.4.1 (​github:gh-631) Storage: Fixed issue when VIRTIO-SCSI device was not recognized as SSD device by guest system (​github:gh-634) Network: Fixed issue in E1000 emulation code which triggered debug log creation (​github:gh-645) Network: Fixed issue in E1000 emulation code which prevented OS/2 guest from booting (​github:gh-683) Linux Host: Fixed issue when VMs could not be started due to kernel oops (​github:gh-639) Linux Host and Guest: Fixed issue when kernel modules were failing to build with openSUSE 16.0 kernel Linux Host and Guest: Added initial support for kernel 7.1 Linux Host and Guest: Added extra fixes for RHEL 9.8 kernel (​github:gh-676) Linux Host and Guest: Added possibility to build source code using NASM instead of YASM as the assembler (​github:gh-520) Linux Guest Additions: Added initial support for Extended Data Control Protocol for clipboard sharing with Plasma on Wayland guests (​github:gh-33) Linux Guest Additions: Added extra fixes for preventing vboxvideo kernel module build with kernel version 7.0 and newer (​github:gh-655) OS/2 Guest Additions: Fixed issue when Shared Folders automount and clipboard sharing stopped working (​github:gh-551) Download: VirtualBox 7.2.10 | 170.0 MB (Open Source) Download: VirtualBox 7.2.10 Extension Pack | 19.1 MB View: VirtualBox Home Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • OK, now ask yourself how are they going to enforce that law? By requiring every single adult to prove their age and provide their legal identity documents to an UNREGULATED 3rd party company that already has a long track record of multiple data breaches. Not to mention, parliament have voted AGAINST this ban, twice, and Starmer is going ahead anyway. So, where's the democracy here, because that looks like dictatorship to me. The solution here is parental responsibility, not government control. Run some public service announcements on TV and UK social media teaching parents how to setup parental controls. That's already been proven to actually work. But the, this is not and has NEVER been about keeping kids safe. It's about control and monitoring. Watching what you're doing online and controlling what you can see and what you can say.
    • Interesting read. I knew the adware was quite controversial at the time, however never realised to the point The Guardian wrote an article about Patchou. I just said no and enjoyed his creation, I’d probably be a lot more wary of something like that today though.
  • Recent Achievements

    • One Month Later
      Windows Guy earned a badge
      One Month Later
    • One Month Later
      Prasann earned a badge
      One Month Later
    • Week One Done
      Prasann earned a badge
      Week One Done
    • First Post
      Dys Topia earned a badge
      First Post
    • Collaborator
      vjlex earned a badge
      Collaborator
  • Popular Contributors

    1. 1
      +primortal
      525
    2. 2
      +Edouard
      180
    3. 3
      PsYcHoKiLLa
      105
    4. 4
      Steven P.
      89
    5. 5
      ATLien_0
      70
  • Tell a friend

    Love Neowin? Tell a friend!