ALU sells the CCO, standard Tserver 7.5 (iirc) with routing to a pilot (not a RSI) in PBX.
It works pretty well, but ALU provides it’s own SDK for PCSoftPhone (not a voip phone!) application for Agent,
i wonder if anyone was so brave to use only Tserver from this bundle, integrate with Tserver with standard SDK from Genesys and survived this, to tell a story about it.
If not, then, well wish me luck. 8)
I’ll save my comments to avoid repeat
And i will go to another town to install this, and IF i survive the test run, i will describe what was done and what was not possible.
Just another silly question: 100 agents, as per docs = 150 B channels (so, at least 5 T2 trunks) to do outbound, is this correct or docs need to be treated as ‘good, oldalcatel docs’ ?
1 Like
In Predictive mode? Then yes…150x1.5 dialing resources
Good luck!! ;D
2 Likes
150x1.5=225 times a Ghost Z ? (virtual, analog port if someone is not ALU-oriented).
1 Like
Yup. You can find all that on CCO installation guide:
Virtual Z nb = CCOutbound agent nb x 1.5Progressive and Predictive dialling mode requires Voice Activity Detection feature
This feature is hosted on GPA board, which can handle max 5 DSP,9 VAD per DSP (=> Max:
45 VAD per GPA).VAD nb = predialling (i.e progressive and predictive ) CCOutbound agent nb x 1.5
Example:
Considering an installation with
100 CCD declared agents (including 20 CCOutbound agents)
40 CCD agents simultaneously loggued (20 CCD + 20 CCO)
20 CCOutbound agents with 5 in preview and 15 in progressive/predictive modethe OPS locks would be:
47 -Alarm47xx_via_CMIP = f ( subscriber nb )
76 -CCDNumberAgents = 40 (simult. Logged)
115-CCAAgents = 0 (not used for CCA loggued with “CCO” Boolean)
158-CSTAByPass = 146 ( 100 + 20 CCOutbound x1.3 + 20 CCA)
161-CCO:agents = 20
162-Ccoutpredialling = 15
169 -VAD = 0 bypassed when CCO in OTR4.2
189 -CCTI = 20 for SDK use in OTR4.2
312 – Outbound Scripting = 20 (is using CCO scripting 5.1)
+ hardware: 15 x 1.5 = 23 VAD calculated by Actis (i.e 3 DSP)
Well, at least i have the very same doc ! >
Test run deployment ETA: 7-10 days.
1 Like