03-02-2009 10:56 AM - edited 03-15-2019 04:33 PM
I have an IP Communicator phone on my desktop. You can make on campus, local, long distance and international calls from the IC. When you call into the IPCC Queue, you are trasferred two times and get a fast busy signal. How can we correct this problem?
03-02-2009 10:59 AM
Can you explain the problem a little more elborately ? When you call into IPCC queue and you are logged into CAD (using IPComm), you will get the call the first time (3 or 4 rings or how many you set in the IPCC script) and then it will push your status on CAD to not ready mode and place teh call in queue (caller will hear MOH if configured). This should be the normal behaviour...
During this period if you go back to ready mode, of course the call will transferred to you a second time..
03-02-2009 12:04 PM
Two of the numbers that take you into IPCC Queue are 8110 or 4357. If you call either one of these numbers from an IP Communicator device you will get transferred twice and get afast busy signal. At this point we are not using IP Communicator to log on/off of IPCC.
If you use the IP Communicator device to call local,LD, International it works just fine. Something that has to do with IPCC makes the call not go through.
03-02-2009 12:13 PM
Hello,
This sounds like a codec problem. Check your location/region configuration. More than likely, the call from the IP Communicator is trying to reach the IPCC over G729, and the IPCC is more than likely set to talk G711 codec.
Therefore, set whichever device pool the IP Communicator resides in to talk G.711 to the device pool in which your CTI route points for IPCC reside.
Hope that helped, if so please rate.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide