ipccx coresident with ccm

Answered Question
Dec 15th, 2007

hi

in http://www.cisco.com/en/US/partner/products/sw/custcosw/ps1846/products_promotion0900aecd800fe55c.html

it states that :

Co-Resident Performance and Capacity Limitations: Cisco Unified Contact Center Express 3.5 and 4.0 Standard and Enhanced

Cisco Unified Contact Center Express 3.5 Standard and Enhanced, when deployed on the same server as the Cisco CallManager, may not exceed the following limitations:

• No more than 10 agents

• No more than 1 supervisor (not taking calls)

• No more than 10 prompt and collect ports

• For Cisco Unified Contact Center Express Enhanced, no more than 1 recording or 1 monitoring session

• Running of no more than 1 historical report, and only during periods of low Cisco Unified Contact Center Express or Cisco CallManager activity

does this mean that ipccx (standard or enh) when deployed coresident with ccm supports only up to 10 agents in addition to the other points (up to 1 supervisor, up to 10 promptcollect ports,...) ?!

thanks

I have this problem too.
0 votes
Correct Answer by Chris Deren about 9 years 1 month ago

Sorry, I guess the main reason for that is to force customrs to get dedicated servers for ease of support, also UCCX does place some stress on the server resources in busy contact center and CallManager server might be bit overwhelmed :-(

Chris

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 4.5 (2 ratings)
Loading.
Chris Deren Sun, 12/16/2007 - 08:05

You got it. Keep in mind that the cooresident deployment can only be done on Windows based CallManager as there is no platform UCCX yet.

HTH,

Chris

user-cisco Sun, 12/16/2007 - 08:27

thanks chris for ur response, but is it strange to support up to 10 agents in case of coresident deployment against up to 300 agents in case seperate ipccx server!

Correct Answer
Chris Deren Sun, 12/16/2007 - 08:32

Sorry, I guess the main reason for that is to force customrs to get dedicated servers for ease of support, also UCCX does place some stress on the server resources in busy contact center and CallManager server might be bit overwhelmed :-(

Chris

Actions

This Discussion