Choosing a replacement for Cisco Attendant Console

There are several factors that will come into play when choosing a product to replace the legacy Cisco Attendant Console.

The Factors

 

1.  Number of operators - How many users will be running the software at 1 time.

2.  Shared information - Whether you want your users to be able to share contacts, chat with each other, or have shared park detail.

3.  The cost - What will the replacement cost be on something that used to be free.

4.  The architecture - How the AC solution will interact with the CUCM.

 

Two main types of solutions

 

1. Serverless Standalone Client - A viable solution for a single operator shop

 

Pros

Cons

Ease of Installation - The entire product can be deployed on a single PC

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.

Price - For a single operator this is usually a more cost effective deployment

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.

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

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.


*Our competitors serverless options also suffer from many other Cons like;
Java based, no 64 bit option, lack of AD integration, no Messaging, no Paging, no Ipad or Android version, No Jabber or Lync integration, no Hunt Group login/out or visibility, and many more.

 

2. Client / Server Deployment - The best solution for more than one operator

 

Pros

Cons

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

Server License Required - A valid server OS license would need to be purchased for server install.

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.

*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.

See pricing details here

 

 

Related Content

© 2016 Bridge Communications - Closing the Communications Gap - +17012124797

  Rating: ★★★★★ (98 out of 100) Total votes: 197 (197 reviews) See Reviews

Contact Bridge Communications