Below are some commonly asked questions and answers
Q: What are the components I need?
A: There are two base pieces to a BOC build out, the BOC Connector
and the BOC Client. You will need a dedicated Windows server (2003
or better) to run the BOC Connector. You will also need access to a
Microsoft SQL server. You may use the free Microsoft SQL Express
running on the BOC Connector server in smaller environments.
Recommended: For optimal usage, we recommend the BOC
Client for each user with a phone and a computer within your
Client Operating Systems
Q: Will this program impact my phone server?
A: Unlike most of our competitors, BOC uses a middleware piece we
call the BOC Connector. The end user client does not talk directly
to the phone server. With most deployments, there is only ever one
connection made to the phone server, not one per receptionist or
user. This allows us to scale much larger, without any more impact
on your phone server. In a Cisco Call Manager environment, our
Connector can even be directed at the subscriber with only an
imperceptible reduction in performance.
Q: Does the client have a full 64 bit version?
A. Yes. The client does not talk directly to the
phone server. Therefore our client is not dependent upon
the TAPI service provider being supported on the client
operating system. That gives us a huge advantage over the
competition, since our program runs like you'd expect on
today's modern computers, without having to run in emulation
mode. Windows 7 64bit, no problem!
Q: Does BOC answer calls instead of the phone?
A: Absolutely not. We are not a softphone or phone
system. At any time you can switch
between BOC, your phone, or a headset midstream in any call.
They are all completely interchangeable with 100%
functionality at any point during the call. We merely
"observe and report". We function very much like a
smart remote control for phone. We don't not take any function away
from your phone server. You do not have to make a conscious
choice on how you will answer the phone.
Q. Can I run the connector service in
a virtual environment such as VMware?
A. Yes, in fact that is our preferred method of
installation. VMWare and others have the ability to deploy
and maintain a high availability installation resilient to
hardware failure and excessive machine loads. In addition,
the virtual machine will not suffer from the hardware/driver
incompatibility issues that are possible in a physical
Q. Can the client be run in Terminal
Services or Citrix?
A. Yes. Since we don't answer the phone or make any sort of
direct connection to the phone serer, these environments
work fine with our client. Our client is relatively
lightweight and will not significantly impact a terminal
Q. How many phones will BOC be able to
monitor and control?
A. That largely depends on the landscape of your
organization, size of your phone server, and power of the
connector server. We haven't hit any limit yet, in
fact, many customers have over 7500 phones running on a
minimum single processor connector.
Q. Do I have to scroll to find users, and
what happens when another call comes in?
A. Simply put, the screen will not refresh during a call
transfer causing you to lose your place or worse, the call.
BOC offers fast searching, globally across all phones, on
name or extension all from a single box. When another call
comes in, we won't alter your existing search or navigation.
We are built to be easy to use. For example, there are 10
different ways to transfer a call with BOC (5 attended and 5
blind transfer methods). In short, without any training a user
can transfer a call. There is almost no wrong way to do it.