Can anyone please explain why UCCX and Q.sig path replacement are mutually exclusive? I have a client who is looking to deploy UCCX 5.0 as an adjunct IVR to a Siemens ISDX. The IVR provides an operator transfer-out option. The operator consoles are associated with the ISDX - call queuing will be provided by the ISDX. This is a busy IVR. E1 integration exists between CUCM5.0 and the ISDX. Clearly without path replacement this is going to chew up a lot of channels.
Hi, we are experiencing the same problem with an IVR from other vendor, Did you manage to configure a workaround?
Getting Started
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: