Bridge Operator Console Choosing an Attendant Console

When choosing an attendant console there are several factors to consider

  • Number of operators - How many users will be running the software at 1 time.
  • Shared information - Whether you want your users to be able to share contacts, chat with each other, or have shared park detail.
  • The cost - What will the replacement cost be on something that used to be free.
  • The architecture - How the AC solution will interact with the CUCM.

There are 2 main types of solutions


Serverless Standalone Client

A viable solutions for a single operator environment

Pros of Standalone

Ease of Installation

The entire product can be deployed on a single PC. There is no server or virtual machine to setup and maintain to make the product work.

Price

For a single operator this is usually a more cost effective deployment. Once you need more than a single operator, the pricing and features offered by Bridge Operator Console in Client/Server mode will be far superior to any other product.

In a single operator deployment a stand alone, serverless solution will be able to obey the data restrictions and not overburden the CUCM cluster.

Cons of Standalone

Harder to backup important data

Some sort of PC based backup would need to be deployed to ensure any AC data was preserved in the event of a machine failure.

Scalability

A serverless deployment will not scale beyond a couple of users. The CUCM model has it's data query, CTI, Real-time services, and performance monitoring services throttled to protect call integrity. If you try to push the number of installed clients beyond a few you'll cause several issues with your phone servers.

Data Sharing

Users will have a difficult time sharing contact data, meaning many more hours of data entry will be necessary to maintain the same number of contacts.

Once the number of operators grows too large, the operators will not be able to function efficiently without causing problems on the CUCM cluster and affecting all the users on the system.


Client / Server Deployment

The best solution for more than one operator

Pros of Client/Server

Scalability

By using the server to limit the use of the CUCM resources, this deployment can scale up to over 100 clients quite easily.

Price

If you require 3 or more clients with our pricing model it becomes less expensive to deploy this model, including the OS license.

Backup

It is much easier to overcome hardware failure in the client / server model especially if your server is deployed in a virtual environment.

Extended Features

In this deployment it is much easier to take advantage of extended features, like shared park for visibility, messaging, paging, chat, and more.

WAN friendlier

Deploying this way allows you position servers near subscribers avoiding the need to back haul everything over your WAN.

Data Sharing

This deployment makes it easier for all operators to share a global address book, copy contacts to each others personal AB, chat, and see shared visibility of users and parked calls with extended details.

Cons of Client/Server

Server License Required

A valid server OS license would need to be purchased for server install.

Our Competitors Client/Server

Our competitors Client / Server models also suffer from several other Cons like; Phone, Queue or User Limits, use of CTI Route points, Proprietary parking lots and music on hold, very expensive, no Mobile device support, no Messaging, no Paging, and worst of all they are difficult to learn and use.


Some Good News

We Offer Both Types of Solutions! And... we have the only path so you can migrate from Stand alone to Client / Server as your business grows.