A PG, under the same customer instance, can only have a single ACD PIM type combined with VRU - e.g. CCM and IVR, Avaya and IVR, Symposium and IVR. The best solution is to install 2 PGs, so PG1 is PIM1 CCM and PIM2 IVR and PG2 is PIM1 Avaya. Two different ACD type (e.g. CCM and Avaya) on the same PG is not allowed.
Adding another Customer Instance (on the left hand side on the first screen in ICM Setup) is not a viable solution.
I think that I have got to note that you can try to install two different PGs in the same machines only for testing purpouses, not for a production system.
I had got to do that configuration for a customer to show the ICM capabilities with a CallManager and an Avaya Definity. For hardware limitations, I only had got one machine to install the full system, and I got it, but with a lot of work.
Apologies for not specifying the use of this architecture in a lab enviroment.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...