CVP server/port limits in UCCE UCS deployments

Question

Hello
I am reviewing the Docwiki for UCCE/CVP deployments in a UCS environment.  The highest
capacity example was for 12000 agents and 3600 N+N CVP ports.  This CVP port sizing
is not the limit though?  I was reviewing Cisco Unified Customer Voice Portal  book and
it had the same example but in the notes section it states that "any number of unified cvp
VM's and combinations of coresidency of unfied CVP VM's  with other UC applications
are possible on an ESXi server..." as long as the resources of the CPU, memory, etc
are not over commited.
In my design, we are using B200 M3's and I should be able to have 5500 CVP ports and 5500 CVP
redundant ports running on their own respective CVP servers assuming Im not exceeding
the capcity of the blades (Im not spliitting across any cores).  This would be a router/logger configuation
with 6500 agents (hybrid - ICM agents and UCCE agents)
So as long as I observe the resource allocations of the blade servers, I should be ok for
5500 ports N+N, 7500 ports N+N, etc?
Thanks
Mike Kana

Answer 1

Yasir,
You can do this with what you already have. There are no extra licenses required.
Designing the CVP application to do the recording will take some work. You will need to set up FTP on both CVP Media servers so that you can transfer the recorded prompt to both of them. For putting prompts into the right locations in the ICM script, you have a couple options that I see:
Have the CVP app overwrite prompt files directly based on selections made in a menu.
Have the CVP app create a new file on the media server for each recording, and write the filename to a SQL database that ICM can read from with a DB lookup node.
Combination of options 1 and 2, but using the database to store activated/deactivated status
I've built a similar application before myself. I used static filenames for each prompt - the user calls the application, supplies the ID of the prompt they'd like to record, and can then activate the prompt and set a duration to leave the recording active for. It's very useful for putting any sort of emergency messaging in place. I could see using the same basic design for all of the prompts in an ICM script, though it would add a lot of time to setting up the ICM script.
-Jameson