Help with D/B/E Attendant Console sizing

Unanswered Question
Apr 6th, 2012

Hi I have operators working in 5 different locations each with local access numbers, some with overlapping.

We need a solution that can help then since we are upgrading from CUCM 6.1.3 that had a attendant console to 8.5.1 that needs a separated server.

By first we were recommended to use Enterprise since we can expand from the 9 operators that are working at the same time, but the instalation of the trial for the Enterprise seems to cause more problems than solve since I can't separate cti port groups to each queue, and for the operator to fully function they need to have separated CSS to allow exit through the correct location even more for blind transfers.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Average Rating: 0 (0 ratings)
jamgale Wed, 04/11/2012 - 14:03

Hi,

You are correct, today the product only uses a single pool of CTI Ports in the system, this does mean you have to use the same CSS/PTN/MoH for all the queues and operators.

In version 9 (due for release in June) it will be possible to create multiple pools of devices and associate these to queue(s), this will allow the configuration you are after.

In the meantime, there is actually a way to by pass the use of CTI Ports when performing a blind transfer called direct transfers, you can enable this on the Operators PC and what it does is redirect the call from the orginating device (voice gateway) and will therefore use the CSS of that device and therefore achieve what you are after.

The "downside" of using this is that it removes the feature of recalling calls if the transfer goes unanswered, this is because CUEAC is not able to monitor the call once the redirect has taken place.

Hope this helps.

Actions

Login or Register to take actions

This Discussion

Posted April 6, 2012 at 8:55 PM
Stats:
Replies:2 Avg. Rating:
Views:456 Votes:0
Shares:0
Tags: No tags.

Discussions Leaderboard